NSX Manager Manual Deployment and Cluster Join without Compute Manager

Products

• VMware NSX

Issue/Introduction

• An NSX Manager node within the management cluster has entered an unrecoverable state and requires replacement. Because the Compute Manager (vCenter Server) is not configured or integrated with the environment where the NSX Manager appliances are deployed, automated node deployment via the NSX UI is unavailable. To restore the management cluster to a healthy, three-node quorum, a manual appliance OVA deployment followed by a CLI-driven cluster join procedure must be executed.

Environment

• VMware NSX-T Data Center
• VMware NSX
• VMware vCenter Server

Cause

Automated deployment of NSX Manager nodes requires an active connection to a Compute Manager to orchestrate the OVF deployment and configuration. If a Compute Manager is not configured, or if there is a communication failure between NSX and vCenter, the UI-based deployment cannot proceed.

Resolution

To resolve this issue, you must manually deploy the NSX Manager appliance and join it to the cluster using the Command Line Interface (CLI).

Prerequisites

• The OVF/OVA file for the exact same version of the existing NSX Manager(s).
• Administrative access to the existing NSX Manager(s) CLI and the new appliance CLI.
• The Cluster ID and Thumbprint of the existing cluster.

Procedure

1. Manually Deploy the Appliance

   • Log in to the vSphere Client.
   • Deploy the NSX Manager OVA/OVF. Ensure the management IP, gateway, and DNS match the intended network configuration.
   • Power on the new appliance and wait for all services to start.

2. Retrieve Cluster Information from a Healthy Node

   • SSH into one of the existing, healthy NSX Managers as the admin user.
   • Run the following command to retrieve the cluster ID and thumbprint:
      

     get cluster config

   • Note the Cluster ID and the API Thumbprint.

3. Join the New Node to the Cluster

   • SSH into the newly deployed NSX Manager.
   • Execute the join command using the details retrieved in Step 2:
      

     join <Existing-Manager-IP> cluster-id <Cluster-ID> username admin password <Admin-Password> thumbprint <API-Thumbprint>

   • Confirm the prompt to proceed.

4. Verify Cluster Health

   • From any node in the cluster, check the status:
      

     get cluster status

   • Verify that all members show a status of UP and the cluster connectivity is STABLE.

Additional Notes:

• If replacing a failed node, ensure the old node is removed from the configuration first using the detach node <Node-ID> command on a healthy member.
• Refer to the VMware NSX Installation Guide for specific OVF parameter requirements.