Thread: [SSI-devel] Ha-lvs
Brought to you by:
brucewalker,
rogertsang
From: Hinchley, S. <sco...@hp...> - 2003-07-23 16:55:40
|
I just did a build with Top-of-Tree yesterday (cvs)and most things seem to be there for HA-LVS, using the RedHat branched stuff. So HA-LVS started and is responding (used CVIP to log in with sshd), it read the config file with no problems. But I wanted to setup load balancing and was trying to look at some of the lvs stuff, the first thing I noticed was that /proc/cluster/lvs and /proc/cluster/ip_vs_portweight do not exist ( I started ha-lvs on node 4 'service ha-lvs start') on any node. I have not tried to stop node 1 (since with this cluster I have no filesystem failover), so don't know if failover work, will probably change the config in a sec so I can try that. Also when I tried to run the setport_weight command I got the following: [root@OSSI:1 root]# setport_weight --start-port=3D22 setport_weight OPTIONS --start-port=3Dvalue ( The start port ) --end-port=3Dvalue ( The end port ) --weight=3Dvalue ( The loadbalancing weight) [root@OSSI:1 root]# setport_weight --start-port=3D22 --end-port=3D22 setport_weight OPTIONS --start-port=3Dvalue ( The start port ) --end-port=3Dvalue ( The end port ) --weight=3Dvalue ( The loadbalancing weight) [root@OSSI:1 root]# setport_weight --start-port=3D22 --end-port=3D22 --weight=3D10 Invalid argument Let me know if there are things you want me to check, I am going to poke around my self, but what ever help you can give.... Thanks Laterness sjh |
From: Aneesh K. K.V <ane...@di...> - 2003-07-24 03:44:51
|
On Wed, 2003-07-23 at 22:25, Hinchley, Scott (HP) wrote: > Also when I tried to run the setport_weight command I got the following: > > [root@OSSI:1 root]# setport_weight --start-port=22 > setport_weight OPTIONS > --start-port=value ( The start port ) > --end-port=value ( The end port ) > --weight=value ( The loadbalancing weight) > [root@OSSI:1 root]# setport_weight --start-port=22 --end-port=22 > setport_weight OPTIONS > --start-port=value ( The start port ) > --end-port=value ( The end port ) > --weight=value ( The loadbalancing weight) > [root@OSSI:1 root]# setport_weight --start-port=22 --end-port=22 > --weight=10 > Invalid argument This is on my cluster. gfsserv:/home/kvaneesh# more /proc/cluster/lvs CVIP Address Node number xxx.xxx.xxx.xxx 1 gfsserv:/home/kvaneesh# more /proc/cluster/ip_vs_portweight Port Range Weight gfsserv:/home/kvaneesh# setport_weight --start-port=22 --end-port=22 --weight=10gfsserv:/home/kvaneesh# gfsserv:/home/kvaneesh# more /proc/cluster/ip_vs_portweight Port Range Weight 22 - 22 10 gfsserv:/home/kvaneesh# I guess you don't have ipvs built as a part of the kernel. You can look at the config.alpha to see what need to be turned on -aneesh |
From: Brian J. W. <Bri...@hp...> - 2003-07-24 06:29:11
|
Aneesh Kumar K.V wrote: > I guess you don't have ipvs built as a part of the kernel. You can look > at the config.alpha to see what need to be turned on Scott- I fixed the RH-based kernel to build IPVS statically. I think that will fix the problem. Brian |
From: Aneesh K. K.V <ane...@di...> - 2003-07-24 07:10:55
|
On Thu, 2003-07-24 at 11:59, Watson, Brian J. (HP) wrote: > Aneesh Kumar K.V wrote: > > I guess you don't have ipvs built as a part of the kernel. You can > look > > at the config.alpha to see what need to be turned on > > Scott- > > I fixed the RH-based kernel to build IPVS statically. I think that will > fix the problem. > Other things that would be needed is to disable ipvsadm(/etc/init.d/ipvsadm in all the run levels. All that it does and more is done by /etc/init.d/ha-lvs ) put ha-lvs( /etc/init.d/ha-lvs ) to be started in the needed run levels after networking and before xinetd/inetd. ( I didn't do it because i am not sure about the numbering ( SNNha-lvs ) On debian i have it as S20ha-lvs ). On debian i did update-rc.d -f ipvsadm remove update-rc.d ha-lvs defaults I guess we need to finalise on the nuber NN Add ha-lvs to rc.info ( /etc/rc.d/rc.info on redhat /etc/rc.info on debian ) Now the wonder of David's work !!!. If things seems to be not working say on debian invoke-rc.d ha-lvs stop invoke-rc.d ha-lvs start invoke-rc.d xinetd stop invoke-rc.d xinetd start. On all the cluster you will have xinetd running now. Now just say telnet <your-cluster-ip> -aneesh |