[c-nsp] IP LFA in ring topology

[Phil Bedard]

I don't know about support in some newer releases but the old
auto-tunnel one hop would just build tunnels to adjacent nodes and then
had the ability to create bypasses. So you got the benefits of RSVP-TE
local protection but the route followed the IGP and you didn't really
have any TE.

If you are using LDP and not just IP routing Cisco supports rLFAs or
remote LFAs which will attempt to build a tunnel to bypass LFA
failures. Junos can use RSVP tunnels to get around coverage problems as
well, not sure about Cisco. rLFA also isn't available on IOS-XR as far
as I remember but it is coming.

G.8032 works if you are pure L2 but has its own drawbacks.

Phil From: Saku Ytti
Sent: 11/29/2012 8:23
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] IP LFA in ring topology
On (2012-11-29 13:48 +0100), Adam Vitkovsky wrote:

> What brings us to mpls-te primary and backup tunnel from each node to every
> other node on the ring
> And that is crazy as well

MPLS FRR with auto-tunnels?

There is no technical reason why we couldn't do MPLS FRR without any
RSVP-tunnels, based purely on pre-calculated IGP.

Say you have the topology and fault I wrote earlier. And you have global
IGP labels.
Then when R5 notices the fault, could impose label R3 on top of existing
[P1, VPNn] stack it had.
So stack would be [R3, P1, VPNn], R5 would push this to R4, which would not
return it to R5, as it's going towards R3, which path is unaffected by
failure.
At R3 the label would be popped, and forwarded based on original [P1, VPNn]
stack, which is also unaffected by the fault, from R3 POV.

All this is fully local repair, any topology, any single fault, before,
after and during IGP reconvergence. R5 has all the information it needs.

Fast and local repair is focus on standard bodies and I'm sure something
like this, 0 config to operators, will appear to the patient.

-- 
  ++ytti
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/