SNMP

Sabareshwari

Introduction

Modern computer networks consist of hundreds or even thousands of interconnected devices such as routers, switches, servers, firewalls, wireless access points, printers, and IoT devices. These devices continuously exchange data to keep organizations connected. As networks grow larger, manually monitoring every device becomes almost impossible.

Imagine managing a university campus network with more than 500 computers, dozens of switches, multiple routers, wireless access points, and servers. If one router suddenly fails or a server's CPU usage reaches 100%, how would the network administrator know immediately?

This is where Simple Network Management Protocol (SNMP) becomes essential.

SNMP is one of the most widely used protocols for monitoring, managing, and troubleshooting network devices. It provides a standardized method for collecting information from network devices and, in some cases, remotely configuring them.

Whether you are managing a small office network or a global enterprise infrastructure, SNMP helps administrators monitor network performance, detect failures, receive alerts, and maintain network reliability.

What is SNMP?

Simple Network Management Protocol (SNMP) is an Application Layer protocol in the TCP/IP protocol suite that is used to monitor and manage network devices over an IP network.

It was developed by the Internet Engineering Task Force (IETF) and was initially defined in RFC 1157.

SNMP allows communication between a Network Management System (NMS) and network devices such as:

Routers
Switches
Servers
Firewalls
Wireless Access Points
Network Printers
Storage Devices
UPS Systems
IP Cameras
IoT Devices

Instead of checking every device manually, administrators can monitor the entire network from one centralized management system.

Simple Definition

SNMP is a protocol that allows network administrators to monitor, collect information from, and manage network devices remotely.

Real-World Analogy

Imagine a hospital.

The Hospital Administrator supervises everything.
Doctors and nurses continuously update patient information.
Emergency alarms immediately notify the administrator if a patient's condition becomes critical.

Similarly:

Hospital - SNMP
Administrator - SNMP Manager
Doctors/Nurses - SNMP Agents
Patients - Network Devices
Medical Records - MIB
Patient Information - Managed Objects
Emergency Alarm - Trap Message

The administrator does not visit every room every minute. Instead, they receive updates whenever necessary.

SNMP works exactly the same way.

Why Was SNMP Developed?

Before SNMP existed, network administration was extremely difficult.

Administrators had to:

Log in to every router individually.
Check every server manually.
Monitor network traffic using command-line tools.
Detect failures only after users complained.
Configure each device separately.

As organizations expanded, managing hundreds of devices manually became unrealistic.

Different manufacturers such as Cisco, Juniper, HP, IBM, Dell, and others also used different proprietary management methods. There was no common protocol that worked across all vendors.

To solve this problem, the IETF introduced SNMP as a vendor-independent network management protocol.

Today, almost every enterprise networking device supports SNMP.

Why Do We Need SNMP?

Managing a modern network without SNMP is similar to driving a car without a dashboard.

A driver depends on indicators such as:

Speedometer
Fuel gauge
Engine warning light
Temperature meter

Without these indicators, the driver would only notice a problem after the car stopped working.

Likewise, SNMP continuously monitors network devices and reports problems before they become serious.

Problems Without SNMP

Without SNMP, administrators would face several challenges:

No centralized monitoring
Manual device checking
Slow troubleshooting
Delayed fault detection
Poor network visibility
Increased downtime
Higher maintenance costs

Benefits of SNMP

SNMP provides several important advantages:
Centralized monitoring of all network devices
Automatic fault detection
Performance monitoring
Remote device management
Real-time alerts
Better network reliability
Faster troubleshooting
Vendor-independent communication

Example Scenario

Suppose a company has:

300 Computers
25 Switches
12 Routers
18 Servers
40 Wi-Fi Access Points

Without SNMP:

The administrator must log in to every device individually to check:

CPU usage
Memory utilization
Network traffic
Interface status
Temperature
Disk usage

This process could take several hours.

With SNMP:

The Network Management System automatically collects all this information every few minutes and displays it on a dashboard. If a device fails, an alert is generated immediately.

Features of SNMP

Some important features include:

Centralized management
Standard protocol
Lightweight communication
Remote monitoring
Fault detection
Performance analysis
Scalability
Vendor interoperability
Event notifications
Configuration support

