Refresh API for Edge VM deployed using NSX-T Manager hits error: Refresh edge null placement configuration failed. Check network connectivity of the edge node

Products

• VMware NSX

Issue/Introduction

• For Edge nodes deployed using NSX Manager, if there are changes to Edge VM external to NSX Manager such that the VM MoRef in vSphere changes, the Edge deployment config in NSX Manager may have discrepancies as compared to the current Edge VM config in the Compute Manager.
• For example, if the VM is removed from vSphere inventory and subsequently added back:
  • Edge placement config in NSX Manager may not reflect current name, networks and placement configuration of the edge VM in Compute Manager.
  • Using NSX Manager, update of Edge VM networks and name might fail.
  • Refresh job that syncs VM info from Compute Manager might fail.
• Following log line is seen in var/log/proton/localhost_access_log.txt:

POST /nsxapi/api/v1/transport-nodes/af9a####-####-####-####-########4f97?action=refresh_node_configuration&resource_type=EdgeNode HTTP/1.1" 400 224 4448 4448

• Following log lines are seen in /var/log/proton/nsxapi.log:

INFO http-nio-127.0.0.1-7440-exec-16 AuditingServiceImpl - FABRIC [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="f063####-####-####-####-########db4a" subcomp="manager" username="admin"] UserName="admin", ModuleName="TransportNodeLcm", Operation="RefreshTransportNode", Operation status="failure", New value=["af9a####-####-####-####-########4f97"]

INFO http-nio-127.0.0.1-7440-exec-16 NsxBaseRestController - - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Error in API /nsxapi/api/v1/transport-nodes/af9a####-####-####-####-########4f97?action=refresh_node_configuration&resource_type=EdgeNode caused by exception com.vmware.nsx.management.edge.common.exceptions.EdgeException: {"moduleName":"FABRIC","errorCode":16047,"errorMessage":"[Fabric] Refresh edge null placement configuration failed. Check network connectivity of the edge node."}

Environment

VMware NSX

Cause

After removing Edge VM from vCenter Server and adding it back, its MoRef changes because of which getVMConfig returns 'null'.

Resolution

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


Workaround:

• Auto-deploy and configure a new Edge VM.
• Use 'Replace edge cluster member' workflow to move all logical config to the new Edge VM.
• Delete the previous Edge VM from VC and NSX manually.
  
  

Additional Information

In this state, Edge VM lifecycle management operations like updates and reporting current state activity are impacted. Edge routing continues to function.

Related KB:

Editing an VMware NSX-T Data Center Edge Node results in: Transport node refresh failed