NSX-T host preparation fails with error: Host {UUID} is not added to VDS value
Article ID: 319960
Updated On:
Products
Issue/Introduction
Symptoms:
- NSX-T Data Center 3.2
- Host preparation fails with error: Host {UUID} is not added to VDS value
- NSX-v to NSX-T migration fails with host preparation: Host {UUID} is not added to VDS value
- NVDS to CVDS migration fails with an error:
- Network folders are configured in the vCenter inventory
- On the Manager, /var/log/proton/nsxapi.log shows the following warning.
Environment
VMware NSX-T Data Center
Cause
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.
Resolution
- This is a known issue currently impacting NSX-T Data Center 3.2.and NSX 4.0.
Workaround:
NSX-T versions prior to 3.2.1
The 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-moref
The 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
or
Example 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
- From vCenter UI manually move the DVS to folder group-n1156 and retry host preparation
- group-n1156 is the parent folder for the first network.
NSX-T 3.2.1/ NSX 4.0.0.1 and above
The 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
or
Example 2
If 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.
Additional Information
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)
Or
Run 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 moref
Example: 73a9b0bf-xxxx-xxxx-xxxxxxx:host-1004
In this case, host moref is host-1004
Validate 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: Network
https://<VC-IP/FQDN>/mob/?moid=<folder ID>
Example: group-n1156 taken from the log snippet mentioned in the KB
Expand the field to see all networks under the folder: ManagedObject Reference: ManagedEntity
Impact/Risks:
- Prevents the preparation of new hosts
- Existing 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.
Feedback
