Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

UCS Fabric Interconnect After Failover(primary,subordinate)

     Dear Team,

After the failover of FI-A to FI-B when we check show cluster status its show FI-B as primary and FI-A as subordinate

Now the FI-A is Back on line and HA shows as ready, but when we check show cluster status its still shows FI-B as primary and FI-A as subordinate

Will the FI-A revert back itself as primary or do we need to give the command force lead from FI-B to make FI-A as primary again?

Thanks and Regards

Jose

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

UCS Fabric Interconnect After Failover(primary,subordinate)

Hi Jose,

FI A won't revert back to being primary again. The primary/sub-ordinate is purely from a management perspective and nothing else (both FIs forward traffic etc). So there is no problem in having FI B as primary or vice-versa.

On a side note, if you want to trigger a failover manually, you can do it from the CLI by going to the local-mgmt context of the primary FI:

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

Thanks,

Shankar
1 REPLY
Cisco Employee

UCS Fabric Interconnect After Failover(primary,subordinate)

Hi Jose,

FI A won't revert back to being primary again. The primary/sub-ordinate is purely from a management perspective and nothing else (both FIs forward traffic etc). So there is no problem in having FI B as primary or vice-versa.

On a side note, if you want to trigger a failover manually, you can do it from the CLI by going to the local-mgmt context of the primary FI:

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

Thanks,

Shankar
8976
Views
0
Helpful
1
Replies
CreatePlease login to create content