NSX – Troubleshooting deployment of distributed Logical Routers and Edge Gateways – esxi hosts

Command line troubleshooting skills are invaluable when trying to diagnose problems. In this post I’ve collected some useful commands and a basic troubleshooting methodology for errors affecting the deployment of distributed Logical Routers and Edge Gateways

This assumes the nsx manager and controllers have been deployed


1. First check esx hosts have been prepared and configured with vteps



2. Check that esx hosts are added to the transport zone




3. Check VTEP is available on esx host

(here is my vtep ip, and vmk3 is the vmkernel interface)

If you don’t see your vtep be sure you have added the host to the transport zone…

<esx host># esxcli network ip route ipv4 list -N vxlan
 Network        Netmask        Gateway        Interface  Source
 -------------  -------------  -------------  ---------  ------
 default  vmk3       MANUAL        vmk3       MANUAL

4. Check esx host VTEP connectivity, the MTU, note the mac etc

<esx host> # esxcfg-vmknic -l
 Interface  Port Group/DVPort/Opaque Network        IP Family IP Address            Netmask         Broadcast       MAC Address       MTU     TSO MSS   Enabled Type                NetStack
 vmk0       38                                      IPv4 00:50:56:b2:09:10 1500    65535     true    STATIC              defaultTcpipStack
 vmk1       11                                      IPv4 00:50:56:6a:8a:62 1500    65535     true    STATIC              defaultTcpipStack
 vmk2       17                                      IPv4 00:50:56:6f:18:28 1500    65535     true    STATIC              defaultTcpipStack
 vmk3       50                                      IPv4 00:50:56:69:b3:cd 1600    65535     true    STATIC              vxlan



5. Ping other vteps in the enviroment from the esx host

ping ++netstack=vxlan -I vmk3 < another hosts vtep ip >
<esx host> # ping ++netstack=vxlan -I vmk3
 PING ( 56 data bytes
 64 bytes from icmp_seq=0 ttl=64 time=2.638 ms
 64 bytes from icmp_seq=1 ttl=64 time=1.054 ms
 Check controller is connected to the ESXi host.
 # cat /etc/vmware/netcpa/config-by-vsm.xml

5. Check on esx host if the controllers are registered in netcpa

In the example the controllers are,,

<esx host> # cat /etc/vmware/netcpa/config-by-vsm.xml
 <connection id="0000">
 <connection id="0001">
 <connection id="0002">
 <vdrDvs id="0000">
 <uuid>24 aa 2d 50 e3 17 ca 58-74 c7 06 f5 e5 74 f8 7b</uuid>

6. Check esx host vxlan status

Control plane should be in synch, and segment info, vtep ip should be clear.

# net-vdl2 -l
 VXLAN Global States:
 Control plane Out-Of-Sync:      No
 UDP port:       8472
 VXLAN VDS:      vDS-Branch
 VDS ID: 24 aa 2d 50 e3 17 ca 58-74 c7 06 f5 e5 74 f8 7b
 MTU:    1600
 Segment ID:
 Gateway IP:
 Gateway MAC:    00:50:56:b2:02:1d
 Vmknic count:   1
 VXLAN vmknic:   vmk3
 VDS port ID:    50
 Switch port ID: 33554439
 Endpoint ID:    0
 VLAN ID:        0
 Segment ID:
 IP acquire timeout:     0
 Multicast group count:  0
Restart the netcpa service and looks at the logs if the connection isn't registered
etc/init.d/netcpad restart
 cat /var/log/netcpa.log | grep connection



Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.