|
http://bishop.itsp.purdue.edu/cgi-bin/trac.cgi/file/branches/vsc-2.0/NESSUS-LVS
This is the how-to I am trying to follow.
In i, there is an exampe of lvs_dr init script that configures teh director to
handle requests for nessus....
http://bishop.itsp.purdue.edu/cgi-bin/trac.cgi/file/branches/vsc-2.0/Examples/lvs_dr
now If i follow this, do I have to follow the how-to on ultramonkey or lvs.org?
Or using this guides helps to set up lvs just fine?
--p
Horms <horms@xxxxxxxxxxxx> wrote:
On Tue, Nov 01, 2005 at 10:36:26AM -0800, jess patel wrote:
> I was also wondering if someone could help me
> understand these lines:
>
> cluster, vscan1, vscan2 are defined in /etc/hosts
>
>
> /bin/ping -c 1 ${CLUSTER}
> /bin/netstat -rn
>
> ${IPVSADM}/ipvsadm -C
> ${IPVSADM}/ipvsadm -A -t cluster:1241
> -s rr
>
> #${IPVSADM}/ipvsadm -a -t cluster:1241
> -r vscan1 -g -w 1
> #ping -c 1 vscan1
> #${IPVSADM}/ipvsadm -a -t cluster:1241
> -r vscan2 -g -w 1
> #ping -c 1 vscan2
>
> there are three ip addresses being used I am
> guessing...one for CLUSTER, cluster, vscan1, vscan2.
> Are these all necessary? Lets say I want nessus on
> two nodes only. Comp1, comp2. how do i change these
> lines? what does cluster:1241 represent? God, I am so
> lost ...help me please
cluser, is the Virtial IP address, that is, the address
that end-users will connect to.
vscan1 and vscan2 are the addresses of the real-servers,
that is, the addresses that the linux-director forwards packets to.
The role of the linux-director, real-servers, and end-users
is covered in the HOWTO. Its also breifly covered here:
http://www.ultramonkey.org/3/lvs.html
The basic principles of LVS are quite simple. It only seems
complex because there are a number of machines and addresses involved.
But if you take the time to understand the basics, then everything
builds on top of that. In other words, there is no magic in there.
--
Horms
---------------------------------
Yahoo! FareChase - Search multiple travel sites in one click.
|
