Hi Emilio, I'm either missing a key point or I'm totally lost, or maybe my brain is still on vacation from 2 weeks ago lol, perhaps it's just the terminology that your web interface is using...
Here is an example of what I have currently with linux HA, which is what I was trying to mimic on Zen. HA Box 1: Eth1: 172.15.35.1 255.255.255.252 <- back to back connection (x over cable) Eth2: 172.16.31.34 255.255.255.0 <- LAN Eht3: 10.10.10.234 255.255.255.0 <- BackLAN/Management Lan HA Box 2: Eth1: 172.15.35.2 255.255.255.252 <- back to back connection (x over cable) Eth2: 172.16.31.35 255.255.255.0 <- LAN Eht3: 10.10.10.235 255.255.255.0 <- BackLAN/Management Lan And with linux HA running Eth2:0 172.16.31.12 255.255.255.0 floats between Eth2 on box 1 and eth2 on box 2, with the cluster heartbeat traffic riding over the x over cable between the two nodes. With Zen, I have this Zen box 1: Eth0 : 142.x.x.243 255.255.255.0 <- LAN Eth1 : 10.10.10.70 255.255.255.0 <- Backlan/Management Lan Eth2 : 172.16.0.10 255.255.255.0 <- Dedicated Lan to Web servers for http Traffic Eth3 : 192.168.251.1 255.255.255.0 <- X over cable between zen nodes Zen Box 2: Eth0 : 142.x.x.240 255.255.255.0 <- LAN Eth1 : 10.10.10.71 255.255.255.0 <- Backlan/Management Lan Eth2 : 172.16.0.11 255.255.255.0 <- Dedicated Lan to Web servers for http Traffic Eth3 : 192.168.251.2 255.255.255.0 <- X over cable between zen nodes And what I wanted to have was my farm ip's Eth0:Farm1 142.x.x.211 255.255.255.0 Eth0:Farm2 142.x.x.207 255.255.255.0 Hop between the zen1 and zen2 nodes in the event of a failure, while the heartbeat cluster traffic use the x-over cable for its communication like in standard linux-HA The entire setup works minus the cluster... The Cluster service is insisting on using a VIP, but I'm not sure what that VIP is being used for ? I tried creating a VIP on my x-over network and at the moment I've lost all connectivity to my Zen2 box so that obviously isn't the right way of going about things :) Now I notice your cluster service takes over all the interfaces that aren't on the cluster interface and downs them making them the same on both boxes.. I can live with that although it would be nice to be able to exclude interfaces from the cluster config (complete wish list, not 100% necessary). This being said, what am I doing wrong? Do I need another ip on my LAN to use as the cluster ? Can anyone or Emilio turn the lights on for me :) Thanks, Dave -----Original Message----- From: Emilio Campos [mailto:[email protected]] Sent: August-08-11 4:23 PM To: [email protected] Subject: Re: [Zenloadbalancer-support] zen v1rc4 HI Dave. About your issue with the configuration, we going to add for the new release, a checking for search a farm configured on the cluster interface selected. By other hand, what do you mean with back-to-back?, a independent network?, comunication nodes over cross-over cable, for example? on this case, we added this property on rc4; you can read this line on my email o Implemented suggestion: GUI ip and Cluster ip doesn't have to be the same Or the same: one interface for GUI and other interface for cluster service. Please, confirm this issue. Thanks and Regards 2011/8/8 [email protected] <[email protected]>: > Thanks Emilio, > > I upgraded to rc4.. only one little issue.. it took one of my farm addresses > and turned it into a cluster ip. I just had to stop the cluster service to > get it to release it from its locked state. Other than that the upgrade was > fine. > > Just so I know, I'm assuming the clustering over a back-to-back interface is > not in this release, do you have any idea when that would be going to be > included? I'm just planning on when I am going to put my load-balancer into > production and that is the one feature that would be really nice, however if > it is going to be a while I will go ahead and go live without it. > > Thanks again. > > Dave > > -----Original Message----- > From: Emilio Campos [mailto:[email protected]] > Sent: July-31-11 6:11 PM > To: [email protected] > Subject: [Zenloadbalancer-support] zen v1rc4 > > Hi folks! > > We're glad to announce the next release candidate for Zen Load > Balancer v1rc4. This release is a hugh step to build a more stable > product, in which a lot of bugs detected these months are fixed. > > All of you that have already the v1rc1/2/3 installed, it's save to > upgrade from apt. Also, we've released a new Zen LB iso with the > latest package v1rc4, which is avaliable through the website > downloads. > > Here you have the changelog applied to this release: > > o Fix creation of network rules for every interface > o Delete rrd graphs for unavaliable network interfaces > o Fix Global Information section of Global view > o Improvement of CSS frontend > o Implemented suggestion: Add delete network interface icon for physical NICs > o Improved configuration process and panel of Cluster section > o Implemented suggestion: GUI ip and Cluster ip doesn't have to be the same > o Fix the RSA configuration between cluster nodes > o Fix replication service between cluster nodes > o Addition of 'Force sync configuration' button on the master cluster node > o Automatic insertion of apt network repositories > o The ZenLB ISO is able to be burned into a USB memory device like a CD > o Fix other BUGs detected on lab testing > o Fix problems with farmguardian and double quotes on execution scripts > > We give special thanks to every members of the list for report your > bugs detected and suggestions. > > -- > Load balancer distribution - Open Source Project > http://zenloadbalancer.sourceforge.net > Distribution list (subscribe): [email protected] > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Zenloadbalancer-support mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Zenloadbalancer-support mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support > -- Load balancer distribution - Open Source Project http://zenloadbalancer.sourceforge.net Distribution list (subscribe): [email protected] ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Zenloadbalancer-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Zenloadbalancer-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
