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

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

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

logging buffered

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.

2 REPLIES
Hall of Fame Super Silver

Re: logging buffered

Martin

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.

HTH

Rick

Re: logging buffered

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

--John

HTH, John *** Please rate all useful posts ***
419
Views
0
Helpful
2
Replies