This article provides the procedure to adjust the SNMP timeout and retry interval for a specific device in OpenNMS to ensure successful data collection.

The MIB resource graph is visible, but performance graph data appears blank or shows NaN values.

SNMP data collection is failing due to insufficient polling timeout or retry values configured for the device. Increase the polling timeout and retries for the affected device.

Step 1: Review data-collection failures

Check the collectd.log for SNMP data-collection errors:

# tail -f /var/log/opennms/collectd.log 

Step 2: Modify SNMP timeout and retry values

Update the SNMP configuration for the specific device to prevent collection failures:

1. Navigate to
   Network Monitoring → Admin → Configure SNMP Community Names by IP Address

2. Enter the device IP and click Lookup.

3. Update the timeout and retry parameters.

4. Save the configuration.

This updates the snmp-config.xml file for the device.

You can verify the updated entries in below file:

Sample:

[root@space-005056a9ffe6 admin]# cd /opt/opennms/etc/
[root@space-005056a9ffe6 etc]# less snmp-config.xml | more

 <definition security-name="junos_space" security-level="3" auth-passphrase="Juniper123" auth-protocol="SHA" privacy-passphrase="Juniper123" privacy-protocol="AES" version="v3" timeout="5000" retry="3">
   <specific>a.a.a.a</specific>
   <specific>x.x.x.x</specific>
   <specific>y.y.y.y</specific>

Step 3: Restart OpenNMS module if manual editing is done

If you manually edit snmp-config.xml, a restart of the OpenNMS module is required.

Note : If you face any further issues, please contact JUNIPER JTAC Support for assistance.