Login
- Table of Contents
-
- 07-Layer 3—IP Services Command Reference
- 00-Preface
- 01-ARP commands
- 02-IP addressing commands
- 03-DHCP commands
- 04-DNS commands
- 05-NAT commands
- 06-IP forwarding basics commands
- 07-Fast forwarding commands
- 08-Multi-CPU packet distribution commands
- 09-Adjacency table commands
- 10-IRDP commands
- 11-IP performance optimization commands
- 12-UDP helper commands
- 13-IPv6 basics commands
- 14-DHCPv6 commands
- 15-IPv6 fast forwarding commands
- 16-Tunneling commands
- 17-GRE commands
- 18-ADVPN commands
- 19-WAAS commands
- 20-AFT commands
- 21-Lighttpd service commands
- 22-Web caching commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 16-Tunneling commands | 167.08 KB |
display ds-lite b4 information
reset counters interface tunnel
tunnel discard ipv4-compatible-packet
Tunneling 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 (in kbps) is the interface maximum rate divided by 1000.
Views
Tunnel 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 link costs in OSPF, OSPFv3, and IS-IS. For more information, see Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth for Tunnel 1 to 100 kbps.
<Sysname> system-view
[Sysname] interface tunnel 1
[Sysname-Tunnel1] bandwidth 100
default
Use default to restore the default settings for a tunnel interface.
Syntax
default
Views
Tunnel 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 1.
<Sysname> system-view
[Sysname] interface tunnel 1
[Sysname-Tunnel1] 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 interface is Tunnelnumber Interface, for example, Tunnel1 Interface.
Views
Tunnel 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 different interfaces for identification and management purposes.
You can use the display interface command to display the configured interface description.
Examples
# Configure the description of Tunnel 1 as tunnel1.
<Sysname> system-view
[Sysname] interface tunnel 1
[Sysname-Tunnel1] description tunnel1
display interface tunnel
destination
Use destination to specify the destination address for a tunnel interface.
Use undo destination to restore the default.
Syntax
destination { ipv4-address | ipv6-address | dhcp-alloc interface-type interface-number }
undo destination
Default
No tunnel destination address is configured.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies the tunnel destination IPv4 address.
ipv6-address: Specifies the tunnel destination IPv6 address.
dhcp-alloc interface-type interface-number: Specifies an interface by its type and number to obtain AFTR's IPv6 address from DHCPv6 packets.
Usage guidelines
For a manual tunnel interface, you must configure the destination address. For an automatic tunnel interface, you do not need to configure the destination address.
The tunnel destination address must be the address of the receiving interface on the tunnel peer. It is used as the destination address of tunneled packets.
The destination address of the local tunnel interface must be the source address of the peer tunnel interface. The source address of the local tunnel interface must be the destination address of the peer tunnel interface.
Do not specify the same tunnel source and destination addresses for the tunnel interfaces on the same device.
For a B4 router to automatically establish a DS-Lite tunnel with an AFTR, configure DHCPv6 client, IPv6 DNS client, and the destination dhcp-alloc command on the B4 router. In addition, make sure a DHCPv6 server and an IPv6 DNS server (for dynamic DNS) exist in the network.
After receiving a DHCPv6 packet from the interface specified by the destination dhcp-alloc command, the B4 router performs the following operations:
1. Obtains the domain name of the AFTR from the packet.
2. Sends a name query to the IPv6 DNS server to obtain the AFTR's IPv6 address.
The server resolves the domain name to the IPv6 address of AFTR.
For more information about DHCPv6 server, DHCPv6 client, and IPv6 DNS, see Layer 3—IP Services Configuration Guide.
Examples
# The interface GigabitEthernet 1/0/1 on Sysname 1 uses the IP address 193.101.1.1 and the interface GigabitEthernet 1/0/1 on Sysname 2 uses the IP address 192.100.1.1. Configure the source address 193.101.1.1 and destination address 192.100.1.1 for the tunnel interface on Sysname 1.
<Sysname1> system-view
[Sysname1] interface tunnel 1 mode gre
[Sysname1-Tunnel1] source 193.101.1.1
[Sysname1-Tunnel1] destination 192.100.1.1
# Configure the source address 192.100.1.1 and destination address 193.101.1.1 for the tunnel interface on Sysname 2.
<Sysname2> system-view
[Sysname2] interface tunnel 1 mode gre
[Sysname2-Tunnel1] source 192.100.1.1
[Sysname2-Tunnel1] destination 193.101.1.1
display interface tunnel
interface tunnel
ipv6 address dhcp-alloc
source
display 6rd
Use display 6rd to display 6RD tunnel interface information.
Syntax
display 6rd [ interface tunnel number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface tunnel number: Specifies an existing tunnel interface by its number. If you do not specify a 6RD tunnel interface, this command displays information about all existing 6RD tunnel interfaces.
Examples
# Display information about 6RD tunnel interface Tunnel 1.
<Sysname> display 6rd interface tunnel 1
Interface : Tunnel1
Tunnel source : 10.11.12.13
6RD status : Operational
IPv6 prefix : 2001:1000::/32
IPv4 prefix : 10.0.0.0/8
IPv4 suffix : 0.0.0.0/0
BR address : 10.11.12.1
Delegated prefix: 2001:1000:B0C:D00::/56
# Display information about all 6RD tunnel interfaces.
<Sysname> display 6rd
Interface : Tunnel0
Tunnel source : 0.0.0.0
6RD status : Not operational
IPv6 prefix : 2002:1000::/32
Interface : Tunnel1
Tunnel source : 10.11.12.13
6RD status : Operational
IPv6 prefix : 2001:1000::/32
IPv4 prefix : 10.0.0.0/8
IPv4 suffix : 0.0.0.0/0
BR address : 10.11.12.1
Delegated prefix: 2001:1000:B0C:D00::/56
Table 1 Command output
|
Field |
Description |
|
Interface |
Tunnel interface. |
|
Tunnel source |
Source address of the tunnel. If a source interface is specified for the tunnel interface, this field displays the IP address of the source interface. If no source address or source interface is specified for the tunnel interface, or the specified source interface has no IP address, this field displays 0.0.0.0. |
|
6RD status |
6RD configuration status: · Operational—6RD configuration is available. · Not operational—6RD configuration is not available. This field displays Operational when the tunnel source address and 6RD prefix are configured. |
|
IPv6 prefix |
6RD prefix and its length. If no 6RD prefix is configured, this field displays Not configured. |
|
IPv4 prefix |
IPv4 prefix and its length. If the prefix length is not configured, this field displays 0.0.0.0/0. |
|
IPv4 suffix |
IPv4 suffix and its length. If the suffix length is not configured, this field displays 0.0.0.0/0. |
|
BR address |
IP address of the BR router. If no BR address is configured, this field displays Not configured. |
|
Delegated prefix |
6RD delegated prefix calculated based on the 6RD configuration. This field is empty if the 6RD status is Not operational. |
Related commands
tunnel 6rd br
tunnel 6rd ipv4
tunnel 6rd prefix
display 6rd destination
Use display 6rd destination to display a 6RD tunnel destination address.
Syntax
display 6rd destination prefix ipv6-prefix interface tunnel number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
prefix ipv6-prefix: Specifies a 6RD delegated prefix.
interface tunnel number: Specifies an existing tunnel interface by its number.
Usage guidelines
After this command is executed, the system displays the 6RD tunnel destination address calculated by the specified 6RD delegated prefix and 6RD configuration on the tunnel interface. The 6RD configuration includes the 6RD prefix/prefix length, IPv4 prefix/prefix length, and IPv4 suffix/suffix length.
Examples
# Display the 6RD tunnel destination address calculated by the 6RD delegated prefix 2001:1000:0101:0100:: and 6RD configuration on Tunnel 1.
<Sysname> display 6rd destination prefix 2001:1000:0101:0100:: interface tunnel 1
Interface : Tunnel1
Delegated prefix: 2001:1000:101:100::
Destination : 10.1.1.1
Table 2 Command output
|
Field |
Description |
|
Interface |
Tunnel interface. |
|
Delegated prefix |
6RD delegated prefix. |
|
Destination |
Tunnel destination address. |
Related commands
display 6rd prefix
display 6rd prefix
Use display 6rd prefix to display a 6RD delegated prefix.
Syntax
display 6rd prefix destination ipv4-address interface tunnel number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
destination ipv4-address: Specifies a 6RD tunnel destination address.
interface tunnel number: Specifies an existing tunnel interface by its number.
Usage guidelines
After this command is executed, the system displays the 6RD delegated prefix calculated by the specified 6RD tunnel destination address and 6RD configuration on the tunnel interface. The 6RD configuration includes the 6RD prefix/prefix length, IPv4 prefix/prefix length, and IPv4 suffix/suffix length. The 6RD delegated prefix calculated on the peer tunnel interface must be the same as the 6RD delegated prefix configured on the local device.
Examples
# Display the 6RD delegated prefix calculated by the 6RD tunnel destination address 10.1.1.1 and 6RD configuration on Tunnel 1.
<Sysname> display 6rd prefix destination 10.1.1.1 interface tunnel 1
Interface : Tunnel1
Destination : 10.1.1.1
Delegated Prefix: 2001:1000:101:100::
Table 3 Command output
|
Field |
Description |
|
Interface |
Tunnel interface. |
|
Destination |
6RD tunnel destination address. |
|
Delegated Prefix |
6RD delegated prefix. |
Related commands
display 6rd destination
display ds-lite b4 information
Use display ds-lite b4 information to display information about the connected B4 routers on the AFTR, including the IPv6 addresses of the B4 routers, and the assigned tunnel IDs.
Syntax
display ds-lite b4 information
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# (In standalone mode.) Display information about the connected B4 routers.
<Sysname> display ds-lite b4 information
B4 address Tunnel ID Tunnel interface Idle time
1234:5678:1234:5678:abcd:abcd:efff:1234 0x00000023 1 12
2000::100:1 0x80000013 2 13
3000::2 0x00000015 3 8
3001::2 0x00000032 -- 15
Total B4 addresses: 4
# (In IRF mode.) Display information about the connected B4 routers.
<Sysname> display ds-lite b4 information
Slot 0 Cpu 0:
B4 address Tunnel ID Tunnel interface Idle time
1234:5678:1234:5678:abcd:abcd:efff:1234 0x00000023 1 12
2000::100:1 0x80000013 2 13
3000::2 0x00000015 3 2
3001::2 0x00000032 -- --
Total B4 addresses: 4
Slot 1 Cpu 0:
B4 address Tunnel ID Tunnel interface Idle time
1234:5678:1234:5678:abcd:abcd:efff:ffff 0x00000125 1 12
5000::100:1 0x80000010 5 13
Total B4 addresses: 2
Table 4 Command output
|
Field |
Description |
|
B4 address |
IPv6 address of the B4 router. |
|
Tunnel ID |
Tunnel ID that the IPv6 address of the B4 router maps to. |
|
Tunnel interface |
ID of the tunnel interface on the DS-Lite tunnel to which the mapping belongs. When the tunnel to which the mapping belongs is removed or a tunnel with the same ID but different mode is created, this field displays hyphens (--). |
|
Idle time |
Remaining time in minutes for the mapping between the IPv6 address of the B4 router and tunnel ID. When the mapping ages out but is still used by a session, this field displays hyphens (--). |
|
Total B4 addresses |
Number of IPv6 addresses of the B4 routers. |
display interface tunnel
Use display interface tunnel to display tunnel interface information.
Syntax
display interface [ tunnel [ number ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
tunnel [ number ]: Specifies a tunnel interface. The number argument specifies the tunnel interface number. The specified tunnel interface must have been created. If you do not specify the tunnel keyword, this command displays information about all interfaces except VA interfaces on the device. For information about VA interfaces, see PPPoE in Layer 2—WAN Access Configuration Guide. If you specify the tunnel keyword without the number argument, this command displays information about all existing tunnel interfaces.
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 1.
<Sysname> display interface tunnel 1
Current state: UP
Line protocol state: UP
Description: Tunnel1 Interface
Bandwidth: 64kbps
Maximum transmission unit: 1476
Internet address: 10.1.2.1/24 (primary)
Tunnel source 2002::1:1 (Vlan-interface10), destination 2001::2:1
Tunnel TOS 0xC8, Tunnel TTL 255
Tunnel protocol/transport GRE/IPv6
GRE key disabled
Checksumming of GRE packets disabled
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
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 5 Command output
|
Field |
Description |
|
Tunnel1 |
Information about the tunnel interface Tunnel 1. |
|
Current state |
Physical link state of the tunnel 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 (possibly because no physical link exists or the link has failed). · DOWN (Tunnel-Bundle administratively down)—The tunnel bundle interface to which the interface belongs has been shut down by using the shutdown command. · UP—The interface is both administratively and physically up. |
|
Line protocol state |
Data link layer state of the 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 interface. |
|
Bandwidth |
Expected bandwidth of the tunnel interface. |
|
Maximum transmission unit |
MTU of the tunnel interface. |
|
Internet protocol processing: Disabled |
The tunnel interface is not assigned an IP address and cannot process IP packets. |
|
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. |
|
Tunnel source |
Source address of the tunnel. If a source interface is specified for the tunnel interface, this field also displays the source interface in parentheses. |
|
destination |
Destination address of the tunnel. |
|
Tunnel keepalive enabled, Period(50 s), Retries(3) |
GRE keepalive is enabled. In this example, the keepalive interval is 50 seconds and the keepalive number is 3. |
|
Tunnel TOS |
ToS of tunneled packets. |
|
Tunnel TTL |
TTL of tunneled packets. |
|
Tunnel protocol/transport |
Tunnel mode and transport protocol: · CR_LSP—MPLS TE tunnel mode. · GRE/IP—GRE/IPv4 tunnel mode. · GRE/IPv6—GRE/IPv6 tunnel mode. · GRE P2MP—GRE/IPv4 P2MP tunnel mode. · GRE P2MP/IPv6—GRE/IPv6 P2MP tunnel mode. · GRE_ADVPN/IP—GRE-encapsulated IPv4 ADVPN tunnel mode. · GRE_ADVPN/IPv6—GRE-encapsulated IPv6 ADVPN tunnel mode. · UDP_ADVPN/IP—UDP-encapsulated IPv4 ADVPN tunnel mode. · UDP_ADVPN/IPv6—UDP-encapsulated IPv6 ADVPN tunnel mode. · IP/IP—IPv4 over IPv4 tunnel mode. · IP/IPv6—IPv4 over IPv6 tunnel mode. · IPv6—IPv6 tunnel mode. · IPv6/IP—IPv6 over IPv4 manual tunnel mode. · IPv6/IP 6to4—IPv6 over IPv4 6to4 tunnel mode. · IPv6/IP auto-tunnel—Automatic IPv6 over IPv4 tunnel mode. · IPv6/IP ISATAP—IPv6 over IPv4 ISATAP tunnel mode. · IPv6/IPv6—IPv6 over IPv6 tunnel mode. · DSLITE—DS-Lite tunnel mode on the AFTR. · UDP_VXLAN/IP—UDP-encapsulated IPv4 VXLAN tunnel mode. · NVE/IP—IPv4 NVE tunnel mode. |
|
GRE key disabled |
No GRE tunnel interface key is configured. |
|
Checksumming of GRE packets disabled |
The GRE packet checksum feature is disabled. |
|
Source port number is 18001 |
The source port number is 18001 in ADVPN packets sent by the UDP-encapsulated ADVPN tunnel interface. |
|
Output queue - Urgent queuing: Size/Length/Discards 0/100/0 |
Urgent output queue statistics: |
|
Output queue - Protocol queuing: Size/Length/Discards 0/500/0 |
Protocol output queue statistics: |
|
Output queue - FIFO queuing: Size/Length/Discards 0/75/0 |
FIFO output queue statistics: When a CBQ or WFQ queue is configured, this field displays statistics for the CBQ or WFQ queue. |
|
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. |
|
Input: 0 packets, 0 bytes, 0 drops |
Total input packets, total input bytes, and total input packets dropped. |
|
Output: 0 packets, 0 bytes, 0 drops |
Total output packets, total output bytes, and total output packets dropped. |
# Display brief information about Tunnel 1.
<Sysname> display interface tunnel 1 brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Tun1 UP UP 1.1.1.1 Tunnel1
# Display brief information about Tunnel 1, including the complete interface description.
<Sysname> display interface tunnel 1 brief description
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
Tun1 UP UP 1.1.1.1 Tunnel1
# Display information about interfaces in DOWN state and the causes.
<Sysname> display interface tunnel brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
Tun0 DOWN Not connected
Tun1 DOWN Not connected
Table 6 Command output
|
Field |
Description |
|
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. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state 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 is not established. · DOWN (Tunnel-Bundle administratively down)—The tunnel bundle interface to which the tunnel interface belongs has been shut down by using the shutdown command. |
Related commands
destination
interface tunnel
source
ds-lite enable
Use ds-lite enable to enable DS-Lite tunneling on an interface.
Use undo ds-lite enable to disable DS-Lite tunneling on an interface.
Syntax
ds-lite enable
undo ds-lite enable
Default
DS-Lite tunneling is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
Use this command on the AFTR's interface connected to the public IPv4 network, so the AFTR can forward IPv4 packets to the B4 router through the DS-Lite tunnel.
You cannot enable DS-Lite tunneling on a DS-Lite tunnel interface on the AFTR.
Examples
# Enable DS-Lite tunneling on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ds-lite enable
encapsulation-limit
Use encapsulation-limit to set the maximum number of nested encapsulations of a packet allowed on a tunnel interface.
Use undo encapsulation-limit to restore the default.
Syntax
encapsulation-limit number
undo encapsulation-limit
Default
There is no limit to the nested encapsulations of a packet.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
number: Specifies the number of nested encapsulations, in the range of 0 to 10.
Usage guidelines
A packet added with excessive headers becomes oversized. If it exceeds the MTU, it must be fragmented. The fragmentation decreases forwarding rate and increases processing complexity. To avoid this situation, use this command to limit the number of encapsulations.
This command is applicable only to IPv6 over IPv6 tunnels.
Examples
# Set the maximum number of nested encapsulations to 3 on Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode ipv6
[Sysname-Tunnel1] encapsulation-limit 3
Related commands
display interface tunnel
interface tunnel
Use interface tunnel to create a tunnel interface, specify the tunnel mode, and enter tunnel interface view, or enter the view of an existing tunnel interface.
Use undo interface tunnel to delete a tunnel interface.
Syntax
interface tunnel number [ mode { advpn { gre | udp } [ ipv6 ] | ds-lite-aftr | gre [ ipv6 ] | gre-p2mp [ ipv6 ] | ipsec [ ipv6 ] | ipv4-ipv4 | ipv6 | ipv6-ipv4 [ 6rd | 6to4 | auto-tunnel | isatap ] | mgre | mpls-te | nve | vxlan } ]
undo interface tunnel number
Default
No tunnel interfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
number: Specifies the number of the tunnel interface. The number of tunnel interfaces that can be created is restricted by the total number of interfaces and the memory.
The following compatibility matrix shows the value ranges for the tunnel interface number:
|
Hardware |
Value range |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
0 to 10239 |
|
MSR810-LMS, MSR810-LUS |
0 to 1023 |
|
MSR2600-6-X1, MSR2600-10-X1 |
0 to 10239 |
|
MSR 2630 |
0 to 10239 |
|
MSR3600-28, MSR3600-51 |
0 to 10239 |
|
MSR3600-28-SI, MSR3600-51-SI |
0 to 10239 |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
0 to 10239 |
|
MSR3610-I-DP, MSR3610-IE-DP |
0 to 10239 |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
0 to 10239 |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
0 to 10239 |
|
MSR3610-G, MSR3620-G |
0 to 10239 |
mode advpn gre: Specifies the GRE-encapsulated IPv4 ADVPN tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode advpn udp: Specifies the UDP-encapsulated IPv4 ADVPN tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode advpn gre ipv6: Specifies the GRE-encapsulated IPv6 ADVPN tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode advpn udp ipv6: Specifies the UDP-encapsulated IPv6 ADVPN tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode ds-lite-aftr: Specifies the DS-Lite tunnel mode on the AFTR.
mode gre: Specifies the GRE/IPv4 tunnel mode.
mode gre ipv6: Specifies the GRE/IPv6 tunnel mode.
mode gre-p2mp: Specifies the GRE/IPv4 P2MP tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode gre-p2mp ipv6: Specifies the GRE/IPv6 P2MP tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode ipsec: Specifies the IPsec/IPv4 tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode ipsec ipv6: Specifies the IPsec/IPv6 tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode ipv4-ipv4: Specifies the IPv4 over IPv4 tunnel mode.
mode ipv6: Specifies the IPv6 tunnel mode. Set this mode for IPv4 over IPv6 manual and IPv6 over IPv6 tunnels.
mode ipv6-ipv4: Specifies the IPv6 over IPv4 manual tunnel mode.
mode ipv6-ipv4 6rd: Specifies the 6RD tunnel mode.
mode ipv6-ipv4 6to4: Specifies the 6to4 tunnel mode.
mode ipv6-ipv4 auto-tunnel: Specifies the IPv4-compatible IPv6 automatic tunnel mode.
mode ipv6-ipv4 isatap: Specifies the ISATAP tunnel mode.
mode mgre: Specifies the mGRE tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode mpls-te: Specifies the MPLS TE tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK: Yes MSR810-LMS-EA: No |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode nve: Specifies the NVE tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
mode vxlan: Specifies the VXLAN tunnel mode.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
Usage guidelines
To create a new tunnel interface, you must specify the tunnel mode in this command. To enter the view of an existing tunnel interface, you do not need to specify the tunnel mode.
A tunnel interface number is locally significant. The tunnel interfaces on the two ends of a tunnel can use the same or different interface numbers.
Examples
# Create GRE/IPv4 tunnel interface Tunnel 1 and enter tunnel interface view.
<Sysname> system-view
[Sysname] interface tunnel 1 mode gre
[Sysname-Tunnel1]
Related commands
destination
display interface tunnel
source
mtu
Use mtu to set the MTU on a tunnel interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
If the tunnel interface has never been up, the MTU is 64000 bytes.
If the tunnel interface is up, its MTU is identical to the outgoing interface's MTU minus the length of the tunnel headers. The outgoing interface is automatically obtained through routing table lookup based on the tunnel destination address.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU, in the range of 100 to 64000 bytes.
Usage guidelines
After you configure an MTU for a tunnel interface, the configured MTU applies regardless of the tunnel interface status (up/down) and the outgoing interface MTU.
To avoid fragmentation after tunnel encapsulation, set the tunnel interface MTU no greater than the value of the outgoing interface MTU minus the length of the tunnel headers.
Examples
# Set the MTU on Tunnel 1 to 1000 bytes.
<Sysname> system-view
[Sysname] interface tunnel 1
[Sysname-Tunnel1] mtu 1000
Related commands
display interface tunnel
reset counters interface tunnel
Use reset counters interface tunnel to clear tunnel interface statistics.
Syntax
reset counters interface [ tunnel [ number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
tunnel [ number ]: Specifies a tunnel interface. The number argument specifies the tunnel interface number. If you do not specify the tunnel keyword, this command clears statistics for all interfaces except VA interfaces. If you specify the tunnel keyword without the number argument, this command clears statistics for all tunnel interfaces.
Usage guidelines
Use this command to clear old statistics so you can observe new traffic statistics on a tunnel interface.
Examples
# Clear statistics for Tunnel 1.
<Sysname> reset counters interface tunnel 1
display interface tunnel
service
Use service to specify a primary traffic processing slot for a tunnel interface.
Use undo service to restore the default.
Syntax
service slot slot-number
undo service slot
The following compatibility matrix shows the support of hardware platforms for this command:
|
Hardware |
Command compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
No |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
No |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
Default
No primary traffic processing slot is specified for a tunnel interface.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
|
|
CAUTION: The following operations might cause a tunnel interface in up state to be down and then up: · Specifying a primary or backup traffic processing slot for the tunnel interface. · Rebooting or hot-swapping the primary or backup traffic processing slot of the tunnel interface. Make sure you understand the potential impact of the operations on your network. |
This command is supported only in IRF mode.
Specify a traffic processing slot if a feature (for example, IPsec antireplay) requires that all traffic on a tunnel interface 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. The 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 processing slot for Tunnel 200.
<Sysname> system-view
[Sysname] interface tunnel 200
[Sysname-Tunnel200] service slot 1
Related commands
service standby
service standby
Use service standby to specify a backup traffic processing slot for an interface.
Use undo service standby to restore the default.
Syntax
service standby slot slot-number
undo service standby slot
The following compatibility matrix shows the support of hardware platforms for this command:
|
Hardware |
Command compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
No |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
No |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
No |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
Default
No backup traffic processing slot is specified for an interface.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
|
|
CAUTION: The following operations might cause a tunnel interface in up state to be down and then up: · Specifying a primary or backup traffic processing slot for the tunnel interface. · Rebooting or hot-swapping the primary or backup traffic processing slot of the tunnel interface. Make sure you understand the potential impact of the operations on your network. |
This command is supported on IRF-capable devices.
Specify a traffic processing slot if a feature (for example, IPsec antireplay) requires that all traffic on a tunnel interface 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. The 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 and a backup traffic processing slot for Tunnel 200.
<Sysname> system-view
[Sysname] interface tunnel 200
[Sysname-Tunnel200] service slot 2
[Sysname-Tunnel200] service standby slot 3
Related commands
service
shutdown
Use shutdown to shut down a tunnel interface.
Use undo shutdown to bring up a tunnel interface.
Syntax
shutdown
undo shutdown
Default
A tunnel interface is down.
Views
Tunnel interface view
Predefined user roles
network-admin
Usage guidelines
This command disconnects all links set up on the interface. Make sure you fully understand the impact of the command on your network.
Examples
# Shut down Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1
[Sysname-Tunnel1] shutdown
Related commands
display interface tunnel
source
Use source to specify the source address or source interface for a tunnel interface.
Use undo source to restore the default.
Syntax
source { ipv4-address | ipv6-address | interface-type interface-number }
undo source
Default
No source address or source interface is specified for a tunnel interface.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies the tunnel source IPv4 address.
ipv6-address: Specifies the tunnel source IPv6 address.
Usage guidelines
The specified source address or the address of the specified source interface is used as the source address of tunneled packets. To display the configured tunnel source address, use the display interface tunnel command.
Do not specify the same tunnel source and destination addresses for the tunnel interfaces on the same device.
The destination address of the local tunnel interface must be the source address of the peer tunnel interface. The source address of the local tunnel interface must be the destination address of the peer tunnel interface.
If you execute this command multiple times, the most recent configuration takes effect.
You cannot specify the tunnel interface of the DS-Lite tunnel on the AFTR as the source interface.
Examples
# Specify GigabitEthernet 1/0/1 as the source interface of Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode gre
[Sysname-Tunnel1] source gigabitethernet 1/0/1
# Specify 192.100.1.1 as the source address of Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode gre
[Sysname-Tunnel1] source 192.100.1.1
destination
display interface tunnel
interface tunnel
tunnel 6rd br
Use tunnel 6rd br to specify a BR address for a 6RD tunnel.
Use undo tunnel 6rd br to restore the default.
Syntax
tunnel 6rd br ipv4-address
undo tunnel 6rd br
Default
No BR address is specified for a 6RD tunnel.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies the BR address (IPv4 address of a 6RD BR router), in dotted decimal notation.
Usage guidelines
Use this command on a 6RD CE. For a 6RD network to communicate with a non-6RD network over a 6RD tunnel, you must specify the BR address on the 6RD CE.
All the 6RD CEs and 6RD BR routers in a 6RD network must have the same IPv4 prefix and suffix. Make sure the BR address and the tunnel source address have the same IPv4 prefix and suffix.
Examples
# Specify the BR address as 10.11.12.13 on Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode ipv6-ipv4 6rd
[Sysname-Tunnel1] tunnel 6rd br 10.11.12.13
Related commands
display 6rd
tunnel 6rd ipv4
Use tunnel 6rd ipv4 to specify a prefix length and a suffix length for a 6RD tunnel source address.
Use undo tunnel 6rd ipv4 to restore the default.
Syntax
tunnel 6rd ipv4 { prefix-length length | suffix-length length } *
undo tunnel 6rd ipv4
Default
All 32 bits of the IPv4 tunnel source address are used to create the 6RD delegated prefix.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
prefix-length length: Specifies the prefix length in the range of 0 to 31.
suffix-length length: Specifies the suffix length in the range of 0 to 31.
Usage guidelines
All 6RD tunnel interfaces in a 6RD network must be configured with the same IPv4 prefix length and suffix length.
You can specify a prefix length, a suffix length, both prefix and suffix lengths, or neither. The device will remove the prefix and suffix bits from the tunnel source address and embed the left bits of the address to the 6RD delegated prefix. If neither a prefix length nor a suffix length is specified, all 32 bits of the IPv4 tunnel source address will be embedded in the 6RD delegated prefix.
Examples
# Specify both the prefix length and suffix length as 8 on Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode ipv6-ipv4 6rd
[Sysname-Tunnel1] tunnel 6rd ipv4 prefix-length 8 suffix-length 8
Related commands
display 6rd
display 6rd destination
display 6rd prefix
tunnel 6rd prefix
Use tunnel 6rd prefix to configure the 6RD prefix for a 6RD tunnel.
Use undo tunnel 6rd prefix to restore the default.
Syntax
tunnel 6rd prefix ipv6-prefix/prefix-length
undo tunnel 6rd prefix
Default
No 6RD prefix is configured for a 6RD tunnel.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
ipv6-prefix/prefix-length: Specifies the IPv6 prefix and its length. The value range for the prefix length is 1 to 127.
Usage guidelines
A 6RD delegated prefix contains a 6RD prefix and all or part of the bits in the IPv4 tunnel source address.
All tunnels in a 6RD network must have the same 6RD prefix.
Examples
# Configure the 6RD prefix as 2001:1000::/32 on Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode ipv6-ipv4 6rd
[Sysname-Tunnel1] tunnel 6rd prefix 2001:1000::/32
Related commands
display 6rd
display 6rd destination
display 6rd prefix
tunnel dfbit enable
Use tunnel dfbit enable to set the Don't Fragment (DF) bit for tunneled packets.
Use undo tunnel dfbit enable to restore the default.
Syntax
tunnel dfbit enable
undo tunnel dfbit enable
Default
The DF bit is not set for tunneled packets.
Views
Tunnel interface view
Predefined user roles
network-admin
Usage guidelines
To avoid fragmentation and delay, set the DF bit for tunneled packets. Make sure the path MTU is larger than the tunneled packet length. To avoid discarding tunneled packets whose length is larger than the path MTU, do not set the DF bit.
This command is not supported on a GRE/IPv6 tunnel interface and an IPv6 tunnel interface.
Examples
# Set the DF bit for tunneled packets on Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode gre
[Sysname-Tunnel1] tunnel dfbit enable
tunnel discard ipv4-compatible-packet
Use tunnel discard ipv4-compatible-packet to enable dropping IPv6 packets that use IPv4-compatible IPv6 addresses.
Use undo tunnel discard ipv4-compatible-packet to restore the default.
Syntax
tunnel discard ipv4-compatible-packet
undo tunnel discard ipv4-compatible-packet
The following compatibility matrix shows the support of hardware platforms for this command:
|
Hardware |
Command compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
Default
IPv6 packets that use IPv4-compatible IPv6 addresses are not dropped.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command enables the device to check the source and destination IPv6 addresses of the de-encapsulated IPv6 packets from a tunnel. If a packet uses an IPv4-compatible IPv6 address as the source or destination address, the device discards the packet.
Examples
# Enable dropping IPv6 packets that use IPv4-compatible IPv6 addresses.
<Sysname> system-view
[Sysname] tunnel discard ipv4-compatible-packet
tunnel tos
Use tunnel tos to set the ToS of tunneled packets.
Use undo tunnel tos to restore the default.
Syntax
tunnel tos { copy-inner-tos | tos-value }
undo tunnel tos
Default
For VXLAN tunneled packets, the ToS is 0.
For non-VXLAN tunneled packets, the ToS is the same as the ToS of the original packets.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
tos-value: Specifies the ToS of tunneled packets, in the range of 0 to 255.
copy-inner-tos: Configures tunneled packets to use the ToS of the original packets. This keyword is supported only by VXLAN tunnels.
The following compatibility matrix shows the support of hardware platforms for this keyword:
|
Hardware |
Parameter compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA |
Yes |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR2600-6-X1, MSR2600-10-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC |
Yes |
|
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
Usage guidelines
After you execute this command, all the tunneled packets of different services sent on the tunnel interface will use the same configured ToS. For more information about ToS, see ACL and QoS Configuration Guide.
Examples
# Set the ToS of tunneled packets to 20 on Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode gre
[Sysname-Tunnel1] tunnel tos 20
# Configure VXLAN tunnel interface Tunnel 2 to use the ToS of the original packets as the ToS of tunneled packets.
<Sysname> system-view
[Sysname] interface tunnel 2 mode vxlan
[Sysname-Tunnel2] tunnel tos copy-inner-tos
Related commands
display interface tunnel
tunnel ttl
Use tunnel ttl to set the Time to Live (TTL) of tunneled packets.
Use undo tunnel ttl to restore the default.
Syntax
tunnel ttl ttl-value
undo tunnel ttl
Default
The TTL of tunneled packets is 255.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
ttl-value: Specifies the TTL of tunneled packets, in the range of 1 to 255.
Usage guidelines
The TTL determines the maximum number of hops that the tunneled packets can pass. When the TTL expires, the tunneled packets are discarded to avoid loops.
Examples
# Set the TTL of tunneled packets to 100 on Tunnel 1.
<Sysname> system-view
[Sysname] interface tunnel 1 mode gre
[Sysname-Tunnel1] tunnel ttl 100
Related commands
display interface tunnel
tunnel vpn-instance
Use tunnel vpn-instance to specify a VPN instance for the destination address of a tunnel interface.
Use undo tunnel vpn-instance to restore the default.
Syntax
tunnel vpn-instance vpn-instance-name
undo tunnel vpn-instance
Default
The destination address of a tunnel interface belongs to the public network.
Views
Tunnel interface view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
After this command is executed, the device looks up the routing table of the specified VPN instance to forward tunneled packets on the tunnel interface.
For a tunnel interface to come up, the tunnel source and destination must belong to the same VPN instance. To specify a VPN instance for the tunnel source, use the ip binding vpn-instance command on the tunnel source interface.
Examples
# Specify VPN instance vpn10 for the tunnel destination on Tunnel 1.
<Sysname> system-view
[Sysname] ip vpn-instance vpn10
[Sysname-vpn-instance-vpn10] route-distinguisher 1:1
[Sysname-vpn-instance-vpn10] vpn-target 1:1
[Sysname-vpn-instance-vpn10] quit
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] ip binding vpn-instance vpn10
[Sysname-GigabitEthernet1/0/1] ip address 1.1.1.1 24
[Sysname-GigabitEthernet1/0/1] quit
[Sysname] interface tunnel 1 mode gre
[Sysname-Tunnel1] source gigabitethernet 1/0/1
[Sysname-Tunnel1] destination 1.1.1.2
[Sysname-Tunnel1] tunnel vpn-instance vpn10
Related commands
ip binding vpn-instance (MPLS Command Reference)
