The following procedure describes replacing an NSX Edge transport node in an NSX Edge cluster using the NSX Manager UI. You can replace the Edge transport node regardless of whether it is running or not.

If the Edge node to be replaced is not running, the new Edge node can have the same management IP address and TEP IP address. If the Edge node to be replaced is running, the new Edge node must have a different management IP address and TEP IP address.

Prerequisites

Familiarize yourself with the procedure to install an NSX Edge node, join the Edge node with the management plane, and create an NSX Edge transport node. For more information, see the NSX-T Data Center Installation Guide.

Procedure

  1. If you want the new Edge transport node to have the same configurations as the Edge transport node to be replaced, make the following API call to find the configurations:
    GET https://<nsx-manager-IP>/api/v1/transport-nodes/<tn-id>
  2. Follow the procedures in the NSX-T Data Center Installation guide to install and configure an Edge transport node.
    If you want this Edge transport node to have the same configurations as the Edge transport node to be replaced, use the configurations obtained in step 1.
  3. In NSX Manager, select System > Fabric > Nodes > Edge Clusters.
  4. Select an Edge cluster by clicking the checkbox in the first column.
  5. Click Actions > Replace Edge Cluster Member.
    It is recommended that you place the transport node being replaced in maintenance mode. If the transport node is not running, you can safely ignore this recommendation.
  6. Select the node to be replaced from the dropdown list.
  7. Select the replacement node from the dropdown list.
  8. Click Save.

Results

If you are running an NSX-T version earlier than 3.1.3, after replacing the NSX Edge transport node, you might see the alarm "All BGP/BFD sessions are down." To resolve the issue, follow the workaround instructions in the KB article https://kb.vmware.com/s/article/83983.