one question for ntp

[lit]

Hi,
when i runing ntp in my host , it's not work:
kkk:/var/adm#ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
10.243.1.193 0.0.0.0 16 u 40 64 0 0.00 0.000 16000.0

ntpdate -d 10.243.1.193,following result:

/var/adm#ntpdate -d 10.243.1.193
transmit(10.243.1.193)
receive(10.243.1.193)
transmit(10.243.1.193)
receive(10.243.1.193)
transmit(10.243.1.193)
receive(10.243.1.193)
transmit(10.243.1.193)
receive(10.243.1.193)
transmit(10.243.1.193)
server 10.243.1.193, port 123
stratum 16, precision -18, leap 00, trust 000
refid [211.136.70.97], delay 0.02763, dispersion 0.00002
transmitted 4, in filter 4
reference time: c2d3c786.e0901000 Fri, Aug 1 2003 0:51:18.877
originate timestamp: c390e8e4.deb04000 Mon, Dec 22 2003 11:52:04.869
transmit timestamp: c390e8d9.2c8e0000 Mon, Dec 22 2003 11:51:53.174
filter delay: 0.02809 0.02765 0.02763 0.02769
0.00000 0.00000 0.00000 0.00000
filter offset: 11.69494 11.69479 11.69478 11.69475
0.000000 0.000000 0.000000 0.000000
delay 0.02763, dispersion 0.00002
offset 11.694781

22 Dec 11:51:53 ntpdate[7424]: no server suitable for synchronization found

ntptrace command:
kkk:/#ntptrace 10.243.1.193
10.243.1.193: stratum 16, offset 11.672237, synch distance 142.07112
211.136.70.97: *Timeout*

so, here i have a question:if the reference host(211.136.70.97) can't work normal, can i get the time from the ntp server which ntp.conf
point to?

br,tianlit

[RAC_1]

You are having the problems reaching to ntp server. (10.243.1.193). The problem is at 211.136.70.97.

If you are not reaching to 10.243.1.193, you can not put it in /etc/ntp.conf.

Find some other time source. You can also use any system in your setup which has got good stable clock.

[lit]

but i can ping or telnet 10.243.1.193.
(the 211.136.70.97 is a outer ntp server and now can't work)

[RAC_1]

You are having problems reaching 211.136.70.97.

Put 10.243.1.193 as you ntp server in /etc/ntp.conf. And you are done. start ntp
/sbin/init.d/xntp.

Also keep checking for any erros in syslog.

If the offset is very high, it may stop working.

[Bob_Vance · Accepted solution]

The problem is at 10.243.1.193, not 211.136.70.97, at least as far as your local server is concerned.

10.243.1.193 is not synchronized to a NTP server (at least one of which is 211.136.70.97) and, therefore, is not a "suitable" server for your local NTP to use.

If you can, log on to 10.243.1.193 and run

/usr/sbin/ntpq -p

This will show the status of the NTP server at 10.243.1.193 vis-a-vis *its* servers.

It appears that 10.243.1.193 is configured to use 211.136.70.97 (which is a "real" Internet address -- authority is "apnic.net"), but, as far as I can tell, 211.136.70.97 does not exist. It does not resolve and it does not respond to pings or NTP requests.

Fix the NTP configuration at 10.243.1.193.


bv