Troubleshooting Guide

8-80
Cisco Unified Contact Center Express Servicing and Troubleshooting Guide, Release 7.0(1)
Chapter 8 Troubleshooting Tips
High Availability and Failover
Recommended Action Manually clean the BSTxState?/ directory.
Step 1 Shut down the Node Manager.
Step 2 Copy everything in the wfavvid\BSTxState\ directory to a backup directory. Then delete all the files in
wfavvid\BSTxState\.
Step 3 Restart the Node Manager.
High Availability and Failover
This section contains the following troubleshooting tips on Unified CCX 7.0(1) high availability and
failover problems:
• Conflicts in Datastore Control Center history, page 8-80
• Cannot make configuration changes in HA cluster, page 8-81
• Cannot make configuration changes in RmCm Subsystem, page 8-81
• Service constantly shows Invalid, page 8-81
• Cisco Unified CCX server keeps rebooting due to Cisco Unified CCX Node Manager failure,
page 8-82
• Cluster is in partial service, page 8-82
• Server is in partial service, page 8-82
• Cisco Unified CCX does not accept a call or function properly, page 8-83
• Service Master/Slave status is not shown on Cisco Unified CCX Administration Control Center,
page 8-83
• Cluster time synch fails, page 8-83
• Cisco Unified CCX Servers respond slowly in a High Availability environment, page 8-84
• Multiple failovers with high CPU usage, page 8-84
Conflicts in Datastore Control Center history
Symptom With high availability, messages appear in the comment column in the subscription agent
history. To see the message from Cisco Unified CCX Administration, select Datastore Control Center
> History for a subscription agent.
Error Message A message similar to Downloaded 111 data changes (0 inserts, 111 updates, 0
deletes, 111 conflicts) appears.
Possible Cause To support high availability, SQL merge replication is being used to replicate data
between the subscriber node and the publisher. As part of this, SQL logs these messages in the
subscription agent history.
Recommended Action No user action required.