A management application communicates with an SNMP agent that exposes structured management information. That data is organized as objects identified by object identifiers (OIDs) and described through management information bases (MIBs).
SNMP operations can read individual or sequential values, retrieve larger collections, change permitted values, and carry notifications such as traps or informs. Uses include collecting interface counters, device status, and configuration facts. SNMPv1, community-based SNMPv2c, and the SNMPv3 framework have materially different message and security capabilities.
Key points
Management dataStandard and vendor-defined MIB modules describe object names, types, access, and semantics; an OID alone does not explain how a value should be interpreted.
OperationsGET, GETNEXT, GETBULK, SET, response, and notification operations support polling, controlled changes, and event reporting.
Security designSNMPv3 can use the User-based Security Model for message authentication and privacy and the View-based Access Control Model to limit accessible management data.
Important limitationChoosing “SNMPv3” does not by itself create secure management. Weak security levels, keys, or algorithms, broad views, exposed management interfaces, and unnecessary write access can still create serious risk; community-based SNMPv1 and SNMPv2c do not provide comparable cryptographic protection.