[c-nsp] MPLS TE explicit-path: secondary ip as next-address

Oliver Boehmer (oboehmer) oboehmer at cisco.com
Tue Feb 5 06:08:30 EST 2013

On 05/02/2013 11:03, "Artyom Viklenko" <artem at viklenko.net> wrote:

>05.02.2013 10:30, sthaug at nethelp.no пишет:
>>> New ip addresses was configured as secondary on interfaces in question.
>>> These new subnets (/30) appear in routing table, cef, etc. Network
>>> statement also was added to ospf configuration.
>> Note that it at least *used* to be the case that OSPF wouldn't form
>> adjacencies over secondary addresses. I don't know if this limitation
>> still holds, but it could be relevant to your case.
>But it doesn't in  output of 'show mpls traffic-eng topology' like any
>other secondary subnets. This lead to errors establishing path.

indeed, that's the reason CSPF won't find a path when you reference the
secondary in the path.. Don't think you can add those to the topology, so
the only approach would be to work with alternate path options and
re-oprtimization which would use a temporary path around the links you're
Or maybe you don't have that much traffic during low-peak hours that you
could do away without the tunnels when you change the links?


More information about the cisco-nsp mailing list