|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: Curious thing in a Cisco router
Where do you get that? The following certainly shows business as usual at
USNO and other time sources. Some are online and other aren't. The
preponderance of them are online and happy as clams. The MHSC time hosts are
stratum 2 and are unreachable from each other for a reason and have always
been that way. This shows that I have at least 3 stratum 1 hosts reachable
via NTP. In fact, I never showed a glitch. My information also shows that
WWV and WWVH never even hiccuped, I don't use GPS. LOCAL is a radio clock
that needs a new antenna lashup (way down on the budgetary priority list,
talk to my suits).
If a Cisco router is having a problem then it is either pilot error or
someone needs to be talking to Cisco. I doubt that Cisco is the problem. If
you need stable time references then TIME.MHSC.NET is running at stratum 2.
----------------------------------------------------------------------------
--
ntpq> pe
remote refid st t when poll reach delay offset
disp
============================================================================
==
LOCAL(0) .LCL. 0 l 34 64 377 0.00 0.000
10.01
tock.usno.navy. 0.0.0.0 16 u - 1024 0 0.00 0.000
16000.0
+tick.usno.navy. .USNO. 1 u 55 128 377 101.49 3.068
11.96
-tock.usno.navy. .USNO. 1 u 258 1024 377 156.88 27.304
25.67
+ntp2.usno.navy. ntp1.usno.navy. 2 u 8 128 377 101.59 -3.054
4.10
*clock.llnl.gov .WWVB. 1 u 3 128 277 37.14 -0.243
12.60
norad.arc.nasa. 0.0.0.0 16 u - 1024 0 0.00 0.000
16000.0
noc.svcs.mhsc.n 0.0.0.0 16 u - 1024 0 0.00 0.000
16000.0
condor.lvrmr.mh 0.0.0.0 16 u - 1024 0 0.00 0.000
16000.0
falcon.lvrmr.mh ntp0.usno.navy. 2 u 27d 1024 0 0.24 3.864
16000.0
raven.lvrmr.mhs falcon.lvrmr.mh 3 u 715 1024 377 0.56 -1.579
1.14
ntpq> q
[email protected]:/var/spool/mail
Sat Jan 1 14:14:17#>ntpq
ntpq> as
ind assID status conf reach auth condition last_event cnt
===========================================================
1 16028 f034 yes yes ok insane reachable 3
2 16029 8000 yes no
3 16030 9494 yes yes none synchr. reachable 9
4 16031 9394 yes yes none outlyer reachable 9
5 16032 9494 yes yes none synchr. reachable 9
6 16033 9674 yes yes none sys.peer reachable 7
7 16034 8000 yes no
8 16035 c000 yes no
9 16036 c000 yes no
10 16037 c043 yes no lost reach 4
11 16038 d034 yes yes bad insane reachable 3
ntpq> q
[email protected]:/var/spool/mail
Sat Jan 1 14:15:35#>
----------------------------------------------------------------------------
--
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On Behalf Of
> Sean Donelan
> Sent: Friday, December 31, 1999 8:10 PM
> To: [email protected]
> Subject: Re: Curious thing in a Cisco router
>
>
>
> At 10:17 PM -0200 12/31/99, Rubens Kuhl Jr. wrote:
> >While monitoring GMT Y2K progression on a Cisco router,
> something curious
> >showed up:
> [...]
> >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'.
>
> This doesn't seem to be a problem with cisco, but if you are
> synchronizing
> to certain NTP servers (i.e. usno or nist) they currently
> have reachability
> problems. So your cisco reports a "." that your ntp is
> unsynchronized.
>
> I haven't found out if the government networks are
> deliberately throttling
> traffic or if the links to the time servers are just congested.
>
> I have no idea why it started at almost exactly midnight UTC.
>
>
>
|