Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.7 Administrator Guide > Monitor with Orion agents in SAM > Configure SNMP for agents for SAM

Configure SNMP for agents for SAM

Updated: 3-9-2017

SNMP is a polling method used by Orion agents and as default to collect for monitors and resources. Review this information to locate and resolve any issues when troubleshooting connectivity, access, and data polled in SAM.

The following components and resources depend on SNMP connections:

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

Configure SNMP

To configure SNMP, you need to install the SNMP daemon if 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.

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

To install:

  • 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 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.


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.


Last modified