|
Randy Paries wrote:
>
>
> This is my ldirectord.cf
> ==========================================
> virtual=66.208.187.27:80
> real=192.168.0.203:80 gate
> In my httpd.conf on 192.168.0.203 I have
> <VirtualHost 192.168.0.203 >
> ServerName 192.168.0.203
> DocumentRoot /home/unitnet
> ServerAlias unitnet.com
> </VirtualHost>
I'm not an ldirectord user.
However for LVS-DR, on the realserver, the service (here httpd)
has to listen on the VIP. So you don't need x.x.0.203 here,
you need the VIP and the name that it will be known to by
the client.
That's for LVS-DR.
However if the you are monitoring from the director, you need
a service that the director can monitor. Presumably this
is the one on the RIP. You then hope that the state of
the httpd listening on RIP:80 is some indication of the
state of the httpd listening on VIP:80
This is all explained in the HOWTO BTW.
> <VirtualHost 66.208.187.27 >
> ServerName test.unitnet.com
> ServerAlias unitnet.com
> ServerAlias flanders.unitnet.com
> DocumentRoot /home/unitnet
> </VirtualHost>
>
> I had to do the VirtualHost 192.168.0.203 so ldirectord would work.
> Is this what I am suppose to do??
if ldirectord works the way I just described, then yes
Joe
--
Joseph Mack PhD, High Performance Computing & Scientific Visualization
SAIC, Supporting the EPA Research Triangle Park, NC 919-541-0007
Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
|
