Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1998-05-08
2001-11-13
Burgess, Glenton B. (Department: 2153)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000, C707S793000
Reexamination Certificate
active
06317748
ABSTRACT:
FIELD OF THE INVENTION
The invention relates generally to the management of device and other information on computer systems or networks, and more particularly to an improved system and method for providing management information.
BACKGROUND OF THE INVENTION
Network administrators are presently using a collection of technologies referred to as web-based enterprise management (WBEM) to manage network and other information of an enterprise. For example, network administrators run WEBM-compatible management applications to perform such tasks as detect machines on a network, inventory software and hardware configurations, and send key information back to a central database. The results of the communication may appear on a user interface so as to allow administrators to view the data of the network device. Such management applications and components receive this information from a variety of disparate sources, some of which are network devices. By way of example, a management application or component may wish to communicate with remote disk drive software (i.e., an agent) to determine how much free space remains on a network drive, or communicate with a router agent determine some property of a router.
In general, network device agents provide such management information via a standard known as the Simple Network Management Protocol (SNMP). In accordance with SNMP, the management component uses Management Information Bases (MIBs) to describe the structure of the data available at the network device. MIBs are published structures of static information that relate to the dynamic information provided by a network device. For example, a particular MIB might describe information such as an association between a device's data entity and a name (object identifier), a definition of the data type for that entity, a textual description of the entity, how the entity is indexed, if the entity is a member of a complex data type and the access allowed for that entity. The management component then is able to describe the data made available on the SNMP device (e.g., in response to a query or event) by using an appropriate MIB module to model that data.
A recent improvement in management information technology provides a centralized object manager and schema that provide uniform rendering of management information to client management applications. The object manager and schema are described in U.S. patent application Ser. No. 09/020,146, entitled “Object Manager for Common Information Model,” assigned to the assignee of the present invention and hereby incorporated by reference in its entirety. In general, the Common Information Model (CIM) is an object-oriented technology, wherein the components of CIM, such as classes, instances, and qualifiers may be conveniently described in a user-intuitive textual format known as Managed Object Format (MOF), (described below). A CIM object Manager (described below) preferably operates on information on CIM objects described via MOF.
In contrast, MIB modules are not user-intuitive, but rather consist of complex, tree-based structures using object identifiers (OIDs) to describe locations in the tree. An OID is a unique identifier assigned to a specific object, consisting of a variable length sequence of numbers that identify the source of the object as well as the object itself. MIB OIDs are thus unique values organized into a tree structure, wherein the sequence of numbers identifies the various branches of the subtree that a given MIB object comes from. For example, SNMP objects are members of the subtree identified by “iso.org.dod.internet,” which has a defined OID of 1.3.6.1. In this notation, subsequent numbers further define the exact location of a MIB object under that subtree. In short, a primary problem is that SNMP devices utilize these complex MIB modules, while the CIM object manager (which significantly improves enterprise management) use CIM objects.
Moreover, different network devices support different MIB modules, some of which are standardized based on the particular type of device (e.g., IP MIBs, IPX MIBs for routers) while others are proprietary MIBs published by a device manufacturer or the like to provide some value-added device data to their device. A large number of MIB modules, on the order of thousands, have been published, and a similarly large number thereof may be maintained in a repository of a given CIM installation. However, given an arbitrary device, the various MIB modules (or part thereof) supported by that device are not necessarily known. To be manageable via a CIM object manager (CIMOM), however, the subset of supported MIBs needs to be known. Because of time and network bandwidth considerations, there is no straightforward way to query the devices to determine the subset of the total set of MIBS supported thereby. For example, although SNMP devices respond to a Get (OID) operation to answer whether a particular object (specified by its OID) is supported, it is impractical to individually query the device in real time with each of the (relatively large number of) OIDs to see which of the set are supported. As a result, given an arbitrary device, another problem with some SNMP (e.g., version 1) MIBs is that there has heretofore been no efficient way in which to determine the subset of MIB modules (or portion thereof) that the given device supports.
SUMMARY OF THE INVENTION
Briefly, the present invention provides a method and system for mapping SNMP Management Information Base (MIB) objects to object classes, particularly MOF-described object classes. To this end, the objects in a MIB are enumerated by a compiler process, and a determination is made for each enumerated object as to whether the MIB object corresponds to a scalar collection (one unique instance) or a table collection (multiple possible instances). If, the MIB object corresponds to a scalar collection, the MIB object is mapped to a singleton MOF class, such as by accessing a mapping table to translate the MIB object information to MOF class information. If the MIB object corresponds to a table collection, the MIB object information is mapped to a class capable of describing a plurality of instances, such as a keyed MOF object.
A correlator is further provided to efficiently determine which object classes are supported by a given network device. To this end, the correlator first traverses the MIB trees of groups maintained at a CIM installation and creates a range table of groups and corresponding ranges of object IDs therefrom. Then, successively using range starting OIDs from the range table, the device is requested to return its next highest Object ID beyond an object ID provided thereto that is based on a range value. If the returned object ID falls into a range, the group of object classes corresponding to that range in the range table is known to be supported by the device, whereby that group's subsequent entries in the range table need not be tested and are eliminated from the range table. Also, any prior ranges below the returned OID are known to be not supported, and those ranges are eliminated from the range table. The process is successively repeated using remaining ranges to provide OIDs until the range table has no entries remaining.
Other advantages will become apparent from the following detailed description when taken in conjunction with the drawings, in which:
REFERENCES:
patent: 5291583 (1994-03-01), Bapat
patent: 5509123 (1996-04-01), Dobbins et al.
patent: 5659736 (1997-08-01), Hasegawa et al.
patent: 5696697 (1997-12-01), Blau et al.
patent: 5729739 (1998-03-01), Cantin et al.
patent: 5794248 (1998-08-01), Blackman et al.
patent: 5797137 (1998-08-01), Golshani et al.
patent: 5870749 (1999-02-01), Adusumilli
patent: 5893107 (1999-04-01), Chan et al.
patent: 5951649 (1999-09-01), Dobbins et al.
patent: 5956730 (1999-09-01), Burroughs et al.
patent: 5983233 (1999-11-01), Potonniee
patent: 6003035 (1999-12-01), Breame
patent: 6081808 (2000-06-01), Blackman et al.
Thompson, J. Patrick. Web-Based Enterprise Management Architecture, I
Ahmed Syed N.
Byrisetty Rajeev
Menzies Steven J.
Osborne Kenneth M.
Burgess Glenton B.
Michalik & Wylie PLLC
Microsoft Corporation
Trim Nkosi N
LandOfFree
Management information to object mapping and correlator does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Management information to object mapping and correlator, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Management information to object mapping and correlator will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2570142