Replace a manually deployed NSX Manager node when cluster is degraded

Products

• VMware NSX

Issue/Introduction

This process explains how to replace an NSX Manager Appliance after upgrade pre-checks have been performed

Applicable versions of NSX: 4.2.x

Manually deployed NSX Manager Appliance is present where DELETE APPLIANCE button is greyed out: 

Environment

VMware NSX

Cause

The NSX Manager Appliance may be faulty or be in an inconsistent state, where replacing it with a fresh OVA may allow for a smoother upgrade experience on the NSX Management cluster

Resolution

Steps to replace a NSX Manager Appliance:

• Confirm if the NSX Manager VM to be redeployed is the orchestrator node:

  • nsxmanager1> get service install-upgrade

  • nsx-mngr> get service install-upgrade
    Service name:      install-upgrade
    Service state:     running
    Enabled on:        #.#.#.#   <<< orchestrator node

• If the node to be replaced is the orchestrator, change the orchestrator to a manager appliance that is not being replaced (NOTE: This command needs to be run from one of the NSX Manager nodes that you are not going to replace/detach.)

  • nsxmanager2> set repository-ip

• Record config settings for node to be replaced

• To find the node UUID of the NSX Manager to be replaced

  • nsxmanager2> get nodes

• Detach the node from the cluster via admin CLI of a node not being replaced

  • nsxmanager2> detach node <UUID>

• Check cluster status to ensure the node has been removed from all cluster services

  • nsxmanager2> get cluster status

• Power off detached node and delete from disk via vSphere UI

• Deploy new NSX Manager Appliance via NSX UI System > Appliances > Add NSX Appliance

  • Deploy NSX Manager Nodes to Form a Cluster from the UI

• Wait for repo_sync to complete after cluster stabilizes in the NSX UI (this process can take some time)

Additional Information

Replacing a faulty NSX-T manager node in a VCF environment

Deploy NSX Manager Nodes to Form a Cluster from the UI