Configuring tunneling· 1

Overview·· 1

IPv6 over IPv4 tunneling· 1

IPv4 over IPv4 tunneling· 3

IPv4 over IPv6 tunneling· 4

IPv6 over IPv6 tunneling· 5

Protocols and standards 5

Tunneling configuration task list 6

Configuring a tunnel interface· 6

Configuring an IPv6 over IPv4 manual tunnel 8

Configuration example· 9

Configuring a 6to4 tunnel 11

Configuration example· 12

Configuring an ISATAP tunnel 14

Configuration example· 15

Configuring an IPv4 over IPv4 tunnel 17

Configuration example· 18

Configuring an IPv4 over IPv6 tunnel 20

Configuration example· 21

Configuring an IPv6 over IPv6 tunnel 23

Configuration example· 24

Displaying and maintaining tunneling configuration· 26

Troubleshooting tunneling· 26

Symptom·· 26

Analysis 26

Solution· 27

 

Overview

Tunneling is an encapsulation technology. One network protocol encapsulates packets of another network protocol and transfers them over a virtual point-to-point connection. The virtual connection is called a tunnel. Packets are encapsulated at the tunnel source end and de-encapsulated at the tunnel destination end. Tunneling refers to the whole process from data encapsulation to data transfer to data de-encapsulation.

Tunneling supports the following technologies:

·     Transition techniques, such as IPv6 over IPv4 tunneling, to interconnect IPv4 and IPv6 networks.

·     VPN, such as IPv4 over IPv4 tunneling, IPv4/IPv6 over IPv6 tunneling, GRE, DVPN, and IPsec tunneling.

·     Traffic engineering, such as MPLS TE to prevent network congestion.

Unless otherwise specified, the term "tunnel" in this document refers to IPv6 over IPv4, IPv4 over IPv4, IPv4 over IPv6, and IPv6 over IPv6 tunnels.

IPv6 over IPv4 tunneling

Implementation

IPv6 over IPv4 tunneling enables isolated IPv6 networks to communicate, as shown in Figure 1.

 

NOTE: The devices at the ends of an IPv6 over IPv4 tunnel must support the IPv4/IPv6 dual stack.

 

Figure 1 IPv6 over IPv4 tunnel

 

The IPv6 over IPv4 tunnel processes packets by using the following steps:

1.     A host in the IPv6 network sends an IPv6 packet to Device A at the tunnel source.

a.     Searches the routing table to identify the outgoing interface for the IPv6 packet.

The outgoing interface is the tunnel interface, so Device A knows that the packet needs to be forwarded through the tunnel.

b.     Encapsulates the IPv6 packet with an IPv4 header and forwards it through the physical interface of the tunnel.

In the IPv4 header, the source IPv4 address is the IPv4 address of the tunnel source, and the destination IPv4 address is the IPv4 address of the tunnel destination.

2.     Upon receiving the packet, Device B de-encapsulates the packet.

3.     If the destination address of the IPv6 packet is itself, Device B forwards it to the upper-layer protocol. If not, Device B forwards it according to the routing table.

Tunnel modes

IPv6 over IPv4 tunnels include manually configured tunnels and automatic tunnels, depending on how the IPv4 address of the tunnel destination is acquired.

·     Manually configured tunnel—The destination IPv4 address of the tunnel cannot be automatically acquired from the destination IPv6 address of an IPv6 packet at the tunnel source. It must be manually configured.

·     Automatic tunnel—The destination IPv4 address of the tunnel can be automatically acquired from the destination IPv6 address (with an IPv4 address embedded) of an IPv6 packet at the tunnel source.

According to the way an IPv6 packet is encapsulated, IPv6 over IPv4 tunnels are divided into the following modes.

Table 1 IPv6 over IPv4 tunnel modes and key parameters

Tunnel type	Tunnel mode	Tunnel source/destination address	Destination IPv6 address format
Manually configured tunnel	IPv6 over IPv4 manual tunneling	The source and destination IPv4 addresses are manually configured.	Ordinary IPv6 address
Automatic tunnel	6to4 tunneling	The source IPv4 address is manually configured. The destination IPv4 address is automatically obtained.	6to4 address, in the format of 2002:IPv4-destination-address::/48, where the IPv4-destination-address is the IPv4 address of the tunnel destination.
	ISATAP tunneling	The source IPv4 address is manually configured. The destination IPv4 address is automatically obtained.	ISATAP address, in the format of Prefix:0:5EFE:IPv4-destination-address/64 where the IPv4-destination-address is the IPv4 address of the tunnel destination.

 

·     IPv6 over IPv4 manual tunneling—A point-to-point link and its source and destination IPv4 addresses are manually configured. This type of tunneling provides the following solutions:

¡     Connect isolated IPv6 networks over an IPv4 network.

¡     Connect an IPv6 network to an IPv4/IPv6 dual-stack host over an IPv4 network.

·     6to4 tunneling—A point-to-multipoint automatic tunnel. It is used to connect multiple isolated IPv6 networks over an IPv4 network. The destination IPv4 address of a 6to4 tunnel is embedded in the destination 6to4 address of packets. This mechanism enables the device to automatically obtain the tunnel destination address, simplifying tunnel establishment.

The 6to4 address format is 2002:abcd:efgh:subnet number::interface ID/48. 2002 is the fixed IPv6 address prefix, and abcd:efgh represents a 32-bit globally unique IPv4 address in hexadecimal notation. For example, 1.1.1.1 can be represented by 0101:0101. The IPv4 address identifies a 6to4 network (an IPv6 network where all hosts use 6to4 addresses). The border router of a 6to4 network must have the IPv4 address abcd:efgh configured on the interface connected to the IPv4 network. The subnet number identifies a subnet in the 6to4 network. The subnet number::interface ID uniquely identifies a host in the 6to4 network.

·     ISATAP tunneling—An ISATAP tunnel is a point-to-multipoint automatic tunnel. It provides a solution to connect an IPv6 host to an IPv6 network over an IPv4 network.

The destination addresses of IPv6 packets are all ISATAP addresses. The ISATAP address format is prefix:0:5EFE:abcd:efgh. The 64-bit prefix is a valid IPv6 unicast address prefix. The abcd:efgh/64 segments represent a 32-bit IPv4 address, which identifies the tunnel destination but does not require global uniqueness.

ISATAP tunnels are mainly used for communication between IPv6 routers or between an IPv6 host and an IPv6 router over an IPv4 network.

Figure 2 Principle of ISATAP tunneling

 

IPv4 over IPv4 tunneling

