Use this Knowledge Script to monitor the operational status of active services on Communications Manager servers. Although the script monitors the following services by default, you can choose to exclude any default service, or include any service not mentioned in the list.
A Cisco DB
Cisco AMC Service
Cisco CallManager
Cisco CDR Agent
Cisco CTL Provider
Cisco Database Layer Monitor
Cisco DRF Local
Cisco Extension Mobility
Cisco RIS Data Collector
Cisco Tftp
This script raises an event if a stopped service is restarted or fails to restart, or if a service is stopped but the Start service if it is stopped? parameter has not been set to Yes. In addition, this script generates data streams for service availability.
This script is a member of the CiscoCM recommended Knowledge Script Group. For more information, see Section 4.57, Recommended Knowledge Script Group.
CiscoCM_CMServer
By default, this script runs every two minutes.
If you are running this script as part of the Recommended KSG, do not change the schedule. The schedules for the recommended scripts are staggered so as to lessen the impact on CPU utilization when you run the KSG.
Set the following parameters as needed:
Parameter |
How to Set It |
---|---|
General Settings |
|
Job Failure Notification |
|
Event severity when job fails |
Set the event severity level, from 1 to 40, to indicate the importance of the failure of the HealthCheck job. The default is 5. |
Monitor Services |
|
Default services to exclude |
Type the name of any default service you do not want to automatically start. You can specify the names of multiple services, separated by commas. |
Other services to include |
Type the name of any service you want to automatically start, but is not included in the list of default services. You can specify the names of multiple services, separated by commas. |
Start service if it is stopped? |
Select Yes to automatically start all stopped default services on Communications Manager servers. Any service you specify in Default services to exclude will not be started. The default is Yes. NOTE:Only “activated” services can be automatically started. If an administrator has “deactivated” a service, then AppManager cannot start it. |
Event Notification |
|
Raise event if service is stopped and should not be started? |
Select Yes to raise an event if a monitored service is stopped but Start service if it is stopped? is unchecked. The default is Yes. |
Event severity when service is stopped and should not be started |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a monitored service is stopped but Start service if it is stopped? is unchecked. The default is 15. |
Raise event if service fails to start? |
Select Yes to raise an event if AppManager cannot start a monitored service. The default is Yes. |
Event severity when service fails to start |
Set the event severity level, from 1 to 40, to indicate the importance of an event in AppManager cannot start a monitored service. The default is 5. |
Raise event if stopped service has been started? |
Select Yes to raise an event if AppManager successfully starts a monitored service. The default is Yes. |
Event severity when stopped service has been started |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager successfully starts a monitored service. The default is 25. |
Raise event if service is deactivated? |
Select Yes to raise an event if a monitored service has been deactivated by an administrator. The default is unselected. |
Event severity when service is not active |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a monitored service has been deactivated by an administrator. The default is 15. |
Data Collection |
|
Collect data for service availability? |
Select Yes to collect data for charts and reports. If enabled, data collection returns 0 for a stopped service or 1 for a started service. The default is Yes. NOTE:This script generates data streams for services running when the job starts or automatically restarted while the job runs. If a service is deactivated when the job starts, no data stream is generated. |