A device, system and method for realizing MIB adaptation

Abstract

This invention discloses one MIB adaptive device, system and method, wherein, the device comprises the following parts: business layer to receive user operation information; manager to receive device agent non-require information; adaptive layer to respond business layer or manager requires; MIB match database to store MIB and integral data structure relationship leg files; network device and its agent on base of above device. The method comprises the steps of requiring process network message needed MIB point information; responding requires to extract needed point information and sending to manager or business layer.

Description

technical field [0001] The present invention relates to the technical field of communication, and in particular to a device, system and method for realizing MIB adaptation. Background technique [0002] The Simple Network Management Protocol (SNMP, Simple Network Management Protocol) is a set of network management protocols defined by the Internet Engineering Task Force (IETF: Internet Engineering Task Force). This protocol is based on the Simple Gateway Monitor Protocol (SGMP: Simple Gateway Monitor Protocol). Using SNMP, a management workstation can remotely manage all network devices that support this protocol, including monitoring network status, modifying network device configuration, and receiving network event warnings. Although SNMP was originally oriented to IP-based network management, it has also been successfully used as an industry standard for telephone network management. attached figure 1 Describes the typical application environment of SNMP. Through SNMP ...

AI Technical Summary

Problems solved by technology

[0010] 2. For the same standard MIB, different manufacturers have different implementation details. In addition to understanding some nodes differently, some extension nodes may be added according to service characteristics—for example, device X and device 2 have the same service. The defined OID and MIB information are both different (see MIBX and MIB2);

[0011] 3. MIBs of the same manufacturer may have different implementations in different versions—for example, equipment 1 and equipment 2 have the same OID even if they have the same service, but the specific information supported by the MIB table is different (see figure 1 MIB1 and MIB2), device 2 provides more specific information than device 1;

[0013] 5. Between different types of devices of the same manufacturer, there may even be differences as between device X and device 3 (the OID and MIB information corresponding to the same business logic is different; the supported business scope is also different)

For these network management systems based on private protocols, they can only manage their own equipment and cannot manage equipment from other manufacturers.

Moreover, devices using proprietary protocols are not compatible with common SNMP network management products, making it difficult to access upper-layer network management

In this way, there are multiple network management systems in one network, which cannot be integrated

[0015] At the same time, there are still some network management systems in the prior art that can manage all standard MIB-based devices, but they are only limited to standard MIB-compatible devices. Once these devices are extended on the basis of standard MIB, more For rich technical features, this kind of network management system cannot effectively manage them, and users cannot experience these new technical features.

In addition, for devices using private protocols, this kind of network management system is even more unmanageable

Images