CLI to Troubleshoot ESXi Network


esxcli network

esxcli network nic

esxcli network ip connection list -For information corresponding to the Linux netstat command, use the following ESXCLI command 

esxcli network vswitch standard list

esxcli network vswitch standard 

esxcli network vswitch standard policy failover get -v vSwitch0 

VMKernel Interfaces

esxcli network ip interface list -list the VMkernel ports

esxcli network ip interface ipv4 get  -display the interface name, MAC address, and which vSwitch and Portgroup it belongs to. To list the IP address configuration for the VMkernel ports:

Test VMKernel Interfaces Connectivity

esxcli network diag ping -H


Listing  Neighbors

esxcli network ip neighbor list -list established connections

esxcli network ip route ipv4 list  -list the host’s routing table

Troubleshooting Using Netcat

nc -h -help

nc -z 80  -to test connectivity on to port 80

nc -w 1 -z 80-85 -use netcat to test a range of ports on a remote host:

Troubleshooting with ping and vmkping


vmkping -D   -If you use vmkping with the ‘-D’ switch, you can test the host’s IP stack

Troubleshooting SSL  with openssl

openssl s_client -connect  -You can use the open ssl client present on an ESXi host to test connectivity to an ssl port – for example to vCenter or to another host.

Capturing Traffic with tcpdump-uw

tcpdump-uw -i vmk0  -To display packets on the vmkernel interface vmk0, use the tcpdump-uw command with the -i 
tcpdump-uw -i vmk0 -s 1514 -vvv  -To display all of the packets on vmk0 with verbose detail, use the tcpdump-uw command with the -vvv option
tcpdump-uw -i vmk0 -s 1514 tcp  -display only the TCP packets on vmk0, use the tcp option with the tcpdump-uw command
tcpdump-uw -i vmk0 -s 1514 port not 22 and port not 53  -To avoid seeing unwanted traffic types in the tcpdump-uw output, use the not option. For example, to filter out DNS and SSH traffic, use the following command
tcpdump-uw -i vmk0 -s 1514 -C 100M -w /var/tmp/test.pcap  -If the trace is running for long time, you can split the trace pcap file to chunks of desired size using the-C option.

Please Comment and Subscribe

 661 total views,  12 views today

2 thoughts on “CLI to Troubleshoot ESXi Network

  1. Good day! Would you mind if I share your blog with my facebook group? There’s a lot of folks that I think would really appreciate your content. Please let me know. Cheers

Comments are closed.