US5949753A - Redundant internet protocol gateways using local area network emulation - Google Patents

Redundant internet protocol gateways using local area network emulation Download PDF

Info

Publication number
US5949753A
US5949753A US08/826,864 US82686497A US5949753A US 5949753 A US5949753 A US 5949753A US 82686497 A US82686497 A US 82686497A US 5949753 A US5949753 A US 5949753A
Authority
US
United States
Prior art keywords
default gateway
primary
backup
mac address
address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US08/826,864
Inventor
Cedell Adam Alexander, Jr.
John Lloyd
Matthew Blaze Squire
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US08/826,864 priority Critical patent/US5949753A/en
Assigned to IMB CORPORATION reassignment IMB CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LLOYD, J., SQUIRE, M. B., ALEXANDER, C. A., JR.
Priority to KR1019980003471A priority patent/KR100293119B1/en
Priority to JP9288498A priority patent/JP2908785B2/en
Application granted granted Critical
Publication of US5949753A publication Critical patent/US5949753A/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/04Selecting arrangements for multiplex systems for time-division multiplexing
    • H04Q11/0428Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
    • H04Q11/0478Provisions for broadband connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/54Store-and-forward switching systems 
    • H04L12/56Packet switching systems
    • H04L12/5601Transfer mode dependent, e.g. ATM
    • H04L2012/5614User Network Interface
    • H04L2012/5617Virtual LANs; Emulation of LANs
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/54Store-and-forward switching systems 
    • H04L12/56Packet switching systems
    • H04L12/5601Transfer mode dependent, e.g. ATM
    • H04L2012/5625Operations, administration and maintenance [OAM]
    • H04L2012/5627Fault tolerance and recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/54Store-and-forward switching systems 
    • H04L12/56Packet switching systems
    • H04L12/5601Transfer mode dependent, e.g. ATM
    • H04L2012/5638Services, e.g. multimedia, GOS, QOS
    • H04L2012/5665Interaction of ATM with other protocols
    • H04L2012/5667IP over ATM

