EasyManuals Logo

Cisco MCS-7825-H3-IPC1 User Manual

Cisco MCS-7825-H3-IPC1
974 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #138 background imageLoading...
Page #138 background image
3-38
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 3 Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
General Health and Troubleshooting Tips
• 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.
Recommended Action
Depending on what type of interruption you experience, you will need to gather different data that will
help determine the root cause of the interruption.
Use the following procedure if a lack of resources interruption occurs.
Procedure
Step 1 Collect Cisco CallManager traces 15 minutes before and after the interruption.
Step 2 Collect SDL traces 15 minutes before and after the interruption.
Step 3 Collect perfmon traces if available.
Step 4 If the traces are not available, start collecting the perfmon traces and track memory and CPU usage for
each process that is running on the server. These will help in the event of another lack of resources
interruption.

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Cisco MCS-7825-H3-IPC1 and is the answer not in the manual?

Cisco MCS-7825-H3-IPC1 Specifications

General IconGeneral
BrandCisco
ModelMCS-7825-H3-IPC1
CategorySoftware
LanguageEnglish

Related product manuals