SNMP (Simple Network Management Protocol) is a standard protocol used to monitor and manage network-connected devices. It enables Atera to retrieve performance and availability data from compatible hardware across your network.
Examples of SNMP-compatible devices include:
Network routers and switches
Firewalls and security appliances
Wireless access points
Servers (Windows, Linux, UNIX)
Printers and scanners
Load balancers
Storage systems (NAS, SAN)
UPS and PDU units
CCTV cameras
Virtualization platforms (e.g., VMware, Hyper-V)
SNMP Requirements
Before adding an SNMP device in Atera, ensure the following requirements are met:
SNMP is enabled on the device.
Port 161 (UDP) is open and accessible.
The device and the Atera agent are on the same local network (subnet).
The device supports SNMP v1, v2c, or v3.
SNMP traps are not supported — Atera performs monitoring through SNMP polling.
If you’re unsure whether a device supports SNMP, consult the manufacturer’s documentation or their website.
Testing SNMP Connectivity
If your SNMP device cannot be added to Atera, you can test connectivity using Paessler SNMP Tester:
1. Initiate a remote connection to the customer's device and verify that it is operating on the same network as the SNMP device they intend to monitor.
2. Install Paessler on the customer's device.
3. Open Paessler on the customer's device.
4. Add the details, including the IP address, SNMP version, port, and communitystring.
It's important to note that the community string is case-sensitive, so ensure that you input the exact string the customer has configured. It is essential for the customer to know or supply these details. If the customer is unable to provide this information, we will be unable to offer assistance.
5. Opt for the "Custom OID" option and input the specified OID into Paessler. This OID is employed to retrieve the hostname of a device. By querying the machine name in this manner, we can ascertain the availability of the SNMP device. Initiate the querying process by clicking on 'Start'.
1.3.6.1.2.1.1.1.0
Sample output
Paessler SNMP Tester - 23.3.87.552 Computername: DRAGOS-LAPTOP Interface: (10.4.8.76, 172.28.80.1)
24-Oct-23 10:15:07 AM (1 ms) : Device: 10.4.11.37
24-Oct-23 10:15:07 AM (2 ms) : SNMP v1
24-Oct-23 10:15:07 AM (3 ms) : Custom OID 1.3.6.1.2.1.1.1.0
24-Oct-23 10:15:08 AM (124 ms) : SNMP Datatype: ASN_OCTET_STR
24-Oct-23 10:15:08 AM (126 ms) : -------
24-Oct-23 10:15:08 AM (128 ms) : Value: HP ETHERNET MULTI-ENVIRONMENT
24-Oct-23 10:15:08 AM (129 ms) : Done
Common Errors and Solutions
“Failed to add device due to an unknown error”
This is typically caused by a connection issue between the Atera agent and the SNMP device.
Check the following:
The SNMP service is enabled on the device.
The correct SNMP version and community string are being used.
Port 161 is open and not blocked by a firewall.
Both devices are on the same network.
“Value: NULL”
The SNMP device did not return data. This usually indicates:
The queried OID does not exist on the device.
SNMP is not properly configured.
The device’s hostname or data value is unavailable.
“SNMP Error #2003”
This error indicates that the device is not responding to SNMP queries.
It may be caused by:
Firewall or routing restrictions.
SNMP disabled or configured incorrectly.
Port 161 being closed or filtered.
For additional details, refer to Paessler’s article:
PRTG - SNMP Error #2003
Verifying OIDs
Each SNMP component (e.g., CPU, temperature, ink level) is identified by a unique Object Identifier (OID).
You can find OIDs by:
Checking the manufacturer’s documentation
Searching online OID repositories
Using shared SNMP template libraries
Utilizing Atera’s AI OID Generator
Example:1.3.6.1.2.1.1.1.0 – retrieves the device’s hostname.
You can add these OIDs in Atera to display values such as uptime, temperature, or toner level. Values update every 2 minutes.
Interpreting Graph Indicators
The alert graph in Atera shows device alert activity over time:
Each point represents a one-hour period.
Red points indicate an hour during which an alert was active.
Alerts may represent any type (availability, performance, or custom thresholds).
This helps you quickly visualize when an SNMP device experienced performance or connectivity issues.
