Arista EOS lab 3 of 20
MSTP and LACP port-channels
Turn a looped triangle of switches into a loop-free, load-shared layer 2 network: bundle the inter-switch links with LACP, design an MSTP region with one root per instance, and protect the edge with portfast, BPDU guard and root guard.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 6,656 MB in total. That fits the free demo too.
In your workspace: Shared, then Arista EOS guided labs, then 03 - MSTP and LACP port-channels
- Level
- Beginner
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 6,656 MB
- Smallest plan
- Lite
The scenario
Northwind's office core is a triangle: two distribution switches (dist1, dist2) joined by two cables, and an access switch (acc1) with one uplink to each. Every link is a trunk for VLANs 10 and 20. A triangle is a loop, so spanning tree is doing all the work, and nobody chose where the root is. Your job: make the dist1–dist2 cables one logical link, then design MSTP so VLAN 10 prefers dist1 and VLAN 20 prefers dist2, and protect the edge.
| Device | Interface | Connects to | Role |
|---|---|---|---|
| dist1 | Ethernet1, Ethernet2 | dist2 Ethernet1, Ethernet2 | to become Port-Channel12 |
| dist1 | Ethernet3 | acc1 Ethernet1 | trunk 10,20 |
| dist2 | Ethernet3 | acc1 Ethernet2 | trunk 10,20 |
| acc1 | Ethernet3 | h10 | access VLAN 10 |
| SVI (for testing only, no routing) | dist1 | dist2 | acc1 | h10 |
|---|---|---|---|---|
| VLAN 10 · 10.10.10.0/24 | .1 | .2 | .3 | .11 |
| VLAN 20 · 10.10.20.0/24 | .1 | .2 | .3 | – |
What you’ll practise
- Bundle two links into an LACP port-channel and verify the bundle
- Configure an MSTP region (name, revision, VLAN-to-instance map) identically on every switch
- Place the root bridge of each instance deliberately with priorities
- Predict and verify port roles and states per instance
- Protect edge ports with portfast and BPDU guard, and the distribution layer with root guard
The tasks
- Look at the loop spanning tree has blocked
- Bundle the dist1–dist2 links with LACP
- Design the MST region
- Place the roots
- Protect the edge and the core
- Prove both instances forward
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
- dist1
Ethernet1to dist2Ethernet1 - dist1
Ethernet2to dist2Ethernet2 - dist1
Ethernet3to acc1Ethernet1 - dist2
Ethernet3to acc1Ethernet2 - acc1
Ethernet3to h10eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| dist1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| dist2 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| acc1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| h10 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Arista EOS guided labs.Open
03 - MSTP and LACP port-channelsand 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 Arista EOS labs
Related labs in other courses
CloudLabBox is independent of Arista Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.