Simple definition
SNMP lets monitoring software read device information such as interface state, traffic, temperature or availability. An agent on the device exposes these values. The device can also send notifications without waiting for the monitoring platform’s next scheduled query.
Technical definition
Simple Network Management Protocol uses objects identified by OIDs and described in MIBs. A manager queries agents, commonly over UDP 161. Notifications typically go to UDP 162: an SNMP trap does not request an SNMP-level acknowledgement, while an inform does. SNMPv3 can provide authentication and privacy; authPriv must be explicitly configured with compatible security parameters.
What is it used for?
Monitor switches, routers, UPS devices, printers and servers alongside other checks. Counters support trend analysis, while notifications can accelerate event detection. Neither mechanism alone provides complete evidence of end-to-end service health.
Practical example
Monitoring tracks a switch port’s error counters. A notification subsequently reports the link going down. The team correlates both observations and checks the neighboring device rather than assuming that a single traffic measurement identifies the failure’s cause.
Common issues
- Weak communities or excessive read permissions in SNMPv1/v2c.
- Incompatible SNMPv3 credentials, security levels or algorithms.
- An unsupported OID, unsuitable MIB or filtered UDP traffic.
Operational checks
A TCP connection test on port 161 does not validate SNMP over UDP. Send an authorized SNMP query for a known OID and inspect responses, timeouts and logs. Check notification destination settings and collector receipt separately from polling.
- Confirm the version and security profile configured at both ends.
- Query a known OID from the authorized collector.
- Check UDP 161 for requests and UDP 162 for notifications.
- Validate the monitoring system’s interpretation of values, units and counters.
What to distinguish
| Element | Role |
|---|---|
| Manager | Collector that queries device agents. |
| Agent | Device service exposing managed objects. |
| OID / MIB | Object identifier and its semantic description. |
| Trap / inform | Notifications without or with SNMP-level acknowledgement. |
Limits and precautions
Avoid unnecessary Internet exposure. Restrict sources, accessible objects and permissions, and prefer SNMPv3 authPriv where supported. Loading a MIB does not make an OID available if the device agent does not implement it. Confirm that successful data collection results in useful monitoring and actionable alerts.
Official documentation
Related terms
Key takeaway: SNMP, Simple Network Management Protocol, collects network-device status and counters and supports device notifications.