Question 340
Several VLANs have unexpected root placement under VSTP after port membership changes. Which next action best resolves this observed routing or switching failure?
Explanation
Correct Answer
Correct diagnosis: Per-VLAN spanning-tree behavior can differ across VLANs. The appropriate action is: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary. The follow-up evidence required is: Each tested VLAN elects its approved root and loop-free port roles.
Incorrect Answers
That result would be useful for a different failure, namely: A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. The current case specifically calls for: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary. The required observed result is: Each tested VLAN elects its approved root and loop-free port roles.
This response would target a different source scenario: An edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. It cannot establish the current acceptance requirement, which is: Each tested VLAN elects its approved root and loop-free port roles. The relevant action is: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.
Inspect interface faults and control-plane events before changing STP timers is a relevant step for the separate scenario in which an RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. It does not directly fix this case. Instead inspect per-VLAN STP instances and configured priorities, not just a global STP summary; verify: Each tested VLAN elects its approved root and loop-free port roles.