SNMP Glossary
SNMP carries a lot of jargon for a "simple" protocol. This SNMP glossary defines the snmp terms you'll meet across the rest of the site — agent, manager, OID, MIB, community, trap, PDU, USM, VACM, and the three protocol versions — in plain language, each with a link to the page that covers it in depth. The goal is snmp definitions you can actually use: short, correct, and grounded in real OIDs and RFCs rather than hand-waving. Skim it once and the sensor pages, setup guides, and error references all read faster.
Overview
Read this as a map, not a manual. Each entry gives you a working definition and a deep link, so you can settle a term in ten seconds and jump to the full treatment when you need it. To orient yourself, it helps to see how the biggest pieces fit before diving into the alphabet:
- A manager polls an agent over UDP.
- It asks for an OID, a numbered address for one value.
- A MIB gives that OID a name and meaning.
- A community string (v1/v2c) or USM credential (v3) controls access.
- The agent's reply, or a pushed trap, is carried in a PDU.
With that skeleton in mind, here's a quick expansion of the acronyms that repeat most, followed by the terms in alphabetical order.
| Acronym | Stands for |
|---|---|
| SNMP | Simple Network Management Protocol |
| OID | Object Identifier |
| MIB | Management Information Base |
| PDU | Protocol Data Unit |
| SMI | Structure of Management Information |
| USM | User-based Security Model |
| VACM | View-based Access Control Model |

Terms A–Z
Agent — The SNMP software running on a monitored device (on Linux, typically the Net-SNMP daemon snmpd). It holds the managed values and answers queries. See common SNMP questions.
Community string — The shared-secret access credential in SNMPv1 and v2c, sent with every request. Usually read-only for monitoring, and unencrypted in v2c, so it's a weak password best kept to a trusted network. More in common SNMP questions.
Diagnostics — The practice of proving an SNMP path works end to end with tools like snmpget and snmpwalk, isolating one variable at a time. Covered in SNMP diagnostics.
GET / GETNEXT — The two basic read operations. GET fetches one named OID; GETNEXT returns the next object in the tree and is how a walk traverses a table. See common SNMP questions.
GETBULK — A v2c operation that retrieves many table rows in a single request, making large walks far faster than chaining GETNEXT calls. Defined alongside the other SNMP standards.
Host Resources MIB — RFC 2790, the MIB that exposes a server's CPU, memory, storage, processes, and uptime — for example uptime at 1.3.6.1.2.1.25.1.1.0. These are the metrics in the sensor & OID catalog.
IF-MIB — RFC 2863, the MIB describing network interfaces, including 64-bit traffic counters in its ifXTable. Also in the sensor & OID catalog.
Manager — The station that polls agents, stores the results, and raises alerts. It sets the cadence, since SNMP is a pull protocol. See common SNMP questions.
MIB — A Management Information Base: the schema mapping numeric OIDs to human-readable names and data types. You poll OIDs and read MIBs to interpret them. Explained in common SNMP questions.
MIB-II — RFC 1213, the core MIB of standard system and interface objects that nearly every agent implements. Listed among the SNMP standards.
noSuchObject / noSuchInstance — v2c responses meaning the object type isn't implemented here, or the object exists but not the specific row you asked for. Decoded in SNMP error messages.
OID — An Object Identifier: a dotted-number path through the global management tree, such as 1.3.6.1.2.1.25.1.1.0. Each number narrows the scope. See common SNMP questions.
PDU — A Protocol Data Unit: the structured message that carries an SNMP request or response, including the operation type and the OID/value pairs.
Poll — A single request-and-response exchange, and by extension the scheduled act of querying an agent on a fixed interval. The foundation of reliable monitoring; see common SNMP questions.
RFC — A Request for Comments, the IETF document type that standardizes SNMP. RFC 1157 defines v1; the full set is mapped on the SNMP standards page.
SET — The write operation that changes a value on the agent. Powerful and usually disabled in read-only monitoring setups.
SMIv2 — RFC 2578, the Structure of Management Information version 2: the grammar every modern MIB is written in. Referenced on the SNMP standards page.
SNMPv1 — RFC 1157, the original protocol version. Simple, community-based, still found on legacy gear. See SNMP standards.
SNMPv2c — The community-based version 2 (RFC 1901/3416/3417), adding GETBULK and better error handling while keeping the plain-text community. The common choice for read-only monitoring; see SNMP standards.
SNMPv3 — RFC 3411–3418, the secure version, adding USM authentication/privacy and VACM access control. Detailed on the SNMP standards page.
Trap — An unsolicited notification an agent pushes to a manager (by convention on UDP 162) when an event fires. Fire-and-forget in v1/v2c. See common SNMP questions.
USM — The User-based Security Model in SNMPv3, providing authentication and encryption per user. Part of the SNMP standards.
VACM — The View-based Access Control Model in SNMPv3, deciding which users may read which OIDs. Also in the SNMP standards.
View / OID allowlist — The set of OID subtrees an agent will expose to a given community or user, configured in snmpd.conf. An OID outside the view returns nothing. See the OID allowlist guide.
