I actually had this written down in my notes somewhere, and today a colleague of mine called me because he was having some issues. Since it’s not necessarily obvious, and others might be having the same problem, I thought I’d post a quick note here.
To reset the fabric interconnect on a Cisco UCS 6100 series, connect via your serial cable or use putty to ssh in to your fabric, and use the following commands:
connect local-mgmt [enter]
reboot [enter]
Obviously you leave out the space after the command, and the [enter] should be replaced by you actually pressing the enter key. Not sure if this is of help to folks out there, but I figured it’s more useful out here than in my private notes.
Update – July 10th:
Dan gave a good hint in the comments, that you might want check if the fabric interconnect you are trying to reboot is the primary or the subordinate, so here goes.
Connect to your fabric interconnect just like you did in the top example, and enter the local management:
connect local-mgmt
Now, check to see the state of the fabric interconnect you have attached to:
show cluster extended-state
This will give you a bunch of output, but there is one part that you are interested in more than anything else:
B: UP, SUBORDINATE
A: UP, PRIMARY
B: memb state UP, lead state SUBORDINATE, mgmt services state: UP
A: memb state UP, lead state PRIMARY, mgmt services state: UP
heartbeat state PRIMARY_OK
At the prompt, you can see (and hopefully you already knew to begin with) to what node or member you are connecting to. If you are at the node that is in a subordinate state, use the following command to change the state of the node you are rebooting to subordinate:
cluster lead a
or
cluster lead b
Where a or b is the node that you want to become subordinate. After that you can reboot the respective member
BasRaayman's Technical Take 