From: Howard C. Berkowitz (hcb@gettcomm.com)
Date: Fri Dec 26 2003 - 11:46:03 GMT-3
At 7:20 PM +0900 12/26/03, Ashok Verma (ashoverm) wrote:
>Hi All
>
>I have a query about NEIGHBOR command, which is used in the NBMA network
>to make the ospf peering
>
>When we define the #neighbour x.x.x.x priority 0
>
>What is the priority 0 means . Is it mean the other side router can not
>become the DR .
>
>One more observation I have is even if configure the # neighbour x.x.x.x
>priority 0
>
>When I check the configuration I see it as #neighbour x.x.x.x priority 1
>.....is it a bug ?
That does sound a little strange. Could you post the configuration
for the entire interface and subinterfaces (i.e., all hubs and
spokes), as well as the OSPF statement?
What I'm wondering is whether something else in the interface
configuration is making IOS think that the particular neighbor needs
to be DR-eligible. Changing things isn't unprecedented in IOS -- you
see this sort of behavior in wildcard masks in access lists, where,
if the low-order bits are wildcards but the address argument is
exact, IOS may mask to zero the low-order bits of the address.
It's always worth remembering that the show running command doesn't
actually play back your keystrokes. At least on the slower routers,
you'll often notice a brief delay before the listing starts. That
delay comes from processing by the show command, which is actually a
reverse compiler that goes through the current data structures in the
executable, and creates a set of configuration statements that it
thinks would have produced the state of those structures. So,
something else you are doing might make IOS think that this neighbor
needs priority 1.
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:45 GMT-3