During NSX host preparation while applying a VCP profile an ESX host may transition to a disconnected state within vCenter at / around 68%.
Management network connectivity is lost and the ESX host becomes unable via the management interface and the host UI.
In the vCenter VUM server logs, you may see an error similar to the following:
####-##-##T##:##:##.###Z ERROR vmware-vum-server 1383506 [⋮ sub="com.vmware.vcIntegrity.lifecycle.ConfigurationApplyTask" opID="212e3211-df56-4e9d-8562-5d4daad475f8"] [RemediationHandler 2696] Remediation task failed: Error:--> com.vmware.vapi.std.errors.internal_server_error--> Messages:--> ext[com.vmware.nsx.management.nsxt.vcp/9.1.0.0.25262056/nsx/post_host_remediation]com.vmware.nsx.host.apply.issue<Host host-28 failed to remediate. {"module_name":"common-services","error_message":"Some appliance components are not functioning properly.","details":"Component health: MANAGER:UNKNOWN, SEARCH:UNKNOWN, UI:UP, HTTP:UP, NODE_MGMT:UP","error_code":101}. Please check the error on NSX Manager and/or retry the cluster remediate again.>
In the NSX Manager logs, you may see a failure similar to the following:
"failure_message": "Waiting for fabric-node installation failure to be fixed: Failed to get response from NSX-SFHC component.""failure_message": "Heartbeat between NSX management node and host ########-####-####-####-############ is down."
vCenter 9.1
ESX 9.1
This issue has been attributed to a lack of ENA ENA_UENS drivers within the ESX host. By default, Enhanced Data Protection requires these drivers to be available on the target ESX hosts during the profile application.
The two methods to resolve this are as follows:
For additional information on using vSphere Configuration Profiles see vSphere Configuration Profiles.