Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Troubleshooting an error when onboarding a cluster

If the relationship between a cluster and access switch is missing, you might encounter the following error while onboarding a cluster:

No matching switches found between Pod and VirtualCluster [CustomerWorkload], or VirtualHosts in that VirtualCluster

To troubleshoot the issue, make sure that the device URL in BMC Network Automation matches the artifacts specific to BMC Server Automation. The BMC Network Automation device URL is a combination of the switch name, ESX name (applicable for standard vSwitches only), and vCenter name. If you ensure that the fully qualified domain name (FQDN) includes the correct domain names, you can eliminate errors when onboarding a cluster. Examples of device URLs are:

  • vSwitch0@esx1.mydomain.com@myvcenter.mydomain.com
  • dvSwitch1@myvcenter.mydomain.com

Example

If there is an N1K switch, the current virtual cluster onboard flow does not handle the host name of the switch configured in BMC Network Automation.

Resolution: Enter the IP address in the Host Name, IP Address, or URL field when configuring a Cisco DVS device in BMC Network Automation. BMC Cloud Lifecycle Management relies on reverse DNS lookups and expects an IP address when configuring a device. To perform a reverse DNS lookup, enter the IP-to-host-name-mapping entry in the hosts file on Platform Manager

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*