Error: java.net.UnknownHostException during NSX Manager deployment in VMware NSX

Products

• VMware NSX

Issue/Introduction

Symptoms:

• NSX Manager deployment fails or hangs at 70%.
• The following error appears in logs or the UI: Connection error for nsx manager https://sdkTunnel:8089/sdk/vimService invocation failed with "java.net.UnknownHostException: <vCenter_FQDN>".
• Compute Manager status shows as DOWN in the NSX UI.
• cm-inventory service may appear as down or flapping.

Environment

VMware NSX 4.x

Cause

The NSX Manager cannot resolve the vCenter Server FQDN via DNS. This prevents the SDK tunnel from establishing a connection to port 8089 for management tasks, including cluster joining and legacy node removal.

Resolution

To resolve this issue, ensure the NSX Manager can resolve the vCenter FQDN or use the manual deployment workaround below:

Method 1: Correct DNS Configuration

1. Log in to the NSX Manager CLI as admin.
2. Verify resolution using nslookup <vCenter_FQDN>.
3. Check configured name servers using get name-servers.
4. If incorrect, update the name servers: set name-servers <DNS_IP>.
5. Verify the Compute Manager connection in the NSX UI.

Method 2: Manual OVF Deployment (Workaround)

1. Download NSX Manager OVA from Broadcom Portal. Download Broadcom Products
2. Manually deploy the OVF directly in vCenter on the target cluster.
3. Power on the VM and log in to the CLI.
4. Once the VM is powered on, log in to the CLI and use the join command to manually add the node to the cluster. Form an NSX Manager Cluster Using the CLI
   nsx-manager> join <Manager-IP> cluster-id <Cluster-ID> username admin password <Password> thumbprint <Thumbprint>
5. Perform a Delete Appliance from the NSX UI and Force Delete of any legacy managers that fail to remove through the UI.

Additional Information

For steps on changing NSX Manager IPs, see Change the IP Address of an NSX Manager .