Ldp Frr Procedures - Alcatel-Lucent 7210 SAS M User Manual

Label Distribution Protocol
Note that when an interface is excluded from the LFA SPF in IS-IS, it is excluded in both level 1
and level 2. When the user excludes an interface from the LFA SPF in OSPF, it is excluded in all
areas. However, the above OSPF command can only be executed under the area in which the
specified interface is primary and once enabled, the interface is excluded in that area and in all
other areas where the interface is secondary. If the user attempts to apply it to an area where the
interface is secondary, the command will fail.

LDP FRR Procedures

The LDP FEC resolution when LDP FRR is not enabled operates as follows. When LDP receives
a FEC, label binding for a prefix, it will resolve it by checking if the exact prefix, or a longest
match prefix when the aggregate-prefix-match option is enabled in LDP, exists in the routing
table and is resolved against a next-hop which is an address belonging to the LDP peer which
advertized the binding, as identified by its LSR-id. When the next-hop is no longer available, LDP
de-activates the FEC and de-programs the NHLFE in the data path. LDP will also immediately
withdraw the labels it advertised for this FEC and deletes the ILM in the data path unless the user
configured the label-withdrawal-delay option to delay this operation. Traffic that is received
while the ILM is still in the data path is dropped. When routing computes and populates the
routing table with a new next-hop for the prefix, LDP resolves again the FEC and programs the
data path accordingly.
When LDP FRR is enabled and an LFA backup next-hop exists for the FEC prefix in RTM, or for
the longest prefix the FEC prefix matches to when aggregate-prefix-match option is enabled in
LDP, LDP will resolve the FEC as above but will program the data path with both a primary
NHLFE and a backup NHLFE for each next-hop of the FEC.
In order perform a switchover to the backup NHLFE in the fast path, LDP follows the uniform
FRR failover procedures which are also supported with RSVP FRR.
When any of the following events occurs, LDP instructs in the fast path the IOM to enable the
backup NHLFE for each FEC next-hop impacted by this event. The IOM do that by simply
flipping a single state bit associated with the failed interface or neighbor/next-hop:
1. An LDP interface goes operationally down, or is admin shutdown. In this case, LDP sends
2. An LDP session to a peer went down as the result of the Hello or Keep-Alive timer
3. The TCP connection used by a link LDP session to a peer went down, due say to next-hop
Page 244
ration Guide
a neighbor/next-hop down message to the IOM for each LDP peer it has adjacency with
over this interface.
expiring over a specific interface. In this case, LDP sends a neighbor/next-hop down
message to the IOM for this LDP peer only.
tracking of the LDP transport address in RTM, which brings down the LDP session. In this
case, LDP sends a neighbor/next-hop down message to the IOM for this LDP peer only.
7210 SAS M, T, X, R6, Mxp MPLS Configu-