Table of Contents

Chapter 1 Tunneling Configuration Commands. 1-1

1.1 Tunnel Configuration Commands. 1-1

1.1.1 aggregation-group. 1-1

1.1.2 debugging ipv4-tunnel 1-2

1.1.3 debugging ipv6-tunnel 1-4

1.1.4 debugging tunnel 1-7

1.1.5 destination. 1-9

1.1.6 display interface tunnel 1-11

1.1.7 display ipv6 interface tunnel 1-12

1.1.8 expediting enable. 1-14

1.1.9 expediting subnet 1-14

1.1.10 interface tunnel 1-16

1.1.11 mtu (tunnel interface view) 1-17

1.1.12 source. 1-17

1.1.13 tunnel-protocol 1-18

 

Chapter 1  Tunneling Configuration Commands

1.1  Tunnel Configuration Commands

1.1.1  aggregation-group

Syntax

aggregation-group aggregation-group-ID

undo aggregation-group

View

Tunnel interface view

Default Level

2: System level

Parameters

aggregation-group-id: Link aggregation group ID to be referenced.

Description

Use the aggregation-group command to specify a link aggregation group to be referenced by a tunnel.

Use the undo aggregation-group command to remove the link aggregation group referenced by a tunnel.

By default, a tunnel does not reference any link aggregation group.

Before specifying a link aggregation group for a tunnel in tunnel interface view, you have configured the link aggregation group and set the service type of the link aggregation group to tunnel in system view.

One tunnel interface can reference only one link aggregation group.

Related commands: link-aggregation group in Link Aggregation Commands in Access Volume.

Examples

# Create link aggregation group 1, and set the configuration mode to manual and the service type to tunnel.

<Sysname> system-view

[Sysname] link-aggregation group 1 mode manual

[Sysname] link-aggregation group 1 service-type tunnel

# Add a Gigabit Ethernet interface to link aggregation group 1 on the card that supports IPv6.

[Sysname] interface GigabitEthernet 6/4/1

[Sysname-GigabitEthernet6/4/1] stp disable

[Sysname-GigabitEthernet6/4/1] port link-aggregation group 1

# Reference link aggregation group 1 in tunnel interface view.

[Sysname] interface Tunnel 3/0/1

[Sysname-Tunnel3/0/1] aggregation-group 1

1.1.2  debugging ipv4-tunnel

Syntax

debugging ipv4-tunnel { all | error | packet }

undo debugging ipv4-tunnel { all | error | packet }

View

User view

Default Level

1: Monitor level

Parameters

all: Enables all types of debugging for the IPv4 tunnel module.

error: Enables error debugging for the IPv4 tunnel module.

packet: Enable packet debugging for the IPv4 tunnel module.

Description

Use the debugging ipv4-tunnel command to enable debugging for the IPv4 tunnel module.

Use the undo debugging ipv4-tunnel command to disable debugging for the IPv4 tunnel module.

By default, debugging for the IPv4 tunnel module is disabled.

Table 1-1 Description on the fields of the debugging ipv4-tunnel error command

Field	Description
Getting tunnel mode failed.	Failed to get the tunnel mode based on interface index
Transmitting IP packet failed.	The tunnel interface failed to forward the encapsulated IPv4 packet.
Transmitting IPv6 packet failed.	The tunnel interface failed to forward the encapsulated IPv6 packet.
Adding IPv4 header failed.	Failed to add the IPv4 header to the IPv6 packet.
Adding IPv6 header failed.	Failed to add the IPv6 header to the IPv6 packet
Invalid V4 source address	The packet will be discarded due to the invalid source address in the IPv4 header.
Invalid V6 source address	The packet will be discarded due to the invalid source address in the IPv6 header.

 

Table 1-2 Description on the fields of the debugging ipv4-tunnel packet command

