topic Re: MC/SG pkg startup priority in Operating System - HP-UX

MC/SG pkg startup priority

Andrew_80 — Wed, 02 Jun 2004 08:56:05 GMT

Hello everyone,
I have 2 Pkg's on the cluster (PRI & SEC) and the SEC pkg depends on the PRI pkg to be up and running, so in case of a failover I need the SEC pkg to wait until the PRI is up and running. Is there a way to do that ?

Re: MC/SG pkg startup priority

G. Vrijhoeven — Wed, 02 Jun 2004 09:00:11 GMT

Hi,

Not jet. What you can do is create a script that is called in the customer_defined_run_cmds that checks if PRI is up before running the next script.

Something like
While VAR=0
do
cmviewcl -p | grep -q running
if [ $? -eq 0 ]
then
VAR=1
else
VAR=0
sleep 5
fi
done

HTH,

Gideon

Re: MC/SG pkg startup priority

Ashwani Kashyap — Wed, 02 Jun 2004 09:10:22 GMT

Package dependencies are not built in yet in service guard , however the control scripts provide enough flexibiity to build your own dependencies .

YOu can script anything in the package control file in hte customer_defined_run_cmds section . You can put enough sleep interval there on SEC package to allow primary to come up before the SEC is started , or you can loop there awaitng for the PRI to complete the startup before starting the SEC .

Re: MC/SG pkg startup priority

Geoff Wild — Wed, 02 Jun 2004 09:26:48 GMT

You will have to configure it in your customer_defined_run_cmds.

I've attached a rather extensive example.

Rgds...Geoff

Re: MC/SG pkg startup priority

Jose Mosquera — Wed, 02 Jun 2004 09:48:33 GMT

Hi,

In the past we have configured our two nodes configuration in this form. Because the secondary node was an "K" class and starting-up process was too large that primary node, to solve this we configured an awiting time for the cluster reformation, no package.
This parameter is NODE_TIMEOUT, look for it into /ect/cmcluster/cluster.conf. Pls note that this time is in microseconds. A little explanation can be found in this file.

Rgds.

Re: MC/SG pkg startup priority

Emil Velez — Thu, 03 Jun 2004 07:07:32 GMT

You can implement package dependencies using EMS.

In the SEC package config file you put the following

RESOURCE_NAME /cluster/package/package_status/PRI
RESOURCE_POLLING_INTERVAL 30
RESOURCE_UP_VALUE = UP

Unfortunately you have to stop the cluster to change EMS stuff. Also make sure you have good ems and check the presence of the resources with the resls command

resls /
resls /cluster
resls /cluster/package

Good luck