OpenNMS should, as well, find the optimal protocol configuration (max-vars-per-pdu, timeout, max-repetitions, etc.).
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Markus von Rüden May 16, 2013 at 3:18 AM
I had a deeper look at the ticket and decided that it is not related to the snmp stuff I worked on.
David Hustace April 30, 2013 at 10:13 AM
Jerome Callaghan September 26, 2012 at 5:28 PM
I think it should be automatic rather than a user action. Under some failure condition, SNMP not working for x tries but ICMP working, throw it on a "figure it out" queue.
Rather than fixed combinations of community strings and versions, it would be good to be able to have a set of community strings and set of versions and try all combinations.
Matt Brozowski July 12, 2011 at 9:42 AM
This has had to be dumped from the 1.10 list because of other activities and time constraints
Major
From the node page and from an event, a user should be able to ask OpenNMS to detect the SNMP agent's configuration:
The SNMP configuration should allow users to specify a list of strings to try as valid community names as well as valid v3 definitions.
<snmp-config xmlns="http://xmlns.opennms.org/xsd/config/snmp" retry="1"
timeout="1800" read-community="public" version="v2c">
<test-definitions>
<id>standard</id>
<id>cisco-v3</id>
<id>noz</id>
</test-definitions>
<!-- new optional "id" attribute />
<definition id="standard" read-community="public" write-community="private" version="v2c"/>
<definition id="noz" read-community="YrusoNoz" />
<definition version="v3" security-name="opennmsUser" auth-passphrase="0p3nNMSv3" auth-protocol="MD5" privacy-passphrase="0p3nNMSv3" privacy-protocol="DES" />
</snmp-config>
OpenNMS should, as well, find the optimal protocol configuration (max-vars-per-pdu, timeout, max-repetitions, etc.).