[ntp:questions] ntp peer association in VLAN query

kiran shirol kiran.shirol at gmail.com
Mon Jan 19 16:30:43 UTC 2009


Phil,

Can you provide me the link to the discussion you had on the same topic ? I 
am interested in knowing more details.

Regards,
Kiran Shirol

<Phil.Newlon at wendysarbys.com> wrote in message 
news:OF934F3A67.43D91A3C-ON85257543.00586C3A-85257543.0058B27B at wendys.com...
> Danny -
>
> It sounds like this is the same behavior that I asked about a few weeks
> ago, I think.
>
> I have a Windows machine with two IP addresses, acting as an NTP time
> source for devices on one of the two networks.  Time synch requests come 
> in
> from the clients on network A, and the response from the Windows machine 
> is
> out the interface on network B.  RE: "query-on"
>
>
> Danny wrote:
>
> What you require is the query-on option. I haven't had time to roll it
> into a release yet. You need outbound queries to go on the routeable
> address, correct?
>
>
> Phil
>
>
>
>
>
>             Danny Mayer
>             <mayer at ntp.isc.or
>             g>                                                         To
>             Sent by:                  kiran shirol
>             questions-bounces         <kiran.shirol at gmail.com>
>             +phil.newlon=wend                                          cc
>             ysarbys.com at lists         questions at lists.ntp.org
>             .ntp.org                                              Subject
>                                       Re: [ntp:questions] ntp peer
>                                       association in VLAN query
>             01/19/2009 11:04
>             AM
>
>
>             Please respond to
>             mayer at ntp.isc.org
>
>
>
>
>
>
> kiran shirol wrote:
>> My switch has configured for peering with the following switches
>>
>> ntp peer 101.1.1.2
>> ntp peer 101.2.2.2
>> ntp peer 102.1.1.2
>>
>> Vlan has the following configuration:
>> ip address 10.1.1.1/24
>> ip address 20.1.1.1/24 secondary
>>
>> Peer sends the NTP message 20.1.1.2(Out-Interface) -> 20.1.1.1(VLANs
> secondary IP)
>> The response comes as 10.1.1.1(VLANs Primary IP) -> 20.1.1.2
>>
>
> That means that the VLAN is using the wrong address to reply to the
> message. NTP will see that it does not match the going address and will
> discard the message. That's correct behavior. You need to figure out why
> the packet is coming back with the incorrect address. i suspect the VLAN
> but I cannot be sure.
>
> Danny
>
>
>> Traces:
>> 2008-12-20 00:01:40.522776     20.1.1.2 -> 20.1.1.1     NTP NTP symmetric
> active
>> 2008-12-20 00:01:42.548166     10.1.1.1 -> 20.1.1.2     NTP NTP symmetric
> passive 





More information about the questions mailing list