Field	Description
Tunnelm packet:Before encapsulation,         Outer packet header ipaddress1->ipaddress2(length = length)	Before encapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipaddress1 and ipaddress2 respectively, and the packet length is length.
Tunnelm packet:After encapsulation,         Outer packet header ipaddress1-> ipaddress2(length = length)	After encapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipaddress1 and ipaddress2 respectively, and the packet length is length.
Ipv4-tunnel_packet: Decapsulate tunnel packet         Incoming packet header ipaddress1-> ipaddress2 (length = length)	Before decapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipaddress1 and ipaddress2 respectively, and the packet length is length.
Tunnelm packet:After decapsulation,         Outgoing packet header ipaddress1-> ipaddress2 (length = length)	After decapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipaddress1 and ipaddress2 respectively, and the packet length is length.

 

Examples

# After establishing an IPv4 tunnel between two devices, enable packet debugging for the IPv4 tunnel module on a device. Use the ping command to view the debugging information.

<Sysname> debugging ipv4-tunnel packet

<Sysname> ping –c 1 5.5.5.2

  PING 5.5.5.2: 56  data bytes, press CTRL_C to break

*0.2812406 Sysname IPV4-TUN/8/debug:

 Tunnel4/0/1 packet:Before encapsulation,

        Outer packet header 5.5.5.1->5.5.5.2(length = 84)

// Before encapsulation at interface Tunnel 4/0/1, the source and destination IP addresses of the packet header are 5.5.5.1 and 5.5.5.2 respectively, and the packet length is 84.

*0.2812422 Sysname IPV4-TUN/8/debug:

 Tunnel4/0/1 packet:After encapsulation,

        Outer packet header 192.168.19.41->192.168.19.42(length = 104)

// After encapsulation at interface Tunnel 4/0/1, the source and destination IP addresses of the packet header are 192.168.19.41 and 192.168.19.42 respectively, and the packet length is 104.

*0.2812468 Sysname IPV4-TUN/8/debug:

 ipv4-tunnel_packet: Decapsulate tunnel packet

        Incoming packet header 192.168.19.42->192.168.19.41(length = 104)

// Before decapsulation at interface Tunnel 4/0/1, the source and destination IP addresses of the packet header are 192.168.19.42 and 192.168.19.41 respectively, and the packet length is 104.

*0.2812468 Sysname IPV4-TUN/8/debug:

 Tunnel4/0/1 packet:After decapsulation,

        Outgoing packet header 5.5.5.2->5.5.5.1(length = 84)

// After decapsulation at interface Tunnel 4/0/1, the source and destination IP addresses of the packet header are 5.5.5.2 and 5.5.5.1 respectively, and the packet length is 84.

    Reply from 5.5.5.2: bytes=56 Sequence=1 ttl=255 time=78 ms

 

  --- 5.5.5.2 ping statistics ---

    1 packet(s) transmitted

    1 packet(s) received

    0.00% packet loss

    round-trip min/avg/max = 78/78/78 ms

1.1.3  debugging ipv6-tunnel

Syntax

debugging ipv6-tunnel { all | error | packet }

undo debugging ipv6-tunnel { all | error | packet }

View

User view

Default Level

1: Monitor level

Parameters

all: Enables all types of debugging for the IPv6 tunnel module.

error: Enables error debugging for the IPv6 tunnel module.

packet: Enables packet debugging for the IPv6 tunnel module.

Description

Use the debugging ipv6-tunnel command to enable debugging for the IPv6 tunnel module.

Use the undo debugging ipv6-tunnel command to disable debugging for the IPv6 tunnel module.

By default, debugging for the IPv6 tunnel is disabled.

Table 1-3 Description on the fields of the debugging ipv6-tunnel error command

Field	Description
Getting destination failed	Failed to get the tunnel destination IPv4 address embedded in the destination address of the IPv6 packet
Getting tunnel mode failed.	Failed to get the tunnel mode based on interface index
fragment check	Check IPv6 packet fragments based on RFC 2893
IPv4 transmit failed.	The tunnel interface failed to forward the encapsulated IPv4 tunnel packet.
IPv6 transmit failed.	The tunnel interface failed to forward the encapsulated IPv6 tunnel packet.
Adding IPv4 header failed.	Failed to add the IPv4 header to the IPv6 packet
Adding IPv6 header failed.	Failed to add the IPv6 header to the IPv6 packet
transprotocol is invalid.	The packet sent out the tunnel uses an invalid transport layer protocol.

 

