Re: MPLS TE and ISIS

I got the solution for this. Yes the problem was related to inter
area/level TE which by default does not work For this to work in ISIS
we need wide area metric, explicit path with next-hop loose x.x.x.x.
Sorry can't post the solution as I am not home but if you google up
Interarea TE you will get all.

Thx
Aamir

On 12/3/10, Rich Collins <nilsi2002_at_gmail.com> wrote:
> Hi Aamir,
>
> Isn't your problem that the TE tunnel spans more than one area (either
> level-1 or level-2) in the one case?
>
> -Rich
>
> On Wed, Dec 1, 2010 at 4:34 PM, Aamir Aziz <aamiraz77_at_gmail.com> wrote:
>> Dear all,
>>
>> I have an interesting issue here with MPLS TE and ISIS. I have four
>> routers, R1, R2, R3 and R4.
>>
>> R1-------R2-------R3---------R4
>>
>> R1 and R2 are in ISIS level 1 (router isis)
>> R2 and R3 are in ISIS level 2 (router isis SECOND)
>> R3 and R4 are in ISIS level 1 (router isis)
>>
>> i have created tunnel on R1 with explicit path:
>>
>> R1->R2->R3->R4
>>
>> I have redistributed the connected link between R2 and R3 from ISIS
>> level 2 SECOND (router isis SECOND) into ISIS level 1 (router isis)
>> which is working fine and on R1 and R4 i get that connected (x.x.23.0)
>> link as iL1. The issue is tunnel is up and down.
>>
>> But as soon as i put the connected link between R2 and R3 (interface
>> FastEthernet0/0.23) in ISIS level 1 (router isis) tunnel is up up and
>> it works fine. Any idea why it was not working before?
>>
>> here are the configs:
>>
>> R1:
>>
>> tinterface Tunnel10
>> ip unnumbered Loopback0
>> tunnel destination x.x.x.4
>> tunnel mode mpls traffic-eng
>> tunnel mpls traffic-eng autoroute announce
>> tunnel mpls traffic-eng priority 0 0
>> tunnel mpls traffic-eng bandwidth 2000
>> tunnel mpls traffic-eng path-option 1 explicit name CISCO
>>
>> router isis
>> net x.x.x.x
>> is-type level-1
>> metric-style wide
>> mpls traffic-eng router-id Loopback0
>> mpls traffic-eng level-1
>>
>> R2:
>>
>> router isis
>> net x.x.x.x
>> is-type level-1
>> metric-style wide
>> redistribute connected route-map CONN level-1
>> mpls traffic-eng router-id Loopback0
>> mpls traffic-eng level-1
>>
>> router isis SECOND
>> net x.x.x.x
>> is-type level-2-only
>> metric-style wide
>> mpls traffic-eng router-id Loopback1
>> mpls traffic-eng level-2
>>
>> interface FastEthernet0/0.23
>> encapsulation dot1Q 23
>> ip address x.x.23.2 255.255.255.0
>> ip router isis SECOND
>> mpls traffic-eng tunnels
>> mpls ip
>> ip rsvp bandwidth 20000
>>
>> ip access-list standard CONN
>> permit x.x.23.0
>>
>> route-map CONN permit 10
>> match ip address CONN
>>
>> R3:
>>
>> router isis
>> net x.x.x.x
>> is-type level-1
>> metric-style wide
>> redistribute connected route-map CONN level-1
>> mpls traffic-eng router-id Loopback0
>> mpls traffic-eng level-1
>>
>> router isis SECOND
>> net 49.0010.0000.0000.2222.00
>> is-type level-2-only
>> metric-style wide
>> mpls traffic-eng router-id Loopback1
>> mpls traffic-eng level-2
>>
>> interface FastEthernet0/0.23
>> encapsulation dot1Q 23
>> ip address x.x.23.3 255.255.255.0
>> ip router isis SECOND
>> mpls traffic-eng tunnels
>> mpls ip
>> ip rsvp bandwidth 20000
>>
>> ip access-list standard CONN
>> permit x.x.23.0
>>
>> route-map CONN permit 10
>> match ip address CONN
>>
>>
>> thanks,
>> Aamir
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>

-- 
Sent from my mobile device
Blogs and organic groups at http://www.ccie.net