Begin by connecting to the cluster IP over SSH and checking which FI is Primary/Subordinate:

FI-A# show cluster state
A: UP, PRIMARY
B: UP, SUBORDINATE

Note: show cluster extended-state will provide more detailed information.

Having confirmed the ‘B’ fabric switch is the subordinate connect to FI-B mgmt cli interface:

FI-A# connect local-mgmt B

From FI-B local-mgmt interface issue the reboot command:

FI-B(local-mgmt)# reboot
Before rebooting, please take a configuration backup.
Do you still want to reboot? (yes/no):yes

Run the ‘cluster state’ command again to check on the status of FI-B:

FI-A(local-mgmt)# show cluster state
A: UP, PRIMARY
B: DOWN, INAPPLICABLE
HA NOT READY
Peer Fabric Interconnect is down


Once the cluster enters a HA READY status, make FI-B the Primary switch in order to reboot FI-A:

FI-A(local-mgmt)# cluster lead b

Note: After initiating a fail over the SSH session will disconnect, re-connect to the cluster and confirm cluster state.

Connect to local mgmt ‘a’ and reboot FI-A:

FI-B# connect local-mgmt a
FI-A(local-mgmt)# reboot
Before rebooting, please take a configuration backup.
Do you still want to reboot? (yes/no):yes

Confirm HA READY status before setting FI-A back to PRIMARY:

FI-B# show cluster state
B: UP, PRIMARY
A: UP, SUBORDINATE
HA READY


Set FI-A as PRIMARY, this will need to be set from current PRIMARY FI-B mgmt interface:

FI-B# connect local-mgmt b
FI-B(local-mgmt)# cluster lead a