This section provides information to configure LDP using the command line interface.
When the implementation of LDP is instantiated, the protocol is in the no shutdown state. In addition, targeted sessions are then enabled. The default parameters for LDP are set to the documented values for targeted sessions in draft-ietf-mpls-ldp-mib-09.txt.
This chapter provides information to configure LDP and remove configuration examples of common configuration tasks.
The LDP protocol instance is created in the no shutdown (enabled) state.
LDP must be enabled in order for the protocol to be active. MPLS must also be enabled. MPLS is enabled in the config>router>mpls context.
Use the following syntax to enable LDP on a router.
Graceful-restart helper advertises to its LDP neighbors by carrying the fault tolerant (FT) session TLV in the LDP initialization message, assisting the LDP in preserving its IP forwarding state across the restart. Nokia’s recovery is self-contained and relies on information stored internally to self-heal. This feature is only used to help third-party routers without a self-healing capability to recover.
Maximum recovery time is the time (in seconds) the sender of the TLV would like the receiver to wait, after detecting the failure of LDP communication with the sender.
Neighbor liveness time is the time (in seconds) the LSR is willing to retain its MPLS forwarding state. The time should be long enough to allow the neighboring LSRs to re-sync all the LSPs in a graceful manner, without creating congestion in the LDP control plane.
Use the following syntax to configure graceful-restart parameters.
Both inbound and outbound label binding filtering are supported. Inbound filtering allows a route policy to control the label bindings an LSR accepts from its peers. An import policy can accept or reject label bindings received from LDP peers.
Label bindings can be filtered based on:
Outbound filtering allows a route policy to control the set of LDP label bindings advertised by the LSR. An export policy can control the set of LDP label bindings advertised by the router. By default, label bindings for only the system address are advertised and propagate all FECs that are received.
Matches can be based on:
Use the following syntax to apply import and export policies.
Use the following syntax to specify targeted-session parameters.
The following is a sample LDP configuration output.
Use the following syntax to configure interface parameters.
The following is a sample interface parameter configuration output.
Use the following syntax to specify session parameters.
When LDP is enabled, targeted sessions can be established to create remote adjacencies with nodes that are not directly connected. When service distribution paths (SDPs) are configured, extended discovery mechanisms enable LDP to send periodic targeted hello messages to the SDP’s far-end point. The exchange of LDP hellos trigger session establishment. The SDP’s signaling default enables tldp. The service SDP uses the targeted-session parameters configured in the config>router>ldp>targeted-session context.
Use the following syntax to configure enable LDP on an MPLS SDP.
The following is a sample SDP configuration output showing the signaling default tldp enabled.
This section describes the LDP configuration management tasks.
The no ldp command disables the LDP protocol on the router. All parameters revert to the default settings. LDP must be shut down before it can be disabled.
Use the following command syntax to disable LDP.
The modification of LDP targeted session parameters does not take effect until the next time the session goes down and is re-establishes. Individual parameters cannot be deleted. The no form of a targeted-session parameter command reverts modified values back to the default.
The following shows the command usage to revert targeted session parameters back to the default values.
The following output displays the default values.
The modification of LDP targeted session parameters does not take effect until the next time the session goes down and is re-establishes. Individual parameters cannot be deleted. The no form of a interface-parameter command reverts modified values back to the defaults.