HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 67 (of 108)
Chapter 15 Serviceguard
October 29, 2013
# cmmodpkg -e <package-name>
If after cleaning up the node on which the timeout occurred it is desirable to have that
node as an alternate for running the package, remember to re-enable the package to run
on the node:
# cmmodpkg -e -n <node-name> <package-name>
Package Movement Errors
Package fail to move to an adoptive node for these reasons:
 The initial package halt failed
 Package startup occurred on the target node, but something failed during package startup.
 Package startup is not allowed on the target node
The first two causes require inspection of the package log and maybe the syslog. The last cause requires
inspection of the AUTO_RUN and Node_Switching flags, which requires ‘cmviewcl –v –p <pkg_name>’.
Enable AUTO_RUN using ‘cmmodpkg –e <pkg_name>’ and enable Node_switching using ‘cmmodpkg –e
–n <nodename> <pkg_name>’
Network issues
Here we will first cover Node and Network Failures which are normal action of Serviceguard
and then discuss how to troubleshoot “real” network Problems.
Node and Network Failures
These failures cause Serviceguard to transfer control of a package to another node. This is the
normal action of Serviceguard, but you have to be able to recognize when a transfer has taken
place and decide to leave the cluster in its current condition or to restore it to its original
condition.
Possible node failures can be caused by the following conditions:
 HPMC - ( High Priority Machine Check) is a system panic caused by a hardware error.
 TOC – admin manually forced a transfer of control to the TOC/dump vector in
microcode.
 Panics – kernel malfunction, generating a memory dump
 Hangs – Serviceguard will trigger a TOC.