Cisco Terminal Monitor and Logging Monitor

If you ever connected to a Cisco IOS device using the console, you might have noticed a message like this:

%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down

As you can probably guess from the output, the message indicates that the link connected to the GigabitEthernet0/0 interface went down. This message was shown to you because the logging console command is enabled by default for the console line and console logging. However, SSH and Telnet users will not be shown this message by default.


Terminal Monitor Command

After executing the terminal monitor EXEC command, the logging messages will also appear on the non-console terminal lines in the current terminal session. It will show system error messages, and display debug command output to monitor logs.

R1#terminal monitor


The command terminal no monitor disables the showing of the log messages. Notice that this is not the standard Cisco syntax – usually, the keyword ‘no’ goes in front of the command. We would usually expect the command to be no terminal monitor, but the correct command is actually terminal no monitor.


Logging Monitor Command

To enable system message logging to be shown in the terminal lines, another log monitoring command is the ‘logging monitor’. The command is entered in the global configuration mode, and the command syntax can include the severity level.

Router(config)#logging monitor 2

The terminal displays severity level 7 debugging messages and the other lower levels by default. To disable logging monitor, use the no form of the command.

Router(config)#no logging monitor

Download our Free CCNA Study Guide PDF for complete notes on all the CCNA 200-301 exam topics in one book.

We recommend the Cisco CCNA Gold Bootcamp as your main CCNA training course. It’s the highest rated Cisco course online with an average rating of 4.8 from over 30,000 public reviews and is the gold standard in CCNA training: