CCNA lab 15 of 46
Port security with sticky MACs and violation modes
Lock three office ports to the devices that belong there with sticky and static secure MACs, trigger a real violation from a Linux host that changes its MAC address, and compare protect, restrict and shutdown before recovering the port.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 4,608 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 15 - Port security with sticky MACs and violation modes
- Level
- Intermediate
- Time
- About 45 minutes
- Nodes need
- 5 vCPU, 4,608 MB
- Smallest plan
- Lite
The scenario
Ashby Dental's reception switch (S1) has a free port at a hot desk, and last week a visitor plugged in their own laptop and a pocket switch. The practice wants each port tied to its own device: the reception PC (PC1), the accounts PC (PC2) and the hot-desk laptop (H1), which the IT supplier registers by MAC address.
| Device | Port | Address | Port security policy |
|---|---|---|---|
| R1 | Gi0/0 (uplink, S1 Gi0/0) | 10.15.10.1/24 | none (uplink) |
| PC1 | S1 Gi0/1 | 10.15.10.11/24 | 1 MAC, sticky, shutdown |
| PC2 | S1 Gi0/2 | 10.15.10.12/24 | 1 MAC, sticky, protect |
| H1 | S1 Gi0/3 | 10.15.10.13/24, MAC 02:00:00:00:15:13 | 1 MAC, static 0200.0000.1513, restrict |
Topology: R1 Gi0/0 — S1 Gi0/0 · S1 Gi0/1, Gi0/2, Gi0/3 — PC1, PC2, H1.
What you’ll practise
- Explain the threats port security addresses: MAC flooding and unauthorised devices
- Configure maximum addresses, sticky learning and static secure MACs
- Choose between the protect, restrict and shutdown violation modes
- Trigger and diagnose a violation with show port-security and the logs
- Recover an err-disabled port by hand and with errdisable recovery
The tasks
- Get the hot-desk laptop online
- Lock reception with sticky learning
- Register the hot desk with a static secure MAC
- Compare the violation modes
- Trigger a violation
- Recover the port
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
- R1
Gi0/0to S1Gi0/0 - S1
Gi0/1to PC1eth0 - S1
Gi0/2to PC2eth0 - S1
Gi0/3to H1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| S1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 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 |
| H1 | 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
CCNA 200-301 guided labs.Open
15 - Port security with sticky MACs and violation modesand 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 CCNA 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.