Skip to main content

SNMP MIB

To operate a device with SNMP, a set of managed information supported by the device, which is usually called a managed object (MO), requires a definition. In SNMP, it is defined as a Management Information Base (MIB). If the device supports SNMP, specify which MIBs are supported in the Feature, and the Manager can collect information based on the MIBs. In this post, I will briefly look at MIB.

MIB Overview

MIB is a text file written in ASN.1 syntex. Since it is a standard syntex, it can interpret either standard MIB or private MIB.

Taking RFC 1213 (MIB-2) as an example, objects are defined as shown below.

sysUpTime OBJECT-TYPE
              SYNTAX  TimeTicks
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The time (in hundredths of a second) since the
                      network management portion of the system was last
                      re-initialized."
              ::= { system 3 }

sysContact OBJECT-TYPE
              SYNTAX  DisplayString (SIZE (0..255))
              ACCESS  read-write
              STATUS  mandatory
              DESCRIPTION
                      "The textual identification of the contact person
                      for this managed node, together with information
                      on how to contact this person."
              ::= { system 4 }

SNMP OID

Manager and Agent communicate through SNMP, and when performing GET/SET operation, it is necessary to specify which object to GET/SET to each other. OID value is required for this.

OIDs have a hierarchical structure and have a unique value for all devices worldwide. In the example above, the object called 'sysUpTime' has an OID of 1.3.6.1.2.1.1.3 and is delivered to the SNMP PDU.

You can find out the OID values through RFC 1213,

mib-2 OBJECT IDENTIFIER ::= {mgmt 1}
mgmt is predefined with a value of 1.3.6.1.2. in RFC 1213, and mib-2 has the value of 1 under mgmt.

In other words, mib-2's OID is 1.3.6.1.2.1.

system OBJECT IDENTIFIER ::= {mib-2 1}
system is defined as a value of 1 under mib-2. That is, the OID becomes 1.3.6.1.2.1.1.

sysUpTime ::= {system 3}
sysUpTime is defined as a value of 3 under system. The OID value becomes 1.3.6.1.2.1.1.3.


MIB OID can be defined in two types as follows, depending on its nature.
Scalar: Single value (instance)
Table: Multiple values (instance), index is required. 

For Scalar, you can read that value by adding .0 to the OID.
In the case of a table, there are multiple values, so an index of the value is required.
 (For example, if there are multiple LAN ports, specify which port information to read)

 

Syntex

You can refer to rfc4181 for the guide to create the MIB, but if you refer to the already created standard MIB, you can write it without difficulty. Usually, when opening a MIB file with an editor or using a tool like brower, the following two values ​​are mainly seen.

 

SYNTEX: You can think of it as Data Type.
ACCESS: read-only, read-write, read-create, if you can read and write or not.








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...