Hallo Lars
> Uhm, what do you think should happen when you shutdown ha-2 - of
> course they stat on ha-1 in that case?
I meant that I shut it down temporarily and if it comes back again the
clones stay both on one node instead of going back again.
> I don't know what you're saying here ;-)
I said. That ressource_stickiness=0 does not work for me so I used a
location constraint to put ip:0 on ha-1 and ip:1 on ha-2 to get the
behaviour. But as I write this e-mail I realize that I misspelled
resource_stickiness.
> > <nvpair name="ressource_stickiness"
> > value="0" id="ressource-stickiness"/>
> With resource stickiness, this should be spread across two nodes?
Sure thing, if I manage to write it correctly. :-)
> This setting is wrong. globally_unique must be true for the cluster
> ip. Your configuration doesn't really work ;-)
Okay. That is the right moment to ask what globally_unique is about
anyway? I never got it. I just copy and pasted it.
> > <nvpair id="clusterip-clone-2" name="clone_max" value="2"/>
> You can drop this line, it defaults to the number of nodes anyway -
> unless, of course, you want to make it larger so you can do more fine
> grained load control later.
Thanks. I will do that.
> > <nvpair id="ia-ip0-4" name="mac" value="01:02:03:04:05:06"/>
> That's not a valid multicast MAC.
I see. I thought every mac address that starts with the first bit set to
one is a multicast MAC address. However I used an autogenerated, too.
And I got it working. But only on the same network. It seems that I have
to set a static entry on the default router to really get it working.
Thomas
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
