Service Guard Configuration Won't Apply

[GBR]

Hi,

I have to re-apply my Servie Guard (A.11.16.00) configuration to all my nodes in the cluster (4 nodes). The following command to test the configuration runs fine:

> cmcheckconf -v -C cmclconf.ascii -p pkg.inf

The next command to apply the configuration seems to hang and never runs to completion:

> cmapplyconf -v -C cmclconf.ascii -p pkg.inf

I didn't halt any currently running packages and I didn't turn off any Service Guard services. Any ideas? Should I turn off any Service Guard services? Do I need to halt any packages?

Thanks,
GBR

[Ganesan R]

Hi,

How the changes will get into cluster binary file if you try to apply the changes when the cluster is up and running?

It is must to stop all the packages and cluster whenever you are doing any modifications and applying on cluster and package config files.

[melvyn burnard]

It should tell you that certain things need to be halted if you are making changes that require halting.
What changes have you made?
Are they just to the cluster and not to any packages?
or is it just to a package or packages?

[GBR]

Okay, thanks. I am very new to Service Guard. I know how to halt packages, but I don't know how to turn off "Servie Guard" so to speak.

I want to apply changes to package configurations only and/or add new packages. It's not necessary to modify the cluster configuration, that will remain the same.

GBR

[Ganesan R]

Hi,

If you want to modify the package configuration(adding new package or edit existing), you should

halt the packages and halt the cluster.
Do the modifications.
Check for syntax errors if any
Apply the config

Then only all the changes will be compiled and new cluster binary will get created and distributed to all the nodes.

[GBR]

Great, that is helpful. I will try that once I get root access to the server this evening.

How do I halt the cluster?

GBR

I will submit points once I have tried a few of these suggestions.

Also, if there are any other suggestions please let me know.

[Ganesan R]

Hi,

Steps to halt the cluster. First you should halt the running packages then halt the node one. Finally you can halt the cluster.

1.Halt the packages
#cmhaltpkg -v

2.Halt the node.
#cmhaltnode -v

3.Halt the cluster
#cmhaltcl -v

[melvyn burnard · Accepted solution]

If you are only changing a package, you do NOT need to halt the cluster, only the package.
Simply cmhaltpkg ,
use cmapplyconf -v -P

[GBR]

What about creating a new package? Does anything special need to be done?

[Ivan Krastev]

Just follow the steps - http://docs.hp.com/en/B3936-90100/ch06s01.html

regards,
ivan

[Ganesan R]

Hi,

The below are the general steps normally we will follow. But I would recommand you to go through the HP official document to do this kind of activities. There are many documents available related to this.

=>Create cluster VG for that package
=>After creating the VG create a map file by exporting in preview mode
=>copy the map file to other nodes where the pkg should be failover
=>import the vg by using map file
=>you can deactivate the vg on first node and try activating on other nodes

=>make a pkg directory under /etc/cmcluster
#mkdir /etc/cmcluster/pkg1

=>Create pkg config template
#cmmakepkg â p /etc/cmcluster/pkg1/pkg1conf.ascii

Edit the package configuration template file
Package Name : pkg1
NODE NAMES:
Package IP :
RUN SCRIPT : /etc/cmcluster/pkg1/control.sh
STOP SCRIPT: /etc/cmcluster/pkg1/control.sh
create pkg control script template

=>#cmmakepkg â s /etc/cmcluster/pkg1/control.sh
Edit the control script to enter the following info
CLUSTER VG :
IP[0] :
IP[1] :
LV â s and their mount points

=> distribute the control script and config file to other nodes

=>Check the conf file for any errors
#cmcheckconf -v -P /etc/cmcluster/pkg1/pkg1conf.ascii
=>Apply the conf file
#cmapplyconf â v -P /etc/cmcluster/pkg1/pkg1conf.ascii

[GBR]

Closed. I now have the information I need to play around.