User manual

The WebMux™ Model 480S, 580SG, and 680PG User Guide – Version 7.0.x

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 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™.

ICMP Packet input policy:

Accept: The WebMux™ will allow all ICMP packets to travel through the

WebMux™. For CLI arp commands working properly, this must be accept.

Deny: The WebMux™ will NOT allow any ICMP packets to travel through the

WebMux™.

NOTE: During installation, having the ability to PING the other hosts on the

networks is typically useful. When the installation is complete, setting the “ICMP

packet policy” to DENY, is recommended as a security precaution.

Forward Policy:

Accept: The WebMux™ will route IP packets both directions. The WebMux™ will

not act as a firewall in this mode.

Deny: The WebMux™ will NOT allow any incoming IP packet traveling through

the WebMux™, except IP packets in farm IP/port. This is the default setting.

Front Router Connection Verification:

It can be “none”, “ARP”, “TCP Connection”, or “ping”. Depending on the front

end router, this can be changed. For example, most Cisco routers will talk to the

WebMux™ through ARP and TCP Connection; however, most Cisco DSL

modems will only talk to the WebMux™ through Ping. The change to this

verification method will take effect after the WebMux™ has been rebooted.

Front Router Connection Verification IP Address:

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.