Error: Host <UUID> is not added to VDS value: <value> . (Error code: 9548)

Products

• VMware NSX

Issue/Introduction

You are preparing ESXi Host for NSX and during configuration of Host Switch you encountered below error:

Error: Host c4####-6a2a-####-aa61-3bc6d5###### is not added to VDS value: "50 #### 6f b7 9f ####-ab 5e ae 24 0d ######" . (Error code: 9548)

Environment

VMware NSX

Cause

This error occurs when the ESXi host being prepared for NSX-T is not associated with the specified vSphere Distributed Switch (VDS)

Resolution

1. Verify the host is added to the correct VDS in vCenter.
2. Confirm the host’s physical NICs are connected to uplinks on the VDS.
3. If the host was recently re-imaged or re-added, ensure it's reattached to the appropriate VDS.
   1. See KB 307917 if you hit error "Unable to Create Proxy DVS ; Status(bad0005)= Already exists" when trying to add host back to the VDS in vCenter.
4. Resync the host configuration in vCenter and retry the NSX preparation.
5. If the issue persists after adding the host back to the DVS check the following.
   1. Check if the vmnics that were added to the DVS are showing as assigned to a Standard Switch on the host.
   2. Attempt to remove the vmnics from the Standard Switch via the VC UI.
   3. If there's no error thrown and the vmnics remain on the Standard Switch do the following.
      1. Confirm that the Standard Switch is not in use.
      2. Delete the Standard Switch
      3. Assign the vmnics to the DVS
      4. From within the NSX UI, confirm that host is successfully prepared for NSX

 

Alternatively, you may need to remove and re-add the ESXi host from the inventory. This should remove any NSX vibs on the ESXi host. This can be verified through below from ESXi cli: 

# esxcli software vib list | grep -i nsx

If the NSX vibs are still present after removal from inventory, you can perform manual deletion by way of below command: 

# nsxcli -c del nsx

Once the NSX vibs are removed, perform an ESXi host reboot. Once completed, re-add the host into the cluster. Then confirm from NSX UI, that host has been successfully added back.