SECURITY Permission to manage Sites and manage Devices
NAVIGATION Sites > open a site > New Device
There are times when you would like to manage and monitor certain devices but you cannot install a Datto RMM Agent on them. For example, you may want to know when the data transfer rate of a switch port goes over a certain threshold, or if the battery in your UPS starts discharging, or whether you need to change your printer's toner. In instances when Agent installation is not possible, a fully Managed Network Node device can connect to and manage your device using Simple Network Management Protocol (SNMP).
This document is not intended to be a comprehensive SNMP theory tutorial; however, it offers the following:
- It details the Network Node requirements for SNMP monitoring.
- It provides some background information for SNMP monitoring in Datto RMM.
- It walks you through the process of adding an SNMP-enabled device as a Managed device to your account.
- It also mentions how to monitor your SNMP devices and refers you to the appropriate topic in the Datto RMM Help.
If you are not familiar and comfortable with the concepts, terminology, and technology around SNMP, we strongly recommend some background reading before you start with SNMP monitoring. There are a number of useful guides on the subject but here are a few examples that we've looked at and liked:
IMPORTANT The Network Node device performing SNMP monitoring must be compatible with the Microsoft .NET Core 3.1 runtime.
NOTE The Agent is not compatible with the Microsoft .NET Core 3.1 runtime standalone installation. The Agent will download and use a packaged version when prerequisites are met.
SNMP monitors configured on Network Nodes that do not support .NET Core 3.1 will automatically raise an alert in order to bring the issue to attention. The alert raised is worded as follows:
SNMP monitor is only supported by Agents with a compatible .NET runtime. For more details see dat.to/rmmagentreq.
If a subsequent two-hourly .NET Core 3.1 prerequisite check is successful, the alert will be resolved.
NOTE Network Node devices that do not use SNMP monitoring do not have to meet the .NET Core 3.1 runtime requirement.
.NET Core 3.1 is natively supported by all modern Windows operating systems:
- Windows 10
- Windows Server 2016
- Windows Server 2019
The following legacy Windows operating systems are supported with Windows Updates KB2999226 and KB2533623 installed:
- Windows 7 SP1
- Windows Server 2008 R2 SP1
The following legacy Windows operating systems are supported with Windows Update KB2999226 installed:
- Windows 8.1
- Windows Server 2012 R2
NOTE Windows Update KB2999226 is packaged with Microsoft Visual C++ 2015 Redistributable Update 3 or above. This includes Microsoft Visual C++ 2017 Redistributable.
NOTE Agents will check for .NET Core 3.1 compatibility at startup and subsequently every 2 hours. If the check is successful, a new binary will be downloaded and the AEMAgent process will restart.
macOS and Linux
.NET Core 3.1 also runs on macOS and Linux. The Datto RMM Agent running on these operating systems already uses .NET Core 3.1 to function.
Datto RMM SNMP monitoring relies on object identifiers (OIDs) to define the path through a device's OID tree to a managed object containing data to be monitored. OIDs follow a strict hierarchical pattern much like a computer directory structure; however, OIDs only use numbers to define a path.
EXAMPLE In the screenshot below, an OID of 184.108.40.206.4.1.9 would navigate to the root of the private enterprise node for Cisco. (Source: Network Management Software)
Another way of visualizing the OID tree is in the form of a folder structure that looks similar to a file explorer.
EXAMPLE The highlighted management object in the screenshot below would be referenced using the OID 220.127.116.11.18.104.22.168.1.8. (Source: Network Management Software)
Datto RMM does not have inbuilt OID browsing functionality so a third party tool is required to discover OIDs before configuring SNMP monitoring. OiDViEW SNMP MIB Browser is a popular choice and has a free version with some functional limitations (versus the licensed version).
Two types of SNMP managed objects exist:
- Scalar objects define a single object instance. In the examples in the OIDs section above, an OID is used to reference an SNMP management object directly, and it would return a single value.
- Tabular objects define multiple related object instances grouped in tables. Tabular objects can be visualized similarly to a spreadsheet or a database table:
The path to the root of the table is defined using an OID with additional numbers to indicate the row and column for which to retrieve data.
EXAMPLE For example, in the screenshot above, if 22.214.171.124.126.96.36.199 is the OID used to reference the root of the table, then adding .4 would indicate row 4 (or index 4), adding .10 would indicate column 10, making it 188.8.131.52.184.108.40.206.4.10. This would retrieve the value 758125 for ifInUcastPkts highlighted in the table.
Datto RMM SNMP monitoring allows you to monitor both scalar and tabular objects. If the SNMP monitor definition OID is marked as a table, the Datto RMM Agent will check the table from the root to discover all available instances and apply separate monitors for each one discovered.
Each monitored instance will have its own alert status and treat any tickets raised in Autotask PSA or ConnectWise Manage as separate entities if you have either of the integrations enabled.
To learn how to monitor your managed network devices using SNMP, refer to Configure an SNMP Monitor.
To be able to monitor your SNMP-enabled devices, you need to add them as Managed devices to one of your Managed sites.
One way to do it is to have a fully Managed Network Node device discover other devices for you. For further information, refer to Network discovery.
However, if the network scanning of SNMP devices is disabled for your account, or you are unable to find your device in the list of discovered devices, you can add it manually by following these steps:
- Refer to the first few steps outlined in Downloading or emailing the Agent installer to navigate to the correct site.
NOTE Network devices and printers can only be added to Managed sites.
- Click the Network or Printer icon as required.
- You will now be prompted with the Add a Network Device or Add a Network Printer window as per your selection in step 3.
- Fill in the following details:
|IP Address||Enter the IP address of your device.|
|Network Node||Select a Network Node device that will monitor your device. For more information about Network Nodes, refer to Network discovery.|
|Device Type||Only available for network devices. Select one of the following device types:
• Network Device (Firewall)
• Network Device (IP Phone)
• Network Device (NAS)
• Network Device (Network Appliance)
• Network Device (Other)
• Network Device (Router)
• Network Device (SAN)
• Network Device (Switch)
• Network Device (UPS)
|Name||Give your device a meaningful name.|
|Description||Enter a meaningful description.|
|Manufacturer||Enter the name of the manufacturer of your device.|
|Model||Enter the model of your device.|
|New SNMP Credentials||Enter the SNMP credentials of your device. For information on what to enter, refer to the SNMP Credentials section in Account Settings and Site Settings.|
|Use Account/Site SNMP Credentials||Choose this option if you have SNMP credentials stored at the account or site level. The Site SNMP Credentials will be displayed in addition to the SNMP credentials specified in Account Settings unless this option is disabled in Site Settings. For information on how to store the SNMP credentials for the entire account or at the site level, refer to the SNMP Credentials section in Account Settings and Site Settings.
You can also choose any of the Default SNMP Credentials (v1 and v2c, public) listed here.
- Click Save. Your SNMP device is now added as a Managed device to your account.
Once a network device has been enrolled, you can start monitoring it. SNMP monitoring is performed through a Network Node. For information on requirements, refer to Requirements.
For information about how to create a monitoring policy, refer to Create a Monitoring policy.