|
On Wed, Nov 02, 2005 at 07:18:21AM -0800, jess patel wrote:
> 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?
You should read whatever documentation you need to get your setup
working. The fundamental comcepts are very simple.
http://www.ultramonkey.org/3/lvs.html
Each machine needs its own ip address on each network it is connected
to, though they may be private RFC1819 addresses. You need one extra
address for the cluster istelf, this needs to be a publicly routed
address if you want end-users from the internet to be able to connect.
I would recmomend drawing a diagram of your network, and labeling each
ip address in the diagram. Something like the diagram here:
http://www.ultramonkey.org/3/topologies/hc-ha-lb-eg.html
However, please note that LVS-DR can be tricky to setup,
and LVS-NAT is somewhat simpler. As this is your first attempt
at setting up LVS, and you are clearly having some issues understanding
how things work, I would recommend starting with an LVS-NAT setup,
then moving to LVS-DR once you have mastered that.
http://www.ultramonkey.org/3/topologies/ha-lb-eg.html
Note that for LVS-DR the cluster has 2 ip addresses, but
only the external one needs to be public, the other may
be RFC1819.
http://www.ietf.org/rfc/rfc1819.txt
--
Horms
|
