09-16-2014 07:44 AM - edited 03-07-2019 08:46 PM
.... as show in the entries below:
*Feb 28 16:00:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/2, changed state to up
.Sep 16 06:28:01: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 164.72.58.198 Port 514 started - CLI initiated
.Sep 16 06:28:02: %LINK-3-UPDOWN: Interface Port-channel14, changed state to up
Sep 16 06:28:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel14, changed state to up
Solved! Go to Solution.
09-16-2014 08:05 AM
Asterisk(*):-
The datetime keyword adds time stamps in the format mmm dd hh:mm:ss, indicating the date and time according to the system clock. If the system clock has not been set, the date and time are preceded by an asterisk (*), which indicates that the date and time have not been set and should be verified.
The no form of the service timestamps command causes messages to be time-stamped in the default format.
Entering the service timestamps form of this command without any keywords or arguments is equivalent to issuing the service timestamps debug uptime form of this command.
Task ID
dot (.):-
The dot means the router has gone out of sync with its configured NTP server and therefore the date/time may be incorrect.
If it only happened for a short period then it may have been a network problem or problem on the NTP server where this router was unable to sync to it. If it is still happening do a "sho ntp assoc detail" and make sure it is in sync with the NTP server (sane/valid). If it isn't then you need to check your NTP server config, or perhaps there's a firewall in between that is blocking the NTP packets.
HTH
Inayath
********Plz dont forget to rate usefull posts.
09-16-2014 08:05 AM
Asterisk(*):-
The datetime keyword adds time stamps in the format mmm dd hh:mm:ss, indicating the date and time according to the system clock. If the system clock has not been set, the date and time are preceded by an asterisk (*), which indicates that the date and time have not been set and should be verified.
The no form of the service timestamps command causes messages to be time-stamped in the default format.
Entering the service timestamps form of this command without any keywords or arguments is equivalent to issuing the service timestamps debug uptime form of this command.
Task ID
dot (.):-
The dot means the router has gone out of sync with its configured NTP server and therefore the date/time may be incorrect.
If it only happened for a short period then it may have been a network problem or problem on the NTP server where this router was unable to sync to it. If it is still happening do a "sho ntp assoc detail" and make sure it is in sync with the NTP server (sane/valid). If it isn't then you need to check your NTP server config, or perhaps there's a firewall in between that is blocking the NTP packets.
HTH
Inayath
********Plz dont forget to rate usefull posts.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide