This issue is resolved in VMware vCenter Server 6.5, available at
VMware Downloads.
Note: Otherwise, a database maintenance is required , please file a support request with VMware Support and quote this Knowledge Base article ID (52550) in the problem description. For more information, see
How to Submit a Support Request.
Workaround:
To work around this issue:
- Depending on the severity of the situation, restart of EAM might resolve agents missing from EAM runtime.
- A preventative workaround would be to add host to non-NSX prepared cluster prior to moving to NSX Cluster. (Avoid moving standalone host to NSX Prepared cluster)
- There is a VPXD parent ID assigned to host while it is standalone, this is not the case while host is part of a cluster. The software defect is related to the VPXD parent ID and mechanism of removal while transitioning to NSX prepared cluster.