IntermediatePublished 2026-06-30
CCNA Port Security: Maximum Secure MACs on Access Ports
Bundle lab
Deploy and verify port security maximum settings on host-facing access ports in a pure Layer-2 campus with two access switches uplinked to a distribution switch. You will raise the allowed secure MAC count to 2 on each user port to support a PC and a potential downstream device (e.g., a dock), then verify with show commands. No Layer-3, SVIs, or routing are used; focus purely on access VLANs, trunks, and the port-security maximum behavior.
Learning objectives
- Configure switchport port-security with a specific maximum (2) on host-facing access ports
- Verify maximum and current secure MAC counts with show port-security interface
- Differentiate what traffic is permitted vs. blocked when the secure MAC count exceeds the maximum
- Avoid misconfiguration by never applying port-security on trunks
Troubleshooting focus
- A host port left in the wrong VLAN breaks same-VLAN pings.
- Pings fail only between the two access switches: VLAN 20 is missing from a trunk allow-list. Align the allowed list on both ends of each distribution link.
- A trunk reports a native VLAN mismatch: both ends must use VLAN 999 as native. A mismatch draws CDP/LLDP warnings and makes some control-plane behaviour inconsistent.
- Port-security only takes on a static access port, and belongs only on host-facing ports — remove it from any trunk configured in error.
show port-security interface Ethernet0/1reportsPort Security: Disabledeven though the maximum and violation lines are present: the interface accepts those options with the feature switched off.- A legitimate second device behind a port triggers a violation: the maximum is still 1.
show port-security interface Ethernet0/1must report Maximum 2 — the default violation mode is shutdown.
Topology
Subscribe to preview this lab's topology.
See plansGrade your work
How this lab is graded
- Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with
access-class, are stated in the guide and do have to match. - Addresses, modes and protocol keywords are exact. An IP address, a subnet mask,
switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide. - Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the running-config — a change that only exists in a terminal session never reaches the grader.
- You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
- Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.
Create a free account to submit your lab for grading.
Create a free accountFound a problem with this lab?
Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.