Alcatel-Lucent 7450 - Page 679

Targeted Session Commands
7450 ESS MPLS Guide Page 679
disable-targeted-session
Syntax [no] disable-targeted-session
Context config>router>ldp>targ-session
Description This command disables support for SDP triggered automatic generated targeted sessions. Targeted
sessions are LDP sessions between non-directly connected peers. The discovery messages for an
indirect LDP session are addressed to the specified peer and not to the multicast address.
The no form of the command enables the set up of any targeted sessions.
Default no disable-targeted-session
peer
Syntax [no] peer ip-address
Context config>router>ldp>targeted-session
Description This command configures parameters for an LDP peer.no
Default none
Parameters ip-address — The IPv4 or IPv6 address of the LDP peer in dotted decimal notation.
peer-template-map
Syntax peer-template-map template-name policy peer-prefix-policy1 [peer-prefix-policy2..up to 5]
no peer-template-map peer-template template-name
Context config>router>ldp>targeted-session
Description This command enables the automatic creation of a targeted Hello adjacency and LDP session to a
discovered peer. The user configures a targeted session peer parameter template and binds it to a peer
prefix policy.
Each application of a targeted session template to a given prefix in the prefix list will result in the
establishment of a targeted Hello adjacency to an LDP peer using the template parameters as long as
the prefix corresponds to a router-id for a node in the TE database. As a result of this, the user must
enable the traffic-engineering option in ISIS or OSPF. The targeted Hello adjacency will either trigger
a new LDP session or will be associated with an existing LDP session to that peer.
Up to 5 peer prefix policies can be associated with a single peer template at all times. Also, the user
can associate multiple templates with the same or different peer prefix policies. Thus multiple
templates can match with a given peer prefix. In all cases, the targeted session parameters applied to a
given peer prefix are taken from the first created template by the user. This provides a more
deterministic behavior regardless of the order in which the templates are associated with the prefix
policies.