User guide

- 41 -
WebMux https control port:
Since the WebMux is 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 to any port that is not being load balanced, if so desired. The front push
buttons can also change this.
SNMP UDP Port:
SNMP on the WebMux is active and uses port 161 by default. You can change the port here.
Or you can enter “0” or “none” or leave blank to disable SNMP altogether.
SNMP Community String:
WebMux uses SNMP v1 and the community string “webmux” by default.
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.
WebMux failover ports:
The WebMux allows configuration of fail-over ports being used by primary and backup
WebMuxes. Default port numbers are 2000 and 2001. You will only need to change the port
numbers unless there conflict with other services.
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 sent through multiple
cache servers; it is possible the requests for one HTML page are 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 the 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 this 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 to combine. When too
large a mask applied, it will defeat the load balancing function of the WebMux.
Act as IP Router:
Yes: The WebMux will route IP packets both directions. The WebMux will not act as a
firewall in this mode.