H3C Technologies H3C S12500-X Series Switches - Manual (Page 161)

150
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)
• Configure the IPv6 host:
# Configure a route to the ISATAP switch.
C:\>netsh interface ipv6 set route 2001::/64 5 3001::1
Verifying the configuration
# Ping the IPv6 host from the ISATAP host. The ping operation succeeds, indicating an ISATAP tunnel has
been established.
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, and vice versa.
• 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.