Alcatel-Lucent 7450 Manual page 652

Default
Parameters
fast-reroute
Syntax
Context
Description
Page 652
If no export policy is specified, non-LDP routes will not be exported from the routing table manager
to LDP. LDP-learned routes will be exported to LDP neighbors. Present implementation of export
policy (outbound filtering) can be used "only" to add FECs for label propagation. The export policy
does not control propagation of FECs that an LSR receives from its neighbors.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The
first policy that matches is applied. If multiple export commands are issued, the last command
entered will override the previous command. A maximum of 5 policy names can be specified.
The no form of the command removes all policies from the configuration.
no export — No export route policies specified.
policy-name — The export route policy name. Allowed values are any string up to 32 characters long
composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $,
spaces, etc.), the entire string must be enclosed within double quotes.
The specified name(s) must already be defined.
[no] fast-reroute
config>router>ldp
This command enables LDP Fast-Reroute (FRR) procedures. When enabled, LDP uses both the
primary next-hop and LFA next-hop, when available, for resolving the next-hop of an LDP FEC
against the corresponding prefix in the routing table. This will result in LDP programming a primary
NHLFE and a backup NHLFE into the forwarding engine for each next-hop of a FEC prefix for the
purpose of forwarding packets over the LDP FEC.
When any of the following events occurs, LDP instructs in the fast path the forwarding engines to
enable the backup NHLFE for each FEC next-hop impacted by this event:
• An LDP interface goes operationally down, or is admin shutdown.
• An LDP session to a peer went down as the result of the Hello or Keep-Alive timer
expiring.
• The TCP connection used by a link LDP session to a peer went down, due say to
next-hop tracking of the LDP transport address in RTM, which brings down the
LDP session.
• A BFD session, enabled on a T-LDP session to a peer, times-out and as a result the
link LDP session to the same peer and which uses the same TCP connection as the
T-LDP session goes also down.
• A BFD session enabled on the LDP interface to a directly connected peer, times out
and brings down the link LDP session to this peer.
The tunnel-down-dump-time option or the label-withdrawal-delay option, when enabled, does not
cause the corresponding timer to be activated for a FEC as long as a backup NHLFE is still available.
7450 ESS MPLS Guide