Browse Prior Art Database

Topology Database of Managed Objects

IP.com Disclosure Number: IPCOM000113175D
Original Publication Date: 1994-Jul-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 113K

Publishing Venue

IBM

Related People

Holt, VS: AUTHOR [+5]

Abstract

In Network Management based on applications interacting with objects and/or agents for the purpose of performing management functions, it is beneficial to these applications to have a common repository or database from which they may obtain information such as the location (network address), classes and names of instances of the objects and certain attributes of those objects. However, creating such a database is a complex problem, caused by the diversity and indeterminate nature of the objects discovered. The objects consist of several different semantics and data types, use different management protocols. Also, there may exist management functions that do not use objects at all.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 49% of the total text.

Topology Database of Managed Objects

      In Network Management based on applications interacting with
objects and/or agents for the purpose of performing management
functions, it is beneficial to these applications to have a common
repository or database from which they may obtain information such as
the location (network address), classes and names of instances of the
objects and certain attributes of those objects.  However, creating
such a database is a complex problem, caused by the diversity and
indeterminate nature of the objects discovered.  The objects consist
of several different semantics and data types, use different
management protocols.  Also, there may exist management functions
that do not use objects at all.  This database should provide a
single common access method independent of the information to be
stored or retrieved, preferably one that is consistent with the
programming interface used by the applications when performing their
management functions on the objects or agents.  In addition,
applications need to be informed when information is added, changed
or deleted from the database.

      This solution takes advantage of the industry standards for
network management by using the Common Management Information
Services (CMIS) standards for implementing the database, and the
X/Open Management Protocols* (XMP) API standards for implementing the
access method.  This is because these standards provide a solution
that may also be used by management applications for performing their
management functions.  Therefore, the applications may use the same
interface for interactions with their managed objects and agents as
well as the database.  The database is implemented as an agent
representing the CMIS object defined for the database.  The access
methods are implemented as CMIS actions.  One action is defined for
input to the database and another for querying the database.
Parameters on the actions are used to identify the specific
information item to be added or retrieved from the database.

      Each object is stored in the database using the semantics of
the CMIS Get Result object.  This construct provides an effective
means of storing the objects CMIS class, instance identifier
(distinguished name) and any attributes of the object.  It also has
the additional value, of allowing the database to return a query
result in a form that is identical to the form of the result returned
by a CMIS Get operation.  In other words, an application sees the
query result for an object stored in the database in the same format
as that which is received if the application had sent a CMIS Get
directly to the object for the same information.

      Objects are arranged in the database in a set of hierarchical
trees, each of which contains the objects for a distinct physical
system that exists in the managed network.  The root of each tree is
an object representing a physical machine in the network.  Objects
disc...