Print Download PDF Send Feedback

Previous

Next

Initiating Manual Cluster Failover

Description

This command lets you initiate a manual cluster failover (see sk55081).

Syntax

Shell

Command

Gaia Clish

set cluster member admin

down

up

Expert mode

clusterXL_admin

down

up

Example

Member2> show cluster state

 

Cluster Mode: High Availability (Active Up) with IGMP Membership

 

ID Unique Address Assigned Load State Name

 

1 192.168.20.176 0% STANDBY Member1

2 (local) 192.168.20.177 100% ACTIVE Member2

 

Active PNOTEs: None

 

Last member state change event:

Event Code: CLUS-11482

State change: STANDBY -> ACTIVE

Reason for state change: No other ACTIVE member has been found in the cluster

Event time: Sun Jun 3 20:24:35 2018

 

Last cluster failover event:

Transition to new ACTIVE: Member 1 -> Member 2

Reason: Interface eth1 is down (Cluster Control Protocol packets are not received)

Event time: Sun Jun 3 20:24:35 2018

 

Cluster failover count:

Failover counter: 261

Time of counter reset: Sun Jun 3 20:24:35 2018 (reboot)

 

Member2>

 

Member2> set cluster member admin down

Setting member to administratively down state ...

Member current state is DOWN

Member2>

 

Member2> show cluster state

 

Cluster Mode: High Availability (Active Up) with IGMP Membership

 

ID Unique Address Assigned Load State Name

 

1 192.168.20.176 100% ACTIVE Member1

2 (local) 192.168.20.177 0% DOWN Member2

 

Active PNOTEs: ADMIN

 

Last member state change event:

Event Code: CLUS-11144

State change: ACTIVE -> DOWN

Reason for state change: ADMIN_DOWN PNOTE

Event time: Sun Jun 3 20:27:19 2018

 

Last cluster failover event:

Transition to new ACTIVE: Member 2 -> Member 1

Reason: ADMIN_DOWN PNOTE

Event time: Sun Jun 3 20:27:19 2018

 

Cluster failover count:

Failover counter: 262

Time of counter reset: Sun Jun 3 20:27:19 2018 (reboot)

 

Member2>

 

Member2> set cluster member admin up

Setting member to normal operation ...

Member current state is STANDBY

Member2>

 

Member2> show cluster state

 

Cluster Mode: High Availability (Active Up) with IGMP Membership

 

ID Unique Address Assigned Load State Name

 

1 192.168.20.176 100% ACTIVE Member1

2 (local) 192.168.20.177 0% STANDBY Member2

 

Active PNOTEs: None

 

Last member state change event:

Event Code: CLUS-11490

State change: DOWN -> STANDBY

Reason for state change: There is already an ACTIVE member in the cluster (member 1)

Event time: Sun Jun 3 20:27:44 2018

 

Last cluster failover event:

Transition to new ACTIVE: Member 2 -> Member 1

Reason: ADMIN_DOWN PNOTE

Event time: Sun Jun 3 20:27:19 2018

 

Cluster failover count:

Failover counter: 262

Time of counter reset: Sun Jun 3 20:27:44 2018 (reboot)

 

Member2>