(Optional) Configuring Dynamic Bandwidth for Hot-Standby CR-LSPs
Context
Hot-standby CR-LSPs are established using reserved bandwidth resources by default. The dynamic bandwidth function can be configured to allow the system to create a primary CR-LSP and a hot-standby CR-LSP with the bandwidth of 0 bit/s simultaneously.
The dynamic bandwidth protection function allows a hot-standby CR-LSP to obtain bandwidth resources only after the hot-standby CR-LSP takes over traffic from a faulty primary CR-LSP. If the primary CR-LSP fails, traffic immediately switches to the hot-standby CR-LSP with 0 bit/s bandwidth. The ingress node uses the make-before-break mechanism to reestablish a hot-standby CR-LSP. After the new hot-standby CR-LSP has been successfully established, the ingress node switches traffic to this CR-LSP and tears down the hot-standby CR-LSP with 0 bit/s bandwidth. If bandwidth resources are insufficient, the ingress node is unable to reestablish a hot-standby CR-LSP with the desired bandwidth, and therefore switches traffic to the hot-standby CR-LSP with 0 bit/s bandwidth, ensuring uninterrupted traffic transmission.
Perform the following configurations on the ingress node of an MPLS TE tunnel.
Procedure
- Run system-view
The system view is displayed.
- Run interface tunnel tunnel-number
The tunnel interface view is displayed.
- Run mpls te backup hot-standby dynamic-bandwidth
The dynamic bandwidth function is enabled for hot-standby CR-LSPs.
If a hot-standby CR-LSP has been established before the dynamic bandwidth function is enabled, the system uses the Make-Before-Break mechanism to establish a new hot-standby CR-LSP with the bandwidth of 0 bit/s to replace the existing hot-standby CR-LSP.
The undo mpls te backup hot-standby dynamic-bandwidth command can be used to disable the dynamic bandwidth function. This allows the hot-standby CR-LSP with no bandwidth to obtain bandwidth.
- Run commit
The configuration is committed.