After connecting to nxos some no of show nxos cli commands available on nexus 5x series are available but no conf t works.
Ucs fabric interconnect commands.
The success in doing that would have instantly led me to the mgmt0 connection on the b fabric.
You must force the failover from the primary fabric interconnect.
However in the ucs fi cli guide there is no mention of this command.
Ucs forcing a fabric interconnect failover forcing a fabric interconnect failover this operation can only be performed in the cisco ucs manager cli.
The following example shows how to activate a specific version of kernel software on fabric interconnect a.
Power on this fabric interconnect leaving the secondary interconnect powered off for now.
Following on from cabling our cisco ucs infrastructure we will first begin to configure the fabric interconnects using the basic system configuration dialog.
Ucs a scope fabric interconnect a ucs a fabric interconnect set out of band ip 10 105 214 107 netmask 255 255 255 0 gw 10 105 214 1 warning.
From there i could have run connect local mgmt b and accessed ucsm which was running just fine on fabric interconnect b and flipped ucsm back to fabric interconnect a using local mgmt commands.
Found that from ucs fabric interconnect there is a command to connect to nxos.
Well i could always access the a fabric interconnect.
Connect to the console port of fabric interconnect 1 which will be the primary member in the cluster.
Now i want to take a closer look at the function of the cisco ucs fabric interconnect and some things to think about when you are deploying it.
Ucs a scope fabric interconnect a ucs a fabric interconnect activate firmware kernel version 3 0 ucs a fabric interconnect commit buffer ucs a fabric interconnect related commands.