FI Cluster IP unreachable

[manoj.karmacharya]

Fabric Interconnect Cluster IP unreachable when one fabric interconnect goes down or on reboot. 

[Kirk J · Accepted solution]

Greetings.

If your FI that has the Primary lead role goes down, it can take a couple of minutes for the 2ndary FI to assume the Primary lead role, and respond to the VIP ip.

If this does not happen then there is an issue with the cluster health.

What do you get from each FI's CLI:

#connect local

local#show cluster extend

Thanks,

Kirk...

[manoj.karmacharya]

It took much long time than expected. Thanks a lot kirk

[manoj.karmacharya]

FI-B(local-mgmt)# show cluster extended-state
Cluster Id: 0x19cf75e02f4d11e8-0x89d700defbe6aa2d

Start time: Wed Apr 4 18:11:59 2018
Last election time: Wed Apr 4 18:22:41 2018

B: UP, PRIMARY
A: DOWN, INAPPLICABLE

B: memb state UP, lead state PRIMARY, mgmt services state: UP
A: memb state DOWN, lead state INAPPLICABLE, mgmt services state: DOWN
heartbeat state SECONDARY_FAILED

INTERNAL NETWORK INTERFACES:
eth1, DOWN
eth2, DOWN

HA NOT READY
Peer Fabric Interconnect is down
Detailed state of the device selected for HA storage: