2017Unpublished venueRequires access

Fault management and Management Information Base (MIB)

Oliver Jukić, I. Heđi, I. Špeh

Open publisher page 6 citations

Abstract

Fault management function mostly rely on SNMP protocol and SNMP agent capabilities, where SNMP agents are implemented over different network elements. Structure of management information is described in Management Information Base (MIB) for every single SNMP agent class. Hence, integrated management systems needs to implement different SNMP managers capable to communicate with number of different SNMP agents, obtaining management information from real telecommunication network. Those managers are often called access modules. In order to decrease delivery time for SNMP management solutions, number of generic fault management MIBs are designed (e.g. Alarm Management Information Base). Theoretically, if different SNMP agents rely on the same management information base, only one SNMP manager (access module) is enough to manage different network elements. It is very logical way of thinking, if we consider that in real life different network elements share the same management information structure. For instance, alarm message from many different network elements consists of start time, probable cause, additional information, affected network element, etc. However, state of the art is not so idyllic, from the integrator's point of view. Number of MIBs exist in real telecommunications network. In this paper we will make short research on MIBs implemented on different network elements, in order to detect real integrator position in network management solution's development. At the end, solution is proposed for SNMP agent software development.

About this research paper

What this paper is about

Fault management function mostly rely on SNMP protocol and SNMP agent capabilities, where SNMP agents are implemented over different network elements. Structure of management information is described in Management Information Base (MIB) for every single SNMP agent class. Hence, integrated management systems needs to implement different SNMP managers capable to communicate with number of different SNMP agents, obtaining management information from real telecommunication network. Those managers are often called access modules. In order to decrease delivery time for SNMP management solutions, number of generic fault management MIBs are designed (e.g. Alarm Management Information Base). Theoretically, if different SNMP agents rely on the same management information base, only one SNMP manager (access module) is enough to manage different network elements. It is very logical way of thinking, if we consider that in real life different network elements share the same management information structure. For instance, alarm message from many different network elements consists of start time, probable cause, additional information, affected network element, etc. However, state of the art is not so idyllic, from the integrator's point of view. Number of MIBs exist in real telecommunications network. In this paper we will make short research on MIBs implemented on different network elements, in order to detect real integrator position in network management solution's development. At the end, solution is proposed for SNMP agent software development.

Why it matters

OpenAlex reports 6 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Fault management function mostly rely on SNMP protocol and SNMP agent capabilities, where SNMP agents are implemented over different network elements. Structure of management information is described in Management Information Base (MIB) for every single SNMP agent class. Hence, integrated management systems needs to implement different SNMP managers capable to communicate with number of different SNMP agents, obtaining management information from real telecommunication network. Those managers are often called access modules. In order to decrease delivery time for SNMP management solutions, number of generic fault management MIBs are designed (e.g. Alarm Management Information Base). Theoretically, if different SNMP agents rely on the same management information base, only one SNMP manager (access module) is enough to manage different network elements. It is very logical way of thinking, if we consider that in real life different network elements share the same management information structure. For instance, alarm message from many different network elements consists of start time, probable cause, additional information, affected network element, etc. However, state of the art is not so idyllic, from the integrator's point of view. Number of MIBs exist in real telecommunications network. In this paper we will make short research on MIBs implemented on different network elements, in order to detect real integrator position in network management solution's development. At the end, solution is proposed for SNMP agent software development.

Key concepts: Simple Network Management Protocol, Network management, Network management station, Structure of Management Information, Network management application, Computer science, Network element, Element management system

Related papers

Back to paper searchBrowse research topicsOriginal source
Fault management and Management Information Base (MIB) — Research Paper | ScholarLens