Installing Self-Checker Monitor for HA
This topic describes how to install the Self-Checker Monitor in an HA environment.
Note
The Self-Checker Monitor does not support Load-Balancer HA products like the BMC Remedy mid tier, AR System, or BMC Server Automation. But you can still monitor the status of your environment if you map the load-balancer host name with each primary host name of the product on the Self-Checker host. In this way, agentinfo successfully returns accurate output and data collection is started for all primary VMs.
Overview for implementing HA Self-Checker Monitor
To create a robust Self-Checker Monitor implementation, the H2DB Configurations data must be constantly available. The HA Active-Passive implementation of the Self-Checker Monitor uses Cluster Technology so that the Health Dashboard data syncs after failover.
Supported BMC Cloud Lifecycle Management versions
You must be using BMC Cloud Lifecycle Management 3.0, 3.1, 4.0, 4.1, or 4.5.
HA system requirements
For detailed installation requirements, see Installing standalone CLM Self-Check Monitor.
Installing the Self-Checker Monitor on the Platform Manager
This section provides high-level steps on installing the Self-Checker Monitor on the Platform Manager host.
- Install the Self-Checker Monitor on the Primary Active Node.
Typically, port 8090 is used. For more information, see Installing standalone CLM Self-Check Monitor. - Copy the h2 folder data on the share disk location.
- Update the configuration.properties file on the PrimaryNode and Secondary Node (for example, /selfchecker/tomcat/conf/configuration.properties for Linux or C:\selfchecker\tomcat\conf\configuration.properties for Windows) with the share disk location details (for example, jdbc.url=jdbc:h2:<sharedisk>:/h2/CloudMon).
- Set the Failover Cluster to the Secondary Node.
- Make sure that the share disk is now available on the Secondary Passive Node. It now becomes the Active Node.
- Install the Self-Checker Monitor on the Secondary Passive Node.
Use the same port as the Primary Active Node, for example, port 8090. - Install or manually create services on the Secondary Passive Node.
- Verify that the h2 folder is available on the share disk location.
- Create a Generic Service and add the clmhealth service in the Failover Cluster Manager.
- Verify that the Self-Checker Monitor works successfully with the Cluster Hostname.
For example:
http://10.129.188.72:8090/health - Start and stop the services when the Cluster is active on Primary Node.
For more information, see Stopping and restarting BMC Cloud Lifecycle Management component services. - Start and stop the services when the Cluster is active on the Secondary Node.
Comments
Log in or register to comment.