RSTP and MSTP

RSTP and MSTP

Quick Answer: RSTP speeds STP by using active handshakes and fewer states (Discarding/Learning/Forwarding) while keeping the same root/path-cost ideas. Configure access ports as edge ports so hosts come up quickly. MSTP groups VLANs into instances, each with its own tree, so redundant uplinks can both carry traffic for different VLAN sets instead of one blocked tree for everything.

Classic 802.1D solved loops but was too slow for modern campus expectations: waiting through Max Age and dual Forward Delay after a fiber cut meant voice and data applications timed out. Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) keeps the election mathematics you already know and redesigns the state machine and neighbor signaling so failover often completes in sub-second to a few seconds on point-to-point full-duplex links. Multiple Spanning Tree Protocol (MSTP, IEEE 802.1s) then solves a different problem: a single tree wastes bandwidth on blocked links for all VLANs; multiple instances allow intelligent load sharing.

What RSTP keeps from STP

RSTP still:

• Elects one root bridge using the lowest Bridge ID (priority + MAC).
• Elects root ports using lowest path cost to the root.
• Elects designated ports per segment.
• Blocks redundant ports so the active topology is a tree.

If you only change the mode from STP to RSTP without redesigning priorities, the same switch still becomes root and the same links still tend to block. Faster convergence does not replace good root placement.

Faster convergence mechanisms

Proposal / agreement on point-to-point links

On full-duplex point-to-point links between switches, RSTP uses a proposal/agreement handshake. A designated port proposes to move quickly to forwarding; the neighbor agrees after ensuring its own downstream ports will not create a temporary loop. This handshake replaces the long, blind timer waits of classic Listening/Learning on those links.

Fewer conceptual states

RSTP collapses classic Blocking/Listening into Discarding (does not forward user frames), keeps Learning, and uses Forwarding. Many exam questions still mention both vocabularies; map them:

Alternate and backup roles

RSTP names blocked ports more precisely:

When the root port fails, an alternate port can move to forwarding rapidly because it already knows it is a viable backup path. That is a key speed win over classic STP’s slow re-election from scratch.

Edge ports: the access-layer exam trap

Ports that connect only to end hosts (PCs, printers, IP phones) should never form a switch-to-switch STP adjacency. RSTP treats them as edge ports. On Huawei VRP the common configuration idea is:

[SW-GigabitEthernet0/0/10] stp edged-port enable

Benefits:

• The port transitions to forwarding immediately (or nearly so) when the link comes up—critical for DHCP clients and phones.
• The port does not expect BPDUs from a neighboring bridge as part of normal operation.

Exam trap: Do not enable edge mode on inter-switch uplinks or on ports that might connect a user’s unauthorized switch. If a BPDU appears on an edge port, something unexpected is on the wire. Production designs pair edge ports with BPDU Guard so the port error-disables when a BPDU arrives, protecting the spanning tree from a rogue switch that would otherwise inject superior BPDUs and potentially steal the root role.

Conceptual BPDU Guard behavior (HCIA level): edge port + BPDU received → shut down / error-down the port rather than silently accepting a topology change that might black-hole the campus.

Huawei mode selection notes

Campus switches often default to a rapid or multiple mode depending on software and model. Conceptual commands you should recognize:

[SW] stp mode rstp
[SW] stp mode mstp
[SW] stp enable
[SW] display stp brief

Use display stp output to confirm the protocol mode, root BID, local port roles (ROOT/DESI/ALTE), and whether a port is treated as an edge port. When troubleshooting slow PC link-up, check whether the access port is edge-enabled and whether STP is unexpectedly blocking because a loop or mis-cabling exists.

Why a single tree is not enough: introducing MSTP

Suppose distribution switches D1 and D2 dual-home to the core, and VLANs 10 and 20 both need capacity. With one spanning tree for all VLANs, one of the dual uplinks is blocked for every VLAN. Half of the fiber capacity sits idle for Layer 2 traffic even though the physical plant is redundant.

MSTP creates multiple logical trees (instances). You map VLANs to instances so that:

• Instance 1 (for example VLANs 10–19) uses D1’s uplink as preferred forwarding path.
• Instance 2 (VLANs 20–29) prefers D2’s uplink.

Both physical uplinks carry traffic, but for different VLAN groups—true Layer 2 load sharing without loops inside each instance.

MSTP building blocks (conceptual)

All switches in a region must agree on the mapping. A mismatch effectively places devices in different regions and can produce unexpected blocking or suboptimal paths—configuration consistency is part of the operational story even at associate level.

HCIA-level configuration patterns

Exact CLI depth varies by software, but the mental model for VRP resembles:

[SW] stp mode mstp
[SW] stp region-configuration
[SW-mst-region] region-name CAMPUS
[SW-mst-region] instance 1 vlan 10 to 19
[SW-mst-region] instance 2 vlan 20 to 29
[SW-mst-region] active region-configuration
[SW] stp instance 1 root primary
[SW] stp instance 2 root secondary

On another aggregation switch you invert instance root roles so instance 1 prefers one chassis and instance 2 prefers the other. Always finish region changes with activation so the mapping takes effect, then verify with display stp / instance-focused displays.

RSTP vs MSTP vs classic STP — comparison table

Design guidelines for campus

1. Run a rapid mode (RSTP or MSTP) rather than pure 802.1D on modern Huawei campus switches unless interoperability forces otherwise.
2. Root per instance on distribution/core devices; access switches should not become root.
3. Edge + BPDU Guard thinking on every host-facing access port.
4. Map VLANs thoughtfully in MSTP so each dual-homed path carries meaningful traffic shares; avoid mapping all busy VLANs into one instance.
5. Keep region parameters identical across the domain that should act as one MST region.
6. Do not confuse MSTP instances with VRFs or L3 ECMP—MSTP still works at Layer 2 inside VLANs; inter-VLAN routing remains on VLANIF/SVIs or routers.

Exam checklist

• Explain why RSTP converges faster than 802.1D (handshake + alternate ports, not only shorter timers).
• Define edge port behavior and why access ports should use it; state BPDU Guard’s protective reaction.
• Distinguish alternate vs backup roles at a definition level.
• State MSTP’s benefit: map VLANs to instances for multi-tree load balancing.
• Know that region name, revision, and VLAN mapping must match for switches to share an MST region.

With loop-free multi-instance trees in place, the next bandwidth tool is link aggregation—bonding parallel Ethernet links into one logical pipe without creating a loop between the same pair of devices.