Hi,
try this:
policy-options policy-statement lb
then {
load-balance per-packet;
}
then you export the policy
set routing-options forwarding-table export lb
and this is how load-balance is enabled.
This will add both routes in the forwarding table and real fast reroute will
be activated.
This means few milliseconds of recovery time rather than hundreds of ms (and
no ping typically lost)
Br,
Filippo
----- Original Message -----
From: "Cord MacLeod" <[email protected]>
To: "William Jackson" <[email protected]>
Cc: <[email protected]>
Sent: Monday, April 27, 2009 7:00 PM
Subject: Re: [j-nsp] MPLS Question
From my own tests with this, Junipers will swap the path in the same
second. But yes, generally a single ping will be lost.
On Apr 27, 2009, at 8:00 AM, William Jackson wrote:
Hi
Just dipping my feet into the world of MPLS and have some quick
questions.
On my ingress router I am setting up some RSVP label paths with strict
ERO's, I add the fast reroute option and the adaptive option. So that
the primary and secondary paths are already up.
On my transit nodes I add the RSVP link-protection command to the
relevant interfaces.
On my ingress node I also see options for node-link-protection and
link-protection under the label-switched-path section, are these all
needed on the ingress node to get fast-reroute working
I am getting a single ping packet lost when I pull a cable out was
wondering if there was a way to get even faster path swap over?
Do I have to tweak any timers or something?
Thanks
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
