| 
 I was a little confused about this but I think we are talking about the same
thing.  In your example here you have your default gateway set to your VIP.
In my configuration I am doing the same thing (on a single network) but it
is not working.
My routing table on my realservers looks like this:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         VIP or DIP      0.0.0.0         UG        0 0          0
eth0
I think you are telling me to do what I have already set up and it is not
working for me but it's very possible that I am missing some piece of the
puzzle that I am not getting from your posts.  
My LVS works fine (if I use the director's IP for a default gw) and my HA IP
address takeover works fine.  The problem occurs when the backup has taken
over.  If my realservers are using the directors IP as a gateway nothing
will work for obvious reasons.  I have tried to use the VIP as the
realservers default gw but this will not work for the primary or backup lvs.
1. Should I be able to use the VIP as the realservers default gw?
2. If yes, what could I be doing wrong that is causing my problem?
3. If no, what can I use to reset my realserver default gw when the backup
takes over?
I'd really appreciatte it if someone could help me clear this up.
-----Original Message-----
From: Alex Kramarov [mailto:alex@xxxxxxxxxxxxxxx]
Sent: Wednesday, November 27, 2002 11:05 AM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: One Network LVS-NAT with HA
No, i am definitely not saying that you should switch, I am just saying that
the documentation of keepalived described very well the principals that you
should configure heartbeat with . 
a sample of redundant active-active lvs directors setup with heartbeat  :
on f1 :
external interface 200.200.200.1
internal interface 10.0.0.1
on f2 :
external interface 200.200.200.2
internal interface 10.0.0.2
 
haresources on both machines :
f1 10.0.0.253 200.200.200.3
f2 10.0.0.254 200.200.200.4
half of real servers have default gateway point to 10.0.0.253 , and the
other half to 10.0.0.254
half of the clients access the real servers with ip address  200.200.200.3,
and half with  200.200.200.4
if you don't need active active setup , just (in this config) i would have
in haresources :
f1 10.0.0.253 200.200.200.3
all real servers have as default gateway 10.0.0.253, and all clients would
access the cluster at 200.200.200.3
 
 
CONFIDENTIALITY NOTICE: The information in this e-mail is privileged and
confidential. Any use, copying or dissemination of any portion of this
e-mail by or to anyone other than the intended recipient(s) is unauthorized.
If you have received this e-mail in error, please reply to sender and delete
it from your system immediately.
 
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
 
. 
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
CONFIDENTIALITY NOTICE:  The information in this e-mail is privileged and
confidential.  Any use, copying or dissemination of any portion of this
e-mail by or to anyone other than the intended recipient(s) is unauthorized.
If you have received this e-mail in error, please reply to sender and delete
it from your system immediately.
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
CONFIDENTIALITY NOTICE:  The information in this e-mail is privileged and
confidential.  Any use, copying or dissemination of any portion of this
e-mail by or to anyone other than the intended recipient(s) is unauthorized.
If you have received this e-mail in error, please reply to sender and delete
it from your system immediately.
 |