How to convert 1y8w: into normal timing

[atuldalvi]

Cat_3550#show logging

Syslog logging: enabled (0 messages dropped, 11 messages rate-limited, 0 flushes, 0 overruns)

Console logging: level debugging, 26755 messages logged

Monitor logging: level debugging, 0 messages logged

Buffer logging: level debugging, 26766 messages logged

Exception Logging: size (4096 bytes)

File logging: disabled

Trap logging: level informational, 26770 message lines logged

Log Buffer (4096 bytes):

o down

1y8w: %LINK-3-UPDOWN: Interface FastEthernet0/47, changed state to up

1y8w: %LINK-3-UPDOWN: Interface FastEthernet0/47, changed state to down

1y8w: %LINK-3-UPDOWN: Interface FastEthernet0/47, changed state to up

1y8w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/47, changed state to up

1y8w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/47, changed state to down

1y8w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/47, changed state to up

1y8w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/47, changed state to down

[Richard Burts]

Atul

The default for logging messages is to timestamp the message with the uptime (the amount of time since the router booted). The main reason for that is that some of the routers do not maintain the time over a reboot and since their clock was not reliable it was more meaningful to show uptime. If you want to have logging messages show the actual time it is done with the command service timestamps. This is the version of the command that I typically use:

service timestamps log datetime localtime show-timezone

It is helpful for the router to have a reliable setting of time. The most common solution for that is to configure NTP.

HTH

Rick

[atuldalvi]

Dear Rick,

Thanks a lot!!!

Regards

Atul