CCNP ENCOR lab 26 of 36
SPAN and RSPAN: mirror traffic to an analyser
Mirror a warehouse PC's traffic to a Linux analyser, first with local SPAN on the same switch and then with RSPAN across a trunk to a second switch, and capture it with tcpdump.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 4,096 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 26 - SPAN and RSPAN - mirror traffic to an analyser
- Level
- Intermediate
- Time
- About 50 minutes
- Nodes need
- 5 vCPU, 4,096 MB
- Smallest plan
- Lite
The scenario
Fernhill Freight's payroll clerk (PC1) reports that a payroll application keeps timing out. The application team wants a packet capture of PC1's traffic, and they'd also like to see everything in the staff VLAN from the network operations desk, which is connected to a different switch.
You'll mirror traffic to ANALYSER, a small Linux box with two network cards: eth0 is plugged into SW1 (for local SPAN), eth1 into SW2 (for RSPAN). SW1 already pings PC1 every two seconds from its VLAN 10 address (IP SLA 1), so there's always something to capture.
| Device | Port | Role |
|---|---|---|
| SW1 | Gi1/0 | PC1 (VLAN 10, 10.10.10.10): the port to mirror |
| SW1 | Gi1/1 | PC2 (VLAN 10, 10.10.10.11) |
| SW1 | Gi1/2 | ANALYSER eth0 (local SPAN destination) |
| SW1 | Gi0/1 | trunk to SW2 |
| SW1 | Vlan10 | 10.10.10.2/24 |
| SW2 | Gi0/1 | trunk to SW1 |
| SW2 | Gi1/0 | ANALYSER eth1 (RSPAN destination) |
Topology: SW1 — SW2 over a trunk; PC1, PC2 and ANALYSER eth0 on SW1; ANALYSER eth1 on SW2.
What you’ll practise
- Explain SPAN, RSPAN and ERSPAN and when each one is used
- Configure a local SPAN session with source ports, direction and destination port
- Create an RSPAN VLAN and build source and destination sessions on two switches
- Capture mirrored traffic with tcpdump and verify sessions with show monitor
The tasks
- Prepare the analyser
- Know your mirroring options
- Local SPAN of PC1's port
- Prepare the RSPAN VLAN
- Build the RSPAN sessions
- Capture like an engineer
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
Gi0/1to SW2Gi0/1 - SW1
Gi1/0to PC1eth0 - SW1
Gi1/1to PC2eth0 - SW1
Gi1/2to ANALYSEReth0 - SW2
Gi1/0to ANALYSEReth1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| SW2 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 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 |
| ANALYSER | 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
CCNP ENCOR 350-401 guided labs.Open
26 - SPAN and RSPAN - mirror traffic to an analyserand 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 CCNP ENCOR labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.