SNMP
What It Is
SNMP (Simple Network Management Protocol) is a standard, widely-deployed protocol for monitoring and managing devices on an IP network — routers, switches, servers, and (increasingly) purpose-built site equipment. It gives network administrators, and the monitoring software they use, a common way to query a device's status, read its performance and health data, change configuration values remotely, and receive proactive alerts when something on the device changes state or fails.
Core Concepts
- Manager / Agent model. SNMP works as a client-server relationship: an SNMP manager (a central network management station or monitoring application) issues requests to gather data or push configuration changes, while an SNMP agent — a small piece of software running on the managed device itself — listens for those requests, responds with the requested data, and can also proactively notify the manager of events.
- MIB (Management Information Base). Each device exposes its monitorable and configurable data points through a structured, hierarchical database called a MIB. The MIB defines what information exists on that device (e.g., interface status, temperature, uptime, alarm state) and how it's organized, so both the agent and the manager have a shared, standardized understanding of the device's data.
- OID (Object Identifier). Every individual data point inside a MIB is addressed by a unique numeric OID — essentially the "address" the manager uses to ask for one specific value, such as a particular interface's link status or a particular alarm input's current state.
- GET / SET operations. A manager uses a GET request to retrieve the current value of an OID from an agent, and a SET request to write a new value to an OID, allowing remote configuration changes to be pushed to the device.
- TRAP messages. Unlike GET/SET, which are always initiated by the manager, a TRAP is a message the agent sends to the manager on its own initiative — an unsolicited alert that something happened (e.g., a link went down, a threshold was crossed, an alarm input tripped) without waiting to be asked. This is what allows SNMP-based monitoring to be proactive/event-driven rather than purely poll-based.
Versions and Security
SNMP has evolved through three major versions, primarily differing in security model:
- SNMPv1 and SNMPv2c — the original and most widely-supported versions. Both authenticate requests using a community string, essentially a shared plaintext password sent along with every request. This string is transmitted in clear text, is not encrypted, and offers only weak, easily-intercepted security — acceptable only on trusted, isolated management networks. SNMPv2c added performance and usability improvements (such as 64-bit counters and bulk-retrieval operations) over v1, but kept the same weak community-string security model.
- SNMPv3 — adds a real security model: user-based authentication (verifying who is making the request) and encryption (protecting the data in transit from eavesdropping and tampering), along with access control. SNMPv3 is the version recommended wherever the monitored data or configuration access needs genuine protection, rather than relying on network isolation alone.
Related Pages
References
- SNMP MIBs & SNMP OIDs Explained - SNMP Architecture Guide, Comparitech
- SNMP Protocol Explained: GET, SET, TRAP Operations, MIB & OID Structure, justprotocols
- Understanding Simple Network Management Protocol (SNMP) Traps, Cisco
- How do SNMP, MIBs, and OIDs work?, Paessler Knowledge Base
- SNMP v2 vs v3 - what are the differences?, Domotz
- SNMP Versions: V1, V2c, or V3 — Which is Best for Your Network Security?, LogicMonitor
- GCM 8000 Trunking Comparator, Motorola Solutions
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.