Skip to main content

SNMP Overview

Simple Network Management Protocol (SNMP) is a Management Protocol most used in network management systems. More than 70% of the world's network equipment supports SNMP, and as it has a long history, it is easy to develop and verify with various tools and libraries that have already been verified.

 

On the other hand, the simple structure of GET, SET, and NOTIFICATION is not easy to standardize, and it is difficult to implement various OAM functions. There are many standard MIBs defined by IETF(RFC xxxx), and large equipment manufacturers basically support them, but most of the MIBs required for operation are supported as private MIBs, and the main functions are often vendor specific.

 

As a result, Service Providers requested a standardized operation plan, which became the background for NETCONF and others. Nevertheless, since SNMP is still the most widely used protocol, so it is essential to understand the management system.


The history of SNMP

As the Internet based on TCP/IP appeared in the 1980s, standardization of management funtion was required, and SNMP was introduced by IETF. They defined a simple operation such as Get, Set, and Trap, but in reality, it was a protocol that required a fairly complex implementation, and there were many restrictions on operation. Anyway, the concept of SNMP first appeared in RFC1067 in 1988. 

# RFC1067 (A Simple Network Management Protocol)

  

SNMP Version 1 is fully defined in RFC 1157 (1988). It is a standard in which all basic concepts of SNMP are defined.

Since then, SNMP Version 2 has the current framework as RFC 1441 and others appeared in the 1990s.

SNMP Version 3 appears in the 2000s as the demand for security increases. About ten years ago, there was no problem when only supporting SNMPv2c, but recently SNMPv3 is mandatory.


SNMP Operation

SNMP consists of communication between Manager and Agent. Manager performs the function that goes up to management system such as NMS or EMS. It is the subject of Get, Set and recipient of Notification (Trap). Agent is implemented in Network Device and performs the function to respond to the Manager's Get and Set Operation. When an event occurs, related information is delivered to the manager through a trap.

 

  • Get: Manager retrieves the value of Agent.
  • Set: Manager sets a value to the Agent.
  • Trap (Notification): Agent delivers information to Manager in asynchronous manner.
  • MIB (Management Information Base): Defines information to be sent and received through SNMP


SNMP Packet

SNMP sends and receives data through UDP. Due to the nature of UDP, the reliability of transmission is not guaranteed, but there is a simple aspect because it does not manage sessions.

 

161 and 162 are used as default ports. 161 is used for Get/Set and 162 is used for trap transmission.


SNMP Packet

IP headerUDP headerversioncommunityPDU-Typerequest-idError-statuserror-indexvariable bindings



Comments

Popular posts from this blog

What is NMS and EMS

First of all, NMS is an abbreviation for Network Management System, and EMS is an abbreviation for Element Management System. TMN, a very old standard document, describes the two as concepts such as NM, EM, and NE. We will look at the relevant standard documents when there is an opportunity in the future, and first, let's look at a schematic concept. In order to efficiently operate and manage network equipment, NMS and EMS suitable for the service area are required. In general, in the case of wired networks, NMS is often operated alone, and in the case of mobile communication networks, EMS is required in addition to NMS. In this article, we will examine the concept of the overall management system and explain the differences between NMS and EMS. Management System refers to a GUI system that performs network management functions, usually represented by FCAPS. Here, FCAPS means the following five functions. l   Fault Management  l   Configuration Management l   Accou...

FCAPS: Major Functions of Management System(NMS, EMS)

  When defining the functions of NMS and EMS, it is often referred to as FCAPS. FCAPS stands for Fault, Configuration, Account, Performance, and Security. The functions of a normal management system are all included in this category. Let's take a look at each function.   Fault Management Fault means unavailable status. When talking about a fault, it is usually referred to as an alarm. Fault and alarm are not specifically distinguished, but to be strict, fault can be considered to mean a phenomenon in which a fault occurred in the system, and faults are classified into hardware and software. Alarm defines in detail about a fault that has occurred and informs the operator when a fault occurs.   According to the definition of the standard document, Alarm usually has Severity, Probable Cause, Category, and additionally includes location information. A brief look at each definition is as follows.   Severity: Severity is defined as Critical Major, Minor, Warn...

Install VirtualBox Ubuntu 20.04

Let's install Ubuntu on VirtualBox. The installed version is based on 20.04, it is the latest LTS version at the time of writing. If you want to download another version, you can go to releases.ubuntu.com and download the version you want. 1. Ubuntu Download  Go to the site below and download Ubuntu 20.04 Version. ubuntu.com/download/desktop   2. Installation 2.2 Input Name, and click Next(N). 2.3 For the memory size, set the recommended memory size of 1024 MB. 2.4 Set up the hard disk. Use the recommended 10.00 GB.     2.5 Select the hard disk file type as VDI. 2.6 Storing on a physical hard drive selects dynamic allocation. 2.7 Confirm file location and size. 2.8 Once you've done that, you'll see your virtual machine as shown below. 2.9  From now on, it is the process of installing Ubuntu on the virtual machine. Run setup and select storage as shown below   2.10 Controller: Select IDE's Empty and choose the optical drive. Just select the Ubuntu file you d...