[lvs-users] Simple LVS cluster

[Venkatesh R]

I have chosen SIP as a tester for LVS functional testing. The output of
ipvsadm is same as below email. I could not see any difference when the
connection is made. 
Do you suggest any other easiest way of testing LVS?
Regards,

Venkatesh


-----Original Message-----
From: lvs-users-bounces at linuxvirtualserver.org
[mailto:lvs-users-bounces at linuxvirtualserver.org] On Behalf Of Graeme
Fowler
Sent: Tuesday, March 11, 2008 3:33 PM
To: LinuxVirtualServer.org users mailing list.
Subject: Re: [lvs-users] Simple LVS cluster

On Mon, 2008-03-10 at 13:47 +0530, Venkatesh R wrote:
> [root at emu82 ha.d]# /sbin/ipvsadm -L -n
> IP Virtual Server version 1.0.8 (size=65536)
> Prot LocalAddress:Port Scheduler Flags
>   -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> UDP  192.168.1.240:5060 wlc persistent 600
>   -> 192.168.1.82:5060            Local   1      0          0         
>   -> 192.168.1.253:5060           Tunnel  1      0          0   

...which all looks perfectly fine. When someone tries to make a UDp
connection to port 5060 on the VIP, what do you see? What's the output
from ipvsadm when that's happening?

Note also that SIP uses both TCP and UDP (assuming, from port 5060, that
you're trying to setup a SIP farm). It uses TCP for the registration and
command channel, UDP for data. The UDP part can move around dramatically
too, it isn't always on UDP/5060 (in fact it almost never is). Sip is a
beast to load balance.

Graeme


_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users at LinuxVirtualServer.org
Send requests to lvs-users-request at LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

============================================================================================================================
 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================