Users Guide

Version Description
9.10(0.1) Introduced on the S6010-ON and S4048T-ON.
9.8(1.0) Introduced on the Z9100–ON.
9.8(0.0P5) Introduced on the S4048-ON.
9.8(0.0P2) Introduced on the S3048-ON.
9.7(0.0) Introduced on the S6000-ON.
9.5(0.1) Introduced on the Z9500.
9.4(0.0) Introduced on the S4810, S4820T, S6000 and Z9000.
Usage Information
Enabling tunnel keepalive causes ICMP echo packets to be sent to the keepalive
target. The ICMP echo will be sourced from the tunnel interface logical IPv4 or IPv6
address and will be tunnel encapsulated. The response will be accepted whether it
returns tunnel encapsulated or not.
When configuring tunnel keepalive at both end points of a tunnel interface it is
recommended to set the tunnel keepalive target to the logical IPv4 or IPv6 address of
the far end tunnel peer, rather than to the tunnel destination. This reduces the chance
of both ends of the tunnel staying in keepalive down state. If both ends get into a
keepalive down state that does not clear in a few seconds, then performing shutdown -
no shutdown sequence on one end should bring both ends back to up.
tunnel-mode
Enable a tunnel interface.
.
Syntax
tunnel mode {ipip | ipv6 | ipv6ip}[decapsulate-any]
To disable an active tunnel interface, use the no tunnel mode command.
Parameters
ipip Enable tunnel in RFC 2003 mode and encapsulate IPv4 and/or
IPv6 datagrams inside an IPv4 tunnel.
ipv6 Enable tunnel in RFC 2473 mode and encapsulate IPv4 and/or
IPv6 datagrams inside an IPv6 tunnel.
ipv6ip Enable tunnel in RFC 4213 mode and encapsulate IPv6
datagrams inside an IPv4 tunnel.
decapsulate-any (Optional) Enable tunnel in multipoint receive-only mode.
Defaults There is no default tunnel mode.
Tunneling 2008