Browse Prior Art Database

Method and aparatus for Spatial and Temporal difference tracking of Point In Time snapshots of CIM compliant management information repository Disclosure Number: IPCOM000202341D
Publication Date: 2010-Dec-14
Document File: 8 page(s) / 379K

Publishing Venue

The Prior Art Database


Common Information Model(CIM) is a hierarchical, object oriented and extensible standard model introduced by DMTF(Distributed Management Task Force), that forms the basic building block of heterogeneous interoperable management infrastructure. CIM compliant devices report their management information through a software module called CIM agent. Point in Time (PiT) snapshots can be taken for any given CIM agent information repository to track the state of managed devices at any given point in time. Currently there are no tools available to track the syntactic and semantic changes for the CIM agent information repository PIT snapshots in spatial and(or) temporal fashion. Our proposed tool performs the following tasks:

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 21% of the total text.

Page 01 of 8

Method and aparatus for Spatial and Temporal difference tracking of Point In Time snapshots of CIM compliant management information repository

Temporal Comparison:

Temporal comparator is meant to compare two states of the same device at different point in times (PIT). As stated above, temporal comparison is mainly for projecting the device state evolution over a period of time. Thus, temporal comparison can be used to give user an insight of changes occurred at the device between two PIT images (t0 and t1) at time T0 and T1. It requires user to capture and store at least one state image in DB, and other could also be captured and stored or could be live device state.

Capturing and storing a state of a CIM device :

Capturing and storing a state of a device is performed in the hierarchical manner. Here hierarchy refers to the Containment Model. For example, it will start from CIMOM data, then registered device under CIMOM (CIMOM contains Device data), then CIM classes (Device has CIM classes), then CIM instances (CIM class has instances), and finally key and non-key properties for each instance (instance has properties). Storing of the data would be done exactly in the reverse order. While storing, checksum will be computed for each node. Checksum computation will move on as you go from leaf-node towards root-node. Checksum of instance is computed from checksum of key and non-key checksums. Checksum of class is computed out of checksum of instances in that class. Checksum of device is computed out of class checksum. Checksum of CIMOM is computed out of device checksums. In my layer based diagram - upper layer checksum will be computed out from lower layer.


Page 02 of 8

(This page contains 00 pictures or other non-text object)

Syntactic Comparison:

Syntactic comparison primarily targets comparing the management data in the form of CIM class instances captured/from live device CIMOM in the syntactic manner i.e. comparing the various instances in their raw format. Typically the resultant output of the syntactic comparison would project:
1) Number of instances created.
2) Number of instances deleted
3) Number of instances modified, along with the precise property values which got changed Syntactic comparison primarily does the data comparison. Proposed invention claims to devise an optimum solution for device state CIM data comparison. As illustrated above, the CIM data storage pattern can be viewed as a Tree format, starting from the root node which represents CIMOM data to leaf node representing Key, non-key properties data. Now, comparing two states of a device becomes a problem of finding if the two trees (respectively representing the reference and target state) are isomorphic or not. Moreover, checksum accompanied with each node would optimize the comparison time. Checksums are calculated similar to a hash tree approach. Calculation of the CIM repository in hash tree is done across different dimensions such as
i) CIM Agent -> Class...