Skip to content

OpenNMS SNMP Data Collection Error — Quick Fix

DodaTech Updated 2026-06-24 2 min read

In this tutorial, you'll learn about OpenNMS SNMP Data Collection Error. We cover key concepts, practical examples, and best practices.

The Problem

OpenNMS is not collecting SNMP data from network devices or servers. The node shows as "Managed" but no SNMP data appears in the graphs or data tables. SNMP walks from the command line work, but OpenNMS does not store the data.

Error example:

SNMP data collection failed for node 'web-01': timeout
No SNMP data available for node 'switch-01': Request timeout
SNMP interface <192.168.1.100> not collected: SNMP community string mismatch

The Fix

Step 1: Verify SNMP configuration for the node

WRONG — assuming OpenNMS uses the same community as snmpwalk:

# OpenNMS may have a different SNMP community configured per node

RIGHT — check the node's SNMP configuration:

# In OpenNMS web UI:
# Info -> Nodes -> Select Node -> SNMP Config tab

# Or check via API:
curl -u admin:admin http://localhost:8980/opennms/rest/snmp/nodes

Verify the community string, port, and version match what the device expects.

Step 2: Check data collection group configuration

WRONG — the node is discovered but not in any data collection group:

# Without a data collection group, no SNMP data is collected

RIGHT — verify the data collection group assignments:

# List data collection groups
ls /opt/opennms/etc/datacollection-config.xml
grep "mibObj" /opt/opennms/etc/datacollection-config.xml | head -10

Check that the node's sysObjectID maps to a data collection group.

Use DodaTech's SNMP Configuration Analyzer to validate SNMP settings, data collection groups, and OID mappings across all monitored nodes.

Prevention Tips

  • Test SNMP with snmpwalk before adding the node to OpenNMS
  • Use SNMPv3 with authentication and encryption for production devices
  • Configure proper timeout and retry values for slow devices
  • Verify sysObjectID mappings in data collection groups
  • Use DodaTech's SNMP Template Manager for consistent data collection policies

Common Mistakes with snmp error

  1. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
  2. Using head and tail instead of pattern matching, causing runtime errors on empty lists
  3. Forgetting that lazy evaluation defers computation until the value is forced, causing space leaks with unevaluated thunks

These mistakes appear frequently in real-world OPENNMS code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

### Why does OpenNMS not graph SNMP data even though my device responds to snmpwalk?

The device may not match any data collection group based on its sysObjectID. Verify the sysObjectID: snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.2.1.1.2.0. Then ensure a matching data collection group exists in datacollection-config.xml.

How do I increase the SNMP timeout in OpenNMS?

Set snmp-timeout="3000" (milliseconds) and snmp-retries="3" in the node's SNMP configuration. For all new nodes, configure defaults in snmp-config.xml under the <defaults> element.

Can I collect SNMP data at different intervals for different OIDs?

Yes. OpenNMS supports per-OID collection intervals in the data collection group configuration. Use the snmp-collection element with max-vars-per-pdu, interval, and retry attributes for fine-grained collection control.

Related: DodaTech's SNMP Monitoring Guide provides best practices for OID selection, collection intervals, and data retention for OpenNMS SNMP deployments.

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro