Week 9 · Lesson 12

Syslog

When a router’s interface flaps or a switch’s CPU spikes at 2:00 a.m., the evidence is written as a syslog message — if you configured logging. Syslog is the standard way network devices record events and push them to a central collector, and understanding its severity levels and message format is the difference between reading a log line and decrypting it. This lesson covers the 0–7 severity scale, message anatomy, IOS logging destinations, and how to verify the whole pipeline.

CCNA 200-301 Domain 4.0 IP Services Verified 2026-10-11
Learning objectives
Part 1

Severity levels 0–7

Every syslog message carries a severity from 0 (most severe) to 7 (least). The exam is merciless here: you must know all eight, in order, including their names and numbers.

LevelKeywordMeaningExample
0emergencySystem unusable.Router hardware failure, no usable memory.
1alertImmediate action needed.Temperature alarm, power loss imminent.
2criticalSerious condition.Interface loss that isolates a site.
3errorError condition.Failed authentication, null TTL dropped.
4warningWarn of future trouble.High CPU or memory utilisation.
5notificationNormal but notable event.Configuration applied from console.
6informationalNormal informative event.Interface up, adjacency formed.
7debuggingVerbose debugging output.debug ip packet output.
Exam tip — memorisation hooks A common mnemonic for 0→7: “Every Ailing Cisco Engineer Needs Warning Notifications Instead Debugging” — Emergency, Alert, Critical, Error, Warning, Notification, Informational, Debugging. The thresholds behave like ACL filters: logging trap 4 means level 4 and more severe (0–4) are forwarded; a message at level 5 is below the threshold and is not forwarded. “Higher number, lower urgency” is the mental model.

The severity also behaves hierarchically: configuring a destination for severity 4 captures warnings, errors, critical, alert, and emergency messages because their numbers are ≤ 4. Debugging (7) is deliberately the noisiest and should never be shipped to production collectors.

In this lesson · select a part to jump

Reference table · select a row

Key ideas & exam traps · select one

Part 2

Anatomy of a syslog message

A Cisco syslog message has a fixed, structured head. Take this line:

*Jun 11 14:22:31.408: %SYS-5-CONFIG_I: Configured from console by console

Reading it left to right:

Definition — the facility-severity-mnemonic triplet The token Facility-Severity-Mnemonic is the address of an event in the Cisco logging taxonomy: which subsystem (SYS), how urgent (5), and which named event (CONFIG_I). Recognising this triplet lets you parse any log line even when the description is unfamiliar.

A classic event to recognise is the interface flap pair — %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down followed by %LINEPROTO-5-UPDOWN. Those two mnemonics (UPDOWN appearing in both LINK and LINEPROTO facilities) are a running joke in the exam because they appear in almost every infrastructure scenario.

Part 3

Where logs can go

IOS has three logging locations worth knowing (a fourth, the console, exists but is covered in the console-logging basics). Each has a different value:

Why a collector at all On-box logging (console/buffer) dies with the device: a router that powers off at 2 a.m. takes its buffer with it, and the console nobody watches records an unnoticed event. A central syslog server gives correlations across devices, longer retention, alerting, and archival — which is the reason the exam expects logging host in enterprise designs.
Part 4

Configuring logging on IOS

A minimal, realistic remote-logging configuration:

R1(config)# logging host 192.168.1.100
R1(config)# logging trap informational
R1(config)# logging source-interface gigabitEthernet 0/0
R1(config)# logging facility local7

Decode each line:

If you also want the on-box buffer with its own threshold (so show logging shows something even when the collector is unreachable):

R1(config)# logging buffered 65536
Buffer size and severity traps The argument to logging buffered is the buffer size in bytes (here 65,536) — an exam distractor will offer “65536 messages” or forget the size entirely. If you want a severity on the buffer, add it: logging buffered 65536 informational. And a running debug with a low threshold will fill any buffer in seconds — keep debugging out of the forwarded thresholds.
Part 5

Verifying with show logging

show logging is the one-stop verification command: it reports the configuration, the counters, and the buffered messages:

R1# show logging
Syslog logging: enabled (11 messages dropped, 4 messages rate-limited,
                0 flushes, 0 overruns, xml disabled, filtering disabled)

    Logging to: 192.168.1.100 (udp port 514, audit disabled,
                 link up, 3 messages logged, 0 lines logged, 0 xml rejected)
    Log Buffer (65536 bytes):
*Jun 11 14:21:19.192: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Jun 11 14:22:31.408: %SYS-5-CONFIG_I: Configured from console by console
Exam tip — what show logging reveals The first line answers “is logging even enabled?” The Logging to: block proves the collector line is up and shows how many messages made it. The buffer shows actual messages with timestamps, facility-severity-mnemonic, and description — exactly the reading skill from Section 2. If a scenario shows a collector that never receives logs, the three suspects are: logging disabled, threshold filtering the events, or UDP 514 blocked between the devices.

The drop and rate-limit counters in the first line are quietly important: IOS rate-limits chatty messages and drops when the pipeline can’t keep up. Non-zero drop counters with a healthy-looking config usually mean a burst of debugging or a badly-chosen threshold.

Router / switch console + RAM buffer messages from all facilities Syslog server listens on UDP 514 central archive + alerts forwarded when severity ≤ threshold e.g. logging trap informational events happen all day: %LINK-3-UPDOWN, %SYS-5-CONFIG_I…
Devices log continuously into console, buffer, and the network. Only messages at or below the configured severity threshold (6 informational here) are pushed to the collector on UDP 514; the RAM buffer keeps a recent copy on the device itself.
Part 6

Reading logs in practice

The skill the exam actually tests is decoding a line. Walk through three real shapes:

%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
%SYS-5-CONFIG_I: Configured from console by vty0 (192.168.1.50)
Interpreting “star time” The leading * before the timestamp means the device clock is not NTP-synchronised — the timestamps are only as trustworthy as the internal clock. If you see * on logs you are supposed to correlate, the fix is not log parsing, it is Lesson 10’s ntp server command. Synchronised devices print the date and time with no asterisk, and your forensic timeline suddenly lines up.

Troubleshooting decks love the summary: severity 0–2 need immediate attention, 3 is an actual error, 4 is the run-up to trouble, 5–6 are the normal rhythm of the network, and 7 is debugging noise. When an interface flaps and you must prove whether it is physical or the protocol, read the facility and mnemonic: LINK-3-UPDOWN versus LINEPROTO-5-UPDOWN is the definitive answer.

Key terms

The vocabulary you need

Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.

Key terms · select a term

Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 5 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics. cisco.com.
  2. IETF. Request for Comments (RFCs). rfc-editor.org.
  3. IANA. Internet Assigned Numbers Authority registries. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.