SNMP configuration testing on Security Analytics

Products

• Security Analytics

Issue/Introduction

SNMP is not providing the full details on the health of the system.  There are only the lo, eth0, and bond0 interfaces showing.

Environment

Release : 8.2.x

Cause

There are two lines which must be updated in /etc/snmp/snmpd.conf.tmpl file for snmp to work.

Resolution

You will need to add one line and update another to enable the full SNMP oid list.

You will need to update the snmpd.conf file with one additional line and uncomment another.

The snmpd.conf.tmpl file you want to edit is in /etc/snmp on Security Analytics. This will require root access from an SSH prompt.

1. vi /etc/snmp/snmpd.conf.tmpl
2. Locate line 60.  You will see a line "view    soleraview     included   .1.3.6.1.4.1.30190"
3. Add the line "view    soleraview     included   .1.3.6.1.4.1.2021"
4. Locate line 94.  You will see "#view mib2   included  .iso.org.dod.internet.mgmt.mib-2 fc"
5. Remove the hash mark, '#', from the first character of the line.
6. Save the file.
7. In the GUI, go to Settings -> Communication. 
8. Scroll down to SNMP Settings
9. Make a change to any field in the SNMP Settings.  For example, set the IP address to what it is currently.
10. Select Save.  This will restart snmpd with the updated settings found in the new .tmpl template file.
11. Test from another system with snmpwalk with the command "snmpwalk -v 1 -m SNMPv2-MIB -c public ip_address .1.3.6.1.4 "
12. Test with SolarWinds or any other SNMP provider.

Before the change, there were 27 entries.  After the change, we see 500+ including cpu load, memory usage, disk usage, and temperatures.  There will be no information on the capture interfaces because they are not under control of the Linux kernel.  They are controlled by the dpdk system.

You can test with  "snmpwalk -v 1 -m SNMPv2-MIB -c public ip_address .1.3.6.1.4" or from the same SA server with  snmpwalk -v 1 -m SNMPv2-MIB -c public localhost .1.3.6.1.4