topic Re: kill cmcld on adoptive node, but the pkg is not failed over to Primary node? in Operating System - HP-UX

kill cmcld on adoptive node, but the pkg is not failed over to Primary node?

Hanry Zhou — Sat, 07 Jan 2006 10:16:43 GMT

If I kill -9 cmcld on primary node, the node will be panic, and the pkg will be failed over to adoptive node. That is verified. But, what if I kill -9 cmcld on the adoptive node? The test shows that the package is not failed over to the primary node, and the adoptive node is not in panic. Why? and further more, I could not manually cmruncl on primary node at this point. why?

Re: kill cmcld on adoptive node, but the pkg is not failed over to Primary node?

Steven E. Protter — Sat, 07 Jan 2006 18:11:34 GMT

Shalom Hanry,

Most likely the problem is in the package configuration. Its not set up to fail back to primary.

Failover is totally controlled by the package, doing something to the node merely triggers it.

Check the package configuration.

SEP

Re: kill cmcld on adoptive node, but the pkg is not failed over to Primary node?

Sivakumar TS — Sun, 08 Jan 2006 03:00:00 GMT

Dear Hanry,

Please use

#cmviewcl -v -p

to check the NODE SWITCHING has been enabled for both the nodes. If any node is node enabled for NODE SWITCHING then it wont be able to receive the package for either failover or failback.

You can enable this by

#cmmodpkg -e -n >packagename>

and to enable the global package switching
you can use

#cmmodpkg -e

With Regards,

Siva.

Re: kill cmcld on adoptive node, but the pkg is not failed over to Primary node?

Deoncia Grayson_1 — Sun, 08 Jan 2006 11:52:10 GMT

Normally after you do a manual failover, in this case you killed a process that initiated a failover, it disables automatic node failover, which can be verifed by doing

cmviewcl -v

in order for this package to be failed back over automatically you have to enable automatic package switching:

cmmodpkg -e
otherwise you will have manually restart the package on the secondary node.

Re: kill cmcld on adoptive node, but the pkg is not failed over to Primary node?

Tvs — Mon, 09 Jan 2006 03:13:15 GMT

Hi Hanry .

cmcld daemon is used to determine cluster membership by sending heartbeat messages to other cmcld deamons on the other nodes within the service gurad cluster.this deamon sets a safety timer in the kernel which is used to detect kernel hangs. if the timer is not reset periodically by cmcld. the kernel will cause the a system TOC. so if u killing the deamon it may cause the system to reboot ( normally ).

and the package switching is depend upon the package configuration.

check it with
#cmviewcl -V

if you want to enable on a single node
# cmmodpkg -n node name -p pkg name
or u wnat to enable globally
#cmmodpkg -e -p pkg name

try to execute

# cmrunnode ( the primmery node )

for adding the primmery node in the running cluster .

and iam not sure why the adoptive node not gone for TOC.. after killing the cmcld process..

we need to take help from others

Regards

Tvs