8-72
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
High Availability and Failover
Symptom #3: or if you see an error message that mentions the file "Tx.per".
Error Message See the previous symptoms topic for the message.
Possible Cause The files in BSTxState? may be corrupted.
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 CRS 5.0 high availability and failover
problems:
• Previously configured log file size is not preserved after system upgrade, page 8-72
• Conflicts in Datastore Control Center history, page 8-73
• Cannot make configuration changes in HA cluster, page 8-73
• Cannot make configuration changes in RmCm Subsystem, page 8-73
• Service constantly shows Invalid, page 8-74
• CRS server keeps rebooting due to CRS Node Manager failure, page 8-74
• Cluster is in partial service, page 8-74
• Server is in partial service, page 8-75
• CRS does not accept call or function properly, page 8-75
• Service Master/Slave status is not shown on CRS Administration Control Center, page 8-75
• Cluster time synch fails, page 8-76
• CRS Servers respond slowly in HA environment, page 8-76
• Multilple failovers with high CPU usage, page 8-76

Previously configured log file size is not preserved after system upgrade

Symptom After upgrade, previously configured CRS log file size is set to default.
Error Message None.
Possible Cause The CRS log layer does not dynamically adjust the log file size after the right value
synchronizes down from LDAP.
Recommended Action Restart the Cisco CRS Node Manager.