|
"Lizambri, Todd" wrote:
> Ifconfig will show the eth0:110 (assuming that someone created the
> alias).
OK
> The MINI-HOWTO says to get your director/realservers to ping each other.
> I have done this, but I used eth0 when setting up my network scripts
> (ifcfg-eth0, not an alias). When I do an ifconfig, you only see eth0. I
> can ping the director from the realservers and vice-versa.
fine
> In the lvs_nat.conf, I had put in the alias eth0:1(I though the script
> would do an ifconfig on the director to set-up the aliased interface).
it should.
> If I change the eth0:1 to just eth0 in the lvs_nat.conf, the original
> problem that Matt and myself had goes away (the one where commenting out
> the remove_old_vip() got us around the problem).
do you mean that the script runs fine and sets up a working LVS? Obviously
not, but what problem goes away?
> I am still losing my default gateway (unless I hardcode DEFAULT_GW=xxx
> into the rc.lvs_nat script).
OK
> Connections initiated from my realserver to the outside world go through
> the director, but are not being NATed.
OK
> Is NOT using aliases a problem?
this is probably it. I always have the VIP on an alias as I need an already
functioning network to test connections before I set up the LVS. I've
never tested it with the VIP on a non-alias.
Is it OK to have an LVS with the VIP on an alias (at least in principle)?
Can you tell me again what goes wrong if the VIP is on eth0:1? The rc.lvs_out
file
shows me that there is no aliased IP (eg eth0:1) in the output of ifconfig.
It appears I don't have the whole picture yet.
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
