System and method for maximizing connectivity during network failures in a cluster system

• US 20050268151A1
• Filed: 04/28/2004
• Published: 12/01/2005
• Est. Priority Date: 04/28/2004
• Status: Abandoned Application

• Current Assignee: Check Point Software Technologies Incorporated (Check Point Software Technologies Limited)
• Original Assignee: Nokia, Inc. (Nokia Corporation)
• Inventors: Subramanian, Anand, Hunt, Peter F.
• Application Number:
  US10/833,650
• Publication Number:
  US 20050268151A1
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/091 Measuring contribution of individual network components to actual service level
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

An apparatus, method, and system are directed to maximizing network connectivity after a network failure in a network clustering system. A cluster master in a cluster is configured to manage membership to the cluster based, in part, on a connectivity of the members to adjacent networks. A network device sends information about its connectivity to the cluster master. The cluster master compares the received information to determine whether the network device has different connectivity than the cluster. If the network device has different connectivity, the cluster master may deny cluster membership to the network device. By rejecting network devices with different connectivity, the invention ensures that data received by the cluster may be delivered with substantially equal reliability by virtually any of the cluster members. Thus, even the cluster master may be rejected from membership to the cluster.

Claims

1. A network device for managing a network failure in a cluster system, comprising:

a transceiver arranged to send and to receive information;

a processor, coupled to the transceiver, that is configured to perform actions, including;

receiving connectivity information associated with another network device; and

if the received connectivity information is substantially different from a set of connectivity information associated with the cluster system, denying cluster membership to the other network device.

2. The network device of claim 1, further comprising:

determining another connectivity information associated with the network device; and

if the other connectivity information associated with the network device is substantially different from the set of connectivity information associated with the cluster system, exiting the cluster system.

3. The network device of claim 2, wherein if the other connectivity information associated with the network device is substantially different, sending an exit message to the cluster system.

4. The network device of claim 1, wherein the received connectivity information further comprises information that identifies a network and whether the other network device has connectivity to the identified network.

5. The network device of claim 4, wherein identification of the network further comprises at least one of a network address, and a network mask length.

6. The network device of claim 1, wherein the processor is further configured to perform actions, further comprising:

determining, based, in part, on the received connectivity information, if the other network device is configured for the same set of networks as the cluster system;

determining, based, in part, on the received connectivity information, if the other network device has connectivity to the same set of networks as the cluster system; and

if the other network device is configured for a different set of networks than the cluster system or has connectivity to a different set of networks than the cluster system, marking the received connectivity information as substantially different from the cluster system.

7. The network device of claim 1, wherein denying cluster membership to the other network device further comprises at least one of denying a request to join the cluster system from the other network device, and requesting the other network device to exit the cluster system.

8. The network device of claim 1, wherein the processor is configured to perform actions, further comprising employing a connectivity timer to delay making a change to the membership of the cluster system.

9. The network device of claim 1, wherein the processor is configured to perform actions, further comprising:

receiving a message from a third network device indicating that the third network device is attempting to operate as a cluster master to the cluster system;

if the network device has greater connectivity than the third network device, sending a response indicating that another master exits to the third network device;

if the network device has substantially a same connectivity as the third network device and if the network device has more cluster members than the third network device, sending the response indicating that another master exits to the third network device; and

if the network device has substantially the same connectivity as the third network device and if the network device has substantially the same cluster members as the third network device, and if a network address associated with the network device is substantially less than a network address associated with the third network device, sending the response indicating that another master exits to the third network device.

10. The network device of claim 9, wherein the processor is configured to perform actions, further comprising:

if the network device has substantially the same connectivity as the third device and if the network device has substantially better system performance than the third network device, sending the response indicating that another master exits to the third network device.

11. A method for managing a network failure in a cluster system, comprising:

receiving connectivity information associated with a network device; and

if the received connectivity information is substantially different from a set of connectivity information associated with the cluster system, denying cluster membership to the network device.

12. The method of claim 11, wherein the received connectivity information further comprises information that identifies a network and whether the network device has connectivity to the identified network.

13. The method of claim 11, wherein denying cluster membership to the network device further comprises at least one of denying a request to join the cluster system from the network device, and requesting the network device to exit the cluster system.

14. A system for managing a network failure in a cluster system, comprising:

a network device configured to perform actions, comprising;

sending a request to join the cluster system; and

sending connectivity information associated with the network device; and

a cluster master that is configured to perform actions, comprising;

receiving the connectivity information associated with the network device; and

if the received connectivity information is substantially different from a set of connectivity information associated with the cluster system, denying cluster membership to the network device.

15. The system claim 14, wherein the cluster master is further configured to perform actions, further comprising:

determining, based, in part, on the received connectivity information, if the network device is configured for the same set of networks as the cluster system;

determining, based, in part, on the received connectivity information, if the network device has connectivity to the same set of networks as the cluster system; and

if the network device is configured for a different set of networks than the cluster system or has connectivity to a different set of networks than the cluster system, marking the received connectivity information as substantially different from the cluster system.

16. The system claim 14, wherein denying cluster membership to the network device further comprises requesting the other network device to exit the cluster system.

17. The system claim 14, wherein the cluster master is configured to perform actions, further comprising employing a connectivity timer to delay making a change to the membership of the cluster system.

18. The system claim 14, wherein the cluster master is configured to perform actions, further comprising:

receiving a message from another network device, indicating that the other network device is attempting to operate as a cluster master to the cluster system;

if the cluster master has greater connectivity than the other device, sending a response indicating that another master exits to the other network device;

if the cluster master has substantially a same connectivity as the other network device and if the cluster master has more cluster members than the other network device, sending the response indicating that another master exits to the other network device; and

if the cluster master has substantially the same connectivity as the other network device and if the cluster master has substantially the same cluster members as the other network device, and if a network address associated with the cluster master is substantially less than a network address associated with the other network device, sending the response indicating that another master exits to the other network device.

19. The system of claim 14, wherein the network device is configured to perform actions, further comprising:

detecting a change in its connectivity;

updating the connectivity information associated with the network device; and

sending the updated connectivity information towards the cluster master.

20. The system of claim 19, wherein sending the updated connectivity information further comprises sending the updated connectivity information within a keepalive message, wherein a monotonically increasing sequence number is associated with the keepalive message to enable packet loss calculation.

21. An apparatus for managing a failure in a cluster system, comprising:

a means for receiving connectivity information associated with a network device;

a means for determining if the received connectivity information is substantially different from a set of connectivity information associated with the cluster system; and

if the received connectivity information is substantially different from a set of connectivity information associated with the cluster system, employing a means for denying cluster membership to the network device.

22. A modulated data signal for enabling the management of a failure in a cluster system, comprising:

sending, by a network device, a request to join the cluster system;

sending, by the network device, connectivity information associated with the network device towards a cluster master; and

if the received connectivity information is substantially different from a set of connectivity information associated with the cluster system, sending, by the cluster master, a message denying cluster membership to the network device.