IPv4 over IPv4 tunneling (RFC 1853) enables isolated IPv4 networks to communicate. For example, an IPv4 over IPv4 tunnel can connect isolated private IPv4 networks over a public IPv4 network.

Figure 3 IPv4 over IPv4 tunnel

 

Packets traveling through a tunnel undergo encapsulation and de-encapsulation, as shown in Figure 3.

·     Encapsulation:

a.     Device A receives an IP packet from an IPv4 host and submits it to the IP protocol stack.

b.     The IPv4 protocol stack determines how to forward the packet according to the destination address in the IP header. If the packet is destined for the IPv4 host connected to Device B, Device A delivers the packet to the tunnel interface.

c.     The tunnel interface adds a new IPv4 header to the IPv4 packet and submits it to the IP protocol stack. In the new header, the source IP address specifies the tunnel source, and the destination IP address specifies the tunnel destination. The IP protocol stack uses the destination IP address of the new IP header to look up the routing table, and then sends the packet out.

·     De-encapsulation:

a.     After receiving the packet, Device B delivers it to the IP protocol stack.

b.     If the protocol number is 4 (indicating an IPv4 packet is encapsulated within the packet), the IP protocol stack delivers the packet to the tunnel module for de-encapsulation.

c.     The tunnel module de-encapsulates the IP packet and sends it back to the IP protocol stack.

d.     The protocol stack forwards the de-encapsulated packet.

IPv4 over IPv6 tunneling

IPv4 over IPv6 tunneling adds an IPv6 header to IPv4 packets so that IPv4 packets can pass an IPv6 network through a tunnel to realize interworking between isolated IPv4 networks.

Figure 4 IPv4 over IPv6 tunnel

 

Packets traveling through a tunnel undergo encapsulation and de-encapsulation, as shown in Figure 4.

·     Encapsulation:

a.     Upon receiving an IPv4 packet, Device A delivers it to the IPv4 protocol stack.

b.     The IPv4 protocol stack uses the destination address of the packet to determine the egress interface. If the egress interface is the tunnel interface, the IPv4 protocol stack delivers the packet to the tunnel interface.

c.     The tunnel interface adds an IPv6 header to the original IPv4 packet and delivers the packet to the IPv6 protocol stack.

d.     The IPv6 protocol stack uses the destination IPv6 address of the packet to look up the routing table, and then sends it out.

·     De-encapsulation:

a.     Upon receiving the IPv6 packet from the attached IPv6 network, Device B delivers the packet to the IPv6 protocol stack to examine the protocol type encapsulated in the data portion of the packet.

b.     If the protocol type is IPv4, the IPv6 protocol stack delivers the packet to the tunneling module.

c.     The tunneling module removes the IPv6 header and delivers the remaining IPv4 packet to the IPv4 protocol stack.

d.     The IPv4 protocol stack forwards the IPv4 packet.

IPv6 over IPv6 tunneling

IPv6 over IPv6 tunneling (RFC 2473) enables isolated IPv6 networks to communicate with each other over another IPv6 network. For example, two isolated IPv6 networks that do not want to show their addresses to the Internet can use an IPv6 over IPv6 tunnel to communicate with each other.

Figure 5 Principle of IPv6 over IPv6 tunneling

 

Figure 5 shows the encapsulation and de-encapsulation processes.

·     Encapsulation:

a.     After receiving an IPv6 packet, Device A submits it to the IPv6 protocol stack.

b.     The IPv6 protocol stack uses the destination IPv6 address of the packet to find the egress interface. If the egress interface is the tunnel interface, the stack delivers it to the tunnel interface.

c.     After receiving the packet, the tunnel interface adds an IPv6 header to it and submits it to the IPv6 protocol stack.

d.     The IPv6 protocol stack forwards the packet according to its destination IPv6 address.

·     De-encapsulation:

a.     Upon receiving the IPv6 packet, Device B delivers it to the IPv6 protocol stack.

b.     The IPv6 protocol stack checks the protocol type of the data portion encapsulated in the IPv6 packet. If the encapsulation protocol is IPv6, the stack delivers the packet to the tunnel module.

c.     The tunnel module de-encapsulates the packet and sends it back to the IPv6 protocol stack.

d.     The IPv6 protocol stack forwards the IPv6 packet.

Protocols and standards

·     RFC 1853, IP in IP Tunneling

·     RFC 2473, Generic Packet Tunneling in IPv6 Specification

·     RFC 2893, Transition Mechanisms for IPv6 Hosts and Routers

·     RFC 3056, Connection of IPv6 Domains via IPv4 Clouds

·     RFC 4214, Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)

·     RFC 6333, Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion

Tunneling configuration task list

Tasks at a glance
(Required.) Configuring a tunnel interface
Perform one of the following tasks: ·     Configuring an IPv6 over IPv4 tunnel: ¡ Configuring an IPv6 over IPv4 manual tunnel ¡ Configuring a 6to4 tunnel ¡ Configuring an ISATAP tunnel ·     Configuring an IPv4 over IPv4 tunnel ·     Configuring an IPv4 over IPv6 tunnel ·     Configuring an IPv6 over IPv6 tunnel

 

Configuring a tunnel interface

Configure a Layer 3 virtual tunnel interface on each device on a tunnel so that devices at both ends can send, identify, and process packets from the tunnel.

The switch cannot directly route a tunneled packet based on the packet's destination address. The packet is sent to a tunnel-type service loopback group, which then delivers the packet to the forwarding module for Layer 3 forwarding. Therefore, you must configure a tunnel-type service loopback group. Otherwise, the tunnel interface will fail to forward and receive packets. For information about service loopback group, see Layer 2—LAN Switching Configuration Guide.

