Re: PRIMARY and NAT_ROUTER confusion with LVS.CF and PULSE handling.

pb wrote:
> Here's the initial confusion. Using Piranha_GUI for
> setup the "PRIMARY=.." becomes not the PUBLIC address
> of PIRANHA/LVS SERVICES usually on the "eth0:1"
> virtual interface, but rather "PRIMARY=.." is the host
> address for physical interface "eth0" on the public
> side!

This is as it should be.  The lvs.cf format is designed so that it can 
be copied *unmodified* to the backup machine.  None of the virtual ips 
for any of the services should be listed in primary or backup, but 
rather the main ip address of the machine itself (the ip that pulse 
should bind to).  The machine will compare the values of 'primary=' and 
'backup=' to it's own addresses and decide whether it is primary or 
secondary.

> Also, I assume I am supposed
> to setup eth0:1 (piranha public addr) and eth1:1 (nat
> router) to be in place, but not activated at boot
> time,
> correct? (That is what I do now.)

Piranha will handle the starting and stopping of the alias devices.  *Do 
not* set up external scripts to configure them.  It's all in lvs.cf.

> Additional confusion.  The lvs.cf file has a
> "NAT_ROUTER=x.x.x.x eth1:1" setting where 
> x.x.x.x is the same (but not simultaneouly activated)
> on both the prime and back lvs systems.

This is correct.  It should be the same.  The idea is the in the nat 
routing scenario, your real servers will have this virtual ip as their 
default route.  When failover occurs, this virtual ip is moved over as 
well, making the failover transparent to the servers.