[c-nsp] MPLS TE conver from IOS to IOS-XR

[Pavel Stefanov]

One more point worth mentioning is that you need "ipv4 unnumbered mpls 
traffic-eng Loopback0" in global config mode on IOS XR to get the 
auto-mesh TE tunnels signalled. Otherwise, you see "Reason for the 
tunnel being down: No IP source address is configured" in show mpls 
traffic-eng tunnels.

It took me ages to find out how to configure the IP address on the 
interface as the attribute-set does not allow you to specify it. I 
would've thought this command would go under the mpls traffic-eng 
hierarchy or as part of the attribute-set...

Pavel


On 26/03/2012 11:15, Xu Hu wrote:
> Hi Team,
> I had something new to updated this topic. I want to highlight two things
> that need to be careful.
> 1. In the auto-tunnel mesh, if you want to define the destination-list,
> must remember to use the prefix list not the access-list, if you use the
> access-list, the auto-tunnel also can created, but the number and path is
> wrong, i trouble shooting so much time.
> 2.If you don't see the backup tunnel work, you need to check if you enable
> the backup tunnel under the interface.
> The command is like this: mpls traffic-eng interface auto-tunnel backup,
> that's all.
>
> Hu Xu
>
> 2012/2/27 Xu Hu <jstuxuhu0816 at gmail.com>
>
>> You can use the Cisco Tools of "Cisco Feature Navigator" to check whether
>> your platform can support or not.
>>
>> Xu Hu
>> 2012/2/27 David Barak <thegameiam at yahoo.com>
>>
>>> BFD is great stuff. Is there any chance of getting BFD on the 45k
>>> platform?
>>>
>>> David Barak
>>> (apologies for the mobile-device-style top post)
>>>
>>>   ------------------------------
>>> * From: * Oliver Boehmer (oboehmer) <oboehmer at cisco.com>;
>>> * To: * <mtinka at globaltransit.net>; Xu Hu <jstuxuhu0816 at gmail.com>;
>>> * Cc: * <cisco-nsp at puck.nether.net>;
>>> * Subject: * Re: [c-nsp] MPLS TE conver from IOS to IOS-XR
>>> * Sent: * Mon, Feb 27, 2012 5:58:18 AM
>>>
>>>
>>>>> "Timer intervals configured, Hello 333 msec, Dead 1, Wait
>>>>> 1, Retransmit 5"
>>>> So what you're talking about is the "OSPF Support for Fast
>>>> Hellos" feature from Cisco:
>>>>
>>>> http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fasthelo.html
>>>>
>>>>
>>>> This feature combines the Hello Interval and Dead Interval,
>>>> along with some enhancements that make it behave like BFD in
>>>> a way.
>>>>
>>>> AFAICT, it's only supported in IOS (and perhaps, IOS XE).
>>>> You can tweak both the Hello and Dead Interval timers in IOS
>>>> XR, but they lack of the enhancements to enable fast
>>>> detection.
>>>>
>>>> For IOS XR, yes, BFD is your best bet.
>>> this holds true for any platform, fast hellos just don't scale.. so
>>> please use BFD if you need to detect neighbour failures quickly.
>>>
>>>      oli
>>>
>>>
>>> _______________________________________________
>>> 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/