Anyone noticing a "tendency" here ?
I very seldom resort to reload for fixing things, but latelly it IS
working more and more. This is a pitty.
MS$ has made us so accustomed to fix by reloading that we care less and
less about this. We even have jokes about that (fixing a non functioning
MS car by stepping out and back in :)
-Carlos
Narbik Kocharians @ 18/04/2009 13:24 -0200 dixit:
> Were you running Vista or NT?
>
> hahahaha just joking man. It has happened to me once on 12.4(19), i had to
> reload to get things going.
>
> On Sat, Apr 18, 2009 at 8:35 AM, Paul Cosgrove <paul.cosgrove_at_gmail.com>wrote:
>
>> Yes only on the hub router. Entered the commands and checked with "show ip
>> ospf nei" but it showed no neighbor entries (no lines, regardless of adj
>> state). Deleted the two neighbor config lines (or at least tried to) and
>> re-entered the same commands and the neighbors are then recognised, forming
>> full adjacencies. I then had duplicate lines in the config for each
>> neighbor.
>>
>> The router allowed me to remove the duplicate entries, but the original two
>> lines could not be removed. I reloaded a few minutes after it happened and
>> it has been fine since, but just thought it was an interesting bug.
>>
>> Paul.
>>
>>
>> Narbik Kocharians wrote:
>>
>>> Paul,
>>>
>>> Are you configuring the neighbor commands on the HUB?
>>>
>>> On Sat, Apr 18, 2009 at 6:53 AM, Ahsan Mohiuddin
>>> <ahsan.mohiuddin_at_gmail.com>wrote:
>>>
>>>
>>>
>>>> Yes we have seen this. Try rebooting the router; do the neighbor commands
>>>> disappear? And while rebooting you see an error like "OSPF neighbor
>>>> command
>>>> is allowed only on non-broadcast interfaces". I think I saw it on
>>>> 12.4(17)
>>>>
>>>> On Fri, Apr 17, 2009 at 10:54 PM, Paul Cosgrove <paul.cosgrove_at_gmail.com
>>>>
>>>>
>>>>> wrote:
>>>>> Just tried a simple topology with a hub and spoke non-broadcast
>>>>> ospf
>>>>> network. The neighbor commands did not take effect the first time
>>>>> around
>>>>> (no neighbors listed) and clearing ospf had no effect. To fix it I
>>>>> tried
>>>>>
>>>>>
>>>> to
>>>>
>>>>
>>>>> remove and reapply the neighbor commands. Neighbor relationships are
>>>>> now
>>>>> formed, but it has left me with an interesting configuration. I guess
>>>>>
>>>>>
>>>> my
>>>>
>>>>
>>>>> router is being a little stubborn today. :-)
>>>>>
>>>>> router ospf 1
>>>>> log-adjacency-changes
>>>>> network 141.1.0.0 0.0.0.255 area 1
>>>>> network 141.1.123.0 0.0.0.255 area 0
>>>>> network 150.1.2.0 0.0.0.255 area 0
>>>>> neighbor 141.1.123.3
>>>>> neighbor 141.1.123.1
>>>>> neighbor 141.1.123.1
>>>>> neighbor 141.1.123.3
>>>>> !
>>>>>
>>>>> Anyone else see this in 12.4(23) or other releases?
>>>>>
>>>>> Paul.
>>>>>
>>>>>
>>>>> Blogs and organic groups at http://www.ccie.net
>>>>>
>>>>> _______________________________________________________________________
>>>>> Subscription information may be found at:
>>>>> http://www.groupstudy.com/list/CCIELab.html
>>>>>
>>>>>
>>>> Blogs and organic groups at http://www.ccie.net
>>>>
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
>
-- Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina Blogs and organic groups at http://www.ccie.netReceived on Sun Apr 19 2009 - 09:05:07 ART
This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:12 ART