From: Roman Rodichev (roman@iementor.com)
Date: Sun Jun 22 2008 - 11:41:54 ART
Don't confuse TE tunnels with GRE tunnels. TE tunnel doesn't do IP in IP
encapsulation. TE tunnel is used to control a label forwarding path to some
next-hop (124.1.1.1) used by MPLS L3VPN. Without TE, you are relying on the
core IGP metrics to determine the path to this next-hop (124.1.1.1), and
with TE you can control the path based on various parameters (not just core
IGP metrics alone).
Roman Rodichev
5xCCIE #7927 (R&S, Security, Voice, Storage, Service Provider)
Instructor, Content Developer. ieMentor Corporation
http://www.iementor.com
Y!M: roman7927
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Rado
Vasilev
Sent: Sunday, June 22, 2008 7:30 AM
To: ccielab@groupstudy.com
Subject: MPLS TE tunnels && routing
Hi Group,
I've a general question re the general way TE tunnels work.
I'm working on a IEWB vol2 task 4.4/Lab 5. Basically a simple TE tunnel
is created but autoroute announce is not allowed:
nterface Tunnel14
ip unnumbered Loopback0
tunnel destination 124.1.1.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng bandwidth 2500
tunnel mpls traffic-eng path-option 1 explicit name R4_R1
no routing dynamic
end
In order to use the tunnel I've configured a static route:
ip route 124.1.1.1 255.255.255.255 Tunnel14
Basically we want to use the tunnel for the remote PE's loopback
address. Now this is what confuses me a lot re TE tunnels, as that
loopback happens to be the tunnel's destination.
I've got the feeling this is kinda taken care of by the MPLS labels so
the tunnel won't go down (and up and so on) as it happens when we have
normal recursive issue in non-MPLS configurations.
I'd be grateful if anyone on the list with more experience could explain
how is this taken care by IOS so that the routing the tunnel destination
through the tunnel works.
Thanks,
Rado
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:22 ART