Configure SNMP for agents deployed by SAM

SNMP is a polling method used by Orion agents to collect data about monitors and resources. Review this information if you need to troubleshoot connectivity, access, and polling issues in SAM.

The following components and widgets depend on SNMP connections:

  • Location, Contact, and SysObjectID of the Node Details resource
  • SAM SNMP component monitor
  • Hardware Health data and widgets
  • Asset Inventory page and widgets

    Hardware Health and Asset Inventory are not supported on AIX devices.

Configure SNMP

To configure SNMP, you need to install the SNMP daemon if it is missing. The Orion agent configures SNMP for you during deployment. You can manually configure SNMP. If settings need to be modified for Orion agent, the configurations are verified and updated during agent deployment.

On AIX computers, the auto-configuration is not supported. Make sure that SNMP daemon is running.

If you need to install the SNMP daemon, you can install the daemon using a command according to your Linux/Unix distribution. Deploying the agent automatically configures SNMP. If the SNMP daemon is not installed, SNMP cannot be configured.

To install a SNMP daemon on Linux:

  • Install on Ubuntu: sudo apt-get -y install snmpd
  • Install on Red Hat / CentOS: yum -y install net-snmp
  • Install on SUSE: zypper -y install net-snmp

Auto-configuration of SNMP on Linux executes on the following actions:

  • The first step during a Discovery
  • Anytime you initiate a List resource on any node managed by the Orion agent for Linux

SAM completes the following changes during auto-configuration:

  • Checks the snmpd service is configured to start automatically after system reboots.

  • Checks the snmpd.conf file for the configuration of an agent owned community string. If the string is missing, SAM adds the community string. The string is "agent owned" = with an SNMP v2 community string in form of an agent GUID (randomly generated value that is unique for each agent).

    For example:

    ### BEGIN SolarWinds Agent SNMP auto config
    rocommunity 36343901-D61F-4C72-B860-A8E18DD892E4 localhost
    ### END SolarWinds Agent SNMP auto config

    If SAM adds the community string, SNMP is restarted.

Configure SNMP v3

If you have SNMP v3 configurations detecting users through the configuration file without an SNMP v2 community string, SAM will not modify the configuration file. SNMP v3 will not be auto-configured on deployment. You can provide SNMP credentials manually at the node level to configure access.

Prerequisites

To add SNMP credentials, you can enter the credentials through the Add Node Wizard or edit an existing node. You cannot test the credentials until the agent is deployed.

For encryption, you also need to install a common python extension pycrypto on the target machine to make polling possible. To install:

PyCrypto installation on ubuntu
apt-get install python-pip
pip install pycrypto

Test Credentials

You can test any manually entered credentials by editing the Node. To test, you need a properly connected agent deployed to the target node. Review the credentials and click Test.

Enable the SNMP daemon on AIX computers

Use of the SNMP Monitor on AIX devices requires that the SNMP daemon be enabled. Otherwise, the following information will not be available in the Node Details widget:

  • Location
  • Contact
  • SysobjectID

To enable the SNMP daemon, update the configuration file in /etc/snmpdv3.conf which configures snmpv1, v2c, and v3 access. Use the following configuration example as a reference:

# Two snmpv1 community strings: public commstr1

VACM_GROUP group1 SNMPv1 public -

VACM_GROUP group1 SNMPv1 commstr1 -

VACM_VIEW group1view internet - included -

VACM_ACCESS group1 - - noAuthNoPriv SNMPv1 group1view - - -

COMMUNITY public public noAuthNoPriv 0.0.0.0 0.0.0.0 -

COMMUNITY commstr1 commstr1 noAuthNoPriv 0.0.0.0 0.0.0.0 -

# snmpv2c community string: swiagent

VACM_GROUP group2 SNMPv2c swiagent -

VACM_VIEW group2view internet - included -

VACM_ACCESS group2 - - noAuthNoPriv SNMPv2c group2view - - -

COMMUNITY swiagent swiagent - 0.0.0.0 0.0.0.0 -

COMMUNITY public public - 0.0.0.0 0.0.0.0 -

# snmpv3 user with no authorization: user1

USM_USER user1 - none - - - - -

VACM_GROUP group4 USM user1 -

VACM_VIEW group4view internet - included -

VACM_ACCESS group4 - - noAuthNoPriv USM group4view - - -

DEFAULT_SECURITY no-access - -

logging file=/usr/tmp/snmpdv3.log enabled

logging size=100000 level=3

Test the SNMP configuration

  • To test the configuration for v1 requests, use snmpdinfo.
  • To test v2c and v3 requests, use clsnmp for v2c and v3 requests and configure /etc/clsnmp.conf.
    v2cstring localhost snmpv2c
    v3user_noauth localhost snmpv3 user1 - - - - - - -

This configuration matches the examples above.