Cisco Cisco Unified Queue Manager, Руководство по обслуживанию и устранению неисправностей

Страница: 140 / 148

8-76
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
VoIP Monitor Problems
Cluster time synch fails
Symptom The cluster time on the CRS machines (on the same cluster) is not synchronized with the
Unified Communications Manager.
Error Message
The Network Time Protocol Service on the CRS machine exits with a
message in the event log stating that the time difference is greater than the
threshold.
Possible Cause
The NTP service has a built-in threshold of 1000 seconds. If the time difference between
the NTP client (CRS machines) and the server (Cisco Unified Communications Manager) is more
than this threshold, the NTP service does not correct the time.
Recommended Action
Do the following:
• Manually set the clock on each CRS machine in the cluster. The Time on the CRS machines should
be approximately the same as the time on the Unified Communications Manager machine.
•
Restart the Network Time Protocol service on the CRS machines, using the Service Control
Manager.
CRS Servers respond slowly in HA environment
Symptom CRS servers in a high availabilitly (HA) environment respond very slowly. Because of the slow
response time, the CRS system is unusable. No calls can get to agents.
Error Message
LDAP error 51 in MADM logs. SDL and SQL errors on the Subscriber.
Possible Cause
Publisher and Subscriber databases are no synchronized.
Recommended Action
Synch up the Publisher and Subscriber databases.
Multilple failovers with high CPU usage
Symptom Multiple failovers occur in a high availability environment and there is high CPU usage on both
servers. When the CRS server boots up, the primary server begins to spike the CPU usage causing the
primary server to be unusable, and it fails over to the secondary server. The secondary server then starts
the same behavior and eventually fails back over to the primary server.
Error Message
None.
Possible Cause
The problem can be caused by errors in the customer Java steps.
Recommended Action
Check for custom Java steps in the scripting and remove them.
VoIP Monitor Problems
This section contains the following troubleshooting tips on VoIP Monitor Problems
• VoIP monitor does does not work correctly, page 8-77
•
CRS fails to start, page 8-77