librenms-librenms/doc/Support/SNMP-Configuration-Examples.md

source: Support/SNMP-Configuration-Examples.md

SNMP configuration examples

Table of Content:

• Devices
  • Cisco
    • Adaptive Security Appliance (ASA)
    • IOS / IOS XE
    • NX-OS
    • Wireless LAN Controller (WLC)
  • HPE 3PAR
    • Inform OS 3.2.x
  • Infoblox
    • NIOS 7.x+
  • Juniper
    • Junos OS
  • Mikrotik
    • RouterOS 6.x
  • Palo Alto
    • PANOS 6.x/7.x
• Operating systems
  • Linux (snmpd v2)
  • Linux (snmpd v3)
  • Windows Server 2008 R2
  • Windows Server 2012 R2 and 2016
  • Mac OSX

Devices

Cisco

Adaptive Security Appliance (ASA)

ASDM

1. Launch ASDM and connect to your device
2. Go to Configuration > Management Access > SNMP
3. Add your community string
4. Add in the "SNMP Host Access List" section your LibreNMS server IP address
5. Click Apply and Save

CLI

# SNMPv2c

snmp-server community <YOUR-COMMUNITY>
snmp-server contact <YOUR-CONTACT>
snmp-server location <YOUR-LOCATION>
snmp-server host <INTERFACE> <LIBRENMS-IP> poll community <YOUR-COMMUNITY> version 2c

# SNMPv3

snmp-server group <GROUP-NAME> v3 priv
snmp-server user <USER-NAME> <GROUP-NAME> v3 auth sha <AUTH-PASSWORD> priv aes 128 <PRIV-PASSWORD>
snmp-server contact <YOUR-CONTACT>
snmp-server location <YOUR-LOCATION>
snmp-server host <INTERFACE> <LIBRENMS-IP> poll version 3 <USER-NAME>

IOS / IOS XE

# SNMPv2c
 
snmp-server community <YOUR-COMMUNITY> RO
snmp-server contact <YOUR-CONTACT>
snmp-server location <YOUR-LOCATION>

# SNMPv3

snmp-server group <GROUP-NAME> v3 priv
snmp-server user <USER-NAME> <GROUP-NAME> v3 auth sha <AUTH-PASSWORD> priv aes 128 <PRIV-PASSWORD>
snmp-server contact <YOUR-CONTACT>
snmp-server location <YOUR-LOCATION>

# Note: The following is also required if using SNMPv3 and you want to populate the FDB table.

snmp-server group <GROUP-NAME> v3 priv context vlan- match prefix 

NX-OS

# SNMPv2c

snmp-server community <YOUR-COMMUNITY> RO
snmp-server contact <YOUR-CONTACT>
snmp-server location <YOUR-LOCATION>

# SNMPv3

snmp-server user <USER-NAME> <GROUP-NAME> v3 auth sha <AUTH-PASSWORD> priv aes 128 <PRIV-PASSWORD>
snmp-server contact <YOUR-CONTACT>
snmp-server location <YOUR-LOCATION>

Wireless LAN Controller (WLC)

1. Access the web admin page and log in
2. If you are running version 8.1 and later, on the new dashboard click "Advanced"
3. Go to management Tab
4. On SNMP sub-menu, select "Communities"
5. Click "New..."
6. Add your community name and leave IP addresses empty
7. Click Apply and Save

HPE 3PAR

Inform OS 3.2.x

• Access the CLI
• Add an SNMP Manager with your LibreNMS IP address:

addsnmpmgr <librenms ip>

• Add your SNMP community:

setsnmppw <community>

Infoblox

NIOS 7.x+

1. Access the web admin page and log in
2. Go to Grid tab > Grid Manager
3. In the right menu select "Grid properties"
4. Select "SNMP" menu
5. Click "Enable SNMPv1/SNMPv2 Queries"
6. Add your community
7. Click Save & Close

Juniper

Junos OS

set snmp description description
set snmp location location
set snmp contact contact
set snmp community YOUR-COMMUNITY authorization read-only

Mikrotik

RouterOS 6.x

#Terminal SNMP v2 Configuration
/snmp community
set [ find default=yes ] read-access=no
add addresses=<SRC IP/NETWORK> name=<COMMUNITY>
/snmp
set contact="<NAME>" enabled=yes engine-id=<ENGINE ID> location="<LOCALTION>"

Palo Alto

PANOS 6.x/7.x

1. Access the web admin page and log in
2. Go to Device tab > Setup
3. Go to the sub-tab "Operations"
4. Click "SNMP Setup"
5. Enter your SNMP community and then click "OK"
6. Click Apply

