Simple Network Management Protocol

Description

The Simple Network Management Protocol (SNMP) is an application-layer protocol, part of the Internet protocol suite as defined by the IETF. It facilitates the exchange of management information between network devices (agents) and network management stations (managers). The core of SNMP is a simple request/response mechanism. A manager sends requests (GET, GETNEXT, GETBULK) to an agent to retrieve the values of specific managed objects. It can also send a SET request to modify a value. The agent, which resides on the managed device (e.g., a router, switch, or 3GPP network element with IP connectivity), responds with the data or an error code. Additionally, agents can asynchronously send TRAP or INFORM messages to managers to notify them of significant events (like a link failure).

The structure of the managed information is defined by Management Information Bases (MIBs). A MIB is a hierarchical tree of managed objects, each identified by a unique Object Identifier (OID). These objects represent scalar values (e.g., system uptime, interface status) or tabular data (e.g., a routing table). 3GPP defines its own MIB modules (e.g., for managing Node B, eNB, or MME functions) that extend standard IETF MIBs. The protocol operates over UDP, typically on ports 161 (for GET/SET) and 162 (for traps), prioritizing simplicity and low overhead over guaranteed delivery.

In a 3GPP management system, SNMP is often used as a southbound interface between a managing system (like an SNM or EM) and the Network Elements, especially for fault and performance management. The manager polls the agent at regular intervals for performance counters (PM) and receives traps for alarm reporting. The protocol's simplicity and ubiquity in the IP world made it a natural choice for managing the IP-based components that became integral to 3G and 4G networks, as referenced across numerous 3GPP specifications including those for management architecture (32.101, 32.102) and integration reference points (IRP) like the Bulk CM IRP (32.622).

Purpose & Motivation

SNMP was created to solve the problem of managing the rapidly growing and heterogeneous devices on IP networks in the late 1980s and early 1990s. Prior to its adoption, management was often done through proprietary command-line interfaces (CLIs) or protocols, making centralized, multi-vendor network management impossible. The key motivation was to provide a simple, extensible, and standards-based method to monitor device health, configure settings, and receive event notifications.

3GPP adopted and references SNMP (as an IETF standard) to manage the IP-based infrastructure within its networks. As 3GPP systems evolved from circuit-switched cores to all-IP architectures (GPRS, IMS, EPS), the need for standardized IP network management became critical. SNMP solves the problem of interfacing with a wide array of commercial off-the-shelf (COTS) IP routers, switches, and servers that form the transport and core network. It provides a well-understood mechanism for the Operations Support System (OSS) to collect performance data and faults from these elements. While 3GPP also defines its own management solutions (like CORBA-based IRPs for core network elements), SNMP remains a vital tool, particularly for element and sub-network level management of infrastructure with strong IP heritage.

Key Features

• Simple request/response (GET, SET) and trap mechanism
• Uses a hierarchical Management Information Base (MIB) structure with OIDs
• Operates over UDP for low overhead
• Widely supported by virtually all IP network equipment
• Enables centralized monitoring and configuration of distributed devices
• Extensible through the definition of new MIB modules

Evolution Across Releases

Defining Specifications