When you configure TE tunnel with multiple protection on its path and merge point is the same node for
more than one protection, you must configure record-route for that tunnel.
Note
Related Topics
Protecting MPLS Tunnels with Fast Reroute, on page 220
IS-IS IP Fast Reroute Loop-free Alternative
For bandwidth protection, there must be sufficient backup bandwidth available to carry primary tunnel traffic.
Use the ipfrr lfa command to compute loop-free alternates for all links or neighbors in the event of a link or
node failure. To enable node protection on broadcast links, IPRR and bidirectional forwarding detection (BFD)
must be enabled on the interface under IS-IS.
MPLS FRR and IPFRR cannot be configured on the same interface at the same time.Note
For information about configuring BFD, see Cisco IOS XR Interface and Hardware Configuration Guide for
the Cisco CRS-1 Router.
MPLS-TE and Fast Reroute over Link Bundles
MPLS Traffic Engineering (TE) and Fast Reroute (FRR) are supported over bundle interfaces. MPLS-TE/FRR
over virtual local area network (VLAN) interfaces is supported. Bidirectional forwarding detection (BFD)
over VLAN is used as an FRR trigger to obtain less than 50 milliseconds of switchover time.
These link bundle types are supported for MPLS-TE/FRR:
•
Over POS link bundles.
•
Over Ethernet link bundles.
•
Over VLANs over Ethernet link bundles.
•
Number of links are limited to 100 for MPLS-TE and FRR.
•
VLANs go over any Ethernet interface (for example, GigabitEthernet, TenGigE, and FastEthernet, so
forth).
FRR is supported over bundle interfaces in the following ways:
•
Uses minimum links as a threshold to trigger FRR over a bundle interface.
•
Uses the minimum total available bandwidth as a threshold to trigger FRR.
Cisco IOS XR MPLS Configuration Guide for the Cisco CRS Router, Release 5.1.x
176
Implementing MPLS Traffic Engineering
MPLS-TE and Fast Reroute over Link Bundles
To Next Page
Loading...
Need help?
General
