HP Operations Manager

Cluster check report


HPOM provides a console tool, that checks to see whether all SPIs and HPOM patches are installed on all cluster nodes. This tool is located in the console tree under Tools HP Operations Manager Tools Cluster Tools. It produces a report similar to the one shown below. 
---------------------------
 HPOM Cluster Check Report
---------------------------

 Inventory
-----------

HPOM cluster version: A.08.00
HPOM local version: A.08.00

HPOM installed on cluster nodes:
* clusternode1.domain.com
* clusternode2.domain.com

Installed SPIs:
* DBSPIMss Version 09.01.01

Installed patches:
* OVOW_00017

 Missing installations
-----------------------

On node clusternode2.domain.com:
* DBSPIMss Version 09.01.01

 Pending uninstallations
-------------------------

On node clusternode2.domain.com:
* OVOW_00151


 * end of report *

First, the report shows the inventory of the HPOM installation. It shows which version of HPOM is installed on the cluster and on the node running HPOM at the moment. It shows the names of the cluster nodes on which HPOM is installed and an inventory of all SPIs and patches installed on the cluster.

After that the report shows if there are any SPIs or patches which are not installed on all cluster nodes. If this list is empty, then the cluster is consistent. However, if there are any entries there you must install the missing SPIs/patches on these nodes as soon as possible because HPOM enforces a consistent installation and will refuse to run on the nodes in this list. This can lead to an unexpected down-time of the management server in case of a failure.

The last part of the report shows if there are any previously installed SPIs or patches which have not been uninstalled on all cluster nodes. If this list is empty, then the cluster is consistent. However, if there are any entries there you must uninstall the SPIs/patches on these nodes as soon as possible, because HPOM enforces a consistent installation and will refuse to run on the nodes in this list. This can lead to an unexpected down-time of the management server in case of a failure.