show logging
Shows the logging configuration for each destination and the messages held in the local log buffer.
Written by a working field network engineer · CCNA, Security+, CySA+
Shows where log messages go (console, terminal monitor, local buffer, syslog server), at what severity, and the contents of the local buffer. When something happened and nobody saw it, the buffer is where to look.
Example output
SW1#show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 14 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 14 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 14 message lines logged
Logging Source-Interface: VRF Name:
Log Buffer (4096 bytes):
Nov 10 07:12:41.207: %LINK-3-UPDOWN: Interface FastEthernet0/7, changed state to up
Nov 10 07:12:41.215: %LINK-3-UPDOWN: Interface FastEthernet0/8, changed state to up
Nov 10 07:12:43.221: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Nov 10 07:12:44.228: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
Nov 10 07:12:44.236: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to up
Nov 10 07:12:44.243: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Nov 10 07:12:47.519: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
Nov 10 07:12:48.526: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
Nov 10 07:13:02.884: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
Nov 10 07:13:03.891: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
Nov 10 07:13:05.112: %LINK-3-UPDOWN: Interface FastEthernet0/2, changed state to up
Nov 10 07:13:06.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2, changed state to up
Nov 10 07:14:20.330: %SYS-5-CONFIG_I: Configured from console by console
Nov 10 07:15:02.664: %SYS-5-CONFIG_I: Configured from console by consoleReference output: hand-written in standard Cisco IOS format for this example network, not captured from a device.
Useful variants
show logging | include LINK|LINEPROTOterminal monitor
What each column or field means
| Field | Meaning |
|---|---|
Syslog logging | Whether logging is enabled overall, with counters for dropped and rate-limited messages. |
Console / Monitor / Buffer logging | Each destination and the most detailed severity level it receives (0 emergencies to 7 debugging), with how many messages it has received. |
Trap logging | The severity sent to syslog servers; informational (6) by default. With a server configured, a “Logging to <host>” line per server follows. None is configured here, so messages stay on the switch. |
Log Buffer | The stored messages with timestamps, oldest first. Here SW1 coming up: the EtherChannel members and Po1, the uplink to R1, then PC1 and PC2. |
%LINK-3-UPDOWN / %LINEPROTO-5-UPDOWN | Facility, severity and mnemonic. LINK is Layer 1 (severity 3, errors); LINEPROTO is the line protocol (severity 5, notifications). |
When it doesn’t look right
The buffer is empty or disabled.
Enable it with logging buffered 16384 informational, so messages survive after they scroll off the console.
Timestamps are wrong or say uptime instead of time.
Configure NTP so clocks agree, and service timestamps log datetime msec localtime.
SSH users see no log messages.
Messages go to VTY sessions only after terminal monitor is entered in that session.
Related commands
Try it yourself
- Syslog & NTP Integration (Pro)
- NTP and Syslog Together (Pro)
- Free lab on this topic: Switch Management VLAN
- Or build the example network in the free Sandbox
Learn it in the CCNA path
- Syslog Operations & Severity Levels (4. IP Services)
Topic
Device Management — Read the configuration and software version, save changes, discover neighbors with CDP and LLDP, and check logging and time.