119
Ste
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter tunnel interface view of
the protected LSP.
interface tunnel tunnel-number N/A
3. Enable FRR.
mpls te fast-reroute
Disabled by default.
Do not configure both FRR and
RSVP authentication on the same
interface.
4. Submit current tunnel
configuration.
mpls te commit N/A
Configuring a bypass tunnel on its PLR
After a tunnel is specified to protect an interface, its corresponding LSP becomes a bypass LSP. The setup
of a bypass LSP must be manually performed on the PLR. The configuration of a bypass LSP is similar to
that of a common LSP, but a bypass LSP cannot act as an LSP to be protected by another LSP at the same
time.
When specifying a bypass tunnel for an interface, make sure:
• The bypass tunnel is up.
• The protected interface is not the outgoing interface of the bypass tunnel.
Up to three bypass tunnels can be specified for a protected interface. The best-fit algorithm determines
which of them is used in case a failure occurs.
Your device has a restriction on links that use the same bypass tunnel so their total bandwidth does not
exceeds a specific value.
To configure a bypass tunnel on its PLR:
Ste
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter interface view of the
bypass tunnel.
interface tunnel tunnel-number N/A
3. Specify the destination
address of the bypass tunnel.
destination ip-address
For node protection, this is the LSR ID
of the next hop router of PLR.
For link protection, this is the LSR ID of
the next hop device of PLR.
4. Configure the bandwidth that
the bypass tunnel can protect.
mpls te backup bandwidth
bandwidth
Bandwidth is not protected by
default. You must use this command
to configure the bandwidth to
protect. Otherwise, the bypass tunnel
cannot be successfully bound to a
protected LSP.
5. Submit current tunnel
configuration.
mpls te commit N/A
6. Return to system view.
quit N/A
To Next Page
Loading...
Need help?
General
