Use the SystemUpTime Knowledge Script to monitor the number of hours that a Cisco Unified Communications server has been up since the last reboot. This script raises an event if a reboot occurs. In addition, this script generates a data stream for the number of hours that the Unified Communications server has been operational since the last reboot.
This script is a member of the CiscoUCM recommended KSG. For more information, see Recommended Knowledge Script Groups.
CiscoUCM_CMServer
By default, this script runs every five 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 to lessen the impact on CPU utilization when you run the KSG.
Set the following parameters on the Values tab 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 SystemUpTime job. The default is 5. |
|
Raise event if system has rebooted? |
Select Yes to raise an event if the Unified Communications server has rebooted during the monitoring period. The default is Yes. |
|
Event severity when system has rebooted |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the Unified Communications server has rebooted. The default is 10. |
|
Monitor System Uptime |
|
|
Data Collection |
|
|
Collect data for system uptime? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of hours that the Unified Communications server has been operational since the last reboot. The default is Yes. |