Table 1-4 Description on the fields of the debugging ipv6-tunnel packet command

Field	Description
Tunnelm packet: Before encapsulation,         Incoming packet header ipv6-address1->ipv6-address2(length = length)	Before encapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipv6-address1 and ipv6-address2 respectively, and the packet length is length.
Tunnelm packet: After encapsulation,         Outgoing packet header ipv6-address1->ipv6-address2 (length = length)	After encapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipv6-address1 and ipv6-address2 respectively, and the packet length is length.
Ipv6-tunnel_packet: Decapsulate tunnel packet         Incoming packet header ipv6-address1->ipv6-address2 (length = length)	Before decapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipv6-address1 and ipv6-address2 respectively, and the packet length is length.
Tunnelm packet: After decapsulation,         Outgoing packet header ipv6-address1->ipv6-address2 (length = length)	After decapsulation at the tunnel interface Tunnelm, the source and destination IP addresses of the packet header are ipv6-address1 and ipv6-address2 respectively, and the packet length is length.

 

Examples

# After establishing an IPv6 tunnel between two devices, enable error debugging for the IPv6 tunnel module on a device, and execute the ping command to view the following debugging information.

<Sysname> debugging ipv6-tunnel packet

<Sysname> ping ipv6 –c 1 2005::2

  PING 2005::2 : 56  data bytes, press CTRL_C to break

*0.3760250 Sysname IPV6-TUN/8/debug:

 Tunnel4/0/2 packet: Before encapsulation,

        Incoming packet header 2005::0001->2005::0002(length = 104)

// Before encapsulation at the tunnel interface Tunnel 4/0/2, the source and destination IP addresses of the packet header are 2005::0001 and 2005::0002 respectively, and the packet length is 104.

*0.3760265 Sysname IPV6-TUN/8/debug:

 Tunnel4/0/2 packet: After encapsulation,

        Outgoing packet header 2003::0001->2003::0002(length = 144)

// After encapsulation at the tunnel interface Tunnel 4/0/2, the source and destination IP addresses of the packet header are 2003::0001 and 2003::0002 respectively, and the packet length is 144.

*0.3760297 Sysname IPV6-TUN/8/debug:

 ipv6-tunnel_event:transproto is ipv6.

*0.3760297 Sysname IPV6-TUN/8/debug:

 ipv6-tunnel_packet: Decapsulate tunnel packet

        Incoming packet header 2003::0002->2003::0001(length = 144)

// Before decapsulation at the tunnel interface Tunnel 4/0/2, the source and destination IP addresses of the packet header are 2003::0002 and 2003::0001 respectively, and the packet length is 144.

*0.3760312 Sysname IPV6-TUN/8/debug:

 Tunnel4/0/2 packet: After decapsulation,

        Outgoing packet header 2005::0002->2005::0001(length = 104)

// After encapsulation at the tunnel interface Tunnel 4/0/2, the source and destination IP addresses of the packet header are 2005::0002 and 2005::0001 respectively, and the packet length is 104.

   Reply from 2005::2: Bytes=56 Sequence=1 hop limit=255  time = 78 ms

 

  --- 2005::2 ping statistics ---

    1 packet(s) transmitted

    1 packet(s) received

    0.00% packet loss

    round-trip min/avg/max = 78/78/78 ms

1.1.4  debugging tunnel

Syntax

debugging tunnel { all | error | event | packet }

undo debugging tunnel { all | error | event | packet }

View

User view

Default Level

1: Monitor level

Parameters

all: Enables all types of debugging for the tunnel module.

error: Enables error debugging for the tunnel module.

event: Enables event debugging for the tunnel module.

packet: Enables packet debugging for the tunnel module.

Description

Use the debugging tunnel command to enable debugging for the tunnel module. Use the undo debugging tunnel command to disable debugging for the tunnel module.