To configure a tunnel interface:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Create a tunnel interface, specify the tunnel mode, and enter tunnel interface view.	interface tunnel number mode { gre [ ipv6 ] | ipv4-ipv4 | ipv6 | ipv6-ipv4 [ 6to4 | isatap ] | mpls-te | nve| vxlan }	By default, no tunnel interface is created. When you create a new tunnel interface, you must specify the tunnel mode. When you enter the view of an existing tunnel interface, you do not need to specify the tunnel mode. To ensure successful packet tunneling, the two ends of a tunnel must use the same tunnel mode.
3.     (Optional.) Configure a description for the interface.	description text	By default, the description of a tunnel interface is Tunnel number Interface.
4.     (Optional.) Specify an IRF member device for forwarding the traffic on the tunnel interface.	service slot slot-number	By default, no IRF member device is specified.
5.     Set the MTU of the tunnel interface.	mtu size	The default MTU is 64000 bytes.
6.     Set the expected bandwidth for the tunnel interface.	bandwidth bandwidth-value	By default, the expected bandwidth is 64 kbps. The expected bandwidth for the tunnel interface affects the link cost value. For more information, see Layer 3—IP Routing Configuration Guide.
7.     Set the ToS for tunneled packets.	tunnel tos tos-value	The default setting is the same as the ToS of the original packet.
8.     Set the TTL for tunneled packets.	tunnel ttl ttl-value	The default TTL for tunneled packets is 255.
9.     Specify the VPN instance to which the tunnel destination belongs.	tunnel vpn-instance vpn-instance-name	By default, the tunnel destination belongs to the public network. For the tunnel interface to come up, the tunnel source and destination must belong to the same VPN. To specify a VPN instance for the tunnel source, use the ip binding vpn-instance command on the tunnel source interface. For more information about the ip binding vpn-instance command, see MPLS Command Reference.
10.     (Optional.) Restore the default settings of the tunnel interface.	default	N/A
11.     (Optional.) Shut down the tunnel interface.	shutdown	By default, the tunnel interface is enabled.

 

Configuring an IPv6 over IPv4 manual tunnel

Follow these guidelines when you configure an IPv6 over IPv4 manual tunnel:

·     The tunnel destination address specified on the local device must be identical with the tunnel source address specified on the tunnel peer device.

·     Do not specify the same tunnel source and destination addresses for the tunnels in the same mode on a device.

·     To ensure correct packet forwarding, identify whether the destination IPv6 network and the IPv6 address of the local tunnel interface are on the same subnet. If they are not, configure a route reaching the destination IPv6 network through the tunnel interface. You can configure the route by using one of the following methods:

¡     Configure a static route, and specify the local tunnel interface as the egress interface or specify the IPv6 address of the peer tunnel interface as the next hop.

¡     Enable a dynamic routing protocol on both tunnel interfaces to achieve the same purpose.

For more information about route configuration, see Layer 3—IP Routing Configuration Guide.

To configure an IPv6 over IPv4 manual tunnel:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Enter IPv6 over IPv4 manual tunnel interface view.	interface tunnel number [ mode ipv6-ipv4 ]	N/A
3.     Specify an IPv6 address for the tunnel interface.	See "Configuring basic IPv6 settings."	By default, no IPv6 address is configured for the tunnel interface.
4.     Configure a source address or source interface for the tunnel interface.	source { ip-address | interface-type interface-number }	By default, no source address or source interface is configured for the tunnel interface. The specified source address or the primary IP address of the specified source interface is used as the source IP address of tunneled packets.
5.     Configure a destination address for the tunnel interface.	destination ip-address	By default, no destination address is configured for the tunnel interface. The tunnel destination address must be the IP address of the receiving interface on the tunnel peer. It is used as the destination IP address of tunneled packets.
6.     (Optional.) Set the DF bit for tunneled packets.	tunnel dfbit enable	By default, the DF bit is not set for tunneled packets.
7.     Return to system view.	quit	N/A
8.     (Optional.) Enable dropping of IPv6 packets using IPv4-compatible IPv6 addresses.	tunnel discard ipv4-compatible-packet	By default, this feature is disabled.

 

Configuration example

Network requirements

As shown in Figure 6, configure an IPv6 over IPv4 tunnel between Switch A and Switch B so the two IPv6 networks can reach each other over the IPv4 network. Because the tunnel destination IPv4 address cannot be automatically obtained from the destination IPv6 addresses of packets, configure an IPv6 over IPv4 manual tunnel.

Figure 6 Network diagram

 

Configuration procedure

Make sure Switch A and Switch B have the corresponding VLAN interfaces created and can reach each other through IPv4.

1.     Configure Switch A:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchA> system-view

[SwitchA] interface vlan-interface 100

[SwitchA-Vlan-interface100] ip address 192.168.100.1 255.255.255.0

[SwitchA-Vlan-interface100] quit

# Specify an IPv6 address for VLAN-interface 101.

[SwitchA] interface vlan-interface 101

[SwitchA-Vlan-interface101] ipv6 address 3002::1 64

[SwitchA-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchA] service-loopback group 1 type tunnel

# Add FortyGigE 1/1/3 to service loopback group 1.

[SwitchA] interface FortyGigE 1/1/3

[SwitchA-FortyGigE1/1/3] port service-loopback group 1

[SwitchA-FortyGigE1/1/3] quit

# Configure an IPv6 over IPv4 manual tunnel interface tunnel 0.

[SwitchA] interface tunnel 0 mode ipv6-ipv4

# Specify an IPv6 address for the tunnel interface.

[SwitchA-Tunnel0] ipv6 address 3001::1/64

# Specify VLAN-interface 100 as the source interface of the tunnel interface.

[SwitchA-Tunnel0] source vlan-interface 100

# Specify the destination address for the tunnel interface as the IP address of the VLAN-interface 100 on Switch B.

[SwitchA-Tunnel0] destination 192.168.50.1

[SwitchA-Tunnel0] quit

# Configure a static route destined for IPv6 network 2 through Tunnel 0.

[SwitchA] ipv6 route-static 3003:: 64 tunnel 0

2.     Configure Switch B:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchB> system-view

[SwitchB] interface vlan-interface 100

[SwitchB-Vlan-interface100] ip address 192.168.50.1 255.255.255.0

[SwitchB-Vlan-interface100] quit

# Specify an IPv6 address for VLAN-interface 101.

[SwitchB] interface vlan-interface 101

[SwitchB-Vlan-interface101] ipv6 address 3003::1 64

[SwitchB-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchB] service-loopback group 1 type tunnel

# Add FortyGigE 1/1/3 to service loopback group 1.

[SwitchB] interface FortyGigE 1/1/3

[SwitchB-FortyGigE1/1/3] port service-loopback group 1

[SwitchB-FortyGigE1/1/3] quit

# Configure an IPv6 over IPv4 manual tunnel interface tunnel 0.

[SwitchB] interface tunnel 0 mode ipv6-ipv4

# Specify an IPv6 address for the tunnel interface.

[SwitchB-Tunnel0] ipv6 address 3001::2/64

# Specify VLAN-interface 100 as the source interface of the tunnel interface.

[SwitchB-Tunnel0] source vlan-interface 100

# Specify the destination address for the tunnel interface as the IP address of VLAN-interface 100 of Switch A.

[SwitchB-Tunnel0] destination 192.168.100.1

