Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM - Knowledgebase Articles > Cisco Call Manager (CUCM) showing No Data Collected Yet

Cisco Call Manager (CUCM) showing No Data Collected Yet

Created by Brian O'Donovan, last modified by MindTouch on Jun 16, 2016

Views: 1,426 Votes: 1 Revisions: 4

Overview

The Cisco Call Manager (CUCM) showing No Data Collected Yet.

 

 

Error in IpSlaM.Collector.Pollers.Jobs_*.log

ERROR:

ERROR SolarWinds.Orion.Pollers.Framework.PollerBase - CCM common data polling error: 
SolarWinds.Orion.Pollers.Framework.SNMP.SnmpTableResponseException: Error 31040 - Error 31040 - Timeout 

Environment

All VNQM Versions

Cause 

There is a known bug in Cisco firmware where it blocks consequent SNMP queries in case of more than 10 parallel SNMP queries (CISCO defect CSCtc85744).

Resolution

Verify that SNMP, AXL & FTP credentials are correct. If so, run SNMP Walk of the device.

 

There are a couple things that you can try to resolve this issue:

  • Set a longer polling interval for polling the CUCM (default is 5 minutes). Set it to 2 hours or 6 hours.
  • Reset the CUCM to reset the SNMP agent to clear the issue.
  • Increase the SNMP Timeout (default 2500 ms). You can increase this to 10000 ms.

 

If these steps do not resolve the issue, open a TAC case with Cisco to investigate why the CUCM is not responding to SNMP requests.

Last modified

Tags

Classifications

Public