Node Status Collected

The following table provides descriptions of node states.

expand icon

Node States

Node State Description
BACKUP In the backup state, this node becomes the primary node if the primary fails or enters the DOWN state. The backup node also receives the checkpoint state data from the primary.
DOWN In the down state, the node is not available to participate in leader election. The node enters this state during any user action, other than a failure, that makes the node unavailable for management. Examples of user actions are:
  • Upgrading the softwareRebooting the system using the reboot command.

  • Initiating a failover using the run failover command.

  • Synchronizing the node software and configuration in non-volatile storage using the synchronize command.

FAIL In the fail state, the node has failed and needs to be restarted or repaired. The node reaches this state if the system has a hardware or software failure.
INIT In the initial state, the node is being initialized. A node stays in this state when it is coming up and remains in this state until it has been fully initialized. Being fully initialized means that all of the hardware has been initialized correctly and there are no diagnostic faults.
MASTER In the primary (master) state, the node is responsible for all switch management functions.
STANDBY In the standby state, leader election occurs—the primary and backup nodes are elected. The priority of the node is only significant in the standby state. In SummitStack, there can be more than two master-capable nodes. All such nodes that do not get elected either master or backup remain in standby state.