
I just wanted to take a moment to write a quick article on some useful commands I use for troubleshooting NSX-T 2.4 By no means is this everything and I will update this article routinly.
If you would like assistance in the below or have general questions about Cloud solutions, VMware, and more, feel free to visit the following URL and I will be able to work directly with you:
https://bit.ly/3qcNxsN
How to find VTEP (Tunnel End Points)
From NSX Manager
#get logical-switch vtep
From ESXi Host to display TEP end point
#esxcfg-vmnic -l
and
#esxcli network ip interface ipv4 get
Other good commands you may use
From ESXi ping between VTEPs to confirm connectivity
#ping ++netstack=vxlan
or if you want a particular destination with a particular size packet
#ping ++netstack=vxlan -s <packet size> -d <Destination IP>
You can also perform a traceroute from the above with one subtle change
#traceroute ++netstack=vxlan
From ESXi Host to display the NSX-T VIBs to confirm they have all uploaded
#esxcli software vib list | grep nsx
From ESXi Host to display your NSX switches & N-VDS
#esxcfg-vswitch -l
From ESXi Host to display vmk interface with a VDS name that matches the name you used when you configured the transport zone and the transport node
#esxcli network ip interface list
NSX Manager to display ARP Table
#get logical-switch arp-table
On NSX to display the MAC table for a specific LS
#get logical-switch mac-table
NSX Manager to display transport node table
#get logical-switch transport-node-table
From NSX Edge to see routes
#get logical-router
#vrf <number of T0>
#get route
From NSX Edge to see BGP Neighbor
#get logical-router
#vrf <number of T0>
#get bgp neighbor
From NSX Manager to see the tunnel between Transport Hosts
#get host-switch tunnels
Summary:
On purpose have I stared with more ESXi host commands to show that even though NSX-T presents an opaque network, you can still turn to ESXi to help troubleshoot issues.