LVS Configuration

["Rogers, Paul" <Paul.Rogers@xxxxxxxxxx>]

Dear All

I notice from the mini-HOWTO that one can use configuration scripts to configure the LVS, which can then be used on both the Real Servers and the Directors.  However these don't appear to be included in th ipvs tarball (ipvs-1.0.6.tar.gz).  I did manage to find a configure-lvs_0.9.4.tar.gz but based on the 0.9.4 I assume the scripts contained therein may be out of date.  I also notice that elsewhere on the site it says something to the effect that "our survey shows most of our users don't use the scripts".

Am I right in thinking the scripts are no longer maintained?  If not would they still work with a 2.4.19 kernel?  What is the preferred method fro configuring the LVS now - the "setup by hand" method mentioned in the mini-HOWTO.

I am trying to set up an LVS-DR with one director and two realservers.  The director has two NICS in it (not sure if this relevant) and all the Real Servers, the Director and most of the clients are all on the same subnet, on our LAN.  All other clients are on our WAN and come via a router.

Again looking at the scripts I am unsure which one I should use. I think the ip's I wish to set up are as follows :

DIP1 = 10.80.18.202
DIP2 = 10.80.18.203

VIP1 = 10.80.18.204
VIP2 = 10.80.18.205

RIP1 = 10.80.18.43
RIP2 = 10.80.18.44

GIP = 10.80.16.1

CIP = 10.80.21.26 (example)

The diagram on page 13 of the HOWTO.introduction appears ver close to what I wish to do.  Can any one suggest which of the scripts is the nearest fit, or alternatively should I amend the setup by hand example to suit?

Many thanks

Paul

*****************************************************************************
This email and any attachments transmitted with it are confidential
and intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please
notify the sender and do not store, copy or disclose the content
to any other person.

It is the responsibility of the recipient to ensure that opening this
message and/or any of its attachments will not adversely affect
its systems. No responsibility is accepted by the Company.
*****************************************************************************