This issue is resolved in VMware NSX-T Data Center 3.1.3, available at Broadcom downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.
Select the applicable solution based on the Cluster's Backing (NVDS/CVDS/vLCM).
NVDS-backed Cluster
Removing an ESXi host
- Put the ESXi host in Maintenance Mode.
- Move the ESXi host to the Datacenter.
- Exit Maintenance Mode for the ESXi host in Datacenter and wait for SVM to get deleted (You can see the Deletion Task on vCenter Server UI). Service Deployment status should be Up after this.
- Put the ESXi host in Maintenance Mode.
- Delete the vmkernel adapters on ESXi host that are connected to any VDS.
- Remove the ESXi host from above VDS.
- On the ESXi host, Uninstall NSX using this command:
nsxcli -c del nsx
For more information, see the article: Uninstall NSX-T Data Center from a vSphere Cluster. Note: After some time, the TN state is shown as "Disconnected" on the NSX UI.
- Force Delete TN from NSX.
- On the vCenter Server, disconnect the ESXi host and then remove from the inventory.
Adding an ESXi host
- Add the ESXi host to the Datacenter.
- Add the ESXi host under the necessary VDS Networks.
- Move the ESXi host to the Cluster.
- Exit Maintenance Mode for the ESXi host. The SVM will be deployed on the ESXi host and the Service Deployment status would turn Up after a successful deployment.
CVDS-backed Cluster
Removing an ESXi host
- Put the ESXi host in Maintenance Mode.
- Move the ESXi host to the Datacenter.
- Exit Maintenance Mode for the ESXi host in Datacenter and wait for SVM to get deleted (You can see the Deletion Task on VC UI). Service Deployment status should be Up after this.
- Put the ESXi host in Maintenance Mode.
- Delete the vmkernel adapters on ESXi host that are connected to any VDS.
- Remove the ESXi host from above VDS.
- On the ESXi host, Uninstall NSX using this command:
nsxcli -c del nsx
For more information, see the article: Uninstall NSX-T Data Center from a vSphere Cluster.
- After the above CLI finishes successfully, remove the ESXi host from the CVDS network. After some time, the TN state is shown as "Disconnected" on the NSX UI.
- Force Delete TN from NSX.
- On the vCenter Server, Disconnect the ESXi host and then remove from the inventory.
Adding an ESXi host
- Add the ESXi host to the Datacenter.
- Add the ESXi host under the necessary VDS Networks (optional).
- Add the ESXi host under CVDS Network and configure Physical Adapter for the CVDS connection.
- Move the ESXi host to the Cluster where the Hostbased SI is deployed. TNP will be applied to the ESXi (can check on NSX UI). Once TNP Apply passes, proceed to the next step.
- Exit Maintenance Mode for the ESXi host. SVM will be deployed for the ESX and the Service Deployment status would turn Up after successful deployment.
vLCM-backed Cluster
Removing an ESXi host
- Put the ESXi host in Maintenance Mode.
- Move the ESXi host to the Datacenter.
- Exit Maintenance Mode for the ESXi host in Datacenter and wait for SVM to get deleted (Can see the Deletion Task on VC UI). Service Deployment status should be Up after this.
- Put the ESXi host in Maintenance Mode.
- Delete the vmkernel adapters on ESXi host that are connected to any VDS.
- Remove the ESXi host from above VDS.
- On the ESXi host, Uninstall NSX using this command:
nsxcli -c del nsx
For more information, see the article: Uninstall NSX-T Data Center from a vSphere Cluster.
- After the above CLI finishes successfully, remove the ESXi host from the CVDS network. After some time, the TN state is shown as “Disconnected” on the NSX UI.
- Force Delete TN from NSX.
- On the vCenter Server, Disconnect the ESXi host and then remove from the inventory.
Adding an ESXi host
- Add the ESXi host to the Datacenter.
- Add the ESXi host under the necessary VDS Networks (optional).
- Add the ESXi host under CVDS Network and configure Physical Adapter for the CVDS connection.
- Move the ESXi host to the Cluster where Hostbased SI is deployed:
a. Here, TNP Configuration starts for the ESX automatically and gets stuck during the step "vLCM Remediation Initiated" due to EAM Health Check and then fails after ~15 minutes.
b. After the above failure, vLCM Compliance check is run automatically and it shows that the ESXi is compliant.
- Exit Maintenance Mode for the ESXi host.
- Re-Apply TNP from NSX UI (Click on the Error Displayed for TN and Resolving it would Re-Apply the TNP to the ESXi). The TNP Re-Apply would succeed shortly. Also, SVM Deployment for the ESX will be done and Service Deployment Status will be Up.