When node is provisioned snmp community string is not present in snmpd.conf, after node is provisioned added comunity string to snmpd.conf, data collection of snmp is not happening.

Description

I have provisioned a node with default snmp community string public, but my snmpd.conf is not having public community string. After node is provisioned, i have modified my snmpd.conf and updated it with public community string and restarted snmp. But in ui sysid is not updated, data collection is not happening not displaying any errors. This case is possible in my monitoring system.

Environment

linux, unix box.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Alejandro Galue October 7, 2014 at 11:16 AM

If the SNMP settings are wrong, that means the enterprise system OID is not populated on the node's table and Collectd doesn't know how to schedule data collection through SNMP without it.

I made a fix for the "force-rescan" handler, and with the latest snapshot of 14.0.0 you can just hit force-rescan, and everything will be rediscovered (including the node level settings). Of course, this works if you are using the SnmpDetector, if you're forcing the SNMP service on the requisition, it is your responsibility to be sure that SNMP works prior synchronizing the requisition. I'm saying this because if you force a service, you're telling OpenNMS "hey, this service exist on this IP", and OpenNMS will trust you without checking. So, if that is not true, well, you lied to OpenNMS winking face

Alejandro Galue May 16, 2012 at 9:45 AM

mvssrmurthyattlassian March 27, 2012 at 1:06 PM

This bug is similar to the bug https://opennms.atlassian.net/browse/NMS-4501#icft=NMS-4501 ( http://issues.opennms.org/browse/NMS-4501 ).
I have to fix this any how, as i have to meet my customer request slightly smiling face Thanks.

Details

Assignee

Reporter

Labels

Due date

Affects versions

Priority

PagerDuty

Created March 27, 2012 at 12:48 PM
Updated September 21, 2021 at 6:24 PM

Flag notifications