Configuring An Ipv6 Over Ipv6 Tunnel; Configuration Prerequisites; Configuration Guidelines - HP 3600 v2 Series Configuration Manual

Output queue : (FIFO queuing : Size/Length/Discards)
Last clearing of counters:
Last 300 seconds input:
Last 300 seconds output:
167 packets input,
0 input error
170 packets output,
0 output error
# Ping the IPv4 address of the peer interface VLAN-interface 100 from Switch A.
[RouterA] ping 30.1.3.1
PING 30.1.3.1: 56
Reply from 30.1.3.1: bytes=56 Sequence=1 ttl=255 time=46 ms
Reply from 30.1.3.1: bytes=56 Sequence=2 ttl=255 time=15 ms
Reply from 30.1.3.1: bytes=56 Sequence=3 ttl=255 time=16 ms
Reply from 30.1.3.1: bytes=56 Sequence=4 ttl=255 time=15 ms
Reply from 30.1.3.1: bytes=56 Sequence=5 ttl=255 time=16 ms
--- 30.1.3.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 15/21/46 ms

Configuring an IPv6 over IPv6 tunnel

Configuration prerequisites

Configure IP addresses for interfaces (such as the VLAN interface, and loopback interface) on the device
to ensure normal communication. One of the interfaces will be used as the source interface of the tunnel.

Configuration guidelines

Follow these guidelines when you configure an IPv6 over IPv6 tunnel:
• Specify public addresses or interfaces as the source and destination addresses or interfaces.
To encapsulate and forward IPv6 packets whose destination address does not belong to the subnet
•
where the receiving tunnel interface resides, configure a static route or dynamic routing for
forwarding those packets through this tunnel interface. If you configure a static route to that
destination IPv6 address, specify this tunnel interface as the outbound interface, or the peer tunnel
interface address as the next hop. A similar configuration is required at the other tunnel end. If you
configure dynamic routing at both ends, enable the dynamic routing protocol on both tunnel
interfaces. For the detailed configuration, see Layer 3—IP Routing Configuration Guide.
The IPv6 address of a tunnel interface must not be on the same subnet as the destination address of
•
the tunnel.
• The destination address of a route with the tunnel interface as the egress interface must not be on
the same subnet as the destination address of the tunnel.
Two or more tunnel interfaces using the same encapsulation protocol must have different source and
•
destination addresses.
Never
1 bytes/sec, 0 packets/sec
1 bytes/sec, 0 packets/sec
10688 bytes
10880 bytes
data bytes, press CTRL_C to break
209
0/75/0