That is the VPC magic :-). That being said,when you have device configured as the VPC-peer, they use a common system MAC or the Primary VPC switch to be forwarded to the downlink devices for the STP. This way we modify the STP behaviour and the VPC domain represent itself as a single root bridge to STP which runs in the background. The downlink devices see the BPDU's coming from a single device as this is all controlled by the VPC Primary switch. VPC Primary switch syncronizes the STP state with peer switch using CFSoE. Once both the peers are synced, all the VPC ports are controlled by the VPC orimary switch.
I have a vPC between two N7K. I did show spanning-tree and show vpc role on both the device. The vpc-system mac (sh vpc role) and root-id and bridge-id (sh spanning-tree), all the 6 mac addresses are same. vPC local system-mac is different. So my question is, what mac address is electing as the Nexus root id mac address.
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...