Simple Network Management Protocol

Simple Network Management Protocol
Name	Simple Network Management Protocol
Caption	SNMP communication model
Developer	Internet Engineering Task Force
Initial release	1988
Latest release	RFC revisions
Status	Draft/Standard

Simple Network Management Protocol

Simple Network Management Protocol is an application-layer protocol for monitoring and managing networked devices such as router, switch, server, workstation, printer, and firewall hardware. It enables administrators using tools from vendors like Cisco Systems, Juniper Networks, Hewlett-Packard, and Dell EMC to collect performance metrics, configure interfaces, and receive fault notifications from agents embedded in devices. Early adoption by organizations including Bell Labs, University of California, Berkeley, and commercial providers such as AT&T and Sprint Corporation helped it become a pervasive element of enterprise and service-provider operations, with support from standards bodies like the Internet Engineering Task Force and Internet Architecture Board.

Overview

The protocol operates over transport layers often provided by User Datagram Protocol and, in later revisions, Transmission Control Protocol or Transport Layer Security channels implemented by vendors including Microsoft, Apple Inc., IBM, and Oracle Corporation. Network management systems produced by companies such as SolarWinds, Micro Focus, NetScout Systems, Nagios Enterprises, and Zabbix SIA use SNMP to interrogate agents on equipment from Huawei Technologies, Arista Networks, Brocade Communications Systems, and VMware. SNMP’s simplicity and extensibility influenced adjacent standards like Remote Network Monitoring, Network Configuration Protocol, and management frameworks adopted by Amazon Web Services, Google Cloud Platform, and Microsoft Azure.

Architecture and Components

The architecture defines roles such as manager and agent, supported by management stations produced by IBM and HPE Aruba. Managed devices store data in a structured database accessible through SNMP agents developed by vendors such as Net-SNMP Project and OpenNMS. Data models are organized in object identifiers maintained by registries overseen by the IANA and by standards committees including the IETF Network Management Research Group. Integration points include interfaces to systems like Syslog, RADIUS, TACACS+, and orchestration platforms such as Ansible, Puppet, and SaltStack.

Protocol Operations and Message Types

Operations include retrieval and update primitives such as GET, GET-NEXT, GET-BULK, SET, and TRAP messages that are implemented in agents by companies such as Cisco Systems and Juniper Networks. The protocol uses PDUs exchanged between managers and agents via transports supported by stacks from FreeBSD, OpenBSD, Linux kernel, and embedded systems in products from Intel Corporation and ARM Holdings. Event notification mechanisms evolved with additions like INFORM and support for asynchronous alerts used by monitoring suites from Dynatrace and Datadog.

Management Information Base (MIB)

The Management Information Base is a hierarchical collection of managed objects identified by OIDs defined in standards contributions and enterprise MIBs published by vendors like Microsoft, Cisco Systems, Hewlett-Packard, and Oracle Corporation. MIB modules are authored using the Structure of Management Information language produced in collaboration with organizations such as the IETF and conform to syntaxes defined in RFCs used by projects including Net-SNMP Project and SNMP Research. Industry-specific MIBs exist for sectors served by Siemens, Schneider Electric, ABB Group, and Schlumberger.

Security and Authentication

Initial versions relied on community strings and minimal security, prompting enhancements like User-based Security Model and View-based Access Control Model adopted in collaboration with the IETF and implemented by vendors such as Cisco Systems, Juniper Networks, Hewlett-Packard Enterprise, and Microsoft. Later revisions introduced cryptographic authentication and privacy using algorithms standardized with input from organizations such as National Institute of Standards and Technology and implemented within TLS or DTLS stacks by projects including OpenSSL and GnuTLS. Operational deployments in enterprises and service providers including Verizon Communications, AT&T, Deutsche Telekom, and Verizon Business rely on best practices combining SNMPv3 with network access controls from Palo Alto Networks and Fortinet appliances.

Implementations and Usage

Open-source implementations such as Net-SNMP Project, OpenNMS Project, and LibreNMS coexist with commercial agents from SolarWinds, Hewlett-Packard Enterprise, Cisco Systems, and Juniper Networks. Large-scale deployments in data centers operated by Facebook, Amazon.com, Google LLC, and Microsoft Corporation integrate SNMP telemetry with analytics platforms such as Splunk, Elastic NV, and Grafana Labs. Telecommunications operators like Verizon Communications and NTT Communications use SNMP alongside streaming telemetry technologies from vendors including Cisco Systems and Arista Networks.

History and Standards Evolution

Work on the protocol began in the mid-1980s within research groups at Bell Labs and universities including University of California, Berkeley and was standardized through a series of RFCs produced by the IETF and reviewed by bodies like the Internet Architecture Board. Successive versions, adopted in collaboration with vendors including Sun Microsystems, IBM, Motorola, and Nokia, addressed scaling, security, and extensibility. The protocol’s evolution influenced and was influenced by efforts such as Simple Mail Transfer Protocol, Border Gateway Protocol, and Network Time Protocol and continues to be referenced in contemporary network management research at institutions such as Massachusetts Institute of Technology, Stanford University, and Carnegie Mellon University.

Category:Network protocols Category:Internet standards