Bound physical interface down. HBA's cannot login to the FABRIC.
I have two MDS switches, connected to two Fabric Interconnects. FI-A to MDS-A (vsan2), FI-B to MDS-B (vsan1) I created 2 vhba templates, 1 for fabric A and another one for fabric B. The HBA's logged in successfully on MDS_A/FI_A without any issues but didn't loggin on MDS_B/FI_B. I verified the physical connections and they're all up. I'm getting an error "FC VIF XXX on server X/X of switch B, reason: Bound physical interface" on fabric B's servers' VIF paths. Except server 1, all the paths for it are up but the other one's are down. I have enabled npiv feature on MDS and npv on the FI as well, uplink ports are up and are in the correct vsan(1).
I have no idea what the problem is,see the attached screenshots
Eventually the HBA's logged on the switches after i added the servers to the storage and installed the OS. The configs were right, i didn't change anything. I don't know y it was doing that. They were supposed to work, wondering!!!!
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...