Dynamic load balancer

• US 7,739,398 B1
• Filed: 11/21/2000
• Issued: 06/15/2010
• Est. Priority Date: 11/21/2000
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Shabtay, Lior
• Primary Examiner(s): STRANGE, AARON N
• Application Number:
  US09/718,143
• Time in Patent Office: 3,493 Days
• Field of Search: 709/238, 709/239, 709/240, 709/229, 718/105
• US Class Current: 709/232
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering

Abstract

A method of accelerating the operation of a load balancer by an accelerator switch. The method includes receiving, by the accelerator switch, packets directed to the load balancer, determining, for at least some of the received packets, whether the packets match an entry of a list of packet groups, by comparing fewer than five parameters of the packets to respective fields of entries of the list, and forwarding, by the accelerator switch, at least some of the received packets, directly to their destination, responsive to the determining.

Claims

1. A load balancing accelerator, comprising:

an input interface which received packets directed to a load balancer, the load balancer and the load balancing accelerator being separate from one another;

a table which lists packet groups and their respective destination servers, the table having physical entries which can accommodate different field sets for storage of data entries;

a comparator which compares at least one of the packets directed to the load balancer to one or more of the data entries of the table;

a forwarding unit which forwards at least one of the packets for which a match was found by the comparator, directly to a server, responsive to the contents of the matching data entry; and

a controller which determines in which field set, from the plurality of different field sets, each of the data entries of the table is stored;

wherein the controller comprises a user interface through which a user may configure the field sets in which the data entries of the table are stored.

2. A load balancing accelerator, comprising;

an input interface which receives packets directed to a load balancer, the load balancer and the load balancing accelerator being separate from one another;

a table which lists packet groups and their respective destination servers, the table having physical entries which can accommodate different field sets for storage of data entries;

a comparator which compares at least one of the packets directed to the load balancer to one or more of the data entries of the table;

a forwarding unit which forwards at least one of the packets for which a match was found by the comparator, directly to a server, responsive to the contents of the matching data entry; and

a controller which determines in which field set, from the plurality of different field sets, each of the data entries of the table is stored;

wherein the controller automatically determines the field sets in which the data entries are stored; and

wherein the controller transmits one or more packets to the load balancer and examines the response of the load balancer to determine the field sets in which the data entries are stored.

3. A load balancing accelerator, comprising:

an input interface which receives packets directed to a load balancer, the load balancer and the load balancing accelerator being separate from one another;

a table which lists packet groups and their respective destination servers, the table having physical entries which can accommodate different field sets for storage of data entries;

a comparator which compares at least one of the packets directed to the load balancer to one or more of the data entries of the table;

a forwarding unit which forwards at least one of the packets for which a match was found by the comparator, directly to a server, responsive to the contents of the matching data entry; and

a controller which determines in which field set, from the plurality of different field sets, each of the data entries of the table is stored;

wherein the controller determines the field sets in which the data entries of the table are stored, such that at least during some periods of operation of the accelerator, the table includes at least two data entries stored in different field sets.