Troubleshooting Virtual Machine Connectivity Issues Caused by Physical Network Infrastructure (VMware vSphere ESXi)

Products

• VMware vSphere ESXi

Issue/Introduction

 This article provides instructions for troubleshooting virtual machine (VM) connectivity issues that are isolated to specific ESXi hosts. When VMs on a particular host exhibit ping failures while VMs on other hosts on the same segment remain reachable, the issue may originate from the physical network infrastructure rather than the host configuration.

Environment

• VMware vSphere ESXi 8.0, 7.0

Cause

Connectivity issues occurring on specific hosts while others remain functional are often caused by external physical network path failures, such as:

• Switch port misconfiguration or disabled ports.
• Incorrect VLAN tagging on physical switch interfaces.
• Spanning Tree Protocol (STP) blocking or port channel mismatches.
• ACLs or firewall rules blocking traffic to specific physical ports.

Resolution

Follow these steps sequentially to isolate and resolve physical network path failures.

1. Isolate the Impact: Verify if the issue is host-specific by migrating an affected VM to a known-functional ESXi host. If the VM regains connectivity on the new host, the issue is confirmed to be local to the original host's physical network path.

2. Comparative Packet Capture Analysis: Perform packet captures on the physical uplink (vmnic) of the problematic ESXi host versus a functional host to observe traffic flow.

   • Use the pktcap-uw utility on the ESXi host. For detailed usage, refer to: Capture and Trace Network Packets by Using the pktcap-uw Utility.
   • Compare the captures: If the functional host shows successful ICMP request/reply exchanges, but the problematic host shows no incoming ICMP requests, the physical path is dropping the traffic.

3. Physical Network Audit: Engage your physical network team to audit the switch port configuration associated with the problematic ESXi host.

   • Verify the port is active and configured in the correct VLAN/Trunk group.
   • Ensure there are no MAC address flaps, STP topology changes, or port-channel mismatches for the specific physical uplink connected to the host.

4. Validate Resolution: Once corrective actions are applied by the physical network team, repeat the packet capture on the ESXi host's vmnic. The resolution is successful when ICMP traffic is visible and the VM is reachable.