If I understand correctly, in an Active/Active FEX design two Cisco Nexus 5000s plug into two Cisco Nexus 2000s which in turn plug into the server. There is a two way vPC between the 2000s and 5000s (it doesn't look like that's shown in the picture though). However, because there is a vPC between the FEXs and the Nexus 5000 you cannot have a vPC between the FEXs and the servers. Why is this? Any clarification on at a conceptual level of how an Active/Active FEX configuration works is also appreciated. I've read the section, but since I haven't had hands on with any of this equipment I'm having some trouble conceptualizing everything. Thanks for your time.
When you have a vpc between fex and parent switch, you do not need to create a custom vpc between the fex and the server. The fex ports by default are in vpc which is created automatically when you dual home the fex port to the same server.
"show vpc" should list all the vpcs which comprise of your fex ports.
What you are referring to is probably the feature where you can assign custom vpc numbers to port-channels between fex and the server and as i remember, this feature is supported after a certain code and one certain platforms ( will have to check the details for this ).
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...