HP Insight Cluster Management Utility User Manual

Page 32

This command does not actually start HP Insight CMU. It only clears the audit mode to enable
HP Insight CMU to be started by the HA tool.

Run the appropriate command for your HA software to start HP Insight CMU.

To verify that HP Insight CMU is still running correctly, review the
/var/log/cmuservice_hostname.log

file for errors.

Install and configure HP Insight CMU on additional management cluster members. Installing
new cluster members is basically the same as for configuring the first member. Because new
members inherit the HP Insight CMU configuration of the first member, you do not have to set
parameters such as the cluster IP address and the Java path.
a.

Using the same procedure as for the first member of the cluster, install the HP Insight CMU
rpm.

If you started HP Insight CMU in standalone mode on the HP Insight CMU management
server currently operating, you must put HP Insight CMU in audit mode and stop it before
migrating the HA service:

# /etc/init.d/cmu set_audit

# /etc/init.d/cmu stop

Migrate the HA service to the server that will perform the post installation procedure.

Run the post installation procedure:

cmuadmin2# /opt/cmu/tools/cmu_ha_postinstall

*** starting setup procedure to operate CMU in HA (Highly Available) environment
*** note: this only affects the management nodes of the HPC cluster

**********************************************************************
requirements to building an Highly Available cluster of cmu mgt nodes:
**********************************************************************
* *
* 1] a shared filesystem mounted at /opt/cmu-store *
* *
* it must support locking via flock() *
* it must be mounted only by one (active) cmu mgt node at a time *
* it must be NFS exportable (for kickstart/diskless/backup/cloning) *
* *
* 2] (at least) one alias IP address: *
* *
* this is the address used by the compute nodes to contact the mgt *
* service, set CMU_CLUSTER_IP into /opt/cmu/etc/cmuserver.conf *
* this address should follow the active cmu management machine *
* *
* [ optionally: a site alias IP address ] *
* *
* 3] a third-party HA software: *
* *
* this software is responsible for: *
* *
* - mounting/unmounting the /opt/cmu-store filesystem *
* - activating/removing the alias IP address(es) *
* - using /etc/init.d/cmu start|stop|status ( NOT /opt/cmu/cmuserver)*
* *
**********************************************************************
do you want to continue (at this stage only /opt/cmu-store is necessary) ?(y/N)y

setting cmu in audit mode

*** CMU is currently in 'audit' mode on cmuadmin2
*** use: '/etc/init.d/cmu unset_audit' to unset audit mode

cmu_ha: saving local cmu config in:/opt/cmu-store/etc/savedConfig/cmuconf1-yyyy.sav
cmu_ha: saving clusterwide cmu config in:/opt/cmu-store/etc/savedConfig/cmuconf2-zzzz.sav

cmu_ha: all existing cmu data has been saved
cmu_ha: if required, restore it with:

/opt/cmu/tools/restoreConfig -f /opt/cmu/etc/savedConfig/

*** successfully configured CMU for HA operation
*** install CMU similarly on the other management node(s) of the cluster

management node(s) configured so far:
cmuadmin1
cmuadmin2

Installing and upgrading HP Insight CMU