vCenter Server inaccessible after vCHA failover due to incorrect vNIC mapping.

Products

• VMware vCenter Server

Issue/Introduction

vCenter Server becomes inaccessible on the network following a High Availability (vCHA) failover event.

• Context:

  • A failover occurred from the Active node to the Passive node.

  • As part of troubleshooting, the vCHA configuration has been destroyed, leaving only the previously Passive node (now Active) running.

  • Despite the node being powered on, the vCenter Server Management interface is unreachable.

• Verification:

  • Upon checking the Virtual Machine settings of the active vCenter node, you observe that both network adapters (vNIC-1 and vNIC-2) are connected to the vCHA Heartbeat network.

  • The correct configuration requires vNIC-1 to be connected to the Management network and vNIC-2 to the Heartbeat network.

  • Attempts to change the network backing for vNIC-1 fail because the target Management portgroup is configured with Static Binding.

Environment

VMware vCenter Server

Resolution

To restore connectivity, you must move the Management interface (vNIC-1) to a reachable network using an Ephemeral portgroup or a Standard Switch (VSS).

1. Access the Host: Log in directly to the ESXi host running the vCenter Server VM using the VMware Host Client.

2. Create Recovery Network: Create a temporary Standard Switch (VSS) with a portgroup mapped to the Management VLAN/Network. Alternatively, if available, use an Ephemeral portgroup on the existing VDS.

3. Remap vNIC: Edit the vCenter Server VM settings and change the network adapter for Network Adapter 1 (vNIC-1) from the Heartbeat network to the new Standard Switch portgroup (or Ephemeral portgroup).

   • Note: Refer to Broadcom KB 318719 for detailed steps on moving vCenter from a Distributed Switch to a Standard Switch during outages.

4. Verify Connectivity: Once the network adapter is connected to the Standard Switch, verify that the vCenter Server is accessible on the network.

5. Restore to VDS: After vCenter connectivity is restored and the VDS is manageable, migrate vNIC-1 back to the correct production Management Distributed Portgroup.