HPE 9000 and HPE e3000 Servers
1827250 Members
2689 Online
109716 Solutions
New Discussion

cmcluster High Abalability

 
Alberto Hurtado
Frequent Advisor

cmcluster High Abalability

please send me information about this errors i have two hp-9000 k570 in a Cluster of MC-Service Guard. The system did not go away down and either was shutdown or reboot.
Your aid is thanked
______________________________________________
Sep 11 13:47:08 mvi902 cmcld[2438]: Communication to node mvi903 has been interrupted

Sep 11 13:47:08 mvi902 cmcld[2438]: Node mvi903 may have died

Sep 11 13:47:08 mvi902 cmcld[2438]: Attempting to form a new cluster

Sep 11 13:47:13 mvi902 cmcld[2438]: 2 nodes have formed a new cluster, sequence#101

Sep 11 13:47:13 mvi902 cmcld[2438]: The new active cluster membership is: mvi903(id=2), mvi902(id=1)

Sep 11 13:47:15 mvi902 vmunix: mpc_bindlwp: Overriding conflicting mandatory binding!

Sep 11 13:47:15 mvi902 vmunix: mpc_bindlwp: Migrating process 491 from processor 1 to processor 0!

Sep 11 13:47:39 mvi902 vmunix: mpc_bindlwp: Migrating process 499 from processor 2 to processor 0!

Sep 11 13:47:39 mvi902 vmunix: mpc_bindlwp: Overriding conflicting mandatory binding!

Sep 11 13:47:40 mvi902 above message repeats 2 times

Sep 11 13:47:39 mvi902 vmunix: mpc_bindlwp: Migrating process 499 from processor 2 to processor 0!

Sep 11 13:47:49 mvi902 vmunix: mpc_bindlwp: Overriding conflicting mandatory binding!

Sep 11 13:47:49 mvi902 vmunix: mpc_bindlwp: Migrating process 567 from processor 3 to processor 0!

Sep 11 16:20:25 mvi902 cmcld[2438]: Communication to node mvi903 has been interrupted

Sep 11 16:20:25 mvi902 cmcld[2438]: Node mvi903 may have died

Sep 11 16:20:25 mvi902 cmcld[2438]: Attempting to form a new cluster

Sep 11 16:20:29 mvi902 cmcld[2438]: Obtaining Cluster Lock

Sep 11 16:20:30 mvi902 cmcld[2438]: Turning off safety time protection since the cluster

Sep 11 16:20:30 mvi902 cmcld[2438]: now consists of a single node. If ServiceGuard

Sep 11 16:20:30 mvi902 cmcld[2438]: fails, this node will not automatically halt

Sep 11 16:20:32 mvi902 cmcld[2438]: Attempting to adjust cluster membership

Sep 11 16:20:35 mvi902 cmcld[2438]: Enabling safety time protection

Sep 11 16:20:35 mvi902 cmcld[2438]: Clearing Cluster Lock

Sep 11 16:20:37 mvi902 cmcld[2438]: Timed out node mvi903.

Sep 11 16:20:37 mvi902 cmcld[2438]: Attempting to adjust cluster membership

Sep 11 16:20:41 mvi902 cmcld[2438]: Clearing Cluster Lock

Sep 11 16:20:46 mvi902 cmcld[2438]: 2 nodes have formed a new cluster, sequence #104

Sep 11 16:20:46 mvi902 cmcld[2438]: The new active cluster membership is: mvi902 (id=1), mvi903(id=2)

3 REPLIES 3
Bhuvaneswari Selvaraj
Valued Contributor

Re: cmcluster High Abalability

Post this in the "System Administration" category of this forum, there you may get answers from people doing system administration
M.Kantharuban
Advisor

Re: cmcluster High Abalability

Hi
Looks like the heartbeat is not stable b/w cluster nodes.
There must be two reasons for this
1.node timeout is set too low, check the
NODETIMEOUT parameter in /etc/cluster/cmclconf.ascii and if it is 2000000 [2 sec ] increase it to 5 - 8 secs
2.check the connectivity reliablity of heartbeat b/w nodes

Regds
Ruban
Bernhard Mueller
Honored Contributor

Re: cmcluster High Abalability

Alberto,

as stated in the previous post, if this happens frequently and/or your network gets clogged occasionally, and/or you have only 10MBit interfaces, you should set the the NODE_TIMEOUT in your cluster to something like 8-10 Seconds (at least 5).
8 second would be a value of "8000000"
It *may* help.

Second, the other message with the mpc_binding is someting that - for HP-UX 11.0 - should be resolved with the base patch PHKL_18543. So you might consider installing a couple of patches.

Regards,
Bernhard