ESXi management network connectivity failure with physical port channel configuration

Products

• VMware vSphere ESXi

Issue/Introduction

This article addresses a scenario where an ESXi host management network becomes unreachable immediately following the configuration of a port channel on upstream physical switch ports. Users may observe that the host is pingable internally but cannot reach the default gateway.

Symptoms:

• ESXi management IP is unreachable via ICMP or Web UI.
• Uplink ports on the vSwitch appear in a "standby" state.
• Packet captures show inbound ARP requests are received, but no outbound ARP responses are transmitted.
• Pings to the default gateway from the ESXi console fail.

Environment

• VMware vSphere ESXi 7.x
• VMware vSphere ESXi 8.x
• Physical switch ports configured as a Static Port Channel/EtherChannel.
• Physical switch ports configured as Access Ports.

Cause

The connectivity failure results from a dual configuration mismatch:

1. Teaming Policy Mismatch: The physical switch expects "Route based on IP hash," but the ESXi port group is set to "Route based on source port ID." This causes ESXi to place uplinks in standby to prevent loops.
2. VLAN Tagging Conflict: The ESXi port group is configured with a VLAN ID (Virtual Switch Tagging), but the physical switch access ports drop tagged traffic.

Resolution

To restore management connectivity, follow these steps:

1. Log in to the ESXi host via the Direct Console User Interface (DCUI) or a standalone host client if accessible.
2. Navigate to Networking > Virtual Switches and select the management vSwitch.
3. Edit the Teaming and failover policy for the Management Network port group:
   • Set Load balancing to "Route based on IP hash."
   • Ensure all physical uplinks are moved to the Active uplinks section.
4. Edit the VLAN ID for the Management Network port group:
   • Change the VLAN ID to None (0) to enable External Switch Tagging (EST), matching the physical access port configuration.
5. Restart the management agents if necessary and verify connectivity to the gateway.

Additional Information

• For further assistance, see Contact Broadcom Support.
• For steps on creating a support case, see Creating and Managing Broadcom Support Cases.