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 fabric interconnect commands.
Following on from cabling our cisco ucs infrastructure we will first begin to configure the fabric interconnects using the basic system configuration dialog.
Connect to the console port of fabric interconnect 1 which will be the primary member in the cluster.
After connecting to nxos some no of show nxos cli commands available on nexus 5x series are available but no conf t works.
In our introduction to cisco ucs architecture we touched briefly on the cisco ucs fabric interconnect specifically we talked about the latest generation the cisco ucs 6454 fabric interconnect.
However in the ucs fi cli guide there is no mention of this command.
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.
You must force the failover from the primary fabric interconnect.
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.
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.
The success in doing that would have instantly led me to the mgmt0 connection on the b fabric.
Well i could always access the a fabric interconnect.
Ucs forcing a fabric interconnect failover forcing a fabric interconnect failover this operation can only be performed in the cisco ucs manager cli.
When committed this change may disconnect the current cli session ucs a fabric interconnect commit buffer enabling a standalone fabric interconnect for cluster configuration.
Found that from ucs fabric interconnect there is a command to connect to nxos.