Re: NTP not sync

From: Jeff Szeto (jytszeto@hotmail.com)
Date: Thu Sep 05 2002 - 22:51:12 GMT-3


Hi Group,

Thank you for everyone's response.

When I add ntp master to R2, R1 is immediately sync with it.

I originally think ntp master is used in client-server mode. That is, I
should have some clients using "ntp server 'ip' " pointing to the master.
Now, I know I misunderstand this.

Regards,

Jeff
----- Original Message -----
From: "Nick Shah" <nshah@connect.com.au>
To: <Noel.MacFadden@swisscom.com>; <surendran_vangadasalam@non.hp.com>;
<jytszeto@hotmail.com>; <ccielab@groupstudy.com>
Sent: Friday, September 06, 2002 7:35 AM
Subject: Re: NTP not sync

> Noel
>
> Address 127.127.7.1 is the 'local' clock. Any router acting as 'master'
> clock must be synchronised with this address (meaning itself), only then
and
> then can any other client synchronise to it.
>
> Try this, deny this ip address in the 'serve' access-list, the local clock
> will not synchronise.
>
> rgds
> Nick
> ----- Original Message -----
> From: <Noel.MacFadden@swisscom.com>
> To: <surendran_vangadasalam@non.hp.com>; <jytszeto@hotmail.com>;
> <ccielab@groupstudy.com>
> Sent: Thursday, September 05, 2002 9:27 PM
> Subject: RE: NTP not sync
>
>
> > Hi:
> > Try checking the following
> > (1) Master clock set to a better stratum on server that
> > that of the client
> > (2) ntp broadcast on interface
> > (3) use debug ntp packet to ensure that ntp packets
> > are being sent and received.
> >
> > The config below is working, but I'm not saying its perfect, for e.g.
> > I cant figure out where the address 127.127.7.1 is coming from ????
> > I have set the source to the loopback address 133.8.1.1
> >
> > --------- Master Router R1: ----------------
> > int s0
> > ...
> > ntp broadcast
> >
> > ntp authentication-key 1 md5 104D000A0618 7
> > ntp authenticate
> > ntp source Loopback1
> > ntp access-group serve 3
> > ntp master 2
> > !
> > interface Loopback1
> > ip address 133.8.1.1 255.255.255.0
> >
> > r1#sh clock
> > 13:19:50.983 UTC Thu Sep 5 2002
> > r1#sh ntp assoc
> >
> > address ref clock st when poll reach delay offset
> disp
> > *~127.127.7.1 .LOCL. 1 27 64 377 0.0 0.00
> 0.0
> > * master (synced), # master (unsynced), + selected, - candidate, ~
> configured
> >
> > r1#sh ntp assoc det
> > 127.127.7.1 configured, our_master, sane, valid, stratum 1
> > ref ID .LOCL., time C121D860.3B90E118 (13:19:28.232 UTC Thu Sep 5 2002)
> > our mode active, peer mode passive, our poll intvl 64, peer poll intvl
64
> > root delay 0.00 msec, root disp 0.00, reach 377, sync dist 0.015
> > delay 0.00 msec, offset 0.0000 msec, dispersion 0.02
> > precision 2**18, version 3
> > org time C121D860.3B90E118 (13:19:28.232 UTC Thu Sep 5 2002)
> > rcv time C121D860.3B90E118 (13:19:28.232 UTC Thu Sep 5 2002)
> > xmt time C121D860.3B8D24CB (13:19:28.232 UTC Thu Sep 5 2002)
> > filtdelay = 0.00 0.00 0.00 0.00 0.00 0.00 0.00
> 0.00
> > filtoffset = 0.00 0.00 0.00 0.00 0.00 0.00 0.00
> 0.00
> > filterror = 0.02 0.99 1.97 2.94 3.92 4.90 5.87
> 6.85
> > Reference clock status: Running normally
> > Timecode:
> >
> > ----- Client Router R2
> > ntp authentication-key 1 md5 045802150C2E 7
> > ntp authenticate
> > ntp trusted-key 1
> > ntp clock-period 17179766
> > ntp server 133.8.1.1 key 1 source Loopback1
> > end
> >
> > r2#sh clock
> > 13:21:15.268 UTC Thu Sep 5 2002
> >
> > r2#sh ntp assoc
> >
> > address ref clock st when poll reach delay offset
> disp
> > *~133.8.1.1 127.127.7.1 2 10 64 177 35.5 0.06
> 125.2
> > * master (synced), # master (unsynced), + selected, - candidate, ~
> configured
> >
> > r2#sh ntp assoc det
> > 133.8.1.1 configured, authenticated, our_master, sane, valid, stratum 2
> > ref ID 127.127.7.1, time C121D8A0.3B89F899 (13:20:32.232 UTC Thu Sep 5
> 2002)
> > our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
> > root delay 0.00 msec, root disp 0.03, reach 177, sync dist 142.944
> > delay 35.51 msec, offset 0.0596 msec, dispersion 125.17
> > precision 2**19, version 3
> > org time C121D8C7.5434B78C (13:21:11.328 UTC Thu Sep 5 2002)
> > rcv time C121D8C7.58BC52B3 (13:21:11.346 UTC Thu Sep 5 2002)
> > xmt time C121D8C7.4F6B1903 (13:21:11.310 UTC Thu Sep 5 2002)
> > filtdelay = 35.51 35.72 35.68 35.77 37.92 35.80 35.68
> 0.00
> > filtoffset = 0.06 0.01 -0.20 -0.15 -1.34 0.10 0.12
> 0.00
> > filterror = 0.02 0.99 1.97 2.94 3.92 4.90 5.87
> 16000.0
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: VANGADASALAM,SURENDRAN (Non-HP-Singapore,ex4)
> > [mailto:surendran_vangadasalam@non.hp.com]
> > Sent: Donnerstag, 5. September 2002 12:07
> > To: 'Jeff Szeto'; 'ccielab@groupstudy.com'
> > Subject: RE: NTP not sync
> >
> >
> > Have you checked the timezone
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Jeff Szeto
> > Sent: 05 September 2002 17:12
> > To: ccielab@groupstudy.com
> > Subject: NTP not sync
> >
> >
> > Hi Group,
> >
> >
> > I want the R1 to synchronize with R2's clock, but it does not sync after
a
> > hour.
> >
> > Please give some advise.
> >
> > Thank you.
> >
> > Jeff
> >
> > R1's config:
> >
> > int e0
> > ip add 192.168.0.2 255.255.255.0
> >
> > ntp authentication-key 1 md5 13061E010803 7
> > ntp authenticate
> > ntp trusted-key 1
> > ntp peer 192.168.0.8 key 1
> >
> >
> > r1#sh clock
> > *02:52:17.079 UTC Mon Mar 1 1993
> > r1#sh ntp ass
> >
> > address ref clock st when poll reach delay offset
> > disp
> > ~192.168.0.8 0.0.0.0 16 16 64 0 0.0 0.00
> > 16000.
> > * master (synced), # master (unsynced), + selected, - candidate, ~
> > configured
> >
> >
> >
> > R2's config:
> >
> > int e0
> > ip add 192.168.0.8 255.255.255.0
> >
> > ntp authentication-key 1 md5 104D000A0618 7
> > ntp authenticate
> > ntp trusted-key 1
> > ntp peer 192.168.0.2 key 1 prefer
> >
> > r2#sh clock
> > .17:08:26.807 H Thu Sep 5 2002
> >
> > r2#sh ntp ass
> >
> > address ref clock st when poll reach delay offset
> > disp
> > ~192.168.0.2 0.0.0.0 16 - 64 0 0.0 0.00
> > 16000.
> > * master (synced), # master (unsynced), + selected, - candidate, ~
> > configured
> > r2#



This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:45 GMT-3