User guide

- 67 -
Server Port Number:
If the port number specified in the farm setup is the same as the real server’s port number,
you can leave this as “same.” In NAT mode, the WebMux can perform port forwarding from
the farm IP port to the server IP port if you specify a server port that is different from the
farm port.
CAUTION Like the IP address, once created, the port number cannot be changed. To
correct the port number, the server needs to be deleted and a new one to be created.
Weight:
Scheduling priority weight. Valid integer numbers are between 1 and 100. A server that has a
weight of 2 will be directed twice as much traffic as a server with a weight of 1.
A special zero weight setting is provided for a graceful shut down of a server. When the
weight is changed to zero, the WebMux will not send new connections, but will maintain all
current connections to the server. The connections will gradually reduce to zero as current
clients’ sessions terminated. When there are no connections, the server is functionally “dead”
or off line until the weight is changed back to a valid number. Then the server can then be
shutdown or taken out of service without affecting any users.
CAUTION Unlike a server that can go down unexpectedly, the WebMux will not move a
STANDBY server to ACTIVE when one or more server’s weight is set to zero. If the
weight of all the servers in a farm were set to zero, then the farm would be “down”
because none of the servers are accepting new connections.
Note If your scheduling method is of the “persistent” type, be aware that the WebMux
will continue to honor those existing persistent sessions. If you have clients that continue
to return before the persistence timeout has expired, then you will continue to see
connections coming in.
Run State
Active—The server will be put into service immediately after it is added
. If there are servers
in the farm in Standby, WebMux will activate a Standby server in its place if it goes out of
service. When the original server comes back in service, it will stay Standby mode until
manually setting its run state to Active again through the browser interface. This will give
system administrator time to fix the system or reboot the server once some software/hardware
update is completed.
Favorite Active—The server will be put into services immediately after it is added. If a
Favorite Active server failed, once it is operational, the WebMux will automatically put it
back to the Active state.
Standby—The server will be put into STANDBY, or backup, mode after it is added. The
WebMux will change a STANDBY server to ACTIVE when one or more ACTIVE servers
fail. The weights will also have an effect on the number of standby servers that are activated.
The if the failed active server had a weight of 20 and there are two standby servers with the
weight of 10, the WebMux will activate the two standby servers to make up the difference.