From: Tasuka Amano Hsu (tasuka@mac.com)
Date: Mon Dec 09 2002 - 00:59:17 GMT-3
I suggest you modify at r2(ntp master)
ntp master 1
for local sync for lower stratum 1, the default is 8,
and add to r5 (ntp client)
ntp server 10.10.10.1 prefer
it mean you will sync time via ntp with the ntp server 10.10.10.1 as
your time source.
And you also need to change the clock timezone or you want the router
run at UCT timezone.
Best Regards
tasuka
On Wednesday, Dec 4, 2002, at 10:46 Asia/Taipei, John Tafasi wrote:
> Hi group,
>
> I have r2 (ntp server) and r5 (ntp client) exchnaging (or supposed to)
> ntp
> information accross an isdn link. r2 is configured to broadcast ntp
> packets
> via its bri0 interface and is doing so sucessfully. r5 is receiving
> the ntp
> packets but the "debug ntp packets" on r5 does not produce any output.
> I can
> see the packets arriving at r5 from the output of the "debug ip
> packet" on
> r5. r5 stil not synchronized. what is the problem?How ntp broadcast
> should
> be configured for this to be successfull? Has any one tried this on an
> ethernet segment? I have a feeling that ntp broadcast will not work on
> an
> isdn link
>
> I have included the following snippet from both routers'
> configuration. Also
> bear in mind that I am connected to both routers through the console.
> Thank
> you for any comment
>
> hostname r2-2516
> !
> interface BRI0
> no ip address
> no ip directed-broadcast
> encapsulation ppp
> dialer pool-member 1
> isdn spid1 0835866101
> isdn spid2 0835866301
> !
> interface Dialer1
> ip address 10.10.10.1 255.255.255.0
> no ip directed-broadcast
> encapsulation ppp
> dialer remote-name r5
> dialer idle-timeout 2147483
> dialer string 8358662
> dialer pool 1
> dialer-group 1
> ntp broadcast
> pulse-time 0
> ppp chap hostname r2
> !
> !
> ntp clock-period 17179826
> ntp master
> end
>
> r2-2516#show ntp status
> Clock is synchronized, stratum 8, reference is 127.127.7.1
> nominal freq is 250.0000 Hz, actual freq is 250.0006 Hz, precision is
> 2**19
> reference time is C197833E.E008EAFC (19:23:42.875 UTC Tue Dec 3 2002)
> clock offset is 0.0000 msec, root delay is 0.00 msec
> root dispersion is 0.02 msec, peer dispersion is 0.02 msec
>
> r2-2516#show ntp associations
>
> address ref clock st when poll reach delay offset
> disp
> *~127.127.7.1 127.127.7.1 7 55 64 377 0.0 0.00
> 0.0
> * master (synced), # master (unsynced), + selected, - candidate, ~
> configured
> r2-2516#
>
> ==================
>
> hostname R5-2503
> !
> interface BRI0
> ip address 10.10.10.2 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 2147483
> dialer map ip 10.10.10.1 name r2 broadcast 8358661
> dialer-group 1
> isdn switch-type basic-ni
> isdn spid1 0835866201
> isdn spid2 0835866401
> cdapi buffers regular 0
> cdapi buffers raw 0
> cdapi buffers large 0
> ppp authentication chap
> ppp chap hostname r5
> ppp multilink
> !
> ntp clock-period 17179601
> end
>
> R5-2503#show ntp stat
> Clock is unsynchronized, stratum 16, no reference clock
> nominal freq is 250.0000 Hz, actual freq is 250.0039 Hz, precision is
> 2**19
> reference time is AF3BF1EE.0D8B939B (02:22:38.052 UTC Mon Mar 1 1993)
> clock offset is 0.0000 msec, root delay is 0.00 msec
> root dispersion is 0.02 msec, peer dispersion is 0.02 msec
> R5-2503#
>
> R5-2503#show ntp associ
>
> address ref clock st when poll reach delay offset
> disp
> * master (synced), # master (unsynced), + selected, - candidate, ~
> configured
> R5-2503#
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:41 GMT-3