Configuring An Ipv4 Over Ipv4 Tunnel - HP 5920 Series Configuration Manual

# 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: 2.1.1.2
router link-layer address: 1.1.1.1
preferred global 2001::5efe:2.1.1.2, life 29d23h59m46s/6d23h59m46s (public)
preferred link-local fe80::5efe:2.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 address
2001::5efe:2.1.1.2. The message "uses Router Discovery" indicates that the router discovery
function is enabled on the host.
Verifying the configuration
# Ping the IPv6 address of the tunnel interface of the switch. The ping operation succeeds, indicating an
ISATAP tunnel has been established.
C:\>ping 2001::5efe:1.1.1.1
Pinging 2001::5efe:1.1.1.1 with 32 bytes of data:
Reply from 2001::5efe:1.1.1.1: time=1ms
Reply from 2001::5efe:1.1.1.1: time=1ms
Reply from 2001::5efe:1.1.1.1: time=1ms
Reply from 2001::5efe:1.1.1.1: time=1ms
Ping statistics for 2001::5efe:1.1.1.1:
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, and vice versa.
Two or more local tunnel interfaces using the same encapsulation protocol must have different
•
source and destination addresses.
The IPv4 address of the local tunnel interface cannot be on the same subnet as the destination
•
address configured on the tunnel interface.
167