Alcatel-Lucent 7450 Manual page 568

Feature Behavior
get associated with an LDP session to the peer if one exists or it will trigger the establishment of a
new targeted LDP session to the peer.
The SR OS supports multiple ways of establishing a targeted Hello adjacency to a peer LSR:
•
•
•
•
•
•
Since the above triggering events can occur simultaneously or in any arbitrary order, the LDP code
implements a priority handling mechanism in order to decide which event overrides the active
targeted session parameters. The overriding trigger will become the owner of the targeted
adjacency to a given peer and will be shown in show router ldp targ-peer.
Page 568
User configuration of the peer with the targeted session parameters inherited from the
config>router>ldp>targeted-session>ipv4 in the top level context or explicitly
configured for this peer in the config>router>ldp>targeted-session>peer context and
which overrides the top level parameters shared by all targeted peers. Let us refer to the
top level configuration context as the global context. Note that some parameters only exist
in the global context and as such their value will always be inherited by all targeted peers
regardless of which event triggered it.
User configuration of an SDP of any type to a peer with the signaling tldp option enabled
(default configuration). In this case the targeted session parameter values are taken from
the global context.
User configuration of a (FEC 129) PW template binding in a BGP-VPLS service. In this
case the targeted session parameter values are taken from the global context.
User configuration of a (FEC 129 type II) PW template binding in a VLL service
(dynamic multi-segment PW). In this case the target session parameter values are taken
from the global context
This Release 11.0.R4 user configuration of a mapping of a targeted session peer parameter
template to a prefix policy when the peer address exists in the TE database. In this case,
the targeted session parameter values are taken from the template.
Note that features using an LDP LSP, which itself is tunneled over an RSVP LSP (LDP-
over-RSVP), as a shortcut do not trigger automatically the creation of the targeted Hello
adjacency and LDP session to the destination of the RSVP LSP. The user must configure
manually the peer parameters or configure a mapping of a targeted session peer parameter
template to a prefix policy. These features are:
→ BGP shortcut (next-hop-resolution shortcut-tunnel option in BGP),
→ IGP shortcut (rsvp-shortcut option in IGP),
→ LDP shortcut for IGP routes (ldp-shortcut option in router level),
→ static route LDP shortcut (ldp option in a static route),
→ VPRN service (auto-bind-tunnel ldp option), and
7450 ESS MPLS Guide