NSX Manager shows Disconnected in SDDC Manager with "Failed to get NSX user details" due to DNS IP Mismatch
search cancel

NSX Manager shows Disconnected in SDDC Manager with "Failed to get NSX user details" due to DNS IP Mismatch

book

Article ID: 441719

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

In VMware Cloud Foundation (VCF), the NSX Manager status appears as Disconnected within the SDDC Manager dashboard. Fetching the NSX certificates information or remediating the account passwords (admin/audit) fail with the following error on SDDC UI:

Error: Failed to get NSX user details
Cause: I/O error on GET request for "https://[HOSTNAME]/api/v1/node/users": Connect to [HOSTNAME]:443 [[IP_ADDRESS]] failed: Connection timed out
Reference Token: #####

 

Environment

VMware Cloud Foundation 9.x

Cause

The issue is caused by a misconfiguration in the DNS server. The FQDNs for the NSX VIP and individual NSX Manager nodes are resolving to an incorrect IP range that does not match the actual static IPs configured on the vCenter appliances 

Resolution

To resolve this issue, the DNS records must be updated to align with the actual appliance configuration.

Step 1: Identify and Update DNS Records

  1. Verify the actual IP addresses assigned to the NSX VIP and each NSX Manager node via the vCenter UI for the particular VM.
  2. Update the A Records in the DNS server to reflect these correct IPs.
    • Example: Update NSX VIP from incorrect 192.0.2.1 to correct 192.0.2.2

Step 2: Verify Resolution from SDDC Manager

  1. Log in to the SDDC Manager via SSH as the vcf user.
  2. Use the nslookup command to confirm the FQDNs now resolve to the correct appliance IPs 
    nslookup <NSXNodeFQDN/IP>

Step 3: Remediate Passwords in SDDC Manager

  1. Once DNS resolution is correct, log in to the SDDC Manager UI.
  2. Navigate to Security> Password Management.
  3. Locate the NSX components and select Remediate Password for the admin and audit accounts
  4. The status should return to Connected once the API communication is restored.