Login
- Table of Contents
-
- 10-MPLS Command Reference
- 00-Preface
- 01-Basic MPLS commands
- 02-Static LSP commands
- 03-LDP commands
- 04-MPLS TE commands
- 05-Static CRLSP commands
- 06-RSVP commands
- 07-Tunnel policy commands
- 08-MPLS L2VPN commands
- 09-MPLS L3VPN commands
- 10-L2VPN access to L3VPN or IP backbone commands
- 11-MPLS OAM commands
- 12-MPLS protection switching commands
- 13-MCE commands
- 14-VPLS commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 12-MPLS protection switching commands | 139.12 KB |
MPLS protection switching commands
display interface tunnel-bundle
display mpls forwarding protection
interface tunnel-bundle protection
protection switching-mode bidirectional
reset counters interface tunnel-bundle
MPLS protection switching commands
bandwidth
Use bandwidth to set the expected bandwidth for an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth of an interface is 64 kbps.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth for an interface affects the CBQ bandwidth, and the link costs in OSPF, OSPFv3, and IS-IS. For more information about the CBQ bandwidth, see ACL and QoS Configuration Guide. For more information about the link costs, see Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth to 1000 kbps for Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2
[Sysname-tunnel-bundle2] bandwidth 1000
Related commands
display interface tunnel-bundle
default
Use default to restore the default settings for a tunnel bundle interface.
Syntax
default
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Usage guidelines
|
|
CAUTION: The default command might interrupt ongoing network services. Make sure you are fully aware of the impact of this command when you use it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies or system restrictions. Use the display this command in interface view to identify these commands. Use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings of Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2
[Sysname-tunnel-bundle2] default
description
Use description to configure the description of an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of a tunnel bundle interface is Tunnel-Bundlenumber Interface, for example, Tunnel-Bundle1 Interface.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 255 characters.
Usage guidelines
Configure descriptions for interfaces for identification and management purposes.
You can use the display interface command to display the configured interface descriptions.
Examples
# Configure a description of tunnel-bundle2 for Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2
[Sysname-tunnel-bundle2] description tunnel-bundle2
Related commands
display interface tunnel-bundle
destination
Use destination to specify the destination address for a tunnel bundle interface.
Use undo destination to restore the default.
Syntax
destination ip-address
undo destination
Default
No tunnel destination address is configured.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the tunnel destination IPv4 address.
Usage guidelines
For MPLS L3VPN, MPLS L2VPN, and VPLS, the tunnel destination address in this command determines whether the tunnel bundle can be the public tunnel to carry VPN services. When the remote PE address is the same as the tunnel destination address for a tunnel bundle interface, the tunnel bundle can be the public tunnel.
As a best practice, configure the same tunnel destination address for a tunnel bundle interface and its member interfaces. If they have different tunnel destination addresses, make sure the member interfaces have a route to the tunnel bundle interface for successful traffic forwarding.
Examples
# Specify 2.2.2.2 as the destination address for Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2
[Sysname-tunnel-bundle2] destination 2.2.2.2
Related commands
display interface tunnel-bundle
display tunnel-bundle
display interface tunnel-bundle
Use display interface tunnel-bundle to display tunnel bundle interface information.
Syntax
display interface [ tunnel-bundle [ number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
tunnel-bundle [ number ]: Specifies a tunnel bundle interface. The number argument specifies the tunnel bundle interface number. If you do not specify the tunnel-bundle keyword, this command displays information about all interfaces on the device. If you specify the tunnel-bundle keyword without the number argument, this command displays information about all existing tunnel bundle interfaces.
number: Specifies the number of an existing tunnel bundle interface.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays information about interfaces in the physical state of DOWN and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display detailed information about Tunnel-Bundle 100.
<Sysname> display interface tunnel-bundle 100
Tunnel-Bundle100
Current state: UP
Line protocol state: UP
Description: Tunnel-Bundle100 Interface
Bandwidth: 64kbps
Maximum transmission unit: 64000
Internet address: 2.2.2.2/24 (primary)
Tunnel-Bundle destination unknown
Tunnel type: CRLSP
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 drops
Output: 0 packets, 0 bytes, 0 drops
Table 1 Command output
|
Field |
Description |
|
Tunnel-Bundle100 |
Information about the tunnel bundle interface Tunnel-Bundle 100. |
|
Current state |
State of the tunnel bundle interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down. · UP—The interface is both administratively and physically up. |
|
Line protocol state |
Data link layer state of the tunnel bundle interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · UP (spoofing)—The data link layer protocol is up, but the link is an on-demand link or does not exist. This attribute is typical of null interfaces and loopback interfaces. · DOWN—The data link layer protocol is down. |
|
Description |
Description of the tunnel bundle interface. |
|
Bandwidth |
Expected bandwidth of the tunnel bundle interface. |
|
Maximum transmission unit |
MTU of the tunnel bundle interface. |
|
Internet address: ip-address/mask-length (Type) |
IP address of the interface and type of the address in parentheses. Possible IP address types include: · Primary—Manually configured primary IP address. · Sub—Manually configured secondary IP address. If the interface has both primary and secondary IP addresses, the primary IP address is displayed. If the interface has only secondary IP addresses, the lowest secondary IP address is displayed. · DHCP-Allocated—DHCP allocated IP address. For more information, see DHCP client configuration in Layer 3—IP Services Configuration Guide. · BOOTP-Allocated—BOOTP allocated IP address. For more information, see BOOTP client configuration in Layer 3—IP Services Configuration Guide. · PPP-Negotiated—IP address assigned by a PPP server during PPP negotiation. For more information, see PPP configuration in Layer 2—WAN Access Configuration Guide. · Unnumbered—IP address borrowed from another interface. · Cellular-Allocated—IP address allocated through the modem-manufacturer's proprietary protocol. For more information, see 3G/4G modem management in Layer 2—WAN Access Configuration Guide. · MAD—IP address assigned to an IRF member device for MAD on the interface. For more information, see IRF configuration in Virtual Technologies Configuration Guide. · MTunnel—IP address of the multicast tunnel interface (MTI), which is the same as the IP address of the MVPN source interface. For more information, see multicast VPN configuration in IP Multicast Configuration Guide. |
|
Internet protocol processing: Disabled |
The interface is not assigned an IP address and cannot process IP packets. |
|
Internet Address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
|
Tunnel-Bundle destination |
Destination address of the tunnel bundle interface. unknown indicates that no destination address is assigned to the interface. |
|
Tunnel type |
Tunnel mode for the tunnel bundle interface. The value can only be CRLSP. |
|
Last clearing of counters |
Last time when counters were cleared. |
|
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec |
Average input rate in the last 300 seconds. |
|
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec |
Average output rate in the last 300 seconds. |
# Display brief information about Tunnel-Bundle 100.
<Sysname> display interface tunnel-bundle 100 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Tunnel-B100 UP UP -- aaaaaaaaaaaaaaaaaaaaaaaaaaa
# Display brief information about Tunnel-Bundle 100, including the complete interface description.
<Sysname> display interface tunnel-bundle 100 brief description
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Tunnel-B100 UP UP -- aaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
# Display information about interfaces in DOWN state and the causes.
<Sysname> display interface tunnel-bundle brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Tunnel-B100 DOWN Not connected
Tunnel-B101 DOWN Not connected
Table 2 Command output
|
Field |
Description |
|
Brief information on interfaces in route mode |
Brief information about Layer 3 interfaces. |
|
Interface |
Abbreviated interface name. |
|
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. |
|
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces. |
|
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
|
Description |
Description of the interface. |
|
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—The tunnel bundle is not established. |
display mpls forwarding protection
Use display mpls forwarding protection to display forwarding state information for MPLS protection groups.
Syntax
In standalone mode:
display mpls forwarding protection [ tunnel-bundle number ] [ slot slot-number ]
In IRF mode:
display mpls forwarding protection [ tunnel-bundle number ] [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
tunnel-bundle number: Specifies an existing tunnel bundle interface by its number. If you do not specify this option, the command displays forwarding state information for all MPLS protection groups.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information on the active MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for the global active MPU. (In IRF mode.)
Examples
# Display forwarding state information for all MPLS protection groups.
<Sysname> display mpls forwarding protection
Total number of protection groups: 1
State:
N: Normal UA: Unavailable PA: Protecting administrative
PF: Protecting failure WTR: Wait-to-Restore DNR: Do-not-Revert
M: Manual switch F: Forced switch P: Protection tunnel failure
W: Working tunnel failure HO: Hold off LO: Lockout of protection
L: Local R: Remote
Group ID Working tunnel Protection tunnel State
2 100 200 UA:LO:R
Table 3 Command output
|
Field |
Description |
|
Group ID |
ID of the protection group. |
|
Working tunnel |
ID of the working tunnel. |
|
Protection tunnel |
ID of the protection tunnel. |
|
State |
This field contains the current protection group state, the cause, and the cause source. Current protection group state: · N—Normal state. The working and protection tunnels operate correctly, and traffic travels along the working tunnel. · UA—Unavailable state. The protection tunnel is unavailable. · PA—Protecting administrative state. The externally configured switching action enables traffic to travel along the protection tunnel. · PF—Protecting failure state. The working tunnel fails, and traffic is switched to the protection tunnel. · WTR—Wait-to-Restore state. The device is waiting for the wait time to switch traffic from the protection tunnel to the working tunnel after the working tunnel recovers. · DNR—Do-not-Revert state. Traffic is not switched from the protection tunnel to the working tunnel after the working tunnel recovers. Cause for the current protection group state: · LO—Lockout of protection. · P—A failure on the protection tunnel is detected by a signaling protocol. · W—A failure on the working tunnel is detected by a signaling protocol. · F—Forced switch. · M—Manual switch. · HO—Hold off. The device is waiting for the holdoff time to switch traffic from the working tunnel to the protection tunnel after the working tunnel fails. Cause source: · L—Local. · R—Remote. For example, UA:LO:L indicates that the protection group becomes unavailable because lockout of protection is performed on the local device. |
display mpls protection
Use display mpls protection to display state and related information for MPLS protection groups.
Syntax
display mpls protection [ tunnel-bundle number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
tunnel-bundle number: Specifies an existing tunnel bundle interface by its number. If you do not specify this option, the command displays current state and related information for all MPLS protection groups.
verbose: Displays detailed information about MPLS protection groups. If you do not specify this keyword, the command displays brief information about MPLS protection groups.
Examples
# Display current state and related information for all MPLS protection groups.
<Sysname> display mpls protection
Total number of protection groups: 1
State:
N: Normal UA: Unavailable PA: Protecting administrative
PF: Protecting failure WTR: Wait-to-Restore DNR: Do-not-Revert
M: Manual switch F: Forced switch P: Protection tunnel failure
W: Working tunnel failure HO: Hold off LO: Lockout of protection
L: Local R: Remote
Group ID Type Working tunnel Protection tunnel State
2 Tunnel bundle 100 200 UA:LO:R
Table 4 Command output
|
Field |
Description |
|
Group ID |
ID of the protection group. |
|
Type |
Tunnel type. The value can only be Tunnel bundle. |
|
Working tunnel |
ID of the working tunnel. |
|
Protection tunnel |
ID of the protection tunnel. |
|
State |
This field contains the current protection group state, the cause, and the cause source. Current protection group state: · N—Normal state. The working and protection tunnels operate correctly, and traffic travels along the working tunnel. · UA—Unavailable state. The protection tunnel is unavailable. · PA—Protecting administrative state. The externally configured switching action enables traffic to travel along the protection tunnel. · PF—Protecting failure state. The working tunnel fails, and traffic is switched to the protection tunnel. · WTR—Wait-to-Restore state. The device is waiting for the wait time to switch traffic from the protection tunnel to the working tunnel after the working tunnel recovers. · DNR—Do-not-Revert state. Traffic is not switched from the protection tunnel to the working tunnel after the working tunnel recovers. Cause for the current protection group state: · LO—Lockout of protection. · P—A failure on the protection tunnel is detected by a signaling protocol. · W—A failure on the working tunnel is detected by a signaling protocol. · F—Forced switch. · M—Manual switch. · HO—Hold off. The device is waiting for the holdoff time to switch traffic from the working tunnel to the protection tunnel after the working tunnel fails. Cause source: · L—Local. · R—Remote. For example, UA:LO:L indicates that the protection group becomes unavailable because lockout of protection is performed on the local device. |
# Display brief information about MPLS protection groups.
<Sysname> display mpls protection verbose
Protection group ID : 2
Protection group type : Tunnel bundle
Tunnel bundle name : Tunnel-Bundle200
Working tunnel : Tunnel100
Protection tunnel : Tunnel200
Protection mode : 1:1
Switching mode : Bidirectional
Tunnel in use : Working-path
Working tunnel state : No defect
Protection tunnel state : Signal fail
Holdoff time : 5s (Remaining: 3s)
Wait to restore time : 30s (Remaining: 10s)
Message interval : 5s
Revertive mode : Revertive
State : Unavailable (UA),
Protection tunnel failure (P),
Local (L)
Table 5 Command output
|
Field |
Description |
|
Protection group ID |
ID of the protection group. |
|
Protection group type |
Tunnel type. The value can only be Tunnel bundle. |
|
Tunnel bundle name |
Name of the tunnel bundle interface name for the protection group. |
|
Working tunnel |
Tunnel interface name for the working tunnel. |
|
Protection tunnel |
Tunnel interface name for the protection tunnel. |
|
Protection mode |
Protection mode: 1+1 or 1:1. |
|
Switching mode |
Switching mode: Bidirectional or Unidirectional. |
|
Tunnel in use |
Tunnel in use: Working-path or Protection-path. |
|
Working tunnel state |
Working tunnel state: · No defect. · Signal fail—A failure is detected by a signaling protocol. · OAM defect—A failure is detected by the OAM mechanism. · Remote defect—A failure is received from the remote device. |
|
Protection tunnel state |
Protection tunnel state: · No defect. · Signal fail—A failure is detected by a signaling protocol. · OAM defect—A failure is detected by the OAM mechanism. · Remote defect—A failure is received from the remote device. |
|
Holdoff time |
Holdoff time and the remaining holdoff time in seconds. |
|
Wait to restore time |
Wait time for the switchover from the protection tunnel to the working tunnel, and the remaining wait time, in seconds. |
|
Message interval |
PSC message sending interval in seconds. |
|
Revertive mode |
Revertive mode: Revertive or Non-revertive. |
|
State |
This field contains the current protection group state, the cause, and the cause source. Current protection group state: · Normal (N)—The working and protection tunnels operate correctly, and traffic travels along the working tunnel. · Unavailable (UA)—The protection tunnel is unavailable. · Protecting administrative (PA)—The externally configured switching action enables traffic to travel along the protection tunnel. · Protecting failure (PF)—The working tunnel fails, and traffic is switched to the protection tunnel. · Wait-to-Restore (WTR)—The device is waiting for the wait time to switch traffic from the protection tunnel to the working tunnel after the working tunnel recovers. · Do-not-Revert (DNR)—Traffic is not switched from the protection tunnel to the working tunnel after the working tunnel recovers. Cause for the current protection group state: · Lockout of protection (LO). · Protection tunnel failure (P)—A failure on the protection tunnel is detected by a signaling protocol. · Working tunnel failure (W)—A failure on the working tunnel is detected by a signaling protocol. · Forced switch (F). · Manual switch (M). · Hold off (HO)—The device is waiting for the holdoff time to switch traffic from the working tunnel to the protection tunnel after the working tunnel fails. Cause source, Local (L) or Remote (R). For example, UA:LO:L indicates that the protection group becomes unavailable because lockout of protection is performed on the local device. |
display tunnel-bundle
Use display tunnel-bundle to display information about tunnel bundle interfaces and their member interfaces.
Syntax
display tunnel-bundle [ number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
number: Specifies an existing tunnel bundle interface and its member interfaces by the tunnel bundle interface number. If you do not specify this argument, the command displays information about all tunnel bundle interfaces and their member interfaces.
Examples
# Display information about all tunnel bundle interfaces and their member interfaces.
<Sysname> display tunnel-bundle
Total number of tunnel bundles: 1, 1 up, 0 down
Tunnel bundle name: Tunnel-Bundle 2
Bundle state : Up
Bundle attributes :
Working mode : 1:1
Tunnel type : CR-LSP
Tunnel destination : 3.3.3.3
Bundle members:
Member State Role
Tunnel4 Up Working
Tunnel5 Up Protection
Table 6 Command output
|
Field |
Description |
|
Total number of tunnel bundles |
Total number of tunnel bundle interfaces in up and down states. |
|
Working mode |
Tunnel bundle interface operating mode: · Load Balancing. · 1+1—1+1 protection switching mode. · 1:1—1:1 protection switching mode. For more information about 1+1 and 1:1 protection switching modes, see MPLS Configuration Guide. |
|
Tunnel type |
The tunnel type can only be CRLSP. |
|
Tunnel destination |
Tunnel destination address of the tunnel bundle interface. |
|
Role |
Role of a member interface: · Working—The tunnel for the member interface is the working tunnel. · Protection—The tunnel for the member interface is the protection tunnel. |
interface tunnel-bundle protection
Use interface tunnel-bundle protection to create a tunnel bundle interface in protection switching mode and enter its view, or enter the view of an existing tunnel bundle interface.
Use undo interface tunnel-bundle to delete a tunnel bundle interface.
Syntax
interface tunnel-bundle number [ protection { oneplusone | onetoone } ]
undo interface tunnel-bundle number
Default
No tunnel bundle interfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
number: Specifies the tunnel bundle interface number. The value range for this argument is 0 to 10239.
protection { oneplusone | onetoone }: Specifies a protection switching mode. To create a tunnel bundle interface, you must specify the protection switching mode. To enter the view of an existing tunnel bundle interface, you do not need to specify the protection switching mode.
· oneplusone: Specifies the 1+1 protection switching mode.
· onetoone: Specifies the 1:1 protection switching mode.
Usage guidelines
After you create a tunnel bundle interface in protection switching mode, you must specify a working tunnel and a protection tunnel for the tunnel bundle interface. The two tunnels comprise an MPLS TE tunnel bundle, which is an MPLS TE protection group. In the group, the device determines the tunnel for traffic forwarding according to the external switching command and the signal fail indication. For information about specifying the working tunnel and protection tunnel, see the member interface command.
The device supports the following protection switching modes:
· 1:1 protection switching—Typically, traffic travels along the working tunnel. When either of the following situations occurs, the ingress node selects the traffic forwarding tunnel (working or protection tunnel) according to the protection state:
¡ The ingress or the egress node detects a failure on the working tunnel.
¡ An external switching command is executed on the node.
· 1+1 protection switching—Typically, traffic travels along both the working and protection tunnels, and the egress node receives traffic from the working tunnel. When either of the following situations occurs, the egress node determines from which tunnel it receives traffic according to the protection state:
¡ The ingress or egress node detects a failure on the working tunnel.
¡ An external switching command is executed on the node.
|
|
NOTE: · The tunnel ingress or egress node can detect tunnel failures through BFD for MPLS or other detection mechanisms. For more information about BFD for MPLS, see MPLS Configuration Guide. · The protection state indicates the comprehensive status of a PS protection group. For more information, see the display mpls forwarding protection command. |
To modify the protection switching mode for a tunnel bundle interface, execute the undo interface tunnel-bundle command to delete the interface and then execute the interface tunnel-bundle protection command.
Examples
# Create tunnel bundle interface Tunnel-Bundle 2 in 1:1 protection switching mode, and enter the tunnel bundle interface view.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2 protection onetoone
[Sysname-tunnel-bundle2]
Related commands
destination
display tunnel bundle
member interface
mpls protection
member interface
Use member interface to specify a member interface for a tunnel bundle interface.
Use undo member interface to delete a member interface from a tunnel bundle interface.
Syntax
member interface tunnel tunnel-number [ protection ]
undo member interface tunnel tunnel-number
Default
No member interfaces exist for a tunnel bundle interface.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
tunnel tunnel-number: Specifies a member interface by the interface number. You must specify an existing tunnel interface number.
protection: Specifies a member interface as the backup member interface. If you do not specify this keyword, the specified member interface is the primary member interface. The tunnel for the primary member interface is the working tunnel, and the tunnel for the backup member interface is the protection tunnel.
Usage guidelines
You can specify only one primary member interface and one backup member interface for a tunnel bundle interface in protection switching mode. The device selects a member interface for traffic forwarding according to the external switching command and the signal fail indication.
Examples
# Specify Tunnel 1 as the primary member interface, and Tunnel 2 as the backup member interface for Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2 protection onetoone
[Sysname-tunnel-bundle2] member interface tunnel 1
[Sysname-tunnel-bundle2] member interface tunnel 2 protection
Related commands
display mpls protection
display tunnel-bundle
mpls protection
Use mpls protection to enable MPLS protection switching and enter MPLS protection switching view.
Use undo mpls protection to disable MPLS protection switching.
Syntax
mpls protection
undo mpls protection
Default
MPLS protection switching is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Enable MPLS protection switching by using the mpls protection command before you execute other MPLS protection switching commands.
When MPLS protection switching is disabled, the display mpls protection command does not display the protection group information for a tunnel bundle interface. However, the tunnel bundle interface can forward traffic according to the specified protection switching mode (1:1 or 1+1).
After MPLS protection switching is enabled, you can configure the tunnel bundle interface for PS as needed, for example, configuring an external switching command and configuring PS state coordination.
Examples
# Enable MPLS protection switching and enter MPLS protection switching view.
<Sysname> system-view
[Sysname] mpls protection
[Sysname-mpls-protection]
protection holdoff
Use protection holdoff to set the holdoff time when a working tunnel failure is detected.
Use undo protection holdoff to restore the default.
Syntax
protection holdoff holdoff-time
undo protection holdoff
Default
The holdoff time is 0 seconds. When the working tunnel fails, traffic is immediately switched from the working tunnel to the protection tunnel.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
holdoff-time: Specifies the holdoff time in the range of 0 to 10 seconds.
Usage guidelines
When the working tunnel fails, the tunnel bundle interface waits for the holdoff time to switch traffic from the working tunnel to the protection tunnel.
To avoid repeated switches on unstable networks, traffic is not switched from the working tunnel to the protection tunnel if the working tunnel recovers within the holdoff time.
You can execute this command only after MPLS protection switching is enabled by using the mpls protection command.
Examples
# Set the holdoff time to 3 seconds for Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2 protection onetoone
[Sysname-tunnel-bundle2] protection holdoff 3
Related commands
mpls protection
protection revertive
Use protection revertive to specify the switchover mode and set the switchover wait time.
Use undo protection revertive to restore the default.
Syntax
protection revertive { never | wtr [ wtr-time ] }
undo protection revertive
Default
When the working tunnel recovers, traffic is immediately switched from the protection tunnel to the working tunnel.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
never: Specifies the switchover mode as non-revertive. After the working tunnel recovers, the protection group continues to use the protection tunnel as long as the protection group is operating correctly.
wtr: Specifies the switchover mode as revertive. In revertive mode, traffic is switched from the protection tunnel to the working tunnel when the working tunnel recovers.
wtr-time: Specifies the wait time in the range of 0 to 3600 seconds. The default value is 600 seconds. When the working tunnel recovers, the wait timer starts. If the working tunnel is still operating correctly when the wait timer expires, traffic is switched from the protection tunnel to the working tunnel.
Usage guidelines
Typically, traffic preferentially uses the working tunnel when both the working and protection tunnels are operating correctly. When the working tunnel recovers, traffic should be immediately switched from the protection tunnel to the working tunnel. However, on an unstable network, the immediate switchover might affect traffic forwarding and burden the device. To resolve the problem, use this command to specify the switchover mode and the wait time for the switchover.
Both ends of a tunnel must have the same switchover mode (revertive or non-revertive) and wait time.
You can execute this command only after MPLS protection switching is enabled by using the mpls protection command.
Examples
# Specify the revertive mode for Tunnel-Bundle 2, and set the wait time to 10 seconds.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2 protection onetoone
[Sysname-tunnel-bundle2] protection revertive wtr 10
Related commands
mpls protection
protection switching-mode bidirectional
protection switch
Use protection switch to execute an external command for protection switching on a tunnel bundle interface.
Syntax
protection switch { clear | force | lock | manual }
Default
No external command is configured.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
clear: Specifies the Clear command. This command clears the active external command.
force: Specifies the Forced Switch command. This command forces traffic to travel on the protection tunnel.
lock: Specifies the Lockout of Protection command. This command locks protection switching. Traffic is always forwarded by the working tunnel.
manual: Specifies the Manual Switch command. This command switches traffic from the working tunnel to the protection tunnel. If the protection tunnel is not available, traffic switching is not performed.
Usage guidelines
The following shows the protection switching triggers in the descending order of priority:
· Clear.
· Lockout of protection.
· Forced switch.
· Signal fail on the protection tunnel—The signaling protocol detected a failure on the protection tunnel.
· Signal fail on the working tunnel—The signaling protocol detected a failure on the working tunnel.
· Clear signal fail—The signaling protocol detected that the working or protection tunnel has recovered.
· Manual switch.
If multiple triggers exist, the one with the highest priority determines the tunnel for traffic forwarding.
Before configuring this command, you must enable MPLS protection switching by using the mpls protection command.
If you execute this command multiple times to specify multiple external commands, the external command with higher priority overwrites the one with lower priority. To change an external command to one with lower priority, first execute the clear command to clear the active external command.
Examples
# On Tunnel-Bundle 2, force traffic to travel on the protection tunnel.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2 protection oneplusone
[Sysname-tunnel-bundle2] protection switch force
Related commands
mpls protection
protection switching-mode bidirectional
Use protection switching-mode bidirectional to configure a protection group to use bidirectional switching.
Use undo protection switching-mode bidirectional to restore the default.
Syntax
protection switching-mode bidirectional
undo protection switching-mode bidirectional
Default
A protection group uses unidirectional switching.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Usage guidelines
A bidirectional MPLS TE tunnel switches the traffic forwarding path in one of the following modes:
· Unidirectional switching—When an external command or a signal fail indication triggers protection switching for traffic in one direction, PS switches the traffic forwarding tunnel only in this direction. The traffic forwarding tunnel in the other direction does not change.
· Bidirectional switching—When an external command or a signal fail indication triggers protection switching for traffic in one direction, PS switches the traffic forwarding tunnels in both directions.
To implement bidirectional switching, the ingress node and the egress node periodically send Protection State Coordination (PSC) packets to each other to coordinate the protection state. When one tunnel end performs a PS, the other end also performs a PS.
Bidirectional path switching requires that the working and protection tunnels are both bidirectional tunnels. For bidirectional path switching to function correctly, you must configure bidirectional path switching on both ends of the working tunnel.
1:1 protection switching supports both unidirectional and bidirectional switching. 1+1 protection switching supports only bidirectional switching.
Before configuring this command, you must enable MPLS protection switching by using the mpls protection command.
Examples
# Configure the protection group for Tunnel-Bundle 2 to use the bidirectional switching mode.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2 protection onetoone
[Sysname-tunnel-bundle2] protection switching-mode bidirectional
Related commands
mpls protection
protection holdoff
psc message-interval
psc message-interval
Use psc message-interval to set the interval for sending PSC messages.
Use undo psc message-interval to restore the default.
Syntax
psc message-interval interval
undo psc message-interval
Default
The PSC message sending interval is 5 seconds.
Views
MPLS protection switching view
Predefined user roles
network-admin
Parameters
interval: Specifies the PSC message sending interval in the range of 1 to 65535 seconds.
Usage guidelines
The two ends of a tunnel periodically send PSC messages to coordinate the protection state for bidirectional path switching.
You can prevent PSC messages from occupying too many system and bandwidth resources by modifying the sending interval as needed.
You can execute this command only after MPLS protection switching is enabled by using the mpls protection command.
Examples
# Set the PSC message sending interval to 10 seconds.
<Sysname> system-view
[Sysname] mpls protection
[sys-mpls-protection] psc message-interval 10
Related commands
mpls protection
protection switching-mode bidirectional
reset counters interface tunnel-bundle
Use reset counters interface tunnel-bundle to clear tunnel bundle interface statistics.
Syntax
reset counters interface [ tunnel-bundle [ number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
tunnel-bundle [ number ]: Specifies a tunnel bundle interface. The number argument specifies the tunnel bundle interface number. The specified tunnel bundle interface number must have existed.If you do not specify the tunnel-bundle keyword, this command clears statistics for all interfaces on the device. If you specify the tunnel-bundle keyword without the number argument, this command clears statistics for all tunnel bundle interfaces.
Usage guidelines
Use this command to clear old statistics so you can observe new traffic statistics on a tunnel bundle interface.
Examples
# Clear statistics for Tunnel-Bundle 2.
<Sysname> reset counters tunnel-bundle 2
Related commands
display interface tunnel-bundle
interface tunnel-bundle
service
Use service to specify a traffic forwarding slot for a tunnel bundle interface.
Use undo service to restore the default.
Syntax
In standalone mode:
service slot slot-number
undo service slot
In IRF mode:
service chassis chassis-number slot slot-number
undo service chassis
Default
No traffic forwarding slot is specified for a tunnel bundle interface. Traffic on a tunnel bundle interface is forwarded by the slot at which the traffic arrives.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Usage guidelines
Specify a traffic processing slot if all traffic on a tunnel bundle interface is required to be processed on the same slot.
For high availability, you can specify one primary and one backup traffic processing slot by using the service command and the service standby command, respectively.
To avoid processing slot switchover, specify the primary slot before specifying the backup slot. If you specify the backup slot before specifying the primary slot, traffic is switched over to the primary slot immediately after you specify the primary slot.
If you specify both primary and backup slots for an interface, traffic on that interface is processed as follows:
· The backup slot takes over when the primary slot becomes unavailable. The backup slot continues to process traffic for the interface after the primary slot becomes available again. A switchover will not occur until the backup slot becomes unavailable.
· When no specified traffic processing slots are available, the traffic is processed on the slot at which it arrives. Then, the processing slot that first becomes available again takes over.
If you do not specify a primary or a backup traffic processing slot for an interface, traffic on that interface is processed on the slot at which the traffic arrives.
Examples
# Specify a traffic forwarding slot for Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2
[Sysname-tunnel-bundle2] service slot 2
service standby
Use service standby to specify a backup traffic processing slot for an interface.
Use undo service standby to restore the default.
Syntax
In standalone mode:
service standby slot slot-number
undo service standby slot
In IRF mode:
service standby chassis chassis-number slot slot-number
undo service standby chassis
Default
No backup traffic processing slot is specified for an interface.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Usage guidelines
Specify a traffic processing slot if all traffic on a tunnel bundle interface is required to be processed on the same slot.
For high availability, you can specify one primary and one backup traffic processing slot by using the service command and the service standby command, respectively.
To avoid processing slot switchover, specify the primary slot before specifying the backup slot. If you specify the backup slot before specifying the primary slot, traffic is switched over to the primary slot immediately after you specify the primary slot.
If you specify both primary and backup slots for an interface, traffic on that interface is processed as follows:
· The backup slot takes over when the primary slot becomes unavailable. The backup slot continues to process traffic for the interface after the primary slot becomes available again. A switchover will not occur until the backup slot becomes unavailable.
· When no specified traffic processing slots are available, the traffic is processed on the slot at which it arrives. Then, the processing slot that first becomes available again takes over.
If you do not specify a primary or a backup traffic processing slot for an interface, traffic on that interface is processed on the slot at which the traffic arrives.
Examples
# Specify a primary traffic forwarding slot and a backup traffic forwarding slot for Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2
[Sysname-tunnel-bundle2] service slot 1
[Sysname-tunnel-bundle2] service standby slot 2
Related commands
service
shutdown
Use shutdown to shut down a tunnel bundle interface and its member interfaces.
Use undo shutdown to bring up a tunnel bundle interface.
Syntax
shutdown
undo shutdown
Default
An interface is up.
Views
Tunnel bundle interface view
Predefined user roles
network-admin
Examples
# Shut down Tunnel-Bundle 2.
<Sysname> system-view
[Sysname] interface tunnel-bundle 2
[Sysname-tunnel-bundle2] shutdown
