Method and architecture for logical aggregation of multiple servers

• US 7,299,301 B1
• Filed: 09/08/2003
• Issued: 11/20/2007
• Est. Priority Date: 02/28/2000
• Status: Expired due to Term

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Senthilnathan, Janakiraman, Verma, Rohit
• Primary Examiner(s): VU, THONG H
• Application Number:
  US10/657,778
• Time in Patent Office: 1,534 Days
• Field of Search: 709/200, 709/223, 709/224, 709/238, 709/227, 709/245, 370/389
• US Class Current: 709/249
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/25 of the same type
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30

Abstract

A system and method are shown for multiple network devices to operate as a single logical entity for serving tunnel connections. A cluster master device is connected to a multiple network devices through a local area network (LAN). The cluster master device is also connected to a wide area network (WAN) and has a master address that is unique on the WAN. The cluster master device receives a tunnel connection set-up request (SCCRQ) from the WAN that is addressed to the master address. The cluster master device selects one of the multiple network devices and forwards the SCCRQ message over the LAN to the selected network device. The selected network device selects a tunnel identification number that is unique for the tunnel connection on the selected network device and places the tunnel identification number into a source tunnel identification field of a connection set-up reply (SCCRP). The selected network device also places its own global address on the WAN into a source address field of the SCCRP, a value from a source address field of the SCCRQ into a destination address field of the SCCRP, and a value from a source tunnel identification field of the SCCRQ into a destination tunnel identification field of the SCCRP. The selected network device then transmits the SCCRP message onto the WAN. Alternatively, the multiple network devices do not have global addresses on the WAN and the SCCRP is transmitted over the LAN to a network address translation (NAT) server that substitutes its own address into the source address field of the SCCRP and retransmits the SCCRP onto the WAN. The NAT creates a table from the information in the SCCRP that it uses to translate and route subsequent packets between the selected network device and the device that requested the tunnel connection.

Claims

1. A tunnel endpoint device comprising:

a network interface connected to a local area network having a cluster of tunnel endpoint devices, the tunnel endpoint device being one of the cluster, the network interface configured to receive a Start-Control-Connection-Request (SCCRQ) message via the local area network to initiate establishment of a tunnel connection, wherein the SCCRQ includes a destination address field modified to be set to a local address of the tunnel endpoint device and a tunnel ID value assigned by a tunnel initiator to the tunnel connection being set-up;

means for forming a Start-Control-Connection-Reply (SCCRP) message having an address of the tunnel initiator, the tunnel ID value assigned to the tunnel connection by the tunnel initiator, and a tunnel ID value assigned to the tunnel connection by the tunnel endpoint device; and

means for transmitting the SCCRP message to a network address translation server via the network interface.

2. The tunnel endpoint device of claim 1, further comprising means for receiving a Start-Control-Connection-Connected (SCCN) message to establish a tunnel connection between the tunnel initiator and the tunnel endpoint device.

3. The tunnel endpoint device of claim 1, further comprising means for forming load status messages that indicate a current traffic load of the tunnel endpoint device.

4. A cluster master device comprising:

a first interface coupled to a first network having a plurality of network devices; and

a second interface for communicating with a second network,

wherein the cluster master device has a master global address that is unique on the second network, and

wherein the cluster master device is configured to receive from the second network tunnel connection request messages having the master global address in a destination address field and, for each tunnel connection request message received;

(i) select one of the plurality of network devices;

(ii) insert a local address for the selected network device into the destination address field of the received tunnel connection request message; and

(iii) transmit the received tunnel connection request message as modified over the first network interface onto the first network.

5. The cluster master device of claim 4, wherein the cluster master device selects one of the plurality of network devices based on a traffic load of each network device.

6. The cluster master device of claim 4, wherein the cluster master device receives load status messages from each network device and assigns the received tunnel connection request message to the network device that currently has the lowest traffic load as indicated by the load status messages.

7. The cluster master device of claim 4, wherein the tunnel connections are Layer 2 Tunneling Protocol (L2TP) connections.

8. The cluster master device of claim 4, wherein the first network is a local area network (LAN) and the second network is an Internet protocol (IP) network.

9. The cluster master device of claim 4, wherein the tunnel connection request messages include a source address field set to an IP address of a tunnel initiator, and a source tunnel ID field set to a tunnel ID value assigned to the tunnel connection by the tunnel initiator.

10. The cluster master device of claim 4, wherein the cluster master device keeps track of network devices that are out of service or temporarily inactive.

11. A method for terminating tunnel connections comprising:

receiving a tunnel connection request message;

receiving a load status message from each tunnel endpoint device of a plurality of tunnel endpoint devices on a network;

based on the load status messages, selecting a tunnel endpoint device to receive the tunnel connection request message; and

assigning the tunnel connection request message to the selected tunnel endpoint device.

12. The method of claim 11, wherein selecting the tunnel endpoint device to receive the tunnel connection request message comprises:

based on the load status messages, determining which tunnel endpoint device has the lowest load; and

selecting the tunnel endpoint device that has the lowest load.

13. The method of claim 11, wherein assigning the tunnel connection request message to the selected tunnel endpoint device comprises:

inserting a local address for the selected tunnel endpoint device into a destination address field of the tunnel connection request message; and

transmitting the tunnel connection request message as modified onto the network.

14. A method for terminating tunnel connections comprising:

receiving tunnel connection request messages having a master global address in a destination address field and, for each tunnel connection request message received;

selecting one of a plurality of network devices connected to a network;

inserting a local address for the selected network device into the destination address field of the received tunnel connection request message; and

transmitting the received tunnel connection request message as modified onto the network.

15. The method of claim 14, further comprising transmitting a tunnel set-up reply message over the network, wherein the tunnel set-up reply message includes a source address field having the address of the selected network device.

16. The method of claim 15, wherein transmitting the tunnel set-up reply message over the network comprises:

transmitting the tunnel set-up reply to a network address translation (NAT) server;

replacing the address of the selected network device in the source address field of the tunnel set-up reply message with a global address for the NAT server;

storing a table entry accessible to the NAT server that relates the global address to the address of the selected network device; and

transmitting the tunnel set-up reply message onto the network.

17. The method of claim 14, wherein selecting one of the plurality of network devices connected to the network comprises selecting one of the plurality of network devices based upon a traffic load on each of the network devices.

18. The method of claim 14, further comprising receiving load status messages from each of the plurality of network devices.

19. The method of claim 18, wherein selecting one of the plurality of network devices connected to the network comprises selecting one of the plurality of network devices based upon which network device currently has the lowest load as indicated by the load status messages.

20. The method of claim 14, wherein the tunnel connections are Layer 2 Tunneling Protocol (L2TP) connections.