Initiating Manual Cluster Failover

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

Description

This command initiates a manual cluster failover.

Syntax

clusterXL_admin {down | up}

Script Workflow

This shell script does one of these:

  • Registers a Critical Device called "admin_down" and reports the state of that Critical Device as "problem".

    This gracefully changes the state of the Cluster Member to "DOWN".

  • Reports the state of the registered Critical Device "admin_down" as "ok".

    This gracefully changes the state of the Cluster Member to "UP".

    Then, the script unregisters the Critical Device "admin_down".

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

... ...

[Expert@Member1]#

[Expert@Member1]# clusterXL_admin down
Setting member to administratively down state ...
Member current state is DOWN
[Expert@Member1]#

[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    0%              DOWN
2          10.231.149.2    100%            ACTIVE


Active PNOTEs: ADMIN

Last member state change event:
   Event Code:                 CLUS-111400
   State change:               ACTIVE -> DOWN
   Reason for state change:    ADMIN_DOWN PNOTE
   Event time:                 Wed Mar 12 01:33:38 2025

Last cluster failover event:
   Transition to new ACTIVE:   Member 1 -> Member 2
   Reason:                     ADMIN_DOWN PNOTE
   Event time:                 Wed Mar 12 01:33:38 2025

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

[Expert@Member1]#

[Expert@Member1]# clusterXL_admin up
Setting member to normal operation ...
Member current state is STANDBY
[Expert@Member1]#

[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    0%              STANDBY
2          10.231.149.2    100%            ACTIVE


Active PNOTEs: None

Last member state change event:
   Event Code:                 CLUS-114802
   State change:               DOWN -> STANDBY
   Reason for state change:    There is already and ACTIVE member in the cluster (member 2)
   Event time:                 Wed Mar 12 01:35:38 2025

Last cluster failover event:
   Transition to new ACTIVE:   Member 1 -> Member 2
   Reason:                     ADMIN_DOWN PNOTE
   Event time:                 Wed Mar 12 01:33:38 2025

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

[Expert@Member1]#