SNMP Asset

The SNMP asset provisioning adapter collects SNMP values to populate asset records for the node. This can be very useful for automatically populating asset fields in a large number of managed systems. Depending on the SNMP MIBs that your devices support, you could either fill in some of the existing asset fields (for example, manufacturer, vendor, modelnumber, and/or serialnumber) or construct a custom-formatted message for the comment field.

The SNMP asset provisioning adapter is invoked every time provisiond adds or updates a node. With the default provisiond configuration, the update takes place once every 24 hours.

You can reload the provisiond SnmpAssetProvisioningAdapter with this command (or just restart OpenNMS):

${OPENNMS_HOME}/bin# ./ --parm 'daemonName Provisiond.SnmpAssetProvisioningAdapter'
By default, this adapter runs 5 minutes after a provisiond nodeScanCompleted event is sent to indicate that provisiond completed the import.


To use this feature you have to install the SNMP asset provisioning plugin from the repository.

  • For RPM-based distributions:

    • yum install opennms-plugin-provisioning-snmp-asset

  • For Debian-based distributions:

    • apt-get install opennms-plugin-provisioning-snmp-asset


Mapping SNMP OID fields to node asset fields is defined in the ${OPENNMS_HOME}/etc/snmp-asset-adapter-configuration.xml file.

Example SNMP asset config
<?xml version="1.0" encoding="UTF-8"?>
    <package name="ciscoWireless">
    <!-- A Cisco wireless sysoid, for example purposes only :) -->
    <assetField name="region" formatString="${gsmCountry}">
            <!-- A Cisco 3G WAN adapter OID -->
            <mibObj oid="." alias="gsmCountry"/>
    <package name="Cisco">
        <assetField name="ram" formatString="${processorRam}">
                <mibObj oid="." alias="processorRam"/>

Variables in the formatString using the ${token} syntax will be replaced by values that are defined by the list of mibObj parameters.

In this configuration example, every node whose sysoid equals . will be matched by the "ciscoWireless" package. The adapter will get the OID value . and place the value in the "region" field in the asset database.

You may want to snmpwalk your target nodes and see if there are any interesting identifiers or string values that you would like to see in an asset field first. Once you identify the mibObjs to use, add them under a package that matches the device sysoid, Horizon will be set to start collecting data.

You may specify any number of <sysoid> or <sysoidMask> tags in the config file.