Unable to add an NVDS / editing edge VM network interface on edge nodes

Products

• VMware NSX

Issue/Introduction

Symptoms:

GUI will report error "PNIC and device configurations do not match. Unconfigured DPDK fastpath interfaces fp-eth1 is used for connecting uplink device. Please provide portgroup connection for this interface." while adding NVDS to edge nodes. 

• Edge placement config at NSX Manager may not reflect current name, networks and placement configuration of the edge VM at the compute manager.
• Dialog to select DV Portgroups or segments will not be available while adding a new host switch or editing an existing switch.

Relevant log location:

/var/log/syslog

2020-09-08T01:00:50.158Z testedge01 NSX 6313 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP15519" level="ERROR" reqId="31f4d619-4942-47a3-a269-8b9d9ccc5b20" subcomp="manager" username="xxxxxx"] [entId=b238aa6a-xxxx-xxxx-xxxx-xxxxxxxx] PNIC and device configurations do not match. Unconfigured DPDK fastpath interfaces fp-eth1 is used for connecting uplink device. Please provide portgroup connection for this interface.

/var/log/nsxapi.log

2020-09-08T01:00:50.158Z ERROR http-nio-127.0.0.1-7440-exec-65 EdgeNodeAdapterImpl - FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP15519" level="ERROR" reqId="31f4d619-4942-47a3-a269-8b9d9ccc5b20" subcomp="manager" username="xxxxxx"] [entId=b238aa6a-xxxx-xxxx-xxxx-xxxxxxxx] PNIC and device configurations do not match. Unconfigured DPDK fastpath interfaces fp-eth1 is used for connecting uplink device. Please provide portgroup connection for this interface.

 

Environment

VMware NSX-T Data Center 2.x
VMware NSX-T Data Center

Cause

The ESXi host where the edge vm is located is moved from one cluster to another cluster OR the MoRef id of the ESXi host got changed because of ESXi host was removed from vSphere inventory and added back.

Resolution

This is a known issue affecting NSX-T Data Center

In 3.0.x and later, a scheduled job will refresh the placement config of Edge VM from vSphere.

Workaround:

1. Verify existing vSphere deployment parameters using API:
GET https://<NSX-IP>/api/v1/transport-nodes/<Edge transport node ID>

2. Refresh the Edge Transport Node state with this API:  (this query will update Edge Transport node with latest state from vSphere)
POST https://<NSX-IP>/api/v1/transport-nodes/<Edge transport node ID>?action=refresh_node_configuration&resource_type=EdgeNode

3. Verify the latest vSphere deployment parameters using API: (This API will refresh the vm_deployment_config [management_network_id, compute_id, host_id, storage_id, and data_network_ids])
GET https://<NSX-IP>/api/v1/transport-nodes/<Edge transport node ID>

4. If we see the vm_deployment_config reference is modified and is latest after step 3 do following steps from NSX UI:
a. Navigate to Fabric > Nodes > Edge Transport Nodes page.
b. Select above Edge Transport Node and click Edit.
c. Go to 'N-VDS' tab and click a network in the Teaming Policy Uplink Mapping section of a Switch. This should launch a dialog to select a DV Portgroup or Segment.

d. Select the desired network and click on Save.