On Wed, 04 Jun 2014, Miguel Angel Martin wrote:
> Package: ipvsadm
> Version: 1:1.26-1
> Severity: important
>
> Dear Maintainer,
>
> I was working in a cluster with pacemker and corosync and lvs to do load
> balancing.
> The cluster has two nodes, and lvs needs two virtual servers (IPv4,IPv6) and
> four real servers (2 IPv4,2 IPv6).
>
> I tried inserting rules both using ldirectord and ipvsadm directly.
> They were unable to add more than one real server per AF.
>
> The expectation was that 2 real servers were included per AF.
>
> Please, see raw ipvsadm commands below:
>
> root@debian:~# ipvsadm -L -n
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 192.168.1.10:389 rr
> -> 192.168.1.11:389 Route 1 0 0
> TCP [fc00:1::1]:389 rr
> -> [fc00:1::2]:389 Route 1 0 0
>
> root@debian:~# ipvsadm -A -t 192.168.1.10:389 -s rr
> Service already exists
>
> root@debian:~# ipvsadm --add-server --tcp-service 192.168.1.10:389
> --real-server 192.168.1.11
> Destination already exists
root@smithers ~ # ipvsadm -A -t 192.168.1.10:389 -s rr
root@smithers ~ # ipvsadm --add-server --tcp-service 192.168.1.10:389
--real-server 192.168.1.11
root@smithers ~ # ipvsadm --add-server --tcp-service 192.168.1.10:389
--real-server 192.168.1.12
root@smithers ~ # ipvsadm -Ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.1.10:389 rr
-> 192.168.1.11:389 Route 1 0 0
-> 192.168.1.12:389 Route 1 0 0
root@scyllaneu ~ # ipvsadm -A -t [fc00:1::1]:389 -s rr
root@scyllaneu ~ # ipvsadm --add-server --tcp-service [fc00:1::1]:389
--real-server [fc00:1::2]:389
root@scyllaneu ~ # ipvsadm --add-server --tcp-service [fc00:1::1]:389
--real-server [fc00:1::3]:389
root@scyllaneu ~ # ipvsadm --add-server --tcp-service [fc00:1::1]:389
--real-server [fc00:1::4]:389
root@scyllaneu ~ # ipvsadm -Ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.1.10:389 rr
-> 192.168.1.11:389 Route 1 0 0
-> 192.168.1.12:389 Route 1 0 0
TCP [fc00:1::1]:389 rr
-> [fc00:1::2]:389 Route 1 0 0
-> [fc00:1::3]:389 Route 1 0 0
-> [fc00:1::4]:389 Route 1 0 0
hmm, this works well here.
Alex
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
