Understanding Cluster/Node Status Summary

On all Pulse One screens, a summary of cluster-related statuses appears at the bottom right of the screen. This summary reflects the current state of the cluster, as viewed from the current node. For example:

The summary statuses are included:

•Cluster Status: The status of the Pulse One cluster, as reported by the cluster. This status can be:

•Disabled. There is no Active/Passive cluster configured.

•Up. An Active/Passive cluster is configured, and both nodes are available.

•Down. An Active/Passive cluster is configured, but only one node is available.

This state indicates that some intervention is required to return the cluster status to Up.

•Changing. This is a transitional state that only appears when a standalone node is changing to be the first (Active) node in a cluster.

•Node Status: The status of the current node, as reported by the node. This status can be:

•Active. The current node is available, and part of an Active/Passive cluster.

•Standalone. The current node is available, but is not part of an Active/Passive cluster.

After a clustered pair has been formed, the name of the Active node is displayed in brackets.

•Auto Failover: The current setting of the automatic failover switch. The switch state is set by the cluster config CLI command. This status can be:

•Enabled. Auto-failover of a correctly-configured Active/Passive pair will be attempted if the current Active node fails.

•Disabled. Auto-failover is off. Manual failover of a correctly-configured Active/Passive pair is still supported.

The automatic failover switch setting is independent of the cluster status and node status.

An Unknown status is also supported for all three summary statuses. For example:

This indicates that either an internal issue has occurred with the cluster, or that the GUI is unable to retrieve the cluster status from the server.

All Active/Passive cluster configuration is performed from the Pulse One Command-Line Interface. See the Pulse One Getting Started Guide for details of all configuration and failover processes.

Example: Typical Node Lifecycle

When you log into a new standalone node, such as one that has just been created, the following summary status appears:

You can then use the cluster commands in the Pulse One CLI to change the standalone node to be the Active Node in an Active/Passive pair with (optionally) auto-failover enabled. To do this:

1.Using the CLI on the standalone node, promote the node to be the Active node in a planned Active/Passive cluster. The name of the node (in this example, Copper) is now included in brackets.

The following summary status appears:

This summary indicates that the node is no longer standalone, but that the transition is still in progress.

2.Using the CLI of the Active node, you can add a Passive node to the intended cluster. Once completed, this creates the required join token.

After this process completes on the Active node, the summary statuses update so that the Cluster Status is Down. This indicates that only a single node is available.

3.Using the CLI of the Passive node, you can then use the join token to finalize the join.

After this process completes on the Passive node, the following summary statuses appear:

4.(Optional) Enable automatic failover from the CLI on the Active node.

After this process completes, the following summary statuses appear:

Configuration of the Active/Passive cluster is now complete, and reported correctly in the Pulse One GUI.

If either node in an Active/Passive cluster fails:

1.Perform either an automatic or manual failover. After this process completes, the new Active node is a standalone Active node.

The following summary statuses appear:

In this example, the Active node is now the previous Passive node, Brass.

2.Repair the failed node and re-form the Active/Passive cluster.

After this process completes, the summary statuses of the cluster returns to an operational state: