Load-Balancing via Modulus Distribution and Tcp Flow Redirection Due to Server Overload

1. A method of routing IP packet flows, the method comprising: coupling an Ethernet switch to a load balancing control engine; configuring load balancing logic within the load balancing control engine to be hidden from the Ethernet switch; the Ethernet switch receiving an IP packet flow, wherein the Ethernet switch routes packets of the IP packet flow to servers from multiple server groups, wherein the multiple server groups comprise a firewall server group, an intrusion detection system (IDS) server group, and an anti-virus application server group; redirecting the IP packet flow to a specific sequence of servers, wherein each server in the specific sequence of servers comes from a different server group from the multiple server groups, and wherein the IP packet flow is redirected to sequentially pass through a selected server from each of the firewall server group, the IDS server group, and the anti-virus application server group; the load balancing control engine determining if the servers are balanced in their utilization; in response to the load balancing control engine determining that the servers are balanced, the Ethernet switch routing the IP packet flow to the servers without the Ethernet switch directly receiving any feedback from the servers regarding their utilization; and in response to the load balancing control engine determining that the servers are unbalanced, the load balancing control engine instructing the Ethernet switch to redirect the IP packet flow to a server that is relatively less busy than other servers.

2. The method of claim 1 , wherein a record of where the IP packet flow is directed is stored in a memory in the Ethernet switch only for IP packet flows that are redirected in response to the servers being unbalanced in their workloads.

3. The method of claim 1 , wherein rules for directing and redirecting IP packet flows are stored in a memory in the Ethernet switch.

4. An Ethernet switch coupled to a load balancing control engine, wherein a load balancing logic within the load balancing control engine is logically isolated from the Ethernet switch, the Ethernet switch comprising: a port for receiving an Internet Protocol (IP) packet flow; a memory for storing instructions for routing IP packet flows to servers from multiple server groups, wherein the multiple server groups comprise a firewall server group, an intrusion detection system (IDS) server group, and an anti-virus application server group; redirecting logic for redirecting the IP packet flow to a specific sequence of servers, wherein each server in the specific sequence of servers comes from a different server group from the multiple server groups, and wherein the IP packet flow is redirected to sequentially pass through a selected server from each of the firewall server group, the IDS server group, and the anti-virus application server group; and IP packet flow directing logic for, in response to the load balancing control engine determining that the servers are balanced, routing the IP packet flow to the servers without receiving any direct feedback from the servers regarding their workloads, and in response to the load balancing control engine determining that the servers are unbalanced, re-routing the IP packet flow to a server that is relatively less busy than other servers.

5. The Ethernet switch of claim 4 , wherein a record of where the IP packet flow is directed is stored only for IP packet flows that are redirected in response to the servers being unbalanced in their workloads.

6. The Ethernet switch of claim 4 , wherein rules for directing and redirecting IP packet flows are stored in the memory in the Ethernet switch.

7. A computer program product for routing Internet Protocol (IP) packet flows, the computer program product comprising: a computer readable storage media; first program instructions to logically couple an Ethernet switch to a load balancing control engine, wherein a load balancing logic within the load balancing control engine is hidden from the Ethernet switch; second program instructions to receive an IP packet flow by the Ethernet switch, wherein the Ethernet switch routes IP packet flows to servers from multiple server groups, wherein the multiple server groups comprise a firewall server group, an intrusion detection system (IDS) server group, and an anti-virus application server group; third program instructions to redirect the IP packet flow to a specific sequence of servers, wherein each server in the specific sequence of servers comes from a different server group from the multiple server groups, and wherein the IP packet flow is redirected to sequentially pass through a selected server from each of the firewall server group, the IDS server group, and the anti-virus application server group; fourth program instructions to determine if the servers are balanced in their workloads; fifth program instructions to, in response to the load balancing control engine determining that the servers are balanced, route the IP packet flow to the servers without the Ethernet switch directly receiving any feedback from the servers regarding their workloads; and sixth program instructions to, in response to the load balancing control engine determining that the servers are unbalanced, instruct the Ethernet switch to redirect the IP packet flow to a server that is relatively less busy than other servers; and wherein the first, second, third, fourth, fifth, and sixth program instructions are stored on the computer readable storage media.

8. The computer program product of claim 7 , wherein a record of where the IP packet flow is directed is stored only for IP packet flows that are redirected in response to the servers being unbalanced in their workloads.

9. The computer program product of claim 7 , wherein rules for directing and redirecting IP packet flows are stored in a memory in the Ethernet switch.