JP2770758B2 - OSI management agent system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an OSI management system, and more particularly to an OSI management agent system for managing instance data of a managed object.

[0002]

2. Description of the Related Art OSI (Open Systems Interconnectio)
n) Management agents are IS / I / E, JTC / S / C, I / C
SO / DP10165 (ISO / IEC JTC / SC21
Based on the management information structure defined in (ISO / DP10165), the management of objects to be managed (hereinafter referred to as MO) is performed directly.
It requests the management agent for management functions. An MO is an abstract representation of various network resources that are actually managed, such as, for example, an exchange, a computer, and software, and a class viewed from a difference in MO management information is called a class. Each managed object that is actually managed is called an instance.

FIG. 5 is a diagram showing an example of a containment tree representing the containment relationship of a plurality of MOs managed by the management agent.
1, A2, B1 to B3, C1 to C4, D1, E1, F1
F5 is an instance. As described above, the instances are configured in a hierarchical tree structure, and are identified from the MO class identifier in which the definition of the MO is described and the parent-child relationship of the containing tree. To identify another instance contained in the same parent instance from one instance, follow the parent instance once and search for a child instance from the parent instance. For example, when referring to the instance C2 from the instance B1, the instance A1 is accessed once, and further the child instance C2 is accessed. Therefore, each instance has information indicating the parent-child relationship, that is, a pointer (position information) to the parent instance or the child instance. The above inclusion relation is described in MIB
Is defined in

FIG. 6 is a block diagram of a conventional OSI management agent system. 21 is a management agent, 2
2 is an MO data management unit, and 23 is a database (Management Information Base, hereinafter referred to as MIB) storing MO attribute data in the OSI management agent system.
), 24a, 24b are external devices that are one of a plurality of instances in the system, 25a,
A data storage unit 25b stores attribute data of the external devices 24a and 24b. The OSI management agent system accesses the MIB 23 when acquiring or setting attribute data for a certain instance.

In this system, the attribute data (hereinafter referred to as remote attribute data) of the external devices 24a and 24b existing outside the management agent 21 are also stored in the MIB2.
3 and stored in the MIB 23. Thus, the attribute data of all MOs are stored in the MIB 23.
23. Therefore, the external device 24a,
When the remote attribute data of 24b changes independently,
It is necessary to request the MIB 23 for an update operation via the MO data management unit 22.

[0006]

As described above, the conventional O
In the SI management agent system, when remote attribute data exists outside the management agent, it is necessary to update data in the MIB corresponding to the data. When a large number of remote attribute data exist, the memory capacity of the MIB increases. However, there is a problem that the time required for updating the data increases. Further, when the attribute data is data whose value changes in real time such as performance data (for example, data indicating an error rate), the communication volume between the remote side and the MIB increases, and the processing capacity of the system increases. However, there is a problem that the temperature is reduced.

Also, in order to refer to another instance contained in the same parent instance from one instance on the containing tree, the parent instance must be accessed and the corresponding instance must be accessed from the parent instance. However, there is a problem that it takes a lot of time to search for another instance from one instance. In addition, since each instance has information indicating a parent-child relationship, a plurality of instances included in the same parent have pointers to the parent instance, and a single parent instance includes many child instances. In such a case, there is a problem that the memory capacity of the MIB increases .

The present invention has been made to solve the above problems.
Communication between the management agent and the outside world
To increase the processing capacity of the OSI management agent system.
The primary purpose is to reduce Also, check for instances
The time required for searching is reduced, and the OSI management agent system is
A second object is to increase the processing capacity of the stem.

[0009]

SUMMARY OF THE INVENTION The present invention provides an OSI management system.
An OSI protocol processing unit for connection with the manager,
The instance tree data indicating the containment relationship of instances
An instance tree data storage unit to store
Message from the management manager obtained by the
Management object to identify the instances in the message
Based on the judging identifier, the instance tree
Attribute data of the instance to be operated
Data access control unit to obtain location information of data
Row that stores attribute data that exists inside the agent
Local attribute data storage and exists outside the management agent
Attribute data to access the attribute data
Data access control unit, location information and message
Based on attribute data identifier to identify attribute data
To store the attribute data of the instance to be operated
Location and this data exists inside the agent
Access the attribute data in the local attribute data storage.
Access to the remote attribute data
Attribute that requests access control unit to access attribute data
The instance tree data has a data management unit, and the instance tree data is shared by an instance of the same class included in the same parent instance as a class definition entry storing class definition information defining attributes and behavior of the class. An instance list common part that stores information, and an array block that stores information of each instance belonging to the instance list common part are configured, and the class definition entry includes a class identifier for identifying a class,
It stores class definition information and a pointer to the instance list common part. The instance list common part stores a pointer to the class definition entry to which it belongs, a pointer to an array block, and common information. The array block stores, for each element corresponding to each instance, a management object identifier, position information of attribute data of this instance, and a pointer to an array block of a child instance having this instance as a parent. At the same time, a pointer to the common part of the instance list to which it belongs is stored in the first element.

