Unsupported content


This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Monitoring BMC Cloud Lifecycle Management health with the CLM Self Checker

The CLM Self Checker provides information about the performance of BMC Cloud Lifecycle Management components, enabling you to monitor the overall health of your BMC Cloud Lifecycle Management environment.

For a high-level overview of the CLM Self Checker and some of the procedures to get started with the CLM Self Checker, check out this video (8:29):


Before you begin

  • Create a cloud administrator that you will use to onboard CLM Self-Check Monitor with Platform Manager. This cloud administrator should not access the BMC Cloud Lifecycle Management portal or the Enterprise AR or Cloud AR servers. Do not use clmadmin
  • On-board the CLM Self Checker.

Back to top

To open the CLM Self Checker

If you are working in the My Cloud Services Console, you can open the CLM Self Checker by clicking More in the Cloud Application Health chart on the Health Dashboard. See Monitoring service request failures and BMC Cloud Lifecycle Management component health for more information about the Health dashboard.

If you are not working in the My Cloud Services Console, open the following URL in a browser: https://computerName:portNumber/health.
For example, https://vw-aus-lab-dv555:8443/health

You must log on to the CLM Self Checker as a cloud administrator. 

Icons next to the component name indicate the overall health of that component. Icons next to a health check indicate the health of that aspect of a component.

  • A blue check mark indicates good health.
  • An orange icon  indicates that you should monitor that aspect of the component frequently, and consider improvements to improve its health.
  • A red triangle indicates the need for immediate attention. Click the triangle to open a window that offers a description, the cause, and an action to take to solve the problem.

To update the charts and to view the last time that the Health Check was run, refresh your browser.

Mouse over a component name to see details for that component.

Click the BMC Server Automation and BMC Atrium Orchestrator names to open Dashboards for those components.

Back to top

Monitoring the health of your Remote ITSM installation

You can integrate Remote ITSM with the Cloud Lifecycle Management stack, as described in Integrating with BMC Change Management. However, there is no independent method to monitor the health of Remote ITSM integrated with CLM Stack. (The current version of CLM Self-Checker supports monitoring of the BMC Remedy ITSM provider only.)

Use the following utility to help adding Remote ITSM and start monitoring health of the same.    

  1. On-board Platform Manager but use the host name of the Remote ITSM which is integrated with CLM Stack.
  2. Enter the the following details:
    • Installation path
    • Cloud Admin User Name (for example, clmadmin) and password

Back to top 

To view email notifications from CLM Self Checker

BMC Self-Checker can send notifications to specific users and groups that have been predefined in the system. These notifications are sent to the receiver’s email addresses. Every time a Health Check turns Orange or Red, based on the Email Notification Configuration, a cloud administrator receives an automatic email notification, which provides detailed steps about the Root Cause and Status of a Healthcheck name.

The following figure shows a sample email notification received by a cloud administrator.

Back to top

Stopping and restarting BMC Cloud Lifecycle Management component services

You can restart BMC Cloud Lifecycle Management component services from the Self Checker.


Restart All Components is not available:

  • in HA environments. 
  • for older versions of BMC Cloud Lifecycle Management (before 4.5.x). Restart All Components is not displayed on the CLM Self Checker UI. 

To manually stop and restart BMC Cloud Lifecycle Management components, see Manually stopping and starting components of Cloud Lifecycle Management.

Before you stop and restart services

Before you try to stop and restart the component services, make sure that:

  • You have onboarded BMC Cloud Lifecycle Management components to the Health Dashboard.
  • Host entry with aliases are present in the hosts file, for example, /etc/hosts
  • RSCD agents are running on all hosts where the CLM components are deployed. Make sure that the RSCD agents on the CLM Self-Checker and the target hosts of all components are running on the same port, for example, 4750. Review the secure file (for example, C:\Windows\rsc\secure) for details: 
  • For Linux, the nexec, agentinfo, and nsh commands are in the PATH environmental variable. 
  • Self Checker database is populated with the service name or operating system. Otherwise, you cannot proceed with restart. You see this especially with Linux where a particular component service is not started and the StackInformation.properties file cannot populate its value. When you onboard this kind of stack, its value might not be present in the Self Checker database table and restart cannot be proceeded. The Self Checker prompts you with an error when you click Restart All Components.
  • No activities are pending (for example, Running SOIs or any other operations). This is because you are restarting the entire CLM stack when you click Restart All Components.

Back to top

To restart BMC Cloud Lifecycle Management components

  1. On the CLM Self Checker, click Restart All Components.


    Because you are restarting the entire cloud stack, verify that there are no pending activities before you click Restart All Components.

    The Restart CLM dialog box opens.

  2. On the Restart CLM dialog box, click Continue.
    When you click Restart All Components, BMC Cloud Lifecycle Management stops the CLM Self Checker in the background to prevent a false health status for a component in the process of being stopped or restarted. Components are stopped in the following order:
    1. Cloud Platform Manager
    2. BMC Network Automation
    3. Enterprise and Cloud AR System
    4. BMC Server Automation
    5. BMC Atrium Orchestrator
    Components are then restarted in the following order:
    1. BMC Network Automation
    2. BMC Atrium Orchestrator
    3. Enterprise and Cloud AR System
    4. BMC Server Automation
    5. Cloud Platform Manager

    During the restart, the health status of a component turns grey.
  3. After all components are restarted, click Cancel.
    If any of the component is not restarted, restart it by clicking Continue again. If there is any problem in the restart process, an error message is displayed. You can manually restart the particular component.


If another user logs on to the CLM Self Checker while the stack is restarting, that user is notified that a restart is in progress.

Back to top

Important troubleshooting information when restarting services

When you start the Cloud Platform Manager for the first time, the StackInformation.properties file is created on the Cloud Platform Manager. This file is useful for troubleshooting. The StackInformation.properties file stores the information about the BMC Cloud Lifecycle Management components and is used to provide information about all the components to the cloud database. For more information, see Configuring the StackInformation.properties file.

  • Stackinformation.properties file is not created on the Platform Manager host if NSH is not installed.
  • On a multi-VM stack, Stackinformation.properties is not created on the Platform Manager host if the RSCD agent service of any of the hosts where CLM components are deployed is not reachable.  
  • If Stackinformation.properties is not created on the Platform Manager host, the Restart All Components button is hidden on the CLM Self-Checker. If you do not see Restart All Components, troubleshoot the possible reasons why the StackInformation file is not created on the Platform Manager host. Possible reasons include:
    • RSCD agent service of any of the computers where CLM components are deployed is not reachable.  
    • RSCD agent is not running on the same port as the Self Check RSCD agent port. Check the following line in the C:\Windows\rsc\secure file:
    • Port value is not the same on all the components.
    • The components machines are not reachable through NSH. You can use an agentinfo command to verify. 
  • When Restart is in-progress:
    • Platform Manager waits for the Enterprise AR service to be running, But if the Enterprise AR service is still not started after 10 attempts, Platform Manger starts with a warning message.
    • Health Check is stopped in the background to avoid false alarms. The stopped health status is displayed with a different color scheme (Gray), which informs you that Restart is in progress and Health checks are paused. After CLM is up and running after restart, Health Check is resumed.
  • If Restart is not completed because the Self Checker Tomcat server has crashed, you are notified the next time you log on to the Self Checker with a Restart was aborted message. If you see this error, the cloud administrator must click Restart All Components again. This action restarts the CLM stack from the beginning because the Self Checker does not store the history of the Restart Stack process.

To back up the CLM Self Checker database file

Copy the installationDirectory\server\h2\CloudMon.h2 file periodically to preserve data in the event of a system failure.

Back to top

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.