Viewing the cluster status

Published on Aug 21, 2026

3 minute(s) read

Article summary

You can view comprehensive status information about the cluster and its components. You can do so using the CLI of either node or the Web UI of the primary node. The following table describes the information that is provided.

Field	Description
Healthy	Whether the cluster is healthy.
Status	The state of the cluster: Running—All services are running, all communication links are up, and all nodes are online. Stopped—At least one service is not running on at least one node. Starting—At least one service is starting up on at least one node, or the database synchronization is being set up on the secondary node. Updating—A software upgrade or downgrade is being performed on a node in the cluster. Degraded—Backup links of the same type are down, or the secondary node is configured, but currently offline. Error—Communication links are down or broken, or a service failed to start. Unknown—The node is not accessible.
Primary Node	The hostname of the primary node. If you are viewing the status from the primary node CLI, `(self)` is also displayed.
Configuration in sync	Whether the configurations of the primary and secondary nodes are synchronized. Important If the value is `no`, do not perform a failover or reload either node. Doing so will put the configuration in an undefined state and make it difficult to recover the cluster.
Nodes Status	The state of each node in the cluster: Running—All services are running, all communication links are up, and all nodes are online. Stopped—At least one service is not running on at least one node. Starting—At least one service is starting up on at least one node, or the database synchronization is being set up on the secondary node. Updating—A software upgrade or downgrade is being performed on a node in the cluster. Degraded—Backup links of the same type are down, or the secondary node is configured, but currently offline. Error—Communication links are down or broken, or a service failed to start. Unknown—The node is not accessible.
Interfaces	The state of the HA interfaces on the primary and secondary nodes: Up—All links of the same type are up. Off—The interface is disabled in the configuration. Down—The interface is configured, but is down. Either all links of the same type are down, or the primary node interface is not connected to the secondary node interface.
Services	The state of the following services: Cluster Communication Engine sends messages between the two nodes in the cluster, handles failover and split-brain occurrences, and so on. Cluster Resource Manager manages the resource agents that monitor and manage cluster resources and services. Data Replication Services (Configuration, Alerts, Security Content) manage the replication of alert data (if enabled), configuration data, and security content between the two nodes in the cluster. State values: Running—The service is running. Stopped—The service is stopped. Starting—The service is starting, or the database synchronization is being set up on the secondary node. Error—The service failed to start. Off—The service is disabled in the configuration. Unknown—The node is not accessible, so the status cannot be reported.
Resources	The state of each resource agent: Running—The agent is running. Stopped—The agent is stopped. Starting—The agent is starting. Error—The agent failed to start. Off—The agent is disabled in the configuration. Unknown—The node is not accessible, so the status cannot be reported. For a description of the resource agents and their normal states on the primary and secondary nodes, see Viewing resource agent status .

Prerequisites

Monitor, Operator, or Admin access

:

Was this article helpful?