[ntp:questions] Re: where should we update sys_rootdispersion?
singh at image.dk
Tue Sep 9 10:09:13 UTC 2003
I am also doing some test with ntp on server and clients. I have to do the
tests manually, since I have not been able to automate the test procedure.
NTP provide very good statistics information, but it is difficult compare
this information with the setup parameter which is was made under.
I can see you have made some script. Is that some you can share with us. It
might give some ideas how-to automate the test procedures.
"Dongling Duan" <duan at cisco.com> wrote in message
news:3F5CD614.CF2F99A7 at cisco.com...
> Thanks David for your explanation!
> I have a script which has more than ten testcases using the topology I
> describe in previous email. I test all kinds of configuration and
> combination, server, peer, broadcast, with/without authentication etc.
> For each test, I reset clock to a random time on all box to see whether
> we are synced or not after some time. Some times offset could be very
> very big. Once it is synched, we check whether each peer is reached via
> Could somehow ntpd internal state fall into some state (sys_jitter is
> very big) because of all the configure/unconfigure, reset clock etc? So
> the ntpd just need more time to be sane?
> "David L. Mills" wrote:
> > Dongling,
> > Not every arriving packet results in a clock update. The clock filter
> > drops some that are older than the best recent packet. These drops are
> > revealed in the debug trace and are normal. The increased dispersion is
> > well below the cutoff limit.
> > I don't know what to tell you. I have duplicated your configuration here
> > and everything works gangbusters. You may need to look more closely at
> > the debug trace.
> > Sorry I can't include your message here; our NNTP server is extremely
> > fascist and insists the the quantity of reply exceed the quantity of
> > quote. I need to drop a hammer on the maintainer.
> > Dave
More information about the questions