In vPC deployments, STP is actually running on both peer devices. And for vPC ports, they are controlled only by the STP instance on primary switch (which means only primary switch generates and sends out BPDUs for vPC ports), while STP instance on secondary switch does not dictate vPC member port state. below are my queries:
Q1: In BPDUs sent by primary switch, vPC System-MAC will be used in Bridge ID or vPC Local System-MAC?
Q2: If BPDUs go this path primary swtich----peer link----secondary switch-----vPC member port----downstream devices, what is the value of Path Cost in BPDU receiced on downstream devices, Path cost of peer link only or Path cost of peer link + path cost of vPC member port ？
Q3: Both vPC member ports on both peer devices always share the same STP port state (FWD state in a steady network). How could this be achieved from STP perspective?
Q4: Why Cisco Strongly recommends not to enable Loopguard and Bridge Assurance on vPC?
Q5: Why Cisco stronlgy recommends to enable Bridge Assurance on vPC peer-link?
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...