Although this alarm can be raised due to common reasons, as outlined in the KB article below:
This KB describes a scenario not covered in the article above.
Along with the alarm, the host nsx-syslog.log reported the following:
[nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="mpa-proxy-lib" tid="######" level="INFO"] MPA: Waiting for node uuid in /etc/vmware/nsx/host-cfg.xml. Empty uuid in config.
VMware NSX
Host TN has empty configuration files, hence it will not connect to NSX managers
Manually register the host to the NSX manager by the following CLI command:
#join management-plane <hostname-or-ip-address[:port]> thumbprint <thumbprint> token <token> [node-uuid <uuid>]