NSX-T Troubleshooting

This page is something I created during the series, mainly because I saw mistakes during the deployment or limitations I knew from deploying that I had to fix afterwards. I will try to split it up a bit into a section first for installation and configuration, which is intended for the initial state of deploying NSX-T. Later on I will no doubt add other sections for issue that I find and categorize that way.

A great help has been the CLI guide although the version I found is only for 2.3.

Also what I found very good is that the CLI works a lot like the cisco CLI you write a command like get and it lists all the possibilities:


You write a command like get cluster ? and it shows you the options you have with that command.


Anyway, on to the couple of topics I found so far. This document is intentionally kept a bit in draft mode because I am sure there will be other troubleshooting points added to it later.

The CLI seems very strong and powerful and should please network engineers with its simplicity.

Installation and configuration

1: When installing the original NSX-T Manager I only added one NTP Server. Since I tend to use two, I wanted to add the second. It is a really simple step from the CLI.

Use get ntp-server to get a list of current ntp servers in use.

Use set ntp-server <IP> to set the new NTP server, then run get ntp-server again to verify that the second server is added.


2: Like above in point two, this I also forgot to add the second DNS server. Again it’s super simple to fix from the CLI.

Use get name-server to get the current name servers in use.

Use set name-server <IP> to set the Name server. Verify your work by re-running get-name-server


3: FQDN is not shown on all nodes.

I was doing the cluster deployment and while getting the cluster status I saw that the FQDN was actually only enabled on one node. It did not seem to have an impact directly but none the less it’s a good idea to enable it on all nodes.


To correct this you need to do the following: