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. And see here for current known issues.

New Member

log timestamps aren't the same as system/device time

i have a few devices, switches and routers, that when i do a "sh logg" the time stamp is different than the time the router has.

does anyone have a suggestion on how to fix this?

i pasted a quick example of what i'm talking about.

Jan 25 20:20:48.075: %SYS-5-CONFIG_I: Configured from console by grivers on vty1
Jan 25 20:22:49.659: %SYS-5-CONFIG_I: Configured from console by grivers on vty1
Jan 25 20:29:29.661: %SYS-5-CONFIG_I: Configured from console by grivers on vty1
KWCHSW27#sh cloc
14:34:10.545 Central Mon Jan 25 2010
KWCHSW27#

Thanks, Gary

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Silver

Re: log timestamps aren't the same as system/device time

Hello Gary,

adding the local-time option at the end of

service timestamps log|debug datetime

can be of help

Hope to help

Giuseppe

3 REPLIES
Hall of Fame Super Silver

Re: log timestamps aren't the same as system/device time

Hello Gary,

adding the local-time option at the end of

service timestamps log|debug datetime

can be of help

Hope to help

Giuseppe

New Member

Re: log timestamps aren't the same as system/device time

Thanks for the advice...

i tried both cmds but neither one corrected the time stamp.

i pasted an example of the output,

Jan 25 20:45:17: %SYS-5-CONFIG_I: Configured from console by grivers on vty0
6d22h: %SYS-5-CONFIG_I: Configured from console by grivers on vty0
Jan 25 20:46:13: %SYS-5-CONFIG_I: Configured from console by grivers on vty0
KWCHSW27#  sh clock
14:46:26.929 Central Mon Jan 25 2010
KWCHSW27#

it looks like the log is showing UTC.

New Member

Re: log timestamps aren't the same as system/device time

i re-read your reply and added "localtime" to the "service timestamps log datetime" cmd and it worked.

Thanks for your help.  Gary 

287
Views
0
Helpful
3
Replies