Installation guide

Load monitoring tool

The LVS router can monitor the load on the various real servers by using either rup or

ruptime. If you select rup from the drop-down menu, each real server must run the rstatd

service. If you select ruptime, each real server must run the rwhod service.

Caution

Load monitoring is not the same as load balancing and can result in hard to

predict scheduling behavior when combined with weighted scheduling

algorithms. Also, if you use load monitoring, the real servers must be Linux

machines.

Scheduling

Select your preferred scheduling algorithm from the drop-down menu. The default is

Weighted least-connection. For more information on scheduling algorithms, see

Section 3.1, “Scheduling Algorithms”.

Persistence

If an administrator needs persistent connections to the virtual server during client

transactions, enter the number of seconds of inactivity allowed to lapse before a connection

times out in this text field.

Important

If you entered a value in the Firewall Mark field above, you should enter a value

for persistence as well. Also, be sure that if you use firewall marks and

persistence together, that the amount of persistence is the same for each virtual

server with the firewall mark. For more on persistence and firewall marks, refer to

Section 5, “Persistence and Firewall Marks”.

Persistence Network Mask

To limit persistence to particular subnet, select the appropriate network mask from the

drop-down menu.

Note

Before the advent of firewall marks, persistence limited by subnet was a crude

way of bundling connections. Now, it is best to use persistence in relation to

firewall marks to achieve the same result.

Chapter 4. Configuring the LVS Routers with Piranha Configuration Tool