NSX-T Edge node failing to deploy with error "Invalid configuration for device '0'"
search cancel

NSX-T Edge node failing to deploy with error "Invalid configuration for device '0'"

book

Article ID: 319126

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Symptoms:
Cannot deploy Edge node using NSX-T manager
Edge nodes can be deployed successfully through vCenter

Log output:
vCenter server
vpxd.log
2022-05-18T21:51:02.927Z info vpxd[06814] [Originator@6876 sub=InvtNetwork opID=1264859e] Checking for DVS with portgroup key dvportgroup-20, port key
...
2022-05-18T21:51:02.927Z info vpxd[06814] [Originator@6876 sub=InvtNetwork opID=1264859e] Network is (null)
...
...
2022-05-18T21:51:02.944Z info vpxd[06862] [Originator@6876 sub=InvtDVS opID=1264859e-01] Opaque network backing is involved in VM op[reconfigure]
2022-05-18T21:51:02.944Z error vpxd[06862] [Originator@6876 sub=coreanchor opID=1264859e-01] Portgroup [dvportgroup-20] is not found in the datacenter [{DC name}
2022-05-18T21:51:02.949Z error vpxd[06862] [Originator@6876 sub=DvsCore opID=1264859e-01] DVPortgroup [dvportgroup-20] no longer exists in VC
2022-05-18T21:51:03.005Z info vpxd[06862] [Originator@6876 sub=VmProv opID=1264859e-01] Applying ConfigSpec (vim.vm.ConfigSpec) {
2022-05-18T21:51:03.061Z error vpxd[06862] [Originator@6876 sub=VmProv opID=1264859e-01] Get exception while executing action vpx.vmprov.ReconfigureVm: N3Vim5Fault17InvalidDeviceSpec9ExceptionE(Fault cause: vim.fault.InvalidDeviceSpec

ESXi host
hostd.log
2022-05-18T21:51:14.492Z error hostd[2101059] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/49140bb5-daef361e/xxxxxxx/{Edge VM}.vmx opID=1264859e-01-11-4687 user=vpxuser:com.vmware.nsx.management.nsxt] Device spec doesn't match up with dvport/dvpg configuration
...
2022-05-18T21:51:14.493Z warning hostd[2101059] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/49140bb5-daef361e/xxxxxxx/{Edge VM}.vmx opID=1264859e-01-11-4687 user=vpxuser:com.vmware.nsx.management.nsxt] Method fault exception during reconfigure: N3Vim5Fault17InvalidDeviceSpec9ExceptionE(Fault cause: vim.fault.InvalidDeviceSpec
--> )
--> [context]zKq7AVICAgAAACzgJAERaG9zdGQAAOJCF2xpYnZtYWNvcmUuc28AATp37WxpYnZpbS10eXBlcy5zbwCBF8EHAYFXHQgBgZlLCAGBP00IAYHqBgQBAo9Ozmhvc3RkAAJ2A8ECYgjBAUKJ8QKwf1IAnMUtACQBLgDSDj8DO30AbGlicHRocmVhZC5zby4wAAS9pw5saWJjLnNvLjYA[/context]
2022-05-18T21:51:14.499Z info hostd[2101059] [Originator@6876 sub=Vimsvc.TaskManager opID=1264859e-01-11-4687 user=vpxuser:com.vmware.nsx.management.nsxt] Task Completed : haTask-18-vim.VirtualMachine.reconfigure-1604876771 Status error

dvportgroup-20 does not exist in table vpx_dvportgroup in VCDB

Environment

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

Cause

id & dvportgroup_key do not match in vpx_dvportgroup table of VCDB

Resolution

1. SSH to vCenter 
2. /opt/vmware/vpostgres/current/bin/psql -d VCDB
3. select id, dvportgroup_name, dvportgroup_key, dvportgroup_type from vpx_dvportgroup;

4. Confirm id & dvportgroup_key match up for the number.
  id | dvportgroup_name | dvportgroup_key | dvportgroup_type
 ----+-------------------------+-----------------+------------------
  29 | Guest-Infra-Edge-A | dvportgroup-26 | earlyBinding
  30 | Overlay-Edge-A | dvportgroup-25 | earlyBinding
  28 | vDS-Edge-A-DVUplinks-23 | dvportgroup-24 | earlyBinding
 
5. If it does not, create a new port group
  id | dvportgroup_name | dvportgroup_key | dvportgroup_type
 ----+-------------------------+-----------------+------------------
  29 | Guest-Infra-Edge-A | dvportgroup-26 | earlyBinding
  30 | Overlay-Edge-A | dvportgroup-25 | earlyBinding
  28 | vDS-Edge-A-DVUplinks-23 | dvportgroup-24 | earlyBinding
  29 | New-Edge-A | dvportgroup-29 | earlyBinding

In addition, when going through the wizard of deploying edge node and selecting port group interface for edge node match what it shows in the vpx_dvportgroup in VCDB.

Additional Information

The "Invalid configuration for device '0'" error can also occur for Service Deployments if a VDS portgroup is selected with mismatched id and dvportgroup_key values. Creating a new VDS portgroup that has matching id and dvportgroup_key will also resolve this issue.


Impact/Risks:
Edge node fails to deploy