Alcatel-Lucent 7450 Manual page 570

Feature Behavior
Manual configuration of SDP with signaling tldp option enabled (creator=service manager)Yes3
PW template binding in BGP-AD VPLS (creator=service manager)Yes3
PW template binding in FEC 129 VLL (creator=service manager)Yes3
LDP-over-RSVP as a BGP/IGP/ LDP/Static shortcutNoN/A
LDP-over-RSVP in VPRN auto-bindNoN/A
LDP-over-RSVP in BGP Label Route resolutionNoN/A
Table 5 1 Targeted LDP Adjacency Triggering Events and Priority
Note that any parameter value change to an active targeted Hello adjacency caused by any of the
above triggering events is performed on the fly by having LDP immediately send a Hello message
with the new parameters to the peer without waiting for the next scheduled time for the Hello
message. This allows the peer to adjust its local state machine immediately and maintains both the
Hello adjacency and the LDP session in UP state. The only exceptions are the following:
•
•
Finally, the value of any LDP parameter which is specific to the LDP/TCP session to a peer is
inherited from the config>router>ldp>session-parameters>peer context. This includes MD5
authentication, LDP prefix per-peer policies, label distribution mode (DU or DOD), etc.
Page 570
The triggering event caused a change to the local-lsr-id parameter value. In this case, the
Hello adjacency is brought down which will also cause the LDP session to be brought
down if this is the last Hello adjacency associated with the session. A new Hello adjacency
and LDP session will then get established to the peer using the new value of the local LSR
ID.
The triggering event caused the targeted peer shutdown option to be enabled. In this case,
the Hello adjacency is brought down which will also cause the LDP session to be brought
down if this is the last Hello adjacency associated with the session.
7450 ESS MPLS Guide