[c-nsp] OSPF's handling of secondary IP addresses on subinterfaces
Aaron
aaron1 at gvtc.com
Tue Apr 10 10:32:55 EDT 2012
Robert, thanks for the update on your saga....as Gert just mentioned, based
on your initial statement...
>>> The OSPF process includes network statements that encompass both
>>> primary and secondary IP addresses and they're all in the same area.
...I believe the community thought this was some strange/weird bug or
something you were experiencing....
I had the same issue a while back where I had the ospf network statements
covering the networks defined as secondaries, BUT if the primary ip address
wasn't covered as a network statement as well, NONE of my secondaries were
advertised.
Aaron
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Robert Johnson
Sent: Monday, April 09, 2012 2:07 PM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] OSPF's handling of secondary IP addresses on
subinterfaces
Okay, I believe I've found my problem.
My primary address statement had a typo that put it outside of the OSPF
network definitions. Apparently when the primary address on an interface
isn't picked up by a particular OSPF process, none of the associated
secondary addresses will be either.
Will test to confirm tonight.
On Sun, Apr 8, 2012 at 12:10 AM, Robert Johnson <fasterfourier at gmail.com>
wrote:
> Yes, I'm actually seeing one subinterface with a secondary address
> have both the primary and secondary address subnets advertised into
> OSPF and another have only the primary advertised. Very strange.
> Suppose it's worth trying redistribute connected... thanks for the
> tip.
>
> Is this expected behavior or a bug?
>
>
> On Sat, Apr 7, 2012 at 5:30 PM, Wayne Lee <linkconnect at googlemail.com>
wrote:
>>
>>
>> Sent from my iPad
>>
>> On 7 Apr 2012, at 03:29, Robert Johnson <fasterfourier at gmail.com> wrote:
>>
>>> I have a FastEthernet interface with multiple 802.1Q based
>>> subinterfaces. OSPF properly advertises routes for the subnets
>>> directly defined on these subinterfaces. However if I add secondary
>>> IP addresses to these subinterfaces, the subnets defined using the
>>> secondary command show up in the local routing table as directly
>>> connected, but OSPF doesn't advertise them to the rest of the area.
>>> The OSPF process includes network statements that encompass both
>>> primary and secondary IP addresses and they're all in the same area.
>>>
>>> Are there any limitations I should know about with OSPF on
>>> subinterfaces with secondary IP addresses?
>>>
>>> IOS 12.4(25) on a 3745.
>>>
>>> Thanks in advance.
>>> _______________________________________________
>>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>>>
>>
>> I've seen this happen before. The same box announced the secondary subnet
on one subinterface but did not on a another. We do have redist connected
subnets enabled.
>>
>> Regards
>>
>> Wayne
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list