What is SNMP?
SNMP (Simple Network Management Protocol) is the standard protocol for reading status information from network devices. Switches, routers, access points, printers and UPS units generally support it.
The monitoring side asks the device for a specific value and the SNMP agent on the device answers. That is how interface traffic, temperature, CPU usage or link state can be read on a regular basis.
- 1
The monitor requests an OID
- 2
The SNMP agent on the device responds
- 3
The value is compared to a threshold
- 4
An incident opens when the threshold is crossed
The values you can read are limited to the OIDs the device supports.
What OID and MIB mean
An OID (Object Identifier) is the address of a single value you want to read. The MIB is the dictionary describing which OIDs exist on that device.
In practice this means what you can read is limited to the values the vendor publishes on that device. If a value is not in the MIB, SNMP cannot read it.
- Interface state and traffic counters
- CPU and memory usage
- Temperature, fan and power supply state
- Uptime and restart information
How the versions differ
SNMP v1 and v2c use a simple shared password called a community string and do not encrypt traffic. v3 adds user-based authentication and encryption.
Corporate networks prefer v3. Older devices may only offer v2c, in which case restricting access at network level is common practice.
How to set up SNMP monitoring
Reading every value is not good monitoring; the more data you produce, the harder the meaningful signal is to see. A healthy setup starts with the few values closest to user impact and grows as needed.
In Sentry, SNMP checks are defined in a monitoring template; values read are compared with thresholds and an incident opens when one is crossed. Changing device configuration, writing values or remote management are out of scope.
- Start with interfaces that affect users directly
- Then trend values such as capacity and temperature
- Set thresholds separately per device type
- Read results together with reachability checks