Your clone is starting on the same server:

   failover-ip2:0    (ocf::heartbeat:IPaddr2):    Started fileserv2
     failover-ip2:1    (ocf::heartbeat:IPaddr2):    Started fileserv2

You are missing colocation definitions, and need interleave=true.

Nick.



On Wed, Nov 16, 2011 at 11:46 AM, Cindy Murdock Ames <[email protected]> wrote:
> Hello,
>
> I have two IP addresses I'm trying to clone with IPaddr2, and it doesn't
> seem to be working correctly.
>
> Here's my config:
>
> node fileserv1 \
>     attributes standby="off"
> node fileserv2 \
>     attributes standby="off"
> primitive failover-ip1 ocf:heartbeat:IPaddr2 \
>     params ip="192.168.10.1" cidr_netmask="24"
> broadcast="192.168.10.255" nic="eth1"
> clusterip_hash="sourceip-sourceport-destport" \
>     op monitor interval="30s"
> primitive failover-ip2 ocf:heartbeat:IPaddr2 \
>     params ip="192.168.30.1" cidr_netmask="24"
> broadcast="192.168.30.255" nic="eth2"
> clusterip_hash="sourceip-sourceport-destport" \
>     op monitor interval="30s"
> clone ip1-clone failover-ip1 \
>     meta globally-unique="true" clone-max="2" clone-node-max="2"
> target-role="Started"
> clone ip2-clone failover-ip2 \
>     meta globally-unique="true" clone-max="2" clone-node-max="2"
> property $id="cib-bootstrap-options" \
>     dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \
>     cluster-infrastructure="openais" \
>     expected-quorum-votes="2" \
>     stonith-enabled="false" \
>     last-lrm-refresh="1321390656"
>
> When I run 'ifconfig -a' to check the IP addresses on each node, on
> fileserv1 eth1 has its assigned IP but eth2 does not.  On fileserv2 both
> interfaces have their assigned IP.  On fileserv1 'iptables -L' shows a
> CLUSTERIP rule for just eth1, but on fileserv2 it shows a rule for both
> interfaces.  However, 'crm status' on each node shows that both clone
> sets are started:
>
> Last updated: Wed Nov 16 11:33:12 2011
> Stack: openais
> Current DC: fileserv2 - partition with quorum
> Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
> 2 Nodes configured, 2 expected votes
> 2 Resources configured.
> ============
>
> Online: [ fileserv1 fileserv2 ]
>
>  Clone Set: ip1-clone (unique)
>      failover-ip1:0    (ocf::heartbeat:IPaddr2):    Started fileserv1
>      failover-ip1:1    (ocf::heartbeat:IPaddr2):    Started fileserv2
>  Clone Set: ip2-clone (unique)
>      failover-ip2:0    (ocf::heartbeat:IPaddr2):    Started fileserv2
>      failover-ip2:1    (ocf::heartbeat:IPaddr2):    Started fileserv2
>
> If I put fileserv2 in standby mode, both IPs shift to fileserv1.  If I
> bring fileserv2 back online, the IPs stay on fileserv1 and do not shift
> back to both nodes.  If I put fileserv1 in standby mode, the IPs both
> shift to fileserv2, and if I bring fileserv1 back online, eth1 shifts to
> both nodes, but eth2 is only up on fileserv2.
>
> BTW, this is on Debian Squeeze.
>
> Is this the expected behavior, am I doing something wrong, or is it a
> bug?  This is my first project using clustering, so I'm a relative
> noob.  Any help would be greatly appreciated!
>
> Regards,
> Cindy
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Cindy Murdock Ames
> IT Services Director
> Meadville Public Library    | CCFLS
> http://meadvillelibrary.org | http://ccfls.org
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to