Guest

Preview Tool

Cisco Bug: CSCsy98435 - ccmAgt CPU and memory pegging high after a network outage

Last Modified

Jul 06, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

6.1(3.2102.1)

Description (partial)

Symptom:
Cisco CallManager SNMP Service (ccmAgt) process' CPU and Memory is high after experiencing a network outage in a Clustering Over Wan Deployment where some subscribers loose communication to the Publisher node.

CallProcessingNodeCpuPegging or CpuPegging and LowAvailableVirtualMemory alerts is received from the effected node.

Conditions:
Due to a related defect CSCsr41156 where after experiencing a network outage some services crashing Cisco CallManager SNMP Service could potentially crash as well due to memory problems, segmentation faults. Unfortunately ccmAgt doesn't handle this error condition properly.

If you have the Cisco CallManager SNMP Service traces at detailed level you can see the following message in the sdi traces over and over

04/08/2009 08:16:52.811 CCMSNMP|Caught signal --- SIGSEGV --- Application Termination signal|<CLID::LindermanCluster><NID::14.86.13.13><LVL::Detailed><MASK::0080>
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.