By default, debugging for the tunnel module is disabled.

Table 1-5 Description on the fields of the debugging tunnel error command

Field	Description
Failed to initialize control block.	Failed to initialize the link control block of the tunnel interface
Failed to release data block.	Failed to release the tunnel mode data block
Failed to sending release msg when disabling TE.	Failed to send the release message when disabling MPLS TE
Failed to send message of change mode.	Failed to send the message for changing the tunnel mode
Failed to initialize tunnel when disabling TE.	Failed to initialize the default tunnel mode when disabling MPLS TE
Failed to get logic slot..	Failed to get the logic slot where the tunnel interface is located
failed to add src-ifindex hash table.	Failed to add entries to the hash table of the tunnel source interface
failed to delete UP tunnel from src-index hash-table.	Failed to delete the tunnel control block (CB) from the hash table of the source interface after the IP address of the source tunnel interface changes.
Failed to get Ipv4 address.	Failed to get the IPv4 address of the interface based on interface index
Failed to get IPv6 address.	Failed to get the IPv6 address of the interface based on interface index
Tunnel CB is NULL.	The tunnel CB pointer is null.
Can't get interface name.	Cannot get the interface name based on interface index.
Can't malloc memories	Cannot allocate memory
can't get physical statistic pointer.	Cannot get the physical CB pointer of the tunnel interface based on interface index
The interface is not tunnel.	The interface is not a tunnel interface because of an invalid interface index.
The ulPortType is not tunnel.	The physical type of the interface is not tunnel.

 

Table 1-6 Description on the fields of the debugging tunnel event command

Field	Description
Tunnelm link state is DOWN, no change.	The link state of Tunnelm is down, which keeps unchanged.
Tunnelm down, because the source ip is not set.	The link state of Tunnelm is down because the source IP address is not configured.
Tunnelm down, because the dest address is required.	The link state of Tunnelm is down because the destination IP address is not configured.
Tunnelm down, because the aggregation group is required.	The link state of Tunnelm is down because the link aggregation group referenced by the tunnel is not configured. (This check is not available unless the link aggregation group ID is a mandatory parameter.)
Tunnelm down, because the status of aggregation group 1 is down.	The link state of Tunnelm is down because the link aggregation group referenced by the tunnel is in down state. (This check is not available unless the link aggregation group ID is a mandatory parameter.)

 

Table 1-7 Description on the fields of the debugging tunnel packet command

Field	Description
Tunnel receive packet	The tunnel interface received the packet from the drive.
Can't get up tunnel	Failed to find the tunnel in the up state according to the protocol type, source IP address and destination IP address of the packet received from the drive.
packet's ulLoopTimes	Times that the packet has been encapsulated by the protocol modules of the local device
Packet length: length	Length of the packet that the drive sent to the tunnel interface
displayed length: length	Displayed length of the packet that the drive sent to the tunnel interface

 

Examples

# Create a tunnel interface, and enable tunnel error debugging.

<Sysname> debugging tunnel error

# Set the tunnel mode to the configured mode, and view the following error information:

*0.4144313 Sysname TUNNEL/7/debug:

Tunnel(index = 0x2f0001) mode is the same to old one, no need to change!

// The tunnel mode is the same as the old one, so there is no need to change it.

1.1.5  destination

Syntax

destination { ip-address | ipv6-address }

undo destination

View

Tunnel interface view

Default Level

2: System level

Parameters

ip-address: Tunnel destination IPv4 address on the interface.

ip-address: Tunnel destination IPv6 address on the interface.

Description

Use the destination command to specify the tunnel destination address on the interface.

Use the undo destination command to remove the configured tunnel destination address.

By default, no tunnel destination address is configured on the interface.

Note that:

l           The tunnel destination address on the interface is the address of the peer interface receiving packets and is usually the tunnel source address on the peer interface.

l           Two or more tunnel interfaces using the same encapsulation protocol must have different source and destination addresses.

