snmpcollector CPU metric family discovery on Cisco 3850 devices (and potentially others)

Document ID:  TEC1249579
Last Modified Date:  06/07/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details


  • CA Unified Infrastructure Management


  • CA Unified Infrastructure Management:Release:8.2
  • CA Unified Infrastructure Management:Release:7.6
  • CA Unified Infrastructure Management:Release:8.0
  • CA Unified Infrastructure Management:Release:8.1
  • CA Unified Infrastructure Management:Release:8.31
  • CA Unified Infrastructure Management:Release:8.4



The snmpcollector does not successfully discover CPU metric families on Cisco 3850 devices.

Seen on: ** Unified Infrastructure Management (UIM) version - 8.2 ** snmpcollector probe version - 2.26 ** device make/model - Cisco 3850

The target device cannot deliver a large batch of OID values all at once.


Open the snmpcollector raw configuration mode and navigate to the 'settings' folder.

Add a key called 'MAX_BATCH' and set it's value to a low number.  20 is the default, so perhaps test with 5 and adjust up or down as necessary.

Additional Information:

At time of this writing the Cisco 3850 is not on the supported device list in spite of having the same MIB tree as supported devices.

1. This same situation could occur for many – usually older- devices, not just the 3850 device.
2. The tuning parameters to handle such devices are MAX_BATCH (default 20), SNMP_RETRIES (default 2), and SNMP_TIMEOUT (default 2000 milliseconds). We recommend that the overall performance of the system (discovery and polling) should be observed carefully when changing these parameters.

See KB Article TEC1024587 for more information on the general issue.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255


Not what you were looking for?

Search Again >

Product Information

Support by Product >


Join a Community >