An administrator encountered a failure with one of the NSX Managers in a VCF Fleet. The administrator has successfully re-deployed an NSX Manager from SFTP backups. However, after replacing the…

Question

Options

• Adetach node <new-uuid>
• Bdelete node <old-uuid>
• Cdetach node <old-uuid> then delete node <old-uuid>
• Ddetach node <old-uuid>

• A
  2% (1)
• B
  11% (6)
• C
  6% (3)
• D
  81% (44)

Explanation

In a VMware Cloud Foundation (VCF) environment, the NSX Management Cluster consists of three nodes to ensure high availability and quorum. When a single node fails and is subsequently replaced--either through a manual deployment or an orchestrated recovery via SDDC Manager-- the internal database (Corfu) and the cluster manager must be updated to reflect the current members of the cluster. When a node is lost or manually deleted from vCenter without being properly decommissioned through the NSX API or CLI, the remaining "Leader" node retains the metadata and the UUID of that missing member. Even after a new node joins the cluster and synchronizes data, the cluster state often remains in a "Degraded" status because the control plane still expects a response from the original, failed UUID. According to NSX troubleshooting and recovery guides, the specific command to purge a stale or defunct member from the cluster configuration is detach node <UUID>. This command must be executed from the CLI of the current Cluster Leader. By running detach node <old-uuid>, the administrator instructs the cluster manager to permanently remove the record of the failed node from the management plane's membership list.

No community discussion yet for this question.