System and method for providing redundant routing capabilities for a network node

• US 8,009,556 B2
• Filed: 10/17/2003
• Issued: 08/30/2011
• Est. Priority Date: 10/17/2003
• Status: Expired due to Fees

• Current Assignee: IP Infusion, Inc. (Access Company Limited)
• Original Assignee: IP Infusion, Inc. (Access Company Limited)
• Inventors: May, Robert Alvin
• Primary Examiner(s): Decady; Albert
• Assistant Examiner(s): DUNN, DARRIN D
• Application Number:
  US10/687,955
• Publication Number:
  US 20050083953A1
• Time in Patent Office: 2,874 Days
• Field of Search: 370/351, 370/229, 370/216, 370/401, 370/219, 370/238, 370/242, 709/238, 709/248, 714/3, 714/11, 714/23
• US Class Current: 370/219
• 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
• CPC Class Codes: H04L 45/586 of virtual routers
• CPC Class Codes: H04L 45/851 Dynamic network selection or re-selection, e.g. after degradation of quality

Abstract

A routing device that provides redundancy for a node is envisioned. The routing device has a dynamic routing module operable to start functioning at a particular time. A configuration manager is provided. The configuration manager is coupled to a second routing device and stores configuration information associated with operational characteristics of a dynamic routing module associated with the second routing device. A network information module stores routing information from the second routing device. The dynamic routing module is executed upon an indication that the second dynamic routing device is no longer operating, and the configuration device configures the dynamic routing module according to the stored configuration information.

Claims

1. A first routing component configured for use in a cluster of network enabled devices having at least a first network enabled device with the first routing component and a second network enabled device with a second routing component and a network manager, the network manager external to and communicably coupled to the first routing component and to the second routing component, each of the network enabled devices in the cluster configured to communicate with network devices external to the cluster through a single network address, each of the network enabled devices in the cluster configured to operate in parallel and independently of each other,

the first routing component comprising:

a first memory;

a first configuration manager module;

a first dynamic routing module; and

a first one or more processors,

the second routing component comprising;

a second memory;

a second configuration manager module;

a second dynamic routing module; and

a second one or more processors,

the first one or more processors configured to, by the first configuration manager module, store configuration information relayed from the second configuration manager module, the configuration information associated with operational characteristics of the second dynamic routing module;

the first one or more processors further configured to, by the first routing component, apply the configuration information through the interaction of the first configuration manager module and the second configuration manager module to an instantiation of a dynamic routing module operating in the first routing component;

the first one or more processors further configured to, by the first dynamic routing module, execute in response to a command from the network manager, and further configured to execute according to the configuration information stored in the first configuration manager module upon an unplanned failure of the second dynamic routing module;

the first one or more processors further configured to transmit a hitless restart event responsive to the unplanned failure of the second dynamic routing module, the hitless restart event signaling network enabled devices external to the cluster to continue forwarding packets to the cluster; and

the first one or more processors further configured to, by a communication module of the first routing component, receive a reply from another routing component associated with the receipt of a hitless restart.

2. The routing component of claim 1 wherein the dynamic routing module implements an OSPF routing protocol.

3. An apparatus for routing network traffic flowing to and from a cluster of network enabled devices having at least a first network enabled device with a first routing component and a second network enabled device with a second routing component and a network manager, the network manager external to and communicably coupled to the first routing component and the second routing component, each of the network enabled devices in the cluster configured to communicate with network devices external to the cluster through a single network address, each of the network enabled devices in the cluster configured to operate in parallel and independently of each other, the apparatus comprising:

means for, at the second network enabled device, receiving one or more incoming messages indicating the single network address as a destination address;

means for, at the second network enabled device, routing the one or more incoming messages to one of the network enabled devices in the cluster;

means for, at a configuration manager module of the first routing component, storing configuration information relayed from a configuration manager module of the second routing component; and

means for, at a dynamic routing module of the first routing component, in response to a command from the network manager, storing routing information received from the second routing component via a cluster internal communication mechanism;

wherein upon an unplanned failure of the second dynamic routing module of the second routing component,

the dynamic routing module of the first routing component executes according to the configuration information stored in the configuration manager module of the first routing component; and

the first routing component transmits a hitless restart event, the hitless restart event signaling network enabled devices outside of the cluster to continue forwarding packets to the cluster.