interface-parameters
config>router>ldp
This command enables the context to configure LDP interfaces and parameters that apply to LDP interfaces.
interface ip-int-namedual-stack]
[no] interface ip-int-name
config>router>ldp>if-params
This command enables LDP on the specified IP interface.
The no form of the command deletes the LDP interface and all configuration information associated with the LDP interface.
The LDP interface must be disabled using the shutdown command before it can be deleted.
You can configure different parameters for IPv4 and IPv6 LDP interfaces by entering ipv4 or ipv6 as the next command.
distinguishes between configurations created before 7705 SAR Release 9.0 from those created in Release 9.0 or later when the interface node implementation was changed to include both IPv4 and IPv6 contexts. If the dual-stack keyword is used, then the IPv4 interface context is not created. If the keyword is not used, then the IPv4 interface context is automatically created.
When entering an already configured interface, there is no need to provide the keyword; it is ignored if it is included.
By default, all configurations created in Release 9.0 or later include dual-stack.
specifies an existing interface. If the string contains special characters (such as #, $, spaces), the entire string must be enclosed within double quotes.
[no] ipv4
config>router>ldp>if-params
config>router>ldp>if-params>if
config>router>ldp>targeted-session
This command enables the context to configure IPv4 LDP parameters that apply to the interface.
[no] ipv6
config>router>ldp>if-params
config>router>ldp>if-params>if
config>router>ldp>targeted-session
This command enables the context to configure IPv6 LDP parameters applied to the interface.
local-lsr-id {system | interface}
no local-lsr-id
config>router>ldp>if-params>if>ipv4
config>router>ldp>if-params>if>ipv6
This command enables the use of the address of the link LDP interface as the LSR ID to establish an LDP adjacency and session with a directly connected LDP peer.
By default, the LDP session uses the system interface address as the LSR ID unless the LSR ID is explicitly configured. This means that targeted LDP (T-LDP) and interface LDP share a common LDP TCP session and therefore a common LDP label space. The system interface must always be configured on the router or the LDP protocol does not come up on the node.
At initial configuration, the LDP session to the peer remains down while the interface is down. If the user changes the LSR ID while the LDP session is up, LDP immediately tears down the session and attempts to re-establish it using the new LSR ID. If the interface used for the local LSR ID goes down, the LDP session also goes down.
The interface option is the recommended setting when static route-LDP synchronization is enabled.
When the interface option is selected, the transport connection (TCP) for the link LDP session configured by the transport-address command is automatically set to interface. Having both the local-lsr-id and transport address set to the local interface creates two TCP sessions to the peer and therefore two different LDP label spaces: one to the interface IP address for link LDP (L-LDP) and one to the system IP address for T-LDP.
The no form of the command resets the local-lsr-id to the default value.
system
specifies that the system IP address is used to set up the LDP session between peers
specifies that the IP interface address is used to set up the LDP session between peers
p2mp-ipv4 {enable | disable}
config>router>ldp>session-params>if>ipv4>fec-type-capability
config>router>ldp>session-params>if>ipv6>fec-type-capability
This command enables or disables IPv4 P2MP FEC capability on the interface.
p2mp disable
enables or disables IPv4 P2MP FEC capability
p2mp-ipv6 {enable | disable}
config>router>ldp>session-params>if>ipv4>fec-type-capability
config>router>ldp>session-params>if>ipv6>fec-type-capability
This command enables or disables IPv6 P2MP FEC capability on the interface.
p2mp disable
enables or disables IPv6 P2MP FEC capability
transport-address {system | interface}
no transport-address
config>router>ldp>if-params>ipv4
config>router>ldp>if-params>ipv6
config>router>ldp>if-params>if>ipv4
config>router>ldp>if-params>if>ipv6
This command configures the transport address to be used when setting up the LDP TCP sessions. The transport address can be configured globally (applies to all LDP interfaces) or per interface. The most specific value is used.
With the transport-address command, you can set up the LDP interface to the connection that can be set to the interface address or the system address. However, there can be an issue of which address to use when there are parallel adjacencies. This address selection situation can also occur when there is a link and a targeted adjacency, because targeted adjacencies request the session to be set up only to the system IP address.
The transport-address value should not be interface if multiple interfaces exist between two LDP neighbors.
Depending on the first adjacency to be formed, the TCP endpoint is chosen. In other words, if one LDP interface is set up as transport-address interface and another as transport-address system, then, depending on which adjacency was set up first, the TCP endpoint addresses are determined. After that, because the hello contains the LSR ID, the LDP session can be checked to verify that it is set up and then the adjacency can be matched to the session.
The no form of the command:
at the global level, sets the transport address to the default value
at the interface level, sets the transport address to the value defined under the global level
system
specifies that the IP interface address is used to set up the LDP session between neighbors. The transport address interface cannot be used if multiple interfaces exist between two neighbors, because only one LDP session is set up between two neighbors.
specifies that the system IP address is used to set up the LDP session between neighbors