logging buffered

Unanswered Question
Nov 14th, 2008
User Badges:

The configuration for logging on a 1841 router is as following:

router#sh log

Syslog logging: enabled (1 messages dropped, 2 messages rate-limited,

0 flushes, 0 overruns, xml disabled, filtering disabled)

Console logging: level debugging, 168 messages logged, xml disabled,

filtering disabled

Monitor logging: level debugging, 0 messages logged, xml disabled,

filtering disabled

Buffer logging: level debugging, 168 messages logged, xml disabled,

filtering disabled

Logging Exception size (4096 bytes)

Count and timestamp logging messages: disabled

On the serial interface counters for abort and carrrier transition are >1000 and >270, last clearing of counters was 1d6h ago.

Since the last clearing of counters there is absolutely no entry in the log.

Why? Were the carrier transitions / aborts to short for beeing recorded in the log or do we have to enable a "higher level" logging?

Thank you for the answer,

Martin Funke.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Richard Burts Fri, 11/14/2008 - 10:02
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN


By default things like aborts and carrier transitions do not generate log messages. Changing the logging severity level will not do you any good. I have not done it on a live router and can not speak from experience. But the documentation looks like configuring under the serial interface: logging event link-status may get you the log messages that you want.

Give it a try and let us know how it works.



John Blakley Fri, 11/14/2008 - 10:25
User Badges:
  • Purple, 4500 points or more

Rick is absolutely correct. That will log up/down changes.



This Discussion