Here is the configuration: [EMAIL PROTECTED] 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
Where 192.168.1.240 is VIP of load balancer, .82 is real ip of load balancer, .253 is real server ip address. Thanks, Venkatesh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sameer Garg Sent: Monday, March 10, 2008 12:47 PM To: LinuxVirtualServer.org users mailing list. Subject: Re: [lvs-users] Simple LVS cluster Venkaesh, Please be more descriptive of the problem. Have you tried running a sniffer to see where your packets are getting lost? Post your config files. ARP issues can arise in lvs-tun setup too but since you are using only one machine I doubt if that is the problem. Sameer On Mon, Mar 10, 2008 at 12:37 PM, Venkatesh R <[EMAIL PROTECTED]> wrote: > > Dear all, > > I have to setup simple RHEL3 cluster, having one load balancer and a > real server; Method of packet forwarding is IP tunneling. I have chosen > Ultra monkey as the source for LVS because it supports IP tunneling. I > have followed the instructions given by Ultra monkey for installation > and configuration. But, I could not see any LVS functionality working as > on today with my test setup. I can see sometimes the load server > receives the SIP messages, but not the real server. I doubt on the ARP > issue with IP tunneling. I could not find the suitable patch code for > ARP issue for RHEL3. If anyone knows about this, please do share with > me. > > > > Thanks in advance. > > Regards, > > Venkatesh > > > > > > > > > > ======================================================================== ==================================================== > > 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.techmahind ra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahind ra.com/Disclaimer.html</a> internally within Tech Mahindra. > > ======================================================================== ==================================================== > _______________________________________________ > LinuxVirtualServer.org mailing list - [email protected] > Send requests to [EMAIL PROTECTED] > or go to http://lists.graemef.net/mailman/listinfo/lvs-users > _______________________________________________ LinuxVirtualServer.org mailing list - [email protected] Send requests to [EMAIL PROTECTED] 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. ============================================================================================================================
ldirectord.cf
Description: ldirectord.cf
ha.cf
Description: ha.cf
_______________________________________________ LinuxVirtualServer.org mailing list - [email protected] Send requests to [EMAIL PROTECTED] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
