NTP sync

[wim_depauw]

Hi,

I have a switch placed at a customer which should get the correct date from our ATM router . Unfortunately I always get the following message :

172.30.1.10 configured, insane, invalid, stratum 3

ref ID 62.233.0.1, time C54F0E70.0410788B (14:43:12.015 GMT Wed Nov 24 2004)

our mode client, peer mode server, our poll intvl 1024, peer poll intvl 1024

root delay 1.10 msec, root disp 1903.67, reach 377, sync dist 1907.700

delay 6.82 msec, offset 293005.6117 msec, dispersion 0.08

precision 2**18, version 3

org time C54F0F38.D66FD7E1 (14:46:32.837 GMT Wed Nov 24 2004)

rcv time C54F0E13.D5DFCDAB (14:41:39.835 GMT Wed Nov 24 2004)

xmt time C54F0E13.D41FAC94 (14:41:39.828 GMT Wed Nov 24 2004)

filtdelay = 6.82 6.87 6.87 6.91 6.85 7.72 6.70 6.91

filtoffset = 293005. 293005. 293005. 293005. 293005. 293005. 293005. 293005.

filterror = 0.02 0.03 0.05 0.06 0.08 0.09 0.11 0.12

When I debug I get the following :

35w0d: NTP: xmit packet to 172.30.1.10:

35w0d: leap 3, mode 3, version 3, stratum 0, ppoll 64

35w0d: rtdel 0000 (0.000), rtdsp 10001 (1000.015), refid 00000000 (0.0.0.0)

35w0d: ref 00000000.00000000 (01:00:00.000 GMT Mon Jan 1 1900)

35w0d: org 00000000.00000000 (01:00:00.000 GMT Mon Jan 1 1900)

35w0d: rec 00000000.00000000 (01:00:00.000 GMT Mon Jan 1 1900)

35w0d: xmt C54F0E04.D46E310C (14:41:24.829 GMT Wed Nov 24 2004)

35w0d: NTP: rcv packet from 172.30.1.10 to 193.108.215.91 on Vlan2:

35w0d: leap 0, mode 4, version 3, stratum 3, ppoll 64

35w0d: rtdel 0048 (1.099), rtdsp 1E757 (1903.671), refid 3EE90001 (62.233.0.1)

35w0d: ref C54F0E70.0410788B (14:43:12.015 GMT Wed Nov 24 2004)

35w0d: org C54F0E04.D46E310C (14:41:24.829 GMT Wed Nov 24 2004)

35w0d: rec C54F0F29.D6C40B8D (14:46:17.838 GMT Wed Nov 24 2004)

35w0d: xmt C54F0F29.D6C4BC2F (14:46:17.838 GMT Wed Nov 24 2004)

35w0d: inp C54F0E04.D64600B8 (14:41:24.837 GMT Wed Nov 24 2004)

35w0d: NTP: xmit packet to 172.30.1.10:

Does anybody know what the problem is ? Is it possible to sync over an ATM network ?

[Richard Burts]

I recently saw symptoms in the network at a customer site which were similar. In our case there turned out to be some connectivity issues which caused significant packet loss. Can you verify the connectivity (extended ping with lots of packets or something like that)?

I am not aware of anything about ATM that would impact the ability to sync NTP over ATM.

HTH

Rick

[wim_depauw]

Hi,

I've tested it with an extended ping but this works fine . I already checked the switch ports with MRTG but is isn't so that the line is fully occupied .

I'll try to take another source on the internet and see if this works .

thx

wim