• Multiple Spanning Tree (), defined in IEEE 802.1s and now part of , is a Layer 2 protocol that lets you group several VLANs into one spanning tree instance.
    Before seeing how it works, you need to feel the problem it solves on a real enterprise network.

    The Network You Inherited

    You are the network engineer of a mid-sized company.
    Three distribution switches (SW1, SW2 and SW3) carry every VLAN of the business.

    Three distribution switches SW1, SW2 and SW3 wired in a triangle with three 1 Gbps uplinks, serving four department VLANs 10, 20, 30 and 40

    Figure 1 – Triangle links, four VLANs

    Behind them sit four departments: Finance and HR on VLAN 10 and 20, Engineering and Sales on VLAN 30 and 40.

    The three switches are wired in a full triangle with three 1 Gbps uplinks.
    The company paid for that redundancy, so all three links should carry traffic. You will see in a moment that classic spanning tree wastes one of them.

    Answer the question below

    Read the topology, then type Complete.

    Per-VLAN Architecture in Rapid-PVST+

    By default, Cisco switches run a Per-VLAN Spanning Tree (PVST+ or ), where a dedicated instance is maintained for every configured VLAN.
    Four user VLANs give you four distinct, independent spanning tree topologies.

    Each tree elects a with the same rule: lowest wins.

    Four Rapid-PVST+ trees for VLANs 10, 20, 30 and 40 all electing SW1 as root bridge because every switch keeps the default priority 32768

    Figure 2 – All VLANs toward SW1

    All your switches keep the default priority of 32768, so the switch with the lowest MAC address is elected. Say it is SW1.

    The four trees all pick the same root.
    And if four trees have the same root, they all block the same redundant link to prevent loops.

    The link between SW2 and SW3 is now blocked for every VLAN.

    The 1 Gbps link between SW2 and SW3 blocked by spanning tree for VLANs 10, 20, 30 and 40 at the same time, carrying no traffic

    Figure 3 – SW2-SW3 link blocked (PVST+)

    One of your three 1 Gbps uplinks carries zero packets.
    The company paid for redundancy and capacity, and only gives you redundancy.

    You could fix this by hand, with a different root priority on each of the four VLANs.
    But that means four trees to tune, four sets of BPDUs on every , and four topologies to troubleshoot. With 200 VLANs, it is 200 of everything.

    Answer the question below

    In Rapid-PVST+, how many spanning tree instances run when you have 4 VLANs?