Question

During a UCS Manager infrastructure firmware upgrade of a clustered pair of Fabric Interconnects (FI-A subordinate, FI-B primary), an administrator activates the new infrastructure firmware and acknowledges the reboot prompt. Blade servers use fabric failover for their vNICs. Which sequence best describes how UCS Manager processes the Fabric Interconnect reboots to minimize data-plane disruption?

Accepted Answer

The subordinate Fabric Interconnect reboots first; after it rejoins the cluster, the administrator must manually acknowledge the primary, which then reboots and fails cluster leadership over

Answer

Both Fabric Interconnects reboot simultaneously so the cluster comes back with matching firmware in the shortest maintenance window

Answer

The primary Fabric Interconnect reboots first to push firmware to the subordinate, then the subordinate reboots automatically

Answer

Only the primary Fabric Interconnect reboots; the subordinate inherits the firmware over the cluster L1/L2 links without rebooting