Specifications

3-38
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
Support of these interfaces on the server includes the following capabilities (specific feature names vary
by hardware vendor):
• Remote console (to access boot screens and the Cisco CLI)
• Remote power management
Phone Registration Status
Phone registration status needs to be monitored for sudden changes. If the registration status changes
slightly and readjusts quickly over a short time frame, then it could be indicative of phone move, add,
or change. A sudden smaller drop in phone registration counter can be indicative of a localized outage,
for instance an access switch or a WAN circuit outage or malfunction. A significant drop in registered
phone level needs immediate attention by the administrator. This counter especially needs to be
monitored before and after the upgrades to ensure the system is restored completely.
Historical Information Download
You can also download some historical information using RTMT Trace Log Center or SOAP APIs, such
as:
• Cisco AMC Service PerfMonLog is enabled by default but deprecated in Cisco Unified CM Release
6.0 because Cisco RIS Data Collector PerfMonLog is introduced.
• Cisco RIS Data Collector PerfMonLog is disabled by default in Cisco Unified CM Release 5.x and
enabled by default in Cisco Unified CM Release 6.0.
Cisco CallManager Service Stops Responding
When the Cisco CallManager service stops responding, the following message displays in the System
Event log:
The Cisco CallManager service terminated unexpectedly.
It has done this 1 time. The following corrective action
will be taken in 60000 ms. Restart the service.
Other messages you may see in this situation:
Timeout 3000 milliseconds waiting for
Cisco CallManager service to connect.
The Cisco Communications Manager failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
At this time when devices such as the Cisco Unified IP Phones and gateways, unregister from the Cisco
Unified Communications Manager, users receive delayed dial tone, and/or the Cisco Unified
Communications Manager server freezes due to high CPU usage. For event log messages that are not
included here, view the Cisco Unified Communications Manager Event Logs.
Possible Cause
The Cisco CallManager service can stop responding because the service does not have enough resources
such as CPU or memory to function. Generally, the CPU utilization in the server is 100 percent at that
time.