[c-nsp] Resilience in order of few hundreds of milliseconds

[Tony Li]

To do that, with the headend providing failure detection, it would  
have to inject a keepalive mechanism (e.g., ping) at an interval of  
about one third of your recovery time.  Is that really what you  
want?  That's very high overhead.

Tony



On Mar 6, 2007, at 9:53 AM, <Alaerte.Vidali at nokia.com>  
<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?
> The headend would sense problem in the first option and switch to  
> second
> option.
>
> 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/
>
> _______________________________________________
> 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/