Troubleshoot VMware NSX Edge Services Issues

Troubleshoot VPN service issues

There are 3 types of VPN which you can configure on NSX edges:

  • SSL-VPN Plus
  • IPSec VPN
  • L2 VPN

Lets start with troubleshooting IPSec VPN.

To troubleshoot any VPN issues, you should have knowledge of how to configure a VPN service so that you can verify that issue is not because of a mis-configured settings. To review the implementation and configuration of the IPSec VPN service refer to article

To run troubleshooting commands on the ESG where IPSec VPN service is configured, connect to the edge via SSH.

To view full list of commands for ipsec, run command: show service ipsec ? 

ipsec-3.PNG

Check IPSec VPN service status: show service ipsec

ipsec-1

To see IPSec configuration  run command: show config ipsec

ipsec-2

Additionally you can configure the ESG (where IPSec is configured) to forward logs to a centralized syslog server.

ipsec-4

Once syslog server is configured on ESG, you will find following log files forwarded to the syslog server.

You can use tail or cat command to read these log files to debug and troubleshoot issues.

ipsec-5

Also when troubleshooting IPSec issues, you can temporarily set the log level for IPSec VPN to debug to capture more details.

ipsec-6

Troubleshooting SSL-VPN Plus issues

Connect to the NSX edge where SSL-VPN Plus is configured and run following commands to debug and troubleshoot issues.

To see full list of command: show service sslvpn-plus ?

sslv-0

Check the SSL VPN service status: show service sslvpn-plus

sslv-1

Check SSL VPN statistics: show service sslvpn-plus stats

sslv-2

To see the SSL VPN config: show config sslvpn-plus

I have included only a part of my ssl-vpn config

sslv-3

Check if SSL VPN clients are connected: show service sslvpn-plus tunnels

Check SSL VPN sessions: show service sslvpn-plus sessions

Also you can set the logging level at Edge where ssl-vpn plus is configured to gather more info from logs. The highest level details are included when logging level is set to ‘debug’.

You can change from default logging level ‘info’ to debug

sslv-4

Logs for remote windows clients trying to connect to the SSL VPN service are located on the folder %username%\AppData/Local\VMware\vpn. You will find a log file by name svp_client

sslv-5.PNG

 

Troubleshoot DHCP service issues

To effectively troubleshoot DHCP issues, make sure to set logging level to debug for the dhcp service. 

dhcp-1.PNG

SSH to the edge gateway where DHCP is configured and run following commands to debug and troubleshoot issues.

View full list of dhcp commands: show service dhcp ?

dhcp-2

Check DHCP service status: show service dhcp

dhcp-3

Check DHCP lease info: show service dhcp leaseinfo

dhcp-4

Check DHCP configuration: show config dhcp

dhcp-5

If you have made any changes to DHCP pool post initial configuration, don’t forget to restart dhcp services on client machines. 

Troubleshoot DNS Service Issues

To effectively troubleshoot DNS issues, make sure to change logging level for DNS service to debug so as to collect maximum details from the logs.

To change the logging level, select the edge where DNS is configured and navigate to Manage > Settings > Configuration > DNS Configuration and click on change. 

dns-1.PNG

Set Log level to ‘debug’ and hit OK.

dns-2

Connect to the ESG via SSH and run following commands

Check DNS service status: show service dns

dns-4

Check DNS config: show config dns

dns-5

Once you have verified that configuration is correct and yet DNS is not working as expected, you can run command show log and look for any entries related to DNS.

If you have made any changes to DNS and those changes has not been updated to DNS cache and as a result of that, DNS resolution is returning incorrect values, then you can delete the old dns cache by running command: clear service dns cache

Troubleshoot Load Balancer Implementation Issues

To review installation/configuration steps for load balancer, please read this article

I found a very helpful flowchart on VMware website which is very handy during troubleshooting load balancer issues.

LB-Troubleshooting Flowchart.png

Additionally you can login to ESG (via SSH or console) where LB is configured and can run following commands:

List all load balancer commands: show service loadbalancer ?

lb-0.PNG

Check load balancer service state: show service loadbalancer

lb-1

Check load balancer configuration: show config loadbalancer

lb-2

Check health status of members of LB pool: show service loadbalancer pool

lb-4.PNG

You can also check for errors by running command:  show service loadbalancer error

Download Technical Support logs from NSX Edge instances

Edge gateway logs are very helpful when debugging and troubleshooting any Edge service related issues. Also if you have filed a support case with VMware, the GSS team asks for logs from edge gateway.

To pull log from a edge gateway, select the Edge from the list of ‘NSX Edges’ and from Actions tab, click on “Download Tech Support Logs”

edge-logs.PNG

Click on Download button once the log bundle generation is completed.

edge-logs-2.PNG

And that’s it for this post.

I hope you find this post informational. Feel free to share this on social media if it is worth sharing. Be sociable 🙂

Leave a Reply