No matching switches found between Pod and VirtualCluster, or VirtualHosts in VirtualCluster

If you run into this problem in CLM 2.1/3.0/3.1 when on-boarding a Virtual Cluster as a Resource, most likely culprit is that the “name” of the VMware dvSwitch or vSwitch part of the BBNA POD does not match BBSA name:

So, how do you fix this? You can do one of two different ways:

1. Remove the Network Container from CLM
2. Offboard POD from CLM
3. Destroy the POD in BBNA
4. Rename the device in BBNA
5. Recreate POD in BBNA
6. Re-onboard the POD in CLM
7. Re-create the Network Container in CLM.
8. Re-onboard the Virtual Cluster

Other tips:

If you are onboarding a standard vSwitch into BBNA, use the following syntax for the vSwitch IP/Host Address:

vSwitch0@vvl-esx-d.vvldemo.local@https://vvl-vcenter-d

For Distributed vSwitches, use:

dvSwitchA@https://vvl-vcenter-d