User manual

The WebMux Pro and Model WM108E User Guide – Version 5. 8 Rev15
Copyright© 1997-2004 CAI Networks, Inc.
30
WebMux http control port:
Since WebMux load balancing incoming HTTP traffic, the HTTP port for the
management console must be set to a different port. By default, the port is 24.
You can change the port, if so desired. Front push button can also change this.
WebMux https control port:
Since WebMux load balancing incoming HTTPS traffic, the HTTPS port for the
management console must be set to a different port. By default, the port is 35.
You can change the port, if so desired. Front push button can also change this.
WebMux diagnostic ports:
The WebMux allows diagnostic sessions from remote access for factory technical
support or trained network engineers through ssh or telnet. Access is also
subject to the restriction of the “Allowed-Host” setting earlier. “superuser” can
login with its password using “ssh” to run certain diagnostic tools (help shows the
commands, how to use these commands are not supported). When this entry is
blank, any diagnostic access is denied. This entry should remain blank under
normal operations. Default port numbers are 77 / 87. The first port is ssh and
second is telnet. If only one port specified, only ssh login is possible. You will
need to notify us the port numbers before obtaining support from us.
Connection warning threshold:
The WebMux monitors the number of connections established. When the
number of connections is greater than the value entered, the WebMux will page
the designated numbers. For example, if a DoS attack is occurring, the number
of connections to the site would be extremely high. Assuming they exceeded the
value set for the “connection warning” threshold, the designated numbers would
be paged.
Least significant bits in client IP address to ignore for persistent
connections:
This feature allows persistent connections to be handled properly when
communicating with America Online’s bank of cache servers. With AOL’s cache
servers, the IP address of the cache server becomes the source address. Since
an end user can be send through multiple cache servers; it is possible the
requests for one HTML page being routed to different web servers in the same
session. Therefore, applications, such as shopping carts, that require persistent
and secure connections will not work properly. This feature will treat multiple
cache servers as one source, thus WebMux can properly handle the persistent
requests from browsers. From customers’ feedback, number three (3) is good
enough for most AOL requests.
The WebMux will use the entry to determine how to load-balance the traffic. It
calculates based on two to the power of the entry as the number of IP addresses