SNMP Monitoring

Domotz allows you to monitor TCP Services and SNMP (v1, v2, v3) objects available on your connected devices.

Note: If you are not familiar with the SNMP protocol, here is a blog post to help get you started.
 
Here is a useful example of monitoring Server Room Temperature using SNMP Sensors.

Here are some other helpful articles on TCP Service Monitoring and using SNMP and TCP with configuration samples.

Monitoring SNMP objects

Domotz allows you to monitor SNMP OIDs by periodically polling the device and displaying the extracted value. Here is a summary:

  • Domotz provides features to facilitate MIB navigation and identify the right OIDs.
  • Numerical values are also put into charts.
  • You can configure alerts, based on conditions of the extracted values.
  • You can change the polling frequency.
  • SNMP versions v1, v2 and v3 are supported.

Enabling SNMP Monitoring on a device

The first step is to make sure that SNMP is enabled on the device you want to monitor.

The next step is to tell Domotz the related credentials. This can be done from the Device Access Manager, in the upper part of the Device Details screen:

SNMP Monitoring screenshot 1

A dialog box for inserting the credentials will be prompted:

SNMP and TCP screenshot 6

SNMP status

SNMP status is shown in the Device details view. At each point in the process, you can edit the authentication configuration or force a new retry.

Status “Checking”

The status will show as checking, for a newly discovered device. The same status will be displayed when selecting “Retry now”.

SNMP monitoring status checking

Status “Reading”

The status “Reading” is displayed when Domotz is allowed to read SNMP data from the device, using either the default communities (in case of SNMP v1, v2) or the user-defined authentication configuration (for SNMP v1, v2, v3).


SNMP Status “Service not found”

The status, “Service not found” is displayed if the Agent detects that the required UDP port 161 is closed:

SNMP monitoring status service not found

Status “Unable to read from SNMP service”

This status is displayed when the UDP port 161 is opened but the agent is not capable of retrieving data using the current authentication configuration.

SNMP status unable to read status

Configuring SNMP sensors

In the Device Details screen go to the SNMP tab and click on Add an SNMP Sensor.

The following dialog will appear. If Domotz already knows the MIB corresponding to the device a navigation panel will allow you to select the right OID to monitor.

SNMP and TCP screenshot 7

If Domotz does not have any MIB associated, you can still configure OIDs manually by clicking on Manually define an SNMP Sensor. Enter the OID you want to monitor and assign a name, description and type to it.

SNMP and TCP screenshot 8

Domotz will confirm that the OID is in the correct format but it is unable to verify the value entered is valid.

The type of value the OID will return must match the manufacturer documentation and is important for the types of Alerts you want to create.

IMPORTANT:
If Domotz does not show you the MIB of a device and you have the MIB of that device, please contact us on support@domotz.com. If you provide the MIB to us, we can insert it into the system, to improve future MIB detection for all users.

In case Domotz does not show you the MIB of a device and you do not know the OID, you can try to find it with a MIB Browser.

Monitoring SNMP sensors

Once you have configured your sensors you will see them listed in the SNMP section. This will include the value the device is returning for that OID and the last time the information was updated.

SNMP and TCP screenshot 9

Domotz also keeps the history of numerical OIDS. By clicking on the chart icon you will see a chart like the following:

SNMP and TCP screenshot 10

Alerts on SNMP sensors

You can configure alerts on the SNMP sensors you have created from the Alerts section of the device:

SNMP Monitoring - Alerts on SNMP Sensors

Domotz will ask you to choose one of the sensors you have already created (and it will also prompt you to create a new one if desired):

SNMP and TCP screenshot 12

After choosing a sensor, you will be able to configure the alert. Assign a Name, Condition, and the Communication Channel for the alert:

SNMP and TCP screenshot 13

And, finally, the alert is configured:

SNMP and TCP screenshot 14

Learn more about SNMP and TCP usage and sampling configuration.

Other uses of SNMP within Domotz

SNMP is a powerful protocol. It is also used by Domotz to implement Network mapping algorithms, PoE management as well as Network Interface Monitoring. Please refer to the respective sections for more details.

It’s important to note that these features are only available if Domotz knows the SNMP credential of a device.

Please make sure that these are configured through the Access Manager of devices:

SNMP Moniroting - other usages

Updated on July 8, 2021

Was this article helpful?