Verify that HA is running and which FI is the primary first, then connect local-mgmt and issue the cluster lead [a|b] command
In the example below, A is initailly the Primary, after the cluster lead b, B is the primary
FI6100-1-A# show cluster extended-state
Cluster Id: 0x79c0e920540811e0-0x9239000decd35dc4
Start time: Sat Mar 26 02:35:30 2011
Last election time: Sat Mar 26 02:35:57 2011
A: UP, PRIMARY
B: UP, SUBORDINATE
A: memb state UP, lead state PRIMARY, mgmt services state: UP
B: memb state UP, lead state SUBORDINATE, mgmt services state: UP
heartbeat state PRIMARY_OK
INTERNAL NETWORK INTERFACES:
eth1, UP
eth2, UP
HA READY
Detailed state of the device selected for HA storage:
Chassis, serial: FOX1326G5KH, state: active
FI6100-1-A# connect local-mgmt a
FI6100-1-A(local-mgmt)# cluster lead
a b
FI6100-1-A(local-mgmt)# cluster lead b
Cluster Id: 0x79c0e920540811e0-0x9239000decd35dc4
FI6100-1-A(local-mgmt)# Connection to 172.25.183.132 closed by remote host.
Connection to 172.25.183.132 closed.
Check
FI6100-1-B# show cluster extended-state
Cluster Id: 0x79c0e920540811e0-0x9239000decd35dc4
Start time: Sat Mar 26 02:36:43 2011
Last election time: Tue Apr 5 00:32:55 2011
B: UP, PRIMARY
A: UP, SUBORDINATE
B: memb state UP, lead state PRIMARY, mgmt services state: UP
A: memb state UP, lead state SUBORDINATE, mgmt services state: UP
heartbeat state PRIMARY_OK
INTERNAL NETWORK INTERFACES:
eth1, UP
eth2, UP
HA READY
Detailed state of the device selected for HA storage:
Chassis, serial: FOX1326G5KH, state: active
