cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
284
Views
0
Helpful
2
Replies
Enthusiast

UCS Cluster Lead won't change

Trying to change the cluster lead from Fabric Interconnect "B" to Fabric Interconnect "A" and it won't change. I issue the "cluster lead A", command but the state reverts to B being lead.

 

 

Fabric-B# sh cluster state
Cluster Id: 0xfc945e3ed27b11e6-0xb59e8c604fde4121

B: UP, PRIMARY
A: UP, SUBORDINATE

HA READY

 

Fabric-B# connect local-mgmt b
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php

 

I issue the "cluster lead a" command from local-mgmt of FI-B.

Fabric-B(local-mgmt)# cluster lead a
If the system is at 'infrastructure firmware' auto-install 'pending user Ack' stage,this action will result in upgrading and rebooting current primary. Please check the outstanding faults (scope monitoring <enter> show new-faults) and make sure the data-paths on FI-A are established properly before making it primary to ensure there is no data outage.
Do you want to continue? (yes/no):yes
Cluster Id: 0xfc945e3ed27b11e6-0xb59e8c604fde4121

 

Check the current state. Note that switchover is in process

Fabric-B(local-mgmt)# show cluster state
Cluster Id: 0xfc945e3ed27b11e6-0xb59e8c604fde4121

B: UP, SUBORDINATE, (Management services: SWITCHOVER IN PROGRESS)
A: UP, PRIMARY, (Management services: SWITCHOVER IN PROGRESS)

HA NOT READY
Management services: switchover in progress on local Fabric Interconnect

 

Wait a minute then check again. Note that B has returned to Primary

Fabric-B(local-mgmt)# show cluster state
Cluster Id: 0xfc945e3ed27b11e6-0xb59e8c604fde4121

B: UP, PRIMARY
A: UP, SUBORDINATE

HA READY

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Enthusiast

Re: UCS Cluster Lead won't change

Management interface of Fabric A was down. Duh.
2 REPLIES 2
Cisco Employee

Re: UCS Cluster Lead won't change

Tim,

 

You may want a case opened to really dig into this, but if you pull a UCSM show tech from the domain you should be able to check the below logging for more information.

 

 

svc_sam_controller.log <--- This will have cluster state logging (so you can see the switchover start and likely some messaging following this with the reason for failing back)

svc_sam_dme.log <--- This is the overarching management process, and may also contain some helpful information

Note for both the above you may need to look into the archived logs (so not just the initial svc_sam_controller.log file).

 

Let us know if you see anything strange there.

--

Niko

Enthusiast

Re: UCS Cluster Lead won't change

Management interface of Fabric A was down. Duh.
CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards