[c-nsp] MPLS TE auto-tunnel and ISIS metric

[dip]

let me ask you this first ,is the destination 192.0.2.6 is a loopback on
Core-2 or its a different physical device attached behind Core-2 ? If its a
loopback on core-2 then i would suggest to put a different router attached
to core-2 for accurate testing .


On Wed, Oct 16, 2013 at 1:40 AM, Peter Rathlev <peter at rathlev.dk> wrote:

> On Tue, 2013-10-15 at 17:29 -0600, dip wrote:
> > you should be able to see the configs with the help of "show derived
> > config interface Tu65336"
>
> Ooh, I didn't know that command. Very nice. :-)
>
>     interface Tunnel65336
>      ip unnumbered Loopback0
>      no ip redirects
>      no logging event link-status
>      mpls ip
>      tunnel mode mpls traffic-eng
>      tunnel destination 10.85.248.34
>      tunnel mpls traffic-eng autoroute announce
>      tunnel mpls traffic-eng path-option 1 explicit name
> __dynamic_tunnel65336
>      tunnel mpls traffic-eng fast-reroute
>      no routing dynamic
>     end
>
> > , one thing you would notice is that they
> > are created with explicit path option not dynamic path option  and
> > thats why you see that  its not following shortest path based on your
> > IGP metric.Though it will detect that there is a better path
>
> Yup.
>
>     dist-1#sh ip explicit-paths name __dynamic_tunnel65336
>     PATH __dynamic_tunnel65336 (strict source route, path complete,
> generation 58, status non-configured)
>         1: next-address 198.51.100.222
>     dist-1#
>     dist-1#show ip route 192.51.100.222
>     Routing entry for 198.51.100.222/32
>       Known via "connected", distance 0, metric 0 (connected)
>       Routing Descriptor Blocks:
>       * directly connected, via TenGigabitEthernet5/4
>           Route metric is 0, traffic share count is 1
>     dist-1#
>
> Strangely (to me at least) is that the explicit path "next-address" is
> actually the local address of the (wrong) interface, not the remote
> address.
>
>     dist-1#show ip interface brief Te5/4
>     Interface              IP-Address      OK? Method Status
>  Protocol
>     TenGigabitEthernet5/4  198.51.100.222  YES NVRAM  up
>  up
>     dist-1#
>
> I still don't understand why it would select this path and not the one
> with the lowest cost.
>
> >  ..So if
> > you do "show mpls traffic-eng tunnels tunnel XYZ" , it should tell you
> > the shortest unconstrained Path which is probably what you want it to
> > follow .
>
> It does exactly tell my that. Is there any way to make it use this? :-)
>
> --
> Peter
>
>
>
>