mpls te backup bandwidth
Use mpls te backup bandwidth to configure the bandwidth and the CT that the bypass tunnel can protect.
Use undo mpls te backup bandwidth to restore the default.
Syntax
mpls te backup bandwidth [ ct0 | ct1 | ct2 | ct3 ] { bandwidth | un-limited }
undo mpls te backup bandwidth
Default
The bandwidth and the CT that the bypass tunnel can protect are not specified.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
ct0: Specifies the bypass tunnel to protect only CRLSPs of CT 0.
ct1: Specifies the bypass tunnel to protect only CRLSPs of CT 1.
ct2: Specifies the bypass tunnel to protect only CRLSPs of CT 2.
ct3: Specifies the bypass tunnel to protect only CRLSPs of CT 3.
bandwidth: Specifies the total bandwidth that the bypass tunnel can protect, in the range of 1 to 4294967295, in kbps.
un-limited: Puts no limit on total protected bandwidth. This keyword means the bypass tunnel does not provide bandwidth protection.
Usage guidelines
If no CT is specified, CRLSPs of all CTs can use the bypass tunnel.
If you specify the un-limited keyword, the bypass tunnel does not provide bandwidth protection. FRR does not guarantee the bandwidth of the protected tunnels. If the sum of traffic of the protected tunnels exceeds the actual bandwidth of the bypass tunnel, traffic of protected tunnels might be lost. The primary CRLSP that does not need bandwidth protection prefers this type of bypass tunnels over other types of bypass tunnels.
If you specify the bandwidth argument, the bypass tunnel provides bandwidth protection. The primary CRLSP that needs bandwidth protection prefers this type of bypass tunnels over other types of bypass tunnels. If you set the value for the bandwidth argument to 0, the bypass tunnel performs best-effort forwarding for the traffic of primary CRLSP, and the occupied bandwidth is not fixed. Therefore, this type of bypass tunnel cannot protect a primary CRLSP with the bandwidth 0 or a primary CRLSP whose bandwidth exceeds the protected bandwidth.
The specified bandwidth value must be less than the actual bandwidth of the bypass tunnel. Otherwise, the bypass tunnel will be overwhelmed after FRR, and the protected tunnel might be torn down.
After an FRR, the primary CRLSP will be down if you modify the bandwidth that the bypass tunnel can protect and your modification results in one of the following:
The CT type changes.
The bypass tunnel cannot protect adequate bandwidth as configured.
FRR protection type (whether or not to provide bandwidth protection for the primary CRLSP) changes.
The bandwidth value specified is used only for calculating and determining the bandwidth protection relationship between a primary CRLSP and a bypass tunnel. The bandwidth is not reserved on the bypass tunnel.
After you execute this command for a tunnel, the record route flag is automatically set for the tunnel, regardless of whether the mpls te record-route command is configured.
Examples
# Configure Tunnel 0 to provide protection for CRLSPs of CT 0 without constraining the protected bandwidth. Configure Tunnel 1 to provide protection for CRLSPs of CT 1 and protect a maximum of 1000 kbps bandwidth.
<Sysname> system-view [Sysname] interface tunnel 0 mode mpls-te [Sysname-Tunnel0] mpls te backup bandwidth ct0 un-limited [Sysname-Tunnel0] quit [Sysname] interface tunnel 1 [Sysname-Tunnel1] mpls te backup bandwidth ct1 1000
Related commands
display mpls te tunnel-interface
mpls te fast-reroute