IntermediatePublished 2026-07-04
Syslog Severity & Buffered Logging
Bundle lab
Tune which syslog messages go where on Cisco IOS using severity levels: keep detailed logs locally in a 16 KB buffer, reduce console noise to warnings, and send notifications to a central server. Single management LAN, no routing. Grading focuses on three R1 commands steering severity: logging buffered 16384 debugging, logging console warnings, and logging trap notifications.
Learning objectives
- Explain the syslog severity scale (0–7) and inclusive matching behavior
- Configure a local log buffer sized and leveled for deep troubleshooting
- Reduce console interruptions by raising the console severity threshold
- Send a moderate set of events (notifications) to a remote syslog host
- Verify effective log destinations and levels using show logging
Troubleshooting focus
- No messages appear on the server: confirm logging host is present and trap level is not higher than the generated events
- Console still too chatty: ensure logging console warnings is applied and not overridden
- Local buffer empty or too short: verify logging buffered size and level
- Unexpected message volume sent upstream: verify logging trap level is notifications (not informational or debugging)
- Timestamps missing in logs: confirm service timestamps log datetime is enabled (informational but useful)
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.