Re: MPLS TE

From: Jay Pal (jay.b.pal@gmail.com)
Date: Mon Mar 16 2009 - 06:57:29 ART


the default timer for re-optimization for TE tunnels by default is 60 min.

or u could use the 'frequency' command to speed things up.
mpls traffic-eng reoptimize timers frequency 10

On Mon, Mar 16, 2009 at 5:10 PM, Jay Pal <jay.b.pal@gmail.com> wrote:

> Hello Everyone,
>
> I am trying to lab up a scenario where I want use explicit path as the
> first priority to set up the path and a dynamic if the explicit path fails.
> I am using OSPF as the underlying IGP, as a test I am just using 3 routers.
> R1 and R3 are directly connected and R4 is connected to R1 and R3
> (triangle). I am building tunnel between R1 & R3, but my explicit path is
> through R4.
>
> I can see the tunnel built through R4 and when I shut down R4, TE tunnel
> goes via 'dynamic' path-option directly to R3. However, when I bring up
> router R4 the tunnel does not fall back to the explicit path-option which
> has a priority of 1 (dynamic is 2).
>
> Below is my configuration for the tunnel. I would imagine that it should go
> back to my explicit path, unless there is a rule that otimization happens
> after certain time. Think I need to do more reading on TE.
>
> let me know if there are other outputs that I shoudl post.
>
> !
> interface Tunnel0
> ip unnumbered Loopback0
> tunnel destination 3.3.3.3
> tunnel mode mpls traffic-eng
> tunnel mpls traffic-eng autoroute announce
> tunnel mpls traffic-eng path-option 1 explicit name r1-r3
> tunnel mpls traffic-eng path-option 2 dynamic
>
> This is what I see even if the explicit path is up and running:
> path option 2, type dynamic (Basis for Setup, path weight 2)
> path option 1, type explicit r1-r3

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:05 ART