HP-UX 11i v3, which package shift to which node in case of failure

[Ghazanfar_1]

Hi Gurus,

There is a three nodes cluster and five packages are running.

I want to now that from where I can check that if any node fails then its package will shift to which node.

Second, can we configure it that in case of failure, package will shift to specific node.

Thanks

[Matti_Kurkela · Accepted solution]

First, use the cmgetconf command to get an ASCII copy of the current (binary) package configuration.

For example, if your package is named "pkg1":

cmgetconf -p pkg1 /tmp/pkg1.ascii

 (A common practice is to store the .ascii files in the package configuration directories. That is OK... but if you are not certain if the .ascii files are up to date or not, it is safest to use cmgetconf: that way you will always get an .ascii file that is 100% guaranteed to match the current configuration.)

Then read the configuration file. If the package is configured to run on any node and not care about which node it runs, you will see:

node_name          *

 If there are multiple node_name lines, the first line will identify the primary node (where the package is normally supposed to run) and the following node_name lines will identify the other allowed nodes and their order of preference.

For example, a package that was configured to run primarily on node1 but allowed to shift to node3 if it is available and to node2 if both node1 and node3 are not available, and never to node4, the node_name lines in the package configuration would be:

node_name node1
node_name node3
node_name node2

If you have an older version of Serviceguard, the configuration keywords may be in upper case, i.e. NODE_NAME instead of node_name.

With newer versions of Serviceguard, you can also configure package dependencies, e.g. package X must run on the same node as package Y, or package Z and package W must never run on the same node. These packages can also have priorities: if all the dependencies cannot be resolved, the priorities will be used to decide which packet is the least important and will be left in a "down" state.