The WebMux™ Model 480S, 580SG, and 680PG User Guide – Version 7.0.x
Copyright© 1997-2006 CAI Networks, Inc.
37
It can be the router in front of the WebMux™, or a router in your ISP’s WAN. It is
recommended to have the router IP address as the verification IP address.
However, it can be any address that is reachable on your Internet side.
Persistence Timeout
:
The WebMux™ will keep track the browser connections if the persistent farm is
defined and accessed. Within the timeout time period, the WebMux™ will send
any request from the browser IP address to the same server. Our survey shows
5-6 minutes is the best value for most cases. The larger the persistence timeout
value, the less chance user connection get lost. However, by keeping a lot of
connections in the WebMux™ memory, the maximum number of concurrent
connections will drop.
Outbound Connection Timeout
:
The WebMux™ keeps track the outbound connections. This outbound proxy
function provides communication tunnels for servers behind it to talk to other
computers on the Internet side. This type of connection is different from the
connections from outside through server farms to the servers. After the
connection closed from the servers to the outside computer, it will wait this
timeout minutes before it removes that from the tracking table. Setting this too
long will cause the WebMux™ to allocate too much memory, thus reduce the
memory for other functions. The default value is 15 minutes. This function has
no effect in Out-of-Path mode.
Server Scan Mode
:
The WebMux™ talks to the real servers in the farm through the layer 4-7
protocols every few seconds. This is important process for monitoring servers’
health situation. If there are a lot of farms and a lot of servers, the WebMux™
may not be able to get around checking all the servers in few seconds. In
concurrent mode, the WebMux™ will start multiple protocol scanners to chat with
servers concurrently. Concurrent mode uses more memory and may have other
side effects. For most setups, sequential scan is recommended.
URL for Custom Service Check
:
Sometimes the WebMux™ built-in server health check is not enough for special
needs. When one ASP/JSP server’s output depends on the database server and
the database server connection is down, one might want to reduce the incoming
traffic to the server, suspend new traffic to the server, or totally redirect incoming
traffic to a different server. To accomplish that, the WebMux™ allows a farm
being set using a “custom defined service”. It will then call the CGI’s URL on the
server defined in this field. This will involve a custom developed CGI code by
your software developer on your server and place it on the path. Upon success
the page should return HTTP response code 200 and a plain text page beginning
with one of the allowed responses. The URL is truncated to 255 bytes (to be a
string of at most 256 bytes with a terminating null). The response from the server
must fit in 4k, including all non-display tag and headers etc. This custom CGI
Summary of Contents for WebMux 480S
Page 4: ...iv...
