This is a known issue affecting VMware NSX-T 3.x.
Currently, there is no resolution.
Workaround:
To work around this issue, use one of these options:
Option -1 -
If Remediation has already started/failed
- After the 70 min timeout, the Remediation will fail. Manually check Compliance of the Cluster. Check if the status of ESX is Compliant (The status of ESX will change from "Remediation Failed" to "Compliant").
- Manually re-apply TNP from NSX Manager to the ESX. Service VM Deployment will also start for the ESX automatically.
Option - 2 - Avoid the 70-minute timeout by putting ESX in Maintenance Mode before Remediating it
- Place the newly added ESX into Maintenance Mode.
- Remediate the ESX using vLCM.
- The Remediation will still fail at 95% but this time, the failure will happen without any timeout.
- Manually take the ESX out of Maintenance Mode after the Remediation fails.
- Manually check Compliance of the Cluster. You will find that the ESX is Compliant (The status of ESX will change from "Remediation Failed" to "Compliant").
- Manually re-apply TNP from NSX Manager to the ESX. Service VM Deployment will also start for the ESX automatically.