Load balancing SCTP associations using VTAG mediation
Presented is a system and methods for routing Stream Control Transmission Protocol (SCTP) between a client and a back-end server by a front-end server operating transparently between the client and the back-end server. The front-end server uses a distribution key created by the front-end server to route the SCTP packets to the proper destination. The distribution key is comprised of a client SCTP port number, a back-end server SCTP port number and a back-end server Initiate-Tag. The front-end server arbitrates clashes between distribution keys of different back-end servers by replacing the back-end server generated SCTP Initiate-Tag with a front-end server generated SCTP Initiate-Tag.
1. A method, stored in a memory and executing on a processor, for distributing Stream Control Transmission Protocol (SCTP) packets between a client and one of a plurality of back-end servers, the method comprising:
routing by a front-end server said SCTP packets, each of which includes a distribution key created based on SCTP parameters associated with said client and said one of said plurality of back-end servers wherein said plurality of back-end servers share a virtual internet protocol (VIP) address with said front-end server;
wherein said distribution key comprises:
an SCTP port number provided by said client;
an SCTP port number provided by said one of said plurality of back-end servers; and
an SCTP Initiate-Tag provided by said one of said plurality of back-end servers; and
wherein said front-end server detects a clash between a first distribution key created for a first back-end server SCTP association and a second distribution key, while creating said second distribution key, for a second back-end server SCTP association and generates a replacement SCTP Initiate-Tag for said second distribution key to preserve the uniqueness of said first distribution key and said second distribution key.
2. The method of claim 1 , wherein said distribution key is generated by said front-end server.
3. The method of claim 1 , wherein said front-end server manages said replacement SCTP Initiate-Tag by maintaining a verification tag translation table to hold said replacement SCTP Initiate-Tag and said second distribution key as a matched pair.
4. The method of claim 1 , wherein said front-end server updates a SCTP common header associated with said second distribution key based on said replacement SCTP Initiate-Tag and recalculating a checksum associated with said SCTP common header.
5. The method of claim 1 , wherein said front-end server operates transparently with regard to said plurality of back-end servers.
6. The method of claim 1 , wherein said plurality of back-end servers, sharing said VIP address, operate independently of each other and are not aware of the existence of each other.
7. The method of claim 1 , wherein said method does not require Stream Control Transmission Protocol (SCTP) modifications.
8. The method of claim 1 , wherein said method does not require Internet Protocol (IP) header modifications.
9. The method of claim 1 , wherein said Initiate-Tag is configured to be the address of said one of said plurality of back-end servers.
10. A front end server for distributing Stream Control Transmission Protocol (SCTP) packets between a client and one of a plurality of back-end servers, comprising a processor and a memory, said memory containing instructions executable by said processor whereby said processor is operative to:
route said SCTP packets, each of which includes a distribution key created based on SCTP parameters associated with said client and said one of said plurality of back-end servers wherein said plurality of back-end servers share a virtual internet protocol (VIP) address with said front-end server;
wherein said distribution key comprises:
an SCTP port number provided by said client; an SCTP port number provided by said one of said plurality of back-end servers; and an SCTP Initiate-Tag provided by said one of said plurality of back-end servers; and
wherein said front-end server detects a clash between a first distribution key created for a first back-end server SCTP association and a second distribution key, while creating said second distribution key, for a second back-end server SCTP association and generates a replacement SCTP Initiate-Tag for said second distribution key to preserve the uniqueness of said first distribution key and said second distribution key.
11. The front end server of claim 10 , wherein said distribution key is generated by said front-end server.
12. The front end server of claim 10 , wherein said front-end server manages said replacement SCTP Initiate-Tag by maintaining a verification tag translation table to hold said replacement SCTP Initiate-Tag and said second distribution key as a matched pair.
13. The front end server of claim 10 , wherein said front-end server updates a SCTP common header associated with said second distribution key based on said replacement SCTP Initiate-Tag and recalculating a checksum associated with said SCTP common header.
14. The front end server of claim 10 , wherein said front-end server operates transparently with regard to said plurality of back-end servers.
15. The front end server of claim 10 , wherein said plurality of back-end servers, sharing said VIP address, operate independently of each other and are not aware of the existence of each other.
16. The front end server of claim 10 , wherein no Stream Control Transmission Protocol (SCTP) modifications are required.
17. The front end server of claim 10 , wherein no Internet Protocol (IP) header modifications are required.
18. The front end server of claim 10 , wherein said Initiate-Tag is configured to be the address of said one of said plurality of back-end servers.