[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Higher Grained Definition of IP Address Assignments?



Hello,
 
What you want sounds more like Load Balancing than HA Clustering.
 
I would suggest building a lvs load balancing cluster with 10.1.1.x as front-end IP and 10.1.2 as backend IP.
Make the LVS the default gateway for your 'cluster servers' (realservers), then configure 1-.1.1.50 on your LVS cluster as Virtual IP with the 10.1.2.x realservers as backend using NAT routing.
 
Documentation isa vailable at:
http://www.austintek.com/LVS/LVS-HOWTO/
or, more specifically:
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.LVS-NAT.html
 
LVS should be included in Red Hat Advanced Platform.
 
Yes, running a LoadBalancing cluster means 2 more servers and 2 more subscriptions, but it will allow for highly-available Load Balancing.
(implicitly allowing you to take realservers offline for maintenance)
 
 
Regards,
 
Kit Gerrits


From: linux-cluster-bounces redhat com [mailto:linux-cluster-bounces redhat com] On Behalf Of Dustin Henry Offutt
Sent: vrijdag 11 juni 2010 20:05
To: linux clustering
Subject: [Linux-cluster] Higher Grained Definition of IP Address Assignments?

Hello.

We have a scenario where a server would have one NIC on a 10.1.1.x network and multiple NICs on a 10.1.2.x network. The server requires the NICs on the 10.1.2 network each have an independent 10.1.2 network address assigned.

In converting this into an HA solution, we're reaching some difficulty in that if the Cluster Service is using a Cluster Resourced IP of 10.1.1.50, it gets assigned to the appropriate NIC on the cluster node.

However, the multple IP resources on the 10.1.2.x network are all getting assigned to a single NIC on the physical cluster node instead of spreading out across those 10.1.2.x NICs.

This particular cluster is Cluster Suite as released with RHEL5.5.

An example cluster.conf snippet regarding IP address resource:

<ip address=10.1.1.101 monitor_link="1">
<ip address=10.1.2.101 monitor_link="1">
<ip address=10.1.2.102 monitor_link="1">
<ip address=10.1.2.103 monitor_link="1">

Please imagine that these four IP resource addresses have been assigned to one cluster service.

Are there any more configurable parameters that can go in there? I would like to be able to assign these four address to four separate NICs on the cluster node.

Right now what happens is the first IP goes correctly to the cluster node's NIC that is assigned a 10.1.1 address, and though the cluster node's three other NICs are assigned 10.1.2 addresses, the three remaining IPs get bunched up one a single 10.1.2 NIC.

Bonding/aggregating isn't an option unfortunately.

Hope this makes sense...

Thank you,
Dusty

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.829 / Virus Database: 271.1.1/2930 - Release Date: 06/10/10 20:35:00


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]