• Glossary
  • What is SNMP (Simple Network Management Protocol module)?

Network observability glossary

What is SNMP (Simple Network Management Protocol module)?

An SNMP module (Simple Network Management Protocol module) is a unit of management definition or agent software that exposes a set of managed objects on a device. It is usually written as a MIB module using the structure of management information, and a manager reads or sets its objects through SNMP.

Let's simplify your DDI
Abstract isometric UI showing network ranges, usage bars, region names (EMEA/APAC), and a purple "Deploy" button
Key takeawaysKey takeaways are generated with AI assistance. Because automated summaries can occasionally contain errors or miss important context, always refer to the full blog post for complete information.

An SNMP module is a unit of management definition or agent software that exposes managed objects on network devices, functioning either as a MIB module file describing objects or as software implementing them on an agent. The module determines what a monitoring system can see and query from devices like routers, switches, DNS servers, and DHCP servers, with managers communicating via UDP port 161 for requests and port 162 for traps. Missing or outdated modules result in unreadable numeric identifiers, incomplete dashboards, and missed alerts, while weak security practices and uncontrolled module libraries create inconsistent monitoring and expanded attack surfaces that require SNMPv3 encryption and access restrictions to mitigate.

  • MIB modules follow RFC 2578 structure of management information standards and are transported over UDP ports 161 and 162, enabling agents to send unsolicited traps or notifications when events occur without requiring manager polling.
  • Vendors ship device-specific SNMP modules beyond standard definitions, and managers can only interpret objects whose corresponding modules have been loaded and imported into the monitoring system.
  • SNMP versions 1 and 2c transmit community strings in clear text, creating security vulnerabilities, whereas SNMPv3 implements user-based security with authentication and encryption as defined in RFC 3414 to protect managed objects and prevent unauthorized configuration changes.

SNMP module at a glance

AttributeValue
Full nameSimple Network Management Protocol module
CategoryNetwork management component
Defined inMIB modules follow the structure of management information version 2, as defined in RFC 2578
Protocol and portSNMP over UDP, port 161 for requests and port 162 for traps and notifications
OSI layerApplication layer
Primary useDescribing and exposing device data and settings for monitoring and management
Related termsSNMP, MIB, OID, SNMP agent, SNMP trap, network monitoring

How SNMP module works

The term is used in two related ways: a MIB module that describes managed objects, and a software module in an agent that implements them. Either way, the module defines what a manager can ask a device.

  1. Define the objects: A MIB module written under the structure of management information names each object, gives its data type and access level, and places it in the object identifier tree.
  2. Load the module: The monitoring system imports the MIB module so it can translate numeric object identifiers into readable names and types.
  3. Implement it in the agent: The agent on the device supplies live values for the objects the module defines, such as interface counters or system uptime.
  4. Query or set objects: The manager sends requests to the agent on UDP port 161, and the agent returns values or applies permitted changes.

Agents can also send unsolicited traps or notifications to a manager on UDP port 162 when an event occurs. Vendors often ship extra modules for device-specific data beyond the standard ones. A manager can only interpret objects whose module it has loaded.

Why SNMP module matters in enterprise networks

SNMP modules determine what a monitoring platform can see. A fleet of routers, switches, DNS servers and DHCP servers may each expose standard and vendor-specific objects, and the manager needs the matching modules to read them. Missing or outdated modules lead to unnamed numeric identifiers, gaps in dashboards, and alerts that never fire because a counter was never polled.

Security depends on the SNMP version in use. SNMP versions 1 and 2c authenticate with a community string sent in clear text, so anyone who captures it can read objects and, if write access is allowed, change settings. SNMPv3 adds authentication and encryption through its user-based security model, defined in RFC 3414. Modules that expose writable objects deserve extra scrutiny because they turn a monitoring channel into a configuration channel.

Managing modules badly causes quiet failures. Teams that never track which modules are loaded, which devices implement them, and which objects are writable end up with inconsistent monitoring, excessive polling, and exposed management interfaces. Keeping a controlled module library, restricting write access, and using SNMPv3 where devices support it keep the data accurate and the attack surface small.

SNMP module vs Simple Network Management Protocol (SNMP)

SNMP is the protocol that carries management requests and responses, while an SNMP module is the definition or agent software that determines which objects those messages can reach. What is SNMP?

AttributeSNMP moduleSimple Network Management Protocol (SNMP)
RoleDescribes or implements a set of managed objectsTransports queries, responses and notifications between manager and agent
FormA MIB module file or an agent software componentA protocol with versions 1, 2c and 3
Where it livesLoaded on the manager and implemented in the agentRuns between the manager and the agent
Effect of absenceObjects appear as unnamed numeric identifiers or are not availableNo management communication takes place

Common SNMP module issues

A device is polled successfully but its objects show as raw numeric identifiers, or dashboards have no data for features such as DNS or DHCP statistics. The cause is usually that the vendor MIB module was never imported into the monitoring system.

A MIB module fails to load because it imports definitions from another module that is not present. Loading the required modules first, in the correct order, resolves most compile errors.

After a firmware update, objects change or move, and thresholds built on the old identifiers stop firing. The monitoring system needs the updated module, and alert rules must be checked against it.

The MIB module loads cleanly but a walk returns no value for some objects. The module only defines the objects; the agent on that device model or software version may not implement them.

Devices left with default or widely shared community strings on SNMP versions 1 and 2c allow anyone who captures or guesses the string to read objects, and to set them if write access is enabled. SNMPv3 with authentication and encryption avoids this.

See how unified DDI simplifies network operations

Manage DNS, DHCP and IP addresses from one platform with automation, visibility and control built in.

Talk to us

SNMP module FAQ

Related terms

Article

Simple Network Management Protocol (SNMP)

A protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behavior.

Learn more
Article

DNS – Domain Name System

A hierarchical naming system that enables communication across devices in a network.

Learn more
Article

DHCP (Dynamic Host Configuration Protocol)

The standard mechanism to dynamically assign IP addresses within a network.

Learn more
Article

DDI (DNS, DHCP, and IPAM)

The integration of DNS, DHCP, and IPAM into one management solution.

Learn more
Article

IPAM (IP address management)

A method for planning, tracking, and managing IP address space on a network.

Learn more
Article

DNS server

Also called a DNS nameserver, it stores DNS records and responds to and resolves DNS queries from devices. Learn More

Learn more
Article

Transport layer security (TLS)

A cryptographic protocol to provide communications security over a computer network.

Learn more
Article

ACL (Access Control List)

Limits which entities are allowed to perform certain functions against a DNS server, such as sending queries or performing dynamic updates.

Learn more
Browse the full glossary