When troubleshooting UCS initialization issues that require Fabric Interconnect reboots, which Fabric Interconnect should be rebooted first?

Question

Options

• AThe primary Fabric Interconnect
• BBoth Fabric Interconnects must be rebooted simultaneously
• CThe Cisco UCS Manager will determine with Fabric Interconnect to reboot
• DThe subordinate Fabric Interconnect

• A
  91% (30)
• B
  6% (2)
• D
  3% (1)

Explanation

Rebooting the primary Fabric Interconnect first triggers a controlled UCS Manager failover to the subordinate FI, which assumes the active management role and maintains cluster operations while the primary re-initializes - this is the safest approach for preserving management plane continuity during troubleshooting. Option B (simultaneous reboot) would cause a complete management outage with no active UCS Manager instance to oversee the cluster, making recovery far more complex. Option C is incorrect because UCS Manager does not autonomously decide which FI to reboot - this is always a deliberate administrative action. Option D confuses the order: rebooting the subordinate first would leave the potentially problematic primary FI in control during the reboot cycle, which is less controlled and may not resolve the initialization issue efficiently.

Memory tip: Think "Primary goes first - like a captain abandoning ship in an orderly way." The primary hands off command to the subordinate before stepping down, keeping the ship (cluster) running throughout.

No community discussion yet for this question.