ACI External Switch STP Link Type Configuration
As part of a migration, legacy non-ACI switches must be connected to the Cisco ACI fabric. All non-ACI switches run per-VLAN RSTP. After the non-ACI switches are connected to Cisco ACI, the STP convergence caused a microloop and significant CPU spike on all switches. Which configuration on the interfaces of the external switches that face the Cisco ACI fabric resolves the problem?
Community Insight
The exam tests knowledge of RSTP compatibility with ACI; the common trap is assuming standard P2P settings apply, whereas 'link-type shared' is required for legacy multi-switch topologies.
This question addresses the configuration of external non-ACI switches connecting to the Cisco ACI fabric, specifically focusing on resolving STP microloops and CPU spikes by setting the correct link type.
Candidates often select BPDU filtering (C) or guard (A), mistakenly believing that blocking BPDUs entirely prevents loops, which can lead to blackholing traffic or err-disabled ports in this context.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Correct answer: D — The interfaces on the external switches facing the ACI fabric must be configured with 'STP type link shared'. Cisco ACI leaf switches operate as a single logical spanning-tree root for the attached domain. When connecting to legacy switches that may have multiple paths or redundant links among themselves, the link type must be set to 'shared' so that RSTP does not assume a simple point-to-point topology. This prevents the aggressive transition times of point-to-point links from causing instability, microloops, and CPU spikes during convergence.Why the Other Options Are Wrong
BPDU guard (A) would shut down the port if a BPDU is received, which is inappropriate since the external switch must participate in the spanning tree. BPDU filtering (C) stops the exchange of BPDUs, effectively removing STP protection and risking severe Layer 2 loops. Aggressive STP timers (B) would exacerbate the issue by speeding up transitions before the topology is stable, likely increasing CPU load rather than resolving it.Community Comment Notes
Community consensus strongly favors option D, with users citing Cisco documentation that explicitly recommends 'link-type shared' for RSTP connections to ACI. One user noted that while shared links are generally discouraged in pure traditional networks due to timer revert issues, they are the necessary best practice here to ensure compatibility with the ACI fabric's operation. Another comment highlighted that point-to-point is reserved for MST or direct single-link connections, making it incorrect for this multi-switch legacy scenario.Official Reference
Exam Strategy
When connecting non-ACI devices to ACI, always check the STP protocol version. If using RSTP, configure the external interface as 'link-type shared'; if using MST, use 'point-to-point'. Memorizing this distinction prevents confusion regarding loop prevention mechanisms.
Frequently Asked Questions
Why not use BPDU filtering to stop STP interactions?
BPDU filtering disables STP on the port, which removes loop protection. In an ACI environment, this can lead to broadcast storms and network blackholing because the fabric relies on STP awareness.
When should I use point-to-point vs shared link type?
Use 'point-to-point' when connecting to a single device running MST or when you are certain there is only one path. Use 'shared' when connecting to legacy switches running RSTP that may have internal redundancy or multiple connections.