Conclusion of Need:
Modern networks cannot function reliably without SNMP. It is the backbone of network visibility and monitoring.
SNMP MANAGEMENT FRAMEWORK — FULL REMAINING PART (VERY DETAILED)
4. Components of SNMP (FULL DEEP EXPLANATION)
4.1 SNMP Manager (Network Management Station – NMS)
SNMP Manager is the central controlling system responsible for monitoring, collecting, analyzing, and
managing data from all network devices. It sends requests to the Agent, processes the responses, and
generates visual dashboards, logs, graphs, and alerts. It stores historical data for long-term analysis and
compares device performance trends.
The Manager maintains polling intervals, meaning it checks each device regularly (e.g., every 30 seconds). It
also maintains device lists, authentication settings, alert thresholds, and job schedules.
Real-world examples include SolarWinds, PRTG, Nagios, ManageEngine OpManager.
4.2 SNMP Agent (Software Module in Device)
The SNMP Agent is a lightweight service running inside each network device. It continuously collects internal
status such as CPU load, temperature, RAM usage, interface speed, packets sent/received, errors, and uptime.
It stores this information in the MIB and shares it with the Manager on request.
The Agent works passively (responding to GET) and actively (sending TRAP). Agents track system health in real
time and ensure monitoring accuracy. All device parameters accessible via SNMP must be registered inside the
MIB; otherwise the Manager cannot read them.
4.3 MIB (Management Information Base – FULL DETAIL)
MIB is a hierarchical database of all manageable objects in the device. It organizes data in a tree-like structure,
where each branch represents a category and each leaf represents a specific value.
Common MIB groups include:
System Group: name, uptime, contact, location
Interface Group: speed, errors, packets, status
IP Group: routing details, IP statistics
TCP/UDP Group: port details, connections
SNMP Group: agent settings, counters
MIB ensures that di erent vendors’ devices follow the same structure, so SNMP Managers can read data
uniformly.
4.4 OID (Object Identifier – FULL DETAIL)
Each MIB object has a unique OID—a numeric path identifying the object precisely.
Example structure:
[Link].[Link].1.10
This could represent incoming tra ic on interface #1.
OID properties:
Globally unique
Hierarchical
Standardized by ISO
Identifies exact data items
Without OIDs, SNMP Manager would not know what information to request.
5. SNMP Communication Cycle (VERY IMPORTANT)
1. Manager sends GET/GET-NEXT/GET-BULK request to Agent.
2. Agent receives request, fetches relevant OIDs from the MIB.
3. Agent prepares response and sends it back to Manager.
4. Manager analyzes returned data and updates dashboards.