User manual

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

205.188.166.10. The WebMux™ will then translate the farm address to the web

server address in your DMZ or internal network.

Since version 4.0.3, we also introduced “label” concept for the farms and servers.

Once the label is specified, the WebMux™ will display in the Show-Status screen

the label for the farm and server instead of the IP addresses. Although labels

can be anything, it is better to have meaningful and unique label for each farm or

server. Since version 5.6, the name label is also being used to check HTTP

layer 7 protocols as part of the MIME header in virtual hosting. The format of the

farm name label will be

www.xyz.com, max length 75 bytes. If the server returns

error code 401, the WebMux™ considers that server dead. For both IIS and

Apache servers doing virtual hosting, the farm name label must be an existing

web site name on the server. For more information on Virtual hosting, please go

to Appendix 4 for details.

In NAT mode, if you use the WebMux™ for your intranet, then the farm IP

address will be the IP address of the original web or application server. The web

or application servers must be changed their IP addresses so that the WebMux™

can translate farm IP address to the server IP address. You can use the

WebMux™ Router LAN IP address as your farm address to save IP address.

You can add multiple farms to this IP address, as long as the port number is

different.

In the NAT (not TM) mode, the WebMux™ acts as a firewall also, all ports except

farm port(s) are blocked. All servers behind the WebMux™ can reach to the

outside through the WebMux™. From outside, the traffic can be seen all come

from the WebMux™ router LAN IP address, or proxy address. If a WebMux™ is

placed behind a firewall, please add a rule on firewall for WebMux router LAN

address to anywhere/anyport. All farm IP addresses should have rules to allow

incoming traffic mapped to the address and port number, as well as return traffic

for each farm IP address from any port to anywhere.

In Transparent (TM or bridge) mode, there is no firewall protection from WebMux.

All servers talk to each other freely cross WebMux. Only the farm IP/port

address is being load balanced using any selected scheduling method.

In Out-of-Path mode, farm(s) must be a different IP address than the WebMux™

Server LAN IP address. At this mode, only server LAN cable is connected.

Multiple farms can be added to one IP address, as long as the port number is

different from each other. In this mode, each server must add a loopback

adapter and under Windows server, the route for the loopback adapter must be

removed. Please refer to Appendix 1 and 2 for more detailed procedures.