[j-nsp] RSVP to LDP migration

[David Ball]

  If/when supplementing with RSVP LSPs isn't an option for you, you
might also wish to consider enabling Loop-Free Alternates (LFA) for
your IGP along with an exported load-balance policy on each Juniper
device to (potentially) speed up convergence in the event of a
failure.  Having a backup next-hop pre-installed in the forwarding
plane has helped me greatly in areas where RSVP w/FRR isn't
available/used.  Its scope is local, so there's no dependency on
having it configured on *every* router in your network.  Your mileage
may vary depending on what your topology looks like (ie. whether LFA
can find a loop-free backup or not).

David


On 28 July 2011 05:16, Thedin Guruge <thedin at gmail.com> wrote:
> Hi,
>
> Yes you could activate LDP everywhere, i.e on all links but you may also
> want to run "per Link" single hop RSVP LSP between directly connected peers
> with "ldp-tunnelling" enabled. This will activate LDPoverRSVP hence traffic
> can be protected by FRR link protection when passes through these links. The
> fact that Junos uses php by default means these single hop LSPs won't really
> be adding another label (i.e additional 4byte overhead) on top of the LDP
> label unless FRR is active.
>
> hope this helps,
>
> Regards,
>
> Thedin
>
> On Thu, Jul 28, 2011 at 3:35 AM, Stefan Fouant <
> sfouant at shortestpathfirst.net> wrote:
>
>> On 7/27/2011 9:41 AM, Phil Bedard wrote:
>>
>>> It's fairly simple.  Just turn up LDP everywhere, make sure the LDP paths
>>> exist in inet.3 and then turn off RSVP or set the preference on RSVP
>>> higher.   You can tunnel LDP over RSVP so if you are just adding gear to
>>> the edge of the existing network it may be easier to turn on LDPoRSVP and
>>> just run LDP on interfaces at the edge.
>>>
>>
>> Just an FYI, the book 'Network Mergers and Migrations' by Gonzalo Gómez
>> Herrero and Jan Antón Bernal van der Ven provides excellent coverage of the
>> subject matter and has a whole chapter dedicated to migration of label
>> distribution protocols.
>>
>> http://www.amazon.com/gp/**product/0470742372/ref=as_li_**
>> ss_tl?ie=UTF8&tag=short0e-20&**linkCode=as2&camp=217145&**
>> creative=399369&creativeASIN=**0470742372<http://www.amazon.com/gp/product/0470742372/ref=as_li_ss_tl?ie=UTF8&tag=short0e-20&linkCode=as2&camp=217145&creative=399369&creativeASIN=0470742372>
>>
>> Stefan Fouant
>> JNCIE-ER, JNCIE-M, JNCIE-SEC, JNCI
>> Technical Trainer, Juniper Networks
>> http://www.shortestpathfirst.**net <http://www.shortestpathfirst.net>
>> http://www.twitter.com/sfouant
>>
>> ______________________________**_________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.nether.net/mailman/listinfo/juniper-nsp>
>>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>