A thousand sincere apologies.
Unfortunately, tracing through the ip script with this attribute enabled, I can see that this has absolutely no effect.
Sorry to get your hopes up.
On Mon, Jun 14, 2010 at 8:18 AM, Martin Waite <Martin Waite datacash com> wrote:
/usr/share/cluster/ip.sh appears to perform the link-monitoring in the "status" command, which is called periodically. I don't know that either rgmanager or cman or other cluster software are directly involved in that.
The "ip" configuration already supports an "interface" attribute:
<ip address="192.168.2.120" interface="eth0" monitor_link="1"/>
the info, but indeed what we need is HA.
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:
or, more specifically:
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)