LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

[lvs-users] problems with hc-ha-lb architecture

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [lvs-users] problems with hc-ha-lb architecture
From: Jordi Garcia <jgarcia@xxxxxxxxxxxx>
Date: Thu, 06 Sep 2007 17:19:11 +0200
Hello,

I have this architecture:

2 fronteds with Debian 4.0
2 backends with CentOS 5.0
2 lb with CentOS 5.0

I balance a MySQL service running in backend servers. With a MySQL
client in frontends, I can connect to backend trought lb process
without problems. The lb backup server, don't have problems to connect
via VIP address with the same MySQL client.

My problem is with lb master server, I cannot use VIP address by connect
to db backend:


ss2:~# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  172.16.17.11:3306 wrr
  -> 172.16.17.9:3306             Route   1      0          0
  -> 172.16.17.8:3306             Route   1      0          0

ss2:~# mysql -h 172.16.17.11 -u email -p
Enter password:
ERROR 2003 (HY000): Can't connect to MySQL server on
'172.16.17.11' (111)

ss2:~# mysql -h 172.16.17.9 -u email -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
[...]

ss2:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_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 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
qlen 1000
    link/ether 00:30:05:fb:61:cd brd ff:ff:ff:ff:ff:ff
    inet 172.16.17.7/27 brd 172.16.17.31 scope global eth0
    inet 172.16.17.11/27 brd 172.16.17.31 scope global secondary eth0
    inet6 fe80::230:5ff:fefb:61cd/64 scope link
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0

ss2:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
172.16.17.0     0.0.0.0         255.255.255.224 U     0      0        0
eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0
eth0
0.0.0.0         172.16.17.1     0.0.0.0         UG    0      0        0
eth0

I follow this doc:
http://www.ultramonkey.org/3/topologies/hc-ha-lb-eg.html


Any ideas?

Thanks
Jordi


Advertencia importante
Este mensaje contiene informacion confidencial y/o privilegiada. Si usted no es 
el destinatario o una persona expresamente autorizada por el destinatario para 
recibir este mensaje no debe utilizar, copia, reenviar, distribuir o, en 
general, disponer en ninguna forma de la informacion incluida en el mismo. Si 
se hubiera recibido este mensaje por error, sirvase informar al emisor en tal 
sentido mediante una respuesta inmediata y borrelo, por favor. Gracias por su 
colaboracion. 

Important notice
This message contains confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, forward, disclose or take any action based on this message or any 
information herein. If you receive this message in error, please advise the 
sender immediately by reply e-mail and delete this message. Thank you for your 
cooperation. 



<Prev in Thread] Current Thread [Next in Thread>