High available method for border gateway protocol version 4

• US 8,467,287 B2
• Filed: 10/29/2008
• Issued: 06/18/2013
• Est. Priority Date: 06/27/2002
• Status: Expired due to Fees

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Foundry Networks LLC (Broadcom, Inc.)
• Inventors: Ning, Qi, Visser, Lance A
• Primary Examiner(s): SCHEIBEL, ROBERT C
• Application Number:
  US12/260,719
• Publication Number:
  US 20090129261A1
• Time in Patent Office: 1,693 Days
• Field of Search: None
• US Class Current: 370/218
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/28 using route fault recovery

Abstract

High availability BGP4 is based on redundant hardware as well as redundant software that replicates the RUN state of BGP4. There are two copies, respectively active and backup, of BGP4 running on two separate redundant hardware platforms. All BGP4 internal implementations apply various methods to replicate the running state of BGP4 independently of peer network routers. When this hardware or software fails on one redundant hardware platform, peer routers are unaware of the failure. Internally, based on duplicative states, the local router recovers from the failure and keeps the protocol running. During the recovery period, the local router can bring up a backup again. In the HA architecture, these activities are not detected by peer routers, such that there is no instability to the Internet backbone caused by BGP4 failure.

Claims

1. A method, comprising:

maintaining a first routing-protocol instance in a first control unit in a router;

maintaining a second routing-protocol instance in a second control unit in the router, wherein the first control unit and second control unit are on separate hardware;

maintaining a first transmission-layer socket in the first routing-protocol instance for communication between the router and a peer router;

cloning onto the second routing-protocol instance a second transmission-layer socket based on the first transmission-layer socket; and

simultaneously receiving route-related data from the peer router at the first and second routing-protocol instances via the first and second sockets, respectively.

2. The method of claim 1, wherein the routing protocol is Border Gateway Protocol (BGP).

3. The method of claim 1, further comprising synchronizing the configuration between the first routing-protocol instance and the second routing-protocol instance.

4. The method of claim 1, wherein the first routing-protocol instance and second routing-protocol instance are maintained by separate operating system software.

5. The method of claim 1, wherein the first routing-protocol instance is an active instance and the second routing-protocol instance is a backup instance;

and

wherein in response to a failure in the router, the method further comprises activating the second routing-protocol instance without the failure being detected by the peer router.

6. A routing system, comprising:

a processor;

a memory;

a first control unit maintains a first routing-protocol instance and a first transmission-layer socket in the first routing-protocol instance for communication between the router and a peer router; and

a second control unit maintains a second routing-protocol instance, wherein the first control unit and second control unit are on separate hardware;

wherein the second routing-protocol instance comprises a second transmission-layer socket that is cloned based on the first transmission-layer socket; and

wherein the first and second routing-protocol instances simultaneously receive route-related data from the peer router via the first and second sockets, respectively.

7. The routing system of claim 6, wherein the routing protocol is Border Gateway Protocol (BGP).

8. The routing system of claim 6, wherein the configuration between the first routing-protocol instance and the second routing-protocol instance is synchronized.

9. The routing system of claim 6, wherein the first routing-protocol instance and second routing-protocol instance are maintained by separate operating system software.

10. The routing system of claim 6, wherein the first routing-protocol instance is an active instance and the second routing-protocol instance is a backup instance;

and

wherein in response to a failure in the router, the second routing-protocol instance is activated without the failure being detected by the peer router.

11. A routing means, comprising:

a first control means for maintaining a first routing-protocol instance and a first transmission-layer socket means for communication between the routing means and peer router; and

a second control means for maintaining a second routing-protocol instance, wherein the first control means and second control means are on separate hardware;

wherein the second routing-protocol instance comprises a second transmission-layer socket means that is cloned based on the first transmission-socket means; and

wherein the first and second routing-protocol instances simultaneously receive route-related data from the peer router via the first and second socket means, respectively.

12. The routing means of claim 11, wherein the routing protocol is Border Gateway Protocol (BGP).

13. The routing means of claim 11, wherein the configuration between the first control means and the second control means is synchronized.

14. The routing means of claim 11, wherein the first control means and second control means are maintained by separate operating system software.

15. The routing means of claim 11, wherein the first control means is an active means and the second control means is a backup means;

and

wherein in response to a failure in the routing means, the second control means is activated without the failure being detected by the peer router.