The common information includes a pointer to an instance list common part of an instance of the same class included in another parent instance and a pointer to an instance list common part of an instance of another class included in the same parent instance. It consists of a pointer and a pointer to the array block of the parent instance.

[0011]

According to the present invention, the attribute data management unit manages the attribute data of the instance to be operated within the management agent based on the position information and the attribute data identifier output from the MO data access control unit. Judge whether the data is data or data held outside the management agent, and sort the access destination.

[0012] Further, a class definition entry storing class definition information, an instance list common part storing common information shared by instances of the same class included in the same parent instance, and
By constructing an array block that stores information on each instance belonging to the instance list common part,
Eliminates the need to have parent-child information for each instance contained in the same parent. In addition, the common information includes a pointer to an instance list common part of an instance of the same class included in another parent instance, a pointer to an instance list common part of an instance of another class included in the same parent instance, By constructing from the pointer to the array block of the parent instance, it becomes easy to access another instance.

[0013]

FIG. 1 is a block diagram of an OSI management agent system showing one embodiment of the present invention. Reference numeral 1 denotes a management agent, and 2 denotes an OSI protocol processing unit for connection with a management manager (not shown). Reference numeral 3 denotes an MO data access control unit which searches for instance tree data indicating an instance inclusion relationship based on a management object identifier for identifying an instance in a message from the management manager, and Find the position information of the attribute data.

Reference numeral 4 denotes an instance tree data storage unit for storing the instance tree data. Reference numeral 5 denotes an attribute data management unit that specifies the storage location of the attribute data of the instance to be operated based on the obtained position information and the attribute data identifier for identifying the attribute data in the message. The local attribute data storage unit or the remote attribute data access control unit is requested to access the attribute data.

Reference numeral 6 denotes a local attribute data storage unit for storing attribute data existing in the agent 1, and reference numeral 7 denotes a remote attribute data access control unit for accessing attribute data existing outside the agent 1. In the present embodiment, the instance tree data storage unit 4, the attribute data management unit 5, the local attribute data storage unit 6, and the remote attribute data access control unit 7
B.

Next, the operation of such an OSI management agent system will be described. OSI protocol processing unit 2
Converts the operation message transmitted from the management manager by the OSI protocol into a data format that can be handled in the management agent 1, and
Pass the operation message to.

The MO data access control unit 3 extracts a management object identifier for identifying an instance to be operated from the operation message, and based on this information, stores the instance tree stored in the instance tree data storage unit 4. The data is searched to obtain a pointer to the attribute data of the corresponding instance (position information indicating the storage location where the attribute data is stored).

FIG. 2 is a diagram showing the basic structure of instance tree data. 10 is the attribute (property) of the class
A class definition entry 11 for storing class definition information defining behaviors and behaviors. An instance list 11 stores information shared by instances of the same class, which is pointed to by a pointer from the class definition entry 10 and is included in the same parent instance. The common part 12 is an array block that is pointed by the pointer from the instance list common part 11 and stores information of each instance of the same class included in the same parent instance.

The class definition entry 10 includes a class identifier for identifying a class, the above class definition information, and a pointer to the instance list common unit 11. Here, a plurality of instance list common units 11 having different parent instances may belong to the class indicated by the class definition entry 10, but the pointers to the instance list common unit 11 are common to the same class. It is a pointer to the common unit 11 created first among the units 11.

With this class definition entry 10, it is possible to obtain definition information of necessary attributes and obtain a pointer to an instance which is a substance of the class. next,
The instance list common unit 11 is composed of a pointer for accessing the class definition entry 10 of the class to which the self belongs, and obtaining class definition information, a pointer to an array block 12, and other common information. .

The common information includes, for example, a pointer to an instance list common part 11 of an instance of the same class included in another parent instance, and a common part 11 of an instance of another class included in the same parent instance.
To the array block 12 of the parent instance.

