72
NOTE:
Configure CR-LSP backup mode at the ingress node of a tunnel. The system automatically selects the
primary LSP and backup LSP. You do not need to configure them.
Configuring FRR
NOTE:
Do not configure both FRR and RSVP authentication on the same interface.
As mentioned earlier, FRR provides quick but temporary per-link or per-node local protection on an LSP.
FRR uses bypass tunnels to protect primary tunnels. As bypass tunnels are pre-established, they require
extra bandwidth and are usually used to protect crucial interfaces or links only.
You can define which type of LSP can use bypass LSPs, and whether a bypass LSP provides bandwidth
protection as well as the sum of protected bandwidth.
The bandwidth of a bypass LSP is to protect its primary LSPs. To guarantee that a primary LSP can always
bind with the bypass LSP successfully, make sure that the bandwidth assigned to the bypass LSP is not less
than the total bandwidth needed by all protected LSPs.
Normally, bypass tunnels only forward data traffic when protected primary tunnels fail. To allow a
bypass tunnel to forward data traffic while protecting the primary tunnel, you need to make sure that
bypass tunnels are available with adequate bandwidth.
A bypass tunnel cannot be used for services like VPN at the same time.
Configuration prerequisites
Before you configure FRR, complete the following tasks:
•
Configure an IGP, making sure that all LSRs are reachable.
•
Configure basic MPLS.
•
Configure MPLS TE basic settings.
•
Establish an MPLS TE tunnel with RSVP-TE.
•
Set up primary LSPs.
Configuration procedure
Enabling FRR on the ingress node of a primary LSP
To enable FRR on the ingress node of a primary LSP:
To do…
Use the command...
Remarks
Enter system view
system-view
––
Enter tunnel interface view of the
primary LSP
interface tunnel
tunnel-number
––
Enable FRR
mpls te fast-reroute
Required
Disabled by default
Submit current tunnel configuration
mpls te commit
Required
