Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

CallManager Memory poll with SNMP changed

We run a number of Cisco Call Managers (version 3.1 & 3.3(3)srx) across our clients, and use SNMP tools to collect performance data such as; 5 min average CPU utilisation, free physical memory, temperature sensor state, and hard disk % used. Up until December, these OIDs were providing correct data and working fine.

During December we applied patch (OS upgrades 2000-2-5 & sr4) to all Call Managers. Since applying the patch, the physical memory free OID will return the total memory value, and not the memory free value we are used to seeing. This means for the past few months our memory counters have flat lined at the amount of physical memory installed in the system, and are of little or no use to use.

It also means we have been unable to apply our thresholds to (and escalate in the case of continuous low free memory) this counter, putting our customers at risk of system crashes due to undetected out-of-memory conditions.

Any ideas?

  • Other Network Infrastructure Subjects

Re: CallManager Memory poll with SNMP changed

It's a known bug, CSCec87953. It's caused by HP Insight Agent 6.4. HP Insight Agent 7.0 will be included in OS Upgrade 2000.2.6 to fully resolve this issue.

Re: CallManager Memory poll with SNMP changed

Thanks, but when is it gonna be released?

We are getting into problems now that we can't poll the memory..