H3C MSR 2600 Series, Configuration Manual

Page: 275 / 288

260
[RouterB-Ethernet1/1] quit
# Specify an IPv4 address for Serial 2/1, which is the physical interface of the tunnel.
[RouterB] interface serial 2/1
[RouterB-Serial2/1] ip address 3.1.1.1 255.255.255.0
[RouterB-Serial2/1] quit
# Create an IPv4 over IPv4 tunnel interface tunnel 2 .
[RouterB] interface tunnel 2 mode ipv4-ipv4
# Specify an IPv4 address for the tunnel interface.
[RouterB-Tunnel2] ip address 10.1.2.2 255.255.255.0
# Specify the IP address of Serial 2/1 as the source address for the tunnel interface.
[RouterB-Tunnel2] source 3.1.1.1
# Specify the IP address of Serial 2/0 on Router A as a destination address for the tunnel interface.
[RouterB-Tunnel2] destination 2.1.1.1
[RouterB-Tunnel2] quit
# Configure a static route destined for the IP network Group 1 through the tunnel interface.
[RouterB] 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 Router A and
Router B. The output shows that the tunnel interfaces are up. (Details not shown.)
# Ping the IPv4 address of the peer interface Ethernet 1/1 from each router. The following shows the
output on Router A.
[RouterA] 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 escape sequence 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/stddev = 0.000/1.000/2.000/0.632 ms
Configuring an IPv4 over IPv6 manual tunnel
Follow these guidelines when you configure an IPv4 over IPv6 manual tunnel:
• The destination address specified for the local tunnel interface must be the source address specified
for the peer tunnel interface, and vice versa.
•
The source/destination addresses of local tunnels of the same tunnel mode cannot be the same.
•
If the destination IPv4 network is not on the same subnet as the IPv4 address of the local tunnel
interface, you must configure a route destined for the destination IPv4 network through the tunnel
interface. You can 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. Alternatively, you
can enable a dynamic routing protocol on both tunnel interfaces to achieve the same purpose. For
the detailed configuration, see Layer 3—IP Routing Configuration Guide .