[j-nsp] MX series ntp clock issue ??

[Jared Mauch]

	If you adjust the time via 'set date ntp 0.us.pool.ntp.org.' 
(you may need ot use the IP, eg: 129.250.35.251) does it keep properly?

	- jared

On Mon, Jan 26, 2015 at 08:25:47AM -0700, John Brown wrote:
> HI,
> While trying track down another issue I went to make sure that the MX
> clock was correct.
> I'm a bit confused by the results.
> 
> Current time via "show system uptime" does NOT match the clock via
> "show ntp status"
> And the reftime in show ntp status and clock from the same aren't the same ?????
> 
> Thoughts, appreciated
> 
> 
> jmbrown at cr01.abq> show system uptime
> Current time: 2015-01-26 08:21:59 MST
> System booted: 2014-04-14 16:46:51 MDT (40w6d 16:35 ago)
> Protocols started: 2014-04-14 16:48:12 MDT (40w6d 16:33 ago)
> Last configured: 2015-01-26 08:14:40 MST (00:07:19 ago) by jmbrown
>  8:21AM  up 286 days, 16:35, 1 user, load averages: 0.06, 0.06, 0.01
> 
> jmbrown at cr01.abq> show ntp status
> status=0644 leap_none, sync_ntp, 4 events, event_peer/strat_chg,
> version="ntpd 4.2.0-a Fri Sep 13 01:28:39 UTC 2013 (1)",
> processor="amd64", system="JUNOS12.3R4.6", leap=00, stratum=3,
> precision=-21, rootdelay=67.766, rootdispersion=75.848, peer=3028,
> refid=216.243.112.132,
> reftime=d870d876.dd44b8d2  Mon, Jan 26 2015  8:15:02.864, poll=10,
> clock=d870da19.ba096ea4  Mon, Jan 26 2015  8:22:01.726, state=4,
> offset=4.583, frequency=16.045, jitter=1.354, stability=0.041
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.