From: Tony Paterra (apaterra@gmail.com)
Date: Wed Sep 20 2006 - 21:34:31 ART
Nevermind, it just dawned on me. I was playing with some IP
addressing (practicing being on different racks) and didn't have a
route to the Loopback address.
Sorry!
On 9/20/06, Tony Paterra <apaterra@gmail.com> wrote:
> All,
> I was playing around with NTP and I noticed the following behavior
> when synching to a backbone router...
>
> When I take my client and set him up to use the BB router as a master,
> I am only able to get my router to synch if I do not change his source
> interface. There are no access-groups set on the master/server and I
> can see traffic being sent through the debugs (but no synch happens).
>
> Config 1 works, Config 2 doesn't (and I definitely left a lot of time
> in each test case for it to synch)... Any thoughts?
>
>
> Backbone config
> ------------------------
> ntp authentication-key 1 md5 106D202A2638 7
> ntp master 4
>
>
> Config 1
> -----------
> ntp authentication-key 1 md5 05282F3C0263 7
> ntp authenticate
> ntp trusted-key 1
> ntp clock-period 17179925
> ntp server 204.12.1.254 key 1
>
> Config 2
> -----------
> ntp authentication-key 1 md5 05282F3C0263 7
> ntp authenticate
> ntp trusted-key 1
> ntp clock-period 17179925
> ntp server 204.12.1.254 key 1
> ntp source Loopback0
>
>
> --
> Tony Paterra
> apaterra@gmail.com
>
-- Tony Paterra apaterra@gmail.com
This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:41 ART