Exinda EXNV-10063, Administration Manual

Page: 477 / 623

Exinda Network Orchestrator 4 Settings | 477
Transparent TCP
– Ensures Exinda's Application Acceleration is fully transparent. Source and destination IP
addresses and port numbers are maintained on all accelerated connections, so any equipment in between two
accelerating Exinda appliances can still see correct IP and TCP headers.
Protocol Tunnel
– When equipment in between two accelerating Exinda appliances will strip the TCP
options, you will need to use the Protocol Tunnel transport type so that other equipment cannot strip these
required option codes.
Window Scaling Factor
– Specifies how large the TCP receive window can be, according to the formula: TCP Win-
dow Size kB = 64 kB x 2 ^ Window Scaling Factor. The scaling factor ranges between 0 and 14, meaning that the receive
window can be between 64 kB and 1 GB. The TCP window scaling factor is needed for efficient transfer of data when
the bandwidth-delay product is greater than 64kB. The default scaling factor is 5 resulting in a window size of 2MB. Lar-
ger window sizes result in more potential memory usage. However, the window size may need to be increased in high-
bandwidth, high-latency environments to ensure the bandwidth is fully utilized.
Congestion Control – Indicates which congestion control algorithm should be used. The most common congestion
control algorithms are listed together with their intended usage. Set this according to the type of WAN the Exinda appli-
ances are deployed into. This setting only affects outbound traffic to the WAN, so the same setting should be applied to
all Exinda appliances on the WAN.
TCP Keep-Alive Enabled
– Enables the sending of keep-alive packets on the WAN.
TCP Keep-Alive Timeout
– Specifies the amount of time, in seconds, that a connection may be idle before sending
keep-alive packets is enabled. Keep-alive packets are sent once per minute until either a response is received, or 5
minutes passes. If five minutes passes without a response the connection is terminated.
Dual Bridge Bypass
– Specifies whether acceleration should be handled on a single bridge or multiple bridges
when traffic is passing through an Exinda appliance multiple times.
Enabled
– All acceleration processing is performed on one bridge only. This is desirable for accelerated back-
hauled traffic.
Disabled – Acceleration processing is performed on whatever bridge it arrives on. This is desirable for asym-
metric routing or link aggregation.
To learn more about this feature, see
Dual Bridge Bypass
.
Acceleration TCP Options Mode – Specifies which option code to use in tagging accelerated packets.Historically,
Exinda appliances used TCP option 30, however, TCP option 30 has be assigned to indicate multi-path TCP. Exinda star-
ted using option 230 in v7.0.
30+230: Send 230 where possible, 30 when unsure, accept both (default) – The system will respond with
whatever the remote used. If both options 230 and 30 are available, option 230 will be used. This is the best
choice when some of your appliances are v7.0 and later and some are v6.x and earlier. This is a compatibility
mode.
230: Send and accept options 230 only – Only option 230 will be used. Packets with option 30 will not be
looked at. Use this when all your appliances are v7.0 and later.
30: Send and accept options 30 only – Only option 30 will be used. Packets with option 230 will not be
looked at. Use this when all your appliances are earlier than v7.0.
230-compat: Send options 230, accept incoming options 30
– Always sends using option 230 and uses
compatibility mode for receiving packets, that is, it will handle receiving both option 230 and option 30.
30-compat: Send options 30, accept incoming options 230 – Always sends using option 30 and uses com-
patibility mode for receiving packets, that is, it will handle receiving both option 230 and option 30.
Multi-Path TCP (MPTCP) Acceleration Bypass – Specifies whether to attempt acceleration if the traffic is identified
as multi-path TCP and falls into an acceleration policy.