l           At present, the S9500 does not support the configuration of any tunnel destination IPv6 address on the interface.

Related commands: interface tunnel, source.

Examples

# Set the interface VLAN-interface 10 (193.101.1.1) of Sysname 1 and the interface VLAN-interface 20 (192.100.1.1) of Sysname 2 to the source and destination interfaces of a tunnel between the two devices, respectively.

<Sysname1> system-view

[Sysname1] interface Tunnel 3/0/1

[Sysname1-Tunnel3/0/1] source 193.101.1.1

[Sysname1-Tunnel3/0/1] destination 192.100.1.1

[Sysname1-Tunnel3/0/1] return

<Sysname2> system-view

[Sysname2] interface Tunnel 4/0/1

[Sysname2-Tunnel4/0/1] source 192.100.1.1

[Sysname2-Tunnel4/0/1] destination 193.101.1.1

1.1.6  display interface tunnel

Syntax

display interface tunnel [ number ]

View

Any view

Default Level

1: Monitor level

Parameters

number: Tunnel interface number, in the format of slot number./subslot number/Tunnel interface number. If the number argument is not specified, the information of all tunnel interfaces will be displayed.

Description

Use the display interface tunnel command to display related information of a specified tunnel interface, such as source address, destination address, and encapsulation mode.

Related commands: interface tunnel, source, destination, tunnel-protocol.

Examples

# Display information of the interface Tunnel 3/0/0.

<Sysname> display interface tunnel 3/0/0

Tunnel3/0/0 current state: UP

Line protocol current state: UP

Description: Tunnel3/0/0 Interface

The Maximum Transmit Unit is 1500

Internet Address is 10.1.2.1/24 Primary

Encapsulation is TUNNEL, aggregation ID not set

Tunnel source 192.13.2.1, destination 192.13.2.2

Tunnel protocol/transport GRE/IP

    GRE key disabled

    Checksumming of GRE packets disabled

    Last 300 seconds input:  0 bytes/sec, 0 packets/sec

    Last 300 seconds output:  0 bytes/sec, 0 packets/sec

    361 packets input,  9953388 bytes

    0 input error

    361 packets output,  30324 bytes

    0 output error

Table 1-8 Description on fields of the display interface tunnel command

Field	Description
Tunnel3/0/0 current state: UP	The physical layer state of the tunnel interface
Line protocol current state: UP	The IPv4 link layer protocol state of the tunnel interface
Description	Descriptive information of a tunnel interface
Tunnel3/0/0 Interface	Tunnel interface number
Maximum Transmit Unit	Maximum transmission unit (MTU) in a tunnel
Internet Address	IP address of the tunnel interface
Encapsulation is TUNNEL	The encapsulation protocol is tunnel
aggregation ID	Link aggregation group ID referenced by a tunnel
Tunnel source	Tunnel source address
destination	Tunnel destination address
Tunnel protocol/transport	Tunnel protocol and transport protocol.
GRE key disabled	No key is configured for the GRE tunnel interface.
Checksumming of GRE packets disabled	Disables the GRE packet checksum function.
Last 300 seconds input	Numbers of input bytes and packets processed by the CPU per second in the last five minutes.
Last 300 seconds output	Numbers of output bytes and packets processed by the CPU per second in the last five minutes.
packets input	Total number of input packets processed by the CPU.
input error	Number of error packets among all input packets processed by the CPU.
packets output	Total number of output packets processed by the CPU.
output error	Number of error packets in all output packets processed by the CPU

 

1.1.7  display ipv6 interface tunnel

Syntax

display ipv6 interface tunnel number

View

Any view

Default Level

1: Monitor level

Parameters

number: Tunnel interface number, in the format of slot No./subslot No./tunnel interface No.

Description

Use the display ipv6 interface tunnel command to display related IPv6 information of a specified tunnel interface, including link state, IPv6 protocol state, and IPv6 address.

Examples

# Display information of the interface Tunnel 3/0/0.

<Sysname> display ipv6 interface tunnel 3/0/0

Tunnel3/0/0 current state :UP

