Hi,
please try either lower-cased host/node names or use the patch I sent
yesterday. The problem is that heartbeat uses the lower-cased hostnames
as nodenames and membership list in the CCM. EVMS compares
case-sensitive. This means evms says your cluster node acquiring the
private container is not
Hi Yan,
Thanks a lot for your help. I took out the evmsSCC
resource from the scenario, but I did not see any difference in the
system behavior, then I followed your suggestion and I manually tested
the EVMS commands from the CLI while both the nodes where in stand-by,
and I actually rea
FWIW, the "Exploring HASF" document does NOT use private containers. It
uses shared containers, so you will need to adjust some things, in
particular the type of CSM container (shared -> private), and use the
evms_failover RA instead of the evmsSCC RA.
Yan
Chris wrote:
> Hi Andrew,
>
Andrew Beekhof wrote:
>
> On Nov 21, 2007, at 10:11 AM, Christian Zemella wrote:
>
>> Hi All,
>>Anybody out there managed to have EVMS container resources
>> properly failing over in a 2 node Heartbeat 2 cluster running on SLES
>> 10 SP1 ?
>
> I believe so... have you read the documentat
Hi Andrew,
Thanks for your reply.
Yes, I got that doc, however it goes through the integration of OCFS2
and Heartbeat2 using the command line, while my test are with the
usage of reiserfs (or ext3) and the hb_gui.
I mean, if the resource configuration in order to have the private
On Nov 21, 2007, at 10:11 AM, Christian Zemella wrote:
Hi All,
Anybody out there managed to have EVMS container resources
properly failing over in a 2 node Heartbeat 2 cluster running on SLES
10 SP1 ?
I believe so... have you read the documentation below?
http://wiki.novell.com/imag
Hi All,
Anybody out there managed to have EVMS container resources
properly failing over in a 2 node Heartbeat 2 cluster running on SLES
10 SP1 ?
In my lab I can only start and stop the resource on the node that has
the container assigned within evms, while if I shut down that node,
the fa
