Use the show command to display the status of nodes in the cluster:
{primary:node0}
user@host> show chassis cluster status redundancy-group 0
Cluster ID: 3
Node name Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 0
node0 254 Primary No No
node1 2 Secondary No No
Output to this command indicates that node 0 is primary.
Use the request command to trigger a failover and make node 1 the primary:
- {primary:node1}
- user@host> request chassis cluster failover
redundancy-group 0 node 1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
- Initiated manual failover for redundancy group 0
Use the show command to display the new status of nodes in the cluster.
{primary:node1}
user@host> show chassis cluster status redundancy-group 0
Cluster ID: 1
Node name Priority Status Preempt Manual failover
Redundancy-group: 0, Failover count: 1
node0 254 Secondary No Yes
node1 2 Primary No Yes
Output to this command shows that node 1 is now primary.
You can reset the failover for redundancy groups using the request command. This change is propagated across the cluster.
- {primary:node1}
- user@host> request chassis cluster failover
reset redundancy-group 0 node 0
- node0:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
- Successfully reset manual failover for redundancy group
1
- node1:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
- Successfully reset manual failover for redundancy group
1
With back-to-back failovers, after doing a manual failover, you must issue the reset failover command before requesting another failover.
When the primary node fails and comes back up, election of the primary is done based on regular criteria (priority and preempt).