3V0-25.25: Advanced VMware Cloud Foundation 9.0 NetworkingDemo

By Broadcom · Question Mode

QuestionQ47

Unknown / not found in official Broadcom sources

An administrator experienced a failure of one NSX Manager in a VCF Fleet. The administrator successfully redeployed an NSX Manager from SFTP backups. However, after the failed Manager node is replaced, the new node joins successfully but the cluster status still remains Degraded.

The get cluster status command on the leader continues to display the old UUID with a state of REMOVED.

Which command resolves the issue?

  • A detach node <old-uuid>
  • B delete node <old-uuid>
  • C detach node <new-uuid>
  • D detach node <old-uuid> then delete node <old-uuid>
Explanation

A failed NSX Manager must be detached from the cluster by using its failed node UUID. The detach node <old-uuid> command removes the obsolete cluster-member record; the replacement node has its own UUID and remains joined. Broadcom documents detach node <failed_node_uuid> as the command for removing a failed NSX Manager from a degraded cluster.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!