Alcatel-Lucent 7450 Manual page 674

import-prefixes
Syntax
Context
Description
Default
Parameters
path-mtu-discovery
Syntax
Context
Description
Default
Page 674
[no] import-prefixes policy-name
config>router>ldp>session-parameters>peer
This command configures the import FEC prefix policy to determine which prefixes received from
this LDP peer are imported and installed by LDP on this node. If resolved these FEC prefixes are
then re-distributed to other LDP and T-LDP peers. A FEC prefix that is filtered out (deny) will not be
imported. A FEC prefix that is filtered in (accept) will be imported.
If no import policy is specified, the node will import all prefixes received from this LDP/T-LDP peer.
This policy is applied in addition to the global LDP policy and targeted session policy.
Policies are configured in the config>router>policy-options context. A maximum of five policy
names can be specified. Peer address has to be the peer LSR-ID address.
The no form of the command removes the policy from the configuration.
no import-prefixes - no import route policy is specified
policy-name — The import-prefix route policy name. Allowed values are any string up to 32
characters long composed of printable, 7-bit ASCII characters excluding double quotes. If the
string contains spaces, use double quotes to delimit the start and end of the string. The specified
name(s) must already be defined.
path-mtu-discovery
no path-mtu-discovery
config>router>ldp>tcp-session-parameters>peer-transport
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.
no path-mtu-discovery
7450 ESS MPLS Guide