[lvs-users] sip persistence engine

Aron Wahl yaron.wahl at gmail.com
Wed Apr 24 11:49:51 BST 2013


Hello,

I am using  ipvsadm v1.26 2008/5/15 (compiled with popt and IPVS v1.2.1) on
a Ubuntu server with kernel 3.5.0-17-generic on a x86_64 platform

I have the following network config
eth0      Link encap:Ethernet  HWaddr 00:0c:29:d7:cd:a6
          inet addr:192.168.49.16  Bcast:192.168.49.255  Mask:255.255.255.0


And using the following ipvsadm config
-A -u ubuntusrv.localdomain:sip -s rr -p 40 pe sip
-a -u ubuntusrv.localdomain:sip -r 192.168.49.7:sip -m -w 1
-a -u ubuntusrv.localdomain:sip -r 192.168.49.17:sip -m -w 1

When I make a sip call to 192.168.49.16 (ubuntusrv.localdomain), I see the
following 2 connections being set up

 ipvsadm -Lcn --persistent-conn
IPVS connection entries
pro expire state       source             virtual            destination
     pe name          pe_data
UDP 00:49  UDP         172.29.9.35:0      192.168.49.16:5060
192.168.49.7:5060 sip
43D826387A240B39D11C000BCB4977CE19396 at 172.29.9.35
UDP 04:41  UDP         172.29.9.35:5060   192.168.49.16:5060
192.168.49.7:5060

Apparently because of the 2nd entry in the table
UDP 04:41  UDP         172.29.9.35:5060   192.168.49.16:5060
192.168.49.7:5060
All my successive calls to 192.168.49.16 are going to the same real server,
although the sip call id is different.
Since I am using Round Robin scheduler, I would have expected every call to
go to another real server.

How come this plain UDP entry is created? I would have expected only the
entry with the sip pe data

Thanks

Yaron


More information about the lvs-users mailing list