[SwitchB-Tunnel0] quit

# Configure a static route destined for IPv6 network 1 through Tunnel 0.

[SwitchB] ipv6 route-static 3002:: 64 tunnel 0

Verifying the configuration

# Use the display ipv6 interface command to display tunnel interface status on Switch A and Switch B. Verify that the interface Tunnel 0 is up. (Details not shown.)

# Verify that Switch B and Switch A can ping the IPv6 address of VLAN-interface 101 of each other. The following shows the output on Switch A.

[SwitchA] ping ipv6 3003::1

Ping6(56 data bytes) 3001::1 --> 3003::1, press CTRL_C to break

56 bytes from 3003::1, icmp_seq=0 hlim=64 time=45.000 ms

56 bytes from 3003::1, icmp_seq=1 hlim=64 time=10.000 ms

56 bytes from 3003::1, icmp_seq=2 hlim=64 time=4.000 ms

56 bytes from 3003::1, icmp_seq=3 hlim=64 time=10.000 ms

56 bytes from 3003::1, icmp_seq=4 hlim=64 time=11.000 ms

 

--- Ping6 statistics for 3003::1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 4.000/16.000/45.000/14.711 ms

Configuring a 6to4 tunnel

Follow these guidelines when you configure a 6to4 tunnel:

·     You do not need to configure a destination address for a 6to4 tunnel, because the destination IPv4 address is embedded in the 6to4 IPv6 address.

·     The source addresses of local tunnels of the same tunnel mode cannot be the same.

·     Automatic tunnels do not support dynamic routing. You must configure a static route destined for the destination IPv6 network if the destination IPv6 network is not in the same subnet as the IPv6 address of the tunnel interface. You can specify the local tunnel interface as the egress interface of the route or specify the IPv6 address of the peer tunnel interface as the next hop of the route. For more information about route configuration, see Layer 3—IP Routing Configuration Guide.

To configure a 6to4 tunnel:

 

Step		Command	Remarks
1.     Enter system view.		system-view	N/A
2.     Enter 6to4 tunnel interface view.		interface tunnel number [ mode ipv6-ipv4 6to4 ]	N/A
3.     Specify an IPv6 address for the tunnel interface.		See "Configuring basic IPv6 settings."	By default, no IPv6 address is configured for the tunnel interface.
4.     Configure a source address or source interface for the tunnel interface.		source { ip-address | interface-type interface-number }	By default, no source address or source interface is configured for the tunnel interface. The specified source address or the primary IP address of the specified source interface is used as the source IP address of tunneled packets.
5.     (Optional.) Set the DF bit for tunneled packets.		tunnel dfbit enable	By default, the DF bit is not set for tunneled packets.
6.     Return to system view.	quit		N/A
7.     (Optional.) Enable dropping of IPv6 packets using IPv4-compatible IPv6 addresses.	tunnel discard ipv4-compatible-packet		By default, this feature is disabled.

 

Configuration example

Network requirements

As shown in Figure 7, configure a 6to4 tunnel between 6to4 switches Switch A and Switch B so Host A and Host B can reach each other over the IPv4 network.

Figure 7 Network diagram

 

Requirements analysis

To enable communication between 6to4 networks, configure 6to4 addresses for 6to4 switches and hosts in the 6to4 networks.

·     The IPv4 address of VLAN-interface 100 on Switch A is 2.1.1.1/24, and the corresponding 6to4 prefix is 2002:0201:0101::/48. Host A must use this prefix.

·     The IPv4 address of VLAN-interface 100 on Switch B is 5.1.1.1/24, and the corresponding 6to4 prefix is 2002:0501:0101::/48. Host B must use this prefix.

Configuration procedure

Make sure Switch A and Switch B have the corresponding VLAN interfaces created and can reach each other through IPv4.

1.     Configure Switch A:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchA> system-view

[SwitchA] interface vlan-interface 100

[SwitchA-Vlan-interface100] ip address 2.1.1.1 24

[SwitchA-Vlan-interface100] quit

# Specify a 6to4 address for VLAN-interface 101.

[SwitchA] interface vlan-interface 101

[SwitchA-Vlan-interface101] ipv6 address 2002:0201:0101:1::1/64

[SwitchA-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchA] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchA] interface FortyGigE 1/1/3

[SwitchA-FortyGigE1/1/3] port service-loopback group 1

[SwitchA-FortyGigE1/1/3] quit

# Create a 6to4 tunnel interface tunnel 0.

[SwitchA] interface tunnel 0 mode ipv6-ipv4 6to4

# Specify an IPv6 address for the tunnel interface.

[SwitchA-Tunnel0] ipv6 address 3001::1/64

# Specify the source interface as VLAN-interface 100 for the tunnel interface.

[SwitchA-Tunnel0] source vlan-interface 100

[SwitchA-Tunnel0] quit

# Configure a static route destined for 2002::/16 through the tunnel interface.

[SwitchA] ipv6 route-static 2002:: 16 tunnel 0

2.     Configure Switch B:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchB> system-view

[SwitchB] interface vlan-interface 100

[SwitchB-Vlan-interface100] ip address 5.1.1.1 24

[SwitchB-Vlan-interface100] quit

# Specify a 6to4 address for VLAN-interface 101.

[SwitchB] interface vlan-interface 101

[SwitchB-Vlan-interface101] ipv6 address 2002:0501:0101:1::1/64

[SwitchB-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchB] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchB] interface FortyGigE 1/1/3

[SwitchB-FortyGigE1/1/3] port service-loopback group 1

[SwitchB-FortyGigE1/1/3] quit

# Create a 6to4 tunnel interface tunnel 0.

[SwitchB] interface tunnel 0 mode ipv6-ipv4 6to4

# Specify an IPv6 address for the tunnel interface.

[SwitchB-Tunnel0] ipv6 address 3002::1/64

# Specify the source interface as VLAN-interface 100 for the tunnel interface.

[SwitchB-Tunnel0] source vlan-interface 100

[SwitchB-Tunnel0] quit

# Configure a static route destined for 2002::/16 through the tunnel interface.

[SwitchB] ipv6 route-static 2002:: 16 tunnel 0

Verifying the configuration

# Verify that Host A and Host B can ping each other.

D:\>ping6 -s 2002:201:101:1::2 2002:501:101:1::2

 

Pinging 2002:501:101:1::2

from 2002:201:101:1::2 with 32 bytes of data:

 

Reply from 2002:501:101:1::2: bytes=32 time=13ms

Reply from 2002:501:101:1::2: bytes=32 time=1ms