Line protocol current state :UP

IPv6 is enabled, link-local address is FE80::101:101

  Global unicast address(es):

    2002:101:101::1, subnet is 2002::/16

  Joined group address(es):

    FF02::1:FF01:101

    FF02::1:FF00:1

    FF02::2

    FF02::1

  MTU is 1500 bytes

  ND reachable time is 30000 milliseconds

  ND retransmit interval is 1000 milliseconds

  Hosts use stateless autoconfig for addresses

Table 1-9 Description on fields of the display interface tunnel command

Field	Description
Tunnel3/0/0 current state: UP	The physical layer state of the tunnel interface
Line protocol current state: UP	The IPv6 link layer protocol state of the tunnel interface
IPv6 is enabled	Enables IPv6 on a tunnel interface
link-local address	Link-local address of a tunnel interface
Global unicast address(es)	Aggregatable global unicast address of a tunnel interface.
Joined group address(es)	Multicast address of a tunnel interface.
MTU is 1500 bytes	Size of the MTU in a tunnel. The MTU in this example is 1,500 bytes.
ND reachable time	Neighbor reachable time
ND retransmit interval	Interval for retransmitting a neighbor discovery message.
Hosts use stateless autoconfig for addresses	Hosts use the stateless auto-configuration mode to acquire IPv6 addresses.

 

1.1.8  expediting enable

Syntax

expediting enable

undo expediting enable

View

Tunnel interface view

Default Level

2: System level

Parameters

None

Description

Use the expediting enable command to enable the expedite termination function.

Use the expediting enable command to disable the expedite termination function.

By default, the expedite termination function is disabled.

Examples

# Enable the expedite termination function

<Sysname> system-view

[Sysname] interface tunnel 2/0/0

[Sysname-Tunnel2/0/0] expediting enable

1.1.9  expediting subnet

Syntax

expediting subnet ip-address mask

undo expediting subnet

View

Tunnel interface view

Default Level

2: System level

Parameters

ip-address: Address of the expedite termination subnet of a tunnel

mask: Mask of the expedite termination subnet of a tunnel

Description

Use the expediting subnet command to set an IP address and mask for the expedite termination subnet.

Use the undo expediting subnet command to remove the configuration.

By default, no expedite termination subnet is configured for a tunnel.

Note that:

l           You must enable the expedite termination before configuring an expedite termination subnet in tunnel interface view.

l           The expediting subnet is not applicable to configured tunnels (for example, GRE tunnel and IPv6 manually configured tunnel). After the expedite termination function is enabled, the system will automatically consider the destination address of a tunnel as the address of the expedite termination subnet, and the subnet mask as 255.255.255.255.

l           For automatic tunnels (for example, 6to4 tunnel, ISATAP tunnel, and automatic IPv4-compatible IPv6 tunnel), you must carry out the expediting subnet command to designate an IP address and subnet for the expedite termination subnet after carrying out the expediting enable command.

 

 

Examples

# Configure an expedite termination subnet for a 6to4 tunnel: First enable the expedite termination, and then set the address of the expedite termination subnet to 1.1.1.2 and the subnet mask to 255.255.255.0.

<Sysname> system-view

[Sysname] interface tunnel 2/0/0

[Sysname-Tunnel2/0/0] expediting enable

[Sysname-Tunnel2/0/0] expediting subnet 1.1.1.2 255.255.255.0

1.1.10  interface tunnel

Syntax

interface tunnel number

undo interface tunnel number

View

System view

Default Level

2: System level

Parameters

number: Tunnel interface number, in the format of slot No./subslot No./tunnel interface No.

Description

Use the interface tunnel command to create a tunnel interface and enter tunnel interface view.

Use the undo interface tunnel command to remove a specified tunnel interface.

By default, there is no tunnel interface on the device.

l           Carry out the interface tunnel command to enter interface view of a specified tunnel. If the tunnel interface is not created, you must create it before entering tunnel interface view.

l           A tunnel interface number has only local significance, and therefore, the same interface number or different interface numbers can be set at both ends of a tunnel.

