Networking :: Keeplalived Refuses To Allow 3rd Instance?

I've beeb setting up keepalived/haproxy as a load balancer for our site.

If you keep it down to two load balancing instances it works just fine. However, I was told to add a 3rd load balancer to the mix and that adds a new wrinkle. I need to add a new keepalived instance and I can't quite figure out how that's done.

It would seem to me to be an issue of the priorities as that is the only thing I altered in the files. Initially, nodes A and B were set to 101 and 100 respectively. I set node A to 102, node B to 101 and node C to 100... keepalived restarts and the virtual IP is pingable. But the website goes down!

SO then I tried Node A set to 101, node B to 100 and node C to 99. Same thing, I restated keepalived and the site goes down, tho the virtual IP remains pinagble and keepalived and haproxy are running.

here is a sample config file from my setup:

Code:
vrrp_instance VI_1 {
state MASTER
interface eth0
virtual_router_id 51

[Code].....