Viewing Cluster State

In the R81.10.X releases, this command is available starting from the R81.10.15 version.

Description

This command monitors the cluster status (after you set up the cluster).

Syntax

cphaprob state

Example

[Expert@Member1]# cphaprob state

Cluster Mode:   High Availability (Active Up)

Sync Mode:   Optimized Sync

ID         Unique Address  Assigned Load   State

1 (local)  10.231.149.1    100%            ACTIVE
2          10.231.149.2    0%              STANDBY

Active PNOTEs: None

Last member state change event:
   Event Code:                 CLUS-114904
   State change:               ACTIVE(!) -> ACTIVE
   Reason for state change:    Reason for ACTIVE! alert has been resolved
   Event time:                 Wed Mar 12 01:33:38 2025

Cluster failover count:
   Failover counter:           0
   Time of counter reset:      Wed Mar 12 00:32:50 2025 (reboot)

[Expert@Member1]#

Description of the "cphaprob state" command output fields:

Table: Description of the output fields

Field

Description

Cluster Mode

Can be one of these:

  • High Availability (Primary Up).

  • High Availability (Active Up).

Sync Mode

Can be one of these:

  • Optimized Sync.

  • Sync Enabled.

  • Sync Disabled.

ID

Indicates the Cluster Member priority.

Unique Address

Usually, shows the IP addresses of the Sync interfaces.

In some cases, can show IP addresses of other cluster interfaces.

Assigned Load

Shows the Active Cluster Member with 100% load, and the Standby Cluster Member with 0% load.

State

In a fully-functioning cluster, one Cluster Member must be in the ACTIVE state and the other Cluster Member must be in the STANDBY state.

See the summary table below "Description of the cluster states".

Active PNOTEs

Shows the Critical Devices that report theirs state as "problem" (see Viewing Critical Devices).

Last member state change event

Shows information about the last time this Cluster Member changed its cluster state.

Event Code

Shows an event code.

For information, see sk125152.

State change

Shows the previous cluster state and the new cluster state of this Cluster Member.

Reason for state change

Shows the reason why this Cluster Member changed its cluster state.

Event time

Shows the date and the time when this Cluster Member changed its cluster state.

Last cluster failover event

Shows information about the last time a cluster failover occurred.

Transition to new ACTIVE

Shows which Cluster Member became the new Active.

Reason

Shows the reason for the last cluster failover.

Event time

Shows the date and the time of the last cluster failover.

Cluster failover count

Shows information about the cluster failovers.

Failover counter

Shows the number of cluster failovers since the boot.

Notes:

  • This value survives reboot.

  • This counter is synchronized between Cluster Members.

Time of counter reset

Shows the date and the time of the last counter reset, and the reset initiator.

When you examine the state of the Cluster Member, consider whether it forwards packets, and whether it has a problem that prevents it from forwarding packets. Each state reflects the result of a test on critical devices. This table shows the possible cluster states, and whether or not they represent a problem.

Table: Description of the cluster states

Cluster
State

Description

Forwarding
packets?

Is this
state a
problem?

ACTIVE

Everything is OK.

Yes

No

ACTIVE(!)

A problem was detected, but the Cluster Member still forwards packets, because it is the only member in the cluster, or because there are no other Active members in the cluster. In any other situation, the state of the member is Down.

Yes

Yes

DOWN

One of the Critical Devices reports its state as "problem" (see Viewing Critical Devices).

No

Yes

LOST

The peer Cluster Member lost connectivity to this local Cluster Member (for example, while the peer Cluster Member is rebooted).

No

Yes

READY

State Ready means that the Cluster Member recognizes itself as a part of the cluster and is literally ready to go into action, but, by design, something prevents it from taking action. Possible reasons that the Cluster Member is not yet Active include:

  • Not all required software components were loaded and initialized yet and/or not all configuration steps finished successfully yet. Before a Cluster Member becomes Active, it sends a message to the rest of the Cluster Members, to check if it can become Active. It checks if there is already an Active member. The Cluster Member remains in the Ready state until it receives the response from the other Cluster Member and decides which, which state to choose next (Active, Standby).

  • Software installed on this Cluster Member has a higher version than the other Cluster Member. For example, when a cluster is upgraded from one version to another, and the Cluster Members have different versions, the Cluster Member with the new version have the Ready state, and the Cluster Member with the previous version have the Active/Active Attention state.

No

No

STANDBY

The Cluster Member waits for an Active Cluster Member to fail in order to start packet forwarding.

No

No

INIT

The Cluster Member is in the phase after the boot and until the Full Sync completes.

No

No