This is a known issue affecting VMware NSX for vSphere 6.3.6.
Currently, there is no resolution.
Workaround:
To work around this issue, use a synchronize API on the NSX Manager to force an update of communication channel credentials between NSX Manager and the failed host.
For example:
https://NSXMGR_IP/api/2.0/nwfabric/configure?action=synchronize
<nwFabricFeatureConfig>
<featureId>com.vmware.vshield.vsm.messagingInfra</featureId>
<resourceConfig>
<resourceId>host-52</resourceId>
</resourceConfig>
</nwFabricFeatureConfig>