[j-nsp] Bypass LSP functionality question
Phil Bedard
philxor at gmail.com
Thu Jul 7 00:29:24 EDT 2011
That's not correct. You should take a look at RFC4090. A Patherr message
is sent to the head-end node with a flag set to notify it local protection
is in use. There are also flags in the RESV RRO to notify the head-end
local protection is in use. The head-end node is smart enough to keep
using the path until it can reserve a new path and do a MBB operation.
Facility bypass wouldn't be very useful if it only protected traffic for a
few ms...:)
Phil
On 7/6/11 11:50 AM, "David Ball" <davidtball at gmail.com> wrote:
> Just looking for confirmation of a suspicion here.
>
> If I have an LSP configured with link-protection on every interface
>along the way (creating many-to-one Bypass LSPs, as opposed to 1:1
>detours), no secondary standby path defined, and a protected interface
>fails, the ingress node will have no ability to perform a
>make-before-break, right? Because the Path Tear messages will be sent
>both upstream and downstream from the failed interface? The bypass
>will only help me up until the upstream nodes process the Path Tears
>and a new LSP is signalled from the ingress node....or am I missing
>something?
>
> More familiar with detours, so just checking myself wrt bypasses....
>
>Cheers,
>
>David
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list