Definitions

  • the present invention relates generally to transmitting data over emulated local area networks (ELANs) using internet protocol (IP), where the ELANs are implemented on an asynchronous transfer mode (ATM) network. More specifically, the present invention relates to creating redundant default gateways for the ELANs.
  • ELANs emulated local area networks
  • IP internet protocol
  • ATM asynchronous transfer mode
  • end stations attached to a router via LAN emulation can either run a routing protocol to determine the next hop for packets destined for subnets not directly connected to the end station, or the system administrator can specify the next hop by configuring a default-gateway.
  • the system administrator can configure a default gateway on the end station by specifying the IP address of a router interface on the ELAN. If the system administrator has configured a default gateway and the default gateway's interface is down, the end station will not be able to forward packets out of its own subnet.
  • a backup default gateway which would automatically start passing packets to other subnets in the event the primary default gateway failed.
  • the switch from the primary default gateway to the backup default gateway should be transparent to end stations and should occur automatically in the event the primary default gateway fails.
  • the router interfaces associated with both the primary and backup default gateways be active simultaneously. This would allow routing protocols such as OSPF to learn the connectivity of the backup default gateway while the primary default gateway is still active.
  • the backup default gateway automatically become active in the event the primary default gateway fails. This switch from the primary default gateway to the backup default gateway should be transparent to end stations.
  • the primary and backup default gateways prefferably be active at the same time so that routing protocols can learn the connectivity of the default gateways.
  • An ELAN having redundant default gateways is attached to an asynchronous transfer mode (ATM) communications network.
  • the ELAN's redundant default gateways are comprised of a first and second routers.
  • the first router is associated with a primary default gateway and the second router is associated with a backup default gateway.
  • Both the primary and backup default gateways are connected to the ELAN and both the primary and backup default gateways are configured with a default gateway IP address and associated MAC address.
  • the primary default gateway registers the default gateway MAC address, thereby becoming the active default gateway.
  • the backup default gateway continually attempts to register the default gateway MAC address. When the primary default gateway fails, the backup default gateway will be able to successfully register the default gateway MAC address and take over the responsibilities of the primary default gateway and become the active default gateway.
  • FIG. 1 illustrates the physical connections of an asynchronous transfer mode network having an emulated local area network
  • FIG. 2 depicts the logical connections of the network shown in FIG. 1;
  • FIG. 3 illustrates a network according to the present invention
  • FIG. 4 is a flowchart which depicts the method whereby the backup default gateway becomes active when the primary default gateway fails.
  • FIG. 1 illustrates a prior art asynchronous transfer mode (ATM) network having an emulated local area network (ELAN). Attached to ATM switch 102 are: router 114, ATM host 104, ATM host 110, and LAN switch 112.
  • ATM host 104 is an ATM device which has been configured to reside on ELAN -- A.
  • ATM host 110 is another ATM device which has been configured to reside on ELAN -- B.
  • LAN switch 112 contains an ATM interface and proxy LAN emulation clients (LECs) 116 and 117.
  • Proxy LECs 116 and 117 are associated with ELAN -- A and ELAN -- B, respectively, and bridge communications from legacy hosts 106 and 108 to their respective ELANs.
  • Legacy hosts 106 and 108 are traditional LAN devices which communicate with ATM switch 102 through proxy LECs 116 and 117.
  • Router 114 performs many services for ATM switch 102. One of the services provided by router 114 is routing traffic from ELAN -- A to ELAN -- B and vice versa.
  • FIG. 2 illustrates the logical connections of the network shown in FIG. 1. Attached to ELAN -- A are ATM host 104 and legacy host 106. Likewise, attached to ELAN -- B are ATM host 110 and legacy host 108. Routing traffic between ELAN -- A and ELAN -- B is router 114.
  • FIG. 3 illustrates the logical connections of a network according to the present invention.
  • LECs 308 and 306 are connected to ELAN 310.
  • LEC 308 provides an interface for the primary default gateway
  • LEC 306 provides an interface for the backup default gateway.
  • Also attached to ELAN 310 are end station 302 and router 304.
  • Router 304's neighboring routers are routers 312 and 314 whose IP addresses are IP1 and IP2, respectively.
  • the system administrator has configured end station 302 to use a default gateway having an IP address of IP3.
  • LEC 308 has been assigned MAC address M1 and corresponding IP address IP1.
  • LEC 306 has been configured with MAC address M2 and corresponding address IP2.
  • both LECs 308 and 306 have been configured with MAC address M3 and corresponding IP address IP3.
  • IP addresses IP1 and IP2 and MAC addresses M1 and M2 are unique, while IP address IP3 and MAC address M3 are shared by LECs 308 and 306.
  • LECs 308 and 306 only process packets addressed to M3/IP3 when their associated default gateway is active. Whether the primary or backup default gateway is active depends on whether the corresponding LEC has successfully registered its M3 MAC address with LAN emulation server (LES) 316. Only one default gateway will be active at a time because LES 316 does not allow the registration of duplicate MAC addresses.
  • LES LAN emulation server
  • LECs in routers 312 and 314 When the LECs in routers 312 and 314 become active, they join ELAN 310 and register MAC addresses M1 and M2 with LES 316. LECs 308 and 306 also both attempt to register MAC address M3 with LES 316. Only LEC 308 or only LEC 306 will successfully register MAC address M3 since LES 316 does not allow registration of duplicate MAC addresses. The LEC which registers MAC address M3 becomes the active default gateway, while the LEC which fails to register MAC address M3 will periodically retry the registration of MAC address M3.
  • LEC 308 registers MAC address M3 and the primary default gateway becomes active
  • LEC 306 will periodically try to reregister MAC address M3.
  • the backup default gateway can become the active default gateway when the primary default gateway fails. This type of operation is possible because when the active default gateway fails, LES 316 will deregister MAC address M3, thereby allowing another LEC to register this address.
  • LEC 306 If LEC 306 registers MAC address M3 before LEC 308, LEC 308 will also periodically try to reregister MAC address M3. In addition, LEC 308 will send LEC 306 a message instructing LEC 306 to deregister MAC address M3, thereby giving LEC 308 a chance to register MAC address M3 and to allow the primary default gateway to become active. This message is described in more detail below.
  • the period of time in which LEC 308 waits before trying to reregister MAC address M3 is shorter than the corresponding period of time for LEC 306. This guarantees that once LEC 308 instructs LEC 306 to deregister MAC address M3, LEC 308 will have a chance to reregister this MAC address before LEC 306 does.
  • LEC 306 retries to register MAC address M3 every 30 seconds, while LEC 308 retries every 5 seconds.
  • the interface providing the active default gateway will now respond to address resolution protocol (ARP) requests and other packets addressed to IP address IP3.
  • End stations with a manually configured default gateway address such as end station 302, will use IP address IP3 to send packets to other subnets. These end stations will send ARP requests for the MAC address corresponding to IP address IP3.
  • the interface providing the active default gateway will respond to these requests by returning MAC address M3.
  • the end stations will then use MAC address M3 when transmitting packets destined for other subnets.
  • Routers 312 and 314 will use the MAC/IP addresses M1/IP1 and M2/IP2, respectively, for all purposes except receiving packets intended for the active default gateway.
  • OSPF running on router 304 connected to ELAN 310 will use IP1 and IP2 to communicate with routers 312 and 314.
  • the primary default gateway will send a signal to the backup default gateway when the primary default gateway wishes to become the active default gateway.
  • the backup default gateway could be active instead of a primary default gateway because it registered its M3 address with LES 316 before the primary default gateway did, or because the primary default gateway has failed.
  • LEC 308 will try to register MAC address M3. If LEC 308 cannot register MAC address M3, it knows that LEC 306 has registered that address. LEC 308 will then send a message to LEC 306 using a private protocol. These messages are similar to the LANE LE -- FLUSH messages.
  • the differences between the messages sent by LEC 308 and the LANE LE -- FLUSH Request message is that the messages sent by LEC 308 contain the MAC address of the default gateway in both the source LAN destination and target LAN destination fields; while the LANE LE -- FLUSH Request messages contain zeros in the source LAN destination field.
  • LEC 306 receives the message from LEC 308, LEC 306 deregisters MAC address M3 from LES 316. After the MAC address M3 is deregistered by the backup default gateway, the primary default gateway will register MAC address M3. Now, when the backup default gateway tries to register MAC address M3, it will be unsuccessful because the primary default gateway has registered this address. However, the backup default gateway will continue to try to register MAC address M3 every 30 seconds. Continually trying to register MAC address M3 allows the backup default gateway to become the active default gateway within 30 seconds if the primary default gateway fails.
  • FIG. 4 is a flowchart which illustrates how the backup default gateway becomes active when the primary default gateway fails.
  • the LES removes the primary's registration of the default gateway MAC address (404).
  • the backup default gateway registers the default gateway MAC address (406).
  • the backup default gateway periodically tries to register the default gateway MAC address, as it has no other way of knowing when the primary default gateway fails.
  • the backup default gateway attempts to register the default gateway MAC address every 30 seconds.
  • the backup default gateway becomes active once it registers the default gateway MAC address (408).
  • the backup default gateway has now assumed the responsibilities of the default gateway.
  • the primary default gateway may eventually come back on-line (410). After coming back on-line, the primary default gateway will try to register the default gateway MAC address with the LES (412). The primary's attempt to register the default gateway MAC address will be unsuccessful, however, because the backup default gateway has already registered this address. In response to this unsuccessful attempt to register the default gateway MAC address, the primary default gateway sends a message to the backup default gateway. This message informs the backup default gateway that the primary default gateway wishes to become active (414). Upon receiving this message, the backup default gateway deregisters the default gateway MAC address with the LES (416). With the backup default gateway deregistered, the primary default gateway will be able to register the default MAC gateway address with the LES upon its next attempt (418).
  • the primary default gateway then becomes the active default gateway (420). After the primary default gateway becomes active, the backup default gateway will still periodically try to register the default gateway MAC address (422). The backup default gateway continues to retry this registration process so that when the primary default gateway fails, the backup default gateway will become active in a timely manner.

Abstract

An ELAN having redundant default gateways is attached to an asynchronous transfer mode (ATM) communications network. The ELAN's redundant default gateways are comprised of a first and second routers. The first router is associated with a primary default gateway and the second router is associated with a backup default gateway. Both the primary and backup default gateways are connected to the ELAN and both the primary and backup default gateways are configured with a default gateway IP address and associated MAC address. Initially, the primary default gateway registers the default gateway MAC address, thereby becoming the active default gateway. While the primary default gateway is active, the backup default gateway continually attempts to register the default gateway MAC address. When the primary default gateway fails, the backup default gateway will be able to successfully register the default gateway MAC address and take over the responsibilities of the primary default gateway and become the active default gateway.

Description

