I spent a good deal of time trying to work that one out. It seems to choose the name of the principal switch and I could not work out how to change the name to something more appealing. At least you can name VSAN's anything you like within reason.
This is also something I'd be interested in seeing. I've got one fabric named correctly, the other after a switch dump took the name of a middle tier 9216i and won't switch back, despite the fact that I changed the principal priority on the 9509 to 1 and then made it the principal with a disruptive(nondisruptive didn't work either).
Cisco documentation is woefully inadequate in certain areas....Also, the error of fabric merge failed, "member mismatch" comes to mind.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...