Timestamp on debug 1

[snootalope]

I've got a debug running on a 2811 router that's dumping it's info off to a syslog server. Both devices sit in the same office..

For some reason, the timestamp on the debug messages is ahead of the clock by 5 hours. The "sho clock" on the router shows the time is accurate.

I can't figure out why this is... help?

 

[burtsbees]

Is the computer clock different? Do you authenticate NTP with an NTP server? Do you have the clock-summertime and timezone correct (-5, -6, etc.)?

Burt

 

[snootalope]

Clocks are the same on the host and router. Same time, timezone, etc.

From what I can tell, I've got the router clock config setup correctly. It does sync with another router that is set as our domains ntp server. I'm assuming that one is fine as well as every device in our domain would be out of whack if the routers ntp config wasn't correct.

I've went back through and setup the routers ntp again and made sure it's correct, still getting the 5 hour time difference though...

 

[burtsbees]

Post a config. Also, can you install something like Kiwi syslog on that server, as well as another server, and test them? That will narrow it down to the app,the server, or the router.

Burt

 

[snootalope]

Here's parts of the config that concern time and the syslog:

!
clock timezone Central -6
clock summer-time Central recurring
!
!
logging trap debugging
logging 10.10.1.16
!

Show clock detail:
11:14:36.569 Central Fri Oct 10 2008
Time source is NTP
Summer time starts 02:00:00 Central Sun Mar 9 2008
Summer time ends 02:00:00 Central Sun Nov 2 2008

I'll try another syslog server and see what happens.

 

[snootalope]

yep...same results on another syslog server. time is ahead by five hours.

 

[snootalope]

Ok, found the fix.. should have done just a bit more googleing..

service timestamps debug datetime localtime

 

[vipergg]

I have seen that , what the syslog server does is timestamp the logs coming in with the local time on the server itself , ours are the same way . Not sure how you get around that , don't think its a switch or router issue though, would have to figure out something on the server end .