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-h
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 lin
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
When we initially configured our RSVP infrastructure we ran into a big
problem since the LSPs/FastReroute were not being handled properly over
aggregated Ethernet links. So I had to fairly quickly convert everything
over to LDP so that I could work on the RSVP/link-aggregation issue later.
I
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
Hi Experts,
One of our customer has a extensive M-series based MPLS network which uses
RSVP and Admin-groups for TE. We are trying to simplfy the network and
introduce some other vendor nodes in the network and hence want to migrate
the network to LDP.
My preference would be to migrate the existi
6 matches
Mail list logo