The array block 12 is made up of a group of elements (1 to N in FIG. 2) for storing information of each instance of the same class included in the same parent instance. And an instance number (the above-described management object identifier), a pointer to the attribute data of the instance, and a pointer to the head of the array block 12 of the child instance having the instance as a parent. By tracing the elements of the array block 12, other instances of the same class included in the same parent instance can be accessed at high speed.

The first element (0 in FIG. 2) of the array block 12 stores a pointer to the instance list common unit 11. By accessing the common unit 11 with this pointer, the common information of the instances belonging to the array block 12 can be extracted. Since the instance tree data shown in FIG. 2 also defines the inclusion relation of the instances, the instance tree data also has a hierarchical structure according to the hierarchical master-slave relationship of the instances.

FIG. 3 is a diagram showing a hierarchical structure of such instance tree data, and FIG. 4 is a diagram showing a containing tree corresponding to the instance tree data. 10b, 10c, 10
e is a class definition entry, 11b to 11e are instance list common parts, 12a to 12e are array blocks, A1
0, A11, B10, B11, C10, D10, E10
Is an instance. Note that instances A10, A
The eleventh class definition entry, the common part of the instance list, and “root” are omitted.

Considering the instance B10 as a starting point, access to the instance B11 included in the same parent instance A10 of the same class as the instance B10 can be realized by tracing the elements of the array block 12b. There is no need to follow A10.

The access to the instance D10 of the same class but a different parent as the instance B10 is performed by accessing the instance list common part 11b from the array block 12b and sharing the common information (pointer) of the common part 11b.
By accessing the common unit 11d of the instance D10 and accessing the array block 12d from the common unit 11d, the processing can be realized. Further, the instance B10 or B11 can be accessed from the instance D10 by following the reverse route.

An instance C of another class included in the same parent instance A10 as the instance B10
The access to 10 can be realized by accessing the common section 11c of the instance C10 and accessing the array block 12c from the common section 11c based on the common information of the instance list common section 11b as described above. Further, the instance C10 can access the instance B10 or B11 by following the reverse route.

Access to the parent instance A10 can be realized by accessing the array block 12a of the parent instance A10 using the common information of the common unit 11b in the same manner as described above. In addition, child instance E10
Can be realized by accessing the head of the array block 12e of the child instance E10 with the pointer of the array block 12b. The access method as described above is the same even when another instance is set as a starting point.

The access from the instance A10 to the instance C10 is performed by accessing the array block 12b of the instance B10 of another class included in the same parent instance A10 as the instance C10 by the above-described method. Common part 11
c, and subsequently by accessing the array block 12c.

This is because the pointer to the child instance stored in each element of the array block belongs to the class created first among a plurality of child instances of different classes included in the instance indicated by this element. This is because the array block of the child instance (B10, B11 in this embodiment) is accessed. In this way, the common information shared by the instances of the same class included in the same parent instance is provided in the instance list common unit 11, so that it is not necessary for each instance included in the same parent to have the information of the parent-child relationship. Space can be saved.

