Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Console Messages display

We have now upgraded from catOS to Cisco IOS. And now we have lost the ability to see on screen the messages that come up when we plug in or remove devices.

such as the pne below:

%PAGP-5-PORTFROMSTP:Port 4/13 left bridge port 4

%PAGP-5-PORTTOSTP:Port 4/13 joined bridge port 4

Please how can I re enable this on the Cisco IOS?


Cisco Employee

Re: Console Messages display

Have you entered the command "logging console" or "term mon"?

Also, what is the current logging level set to on the device? Is it higher or lower than level 5?

Hall of Fame Super Silver

Re: Console Messages display


Your description of the symptoms sounds like something is not set up in logging the way that you expect it. When you talk about messages on screen I am not clear whether you are talking about the console screen or if you are talking about seeing them when you telnet into the switch. Perhaps you can clarify this?

One thing that may explain your experience is that the catOS automatically displays log messages in a telnet session. In IOS you must use the terminal monitor command (a privelege mode command) to see the log messages in a telnet session.

It is also possible that logging may be configured differently - logging to certain destinations (console, monitor, logging host) may be enabled or disabled, and it is possible that the severity level has been set differently which can cause some messages to not be displayed. If you post the first screen of messages when you do show log, it will include information about how the various logging destinations are configured. This may help us find the resolution to your issue.



New Member

Re: Console Messages display

Thank you all very much.

Please find the 'sh log' attached. That is from 2 of the switches.

Yes, I want to see them when I telnet into the switches

Can I leave the terminal monitor command running or do i need to turn it off all the time after I issue it?

Will issuing terminal monitor cause an over run or use up memory? It did this on one of the routers and I had to reboot to clear this. If this should happen, what can I do?

Is it advisable to have console logging enabled?


Hall of Fame Super Silver

Re: Console Messages display


If you want to see the log messages in a telnet session on a device that is running IOS then you need to issue the terminal monitor command. I see no particular reason to turn it off after turning it on, other than a situation where the messages appearing on the screen are a distraction from other things that you are trying to do. Note that terminal monitor is a session specific command. When you establish a remote session you need to enable it. It will remain "on" for the duration of the session (unless you turn it off) and when the session terminates it goes off again. When you establish a new session it will be off until you enter the command again.

It is hard for me to imaging that turning on terminal monitor would cause any kind of over run or anything like that. I suspect that whatever was the problem that caused you to have to reboot was not turning on terminal monitor. It was more likely turning on debug for something that was very processor intensive. If anyone is going to run debug I sugest that they should set the console logging to severity level info (level 6) rather than the default of debug (level 7). Sending debug output to the console is the most impacting aspect of running debug. Debug is much less dangerous if the debug output is not sent to the console (which is the default).

Whether it is advisable to have console logging enabled depends mostly on whether there is anything connected to the console and whether anyone will be monitoring this. If there is a device connected which will display the log messages it may be desirable to have console logging enabled. I find at many of my customer sites that there is frequently not a device connected to the console and in that case there is no advantage to having console logging enabled. (I note that one of your switches does have console logging enabled and one does not. Was that on purpose?) And if you are going to enable console logging I suggest that you set the severity level to info (level 6).



New Member

Re: Console Messages display

Thank you so very much Rick

I can now see the logs in the syslog but not the pagp even though I have the below set

Console logging: disabled

Monitor logging: level debugging, 0 messages logged

Buffer logging: level debugging, 542 messages logged

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

Trap logging: level notifications, 495 message lines logged

Logging to x.x.x.x, 495 message lines logged.

So that when port are removed we are not able to track them and this is really what I want to be able to track whether on the screen or via the RME.



Re: Console Messages display

Hi ,

The Port Aggregation Protocol (PAgP) logging facility reports events involving PAgP, a protocol used to negotiate EtherChannel links between switches. The switch generates the %PAGP-5-PORTFROMSTP syslog message whenever a link is lost on a switch port. The switch generates the %PAGP-5-PORTTOSTP syslog message whenever a link is detected on a switch port. These syslogs are normal, informational messages indicating that a port was removed from or added to the spanning tree. Note that channeling does not have to be enabled for these messages to be


In the your case, the switch first lost the link on port 4/13 (removing the port from the spanning tree), and then again detected link on the port (adding the port back into the spanning tree).

If you see these messages frequently for a particular port, the link is flapping (losing and regaining link constantly) and you should investigate the cause.

Typical causes of link flapping on a switch port include the following:

* speed/duplex mismatch

* faulty cable

* faulty Network Interface Card (NIC) or other end station problem

* faulty switch port

* other misconfiguration

If you want to suppress these syslog messages, you can modify the logging level for the PAgP facility.

Hope this helps you.