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

[Peter Rathlev]

Adam,

Thank you very much for your time on this. :-) But don't use too many
ressources looking into it. We're just experimenting to see if we can
have a cheap/easy way to get a little faster failover. If it's too much
trouble we'll stay with what we have.

On Tue, 2013-10-22 at 14:58 +0200, Adam Vitkovsky wrote:
> Since this seems to be getting more and more complicated, I'd like to ask
> whether there's an option to migrate to a code that would support IP-FRR
> instead of TE-FRR please? 

I'm not too knowledgeable about IP FRR/LFA but as far as I can tell it's
not supported on the 6500 / Sup2T. At least not until Cisco releases
15.2SY images. :-)

> Just shooting in the dark is the fast-reroute enabled on the primary
> tunnels? (via auto-tunnel template)
> Or do you otherwise see that the primary tunnels are protected please?

The auto-template has "tunnel mpls traffic-eng fast-reroute". It doesn't
show up as a "protect" path in "show mpls traffic-eng tunnels", but
"show ip cef <dest-ip-addr> internal" shows a "repair":

  nexthop 192.0.2.35 Tunnel64337, adjacency IP midchain out of Tunnel64337 1789DEC0
  output chain: IP midchain out of Tunnel64337 1789DEC0 label [implicit-null|implicit-null]
  FRR Primary (0x53BEB820)
  <primary:  IP adj out of TenGigabitEthernet5/4, addr 198.51.100.222 1789D500>
  <repair:  IP midchain out of Tunnel65439 1789DD20 label 208 TAG adj out of GigabitEthernet5/1, addr 198.51.100.209 1789BB00>

And "show mpls traffic-eng fast-reroute" mentions the Tunnel64337 that
both RIB and FIB says is next-hop interface.

This might of course still mean no protection if 15.1SY and/or Sup2T
just doesn't want to even though all the commands show the right
output. :-)

-- 
Peter