The OSI common management information service (Co
mmon Management Information Service (CMIS) operation to identify the instance, when using scoping, if you identify the first child instance,
An instance to be scoped can be specified without returning to the parent instance. For example, when the instances B10, B11, and C10, which are one level below the instance A10 in FIG.
2b, the instance list common part 11b
The common part 11c of the instance C10 by the pointer of
And the scope processing can be executed at high speed.

As described above, a pointer to the attribute data of the corresponding instance (hereinafter, referred to as position information) can be obtained from the array block 12 of the instance tree data. Next, the MO data access control unit 3 outputs to the attribute data management unit 5 the position information of the instance thus obtained and the attribute data identifier for identifying the attribute data included in the operation message from the management manager. , Requesting the operation of the attribute data of the corresponding instance.

The attribute data management unit 5 specifies the storage location of the attribute data based on the instance position information and the attribute data identifier obtained from the MO data access control unit 3. When the attribute data to be operated is stored in the management agent 1, the local attribute data storage unit 6 is accessed to execute an operation on the attribute data.

When the attribute data to be operated is stored outside the management agent 1, the remote attribute data access control unit 7 is requested to perform an operation on the remote attribute data. In response to such an operation, when the access result to the local attribute data is returned from the local attribute data storage unit 6 or the access result to the remote attribute data is returned from the remote attribute data access control unit 7, the attribute data The management unit 5 outputs this result to the MO data access control unit 3.

Then, the MO data access control unit 13
Outputs this to the OSI protocol processing unit 2,
The protocol processing unit 2 converts the received result into a data format for transmission to the management manager and transmits the data to the manager. As described above, in this embodiment, the remote attribute data existing outside the management agent 1 is stored in the internal MIB.
, The memory capacity of the management agent 1 can be saved. Further, it is not necessary to update the remote attribute data in the MIB, and the amount of communication from the outside to the management agent 1 is reduced, and the performance of the entire OSI management agent system can be improved.

[0036]

According to the present invention, by providing an attribute data management unit and a remote attribute data access control unit,
The attribute data management unit determines whether the attribute data to be operated is data managed inside the management agent or data held outside, and sorts the access destination, so it exists outside the management agent. There is no need to store attribute data in the agent, and the memory capacity of the management agent can be saved. Further, the amount of communication for updating attribute data from outside the management agent to the agent is reduced, and the performance of the entire OSI management agent system can be improved.

Further, by constructing the instance tree data from a class definition entry, an instance list common part, and an array block, common information shared by instances of the same class included in the same parent instance is shared by the instance list common part. Therefore, it is not necessary for each instance included in the same parent on the containing tree to have parent-child relationship information, and the memory capacity of the management agent can be saved.

Further, by constructing the common information from a pointer to the instance list common part of another instance and a pointer to the array block of the parent instance, the information is changed from one instance to another parent instance on the containing tree. When accessing an instance of the same contained class, or accessing another class instance contained in the same parent instance, there is no need to follow the parent instance, and the time to search for the instance can be reduced. , The performance of the OSI management agent system can be improved.

[Brief description of the drawings]

FIG. 1 is a block diagram of an OSI management agent system showing one embodiment of the present invention.

FIG. 2 is a diagram showing a basic structure of instance tree data.

FIG. 3 is a diagram showing a hierarchical structure of instance tree data.

FIG. 4 is a diagram showing a containing tree corresponding to the instance tree data of FIG. 3;

FIG. 5 is a diagram illustrating an example of a containment tree representing an inclusion relationship of MOs managed by a management agent.

FIG. 6 is a block diagram of a conventional OSI management agent system.

[Explanation of symbols]

1 management agent, 2 OSI protocol processing unit,
3 MO data access control unit 4 Instance tree data storage unit 5 Attribute data management unit 6 Local attribute data storage unit 7 Remote attribute data access control unit 10 Class definition entry 11 Instance list Common part, 12 ... arrangement block.

Claims (2)

(57) [Claims] 1. An OSI protocol processing unit for connection with an OSI management manager, an instance tree data storage unit for storing instance tree data indicating an instance inclusion relationship, and a management manager obtained by the OSI protocol processing unit An MO data access control unit that searches the instance tree data in the storage unit based on a management object identifier for identifying an instance in the message of the operation, and obtains position information of attribute data of the instance to be operated; A local attribute data storage unit for storing attribute data existing inside the agent, a remote attribute data access control unit for accessing attribute data existing outside the management agent, and attribute data present in the position information and the message To identify Based on the sex data identifier identifies the storage location of the attribute data of the operation target instance,
When the data exists inside the agent, the attribute data in the local attribute data storage unit is accessed. When the data exists outside, the attribute data management unit requests the remote attribute data access control unit to access the attribute data. possess the instance tree data, the class is Yes
Stores class definition information that defines attributes and behaviors
Class definition entry and included in the same parent instance
Shared information shared by instances of the same class
The common part of the instance list to be stored and this instance
Stores information of each instance belonging to common list
The class definition entry is composed of an array block
An identifier, the class definition information, and an instance list
The pointer to the common part is stored, and the instance list common part stores the class definition to which it belongs.
Pointer to entry and pointer to array block
And the common information, and the array block is provided for each element corresponding to each instance.
The said managed object identifier and this instance
Attribute information of this attribute and this instance as a parent
And pointers to array blocks of child instances
To the common section of the instance list to which it belongs.
An OSI management agent system for storing an interface in a first element . 2. The OSI management agent system according to claim 1 , wherein the common information is included in another parent instance.
To the instance list common part of the class instance
A pointer and another class contained in the same parent instance
To the instance list common part of the
And a pointer to the array block of the parent instance
OSI management agent system, characterized in that it is made of.