From: Ivan (ivan@iip.net)
Date: Wed Aug 30 2006 - 05:54:37 ART
I read somewhere - NTP-client can synchronize clock with server only if server
have greater than 2 associations. Try to add one more clock source to
Rack1R4. Just to test.
> Hi, I am having trouble with ntp peering across a frame-relay cloud. R3
> and R4 are connected via PPP over frame-relay. R4 is getting its time
> from 2x backbone routers successfully as seen in the output below, but
> when I try to get R3 to obtain its time from R4 it never syncs up. I have
> verified that there are no ACLs blocking traffic, also I have not applied
> the ntp access-group command yet. My configuration lines up with the
> solutions guide yet it still is not working for me. R3 uses its L0 for
> the source and I can ping R4's loopback sourced from R3's loopback. I
> tried to reload the routers and even run some debugs. I couldn't find
> anything from the debugs that would be helpful or maybe I just couldn't
> understand the output correctly. Also I made sure the times were close on
> both routers by manually setting the time on R3 and R4 is synced as I
> mentioned before. Can anyone see what might be wrong here?
> Rack1R4#sho run | i ntp
> ntp authentication-key 1 md5 106D202A2638 7
> ntp authenticate
> ntp trusted-key 1
> ntp server 192.10.1.254 key 1 prefer
> ntp server 204.12.1.254 key 1
> Rack1R4#sho clock
> 05:37:53.350 UTC Mon Mar 1 1993
> Rack1R4#sho ntp status
> Clock is synchronized, stratum 5, reference is 192.10.1.254
> nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
> 2**24
> reference time is AF3C1F43.93308071 (05:36:03.574 UTC Mon Mar 1 1993)
> clock offset is -120631.6448 msec, root delay is 3.72 msec
> root dispersion is 124512.82 msec, peer dispersion is 3881.13 msec
>
> Rack1R4#sho ntp associations address ref clock st when poll
> reach delay offset disp
> *~192.10.1.254 127.127.7.1 4 117 64 52 3.7 -12063
> 3881.1
> +~204.12.1.254 127.127.7.1 4 46 64 177 2.0 -11.20
> 128.3
> * master (synced), # master (unsynced), + selected, - candidate, ~
> configured ----------------R3 Output----------------- Rack1R3#sho run | i
> ntp
> ntp source Loopback0
> ntp server 150.1.4.4
> Rack1R3#ping 150.1.4.4 source 150.1.3.3Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 150.1.4.4, timeout is 2 seconds:
> Packet sent with a source address of 150.1.3.3
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 60/60/60 ms
> Rack1R3#sho ntp status
> Clock is unsynchronized, stratum 16, no reference clock
> nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is
> 2**24
> reference time is AF3C1063.EE4B1506 (04:32:35.930 UTC Mon Mar 1 1993)
> clock offset is -40341.9233 msec, root delay is 49.67 msec
> root dispersion is 56216.98 msec, peer dispersion is 16000.00 msec
>
> Rack1R3#sho ntp associations address ref clock st when poll
> reach delay offset disp
> ~150.1.4.4 204.12.1.254 5 22 64 0 49.6 120496
> 16000.
> * master (synced), # master (unsynced), + selected, - candidate, ~
> configured
> Rack1R3#sho clock
> .05:46:58.818 UTC Mon Mar 1 1993
>
> ------------------------------------------------------------------------
>
> Search from any web page with powerful protection. Get the FREE Windows
> Live Toolbar Today!
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
-- Ivan
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:59 ART