session-parameters
config>router>ldp
This command enables the context to configure peer-specific parameters.
[no] peer ip-address
config>router>ldp>session-params
This command configures parameters for an LDP peer.
n/a
specifies the LDP peer in dotted-decimal notation
export-addresses policy-name [policy-name...(up to 5 max)]
no export-addresses
config>router>ldp>session-params>peer
This command specifies the export prefix policy to local addresses advertised to this peer.
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified.
The no form of the command removes the policy from the configuration.
no export-addresses
the name of an existing export prefix route policy
export-prefixes policy-name [policy-name...(up to 5 max)]
no export-prefixes
config>router>ldp>session-params>peer
This command specifies the export route policy used to determine which prefixes received from other LDP peers are redistributed to this LDP via the LDP session to this peer. Any prefix that has been accepted in the route policy will be exported. Any prefix that has been filtered out of the route policy will not be exported.
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified. The peer address must be the peer LSR ID.
If no export policy is specified, all FEC prefixes learned will be exported to this LDP peer. This policy is applied in addition to the global LDP export policy and targeted sessions.
The no form of the command removes the policy from the configuration.
no export-prefixes
the name of an existing export policy
fec-type-capability
config>router>ldp>if-params>if>ipv4
config>router>ldp>if-params>if>ipv6
config>router>ldp>session-params>peer
This command enables or disables the advertisement of a FEC type for a specified LDP session or Hello adjacency to a peer.
n/a
p2mp {enable | disable}
config>router>ldp>session-params>peer>fec-type-capability
This command enables or disables P2MP FEC capability for the session.
p2mp disable
enables or disables P2MP FEC capability
prefix-ipv4 {enable | disable}
config>router>ldp>if-params>if>ipv4>fec-type-capability
config>router>ldp>if-params>if>ipv6>fec-type-capability
config>router>ldp>session-params>peer>fec-type-capability
This command enables or disables IPv4 prefix FEC capability on the session or interface.
prefix-ipv4 disable
enables or disables IPv4 prefix FEC capability
prefix-ipv6 {enable | disable}
config>router>ldp>if-params>if>ipv4
config>router>ldp>if-params>if>ipv6
config>router>ldp>session-params>peer>fec-type-capability
This command enables or disables IPv6 prefix FEC capability on the session or interface.
prefix-ipv6 disable
enables or disables IPv6 prefix FEC capability
tcp-session-parameters
config>router>ldp
This command enables the context to configure parameters for the TCP transport session of an LDP session to a remote peer.
n/a
[no] peer-transport ip-address
config>router>ldp>tcp-session-parameters
This command configures the peer transport address, which is the IPv4 or IPv6 destination address of the TCP connection to the LDP peer.
n/a
the IPv4 or IPv6 address of the TCP connection to the LDP peer in dotted-decimal notation
auth-keychain name
no auth-keychain
config>router>ldp>tcp-session-params>peer-transport
This command associates an authentication keychain with LDP. The keychain is a collection of keys used to authenticate LDP messages from remote peers. The keychain allows the rollover of authentication keys during the lifetime of a session and also supports stronger authentication algorithms than clear text and MD5.
The keychain must already be defined in the config>system>security>keychain context.
Either the authentication-key command or the auth-keychain command can be used by LDP, but both cannot be supported at the same time. If both commands are configured, the auth-keychain configuration is applied and the authentication-key command is ignored.
By default, authentication is not enabled.
no auth-keychain
the name of an existing keychain, up to 32 characters
authentication-key {authentication-key|hash-key}[hash | hash2]
no authentication-key
config>router>ldp>tcp-session-params>peer-transport
This command specifies the authentication key to be used between LDP peers before establishing sessions. Authentication uses the MD5 message-based digest.
Either the authentication-key command or the auth-keychain command can be used by LDP, but both cannot be supported at the same time. If both commands are configured, the auth-keychain configuration is applied and the authentication-key command is ignored.
The no form of this command disables authentication.
n/a
specifies the authentication key. Allowed values are any string up to 16 characters long (unencrypted) composed of printable, 7-bit ASCII characters. If the string contains special characters (such as #, $, spaces), the entire string must be enclosed within double quotes.
specifies the hash key. Allowed values are any string up to 33 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (such as #, $, spaces), the entire string must be enclosed within double quotes.
This is useful when a user must configure the parameter; however, for security purposes, the actual unencrypted key value is not provided.
specifies that the key is entered and stored on the node in encrypted form
specifies that the key is entered and stored on the node in a more complex encrypted form
If neither the hash or hash2 keyword is specified, the key is entered in clear text. However, for security purposes, the key is stored on the node using hash encryption.