OpenNMS Horizon 28.0.1 - Resource Graphs missing SNMP Node and Interface Data

Problem:
We recently set up a new instance of OpenNMS Horizon ver 28.0.1. We were previously running OpenNMS Horizon ver 22.0.2. After setting up the nodes on the new OpenNMS 28.0.1 server we are not finding SNMP Node Data or SNMP Interface Data when opening Resource Graphs on some nodes.

Screenshots

OpenNMS version:
Horizon 28.0.1

We have the same MIBs loaded in the new server as the old server.

The node (Fortigate firewall) is configured to allow SNMP access from both new and old OpenNMS servers.

Any help would be greatly appreciated.

Do you have the same snmp-config.xml file on both to define SNMP settings? Are your devices allowing the new server access to read SNMP data? Some devices have to explictly allow SNMP polling from specific IP addresses.

Thanks for the quick reply. yes, both systems have identical snmp-config.xml files. In the screenshot I provided, OpenNMS is able to read the interfaces from our host. I am certain the new OpenNMS server has access to read from the host.

I ran the following from the new server (Usernames and TCPIP addresses obfuscated):

Username@Host:~$ /usr/share/opennms/bin/snmp-request -c public -v 1 -Ow TCPIPRemoved .1.3.6.1.2.1.1
Using SNMP4J from: /usr/share/opennms/lib/snmp4j-2.5.5.jar
Using log4j-over-slf4j from: /usr/share/opennms/lib/log4j-over-slf4j-1.7.30.jar
Using SLF4J API from: /usr/share/opennms/lib/slf4j-api-1.7.30.jar
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
1.3.6.1.2.1.1.1.0 = FortiGate 101F
1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.12356.101.1.1001
1.3.6.1.2.1.1.3.0 = 76 days, 21:41:07.29
1.3.6.1.2.1.1.4.0 = Network Admins
1.3.6.1.2.1.1.5.0 = HostnameRemoved
1.3.6.1.2.1.1.6.0 = LocationRemoved
1.3.6.1.2.1.1.7.0 = 78
1.3.6.1.2.1.1.8.0 = 0:00:00.00
1.3.6.1.2.1.1.9.1.1.1 = 1
1.3.6.1.2.1.1.9.1.2.1 = 0.0.0
1.3.6.1.2.1.1.9.1.3.1 =
1.3.6.1.2.1.1.9.1.4.1 = 0:00:00.00

Total requests sent:    12
Total objects received: 12
Total walk time:        105 milliseconds

Can you perform the same test via the Karaf shell?

opennms:snmp-walk ipaddr .1.3.6.1.2.1.1

@dino2gnt Yes, Here is the output from the Karaf shell
username@opennms()> snmp-walk TCPIPRemoved .1.3.6.1.2.1.1
[.1.3.6.1.2.1.1].[1.0] = FortiGate 101F
[.1.3.6.1.2.1.1].[2.0] = .1.3.6.1.4.1.12356.101.1.1001
[.1.3.6.1.2.1.1].[3.0] = 672895826
[.1.3.6.1.2.1.1].[4.0] = Name Removed
[.1.3.6.1.2.1.1].[5.0] = Hostname Removed
[.1.3.6.1.2.1.1].[6.0] = Location Removed
[.1.3.6.1.2.1.1].[7.0] = 78
[.1.3.6.1.2.1.1].[8.0] = 0
[.1.3.6.1.2.1.1].[9.1.1.1] = 1
[.1.3.6.1.2.1.1].[9.1.2.1] = .0.0.0
[.1.3.6.1.2.1.1].[9.1.3.1] =
[.1.3.6.1.2.1.1].[9.1.4.1] = 0

I reapplied all required MIBs, restarted the server and voila, the SNMP interface and node data are now available in the resource graphs. Not sure if it was reapplying the MIBS, Compiling and Generating SNMP data in the MIB compiler or the server reboot to fix the issue, but it is fixed.

2 Likes