This topic explains how Spanning Tree Protocol (STP) Bridge Protocol Data Units (BPDUs) are transmitted and handled in Cisco ACI environments, including the effects of static port assignments, VLAN pools, and VXLAN encapsulation on BPDU flooding and network stability.
-
STP BPDUs are transmitted and received based on static port assignments (access untagged or trunk) under an EPG in Cisco ACI.
-
BPDU flooding occurs within the VLAN ID (FD_VLAN) defined on an EPG path, and VXLAN VNIDs are allocated for forwarding across leaf switches.
-
Overlapping VLAN pools can cause unintentional BPDU flooding between EPGs; using separate VLAN pools for each EPG prevents this issue.
Transmission Scenarios and Configuration Guidance
When two or more switches running STP are connected to Cisco ACI in an EPG, the behavior of BPDU transmission depends on the static port assignments:
-
All statically assigned ports under EPG are access untagged: STP BPDUs are received and sent without a tag.
-
Mix of statically assigned trunk ports and access untagged ports: STP BPDUs received on a trunk port are sent to the access untagged port with a dot1q tag, causing the access port to enter an inconsistent state.
-
Mix of statically assigned trunk ports and access ports under an EPG: Cisco ACI sends STP BPDU with dot1q tag and the access ports use 802.1p access. Use 802.1p access on the Layer 2 switch to receive and process tagged STP packets. If 802.1p is not allowed, use trunk port access.
-
Cisco ACI acts as a full-duplex hub and floods spanning tree BPDUs within the VxLAN VNID associated to the encapsulation VLAN on which the BPDUs were received. External switches running RSTP or RPVST will default to point-to-point link types. If more than two external switches connect to the same encapsulation VLAN and EPG VNID, set the link type to "shared" on the external switch interfaces to avoid convergence and instability issues due to BPDU flooding from all connected bridges.
Spanning tree BPDUs are flooded within a given VLAN ID (FD_VLAN) defined on an EPG path. To forward traffic within the FD_VLAN across leaf switches, Cisco ACI allocates a VXLAN VNID called the fabric_encap . The fabric_encap is derived by adding the index value for the VLAN ID allocated from the VLAN pool to a numeric base identifier. For example, VXLAN VNID 9000 is assigned to VLAN pool A containing VLAN range 10-20; VLAN 10 is assigned VNID 9000, VLAN 11 is assigned VNID 9001, and so on.
If two separate EPGs use the same VLAN ID from the same VLAN pool, the same fabric_encap VNID can be derived for two EPGs on different leaf switches, potentially causing unintentional BPDU flooding between the EPGs.
To avoid this, assign different domains with separate VLAN pools to each EPG, ensuring that each VLAN ID is allocated from a unique VLAN pool and preventing overlapping fabric_encap VNIDs.
The fabric_encap values can be checked using the following command on leaf switches for a given 802.1q VLAN ID:
vsh_lc -c "show system internal eltmc info vlan br"