Options

Logging buffer time is 24 hours?

phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
in CCNA & CCENT
Is it possible to set the logging buffer timestamp to 12-hour clock instead of 24-hour clock?
Feb 18 19:48:33.223: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
Feb 18 19:48:33.251: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
Feb 18 19:48:34.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
Feb 18 19:48:34.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
R1#sh clock
11:49:14.763 GMT Thu Feb 18 2010
R1#
· Share on FacebookShare on Twitter

Comments

  • Options
    tierstentiersten Member Posts: 4,505
    Don't think you can. Why do you want to anyway?
    · Share on FacebookShare on Twitter
  • Options
    phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
    tiersten wrote: »
    Don't think you can. Why do you want to anyway?

    So I know what time an interface actually went down instead of guessing.
    *Feb 18 19:26:18.898: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 19:26:18.902: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 19:27:12.566: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 19:27:12.590: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 19:27:13.586: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 19:27:13.602: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Feb 18 19:29:33.278: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
*Feb 18 19:29:33.282: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Feb 18 19:29:34.278: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 19:29:34.282: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 19:30:05.226: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 19:30:05.250: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 19:30:06.242: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 19:30:06.254: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Feb 18 19:30:49.102: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
*Feb 18 19:30:49.106: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Feb 18 19:30:50.102: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 19:30:50.106: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 19:48:10.122: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 19:48:10.150: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 19:48:11.142: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 19:48:11.154: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Feb 18 19:48:24.270: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
*Feb 18 19:48:24.274: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Feb 18 19:48:25.270: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 19:48:25.274: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 19:49:30.650: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 19:49:30.674: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 19:49:31.670: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 19:49:31.682: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Feb 18 19:53:22.250: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
*Feb 18 19:53:22.254: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Feb 18 19:53:23.250: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 19:53:23.254: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 19:54:01.206: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 19:54:01.230: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 19:54:02.226: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 19:54:02.238: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Feb 18 19:57:34.262: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
*Feb 18 19:57:34.266: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Feb 18 19:57:35.262: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 19:57:35.266: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 19:58:06.262: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 19:58:06.290: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 19:58:07.286: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 19:58:07.298: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Feb 18 20:03:21.090: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
*Feb 18 20:03:21.094: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Feb 18 20:03:22.090: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 20:03:22.094: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 20:03:57.502: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 20:03:57.530: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 20:03:58.522: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 20:03:58.534: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Feb 18 20:04:07.674: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
*Feb 18 20:04:07.678: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Feb 18 20:04:08.674: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to down
*Feb 18 20:04:08.678: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Feb 18 20:04:39.674: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to up
*Feb 18 20:04:39.702: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Feb 18 20:04:40.698: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0, changed state to up
*Feb 18 20:04:40.710: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
    · Share on FacebookShare on Twitter
  • Options
    tierstentiersten Member Posts: 4,505
    phoeneous wrote: »
    So I know what time an interface actually went down instead of guessing.
    What is there to guess? It tells you exactly when the interface status changed.

    You can either do the timezone offset in your head or set the correct timezone for your router. You'd still need to read the 24 hour clock though.
    · Share on FacebookShare on Twitter
  • Options
    networker050184networker050184 Mod Posts: 11,962 Mod
    Guess? Just find out how far off local time is from GMT and convert that to 12 hour format.
    An expert is a man who has made all the mistakes which can be made.
    · Share on FacebookShare on Twitter
  • Options
    Forsaken_GAForsaken_GA Member Posts: 4,024
    or just set the timezone correctly and use an ntp source to get the current time:

    clock timezone EST -5
    clock summer-time EDT recurring

    dorne#sho clock detail
    16:14:26.330 EST Thu Feb 18 2010
    Time source is NTP
    Summer time starts 02:00:00 EST Sun Mar 14 2010
    Summer time ends 02:00:00 EDT Sun Nov 7 2010
    · Share on FacebookShare on Twitter
  • Options
    phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
    tiersten wrote: »
    What is there to guess? It tells you exactly when the interface status changed.

    You can either do the timezone offset in your head or set the correct timezone for your router. You'd still need to read the 24 hour clock though.

    But I hate 24-hour clock icon_sad.gif
    · Share on FacebookShare on Twitter
  • Options
    Forsaken_GAForsaken_GA Member Posts: 4,024
    doesn't appear to be an option to turn it to the 12 hour clock, so if it's greater than 12, just subtract twelve, and that's what time it is in the PM. it's alot easier than doing decimal to binary or hex conversions in your head hehe
    · Share on FacebookShare on Twitter
  • Options
    phoeneousphoeneous Member Posts: 2,333 ■■■■■■■□□□
    Forsaken_GA wrote: »
    doesn't appear to be an option to turn it to the 12 hour clock, so if it's greater than 12, just subtract twelve, and that's what time it is in the PM. it's alot easier than doing decimal to binary or hex conversions in your head hehe

    I know, I'm just being lazy today. Thanks for checking on that though.
    · Share on FacebookShare on Twitter
Sign In or Register to comment.