Create a Static Tunnel
Tunnels that are auto-discovered are called dynamic tunnels; tunnels
that are created manually are called static tunnels. If global
discovery of hosts and tunnel partners is disabled or if you are in migration mode, the only way to have
enhanced Xpress tunnels is to manually create them — dynamic tunnels will
not be formed. Other reasons for creating static tunnels are that they
are given higher priority than dynamic tunnels, they will quickly and
automatically form after the PacketShaper is reset, and they allow you
to force a tunnel setup in a situation when something may be preventing
automatic tunnel formation.
To define a tunnel, you must assign it a name, specify the
tunnel partner's Xpress-IP address, and indicate on which device (built-in
or LEM) that the tunnel will be formed. If you want the tunnel to have
special parameters different from the default settings, you can change
the settings while creating the tunnel.
To create a static tunnel:
1. Click the xpress tab.
2. Click add tunnel. The Add Tunnel
window appears.
 show screen
3. Enter a descriptive Name for the tunnel.
The name can be up 24 characters long and may include alphanumeric characters
and the following special characters: . - _ : @ # $ % = + [ ] { }
Spaces
are not allowed.
The following names are reserved for other uses and are prohibited as tunnel names: acceleration, all, class, compression, default, delete, dictionary, diffserv, discovery, faststart, firewall, force, global, high, holdtime, host, information, ip, local, logging, low, mem, mtu, new, normal, off, on, packing, partner, password, ping, prefetch, priority, remote, remove, scps, service, show, state, static.
Note: Tunnels cannot be renamed so choose your
name carefully. If you later decide that you want to rename a tunnel,
you'll need to remove it and create a new one.
4. For Partner IP, specify the Xpress-IP address
of the partner PacketShaper.
5. For Device, select the device to configure
on the local unit:
main— built-in interface
upper — upper LAN
Expansion Module (LEM)
lower — lower LEM
6. If you want the tunnel to use all of the default
global tunnel settings, you can click OK to create the tunnel.
Otherwise, for each feature select off or use global:
|
Feature
|
Description
|
|
Acceleration
|
Disable acceleration for the tunnel or use the global setting
for acceleration
The SkyX compatible checkbox is for creating
SkyX tunnels.
|
|
Compression
|
Disable compression for the tunnel or use the global setting
for compression
|
| Packing |
Disable packet packing for the tunnel
or use the global setting for packing |
7. For each option, select the desired setting:
|
Option
|
Description
|
|
Firewall
|
Enable or disable firewall support for the tunnel or use the
global setting. If the PacketShaper will be sending and receiving
tunneled traffic through a firewall tunnel (a pair of stateful firewalls), this setting must be enabled.
It is not necessary to enable firewall support on each tunnel
partner. When firewall support is enabled on one end of the tunnel,
it will automatically act as if it is enabled on any partners
(although the firewall setting is not actually physically changed
on these partners).
It is not recommended to enable firewall support on tunnels used just for acceleration.
|
|
DiffServ
|
Enable or disable DiffServ (Differentiated Services) mode for
the tunnel or use the global setting. DiffServ mode should be
enabled when using compression or packing on
a DiffServ network.
If an Xpress tunnel has DiffServ enabled, Xpress will inspect
all packets for its DiffServ Code Point (DSCP) value. Within the
tunnel, it will create a separate lane for each DSCP value.
When Xpress sees packets with a DSCP different from those seen
before, it will create a new lane associated with that DSCP. Any
packets with that DSCP are then sent through the associated lane.
Notes:
- When DiffServ mode is enabled, the tunneled super packets
will inherit the DiffServ markings of the original packets.
- If a super packet is marked with a different DSCP value while
it's inside the MPLS network, the partner PacketShaper at the
other end of the tunnel will remark each of the original packets
with this new value.
- Xpress supports up to five DSCP (DiffServ Code Point) values.
If your network exceeds the maximum, the super packets in the
tunnel will not have DiffServ markings. However, if the super
packet is marked with a different DSCP value while it's inside
the MPLS network, the partner PacketShaper will remark each of
the original packets with the new value.
|
| Discovery |
Disable the auto-discovery of hosts
for the tunnel or use the global setting. When host discovery is disabled,
you will need to manually add hosts to the tunnel using the tunnel local add and tunnel remote add commands.
Note: Automatic host discovery works in enhanced mode only; it is not operable in migration mode. |
| MTU |
Set the Maximum Transmission Unit (MTU) used for packing and acceleration
on the tunnel, or use the global setting. The MTU defines the maximum
size of the super packet — it's the largest datagram than can
be transmitted by an IP interface (without it needing to be broken
down into smaller units). Valid MTU values are 100-1500; the default
is 1500 bytes.
|
8. Click OK. The static tunnel will now be
listed in the Xpress Tunnels Overview. If you changed any of the
default settings, the tunnel name will be italicized.
See also:
Xpress Overview
Configure Global Xpress Settings
Convert a Dynamic Tunnel to Static
|
