Cisco Bug: CSCuj33858 - ClusterManager doesn't self recover after a network outage
Feb 25, 2019
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: Subscriber Node is spiking CPU near 100% where CLM is the top process ClusterManager logs are flooding this line; 14:54:36.753 |Data length (0) violates HMAC_SHA1 minimum length (20) This subscriber is not authenticated to any other node in the cluster and the ServerDown alert is being raised against it. Conditions: ClusterManager gets in this non functional CPU spiking state after the cluster experiences a major network outage.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases