VMware ESXi Network Troubleshooting Checklist

Introduction

Network issues on VMware ESXi hosts can bring down entire clusters of virtual machines, disrupt vMotion migrations, and cripple storage connectivity. Troubleshooting ESXi networking requires understanding both the virtual switching layer inside the hypervisor and the physical network infrastructure it connects to.

This guide provides a structured troubleshooting methodology for the most common ESXi networking problems you will encounter, complete with the CLI commands and diagnostic steps needed to isolate and resolve each issue. Whether you are a VMware admin, a network engineer, or a sysadmin who manages both, this checklist will help you get to root cause faster.

Troubleshooting Methodology

Before diving into specific issues, follow this general approach for any ESXi networking problem:

1. Define the scope: Is the issue affecting one VM, all VMs on a host, all VMs on a port group, or the entire host?
2. Check the physical layer first: NIC link status, speed/duplex, cable faults
3. Check the virtual layer: vSwitch/VDS configuration, port group settings, VLAN assignments
4. Verify end-to-end: vmkping, packet captures, firewall rules
5. Check recent changes: Was anything modified on the ESXi host, vCenter, or physical switches?

Problem 1: ESXi Host Has Lost Network Connectivity

Symptoms

• Host shows as “Disconnected” or “Not Responding” in vCenter
• Cannot SSH to the ESXi host
• VMs on the host have lost all network connectivity

Diagnostic Steps

Problem 2: VMs Cannot Communicate Across VLANs

Symptoms

• VMs on the same port group can ping each other
• VMs cannot reach the default gateway or VMs on other VLANs
• Traffic seems to stay local to the ESXi host

Diagnostic Steps

Problem 3: Intermittent Packet Loss or Slow Performance

Symptoms

• VMs experience intermittent connectivity issues
• Application performance is degraded
• Pings show variable latency or packet loss

Diagnostic Steps

Problem 4: vMotion Fails

Symptoms

• vMotion migration fails with a timeout or network error
• vMotion is extremely slow (minutes for a small VM)
• vCenter reports “migration exceeded maximum switchover time”

Diagnostic Steps

Problem 5: Storage Network Issues (NFS/iSCSI)

Symptoms

• Datastores show as inaccessible
• VMs experience high disk latency
• APD (All Paths Down) or PDL (Permanent Device Loss) events in logs

Diagnostic Steps

Problem 6: VM Network Adapter Issues

Quick Checks

# Check VM's network adapter from ESXi CLI
vim-cmd vmsvc/getallvms
# Get the VM ID, then:
vim-cmd vmsvc/device.getdevices [vmid] | grep -A5 "Network"

# Verify the VM is connected to the correct port group
esxcli network vm list
esxcli network vm port list -w [world-id]

# Check if the VM port group exists
esxcli network vswitch standard portgroup list

Common VM-Level Fixes

• VM NIC disconnected: The “Connected” checkbox in VM settings is unchecked. Edit VM settings and check the “Connected” box
• Wrong port group: The VM is connected to the wrong port group (wrong VLAN). Change the port group assignment in VM settings
• E1000 adapter instead of VMXNET3: Older VMs may have the legacy E1000 adapter. Change to VMXNET3 for better performance (requires VMware Tools and a brief network interruption)
• Guest OS firewall: The guest OS (Windows Firewall, iptables) is blocking traffic. Check guest firewall rules
• Stale MAC address in physical switch CAM table After a vMotion, the physical switch may still have the old host’s port in its MAC address table. Fix: Wait for MAC aging (default 300 seconds) or clear the MAC table entry on the switch: `clear mac address-table dynamic address [mac-addr]`

Essential ESXi Networking Commands Cheat Sheet

Conclusion

ESXi network troubleshooting comes down to methodically working through the layers — physical NIC status, virtual switch configuration, VLAN alignment with the physical network, and end-to-end connectivity verification. The `esxcli` commands and `pktcap-uw` packet capture tool give you the same level of visibility into the virtual network that you have on physical switches. Combined with checking the physical switch side, you can isolate most networking issues to a specific layer and fix them quickly.