[c-nsp] MPLS fast reroute without full mesh traffic engineering

[Oliver Boehmer (oboehmer)]

you obviously need MPLS-TE backup tunnels to achieve fastest
convergence, and auto-tunnel backup addresses this. These backup tunnels
are created dynamically and based on demand, i.e. if there are links not
used by primary tunnels, backup tunnels won't be built. Backup tunnels
will never be fully-meshed, they're NHOP/NNHOP only.. 

To get traffic into tunnels (in order to protect it), you can use
one-hop primaries OR auto-tunnel mesh OR manual tunnels.

	oli

Rubens Kuhl Jr. <> wrote on Monday, January 12, 2009 15:26:

> Very interesting. After reading the document, though,  I couldn't
> fully understand if primary onehop is enough to achieve low latency
> switchover(most likely not), or how to create backup onehop tunnels,
> or if only primary onehop tunnels are allowed and backup tunnels are
> still full-meshed.
> 
> 
> Rubens
> 
> 
> 
> On Mon, Jan 12, 2009 at 12:06 PM, Phil Bedard <philxor at gmail.com>
> wrote: 
>> autotunnel primary one-hop.  The one-hop portion being the important
>> part. 
>> 
>> Phil
>> 
>> On Jan 12, 2009, at 8:38 AM, Rubens Kuhl Jr. wrote:
>> 
>>> I'm trying to map US Patent 7230913
>>> (http://www.patentstorm.us/patents/7230913.html) to an specific IOS
>>> feature... it sounded to me like AutoTunnel, is that so ?
>>> 
>>> 
>>> Rubens
>>> _______________________________________________
>>> 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/