Host HBA Shows Offline in vCenter after Fabric Disruption - Cisco UCS X-Series

Products

• VMware vSphere ESXi

Issue/Introduction

• In VMware vSphere ESXi 8.0 Update 3, physical host bus adapters (HBAs) may intermittently report an "offline" status within the vCenter Server inventory. This behavior is primarily observed with Cisco VIC/vHBA architectures.
• While the HBA status displays as "offline," there is typically no impact on running virtual machines or the host's ability to process I/O, indicating a potential cosmetic reporting issue within the vCenter management layer.

Environment

VMware vSphere ESXi 8.0 Update 3 (or later)

Cause

• The "offline" status is often due to the adapter's state not immediately refreshing after fabric-level configuration changes (such as zoning or storage fabric disruptions). With Cisco VIC/vHBA architectures, the host may initialize the adapter before storage targets are fully available or discovered on the fabric.
• If the HBA fails to perform a successful Fabric Login (FLOGI) or Port Login (PLOGI) discovery during the initial handshake, the adapter may remain in a stale "offline" state in vCenter, even after the underlying connectivity is restored. This requires a manual refresh or host-level trigger to force the HBA to rebuild its storage paths and update its status.

Resolution

To resolve the intermittent "offline" HBA status, perform a manual rescan of the storage adapters via vCenter.

Steps:

1. Log in to the vSphere Client.
2. Navigate to the Hosts and Clusters view.
3. Select the affected ESXi host from the inventory.
4. Navigate to the Configure tab.
5. Under the Storage section, select Storage Adapters.
6. Click the Rescan icon (or "Rescan Storage Adapter") to force the host to re-query the storage fabric and rediscover targets.
7. If the status remains "offline" after the rescan, verify the fabric zoning and perform a controlled host reboot to force a full re-initialization of the HBA login process.

Additional Information

• If the issue persists despite manual refreshes, inspect physical network switch logs and storage array logs for intermittent port flapping or fabric disruptions that may be causing the HBA to lose its login state.
• Ensure that the nfnic driver and Cisco VIC firmware are aligned according to the Broadcom Compatibility Guide. Misaligned versions can contribute to instability in link recovery.
• For further diagnostic assistance, refer to the vSphere Storage documentation on Managing Storage Adapters.