Reply from 2002:501:101:1::2: bytes=32 time=1ms

Reply from 2002:501:101:1::2: bytes=32 time<1ms

 

Ping statistics for 2002:501:101:1::2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 13ms, Average = 3ms

Configuring an ISATAP tunnel

Follow these guidelines when you configure an ISATAP tunnel:

·     You do not need to configure a destination address for an ISATAP tunnel, because the destination IPv4 address is embedded in the ISATAP address.

·     Because automatic tunnels do not support dynamic routing, configure a static route destined for the destination IPv6 network at each tunnel end. You can specify the local tunnel interface as the egress interface of the route or specify the IPv6 address of the peer tunnel interface as the next hop of the route. For more information about route configuration, see Layer 3—IP Routing Configuration Guide.

·     The source addresses of local tunnels of the same tunnel mode cannot be the same.

To configure an ISATAP tunnel:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Enter ISATAP tunnel interface view.	interface tunnel number [ mode ipv6-ipv4 isatap ]	N/A
3.     Specify an IPv6 address for the tunnel interface.	See "Configuring basic IPv6 settings."	By default, no IPv6 address is configured for the tunnel interface.
4.     Configure a source address or source interface for the tunnel interface.	source { ip-address | interface-type interface-number }	By default, no source address or source interface is configured for the tunnel interface. The specified source address or the primary IP address of the specified source interface is used as the source IP address of tunneled packets.
5.     (Optional.) Set the DF bit for tunneled packets.	tunnel dfbit enable	By default, the DF bit is not set for tunneled packets.
6.     Return to system view.	quit	N/A
7.     (Optional.) Enable dropping of IPv6 packets using IPv4-compatible IPv6 addresses.	tunnel discard ipv4-compatible-packet	By default, this feature is disabled.

 

Configuration example

Network requirements

As shown in Figure 8, configure an ISATAP tunnel between the switch and the ISATAP host so the ISATAP host in the IPv4 network can access the IPv6 network.

Figure 8 Network diagram

 

Configuration procedure

1.     Configure the switch:

# Specify an IPv6 address for VLAN-interface 100.

<Switch> system-view

[Switch] interface vlan-interface 100

[Switch-Vlan-interface100] ipv6 address 3001::1/64

[Switch-Vlan-interface100] quit

# Specify an IPv4 address for VLAN-interface 101.

[Switch] interface vlan-interface 101

[Switch-Vlan-interface101] ip address 1.1.1.1 255.0.0.0

[Switch-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[Switch] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[Switch] interface FortyGigE 1/1/3

[Switch-FortyGigE1/1/3] port service-loopback group 1

[Switch-FortyGigE1/1/3] quit

# Configure an ISATAP tunnel interface tunnel 0.

[Switch] interface tunnel 0 mode ipv6-ipv4 isatap

# Specify an EUI-64 IPv6 address for the tunnel interface tunnel 0.

[Switch-Tunnel0] ipv6 address 2001:: 64 eui-64

# Specify VLAN-interface 101 as the source interface of the tunnel interface.

[Switch-Tunnel0] source vlan-interface 101

# Disable RA suppression so that the ISATAP host can acquire information such as the address prefix from the RA message advertised by the ISATAP switch.

[Switch-Tunnel0] undo ipv6 nd ra halt

[Switch-Tunnel0] quit

2.     Configure the ISATAP host:

Configurations on the ISATAP host vary by operating system. The following example is performed on Windows XP.

# Install IPv6.

C:\>ipv6 install

# On a host running Windows XP, the ISATAP interface is typically interface 2. Display information about the ISATAP interface.

C:\>ipv6 if 2

Interface 2: Automatic Tunneling Pseudo-Interface

  Guid {48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}

  does not use Neighbor Discovery

  does not use Router Discovery

  routing preference 1

  EUI-64 embedded IPv4 address: 0.0.0.0

  router link-layer address: 0.0.0.0

    preferred link-local fe80::5efe:1.1.1.2, life infinite

  link MTU 1280 (true link MTU 65515)

  current hop limit 128

  reachable time 42500ms (base 30000ms)

  retransmission interval 1000ms

  DAD transmits 0

  default site prefix length 48

# Specify an IPv4 address for the ISATAP switch.

C:\>netsh interface ipv6 isatap set router 1.1.1.1

# Display information about the ISATAP interface.

C:\>ipv6 if 2

Interface 2: Automatic Tunneling Pseudo-Interface

  Guid {48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}

  does not use Neighbor Discovery

  uses Router Discovery

  routing preference 1

  EUI-64 embedded IPv4 address: 1.1.1.2

  router link-layer address: 1.1.1.1

    preferred global 2001::5efe:1.1.1.2, life 29d23h59m46s/6d23h59m46s (public)

    preferred link-local fe80::5efe:1.1.1.2, life infinite

  link MTU 1500 (true link MTU 65515)

  current hop limit 255

  reachable time 42500ms (base 30000ms)

  retransmission interval 1000ms

  DAD transmits 0

  default site prefix length 48

The host has acquired the address prefix 2001::/64 and has automatically generated the global unicast address 2001::5efe:1.1.1.2. The message "uses Router Discovery" indicates that the router discovery function is enabled on the host.

# Display information about IPv6 routes on the host.

C:\>ipv6 rt

2001::/64 -> 2 pref 1if+8=9 life 29d23h59m43s (autoconf)

::/0 -> 2/fe80::5efe:1.1.1.1 pref 1if+256=257 life 29m43s (autoconf)

3.     On the IPv6 host, configure a route to the ISATAP switch.

C:\>netsh interface ipv6 set route 2001::/64 5 3001::1

Verifying the configuration

# Verify that the ISATAP host can ping the IPv6 host.

C:\>ping 3001::2

 

Pinging 3001::2 with 32 bytes of data:

 

Reply from 3001::2: time=1ms

Reply from 3001::2: time=1ms

Reply from 3001::2: time=1ms

Reply from 3001::2: time=1ms

 

Ping statistics for 3001::2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1ms, Maximum = 1ms, Average = 1ms

Configuring an IPv4 over IPv4 tunnel

Follow these guidelines when you configure an IPv4 over IPv4 tunnel:

·     The destination address specified for the local tunnel interface must be the source address specified for the peer tunnel interface.

·     The source/destination addresses of local tunnels of the same tunnel mode cannot be the same.

·     The IPv4 address of the local tunnel interface cannot be on the same subnet as the destination address configured on the tunnel interface.

·     To ensure correct packet forwarding, identify whether the destination IPv4 network and the IPv4 address of the local tunnel interface are on the same subnet. If they are not, configure a route reaching the destination IPv4 network through the tunnel interface. You can configure the route by using one of the following methods:

¡     Configure a static route, and specify the local tunnel interface as the egress interface or specify the IPv4 address of the peer tunnel interface as the next hop.

¡     Enable a dynamic routing protocol on both tunnel interfaces to achieve the same purpose.

For more information about route configuration, see Layer 3—IP Routing Configuration Guide.

·     The destination address of the route passing the tunnel interface must not be on the same subnet as the destination address configured on the tunnel interface.

To configure an IPv4 over IPv4 tunnel:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Enter IPv4 over IPv4 tunnel interface view.	interface tunnel number [ mode ipv4-ipv4 ]	N/A
3.     Configure an IPv4 address for the tunnel interface.	ip address ip-address { mask | mask-length } [ sub ]	By default, no IPv4 address is configured for the tunnel interface.
4.     Configure a source address or source interface for the tunnel interface.	source { ip-address | interface-type interface-number }	By default, no source address or source interface is configured for the tunnel interface. The specified source address or the IPv6 address of the specified source interface is used as the source IP address of tunneled packets.
5.     Configure a destination address for the tunnel interface.	destination ip-address	By default, no destination address is configured for the tunnel interface. The tunnel destination address must be the IP address of the receiving interface on the tunnel peer. It is used as the destination IP address of tunneled packets.
6.     (Optional.) Set the DF bit for tunneled packets.	tunnel dfbit enable	By default, the DF bit is not set for tunneled packets.

 

Configuration example

Network requirements

As shown in Figure 9, the two subnets IPv4 group 1 and IPv4 group 2 use private IPv4 addresses. Configure an IPv4 over IPv4 tunnel between Switch A and Switch B so the two subnets can reach each other.

Figure 9 Network diagram

 

Configuration procedure

Make sure Switch A and Switch B have the corresponding VLAN interfaces created and can reach each other through IPv4.

1.     Configure Switch A:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchA> system-view

[SwitchA] interface vlan-interface 100

[SwitchA-Vlan-interface100] ip address 10.1.1.1 255.255.255.0

[SwitchA-Vlan-interface100] quit

# Specify an IPv4 address for VLAN-interface 101, which is the physical interface of the tunnel.

[SwitchA] interface vlan-interface 101

[SwitchA-Vlan-interface101] ip address 2.1.1.1 255.255.255.0

[SwitchA-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchA] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchA] interface FortyGigE 1/1/3