SNMP Architecture

SNMP follows a Manager-Agent Architecture.

The manager communicates with every device through its SNMP agent.

Components of SNMP

SNMP mainly consists of three major components:

SNMP Manager
SNMP Agent
Managed Device

Let's understand each component in detail.

1. SNMP Manager

The SNMP Manager, also called the Network Management System (NMS), is the central controller responsible for monitoring and managing all network devices.

The manager:

Sends requests to devices.
Collects device information.
Displays reports and dashboards.
Stores monitoring data.
Generates alerts.
Detects failures.
Configures devices (when permitted).

Think of the manager as the "brain" of the monitoring system.

Responsibilities of an SNMP Manager

The manager performs several important tasks:

Collects network statistics
Detects device failures
Generates alerts
Stores historical performance data
Monitors bandwidth usage
Checks interface status
Collects CPU and memory utilization
Configures device parameters
Produces performance reports

Examples of SNMP Managers

Common network management software includes:

SolarWinds Network Performance Monitor
Manage Engine Op Manager
PRTG Network Monitor
Zabbix
Nagios
Libre NMS

These tools use SNMP to communicate with network devices.

2. SNMP Agent

An SNMP Agent is software running on each managed device.

It acts as the communication bridge between the device and the SNMP Manager.

The agent continuously collects information about the device and stores it in a structured database called the Management Information Base (MIB).

Whenever the manager requests information, the agent retrieves the requested data from the MIB and sends it back.

Responsibilities of an SNMP Agent

The agent performs several important functions:

Collects device information
Monitors hardware resources
Maintains the MIB database
Responds to manager requests
Sends alerts (Trap messages)
Updates performance statistics

Example

Suppose the manager asks:

"What is the CPU utilization of Router A?"

The agent checks its MIB.

If the CPU utilization is 35%, the agent sends:

CPU Utilization = 35%

back to the manager.

3. Managed Device

A managed device is any network-enabled device running an SNMP agent.

Examples include:

Router
Switch
Firewall
Server
Printer
Wireless Controller
UPS
NAS Storage
IP Camera
Access Point

Every managed device stores operational information that can be monitored using SNMP.

Information Stored by Managed Devices

A managed device can provide information such as:

Hostname
IP Address
CPU Usage
Memory Usage
Disk Space
Temperature
Network Interfaces
Uptime
Routing Information
Error Statistics
Traffic Counters

How SNMP Works

The working of SNMP can be understood in a simple sequence:

Step 1

The network administrator opens the Network Management System.

Step 2

The manager sends a request to a device.

Step 3

The SNMP agent receives the request.

Step 4

The agent checks the requested information in its MIB.

Step 5

The requested data is returned to the manager.

Step 6

The manager displays the information on its monitoring dashboard.

Workflow Diagram

Communication Between Manager and Agent

The communication process is straightforward:

The manager requests information.
The agent reads the required value.
The agent sends the response.
If an abnormal event occurs, the agent immediately sends a notification without waiting for a request.

This approach enables both proactive monitoring and rapid fault detection.

Real-World Example

Consider a company with 50 branch offices connected through routers.

Every router runs an SNMP agent.

The central IT team uses an SNMP Manager to monitor all routers.

At 2:00 PM, one branch router's CPU usage reaches 95%.

The SNMP agent detects the condition and reports it.

The manager displays an alert:

Warning!

Router BR-05

CPU Usage: 95%

Severity: High

The administrator can investigate the issue before users experience significant network problems.

Advantages of Using the Manager-Agent Model

The Manager-Agent architecture offers several benefits:

Centralized monitoring
Easy scalability
Reduced manual effort
Vendor interoperability
Faster troubleshooting
Improved network visibility
Automatic event reporting
Efficient performance monitoring

Key Terms You Should Remember

SNMP (Protocol used for monitoring and managing network devices)
Manager (Central system that monitors and controls devices)
Agent (Software running on each managed device)
Managed Device (Router, switch, server, printer, firewall, or other network device)
NMS (Network Management System that acts as the SNMP Manager)
MIB (Database containing information about managed objects)
OID (Unique identifier for every managed object)