An administrator encountered a failure with one of the NSX Managers in a VCF Fleet. The administrator has successfully re-deployed an NSX Manager…

The scenario describes a common issue after replacing a failed NSX Manager node where the old node's configuration entry persists, causing a "Degraded" cluster status. According to official VMware NSX documentation, the correct procedure to forcibly remove a failed or unrecoverable node from the cluster's configuration is to use the detach node command. This command must be run from the command-line interface (CLI) of a healthy, surviving manager node in the cluster, specifying the UUID of the old, failed node. This action purges the stale record, resolves the inconsistency, and allows the cluster to return to a stable, healthy state.

B. delete node : This is not the correct or documented NSX CLI command for removing a manager node from the cluster. The proper command verb is detach.

C. detach node then delete node : This option is incorrect because it includes the non-standard delete node command. The entire procedure requires only a single detach node command.

D. detach node: This is an incomplete command. The detach node command requires the specific UUID of the node to be removed as a mandatory argument to function correctly.

1. VMware NSX-T Data Center 3.2 Administration Guide

Page 101

Section: "Remove a Failed NSX Manager Node from a Cluster".

The guide explicitly states: "If an NSX Manager node fails and cannot be recovered

remove it from the cluster. From the CLI of a healthy NSX Manager node in the cluster

run the detach node command." This confirms the exact syntax and procedure.

2. VMware NSX 4.1 Administration Guide

Section: "NSX Manager Life Cycle" -> "Remove a Failed NSX Manager Node from a Cluster".

This more recent documentation reiterates the same procedure: "From the CLI of a healthy NSX Manager node in the cluster

run the detach node command to remove the failed node." This shows the command has remained consistent across versions.