var/log/nsxapi.log
file indicate issues with DNS:12:49:16.852Z INFO http-nio-127.0.0.1-7440-exec-6 Utils 139026 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-656a-4ebd-b393-############" subcomp="manager" username="admin"] Executing script: /opt/vmware/nsx-common/python/nsx_utils/ip_utils.py -d4 ##-nsx-manager.systems.##.####
12:49:32.393Z INFO http-nio-127.0.0.1-7440-exec-6 Utils 139026 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-656a-4ebd-b393-############" subcomp="manager" username="admin"] getIpv4FromFqdn(): script returned Ipv4: ##.#.#.##
We can observe above that ip_utils.py took 15 seconds to respond
VMware NSX
Problems with DNS configuration can lead to this issue. For example, DNS configuration is pointing to a server that does not exist or is unavailable.
Check the contents of /etc/resolv.conf file in all NSX Managers and ensure that the configured DNS servers are correct, available and in right order.
If you believe you have encountered this issue and need assistance in diagnosing the root cause, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.