System and method for active geographic redundancy

• US 8,565,070 B2
• Filed: 04/02/2007
• Issued: 10/22/2013
• Est. Priority Date: 11/23/2005
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Harper, Matthew H., Ramankutty, Rajesh, Cheever, Greg, Puthiyandyil, Sanil Kumar
• Primary Examiner(s): Hailu, Kibrom T
• Assistant Examiner(s): Beyen, Zewdu A
• Application Number:
  US11/731,920
• Publication Number:
  US 20070253328A1
• Time in Patent Office: 2,395 Days
• Field of Search: 370/219, 370/220, 370/216, 370/217, 370/218, 370/221, 370/476, 370/474, 370/494
• US Class Current: 370/219
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• 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

Abstract

Systems and methods are provided that allow voice and data traffic to be shifted from one chassis to other chassis without interrupting service. Geographic Redundancy (GR) is an inter-chassis redundancy, where the chassis may be a home agent, a packet data serving node, or any combination of wireless networking devices. Additionally, each chassis can have one or more partitions that handle subscriber session traffic and a corresponding redundant partition on a different chassis. The redundant chassis partition can take over all or a portion of the functionality of the active chassis partition if the active chassis or any critical peer servers/gateways communicating with the active chassis should fail. This provides users with uninterrupted service in the case of some failures.

Claims

1. A system that communicates with a second chassis having functionalities for causing wireless communications to be directed to and/or from mobile nodes, the second chassis having an active partition and a standby partition, the system comprising:

a first chassis having functionalities for causing wireless communications to be directed to and/or from mobile nodes, the first chassis including a first partition and a second partition;

wherein the first partition of the first chassis is in an active state and is configured to accept new subscriber sessions, provide mobility management for a first plurality of mobile nodes, and send at least one update regarding the first plurality of mobile nodes to the second chassis standby partition;

wherein the second partition of the first chassis is in a standby state and is configured to receive updates from the second chassis active partition regarding a second plurality of mobile nodes and to maintain subscriber session information of the second plurality of mobile nodes corresponding to subscriber session information on the second chassis active partition, wherein the second partition of the first chassis is configured, when active, to provide mobility management for the second plurality of mobile nodes,

wherein the first partition of the first chassis is a logical partition that maintains a first virtual IP network having a first set of resources that include a first range of IP addresses for assignment to the first plurality of mobile nodes, and the active partition of the second chassis is a logical partition that maintains a second virtual IP network having a second set of resources that include a second range of IP addresses for assignment to the second plurality of mobile nodes that is different from the first plurality of mobile nodes,

wherein the first range of IP addresses is different from the second range of IP addresses and the first range of IP addresses and the second range of IP addresses are derived from a common pool of IP addresses including dynamic IP addresses, and

wherein the first partition of the first chassis monitors (1) dynamic routing peer connectivity of the first chassis, (2) authentication, authorization, and accounting (AAA) server connectivity of the first chassis, and (3) internal software state of the first chassis and initiates a switchover event activating the standby partition of the second chassis by allowing the standby partition of the second chassis to transition to active state when the monitored internal software state or at least one of the dynamic routing peer connectivity and the AAA server connectivity fails.

2. The system of claim 1, wherein the first chassis is implementing an active home agent in the first partition and a standby home agent in the second partition.

3. The system of claim 1, further comprising the first chassis communicating with the second chassis using a service redundancy protocol (SRP), which is based on a transfer control protocol (TCP).

4. The system of claim 1, wherein the first partition includes an ingress context and an egress context, wherein the ingress context and the egress context each include an interface.

5. The system of claim 1, wherein the first chassis includes an authentication, authorization, and accounting (AAA) context and a service redundancy protocol (SRP) context.

6. The system of claim 1, wherein the first chassis includes a session controller to monitor the first partition of the first chassis and a session manager instance to handle subscriber session tasks.

7. The system of claim 1, wherein the second partition of the first chassis transitions from the standby state to an active state and begins receiving data corresponding to subscriber session information that the second partition maintained while in a standby state.

8. The system of claim 1, wherein the first partition of the first chassis uses a loopback address that is common to both partitions.

9. The system of claim 1, in combination with the second chassis having the active partition and the standby partition, wherein the standby partition of the first chassis provides redundancy for the active partition of the second chassis, and the standby partition of the second chassis provides redundancy for the active partition of the first chassis.

