[Pacemaker] VIP on Active/Active cluster
Jake Smith
jsmith at argotec.com
Sun May 13 14:36:59 UTC 2012
clone-node-max="2" should only be one.
How about the output from crm_mon -fr1
And ip a s on each node?
Jake
----- Reply message -----
From: "Paul Damken" <zen.suite at gmail.com>
To: <pacemaker at oss.clusterlabs.org>
Subject: [Pacemaker] VIP on Active/Active cluster
Date: Sat, May 12, 2012 2:49 pm
> Hello,
> >
> > I wonder if someone can light me on how to handle the following cluster
> > scene:
> >
> > 2 Nodes Cluster (Active/Active)
> > 1 Cluster managed VIP - RoundRobin ?
> > SAN Shared Storage (DLM CLVM O2CB) = "OCFS2"
> >
> > My main question is, can one VIP serve 2 nodes?
> >
> > Thanks in advance.
>
> Yes. But I would use the "localnode" feature of the Linux Virtual Server.
> The
> LVS is a real loadbalancer that offers more features than the clustered IP
> address of the normal cluster.
>
> --
> Dr. Michael Schwartzkopff
> Guardinistr. 63
> 81375 M?nchen
>
> Tel: (0163) 172 50 98
>
How could do so?
I tried setting up VIP + Clone VIP and once resource is cloned and started
on both nodes, it is no longer
reachable.
crm(live)configure# show
node havc1
node havc2
primitive failover-ip1 ocf:heartbeat:IPaddr2 \
params ip="192.168.1.20" cidr_netmask="24"
broadcast="192.168.1.255" nic="eth0" clusterip_hash="sourceip-sourceport" \
op monitor interval="20s"
clone ip1-clone failover-ip1 \
meta globally-unique="true" clone-max="2" clone-node-max="2"
target-role="Started"
property $id="cib-bootstrap-options" \
dc-version="1.1.2-2e096a41a5f9e184a1c1537c82c6da1093698eb5" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
stonith-enabled="false" \
last-lrm-refresh="1336841278"
rsc_defaults $id="rsc-options" \
resource-stickiness="100"
-------------------------------------------------------------------------
Chain INPUT (policy ACCEPT)
target prot opt source destination
CLUSTERIP all -- anywhere 192.168.1.20 CLUSTERIP
hashmode=sourceip clustermac=81:30:6E:B7:6D:AF total_nodes=2 local_node=1
hash_init=0
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Any idea what is wrong, or causing this to not being reachable once both
IPaddr2 RA start on both nodes?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120513/d3b8ed48/attachment.htm>
More information about the Pacemaker
mailing list