[c-nsp] Resilience in order of few hundreds of milliseconds
Rodney Dunn
rodunn at cisco.com
Tue Mar 6 14:55:43 EST 2007
On Tue, Mar 06, 2007 at 11:53:54AM -0600, Alaerte.Vidali at nokia.com wrote:
> Hi Rodney,
>
> Yes, I have something in mind. What is the lowest time we can get using
> second precomputed path from headend to tailend on the same tunnel
> interface?
You could have a backu precomputed path but you still need the notification
that the primary path isn't valid anymore (ie: Think BFD triggered FRR).
> The headend would sense problem in the first option and switch to second
> option.
How would it "sense" a failure at any point along the path?
>
> I did not test it.
>
> Tks,
> Alaerte
>
> -----Original Message-----
> From: ext Rodney Dunn [mailto:rodunn at cisco.com]
> Sent: Tuesday, March 06, 2007 2:49 PM
> To: Vidali Alaerte (Nokia-NET/RioDeJaneiro)
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Resilience in order of few hundreds of milliseconds
>
> No way I can think of.
>
> Did you have something in mind?
>
> You have to have a backup path precomputed and ready to switch the
> frames to get that kind of failover.
>
> rodney
>
> On Tue, Mar 06, 2007 at 11:27:50AM -0600, Alaerte.Vidali at nokia.com
> wrote:
> > Hi,
> >
> > Looking for alternatives of fast recovery of MPLS under failure
> > without using FRR.
> > Any input appreciated.
> >
> > (BFD and OSPF timer tuning already considered)
> >
> > Best Regards,
> > Alaerte
> >
> >
> > _______________________________________________
> > 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/
More information about the cisco-nsp
mailing list