For more information about these commands, see Avaya Branch Gateway G430 CLI Reference.
|
Root level command
|
Command
|
Description
|
|
interface tunnel
|
|
Enter tunnel interface configuration context, create a Tunnel interface if it does not exist, or delete a Tunnel interface or sub-interface
|
|
keepalive
|
Enable the tunnel keepalive feature
|
|
tunnel checksum
|
Add a checksum to the GRE header of packets traveling through the tunnel
When a checksum is included on one endpoint, the receiving tunnel endpoint performs checksum validation on incoming packets and packets without a valid checksum are discarded.
|
|
no tunnel checksum
|
Disables checksums
|
|
tunnel destination
|
Set the destination address of the tunnel
|
|
tunnel dscp
|
Assign a DSCP value to packets traveling through the tunnel
The DSCP value is placed in the packet’s Carrier IP header. You can assign a DSCP value of from 0 to 63. If you do not assign a DSCP value, the DSCP value is copied from the packet’s original IP header.
Note:
The Carrier IP header identifies the source and destination IP address of the tunnel.
|
|
tunnel key
|
Enable and set an ID key for the tunnel
Tunnel ID keys are used as a security device. The key must be set to the same value on the tunnel endpoints. Packets without the configured key must be discarded.
|
|
no tunnel key
|
Disables key checking
|
|
tunnel path- mtu-discovery
|
Enable dynamic MTU discovery by the tunnel
|
|
tunnel source
|
Set the source address of the tunnel
|
|
tunnel ttl
|
Assign a TTL value to packets traveling through the tunnel
The TTL value is placed in the packet’s Carrier IP header. You can assign a TTL value of from 1 to 255. The default tunnel TTL value is 255.
|
|
show interfaces tunnel
|
|
Show interface configuration and statistics for a particular tunnel or all GRE tunnels
If the Tunnel interface is down, this command displays the MTU value as not available.
|
