Editing an Edge Node results in Error: Transport node refresh failed
search cancel

Editing an Edge Node results in Error: Transport node refresh failed

book

Article ID: 322405

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • 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
  • When trying 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.
  • 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-############. 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 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/########-####-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) on which this Edge node was deployed on, no longer exists as a Compute Manager in NSX-T or the Edge VM 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, the field "vc-id" (vCenter-id) indicated will be different than the actual "vc-id" (vCenter-id) on which Edge node VM currently resides.

Environment

VMware NSX-T Data Center

VMware NSX

Cause

This issue occurs when a Compute Manager was removed or the Edge VM was moved to another Compute Manager. NSX Manager still thinks that the Edge node is deployed on the removed CM or the CM where it was originally deployed on.

Resolution

This is a known issue affecting NSX and currently there is no resolution. 

Workaround:

Deploy a new Edge node on the correct CM and replace it with the Edge node that has this issue.

Additional Information

Powered by Wolken Software