Note that you need to allow SNMP on the needed interfaces. To do that you need to create a network "Interface Mgmt" profile for standard interface and allow SNMP under "Device > Management > Management Interface Settings" for out of band management interface.

Operating systems

Linux (snmpd v2)

Replace your snmpd.conf file by the example below and edit it with appropriate community in "RANDOMSTRINGGOESHERE".

vi /etc/snmp/snmpd.conf

# Change RANDOMSTRINGGOESHERE to your preferred SNMP community string
com2sec readonly  default         RANDOMSTRINGGOESHERE

group MyROGroup v2c        readonly
view all    included  .1                               80
access MyROGroup ""      any       noauth    exact  all    none   none

syslocation Rack, Room, Building, City, Country [GPSX,Y]
syscontact Your Name <your@email.address>

#Distro Detection
extend .1.3.6.1.4.1.2021.7890.1 distro /usr/bin/distro

If you have 'dmidecode' installed on your host, you can add the following lines for additional hardware detection.

NOTE: On some systems the snmpd is running as an own user, making dmidecode unable to read out /dev/mem and thus showing multiple errors. Either add the snmp user to the kmem group or remove these lines again.

extend .1.3.6.1.4.1.2021.7890.2 hardware '/usr/sbin/dmidecode -s system-product-name'
extend .1.3.6.1.4.1.2021.7890.3 manufacturer '/usr/sbin/dmidecode -s system-manufacturer'
extend .1.3.6.1.4.1.2021.7890.4 serial '/usr/sbin/dmidecode -s system-serial-number'

The LibreNMS server include a copy of this example here:

/opt/librenms/snmpd.conf.example

The binary /usr/bin/distro must be copied from the original source repository:

curl -o /usr/bin/distro https://raw.githubusercontent.com/librenms/librenms-agent/master/snmp/distro
chmod +x /usr/bin/distro

Linux (snmpd v3)

Go to /etc/snmp/snmpd.conf

Open the file in vi or nano /etc/snmp/snmpd.conf and add the following line to create SNMPV3 User (replace username and passwords with your own):

createUser authPrivUser MD5 "authPassword" DES "privPassword"

Make sure the agent listens to all interfaces by adding the following line inside snmpd.conf:

agentAddress udp:161,udp6:[::1]:161

This line simply means listen to connections across all interfaces IPv4 and IPv6 respectively

Uncomment and change the following line to give read access to the username created above (rouser is what LibreNMS uses) :

#rouser authPrivUser priv

Change the following details inside snmpd.conf

syslocation Rack, Room, Building, City, Country [GPSX,Y]
syscontact Your Name <your@email.address>

Save and exit the file

Restart the snmpd service:

CentOS 6 / Red hat 6

service snmpd restart

CentOS 7 / Red hat 7

systemctl restart snmpd

Ubuntu

service snmpd restart

Windows Server 2008 R2

1. Log in to your Windows Server 2008 R2
2. Start "Server Manager" under "Administrative Tools"
3. Click "Features" and then click "Add Feature"
4. Check (if not checked) "SNMP Service", click "Next" until "Install"
5. Start "Services" under "Administrative Tools"
6. Edit "SNMP Service" properties
7. Go to the security tab
8. In "Accepted community name" click "Add" to add your community string and permission
9. In "Accept SNMP packets from these hosts" click "Add" and add your LibreNMS server IP address
10. Validate change by clicking "Apply"

Windows Server 2012 R2 and 2016

1. Log in to your Windows Server 2012 R2
2. Start "Server Manager" under "Administrative Tools"
3. Click "Manage" and then "Add Roles and Features"
4. Continue by pressing "Next" to the "Features" menu
5. Install (if not installed) "SNMP Service"
6. Start "Services" under "Administrative Tools"
7. Edit "SNMP Service" properties
8. Go to the security tab
9. In "Accepted community name" click "Add" to add your community string and permission
10. In "Accept SNMP packets from these hosts" click "Add" and add your LibreNMS server IP address
11. Validate change by clicking "Apply"

Mac OSX

Step 1: sudo nano /etc/snmp/snmpd.conf

#Allow read-access with the following SNMP Community String:
rocommunity public

# all other settings are optional but recommended.

# Location of the device
syslocation data centre A

# Human Contact for the device
syscontact SysAdmin

# System Name of the device
sysName SystemName

# the system OID for this device. This is optional but recommended,
# to identify this as a MAC OS system.
sysobjectid 1.3.6.1.4.1.8072.3.2.16

Step 2:

sudo launchctl load -w /System/Library/LaunchDaemons/org.net-snmp.snmpd.plist