BACKGROUND OF THE INVENTION
1. Technical Field
The present invention relates generally to transmitting data over emulated local area networks (ELANs) using internet protocol (IP), where the ELANs are implemented on an asynchronous transfer mode (ATM) network. More specifically, the present invention relates to creating redundant default gateways for the ELANs.
2. Description of the Related Art
Due to the widespread acceptance of the current IP standard for communicating data, this standard has been adapted for use with ATM devices. Currently, one standard solution for sending IP traffic over an ATM interface is specified by the Internet Engineering Task Force (IETF) and is described by M. Laubach in a document entitled "Classical IP and ARP over ATM," RFC 1577, Hewlett Packard Laboratories, January 1994. Also, due to the large installed base of traditional local area network (LAN) products, standards have been created which allow existing LAN applications to communicate data over ATM networks. See ATM Forum "LAN Emulation over ATM: Version 1.0 Specification," AF-LANE-0021.000, January 1995.
A problem existing with today's ELANs which use IP is the lack of flexible backup gateways. In current systems, end stations attached to a router via LAN emulation (LANE) can either run a routing protocol to determine the next hop for packets destined for subnets not directly connected to the end station, or the system administrator can specify the next hop by configuring a default-gateway. The system administrator can configure a default gateway on the end station by specifying the IP address of a router interface on the ELAN. If the system administrator has configured a default gateway and the default gateway's interface is down, the end station will not be able to forward packets out of its own subnet.
Therefore, it would be desirable to have a backup default gateway which would automatically start passing packets to other subnets in the event the primary default gateway failed. The switch from the primary default gateway to the backup default gateway should be transparent to end stations and should occur automatically in the event the primary default gateway fails. Finally, it would be desirable to have the router interfaces associated with both the primary and backup default gateways be active simultaneously. This would allow routing protocols such as OSPF to learn the connectivity of the backup default gateway while the primary default gateway is still active.
SUMMARY OF THE INVENTION
Therefore, it is one objective of the present invention to provide flexible backup default gateways for end stations attached to emulated local area networks.
It is yet another objective of the present invention that the backup default gateway automatically become active in the event the primary default gateway fails. This switch from the primary default gateway to the backup default gateway should be transparent to end stations.
It is another objective of the present invention for the primary and backup default gateways to be active at the same time so that routing protocols can learn the connectivity of the default gateways.
The foregoing objectives are achieved as follows. An ELAN having redundant default gateways is attached to an asynchronous transfer mode (ATM) communications network. The ELAN's redundant default gateways are comprised of a first and second routers. The first router is associated with a primary default gateway and the second router is associated with a backup default gateway. Both the primary and backup default gateways are connected to the ELAN and both the primary and backup default gateways are configured with a default gateway IP address and associated MAC address. Initially, the primary default gateway registers the default gateway MAC address, thereby becoming the active default gateway. While the primary default gateway is active, the backup default gateway continually attempts to register the default gateway MAC address. When the primary default gateway fails, the backup default gateway will be able to successfully register the default gateway MAC address and take over the responsibilities of the primary default gateway and become the active default gateway.
BRIEF DESCRIPTION OF THE DRAWINGS
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
FIG. 1 illustrates the physical connections of an asynchronous transfer mode network having an emulated local area network;
FIG. 2 depicts the logical connections of the network shown in FIG. 1;
FIG. 3 illustrates a network according to the present invention; and
FIG. 4 is a flowchart which depicts the method whereby the backup default gateway becomes active when the primary default gateway fails.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
FIG. 1 illustrates a prior art asynchronous transfer mode (ATM) network having an emulated local area network (ELAN). Attached to ATM switch 102 are: router 114, ATM host 104, ATM host 110, and LAN switch 112. ATM host 104 is an ATM device which has been configured to reside on ELAN-- A. ATM host 110 is another ATM device which has been configured to reside on ELAN-- B. LAN switch 112 contains an ATM interface and proxy LAN emulation clients (LECs) 116 and 117. Proxy LECs 116 and 117 are associated with ELAN-- A and ELAN-- B, respectively, and bridge communications from legacy hosts 106 and 108 to their respective ELANs. Legacy hosts 106 and 108 are traditional LAN devices which communicate with ATM switch 102 through proxy LECs 116 and 117.
Router 114 performs many services for ATM switch 102. One of the services provided by router 114 is routing traffic from ELAN-- A to ELAN-- B and vice versa.
FIG. 2 illustrates the logical connections of the network shown in FIG. 1. Attached to ELAN-- A are ATM host 104 and legacy host 106. Likewise, attached to ELAN-- B are ATM host 110 and legacy host 108. Routing traffic between ELAN-- A and ELAN-- B is router 114.
FIG. 3 illustrates the logical connections of a network according to the present invention. In network 300, LECs 308 and 306 are connected to ELAN 310. LEC 308 provides an interface for the primary default gateway, while LEC 306 provides an interface for the backup default gateway. Also attached to ELAN 310 are end station 302 and router 304. Router 304's neighboring routers are routers 312 and 314 whose IP addresses are IP1 and IP2, respectively. In network 300, the system administrator has configured end station 302 to use a default gateway having an IP address of IP3.
LEC 308 has been assigned MAC address M1 and corresponding IP address IP1. LEC 306 has been configured with MAC address M2 and corresponding address IP2. Also, both LECs 308 and 306 have been configured with MAC address M3 and corresponding IP address IP3. IP addresses IP1 and IP2 and MAC addresses M1 and M2 are unique, while IP address IP3 and MAC address M3 are shared by LECs 308 and 306. LECs 308 and 306 only process packets addressed to M3/IP3 when their associated default gateway is active. Whether the primary or backup default gateway is active depends on whether the corresponding LEC has successfully registered its M3 MAC address with LAN emulation server (LES) 316. Only one default gateway will be active at a time because LES 316 does not allow the registration of duplicate MAC addresses.
When the LECs in routers 312 and 314 become active, they join ELAN 310 and register MAC addresses M1 and M2 with LES 316. LECs 308 and 306 also both attempt to register MAC address M3 with LES 316. Only LEC 308 or only LEC 306 will successfully register MAC address M3 since LES 316 does not allow registration of duplicate MAC addresses. The LEC which registers MAC address M3 becomes the active default gateway, while the LEC which fails to register MAC address M3 will periodically retry the registration of MAC address M3.
If LEC 308 registers MAC address M3 and the primary default gateway becomes active, LEC 306 will periodically try to reregister MAC address M3. By continually retrying to register MAC address M3, the backup default gateway can become the active default gateway when the primary default gateway fails. This type of operation is possible because when the active default gateway fails, LES 316 will deregister MAC address M3, thereby allowing another LEC to register this address.
If LEC 306 registers MAC address M3 before LEC 308, LEC 308 will also periodically try to reregister MAC address M3. In addition, LEC 308 will send LEC 306 a message instructing LEC 306 to deregister MAC address M3, thereby giving LEC 308 a chance to register MAC address M3 and to allow the primary default gateway to become active. This message is described in more detail below. The period of time in which LEC 308 waits before trying to reregister MAC address M3 is shorter than the corresponding period of time for LEC 306. This guarantees that once LEC 308 instructs LEC 306 to deregister MAC address M3, LEC 308 will have a chance to reregister this MAC address before LEC 306 does. In the preferred embodiment of the present invention, LEC 306 retries to register MAC address M3 every 30 seconds, while LEC 308 retries every 5 seconds.
The interface providing the active default gateway will now respond to address resolution protocol (ARP) requests and other packets addressed to IP address IP3. End stations with a manually configured default gateway address, such as end station 302, will use IP address IP3 to send packets to other subnets. These end stations will send ARP requests for the MAC address corresponding to IP address IP3. The interface providing the active default gateway will respond to these requests by returning MAC address M3. The end stations will then use MAC address M3 when transmitting packets destined for other subnets. Routers 312 and 314 will use the MAC/IP addresses M1/IP1 and M2/IP2, respectively, for all purposes except receiving packets intended for the active default gateway. For example, OSPF running on router 304 connected to ELAN 310 will use IP1 and IP2 to communicate with routers 312 and 314.
The primary default gateway will send a signal to the backup default gateway when the primary default gateway wishes to become the active default gateway. The backup default gateway could be active instead of a primary default gateway because it registered its M3 address with LES 316 before the primary default gateway did, or because the primary default gateway has failed. Initially, LEC 308 will try to register MAC address M3. If LEC 308 cannot register MAC address M3, it knows that LEC 306 has registered that address. LEC 308 will then send a message to LEC 306 using a private protocol. These messages are similar to the LANE LE-- FLUSH messages. The differences between the messages sent by LEC 308 and the LANE LE-- FLUSH Request message is that the messages sent by LEC 308 contain the MAC address of the default gateway in both the source LAN destination and target LAN destination fields; while the LANE LE-- FLUSH Request messages contain zeros in the source LAN destination field. When LEC 306 receives the message from LEC 308, LEC 306 deregisters MAC address M3 from LES 316. After the MAC address M3 is deregistered by the backup default gateway, the primary default gateway will register MAC address M3. Now, when the backup default gateway tries to register MAC address M3, it will be unsuccessful because the primary default gateway has registered this address. However, the backup default gateway will continue to try to register MAC address M3 every 30 seconds. Continually trying to register MAC address M3 allows the backup default gateway to become the active default gateway within 30 seconds if the primary default gateway fails.
FIG. 4 is a flowchart which illustrates how the backup default gateway becomes active when the primary default gateway fails. After the primary default gateway fails (402), the LES removes the primary's registration of the default gateway MAC address (404). Sometime later, the backup default gateway registers the default gateway MAC address (406). The backup default gateway periodically tries to register the default gateway MAC address, as it has no other way of knowing when the primary default gateway fails. In a preferred embodiment of the present invention, the backup default gateway attempts to register the default gateway MAC address every 30 seconds. The backup default gateway becomes active once it registers the default gateway MAC address (408). The backup default gateway has now assumed the responsibilities of the default gateway.
The primary default gateway may eventually come back on-line (410). After coming back on-line, the primary default gateway will try to register the default gateway MAC address with the LES (412). The primary's attempt to register the default gateway MAC address will be unsuccessful, however, because the backup default gateway has already registered this address. In response to this unsuccessful attempt to register the default gateway MAC address, the primary default gateway sends a message to the backup default gateway. This message informs the backup default gateway that the primary default gateway wishes to become active (414). Upon receiving this message, the backup default gateway deregisters the default gateway MAC address with the LES (416). With the backup default gateway deregistered, the primary default gateway will be able to register the default MAC gateway address with the LES upon its next attempt (418). The primary default gateway then becomes the active default gateway (420). After the primary default gateway becomes active, the backup default gateway will still periodically try to register the default gateway MAC address (422). The backup default gateway continues to retry this registration process so that when the primary default gateway fails, the backup default gateway will become active in a timely manner.
The examples shown above only describe ELANs with two backup default gateways attached. However, using the techniques described above, more than two backup default gateways can be attached to an ELAN in order to provide additional backup services.
While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.

