Cisco Bug: CSCum37479 - Cluster Manager floods S1 Alarm for nodes in INITIATOR state
May 09, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: Built-IN RTMT Alert SyslogSeverityMatchFound alert is raised on every polling cycle triggered via this ClusterManager S1 Alarm. Jan 3 11:24:18 ucm-cm1a local7 1 : 10077: ucm-cm1a: Jan 03 2014 16:24:18.153 UTC : %UC_CLUSTERMANAGER-1-CLM_PeerState: %[NodeName=ucm-cm1b][NodeState=INITIATOR][AppID=Cisco Cluster Manager][ClusterID=][NodeID=ucm-cm1a]: Current ClusterMgr session state. Conditions: While a UCM Cluster member is Down or not accessible via network to other nodes in the cluster, the "%UC_CLUSTERMANAGER-1-CLM_PeerState" Cluster Manager is raised on the remaining nodes that are powered on. This Alarm since it is raised at Severity 1 will trigger the Built-IN RTMT alert named SyslogSeverityMatchFound. The CLM "%UC_CLUSTERMANAGER-1-CLM_PeerState" alarm is flooded on every server that changes their PeerState to the UCM Node that remains down or not accessible. This Alarm in turn will lead to the RTMT SyslogSeverityMatchFound Alert flooding.
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