On Thursday, January 23, 2014 3:04:01 PM UTC+1, blu wrote: > What version of Solaris were you using? If you were using Solaris 10, > > then the ntptrace command is the old version that uses the ref field as > > the IPv4 address of the server. Since it does not rely on control or > > private packets it can work even if "noquery" was specified on one of > > the servers in the chain. Since the ref field cannot hold an IPv6 > > address, the ntptrace program was changed in NTP version 4 to use > > control packets to find out the IP address of each server. This works > > with both IPv4 and IPv6, but requires all the servers to allow control > > packets. > > > > On 1/23/2014 2:52 AM, ardi wrote: > > > I have tried to set up 3-level for ntp-setting: > > > > > > xx.xx.xx.aa stratum 1 server (taking time from GPS) > > > ------------------------------------------------------- > > > xx.xx.xx.b1 > > > xx.xx.xx.b2 are stratum 2 servers acting as ntp-servers > > > -------------------------------------------------------- > > > xx.xx.xx.c1 > > > xx.xx.xx.c2 are stratum 3 ntp-clients > > > -------------------------------------------------------- > > > > > > > > > NOTE: all clients have stratum 2 servers defined as ntp-server time sources. > > > > > > a) > > > when doing ntptrace from a client (without parameter), > > > I am getting Timed out : > > > > > > NOK: > > > client.c1 # ntptrace > > > localhost: stratum 3, offset -0.000033, synch distance 0.000230 > > > xx.xx.xx.b1: timed out, nothing received > > > ***Request timed out > > > client.c1 # > > > > > > NOK: > > > client.c1 # ntptrace xx.xx.xx.b1 #towards stratum 2 server > > > xx.xx.xx.b1: timed out, nothing received > > > ***Request timed out > > > > > > OK: > > > client.c1 # ntptrace xx.xx.xx.aa #stratum 1 ntp-server > > > aa.dfdsf.sdff.lab: stratum 1, offset -0.000002, synch distance 0.000000, > > refid 'GPS' > > > client.c1 # > > > > > > doing it from another client, which is solaris: > > > > > > OK: > > > bash-3.00# ntptrace > > > localhost: stratum 3, offset 0.000026, synch distance 0.01694 > > > xx.xx.xx.b1: stratum 2, offset 0.000160, synch distance 0.00133 > > > aa.dfdsf.sdff.lab: stratum 1, offset 0.000315, synch distance 0.00021, > > refid 'GPS' > > > bash-3.00# > > > > > > NOTE: > > > for xx.xx.xx.b1 the first line of ntp.conf is the following: > > > > > > restrict default noquery nomodify notrap > > > > > > b) > > > when i remove noquery parameter on stratum 2 ntp-server xx.xx.xx.b1 and > > restart ntpd: > > > > > > for xx.xx.xx.b1 the first line of ntp.conf is the following: > > > > > > restrict default nomodify notrap > > > > > > then ntptrace from client.c1 is ok > > > > > > What causes that solaris clients work in both cases > > > and for client.c1 only in case, when noquery is removed from stratum 2 > > server? > > > > > > Peter > > > > > > _______________________________________________ > > > questions mailing list > > > questions@lists.ntp.org > > > http://lists.ntp.org/listinfo/questions
I have been using 2 unix clients: solaris 8, and solaris 10. Below is the output of ntpdc on xx.xx.xx.b1 ntp-server: ntpdc> monlist remote address port local address count m ver rstr avgint lstint =============================================================================== xx.xx.xx.aa 123 xx.xx.xx.b1 6298 4 4 0 15 5 xx.xx.xx.b2 123 xx.xx.xx.b1 6297 1 4 1c0 15 13 xx.xx.xx.c1 123 xx.xx.xx.b1 6171 3 4 1c0 16 34 xx.xx.xx.c1 123 xx.xx.xx.b1 5787 3 4 1c0 17 253 solaris8 123 xx.xx.xx.b1 104 3 3 1c0 967 317 solaris10 123 xx.xx.xx.b1 133 3 3 1c0 750 337 ntpdc> I presume, column "ver" shows the ntp version.(3 for both solaris clients) What do other columns mean? I presume "rstr" means relative stratum: 0 means xx.xx.xx.aa is above xx.xx.xx.b1 1c0 means all others are clients 1 level lower to xx.xx.xx.b1. Is that so? Peter _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
