|
I'm playing with a small LVS-DR cluster where the
directors are also the load balancers, modeled after
the "Streamline High Availability and Load Balancing"
example on http://www.ultramonkey.org/. I'm running:
RedHat 7.3 with updates
kernel-2.4.20-19.7.um.1.i586.rpm (ultramonkey.org -
includes LVS 1.0.9 and hidden_interface patches)
ipvsadm-1.21-1.rh.7.3.um.1.i386.rpm (ultramonkey.org)
keepalived-1.1.1 (keepalived.org)
/ETC/SYSCTL.CONF
net.ipv4.ip_forward = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.hidden = 1
net.ipv4.conf.lo.hidden = 1
I have the following IP setup:
VIP: 192.168.100.98
RIP: 192.168.100.96 (server1)
RIP: 192.168.100.97 (server2)
SERVER-DIRECTOR1
eth0 - 192.168.100.96
lo:0 - 192.168.100.98
SERVER-DIRECTOR2
eth0 - 192.168.100.97
lo:0 - 192.168.100.98
Keepalived correctly handles the assignment and
failover of the VIP:192.168.100.98 (via iproute2). My
problem, however, is that I can't ping or otherwise
connect to the VIP from any other boxes on my
192.168.100.X LAN ... regardless of which
SERVER-DIRECTOR is primary and owns the IP.
[root@test1 root]# ip addr show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 192.168.0.98/32 brd 192.168.0.255 scope
global lo:0
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc
pfifo_fast qlen 100
link/ether 00:01:80:02:20:18 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.96/24 brd 192.168.0.255 scope
global eth0
inet 192.168.0.98/24 scope global secondary eth0
If it matters, these two boxes are connected to a hub,
not a switch.
Does anyone have any suggestions on where to start
troubleshooting this? This simple problem is driving
me crazy! Thanks!
-Ken
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
|
