LUALoriotPro WEB site

LoriotPro scripting documentation
Extensions for LUA language

Table of contents Search function

Print the current page Mail this  link UTUBE Channel version française

Step 1 - Reading documentation

The first phase requires experimented skills in SNMP and MIB technology. The administrator should know where to find the management objects (MIB objects) necessary for the monitoring. We have chosen in our example, objects available in the Host Resources MIB. Today there are millions of objects defined either in public MIB files or private MIB files and the trick is to know how to find them. The HOST RESOURCE MIB that we will use in our example contains HOST related management object and a table of SNMP variables, Hrstorageentry, that provides information on storage devices like hard drive, CDROM and memory. 

The Hrstorageentry table entry in the MIB tree of LoriotPro

Description of the Hrstorageentry SNMP table objects

Objet SNMP



OID LEN (10) :

"A (conceptual) entry for one logical storage area on the host.  As an example, an instance of the hrStorageType object might be named hrStorageType.3"


OID LEN (11) :

"A unique value for each logical storage area

contained by the host."


OID LEN (11) :

"The type of storage represented by this entry."


OID LEN (11) :

"A description of the type and instance of the storage described by this entry."


OID LEN (11) :

"The size, in bytes, of the data objects allocated from this pool.  If this entry is monitoring sectors, blocks, buffers, or packets, for example, this number will commonly be greater than one.  Otherwise this number will typically be one."


OID LEN (11) :

"The size of the storage represented by this entry, in units of hrStorageAllocationUnits. This object is writable to allow remote configuration of the size of the storage area in those cases where such an operation makes sense and is possible on the underlying system. For example, the amount of main memory allocated to a buffer pool might be modified or the amount of disk space allocated to virtual memory might be modified."


OID LEN (11) :

"The amount of the storage represented by this entry that is allocated, in units of



OID LEN (11) :

"The number of requests for storage represented by this entry that could not be honored due to not enough storage.  It should be noted that as this object has a SYNTAX of Counter32, that it does not have a defined

initial value.  However, it is recommended that this object be initialized to zero, even though management stations must not depend on such an initialization."

It is also possible to use the Report Center and to create a MIB report that will help you to understand the role of each object of this MIB file

From this information we know how to calculate the disk utilization. We have to collect the number of clusters used by the disk (hrstorageused snmp object) and divide this value by the number of total clusters on the disk (hrstoragesize snmp object) and times the result by 100 to get the percentage.

Let's go to the next step