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

Error Logs

This is the error log of a Cisco 1841 device :

Syslog logging: enabled (0 messages dropped, 3 messages rate-limited,
                0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

 

No Inactive Message Discriminator.


    Console logging: disabled
    Monitor logging: disabled
    Buffer logging:  level debugging, 76 messages logged, xml disabled,
                     filtering disabled
    Logging Exception size (4096 bytes)
    Count and timestamp logging messages: disabled
    Persistent logging: disabled

No active filter modules.

ESM: 0 messages dropped

    Trap logging: level informational, 77 message lines logged
          
Log Buffer (4096 bytes):
otocol on Interface Async0/1/0, changed state to up
Oct  7 15:47:17.769 EDT: %LINK-5-CHANGED: Interface Async0/1/0, changed state to reset
Oct  7 15:47:18.769 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to down
Oct  7 15:47:22.773 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to down
Oct  7 15:48:05.497 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to up
Oct  7 15:48:06.497 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to up
Oct  7 16:01:37.712 EDT: %LINK-5-CHANGED: Interface Async0/1/0, changed state to reset
Oct  7 16:01:38.712 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to down
Oct  7 16:01:42.715 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to down
Oct  7 16:02:21.837 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to up
Oct  7 16:02:22.836 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to up
Oct  7 17:20:35.361 EDT: %LINK-5-CHANGED: Interface Async0/1/0, changed state to reset
Oct  7 17:20:36.361 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to down
Oct  7 17:20:40.365 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to down
Oct  7 17:21:23.597 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to up
Oct  7 17:21:45.724 EDT: %LINK-5-CHANGED: Interface Async0/1/0, changed state to reset
Oct  7 17:21:50.727 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to down
Oct  7 17:24:13.192 EDT: %LINK-3-UPDOWN: Interface Async0/1/0, changed state to up
Oct  7 17:24:14.192 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async0/1/0, changed state to up
Oct  8 12:23:06.679 EDT: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
Oct  8 12:23:07.679 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
Oct  8 15:11:02.345 EDT: %CLEAR-5-COUNTERS: Clear counter on all interfaces by rg87456 on vty0 (192.94.141.89)
Oct  8 17:26:05.941 EDT: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to down
Oct  8 17:26:06.941 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to down
Oct  9 10:24:25.357 EDT: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
Oct  9 10:24:26.357 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
Oct  9 11:03:43.323 EDT: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to down
Oct  9 11:03:44.323 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to down
Oct  9 12:19:16.193 EDT: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
Oct  9 12:19:17.193 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
Oct  9 12:42:11.260 EDT: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to down
Oct  9 12:42:12.260 EDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to down
Oct  9 12:59:54.196 EDT: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up

Is there any way to view the logs before 7th Oct?

 

4 REPLIES
Hall of Fame Super Silver

Your logging buffer is quite

Your logging buffer is quite small (4096 bytes) and it operates as a wrap around so that when it has gotten full and a new log message is written then oldest data is written over. so in this case I do not see any way to see messages before 7th Oct.

 

You might consider making the logging buffer larger so that more messages can be retained before they are written over (On 1841 routers I have frequently set the logging buffer to 65536). And if seeing older message is something you want then you should consider using a logging server which could receive and store the syslog messages from the router.

 

HTH

 

Rick

New Member

Hello Richard, Thank you very

Hello Richard,

 Thank you very much. I appreciate your help. That was very helpful.

Thanks,

Anilkumar

 

Super Bronze

DisclaimerThe Author of this

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

Don't believe so, but going forward you can increase the size of your device log and/or send to an external syslog server.

New Member

So logging server is the only

So logging server and increasing the buffer size are the options I have got. Thank You :-) 

86
Views
0
Helpful
4
Replies