NSX Edge - Troubleshooting via CLI

1 minute read

So let us continue down the path of the various commands to help troubleshooting.  We have been down the path of the VXLAN via esxcli, NSX Controller and Logical Switching, the NSX Controller and Logical Routing/Bridging, and using net-vdr.  Now we can move into troubleshooting from the NSX Edge device.

What is a NSX Edge?

NSX Edge provides network edge security and gateway services to isolate your virtualized networks. You can install an NSX Edge either as a logical (distributed) router or as a services gateway.  The NSX Edge logical (distributed) router provides East-West distributed routing with tenant IP address space and data path isolation. Virtual machines or workloads that reside on the same host on different subnets can communicate with one another without having to traverse a traditional routing interface.  The NSX Edge gateway connects isolated, stub networks to shared (uplink) networks by providing common gateway services such as DHCP, VPN, NAT, dynamic routing, and Load Balancing. Common deployments of NSX Edge include in the DMZ, VPN Extranets, and multi-tenant Cloud environments where the NSX Edge creates virtual boundaries for each tenant.

Without further ado, shall we?

So one thing we would want to see would be how many interfaces exist on a particular NSX Edge device.  To do this, you would simply run the following on the NSX Edge: show interface all

As stated before, one way to deploy NSX Edge is in services gateway mode.  Here are some commands you can run to view the status of some of those services:

  • OSPF: show ip ospf
  • DHCP: show service dhcp
  • Loadbalancer: show service loadbalancer

Need to see the configuration of services on the NSX Edge?  Run these:

  • Firewall: show configuration firewall
  • OSPF: show configuration ospf
  • NAT: show configuration nat

Hopefully you find these as a good starting point for your NSX Edge Troubleshooting.  Of course, a lot of this can be done through the GUI but it is ALWAYS a good idea, IMHO, to be conscious of any CLI commands and their use. Hope this helps and see you again next time!

Leave a Comment