Claims (21)

We claim:
1. An asynchronous transfer mode (ATM) communications network including an emulated local area network (ELAN) having redundant default gateways, comprising:
a first router and a second router, said first router being associated with a primary default gateway and said second router being associated with a backup default gateway, wherein said primary default gateway and said backup default gateway are connected to said ELAN and configured with a default gateway internet protocol (IP) address and a default gateway media access control (MAC) address;
said default gateways being operable in a first mode of operation, wherein
said primary default gateway registers said default gateway MAC address, thereby becoming an active default gateway;
said backup default gateway attempts to register said default gateway MAC address; and
said backup default gateway waits for a period of time and attempts to register said default gateway MAC address, said attempt by said backup default gateway to register said default gateway MAC address being unsuccessful while said primary default gateway is an active default gateway.
2. The communications network as defined in claim 1, said default gateways being operable in a second mode of operation, wherein:
said primary default gateway fails;
a LAN emulation server (LES) deregisters said default gateway MAC address; and
said backup default gateway registers said default gateway MAC address, such that said backup default gateway becomes said active default gateway.
3. The communications network as defined in claim 1, said default gateways being operable in a third mode of operation, wherein:
said primary default gateway unsuccessfully attempts to register said default gateway MAC address;
said primary default gateway sends said backup default gateway a message to deregister said default gateway MAC address; and
said primary default gateway registers said default gateway MAC address, thereby becoming said active default gateway.
4. The communications network as defined in claim 1, wherein said first router and said second router are each configured with an IP address and a MAC address in addition to said default gateway IP address and said default gateway MAC address.
5. The communications network as defined in claim 4, wherein said first and second routers use said additional IP and MAC addresses for all communications except for receiving packets intended for said active default gateway.
6. The communications network as defined in claim 1, further comprising:
an additional router, said additional router being associated with a backup default gateway.
7. The communications network as defined in claim 3, wherein said third mode of operation further includes:
said primary default gateway waiting for a period of time before attempting to reregister said default gateway MAC address after sending said backup default gateway a message to deregister said default gateway MAC address, wherein the period of time which said primary default gateway waits before attempting to reregister said default gateway MAC address when said primary default gateway is not active is less than the period of time said backup default gateway waits before attempting to reregister said default gateway MAC address when said backup default gateway is not active.
8. The communications network as defined in claim 7, wherein said primary default gateway waits for 5 seconds before attempting to reregister said default gateway MAC address when not the active default gateway, and said backup default gateway waits for 30 seconds before attempting to reregister said default gateway MAC address when not the active default gateway.
9. A method of communicating using an asynchronous transfer mode (ATM) communications network including an emulated local area network (ELAN), having redundant default gateways, said method comprising the steps of:
providing a first router and a second router, said first router being associated with a primary default gateway and said second router being associated with a backup default gateway, wherein said primary default gateway and said backup default gateway are connected to said ELAN and configured with a default gateway internet protocol (IP) address and a default gateway media access control (MAC) address;
registering said default gateway MAC address, using the primary default gateway, thereby making the primary default gateway an active default gateway;
attempting to register said default gateway MAC address using said backup default gateway;
waiting for a period of time; and
attempting to register said default gateway MAC address using said backup default gateway, wherein said attempt by said backup default gateway to register said default gateway MAC address is unsuccessful while said primary default gateway is an active default gateway.
10. The method as defined in claim 9, further comprising the steps of:
deregistering said default gateway MAC address in response to a failure of said primary default gateway;
registering said default gateway MAC address using said backup default gateway upon the next attempt by said backup default gateway to reregister the default gateway MAC address, such that said backup default gateway becomes said active default gateway.
11. The method as defined in claim 9, further comprising the steps of:
unsuccessfully attempting to register said default gateway MAC address using said primary default gateway;
sending a message from said primary default gateway to said backup default gateway to deregister said default gateway MAC address; and
registering said default gateway MAC address using said primary default gateway, such that said primary default gateway becomes said active default gateway.
12. The method as defined in claim 9, wherein said first router and said second router are each configured with an IP address and a MAC address in addition to said default gateway IP address and said default gateway MAC address.
13. The method as defined in claim 12, wherein said first and second routers use said additional IP and MAC addresses for all communications except for receiving packets intended for said active default gateway.
14. The method as defined in claim 9, further comprising the steps of:
providing an additional router, said additional router being associated with a backup default gateway.
15. The method as defined in claim 11, further comprising the steps of:
in response to said sending step, waiting for a period of time before attempting to reregister said default gateway MAC address using said primary default gateway, wherein the period of time which said primary default gateway waits before attempting to reregister said default gateway MAC address when said primary default gateway is not active is less than the period of time said backup default gateway waits before attempting to reregister said default gateway MAC address when said backup default gateway is not active.
16. The method as defined in claim 15, wherein said primary default gateway waits for 5 seconds before attempting to reregister said default gateway MAC address when not the active default gateway, and said backup default gateway waits for 30 seconds before attempting to reregister said default gateway MAC address when not the active default gateway.
17. An emulated local access network (ELAN) having redundant default gateways, said ELAN comprising:
an end station;
a first router;
a second router;
means for associating said first router with a primary default gateway;
means for associating said second router with a backup default gateway;
means for configuring said first router and said second router to include a unique address pair and a shared address pair, wherein each said address pair includes a network address and a media access control address;
means for registering said shared media access control address on behalf of said first router such that said primary default gateway becomes an active default gateway;
means for periodically attempting to register said shared media access control address on behalf of said second router such that said backup default gateway may become said active default gateway in response to a failure of said primary default gateway; and
means for configuring said end station to include said shared network address such that said end station may transmit data from said ELAN utilizing said active default gateway.
18. The ELAN as defined in claim 17, wherein said shared network address comprises a default gateway internet protocol address and said shared media access control address comprises a default gateway media access control address.
19. The ELAN as defined in claim 17, further comprising:
means for deregistering said shared media access control address such that said primary default gateway is no longer said active default gateway in response to a failure of said primary default gateway.
20. The ELAN as defined in claim 19, said means for registering said shared media access control address on behalf of said first router further comprising:
means for sending a message to said backup default gateway in response to a registration of said shared media access control address on behalf of said backup default gateway to deregister said shared media access control address; and
means for periodically attempting to reregister said shared media access control address on behalf of said first router such that said primary default gateway may become said active default gateway.
21. The ELAN as defined in claim 20, wherein the period of time which said primary default gateway waits before attempting to reregister said shared media access control address is less than the period of time said backup default gateway waits before attempting to register said shared media access control address.
US08/826,864 1997-04-11 1997-04-11 Redundant internet protocol gateways using local area network emulation Expired - Lifetime US5949753A (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US08/826,864 US5949753A (en) 1997-04-11 1997-04-11 Redundant internet protocol gateways using local area network emulation
KR1019980003471A KR100293119B1 (en) 1997-04-11 1998-02-06 Redundant internet protocol gateways using local area network emulation
JP9288498A JP2908785B2 (en) 1997-04-11 1998-04-06 Communication network and communication method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US08/826,864 US5949753A (en) 1997-04-11 1997-04-11 Redundant internet protocol gateways using local area network emulation

Publications (1)

Publication Number Publication Date
US5949753A true US5949753A (en) 1999-09-07

Family

ID=25247724

Family Applications (1)

Application Number Title Priority Date Filing Date
US08/826,864 Expired - Lifetime US5949753A (en) 1997-04-11 1997-04-11 Redundant internet protocol gateways using local area network emulation

Country Status (3)

Country Link
US (1) US5949753A (en)
JP (1) JP2908785B2 (en)
KR (1) KR100293119B1 (en)

Cited By (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6041063A (en) * 1997-09-16 2000-03-21 Olicom A/S High availability, scaleable bandwidth, multiport ATM-emulated LAN interface
US6141326A (en) * 1997-10-20 2000-10-31 Fujitsu Limited Exchange having function for detecting fault in internal unit
US6195329B1 (en) * 1997-03-28 2001-02-27 Nec Corporation Trouble releasing system and method for ATM logic IP subnetwork
US6226297B1 (en) * 1997-01-30 2001-05-01 International Business Machines Corporation Method and system for providing redundancy to asynchronous transfer mode emulated local-area networks
US6266335B1 (en) * 1997-12-19 2001-07-24 Cyberiq Systems Cross-platform server clustering using a network flow switch
US6324161B1 (en) * 1997-08-27 2001-11-27 Alcatel Usa Sourcing, L.P. Multiple network configuration with local and remote network redundancy by dual media redirect
EP1175065A2 (en) * 2000-07-21 2002-01-23 Hughes Electronics Corporation Method and system for improving network performance enhancing proxy architecture with gateway redundancy
US20030039007A1 (en) * 2001-08-15 2003-02-27 Nayna Networks, Inc. (A Delaware Corporation) Method and system for route control and redundancy for optical network switching applications
US6563830B1 (en) * 2000-03-28 2003-05-13 3Com Corporation Multicast registration of all multicast flows in an asynchronous transfer mode based emulated LAN
US20030118039A1 (en) * 2001-12-17 2003-06-26 Hidetaka Nishi Gateway
US6671253B1 (en) * 1999-09-21 2003-12-30 International Business Machines Corporation Method and system for providing peer redundancy to asynchronous transfer mode emulated local-area networks
US6721801B2 (en) * 2000-12-26 2004-04-13 Brooks Automation Increased network availability for computers using redundancy
US6751191B1 (en) * 1999-06-29 2004-06-15 Cisco Technology, Inc. Load sharing and redundancy scheme
US6772226B1 (en) 2000-08-15 2004-08-03 Avaya Technology Corp. VPN device clustering using a network flow switch and a different mac address for each VPN device in the cluster
US6779039B1 (en) 2000-03-31 2004-08-17 Avaya Technology Corp. System and method for routing message traffic using a cluster of routers sharing a single logical IP address distinct from unique IP addresses of the routers
WO2004082222A1 (en) * 2003-03-11 2004-09-23 Huawei Technologies Co., Ltd. Communication method having the function of partaking the network load
US6807149B1 (en) 2000-07-17 2004-10-19 International Business Machines Corporation Method and system for LEC resiliency with fast failover
US6826623B1 (en) * 2000-09-14 2004-11-30 International Business Machines Corporation Detecting a dead gateway for subsequent non-TCP transmission by sending a first TCP packet and deleting an ARP entry associated with the gateway
US20040264503A1 (en) * 2003-06-30 2004-12-30 Microsoft Corporation Method and system for providing a virtual protocol interlayer
US6839829B1 (en) 2000-01-18 2005-01-04 Cisco Technology, Inc. Routing protocol based redundancy design for shared-access networks
US20050021844A1 (en) * 2003-05-22 2005-01-27 Roberto Puon Network router that efficiently switches between a primary data path and a backup data path
KR100472775B1 (en) * 2000-11-29 2005-03-07 엘지전자 주식회사 Routing table search method for supporting multiple default route
US6880089B1 (en) 2000-03-31 2005-04-12 Avaya Technology Corp. Firewall clustering for multiple network servers
US6885667B1 (en) 2000-12-26 2005-04-26 Cisco Technology, Inc. Redirection to a virtual router
US20050149948A1 (en) * 2003-12-30 2005-07-07 Intel Corporation System and method for monitoring and managing connection manager activity
US20050177762A1 (en) * 2003-12-19 2005-08-11 Nokia Inc. Method and system for efficiently failing over interfaces in a network
US6934762B1 (en) 2000-04-27 2005-08-23 Redundant Networks, Inc. Method and apparatus for providing backup internet access
US7055173B1 (en) 1997-12-19 2006-05-30 Avaya Technology Corp. Firewall pooling in a network flowswitch
US7058007B1 (en) 2000-01-18 2006-06-06 Cisco Technology, Inc. Method for a cable modem to rapidly switch to a backup CMTS
US7068712B1 (en) 2000-01-18 2006-06-27 Cisco Technology, Inc. Cable network redundancy architecture
US20060140164A1 (en) * 2004-12-29 2006-06-29 Cisco Technology, Inc. Methods and apparatus for using DHCP for home address management of nodes attached to an edge device and for performing mobility and address management as a proxy home agent
US20060173988A1 (en) * 2005-02-02 2006-08-03 Tetsuya Yamashita Network, network terminal device, IP address management method using the same, and program therefor
US7174376B1 (en) 2002-06-28 2007-02-06 Cisco Technology, Inc. IP subnet sharing technique implemented without using bridging or routing protocols
US7227863B1 (en) * 2001-11-09 2007-06-05 Cisco Technology, Inc. Methods and apparatus for implementing home agent redundancy
CN100388680C (en) * 2004-12-03 2008-05-14 华为技术有限公司 Method for treating medium access conbrol address in main and spare conversion
US7403474B2 (en) 2004-01-27 2008-07-22 Hewlett-Packard Development Company, L.P. Redundant router set up
US7593346B2 (en) 2003-07-31 2009-09-22 Cisco Technology, Inc. Distributing and balancing traffic flow in a virtual gateway
CN101159606B (en) * 2007-11-09 2010-07-07 华为技术有限公司 Method and network appliance of settling address conflict
EP2247065A1 (en) * 2009-05-01 2010-11-03 Avaya Inc. Method to block split phone and gateway registration
US7881208B1 (en) 2001-06-18 2011-02-01 Cisco Technology, Inc. Gateway load balancing protocol
US20120182992A1 (en) * 2011-01-14 2012-07-19 International Business Machines Corporation Hypervisor routing between networks in a virtual networking environment

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100452158B1 (en) * 2002-05-29 2004-10-08 주식회사 이지브로네트웍스 Internet Access Device with MAC-Address- Translation Ethernet Switching Functionalities And Multi Tenant Premises Communications Management Server Interoperating with The Aforementioned IAD And a Method for Enhancing Subscriber Identification And Network Security And Service Quality for Multi-Tenant Premises Subscribers Where Internet Connectivity Is Provided on The Complex LAN, utilizing the Aforementioned
CN102487342B (en) * 2010-12-03 2014-07-09 阿里巴巴集团控股有限公司 Device and method for controlling virtual internet protocol address binding

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5394402A (en) * 1993-06-17 1995-02-28 Ascom Timeplex Trading Ag Hub for segmented virtual local area network with shared media access
US5450406A (en) * 1993-04-20 1995-09-12 Kabushiki Kaisha Toshiba ATM communication system with high speed connection-less service function
US5473599A (en) * 1994-04-22 1995-12-05 Cisco Systems, Incorporated Standby router protocol
US5485455A (en) * 1994-01-28 1996-01-16 Cabletron Systems, Inc. Network having secure fast packet switching and guaranteed quality of service
US5570084A (en) * 1994-06-28 1996-10-29 Metricom, Inc. Method of loose source routing over disparate network types in a packet communication network
US5600644A (en) * 1995-03-10 1997-02-04 At&T Method and apparatus for interconnecting LANs
US5732071A (en) * 1993-12-29 1998-03-24 Kabushiki Kaisha Toshiba ATM bridge device and ATM bridging scheme for realizing efficient ATM bridge interconnection
US5734824A (en) * 1993-02-10 1998-03-31 Bay Networks, Inc. Apparatus and method for discovering a topology for local area networks connected via transparent bridges
US5737525A (en) * 1992-05-12 1998-04-07 Compaq Computer Corporation Network packet switch using shared memory for repeating and bridging packets at media rate
US5777994A (en) * 1995-02-17 1998-07-07 Hitachi, Ltd. ATM switch and intermediate system

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5737525A (en) * 1992-05-12 1998-04-07 Compaq Computer Corporation Network packet switch using shared memory for repeating and bridging packets at media rate
US5734824A (en) * 1993-02-10 1998-03-31 Bay Networks, Inc. Apparatus and method for discovering a topology for local area networks connected via transparent bridges
US5450406A (en) * 1993-04-20 1995-09-12 Kabushiki Kaisha Toshiba ATM communication system with high speed connection-less service function
US5394402A (en) * 1993-06-17 1995-02-28 Ascom Timeplex Trading Ag Hub for segmented virtual local area network with shared media access
US5732071A (en) * 1993-12-29 1998-03-24 Kabushiki Kaisha Toshiba ATM bridge device and ATM bridging scheme for realizing efficient ATM bridge interconnection
US5485455A (en) * 1994-01-28 1996-01-16 Cabletron Systems, Inc. Network having secure fast packet switching and guaranteed quality of service
US5473599A (en) * 1994-04-22 1995-12-05 Cisco Systems, Incorporated Standby router protocol
US5570084A (en) * 1994-06-28 1996-10-29 Metricom, Inc. Method of loose source routing over disparate network types in a packet communication network
US5777994A (en) * 1995-02-17 1998-07-07 Hitachi, Ltd. ATM switch and intermediate system
US5600644A (en) * 1995-03-10 1997-02-04 At&T Method and apparatus for interconnecting LANs

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Addressing Source Routing in an ATM Emulated LAN, IBM Technical Disclosure Bulletin, vol. 37, No. 10, Oct. 1994. *
Link Services Architecture Reference Model, IBM Technical Disclosure Bulletin, vol. 34, No. 7B, Dec. 1991. *
Method for Improving Network Availability with Redundant Network Servers, IBM Technical Disclosure Bulletin, vol. 39, No. 8, Aug. 1996. *

Cited By (64)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6226297B1 (en) * 1997-01-30 2001-05-01 International Business Machines Corporation Method and system for providing redundancy to asynchronous transfer mode emulated local-area networks
US6195329B1 (en) * 1997-03-28 2001-02-27 Nec Corporation Trouble releasing system and method for ATM logic IP subnetwork
US6324161B1 (en) * 1997-08-27 2001-11-27 Alcatel Usa Sourcing, L.P. Multiple network configuration with local and remote network redundancy by dual media redirect
US6041063A (en) * 1997-09-16 2000-03-21 Olicom A/S High availability, scaleable bandwidth, multiport ATM-emulated LAN interface
US6141326A (en) * 1997-10-20 2000-10-31 Fujitsu Limited Exchange having function for detecting fault in internal unit
US6266335B1 (en) * 1997-12-19 2001-07-24 Cyberiq Systems Cross-platform server clustering using a network flow switch
US7055173B1 (en) 1997-12-19 2006-05-30 Avaya Technology Corp. Firewall pooling in a network flowswitch
US7006431B1 (en) 1999-06-29 2006-02-28 Cisco Technology, Inc. Load sharing and redundancy scheme
US9276834B2 (en) 1999-06-29 2016-03-01 Cisco Technology, Inc. Load sharing and redundancy scheme
US6751191B1 (en) * 1999-06-29 2004-06-15 Cisco Technology, Inc. Load sharing and redundancy scheme
US8077604B1 (en) 1999-06-29 2011-12-13 Cisco Technology, Inc. Load sharing and redundancy scheme
US6671253B1 (en) * 1999-09-21 2003-12-30 International Business Machines Corporation Method and system for providing peer redundancy to asynchronous transfer mode emulated local-area networks
USRE44661E1 (en) 2000-01-18 2013-12-24 Cisco Technology, Inc. Method for a cable modem to rapidly switch to a backup CMTS
US7966409B1 (en) 2000-01-18 2011-06-21 Cisco Technology, Inc. Routing protocol based redundancy design for shared-access networks
US7068712B1 (en) 2000-01-18 2006-06-27 Cisco Technology, Inc. Cable network redundancy architecture
US7058007B1 (en) 2000-01-18 2006-06-06 Cisco Technology, Inc. Method for a cable modem to rapidly switch to a backup CMTS
US6839829B1 (en) 2000-01-18 2005-01-04 Cisco Technology, Inc. Routing protocol based redundancy design for shared-access networks
US6563830B1 (en) * 2000-03-28 2003-05-13 3Com Corporation Multicast registration of all multicast flows in an asynchronous transfer mode based emulated LAN
US6880089B1 (en) 2000-03-31 2005-04-12 Avaya Technology Corp. Firewall clustering for multiple network servers
US6779039B1 (en) 2000-03-31 2004-08-17 Avaya Technology Corp. System and method for routing message traffic using a cluster of routers sharing a single logical IP address distinct from unique IP addresses of the routers
US20060053231A1 (en) * 2000-04-27 2006-03-09 Alan Lange Method and apparatus for providing backup internet access
US6934762B1 (en) 2000-04-27 2005-08-23 Redundant Networks, Inc. Method and apparatus for providing backup internet access
US6807149B1 (en) 2000-07-17 2004-10-19 International Business Machines Corporation Method and system for LEC resiliency with fast failover
EP1175065A3 (en) * 2000-07-21 2003-08-13 Hughes Electronics Corporation Method and system for improving network performance enhancing proxy architecture with gateway redundancy
US20020038373A1 (en) * 2000-07-21 2002-03-28 John Border Method and system for improving network performance enhancing proxy architecture with gateway redundancy
EP1175065A2 (en) * 2000-07-21 2002-01-23 Hughes Electronics Corporation Method and system for improving network performance enhancing proxy architecture with gateway redundancy
US6772226B1 (en) 2000-08-15 2004-08-03 Avaya Technology Corp. VPN device clustering using a network flow switch and a different mac address for each VPN device in the cluster
US6826623B1 (en) * 2000-09-14 2004-11-30 International Business Machines Corporation Detecting a dead gateway for subsequent non-TCP transmission by sending a first TCP packet and deleting an ARP entry associated with the gateway
KR100472775B1 (en) * 2000-11-29 2005-03-07 엘지전자 주식회사 Routing table search method for supporting multiple default route
US6721801B2 (en) * 2000-12-26 2004-04-13 Brooks Automation Increased network availability for computers using redundancy
US6885667B1 (en) 2000-12-26 2005-04-26 Cisco Technology, Inc. Redirection to a virtual router
US7136383B1 (en) 2000-12-26 2006-11-14 Cisco Technology, Inc. Redirection to a virtual router
US7881208B1 (en) 2001-06-18 2011-02-01 Cisco Technology, Inc. Gateway load balancing protocol
US20030039007A1 (en) * 2001-08-15 2003-02-27 Nayna Networks, Inc. (A Delaware Corporation) Method and system for route control and redundancy for optical network switching applications
US7227863B1 (en) * 2001-11-09 2007-06-05 Cisco Technology, Inc. Methods and apparatus for implementing home agent redundancy
US20030118039A1 (en) * 2001-12-17 2003-06-26 Hidetaka Nishi Gateway
US7174376B1 (en) 2002-06-28 2007-02-06 Cisco Technology, Inc. IP subnet sharing technique implemented without using bridging or routing protocols
US7895312B1 (en) 2002-06-28 2011-02-22 Cisco Technology, Inc. IP subnet sharing technique implemented without using bridging or routing protocols
CN100407671C (en) * 2003-03-11 2008-07-30 华为技术有限公司 Network communication method for carrying out load division
WO2004082222A1 (en) * 2003-03-11 2004-09-23 Huawei Technologies Co., Ltd. Communication method having the function of partaking the network load
US7861002B2 (en) 2003-05-22 2010-12-28 Adtran, Inc. Network router that efficiently switches between a primary data path and a backup data path
US20050021844A1 (en) * 2003-05-22 2005-01-27 Roberto Puon Network router that efficiently switches between a primary data path and a backup data path
US20070280249A1 (en) * 2003-06-30 2007-12-06 Microsoft Corporation Method and system for providing a virtual protocol interlayer
US20040264503A1 (en) * 2003-06-30 2004-12-30 Microsoft Corporation Method and system for providing a virtual protocol interlayer
US7593346B2 (en) 2003-07-31 2009-09-22 Cisco Technology, Inc. Distributing and balancing traffic flow in a virtual gateway
US7769862B2 (en) * 2003-12-19 2010-08-03 Check Point Software Technologies Inc. Method and system for efficiently failing over interfaces in a network
US20050177762A1 (en) * 2003-12-19 2005-08-11 Nokia Inc. Method and system for efficiently failing over interfaces in a network
US20050149948A1 (en) * 2003-12-30 2005-07-07 Intel Corporation System and method for monitoring and managing connection manager activity
US20080205264A1 (en) * 2004-01-27 2008-08-28 Rorie Heather N Redundant router set up
US7403474B2 (en) 2004-01-27 2008-07-22 Hewlett-Packard Development Company, L.P. Redundant router set up
US7760622B2 (en) 2004-01-27 2010-07-20 Hewlett-Packard Development Company, L.P. Redundant router set up
CN100388680C (en) * 2004-12-03 2008-05-14 华为技术有限公司 Method for treating medium access conbrol address in main and spare conversion
US8059661B2 (en) 2004-12-29 2011-11-15 Cisco Technology, Inc. Methods and apparatus for using DHCP for home address management of nodes attached to an edge device and for performing mobility and address management as a proxy home agent
US20060140164A1 (en) * 2004-12-29 2006-06-29 Cisco Technology, Inc. Methods and apparatus for using DHCP for home address management of nodes attached to an edge device and for performing mobility and address management as a proxy home agent
US7685284B2 (en) 2005-02-02 2010-03-23 Nec Corporation Network, network terminal device, IP address management method using the same, and program therefor
EP1689147A3 (en) * 2005-02-02 2009-04-29 NEC Infrontia Corporation Network, network terminal and program for IP address management
US20060173988A1 (en) * 2005-02-02 2006-08-03 Tetsuya Yamashita Network, network terminal device, IP address management method using the same, and program therefor
CN101159606B (en) * 2007-11-09 2010-07-07 华为技术有限公司 Method and network appliance of settling address conflict
US20100278039A1 (en) * 2009-05-01 2010-11-04 Avaya Inc. Method to block split phone and gateway registration
CN101877673A (en) * 2009-05-01 2010-11-03 阿瓦雅公司 Stop the method for separating phone and gateway registration
EP2247065A1 (en) * 2009-05-01 2010-11-03 Avaya Inc. Method to block split phone and gateway registration
US9438636B2 (en) * 2009-05-01 2016-09-06 Avaya Inc. Method to block split phone and gateway registration
US20120182992A1 (en) * 2011-01-14 2012-07-19 International Business Machines Corporation Hypervisor routing between networks in a virtual networking environment
US10142218B2 (en) * 2011-01-14 2018-11-27 International Business Machines Corporation Hypervisor routing between networks in a virtual networking environment

Also Published As

Publication number Publication date
JP2908785B2 (en) 1999-06-21
KR100293119B1 (en) 2001-07-12
JPH10303968A (en) 1998-11-13
KR19980079679A (en) 1998-11-25

Similar Documents

Publication Publication Date Title
US5949753A (en) Redundant internet protocol gateways using local area network emulation
US6104870A (en) Method and system for improving communications in data communications networks that provide network emulation
US5936936A (en) Redundancy mechanisms for classical internet protocol over asynchronous transfer mode networks
US5600644A (en) Method and apparatus for interconnecting LANs
US7222188B1 (en) Method and apparatus for forwarding traffic between locally attached networks using level 3 addressing information
US6061728A (en) Arrangement for controlling network proxy device traffic on a transparently-bridged local area network using a master proxy device
KR100899365B1 (en) Method and apparatus for providing mobility within a network
US5982773A (en) Lan connection method
US5581552A (en) Multimedia server
EP1410579B1 (en) Method for configuring a computer network
US7088689B2 (en) VLAN data switching method using ARP packet
WO2004045153A1 (en) Methods and apparatus for broadcast domain interworking
JP4007690B2 (en) End device and router
US6606321B1 (en) Method of establishing MPOA shortcut virtual channel connections
US6212191B1 (en) Method and system for providing security to asynchronous transfer mode emulated local-area networks
JPH1168789A (en) Layer 3 switching using server
EP0825747B1 (en) Address resolution system
JPH1127326A (en) Hierarchical lan switch network
Cisco Using HSRP for Fault-Tolerant IP Routing
Cisco Using HSRP for Fault-Tolerant IP Routing
Cisco Using HSRP For Fault-Tolerant Routing
Cisco LAN Emulation and MPOA
Cisco AppleTalk Commands
JPH1032597A (en) Inter-lan connection device
Taylor LAN emulation over ATM

Legal Events

Date Code Title Description
AS Assignment

Owner name: IMB CORPORATION, NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALEXANDER, C. A., JR.;LLOYD, J.;SQUIRE, M. B.;REEL/FRAME:008786/0463;SIGNING DATES FROM 19970411 TO 19970414

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

REMI Maintenance fee reminder mailed
FPAY Fee payment

Year of fee payment: 12

SULP Surcharge for late payment

Year of fee payment: 11