Symptoms:
- In System - Fabric - Transport Nodes - Edge Nodes, when you attempt to edit the Edge node, you are presented with the following alert:
"Transport node refresh failed: [Fabric] Refresh edge <edge uuid> placement configuration failed. Check network connectivity of the edge node"
- And when tried to sync the edge node configuration, we see the error as:
" Failed to refresh the transport node configuration:[fabric] refresh edge<edge uuid> placement configuration failed. check network connectivity of the edge node.
- The vCenter (Compute Manager) which this Edge node was deployed to, no longer exists as a Compute Manager in NSX-T.
- In the NSX-T manager log /var/log/proton/nsxapi.log we see ERROR:
ERROR task-scheduler-1 EdgeNodeFabricUtils 23929 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP16047" level="ERROR" subcomp="manager"] An error occurred when refreshing edge VM placement config ########-23d7-423b-a5be-############. Exception null Error java.lang.NullPointerException
at com.vmware.nsx.management.inventory.service.CmInventoryService.buildErrorInfoFromCmStatus(CmInventoryService.java:1276)
...
- In the NSX-T manager log /var/log/syslog.log we see the following ERROR:
nsx-mgr-01 NSX 24212 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'admin' ModuleName:'common-services' Operation:'GET@/api/v1/fabric/compute-managers/########-6845-4514-ab42-############' Operation status: 'failure' Error: The requested object : ComputeManagerModel/########-4514-ab42-############ could not be found. Object identifiers are case sensitive.
- The vCenter (Compute Manager) in which this Edge node was deployed on, no longer exists as a Compute Manager in NSX-T or the edge was moved to another Compute Manager.
- Using the API: GET https://<nsx-manager-ip>/api/v1/transport-nodes/{edge-node-uuid} to check the deployment config, in the output file the field "vc-id" (vCenter-id) indicated will be different than the actual "vc-id" (vCenter-id) on which edge node vm currently resides