This is expected behavior. Distributed switches are created and owned by vCenter, and a proxy copy is given to each host. In situations where the host is moved to a new vCenter or the vCenter is rebuilt and the host is re-added, the vCenter Server Distributed Switch does not recognize the host's proxy copy of the switch. This error will generate asking the user to verify that the host's proxy copy is the same as the vCenter Server's Distributed Switch.
To resolve this alarm:
- Connect to the vCenter Server directly using the vSphere Client.
- Verify the vCenter Server's current vDS or create a new vDS.
a. Create and configure the appropriate port groups on the newly create vDS.
- Navigate to Networking tab and select the appropriate vDS.
- Launch the Add and Manage Hosts wizard.
- Select the host and the physical adapters that are currently connected to the host's proxy switch.
- Click Next.
- Select the virtual adapters that are to be migrated to the vDS.
- Choose the virtual NICs that are currently connected to the host's proxy switch, and provide a target port group.
- Click Next.
- Select the virtual machines that you want to migrate to the newly created vDS. All the virtual machines that are currently connected to the host's proxy switch should appear with a warning icon in the list and you can locate them easily. You can select multiple virtual machines and assign a target portgroup at once.
- Complete the wizard. The migration now starts.
In some situations, the user does not need the vDS on the host at all any more. In this case, the user can delete the host's proxy copy by clicking on
Inventory >
Host >
Configure >
Networking >
Virtual Switches. The vDS will be listed here. If objects are still attached to the vDS, they will need to be moved to another switch. Once the vDS is empty, there will be an option to remove the vDS in the menu next to the vDS.
If a "resource is in use" error occurs, see
The resource 'Port-ID' is in use error when removing a host from VDS.