HP Cluster Management Utility CMU Installation Guide with Serviceguard Version 4.0 (May 2009)

# ls -1 /opt/cmu/tools/cmu_sg*

cmu_sg_clean

cmu_sg_pkg.config

cmu_sg_pkg.sh

cmu_sg_pkg.env

Perform the following commands:

# cp /opt/cmu/tools/cmu_sg_clean /etc/init.d

# scp /opt/cmu/tools/cmu_sg_clean cmumgt2 /etc/init.d

# mkdir $SGCONF/cmu_sg_pkg

# cd $SGCONF/cmu_sg_pkg

# cp /opt/cmu/tools/cmu_sg_pkg.config .

# cp /opt/cmu/tools/cmu_sg_pkg.sh .

# cp /opt/cmu/tools/cmu_sg_pkg.env .

Now you can unmount the cmu directory and release the volume:

Unmount and deactivate the volume

CAUTION:

Do not forget to deactivate the volume. If you do not do it,

the cmu serviceguard package will not start correctly

# umount /opt/cmu

# vgchange -a n vgcmu

0 logical volume(s) in volume group "cmu" now active

# vgchange --deltag $(uname -n) vgcmu

Volume group "vgcmu" successfully changed

2-6 Creating the CMU SG package

CAUTION:

The steps in this section must be performed on each of the

two management servers.

Activate the cmu_sg_clean system service

The cmu_sg_clean ensures that no instances of cmu exist outside the Serviceguard. Activate

this service on both management servers as follows:

# chkconfig --add cmu_sg_clean

# ssh cmumgt2 chkconfig --add cmu_sg_clean

Customize the package configuration file

The cmu package configuration file $SGCONF/cmu_sg_pkg/cmu_sg_pkg.config must be

customized to reflect your configuration. You should change the following parameters:

NODE_NAME : there is a NODE_NAME field for each of the two management servers. Each

one must contain the hostname of your management servers.

RUN_SCRIPT and HALT_SCRIPT : these two variables define the start/stop script location

for the cmu serviceguard package. This location is not the same on Redhat and SuSE.

Depending on the distribution of your installed CMU management servers, uncomment the

pertinent lines.