Alcatel-Lucent 7450 Manual page 163

7. The following parameters can be used with a P2MP LSP: adaptive, cspf, exclude, fast-
8. The following parameters cannot be used with a P2MP LSP: adspec, primary, secondary,
9. The node ingress LER will not inset an adspec object in the path message of an S2L sub-
10. The to parameter is not available at the LSP level but at the path level of each S2L sub-
11. The hold-timer configured in the config>router>mpls>hold-timer context applies when
12. The head-end node can add and/or remove a S2L sub-LSP of a specific leaf node without
13. The head-end node performs a make-before break (MBB) on an individual S2L path of a
14. All other configuration changes, such as adaptive/no-adaptive (when an MBBis in
15. MPLS requests CSPF to re-compute the whole set of S2L paths of a given active P2MP
16. MPLS will request CSPF to re-compute the whole set of S2L paths of a given active
17. When performing global MBB, MPLS runs a separate MBB on each S2L in the P2MP
7450 ESS MPLS Guide
node to switch the path of the LSP from the primary P2MP instance to the secondary
P2MP instance is to be determined. This could be based on the number of leaf LSPs which
went down at any given time.
reroute, from, hop-limit, include, metric, retry-limit, retry-timer, resignal-timer.
to.
LSP. If received in the resv message, it will be dropped. The operational MTU of an S2L
path is derived from the MTU of the outgoing interface of that S2L path.
LSP of the primary or secondary instance of this P2MP LSP.
signaling or re-signaling an individual S2L sub-LSP path. It does not apply when the
entire tree is signaled or re-signaled.
impacting forwarding over the already established S2L sub-LSPs of this P2MP LSP and
without re-signaling them.
primary P2MP instance whenever it applies the FRR global revertive procedures to this
path. If CSPF finds a new path, RSVP signals this S2L path with the same LSP-ID as the
existing path.
progress), use-te-metric, no-frr, cspf/no-cspf, result in the tear-down and re-try of all
affected S2L paths.
instance each time the P2MP re-signal timer expires. The P2MP re-signal timer is
configured separately from the P2P LSP. MPLS performs a global MBB and moves each
S2L sub-LSP in the instance into its new path using a new P2MP LSP ID if the global
MBB is successful. This is regardless of the cost of the new S2L path.
P2MP instance each time the user performs a manual re-signal of the P2MP instance.
MPLS then always performs a global MBB and moves each S2L sub-LSP in the instance
into its new path using a new P2MP LSP ID if the global MBB is successful. This is
regardless of the cost of the new S2L path. The user executes a manual re-signal of the
P2MP LSP instance using the command: tools>perform>router>mpls>resignal p2mp-
lsp lsp-name p2mp-instance instance-name.
LSP instance. If an S2L MBB does not succeed the first time, MPLS will re-try the S2L
using the re-try timer and re-try count values inherited from P2MP LSP configuration.
MPLS and RSVP
Page 163