Principles
- Verify network configuration
- Verify a given virtual machine is configured with the correct network resources
- Troubleshoot virtual switch and port group configuration issues
- Troubleshoot physical network adapter configuration issues
- Determine the root cause of a network issue based on troubleshooting information
References
- vSphere Networking Guide
http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-networking-guide.pdf
- vSphere Command Line Interface Concepts and Examples
https://vdc-download.vmware.com/vmwb-repository/dcr-public/0a40d9c5-4d4b-490d-8efa-e373a0ff2109/43a3c005-3878-4e05-8b60-35aca804d61d/vsphere-esxi-vcenter-server-65-command-line-interface-concepts-examples-guide.pdf
- vSphere Troubleshooting Guide
http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-troubleshooting-guide.pdf
Verify network configuration
- Verify physical network has MTU >= 1600
- Check correct (and common) teaming policy is applied NSX enabled vDS:
- “Route Based on Originating Port” is recommended unless a vPC/MLAG is configured
- “Route based in IP Hash (Static Etherchannel)” is recommended for vPC uplinks
- Check VXLAN connectivity: vmkping ++netstack=vxlan -d -s <packet size> <vmknic IP> (set packet size >= 1572)
- If using hybrid mode, ensure an IGMP Querier is configured on the Transport Network
- Check all hosts resolve in DNS
- List vmk interfaces on a host: esxcli network ip interface ipv4 get
- Get vmk interface details: esxcli network ip interface list