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

CAUTION:

For SLES installation only:

For a SLES installation, you have to modify the name of the serviceguard startup file.

Proceed an follows:

# cd /etc/init.d

# rm rc3.d/*cmcluster

# rm rc4.d/*cmcluster

# rm rc5.d/*cmcluster

# mv cmcluster.init cmcluster

# cd /etc/init.d/rc3.d

# ln -s /etc/rc.d/cmcluster K01cmcluster

# ln -s /etc/rc.d/cmcluster S99cmcluster

# cd ../rc4.d

# ln -s /etc/rc.d/cmcluster S99cmcluster

# cd ../rc5.d

# ln -s /etc/rc.d/cmcluster S99cmcluster

# ln -s /etc/rc.d/cmcluster K01cmcluster

2-3-5

Configure the system management homepage

Run the script /opt/hp/hpsmh/tomcat/bin/tomcat_cfg and specify the full path of java:

# /opt/hp/hpsmh/tomcat/bin/tomcat_cfg

Java SDK path guessed is /usr/bin/java

Enter complete path to Java or ENTER to use guessed one:

/usr/java/jdk1.5.0_15/bin/java

Stopping hpsmhd:

Starting hpsmhd:

2-3-6

Partition the shared storage

CAUTION:

Steps in this paragraph must be performed on only one

management server.

The shared storage requires two partition: one small partition (1 Mbytes in the example) is

used as arbitration mechanism. The remaining storage space is used for creating a LVM

volume for hosting the /opt/cmu directory.

Preparing the arbitration mechanism

configure a lock lun on the shared disk for use by Serviceguard ar arbitration mechanism:

# fdisk /dev/sda

The number of cylinders for this disk is set to 51200.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)