Comtech EF Data FX Series Administrator Guide - Manual (Page 93)

Comtech EF Data / Stampede
FX Series Administration Guide - Version 6.1.1 93
Chapter: FX Series ADC Specific Settings
Section: Overview
MN-FXSERIESADM6 Rev 5
HTTP Session Inactive Timeout (seconds):
This setting controls the maximum time that inactive browser sessions are kept open before closing them
in order to minimize thread and TCP session resources. The default interval value is 60 seconds.
HTTP Server Connect Timeout (seconds):
This controls the maximum number of seconds that the FX Series ADC will wait for a TCP connection to
complete to an HTTP content server before timing-out. After the timeout, a 503 HTTP error code will be
returned to the browser that initiated the request. The default value is 20 seconds.
Generate HTML error pages:
This controls whether the FX Series ADC should generate an HTML page describing the problem and
identifying the FX Series ADC when it encounters a problem connecting and/or receiving content from a
back-end server. The default value is “Enabled”.
Preserve Client IP Addresses:
If enabled, then the FX Series ADC will send the requests to the back-end servers with a source IP address
that is the same as the client that the request is on behalf of. Enabling this setting may require a
Transparent Bridging configuration. This setting only applies to single-sided optimization. IP source
preservation with FX Remotes is specified in the L5 application policies. The default value is “Enabled”.
5.1.2 Object Retrieval Logging
Log HTTP Requests:
Enables logging of URLs for all HTTP web object retrievals in “common log format”. The default setting is
“On”.
Maximum Size in KB
This sets the maximum size of the object retrieval log file in kilobytes. When this size is reached
a backup is made and the file is reset. The default setting is 1000000 (1 GB).
5.1.3 Traffic Interception
Traffic interception mode:
This is the means by which the FX-ADC will transparently intercept packets. Choose
either “In-Line”, “Routed”, WCCP” or “Disabled”. The default is “In-Line”.

In-Line mode, the LAN port is eth2 and the WAN port is eth3. Traffic is
intercepted as a transparent bridge. If there is a service disruption then the
units will “fail-to-wire”. In bridged mode, you must assign an IP address to the in-path interface
which bridges the LAN and WAN interfaces. In FX nomenclature, the “WAN” interface is
considered to be the interface which is connected to the satellite modems and the LAN interface
is connected to the internet or to enterprise servers.

In routed mode, traffic must be directed to these interfaces by a router. You must assign an IP
address to the in-path interface which will receive traffic from the router. There is no “fail-to-
wire” capability if there is a service disruption.

In WCCP mode, traffic is redirected to the FX by a Cisco router via WCCP.

If “Disabled” then traffic redirection is effectively shut off.
VLAN mode:
This controls how the FX will process VLAN tags. In 'Trunk' mode, the VLAN tags are already embedded in
the packets when they are intercepted by the FX. In 'Access' mode, the FX will add tags to untagged
traffic. The default setting is ‘Trunk’.
Note: Changing either the ‘Traffic interception mode’ or ‘VLAN mode’ settings will automatically
trigger a restart of the acceleration service.