From: Reinhold Fischer (Reinhold.Fischer@gmx.net)
Date: Thu Mar 30 2006 - 06:42:49 GMT-3
> GK: TE calculates the path to the headend from its TE
> topo database. RSVP path messages follow the path.
> This is processed hop-by-hop. At every hop, next-hop
> is determined either from the path message(explicit)
> or from its own TE database. Resv will carry the
> label. routing table is not used. If you have a
> working setup, simply do not advertise the headend
> router-id in IGP(make it disappear from the routing
> table), TE tunnel shd be working fine. Pls let us know
> what you see.
>
RF: Just tried it in the lab setup. You are right in that
you do not have to take the new loopback explicitely into
the IGP with a network statement or through redistribution.
It is enough to select the new loopback as MPLS-TE router-id
which in turn puts it into the LSDB of the IGP. If you do
not select this loopback as routerid the tunnel will not come
up. Also not if you put the new loopback address with a network
statement or through redistribution into the IGP. So it is
enough to use it as mpls-te routerid on the tailend to be
able to specify it as tunnel destination on the headend.
For me it just feels a bit odd to specify an ip address as
tunnel destination and cannot see it in the routing table.
Have to keep in mind that the LSDB in the background holds
a lot more information ...
reinhold
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:40 GMT-3