Need to change cluster configuration

[Sreer]

Hi Gurus,

I have a requirement for a cluster configuration to avoid restarting packages with out deleting cluster package !

mean halt the package + modify cluster configuration to avoid the pkg restart in case of cluster reboot/node reboot.

"stopping packages (halt)
modyfying cluster configuration to avoid restart of packages"


is it possble? with out deleting the package?

thanks in advance.

Rgds
Sree

[Sajjad Sahir · Accepted solution]

Dear Sree

Please read the attachment which will help configuring reconfiguring cluster and removing and adding packages, a lot of similar things are there, please see it.

thanks and regards

Sajjad Sahir

[Viktor Balogh]

Hi Sreer,

The answer is: it depends. Which version of Serviceguard do you have?

# cmversion

The more newer your SG is, the more property you can configure in SG online. For this, you should figure out your SG version, and look for the appropriate SG document on BSC to get the answer.

Regards,
Viktor

[Sreer]

Hi,

My SG version is ==> A.11.16.00

I reached a work around:

1. Halt the PKG
2. edit the package configuration file

change AUTO RUN NO

3. check package conf files using:

cmcheckconf -v -P /etc/cmcluster/package_name/pkg.conf

4. apply the changes:
cmapplyconf -v -P /etc/cmcluster/package_name/pkg.conf

Pls correct me in case Iam wrong in accordance with the SG version.

Rgds
Sree

[Viktor Balogh]

Sreer,

the process you described was correct.

Regards,
Viktor

[Sreer]

Hi Sajjad & VIKTOR,

Thanks a lot for your help !!

@ Sajjath the document you provided is excellent I was waiting for a such one!!!

Do you have any such cookbook for VPAR/NPAR environment?If so pls send to us.

Thanks again :-)

Rgds
Sree

[P Arumugavel]

hi,

VPAR admin guide
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02029116/c02029116.pdf

NPAR config guide:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01868281/c01868281.pdf

Rgds...

[Sreer]

Hello Gurus,

Iam in my work to modify few packages..

1. Halt the PKG
2. edit the package configuration file

change AUTO RUN NO

3. check package conf files using:

cmcheckconf -v -P /etc/cmcluster/package_name/pkg.conf

4. apply the changes:
cmapplyconf -v -P /etc/cmcluster/package_name/pkg.conf

here the issue is the modified package.conf file is not getting distributed to all other cluster nodes even after using cmapplyconf !!


Could you pls support.thanks in advance.

n4sp1 $ root:/etc/cmcluster/prda3501# cmcheckconf -v -P /etc/cmcluster/prda3501/prda3501.conf

Checking existing configuration ... Done
Gathering configuration information ... Done
Parsing package file: /etc/cmcluster/prda3501/prda3501.conf.
Package prda3501 already exists. It will be modified.
Maximum configured packages parameter is 80.
Configuring 37 package(s).
43 package(s) can be added to this cluster.
200 access policies can be added to this cluster.
Modifying the package configuration for package prda3501.

Verification completed with no errors found.
Use the cmapplyconf command to apply the configuration.
n4sp1 $ root:/etc/cmcluster/prda3501# cmapplyconf -v -P /etc/cmcluster/prda3501/prda3501.conf

Checking existing configuration ... Done
Gathering configuration information ... Done
Parsing package file: /etc/cmcluster/prda3501/prda3501.conf.
Package prda3501 already exists. It will be modified.
Maximum configured packages parameter is 80.
Configuring 37 package(s).
43 package(s) can be added to this cluster.
200 access policies can be added to this cluster.

Modify the package configuration ([y]/n)? y
Modifying the package configuration for package prda3501.
There were no configuration changes to apply.
Completed the cluster update.
n4sp1 $ root:/etc/cmcluster/prda3501# ls -l
Rgds
Sree

[Viktor Balogh]

Hi Sreer,

>There were no configuration changes to apply.

Review that you saved your changes indeed, and this is the config file you have modified. IMHO Serviceguard didn't recognize any changes to the package config.

Regards,
Viktor

[Sreer]

Hi,

Sorry Iam not clear...If we do cmappyconf package.conf file...will it distribute the modified config file to all nodes?

like cmclconfig file in cluster???

Rgds
Sree

[Viktor Balogh]

> If we do cmappyconf package.conf file...will it distribute the modified config file to all nodes?

yes, cmapplyconf will distribute the package config, so you don't need to distribute the conf file.

However, if you are using the legacy package format with separate conf and cntl files, you should manually distribute the _control_file. This is the file which incorporates all the vg activating, fs mounting and application starting scripts. There must be a reference in the conf file to that starting script file.

[Sreer]

Hi Victor ,

Thanks for help.

As we discussed the cmapplyconf file is not distributing the "package.conf" files ato all cluster nodes.
Idont know why.

I copied manually to all nodes!!! which is not recommended!!

Still waiting for a solution ....


Rgds
Sree

[Viktor Balogh]

> As we discussed the cmapplyconf file is not distributing the "package.conf" files ato all cluster nodes.

the cmapplyconf command distribute the package.conf indirectly, which means that it compiles this ascii file to a binary and this binary will be distributed in the end. so you don't need to scp the conf file manually.

[Viktor Balogh]

Sreer,

here is the exact wording from "Managing Serviceguard Eighteenth Edition, September 2010" which you can find here:

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual〈=en&cc=hu&docIndexId=64902&taskId=120&prodTypeId=18964&prodSeriesId=4162060


##

When cmcheckconf has completed without errors, apply the package configuration,
for example:
cmapplyconf -P $SGCONF/pkg1/pkg1.conf
This adds the package configuration information to the binary cluster configuration
file in the $SGCONF directory (normally /etc/cmcluster) and distributes it to all
the cluster nodes.

##

so you don't need to distribute the package conf file manually, this is the task of cmapplyconf, it distributes it in binary form.