Configuring An Ipv6 Over Ipv4 Manual Tunnel - HPE FlexNetwork HSR6800 Configuration Manual

Step
5. (Optional.) Specify a backup
traffic processing slot for the
tunnel interface.
6. Set the MTU of the tunnel
interface.
7. Set the expected bandwidth
for the tunnel interface.
8. Set the ToS for tunneled
packets.
9. Set the TTL for tunneled
packets.
10. Specify the VPN instance to
which the tunnel destination
belongs.
11. (Optional.) Restore the
default settings of the tunnel
interface.
12. (Optional.) Shut down the
tunnel interface.

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 tunnel interfaces 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
Command
•
In standalone mode:
service standby slot
slot-number
•
In IRF mode:
service standby chassis
chassis-number slot
slot-number
mtu size
bandwidth bandwidth-value
tunnel tos { tos-value |
copy-inner-tos }
tunnel ttl ttl-value
tunnel vpn-instance
vpn-instance-name
default
shutdown
283
Remarks
By default, no backup traffic
processing slot is specified for
an interface.
By default, the MTU of a tunnel
interface is 1500 bytes.
The default expected bandwidth
(in kbps) is the interface
maximum rate divided by 1000.
The expected bandwidth for the
tunnel interface affects the link
cost value. For more information,
see Layer 3—IP Routing
Configuration Guide.
By default, the ToS is the same
as that of the original packets for
non-VXLAN packets, and the
ToS is 0 for VXLAN tunneled
packets.
The copy-inner-tos keyword is
supported only by VXLAN
tunnels.
The default TTL for tunneled
packets is 255.
By default, the tunnel destination
belongs to the public network.
For a 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.
N/A
By default, a tunnel interface is in
up state.