[SwitchA-FortyGigE1/1/3] port service-loopback group 1

[SwitchA-FortyGigE1/1/3] quit

# Create an IPv4 over IPv4 tunnel interface tunnel 1.

[SwitchA] interface tunnel 1 mode ipv4-ipv4

# Specify an IPv4 address for the tunnel interface.

[SwitchA-Tunnel1] ip address 10.1.2.1 255.255.255.0

# Specify the IP address of VLAN-interface 101 as the source address for the tunnel interface.

[SwitchA-Tunnel1] source 2.1.1.1

# Specify the IP address of VLAN-interface 101 on Switch B as the destination address for the tunnel interface.

[SwitchA-Tunnel1] destination 3.1.1.1

[SwitchA-Tunnel1] quit

# Configure a static route destined for the IPv4 group 2 through the tunnel interface.

[SwitchA] ip route-static 10.1.3.0 255.255.255.0 tunnel 1

2.     Configure Switch B:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchB> system-view

[SwitchB] interface vlan-interface 100

[SwitchB-Vlan-interface100] ip address 10.1.3.1 255.255.255.0

[SwitchB-Vlan-interface100] quit

# Specify an IPv4 address for VLAN-interface 101, which is the physical interface of the tunnel.

[SwitchB] interface vlan-interface 101

[SwitchB-Vlan-interface101] ip address 3.1.1.1 255.255.255.0

[SwitchB-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchB] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchB] interface FortyGigE 1/1/3

[SwitchB-FortyGigE1/1/3] port service-loopback group 1

[SwitchB-FortyGigE1/1/3] quit

# Create an IPv4 over IPv4 tunnel interface tunnel 2.

[SwitchB] interface tunnel 2 mode ipv4-ipv4

# Specify an IPv4 address for the tunnel interface.

[SwitchB-Tunnel2] ip address 10.1.2.2 255.255.255.0

# Specify the IP address of VLAN-interface 101 as the source address for the tunnel interface.

[SwitchB-Tunnel2] source 3.1.1.1

# Specify the IP address of VLAN-interface 101 on Switch A as the destination address for the tunnel interface.

[SwitchB-Tunnel2] destination 2.1.1.1

[SwitchB-Tunnel2] quit

# Configure a static route destined for the IPv4 group 1 through the tunnel interface.

[SwitchB] ip route-static 10.1.1.0 255.255.255.0 tunnel 2

Verifying the configuration

# Use the display interface tunnel command to display the status of the tunnel interfaces on Switch A and Switch B. Verify that the tunnel interfaces are up. (Details not shown.)

# Verify that Switch A and Switch B can ping the IPv4 address of the peer interface VLAN-interface 100. The following shows the output on Switch A.

[SwitchA] ping -a 10.1.1.1 10.1.3.1

Ping 10.1.3.1 (10.1.3.1) from 10.1.1.1: 56 data bytes, press CTRL_C to break

56 bytes from 10.1.3.1: icmp_seq=0 ttl=255 time=2.000 ms

56 bytes from 10.1.3.1: icmp_seq=1 ttl=255 time=1.000 ms

56 bytes from 10.1.3.1: icmp_seq=2 ttl=255 time=0.000 ms

56 bytes from 10.1.3.1: icmp_seq=3 ttl=255 time=1.000 ms

56 bytes from 10.1.3.1: icmp_seq=4 ttl=255 time=1.000 ms

 

--- Ping statistics for 10.1.3.1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/1.000/2.000/0.632 ms

Configuring an IPv4 over IPv6 tunnel

Follow these guidelines when you configure an IPv4 over IPv6 tunnel:

·     The destination address specified for the local tunnel interface must be the source address specified for the peer tunnel interface.

·     The source/destination addresses of local tunnels of the same tunnel mode cannot be the same.

·     To ensure correct packet forwarding, identify whether the destination IPv4 network and the IPv4 address of the local tunnel interface are on the same subnet. If they are not, configure a route reaching the destination IPv4 network through the tunnel interface. You can configure the route by using one of the following methods:

¡     Configure a static route, and specify the local tunnel interface as the egress interface or specify the IPv6 address of the peer tunnel interface as the next hop.

¡     Enable a dynamic routing protocol on both tunnel interfaces to achieve the same purpose.

For more information about route configuration, see Layer 3—IP Routing Configuration Guide.

To configure an IPv4 over IPv6 tunnel:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Enter tunnel interface view.	interface tunnel number [ mode ipv6 ]	N/A
3.     Configure an IPv4 address for the tunnel interface.	ip address ip-address { mask | mask-length } [ sub ]	By default, no IPv4 address is configured for the tunnel interface.
4.     Configure the source address or interface for the tunnel interface.	source { ipv6-address | interface-type interface-number }	By default, no source address or interface is configured for the tunnel. The specified source address or the primary IPv6 address of the specified source interface is used as the source IPv6 address of tunneled packets.
5.     Configure the destination address for the tunnel interface.	destination ipv6-address	By default, no destination address is configured for the tunnel. The tunnel destination address must be the IPv6 address of the receiving interface on the tunnel peer. It is used as the destination IPv6 address of tunneled packets.

 

Configuration example

Network requirements

As shown in Figure 10, configure an IPv4 over IPv6 tunnel between Switch A and Switch B so the two IPv4 networks can reach each other over the IPv6 network.

Figure 10 Network diagram

 

Configuration procedure

Make sure Switch A and Switch B have the corresponding VLAN interfaces created and can reach each other through IPv6.

1.     Configure Switch A:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchA> system-view

[SwitchA] interface vlan-interface 100

[SwitchA-Vlan-interface100] ip address 30.1.1.1 255.255.255.0

[SwitchA-Vlan-interface100] quit

# Specify an IPv6 address for VLAN-interface 101, which is the physical interface of the tunnel.

[SwitchA] interface vlan-interface 101

[SwitchA-Vlan-interface101] ipv6 address 2001::1:1 64

[SwitchA-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchA] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchA] interface FortyGigE 1/1/3

[SwitchA-FortyGigE1/1/3] port service-loopback group 1

[SwitchA-FortyGigE1/1/3] quit

# Create an IPv6 tunnel interface tunnel 1.

[SwitchA] interface tunnel 1 mode ipv6

# Specify an IPv4 address for the tunnel interface.

[SwitchA-Tunnel1] ip address 30.1.2.1 255.255.255.0

# Specify the IP address of VLAN-interface 101 as the source address for the tunnel interface.

[SwitchA-Tunnel1] source 2001::1:1

# Specify the IP address of VLAN-interface 101 on Switch B as the destination address for the tunnel interface.

[SwitchA-Tunnel1] destination 2002::2:1

[SwitchA-Tunnel1] quit

# Configure a static route destined for IPv4 network 2 through the tunnel interface.

[SwitchA] ip route-static 30.1.3.0 255.255.255.0 tunnel 1

2.     Configure Switch B:

# Specify an IPv4 address for VLAN-interface 100.

<SwitchB> system-view

[SwitchB] interface vlan-interface 100

[SwitchB-Vlan-interface100] ip address 30.1.3.1 255.255.255.0

[SwitchB-Vlan-interface100] quit

# Specify an IPv6 address for VLAN-interface 101, which is the physical interface of the tunnel.

[SwitchB] interface vlan-interface 101

[SwitchB-Vlan-interface101] ipv6 address 2002::2:1 64

[SwitchB-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchB] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchB] interface FortyGigE 1/1/3

[SwitchB-FortyGigE1/1/3] port service-loopback group 1

[SwitchB-FortyGigE1/1/3] quit

# Create an IPv6 tunnel interface tunnel 2.

[SwitchB] interface tunnel 2 mode ipv6

# Specify an IPv4 address for the tunnel interface.

[SwitchB-Tunnel2] ip address 30.1.2.2 255.255.255.0

# Specify the IP address of VLAN-interface 101 as the source address for the tunnel interface.

[SwitchB-Tunnel2] source 2002::2:1

# Specify the IP address of VLAN-interface 101 on Switch A as the destination address for the tunnel interface.

[SwitchB-Tunnel2] destination 2001::1:1

[SwitchB-Tunnel2] quit

# Configure a static route destined for IPv4 network 1 through the tunnel interface.

[SwitchB] ip route-static 30.1.1.0 255.255.255.0 tunnel 2

Verifying the configuration

# Use the display interface tunnel command to display the status of the tunnel interfaces on Switch A and Switch B. Verify that the tunnel interfaces are up. (Details not shown.)

# Verify that Switch A and Switch B can ping the IPv4 address of the peer interface. The following shows the output on Switch A.

[SwitchA] ping -a 30.1.1.1 30.1.3.1

Ping 30.1.3.1 (30.1.3.1) from 30.1.1.1: 56 data bytes, press CTRL_C to break

56 bytes from 30.1.3.1: icmp_seq=0 ttl=255 time=3.000 ms

56 bytes from 30.1.3.1: icmp_seq=1 ttl=255 time=1.000 ms

56 bytes from 30.1.3.1: icmp_seq=2 ttl=255 time=0.000 ms

56 bytes from 30.1.3.1: icmp_seq=3 ttl=255 time=1.000 ms

56 bytes from 30.1.3.1: icmp_seq=4 ttl=255 time=1.000 ms

 

--- Ping statistics for 30.1.3.1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/1.200/3.000/0.980 ms

Configuring an IPv6 over IPv6 tunnel

Follow these guidelines when you configure an IPv6 over IPv6 tunnel:

·     The destination address specified for the local tunnel interface must be the source address specified for the peer tunnel interface.

·     The source/destination addresses of local tunnels of the same tunnel mode cannot be the same.

·     The IPv6 address of the tunnel interface must not be on the same subnet as the destination address configured for the tunnel interface.

·     To ensure correct packet forwarding, identify whether the destination IPv6 network and the IPv6 address of the local tunnel interface are on the same subnet. If they are not, configure a route reaching the destination IPv6 network through the tunnel interface. You can configure the route by using one of the following methods:

¡     Configure a static route, and specify the local tunnel interface as the egress interface or specify the IPv6 address of the peer tunnel interface as the next hop.

¡     Enable a dynamic routing protocol on both tunnel interfaces to achieve the same purpose.

For more information about route configuration, see Layer 3—IP Routing Configuration Guide.

·     The destination address of the route passing the tunnel interface must not be on the same subnet as the destination address configured for the tunnel interface.

