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

About the author:

Vinnie Lima

Vinnie Lima is the Managing Director for VVL Systems & Consulting, a small business focusing on IT Optimization for Cloud, Infrastructure, and End Users. Based out of Baltimore, Maryland, Vinnie Lima has over 21 years in IT Automation, Orchestration, and Cloud. Mr. Lima’s career has been focusing on helping customers drive value from their IT investments through the use of leading edge technologies and approaches, driving innovation in a wide spectrum of industries such as DoD, Federal, Health Care, and Financial.

facebook twitter linkedin instagram

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to our Newsletter
Stay informed with the latest technology news, industry events, and training offered by VVL Systems for free! Fill out this form and receive our newsletter delivered straight to your inbox.

See how VVL has helped clients leverage the latest technologies and agile capabilities.

Latest VVL and Industry News

Upcoming VVL and Industry Events