Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
NSX-T Data Center 3.2Host preparation fails with error: Host {UUID} is not added to VDS valueNSX-v to NSX-T migration fails with host preparation: Host {UUID} is not added to VDS valueNVDS to CVDS migration fails with an error: DVS switch <Switch Name> having id 50 06 99 00 14 ce 70 ed-62 90 7e f2 64 fd 19 a6 is not found in parent network folder group-n30. Network folders are configured in the vCenter inventory On the Manager, /var/log/proton/nsxapi.log shows the following warning. 2022-01-6T14:14:25.428Z WARN task-executor-24 VcResourceServiceImpl 31349 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] DVS switch DSwitch having id 10 10 6c 6b a4 1c 04 0d-c3 96 26 1e 95 7a 08 0b is not found in parent network folder group-n1156
When VDS and the first network on the ESXi host are not under the same hierarchy and and NSX install is triggered on the hosts using the VDS, TN Update or TN Create may fail.This can include NVDS to CVDS migration or new preparation of the ESXi host with CVDS.
Prevents the preparation of new hostsExisting hosts may throw the error as well if Transport Node Profile is attached.This issue occurs when the DVS used in the TNP has a different parent than the parent of the first network of the host.NVDS to CVDS migration gets failed when the CVDS is under a different parent than the first network on the TN being migrated.
This is a known issue currently impacting NSX-T Data Center 3.2.and NSX 4.0.
NSX-T versions prior to 3.2.1The first network of the host is the first network as visible on the network field in the vCenter MOB page https://<VC-IP>/mob?moid=host-morefThe first network of hosts as mentioned above and the concerned VDS should be directly under the same folder. The folder could be either DataCenter or a network folder inside DataCenter.Example 1 Move concerned DVS(s) and the first network(s) ( NSX, Standard or DVS network) out of folders to be directly under DataCenter orExample 2 From the Proton nsxapi log confirm the vCenter moid of the folder where the DVS should be located For example, in the warning below we can see DVS should be in folder group-n1156 2022-01-6T14:14:25.428Z WARN task-executor-24 VcResourceServiceImpl 31349 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] DVS switch DSwitch having id 10 10 6c 6b a4 1c 04 0d-c3 96 26 1e 95 7a 08 0b is not found in parent network folder group-n1156 From vCenter UI manually move the DVS to folder group-n1156 and retry host preparationgroup-n1156 is the parent folder for the first network. NSX-T 3.2.1/ NSX 4.0.0.1 and aboveThe first network of the host as mentioned above should be directly under a folder and desired VDS can be directly under the same folder or can be nested inside the same folder. The folder could be either DataCenter or a network folder inside DataCenter.Example 1 Move the first network on the ESXI host directly under DataCenter or DVS can be in any folder under Datacenter orExample 2If the first network on the ESXI host is in a folder move then vDS to the same folder or DVS can be nested under the same folder.
To get the host-moref ID:https://<VC-IP/FQDN>/mob/ --> content --> ManagedObjectReference:Folder (Datacenter Name) --> ManagedObjectReference:ManagedEntity[] (Datacenter ID) --> ManagedObjectReference:Folder (host) --> ManagedObjectReference:ManagedEntity[] (VC cluster) --> ManagedObjectReference:HostSystem[] (Host ID)OrRun the following API against NSX Manager https://<NSX Manager IP>/api/v1/transport-nodes/<node-id>In the output check for "discovered_node_id" in "node_deployment_info" which will be a combination of compute manager id and host morefExample: 73a9b0bf-71bb-44be-b6ff-2b57d4007eb7:host-1004In this case, host moref is host-1004Validate the Network on the TNode either through or through the MOB page. The first network can be DVPG, NSX Network (NVDS), or a Standard network.https://<VC-IP/FQDN>/mob/?moid=<host moref> Expand the field to see all networks on the TNode: ManagedObject Reference: Networkhttps://<VC-IP/FQDN>/mob/?moid=<folder ID> Example: group-n1156 taken from the log snippet mentioned in the KBExpand the field to see all networks under the folder: ManagedObject Reference: ManagedEntity