To configure an IPv6 over IPv6 tunnel:

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Enter IPv6 tunnel interface view.	interface tunnel number [ mode ipv6 ]	N/A
3.     Configure an IPv6 address for the tunnel interface.	See "Configuring basic IPv6 settings."	By default, no IPv6 address is configured for the tunnel interface.
4.     Configure the source address or source interface for the tunnel interface.	source { ipv6-address | interface-type interface-number }	By default, no source address or interface is configured for the tunnel. The specified source address or the IPv6 address of the specified source interface is used as the source IPv6 address of tunneled packets.
5.     Configure the destination address for the tunnel interface.	destination ipv6-address	By default, no destination address is configured for the tunnel. The tunnel destination address must be the IPv6 address of the receiving interface on the tunnel peer. It is used as the destination IPv6 address of tunneled packets.
6.     Return to system view.	quit	N/A
7.     (Optional.) Enable dropping of IPv6 packets using IPv4-compatible IPv6 addresses.	tunnel discard ipv4-compatible-packet	By default, this feature is disabled.

 

Configuration example

Network requirements

As shown in Figure 11, configure an IPv6 over IPv6 tunnel between Switch A and Switch B so the two IPv6 groups can reach each other without disclosing their IPv6 addresses.

Figure 11 Network diagram

 

Configuration procedure

Make sure Switch A and Switch B have the corresponding VLAN interfaces created and can reach each other through IPv6.

1.     Configure Switch A:

# Specify an IPv6 address for VLAN-interface 100.

<SwitchA> system-view

[SwitchA] interface vlan-interface 100

[SwitchA-Vlan-interface100] ipv6 address 2002:1::1 64

[SwitchA-Vlan-interface100] quit

# Specify an IPv6 address for VLAN-interface 101, which is the physical interface of the tunnel.

[SwitchA] interface vlan-interface 101

[SwitchA-Vlan-interface101] ipv6 address 2001::11:1 64

[SwitchA-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchA] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchA] interface FortyGigE 1/1/3

[SwitchA-FortyGigE1/1/3] port service-loopback group 1

[SwitchA-FortyGigE1/1/3] quit

# Create an IPv6 tunnel interface tunnel 1.

[SwitchA] interface tunnel 1

# Specify an IPv6 address for the tunnel interface.

[SwitchA-Tunnel1] ipv6 address 3001::1:1 64

# Specify the IP address of VLAN-interface 101 as the source address for the tunnel interface.

[SwitchA-Tunnel1] source 2001::11:1

# Specify the IP address of VLAN-interface 101 on Switch B as the destination address for the tunnel interface.

[SwitchA-Tunnel1] destination 2002::22:1

[SwitchA-Tunnel1] quit

# Configure a static route destined for the IPv6 group 2 through the tunnel interface.

[SwitchA] ipv6 route-static 2002:3:: 64 tunnel 1

2.     Configure Switch B:

# Specify an IPv6 address for VLAN-interface 100.

<SwitchB> system-view

[SwitchB] interface vlan-interface 100

[SwitchB-Vlan-interface100] ipv6 address 2002:3::1 64

[SwitchB-Vlan-interface100] quit

# Specify an IPv6 address for VLAN-interface 101, which is the physical interface of the tunnel.

[SwitchB] interface vlan-interface 101

[SwitchB-Vlan-interface101] ipv6 address 2002::22:1 64

[SwitchB-Vlan-interface101] quit

# Create service loopback group 1 and specify its service type as tunnel.

[SwitchB] service-loopback group 1 type tunnel

# Assign FortyGigE 1/1/3 to service loopback group 1.

[SwitchB] interface FortyGigE 1/1/3

[SwitchB-FortyGigE1/1/3] port service-loopback group 1

[SwitchB-FortyGigE1/1/3] quit

# Create an IPv6 tunnel interface tunnel 2.

[SwitchB] interface tunnel 2 mode ipv6

# Specify an IPv6 address for the tunnel interface.

[SwitchB-Tunnel2] ipv6 address 3001::1:2 64

# Specify the IP address of VLAN-interface 101 as the source address for the tunnel interface.

[SwitchB-Tunnel2] source 2002::22:1

# Specify the IP address of VLAN-interface 101 on Switch A as the destination address for the tunnel interface.

[SwitchB-Tunnel2] destination 2001::11:1

[SwitchB-Tunnel2] quit

# Configure a static route destined for the IPv6 group 1 through the tunnel interface.

[SwitchB] ipv6 route-static 2002:1:: 64 tunnel 2

Verifying the configuration

# Use the display ipv6 interface command to display the status of the tunnel interfaces on Switch A and Switch B. Verify that the tunnel interfaces are up. (Details not shown.)

# Verify that Switch A and Switch B can ping the IPv4 address of the peer interface. The following shows the output on Switch A.

[SwitchA] ping ipv6 -a 2002:1::1 2002:3::1

Ping6(56 data bytes) 2002:1::1 --> 2002:3::1, press CTRL_C to break

56 bytes from 2002:3::1, icmp_seq=0 hlim=64 time=9.000 ms

56 bytes from 2002:3::1, icmp_seq=1 hlim=64 time=1.000 ms

56 bytes from 2002:3::1, icmp_seq=2 hlim=64 time=0.000 ms

56 bytes from 2002:3::1, icmp_seq=3 hlim=64 time=0.000 ms

56 bytes from 2002:3::1, icmp_seq=4 hlim=64 time=0.000 ms

 

--- Ping6 statistics for 2002:3::1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/2.000/9.000/3.521 ms

Displaying and maintaining tunneling configuration

Execute display commands in any view and reset commands in user view.

 

Task	Command
Display information about tunnel interfaces.	display interface tunnel [ number [ brief [ description ] ] | brief [ description | down ] ]
Display IPv6 information on tunnel interfaces.	display ipv6 interface [ tunnel [ number ] ] [ brief ]
Clear statistics on tunnel interfaces.	reset counters interface [ tunnel [ number ] ]

 

Troubleshooting tunneling

Symptom

A tunnel interface configured with related parameters such as tunnel source address, tunnel destination address, and tunnel mode cannot come up.

Analysis

The physical interface of the tunnel does not come up, or the tunnel destination is unreachable.

Solution

1.     To resolve the problem:

¡     Use the display interface or display ipv6 interface command to check whether the physical interface of the tunnel is up. If the physical interface is down, check the network connection.

¡     Use the display ipv6 routing-table or display ip routing-table command to check whether the tunnel destination is reachable. If the route is not available, configure a route to reach the tunnel destination.

2.     If the problem persists, contact H3C Support.