They are backwards each time. Both Ciscos ate set to the same sources so
strata should be the same but I will check.

-Ty
On Mar 31, 2014 5:39 PM, "Scott Lambert" <[email protected]> wrote:

> On Mon, Mar 31, 2014 at 03:02:37PM -0500, Ty Featherling wrote:
> > I just went through my routers and was changing the NTP client settings.
> I
> > have NTP servers on both of my edge Cisco routers. I added both as
> primary
> > and secondary on all routers making sure to put the nearer router as
> > primary on every one. Time and again I kept seeing the client report that
> > it got it's update from the secondary server. The primary was available
> and
> > in many cases was many hops nearer with faster response to boot. Is this
> > some bug I have discovered? These routers are more likely to lose contact
> > with their secondary NTP server than the primary; that is why I set them
> > that way. So why chose the 2nd over the 1st?
>
> The secondary may be at a lower (numerically) stratum because it's
> reference clock is of a lower stratum.
>
> I don't know if MikroTik is running ntpd or just ntpdate on a schedule,
> or if they are even using the ntp.org software at all.  I think both
> ntp.org based options chose the "best" server rather than caring about
> the order in which the possible servers are specified.  I believe
> stratum 1 is considered "better" than stratum 2 even if there is a bit
> more network delay to reach the stratum 1 server.
>
> Is it always the same Cisco being chosen?
>
> Can you take out the further away Cisco and get time from the nearer
> Cisco?
>
> router-7204#show ntp status
> Clock is synchronized, stratum 4, reference is xxx.yyy.34.40
> nominal freq is 250.0000 Hz, actual freq is 249.9955 Hz, precision is 2**18
> reference time is D6E468E3.2C713C80 (17:21:23.173 CDT Mon Mar 31 2014)
> clock offset is 2.0125 msec, root delay is 90.61 msec
> root dispersion is 41.40 msec, peer dispersion is 1.89 msec
>
> router-7204#show ntp associations
>
>       address         ref clock     st  when  poll reach  delay  offset
>  disp
> +~xxx.yyy.34.35    67.18.187.111     3   871  1024  377     0.5    5.73
>   1.4
> +~xxx.yyy.34.36    206.209.110.2     3   613  1024  377     0.7   -2.52
>   0.1
> *~xxx.yyy.34.40    71.19.144.130     3   603  1024  377     0.6   -0.89
>   0.7
>  * master (synced), # master (unsynced), + selected, - candidate, ~
> configured
>
> Look at that output on both Ciscos and you will probably have your
> answer.
>
>
> --
> Scott Lambert                    KC5MLE                       Unix SysAdmin
> [email protected]
> _______________________________________________
> Mikrotik mailing list
> [email protected]
> http://mail.butchevans.com/mailman/listinfo/mikrotik
>
> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> RouterOS
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.butchevans.com/pipermail/mikrotik/attachments/20140331/fd26db58/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

Reply via email to