Curious thing in a Cisco router

Mailman List Mirror (Read Only)
1

While monitoring GMT Y2K progression on a Cisco router, something curious
showed up:

R6(11)-L16#sh clock
22:01:02.910 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
22:01:04.191 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
22:01:04.729 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
22:01:05.416 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
.22:08:22.460 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
.22:08:24.516 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
.22:08:35.599 Brazil/East(DST) Fri Dec 31 1999

Notice the dot before the time; it was not appearing before, and even on the
first sample after GMT Y2K-rollover (local time is GMT -0200). It now shows
up on every 'show clock'.

Any similar results on any other Cisco shop ?

Rubens Kuhl Jr.

2

I noticed the same thing...I haven't checked to see if that is affecting
logging in any way...

-David

3

check your NTP
-ron

4

<snip>

R6(11)-L16#sh clock
.22:08:22.460 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
.22:08:24.516 Brazil/East(DST) Fri Dec 31 1999
R6(11)-L16#sh clock
.22:08:35.599 Brazil/East(DST) Fri Dec 31 1999

Notice the dot before the time; it was not appearing before, and even on the
first sample after GMT Y2K-rollover (local time is GMT -0200). It now shows
up on every 'show clock'.

Any similar results on any other Cisco shop ?

According to IOS docs:

The system clock keeps an "authoritative" flag that indicates whether the
time is authoritative (believed to be accurate). If the system clock has
been set by a timing source (system calendar, NTP, VINES, and so forth),
the flag is set. If the time is not authoritative, it will be used only
for display purposes. Until the clock is authoritative and the
"authoritative" flag is set, the flag prevents peers from synchronizing to
the clock when the peers' time is invalid.

The symbol that precedes the show clock display indicates the following:

Symbol
       Description
* Time is not authoritative.
       Time is authoritative.
. Time is authoritative, but NTP is not synchronized

-axel

5

Not seeing it here:

sh clock

04:07:26.230 UTC Sat Jan 1 2000

reno uptime is 12 weeks, 10 hours, 24 minutes
System restarted by reload at 17:42:17 UTC Fri Oct 8 1999
System image file is "slot0:rsp-pv-mz.111-28.CC.bin", booted via slot0

Deepak Jain
AiNET