Contents

Tunneling commands· 1

bandwidth· 1

default 1

description· 2

destination· 2

display ds-lite b4 information· 4

display interface tunnel 5

ds-lite enable· 10

encapsulation-limit 11

interface tunnel 11

mtu· 13

reset counters interface tunnel 14

shutdown· 14

source· 15

tunnel dfbit enable· 16

tunnel discard ipv4-compatible-packet 16

tunnel log updown with-tag· 17

tunnel out-interface· 18

tunnel path-mtu enable· 18

tunnel tos· 19

tunnel ttl 20

tunnel vpn-instance· 21

 

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.

For more information, see OSPF, OSPFv3, and IS-IS in 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

Related commands

display interface tunnel

destination

Use destination to specify the destination address of a tunnel.

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, you must configure the destination address. For an automatic tunnel, 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 a tunnel at the local end must be the source address of the tunnel at the peer end. The source address of the tunnel at the local end must be the destination address of the tunnel at the peer end.

Do not specify the same tunnel source and destination addresses for different tunnels 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

# Interface GigabitEthernet 1/0 on Sysname 1 uses IP address 193.101.1.1 and interface GigabitEthernet 1/0 on Sysname 2 uses IP address 192.100.1.1. Configure the tunnel source address as 193.101.1.1 and tunnel destination address as 192.100.1.1 for tunnel 1 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 tunnel source address as 192.100.1.1 and tunnel destination address as 193.101.1.1 for tunnel 1 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

Related commands

display interface tunnel

interface tunnel

ipv6 address dhcp-alloc

source

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 1 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 PPP 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

Tunnel1

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 2 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. ·     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, 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. ·     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. ·     IPSEC P2MP—IPsec P2MP tunnel mode. ·     DSLITE—DS-Lite tunnel mode on the AFTR. ·     Segment-Routing/IPv6—SRv6 tunnel mode. ·     UDP_VXLAN/IP—UDP-encapsulated IPv4 VXLAN tunnel mode. ·     UDP_VXLAN/IPv6—UDP-encapsulated IPv6 VXLAN tunnel mode. ·     UDP_VXLAN_DCI/IP—UDP-encapsulated IPv4 VXLAN-DCI tunnel mode. ·     UDP_VXLAN_DCI/IPv6—UDP-encapsulated IPv6 VXLAN-DCI 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: Number of packets in the queue/maximum number of packets that the queue can contain/number of packets discarded in the queue.
Output queue - Protocol queuing: Size/Length/Discards 0/500/0	Protocol output queue statistics: Number of packets in the queue/maximum number of packets that the queue can contain/number of packets discarded in the queue.
Output queue - FIFO queuing: Size/Length/Discards 0/75/0	FIFO output queue statistics: Number of packets in the queue/maximum number of packets that the queue can contain/number of packets discarded in the queue. 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 3 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.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] 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 ] | ipsec-p2mp | ipv4-ipv4 | ipv6 | ipv6-ipv4 [ 6to4 | auto-tunnel | isatap ] | mpls-te | nve | nvgre | sr ipv6 | { vxlan | vxlan-dci } [ ipv6 ] } ]

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 value range is 0 to 65534. The number of tunnel interfaces that can be created is restricted by the total number of interfaces and the memory.

mode advpn gre: Specifies the GRE-encapsulated IPv4 ADVPN tunnel mode.

mode advpn udp: Specifies the UDP-encapsulated IPv4 ADVPN tunnel mode.

mode advpn gre ipv6: Specifies the GRE-encapsulated IPv6 ADVPN tunnel mode.

mode advpn udp ipv6: Specifies the UDP-encapsulated IPv6 ADVPN tunnel mode.

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.

mode gre-p2mp ipv6: Specifies the GRE/IPv6 P2MP tunnel mode.

mode ipsec: Specifies the IPsec/IPv4 tunnel mode.

mode ipsec ipv6: Specifies the IPsec/IPv6 tunnel mode.

mode ipsec-p2mp: Specifies the IPsec P2MP tunnel mode.

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 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 mpls-te: Specifies the MPLS TE tunnel mode.

mode nve: Specifies the NVE tunnel mode.

mode nvgre: Specifies the NVGRE tunnel mode.

mode sr ipv6: Specifies the SRv6 tunnel mode.

mode vxlan: Specifies the IPv4 VXLAN tunnel mode.

mode vxlan ipv6: Specifies the IPv6 VXLAN tunnel mode.

mode vxlan-dci: Specifies the IPv4 VXLAN-DCI tunnel mode.

mode vxlan-dci ipv6: Specifies the IPv6 VXLAN-DCI tunnel mode.

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

Related commands

display interface tunnel

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 not administratively 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 of a tunnel.

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.

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.

interface-type interface-number: Specifies the source interface by its type and number. The interface must be up and must have an IP 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 different tunnels on the same device.

The destination address of a tunnel at the local end must be the source address of the tunnel at the peer end. The source address of the tunnel at the local end must be the destination address of the tunnel at the peer end.

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 as the source interface of Tunnel 1.

<Sysname> system-view

