This check was introduced to VMware NSX-T 3.2.1 to compare the Edge VM details in the NSX inventory and the vCenter (VC) inventory. There are 3 scenarios where this error can be presented:
- The Edge VM is present in VC with a different moref id:
- This can happen when the Edge VM is removed from the VC inventory and added back. When added back, the VM will obtain a new moref id from VC, however this will differ from the id in the NSX database. To confirm, use the VC MOB (managed object browser) via the URL https://hostname.yourcompany.com/mob and confirm if the VM moref id is different from the id shown in NSX alarm description.
- The Edge VM is no longer present in vCenter:
- In this instance the Edge VM has been deleted from the VC, so the referenced VM in the NSX database cannot be found.
- Connectivity between the Edge and NSX manager was lost:
- In certain scenarios whereby there is a loss of communication between the NSX Manager and the Edge this alarm is thrown however the periodic refresh task is skipped, so this alarm is not cleared. This can be confirmed from the NSX manager logs in var/log/proton/nsxapi.log by searching for the below error:
nsxapi.log:2022-06-27T17:21:15.160Z INFO l3-tasks1 EdgeNodeRefreshTask #### FABRIC [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] EdgeNodeRefreshTask has started
nsxapi.log:2022-06-27T17:21:15.166Z INFO l3-tasks1 EdgeNodeRefreshTask #### FABRIC [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] Edge node /infra/sites/default/enforcement-points/default/edge-transport-node/########-####-####-####-############ is having reconfiguration errors {VM_PLACEMENT_REFRESH_FAILED=[Fabric] Refresh edge /infra/sites/default/enforcement-points/default/edge-transport-node/########-####-####-####-############ placement configuration failed. Check network connectivity of the edge node.} so skipping refresh activity
NOTE: The preceding log excerpts are only examples. Date, time and environmental variables may vary depending on your environment.