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:
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.
The issue outlined in scenario 3 is resolved in NSX-T 3.2.2 and NSX 4.1 available at Broadcom Downloads.
To workaround each scenario, please use the below API calls: