Alcatel-Lucent 7210 SAS M User Manual page 231

Table 5: Triggering Events and the Associated Priority
Triggering Event
LDP-over-RSVP as a
BGP/IGP/LDP/Static
shortcut
LDP-over-RSVP in
VPRN auto-bind
LDP-over-RSVP in BGP
Label Route resolution
Triggering EventAutomatic Creation of Targeted Hello AdjacencyActive Targeted Adjacency
Parameter Override Priority
Manual configuration of peer parameters (creator=manual)Yes1
Mapping of targeted session template to prefix policy (creator=template)Yes2
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
The above table shows the 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:
•
7210 SAS M, T, X, R6, Mxp MPLS Configuration Guide
Automatic Creation of Tar-
No
No
No
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.
geted Hello Adjacency
Label Distribution Protocol
Active Targeted Adjacency
Parameter Override Priority
N/A
N/A
N/A
Page 231