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:
- Remove the Network Container from CLM
- Offboard POD from CLM
- Destroy the POD in BBNA
- Rename the device in BBNA
- Recreate POD in BBNA
- Re-onboard the POD in CLM
- Re-create the Network Container in CLM.
- 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
Leave a Reply