|
Hi,
I've been playing with the IPVS sync daemon a little lately, and am having
some problems. I'm rather curious about the expected behaviour and
configuration of the sync daemon, as it doesn't appear to be working for
me at all :) I've consulted the docs, but they are somewhat vague as to
what is expected of me, and as to what I can expect, other than to simply
start the daemon.
1. When you configure the sync daemon on the master, I'm assuming you do
the following:
1. Set up virtual server as normal --
ipvsadm -A ipvsadm -A -t 172.16.4.230:110
ipvsadm -a -t 172.16.4.230:110 -r 10.0.10.10
2. Start sync daemon
ipvsadm --start-daemon master --mcast-interface eth1
2. On the backup, I'm assuming you do the same thing, except to specify
backup.
1. Set up virtual server as normal --
ipvsadm -A ipvsadm -A -t 172.16.4.230:110
ipvsadm -a -t 172.16.4.230:110 -r 10.0.10.10
2. Start sync daemon
ipvsadm --start-daemon backup --mcast-interface eth1
On the master:
master# ipvsadm -L -n
IP Virtual Server version 0.9.4 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 172.16.4.230:110 wlc
-> 10.0.10.10:110 Local 1 10 0
When I run tcpdump on the slave, I do see the multicasts:
slave# tcpdump -i eth1 -n -p
11:42:04.323917 M 172.16.4.230.32768 > 224.0.0.81.8848: udp 244 (DF) [ttl 1]
But on the slave, I don't see any connections:
slave# ipvsadm -L -n
IP Virtual Server version 0.9.4 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 172.16.4.230:110 wlc
-> 10.0.10.10:110 Route 1 0 0
So basically, I am asking:
1. Did I theoretically configure everything correctly
2. Should the backup server list connections its received?
If not, how do I verify that it's updated its internal tables?
Thanks,
Kyle Sparger
-----------------------------------------------------------------------
PS: Here's my configuration
director# 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
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:55:54:7f:8c brd ff:ff:ff:ff:ff:ff
inet 172.16.4.230/16 brd 172.16.4.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:55:54:7f:8d brd ff:ff:ff:ff:ff:ff
inet 10.0.10.10/24 brd 10.0.10.255 scope global eth1
eth0 goes to net
eth1 is crossover to eth1 of backup
backup# 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
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:55:54:7f:8e brd ff:ff:ff:ff:ff:ff
inet 172.16.4.231/24 brd 172.16.4.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:55:54:7f:8f brd ff:ff:ff:ff:ff:ff
inet 10.0.9.10/24 brd 10.0.9.255 scope global eth1
eth0 goes to net
eth1 is crossover to eth1 of master
director# ipvsadm -A -t 172.16.4.230:110
director# ipvsadm -a -t 172.16.4.230:110 -r 10.0.10.10
director# ipvsadm --start-daemon master --mcast-interface eth1
backup# ipvsadm -A -t 172.16.4.230:110
backup# ipvsadm -a -t 172.16.4.230:110 -r 10.0.10.10
backup# ipvsadm --start-daemon backup --mcast-interface eth1
And, to verify connectivity over eth1:
director# ping -c1 10.0.9.10
PING 10.0.9.10 (10.0.9.10) from 10.0.10.10 : 56(84) bytes of data.
64 bytes from 10.0.9.10: icmp_seq=0 ttl=255 time=1.098 msec
--- 10.0.9.10 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.098/1.098/1.098/0.000 ms
backup# ping -c1 10.0.10.10
PING 10.0.10.10 (10.0.10.10) from 10.0.9.10 : 56(84) bytes of data.
64 bytes from 10.0.10.10: icmp_seq=0 ttl=255 time=1.015 msec
--- 10.0.10.10 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.015/1.015/1.015/0.000 ms
|
