opennms.conf can break the snmp-request command

Description

On certain environments, specially on those versions of OpenNMS when you have to explicitly enable 18980 on opennms.conf to access JMX from any IP interface, you won't be able to run the snmp-request to perform snmpwalks using SNMP4J. The reason is because this script will use everything defined in opennms.conf which is not necessarily useful for command line tools like this one.

You might see a variety of errors, for example:

I suggest to avoid load opennms.conf inside this script (and maybe other CLI tools in /opt/opennms/bin

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed April 12, 2017 at 9:19 AM

merged to foundation

Alejandro Galue February 27, 2017 at 10:54 AM

The workaround for the snmp-request script is being sure that it won't load opennms.conf, by removing the following from it:

Fixed

Details

Assignee

Reporter

Labels

Components

Sprint

Priority

PagerDuty

Created January 31, 2017 at 2:14 PM
Updated April 12, 2017 at 1:18 PM
Resolved April 12, 2017 at 9:19 AM