HCIA-Datacom lab 9 of 22
MSTP regions and instances for load sharing
Fix the wasted bandwidth of a single spanning tree. You build an MSTP region with two instances, give each instance its own root, and prove that two VLAN groups now use different uplinks while both stay protected from loops.
Run this lab
It needs Standard: its 5 nodes are set to 8 vCPU and 8,192 MB in total.
In your workspace: Shared, then HCIA-Datacom H12-811 guided labs, then 09 - MSTP regions and instances for load sharing
- Level
- Advanced
- Time
- About 60 minutes
- Nodes need
- 8 vCPU, 8,192 MB
- Smallest plan
- Standard
The scenario
Northwind's access switch SW3 has two uplinks: GE1/0/3 to SW1 and GE1/0/2 to SW2, and the two distribution switches are linked to each other. With RSTP there is one tree for all VLANs, so one uplink sits blocked and idle. The team wants Finance and Sales (VLANs 10 and 20) to use the uplink to SW1, and Logistics and Guest (VLANs 30 and 40) to use the uplink to SW2. Each uplink should back up the other.
| Item | Value |
|---|---|
| MSTP region | name NORTHWIND, revision 1 |
| Instance 1 | VLANs 10 and 20; primary root SW1, secondary SW2 |
| Instance 2 | VLANs 30 and 40; primary root SW2, secondary SW1 |
| Gateways (on SW1) | Vlanif10 192.168.10.1/24, Vlanif30 192.168.30.1/24 |
| PC1 / PC2 | SW3 GE1/0/10 (VLAN 10) / SW3 GE1/0/11 (VLAN 30) |
What you’ll practise
- Explain why one spanning tree for all VLANs wastes links, and how MSTP maps VLANs to instances
- Configure an MSTP region (name, revision, VLAN-to-instance mapping) identically on every switch
- Set a different primary and secondary root per instance
- Read display stp region-configuration and display stp instance N brief
The tasks
- Load the starting configuration
- Configure the region on all three switches
- Enable MSTP, then close the loop
- Give each instance its own root
- Prove the load sharing
- Break the region on purpose
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- SW1
GE1/0/1to SW2GE1/0/1 - SW2
GE1/0/2to SW3GE1/0/2 - SW1
GE1/0/3to SW3GE1/0/3 - SW3
GE1/0/10to PC1eth0 - SW3
GE1/0/11to PC2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SW1 | Huawei CloudEngine CE6800 | huaweice6800-bundled | 2 vCPU, 2,048 MB |
| SW2 | Huawei CloudEngine CE6800 | huaweice6800-bundled | 2 vCPU, 2,048 MB |
| SW3 | Huawei CloudEngine CE6800 | huaweice6800-bundled | 2 vCPU, 2,048 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
HCIA-Datacom H12-811 guided labs.Open
09 - MSTP regions and instances for load sharingand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More HCIA-Datacom labs
Related labs in other courses
CloudLabBox is independent of Huawei. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.