10. A method comprising:

receiving subscriber session traffic at a first partition in an active state in a first chassis from a first plurality of mobile nodes;

providing mobility management to the first plurality of mobile nodes using information in the first partition of the first chassis;

sending a message to update a first partition in a standby state in a second chassis with information from the first partition in the first chassis regarding the first plurality of mobile nodes;

receiving a message to update a second partition in a standby state in the first chassis with information regarding a second plurality of mobile nodes that are being provided mobility management from a second partition in an active state in the second chassis; and

maintaining subscriber session information of the second plurality of mobile nodes in the second partition of the first chassis that corresponds to subscriber session information of the second plurality of mobile nodes on the second partition of the second chassis,

wherein the first partition of the first chassis is a logical partition that maintains a first virtual IP network having a first set of resources that include a first range of IP addresses for assignment to the first plurality of mobile nodes, and the second partition of the second chassis is a logical partition that maintains a second virtual IP network having a second set of resources that include a second range of IP addresses for assignment to the second plurality of mobile nodes that is different from the first plurality of mobile nodes,

wherein the first range of IP addresses is different from the second range of IP addresses and the first range of IP addresses and the second range of IP addresses are derived from a common pool of IP addresses including dynamic IP addresses, and

wherein the first partition of the first chassis monitors (1) dynamic routing peer connectivity of the first chassis, (2) authentication, authorization, and accounting (AAA) server connectivity of the first chassis, and (3) internal software state of the first chassis and initiates a switchover event activating the first partition of the second chassis by allowing the first partition of the second chassis to transition to active state when the monitored internal software state or at least one of the dynamic routing peer connectivity and the AAA server connectivity fails.

11. The method of claim 10, further comprising:

initiating a switchover event where the first partition in the second chassis advertises a common loopback address that is shared with the first partition in the first chassis; and

determining which partition will transition to active by exchanging hello messages with attributes.

12. The method of claim 10, further comprising providing an ingress context and an egress context in the first chassis.

13. The method of claim 10, further comprising communicating between the first chassis and the second chassis using a service redundancy protocol (SRP), which is based on a transfer control protocol (TCP).

14. The method of claim 10, further comprising providing a session controller to monitor the first partition and a session manager instance to handle subscriber session tasks.

15. The method of claim 14, further comprising providing a suspend state for the session manage instance in a standby partition.

16. The method of claim 10, further comprising providing a virtual media access control (MAC) address for operation over a common IP subnet.

17. The method of claim 16, further comprising holding an IP address for a user who disconnected for an amount of time determined by an IP hold timer.

18. Logic encoded on one or more non-transient tangible media for execution and when executed operable to:

receive subscriber session traffic at a first partition in an active state in a first chassis from a first plurality of mobile nodes;

provide mobility management to the first plurality of mobile nodes using information in the first partition of the first chassis;

send a message to update a first partition in a standby state in a second chassis with information from the first partition in the first chassis regarding the first plurality of mobile nodes;

receive a message to update a second partition in a standby state in the first chassis with information regarding a second plurality of mobile nodes that are being provided mobility management from a second partition in an active state in the second chassis; and

maintain subscriber session information of the second plurality of mobile nodes in the second partition of the first chassis that corresponds to subscriber session information of the second plurality of mobile nodes on the second partition of the second chassis,

wherein the first partition of the first chassis is a logical partition that maintains a first virtual IP network having a first set of resources that include a first range of IP addresses for assignment to the first plurality of mobile nodes, and the second partition of the second chassis is a logical partition that maintains a second virtual IP network having a second set of resources that include a second range of IP addresses for assignment to the second plurality of mobile nodes that is different from the first plurality of mobile nodes,

wherein the first range of IP addresses is different from the second range of IP addresses and the first range of IP addresses and the second range of IP addresses are derived from a common pool of IP addresses including dynamic IP addresses, and

wherein the first partition of the first chassis monitors (1) dynamic routing peer connectivity of the first chassis, (2) authentication, authorization, and accounting (AAA) server connectivity of the first chassis, and (3) internal software state of the first chassis and initiates a switchover event activating the first partition of the second chassis by allowing the first partition of the second chassis to transition to active state when the monitored internal software state or at least one of the dynamic routing peer connectivity and the AAA server connectivity fails.

19. The logic of claim 18, further comprising providing a virtual media access control (MAC) address for operation over a common IP subnet.