TCP Session Parameters Commands
7450 ESS MPLS Guide Page 685
to the same peer LSR are different from the LSR-ID value, the user must add each of the transport
addresses to the authentication-key configuration as a separate peer. This means when the TCP
connection is bootstrapped by a given Hello adjacency, the authentication can operate over that
specific TCP connection by using its specific transport address.
The no form of this command disables authentication.
Default none
Parameters authentication-key — The authentication key. The key can be any combination of ASCII characters
up to 16 characters in length (unencrypted). If spaces are used in the string, enclose the entire
string in quotation marks (“ ”).
hash-key — The hash key. The key can be any combination of up 33 alphanumeric characters. If
spaces are used in the string, enclose the entire string in quotation marks (“ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual
unencrypted key value is not provided.
hash — Specifies the key is entered in an encrypted form. If the hash keyword is not used, the key is
assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted
form in the configuration file with the hash parameter specified.
hash2 — Specifies the key is entered in a more complex encrypted form. If the hash2 parameter is
not used, the less encrypted hash form is assumed.
path-mtu-discovery
Syntax path-mtu-discovery
no path-mtu-discovery
Context config>router>ldp>tcp-session-parameters>peer-transport
Description This command enables Path MTU discovery for the associated TCP connections. When enabled, the
MTU for the associated TCP session is initially set to the egress interface MTU. The DF bit is also set
so that if a router along the path of the TCP connection cannot handle a packet of a particular size
without fragmenting, it sends back and ICMP message to set the path MTU for the given session to a
lower value that can be forwarded without fragmenting.
Note that if one or more transport addresses used in the Hello adjacencies to the same peer LSR are
different from the LSR-ID value, the user must add each of the transport addresses to the path MTU
discovery configuration as a separate peer. This means when the TCP connection is bootstrapped by a
given Hello adjacency, the path MTU discovery can operate over that specific TCP connection by
using its specific transport address.
Default no path-mtu-discovery
To Next Page
Loading...