Related commands: display interface tunnel, source, destination, tunnel-protocol.

Examples

# Create the interface Tunnel 3/0/0.

<Sysname> system-view

[Sysname] interface tunnel 3/0/0

[Sysname-Tunnel3/0/0]

1.1.11  mtu (tunnel interface view)

Syntax

mtu mtu-size

undo mtu

View

Tunnel interface view

Default Level

2: System level

Parameters

mtu-size: Tunnel interface MTU in bytes.

Description

Use the mtu command to configure the tunnel interface MTU.

Use the undo mtu command to restore the default tunnel interface MTU.

The default value varies with devices.

Examples

# Set the tunnel interface MTU to 10,000 bytes.

<Sysname> system-view

[Sysname] interface tunnel 4/0/6

[Sysname-Tunnel4/0/6] mtu 10000

1.1.12  source

Syntax

source { ip-address | ipv6-address | interface-type interface-num }

undo source

View

Tunnel interface view

Default Level

2: System level

Parameters

ip-address: Source IPv4 address of a tunnel interface.

ip-address: Source IPv6 address of a tunnel interface.

interface-type interface-number: Type and number of a tunnel interface.

Description

Use the source command to specify the tunnel source address on the interface.

Use the undo source command to remove the configured tunnel source address.

By default, no tunnel source address is configured on the interface.

Note that:

l           The source address of the tunnel interface is the address of the sending interface and is usually the destination address set on the peer tunnel interface.

l           Two or more tunnel interfaces using the same encapsulation protocol must have different source addresses and destination addresses.

l           Interfaces of different tunnels on a device (such as manual IPv6 tunnel, IPv4-compatible IPv6 automatic tunnel, 6to4 tunnel, and ISATAP tunnel) must have different source addresses.

l           At present, the S9500 series switches do not support configuring an IPv6 address as the source of a tunnel interface.

Related commands: interface tunnel, destination.

Examples

# Set the tunnel source address to 192.100.1.1 on the interface Tunnel 5/0/0.

<Sysname> system-view

[Sysname] interface Tunnel 5/0/0

[Sysname-Tunnel5/0/0] source 192.100.1.1

1.1.13  tunnel-protocol

Syntax

tunnel-protocol { gre | ipv4-ipv4 | ipv6-ipv4 [ 6to4 | auto-tunnel | isatap ] | mpls te }

undo tunnel-protocol

View

Tunnel interface view

Default Level

2: System level

Parameters

gre: Sets the tunnel to a GRE tunnel.

ipv4-ipv4: Sets the tunnel to an IPv4 over IPv4 tunnel.

ipv6-ipv4: Sets the tunnel to an IPv6 over IPv4 tunnel.

ipv6-ipv4 6to4: Sets the tunnel to IPv6 over IPv4 6to4 tunnel.

ipv6-ipv4 auto-tunnel: Sets the tunnel to an automatic IPv4 compatible IPv6 tunnel.

ipv6-ipv4 isatap: Sets the tunnel to an IPv6 over IPv4 ISATAP tunnel.

mpls te: Sets the tunnel to an MPLS TE tunnel.

Description

Use the tunnel-protocol command to configure the tunnel type.

Use the undo tunnel-protocol to restore the tunnel type to the default.

By default, the tunnel is GRE tunnel.

Note that:

l           A proper tunnel type can be selected for packet encapsulation according to the network topology and application. The same tunnel type must be configured at both ends of the tunnel. Otherwise, packet delivery will fail.

l           Only one automatic tunnel can be configured at the same tunnel source.

l           To change a 6to4 tunnel into another tunnel type, you need to remove the 6to4 relay static route first (if any).

For details about MPLS TE tunnel, refer to MPLS TE Configuration in MPLS Volume.

Examples

# Specify the tunnel type as IPv4 over IPv4 for a tunnel interface.

<Sysname> system-view

[Sysname] interface Tunnel 3/0/0

[Sysname-Tunnel3/0/0] tunnel-protocol ipv4-ipv4