Node management in high-availability cluster

• US 6,928,589 B1
• Filed: 01/23/2004
• Issued: 08/09/2005
• Est. Priority Date: 01/23/2004
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Pomaranski, Ken Gary, Barr, Andrew Harvey
• Primary Examiner(s): Iqbal, Nadeem
• Application Number:
  US10/764,244
• Publication Number:
  US 20050188283A1
• Time in Patent Office: 564 Days
• Field of Search: 714/47, 714/4, 714/16, 714/25, 714/37, 714/39, 714/43, 714/56, 714/15, 714/21, 709/220, 709/221, 709/224, 709/226, 709/239, 709/240
• US Class Current: 714/47.2
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04Q 3/0062 Provisions for network management

Abstract

One embodiment disclosed relates to a method of status generation for a node of a high-availability cluster. A heartbeat signal is sent from the node through a network to the cluster. In addition, a current status of the node is determined, and the status is sent out through a specialized interface to a next node. Another embodiment disclosed relates to a method of cluster-wide management performed per node. A heartbeat input received from the previous node is checked. Furthermore, an up/down status input received from the previous node and a degraded status input received from the previous node are also checked. Another embodiment disclosed relates to a system for of a high-availability cluster. The system includes a general inter-node communication network that is configured to carry signals including heartbeat signals from the nodes. In addition, a separate inter-node communication channel is included for communicating node status signals.

Claims

1. A method of cluster-wide management performed per node, the method comprising:

checking an up/down status input received from a previous node;

checking a degraded status input received from the previous node, wherein the degraded status input comprises multiple degradation levels with one such level comprising a “

bad”

state indicating that the previous node appears down;

checking a heartbeat input received from the previous node; and

comparing the degraded status with a node removal threshold for potential removal of the previous node from the cluster if the degraded status shows degradation above the threshold.

2. The method of claim 1, further comprising:

determining whether a configuration file at the previous node has been changed; and

if the configuration file has been changed, then retrieving the configuration file from the previous node and storing the retrieved configuration file at the present node.

3. The method of claim 1, further comprising:

performing a logical analysis of the inputs to determine whether a failure of the previous node is indicated.

4. The method of claim 3, wherein the logical analysis comprises determining a failure of the previous node if a majority of the status inputs indicates that the previous node appears down.

5. The method of claim 3, wherein the logical analysis differentiates between the failure of the previous node and a failure of an inter-node communication channel.

6. The method of claim 5, wherein the logical analysis further differentiates between a problem with a first inter-node communication channel and a problem with a second inter-node communication channel.

7. The method of claim 6, wherein the first inter-node communication channel comprises a point-to-point link dedicated for node status information, and wherein the second inter-node communication channel comprises a network for carrying heartbeat signals and other communications.

8. The method of claim 1, further comprising reporting that a network carrying the heartbeat is down if the heartbeat is bad and the two status inputs are not both bad.

9. The method of claim 1, further comprising reporting a problem with an inter-node communication channel carrying the status inputs if the heartbeat is okay and one, but not both, of the two status inputs is bad.

10. A system for of a high-availability cluster, the system comprising:

a general inter-node communication network that is configured to carry signals including heartbeat signals from the nodes; and

a separate inter-node communication channel for communicating node status signals including at least an up/down status signal and a degraded status signal;

wherein the degraded status signal is compared with a node removal threshold for potential removal of a node from the cluster if the degraded status signal shows degradation above the threshold.

11. The system of claim 10, wherein the system is configured with a logical analysis procedure that differentiate between a failure of a node and a problem with inter-node communication.

12. The system of claim 11, wherein the logical analysis further differentiates between a problem with the general inter-node communication network and a problem with the separate inter-node communication channel.