[Sysname] interface tunnel 1 mode gre

[Sysname-Tunnel1] source gigabitethernet 1/0

# 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

Related commands

destination

display interface tunnel

interface tunnel

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

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 log updown with-tag

Use tunnel log updown with-tag to add the TUNNEL string to the PHY_UPDOWN log mnemonic for tunnel interfaces.

Use undo tunnel log updown with-tag to remove the TUNNEL string from the PHY_UPDOWN log mnemonic for tunnel interfaces.

Syntax

tunnel log updown with-tag

undo tunnel log updown with-tag

Default

The PHY_UPDOWN log mnemonic for tunnel interfaces does not contain the TUNNEL string.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command adds the TUNNEL string to the PHY_UPDOWN log mnemonic for tunnel interfaces. Use this command if you want to identify the interface state change logs for tunnel interfaces by using a regular expression that contains the TUNNEL string.

A tunnel interface state change log without the TUNNEL string in the mnemonic:

%Jan 8 18:45:33:621 2011 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Tunnel1 changed to down.

A tunnel interface state change log with the TUNNEL string in the mnemonic:

%Jan 8 18:45:33:621 2011 H3C IFNET/3/TUNNEL_PHY_UPDOWN: Physical state on the interface Tunnel1 changed to down.

Examples

# Add the TUNNEL string to the PHY_UPDOWN log mnemonic for tunnel interfaces.

<Sysname> system-view

[Sysname] tunnel log updown with-tag

tunnel out-interface

Use tunnel out-interface to specify an output interface for tunneled packets.

Use undo tunnel out-interface to restore the default.

Syntax

tunnel out-interface interface-type interface-number

undo tunnel out-interface

Default

No output interface is specified for tunneled packets of a tunnel interface. If ECMP routes exist, the device randomly selects an output interface to forward the tunneled packets.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number.

Usage guidelines

Use this command to control the forwarding path of tunneled packets. To ensure successful packet forwarding, the specified output interface must meet the following requirements:

·     The interface is up.

·     The interface has an IP address.

·     The interface has a route to reach the destination.

If you execute this command multiple times, the most recent configuration takes effect.

This command is applicable only to IPv4 ADVPN, IPv6 ADVPN, GRE/IPv4, GRE/IPv6, and VXLAN tunnel interfaces.

Examples

# Specify GigabitEthernet 1/0 as the output interface of GRE packets on tunnel interface Tunnel 0.

<Sysname> system-view

[Sysname] interface tunnel 0 mode gre

[Sysname-Tunnel0] tunnel out-interface gigabitethernet 1/0

tunnel path-mtu enable

Use tunnel path-mtu enable to enable path MTU learning on a tunnel interface.

Use undo tunnel path-mtu enable to disable path MTU learning on a tunnel interface.

Syntax

tunnel path-mtu enable

undo tunnel path-mtu enable

Default

Path MTU learning is disabled on a tunnel interface.

Views

Tunnel interface view

Predefined user roles

network-admin

Usage guidelines

If the size of a tunneled packet exceeds the MTU of an interface in the tunnel path, the packet will be discarded. With the path MTU learning feature, the tunnel source can adjust the MTU of the tunnel interface according to the MTU information in received ICMP destination unreachable messages. After MTU adjustment, the tunnel source will resend the oversized tunneled packets, improving the forwarding reliability of tunnel packets.

This command cannot be used together with the mtu command on a tunnel interface.

This command is supported only on GRE/IPv4, GRE/IPv6, and VXLAN tunnel interfaces.

If path MTU learning is enabled on a GRE/IPv4 tunnel interface and the passenger protocol is IPv6, make sure the MTU of all interfaces in the tunnel path is equal to or greater than 1312 bytes. If the MTU of an interface in the tunnel path is less than 1312 bytes, forwarding failure will occur.

If path MTU learning is enabled on a GRE/IPv6 tunnel interface and the passenger protocol is IPv6, make sure the MTU of all interfaces in the tunnel path is equal to or greater than 1332 bytes. If the MTU of an interface in the tunnel path is less than 1332 bytes, forwarding failure will occur.

Examples

# Enable path MTU learning on tunnel interface Tunnel 0.

<Sysname> system-view

[Sysname] interface tunnel 0 mode gre

[Sysname-Tunnel0] tunnel path-mtu enable

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

copy-inner-tos: Configures tunneled packets to use the ToS of the original packets. This keyword is supported only by VXLAN tunnels.

tos-value: Specifies the ToS of tunneled packets, in the range of 0 to 255.

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

[Sysname-GigabitEthernet1/0] ip binding vpn-instance vpn10

[Sysname-GigabitEthernet1/0] ip address 1.1.1.1 24

[Sysname-GigabitEthernet1/0] quit

[Sysname] interface tunnel 1 mode gre

[Sysname-Tunnel1] source gigabitethernet 1/0

[Sysname-Tunnel1] destination 1.1.1.2

[Sysname-Tunnel1] tunnel vpn-instance vpn10

Related commands

ip binding vpn-instance (MPLS Command Reference)