JP2914237B2 - Management object attribute reading device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a device for reading attributes of a managed object, and more particularly, to a system in which a manager and an agent use CMIP (Common Management).
GET of Information Protocol)
The present invention relates to a management object attribute reading method for reading a management object attribute in response to a request.

[0002]

2. Description of the Related Art Conventionally, in this type of attribute reading method of a managed object, a plurality of attributes of a managed object are read at a time.
As shown in -1 (standard), a method such as a scope or a filter is used.

[0003] For example, as shown in FIG.
When the attribute is read using the scope for the containment tree 13 of the system including the agent 1, the agent 12, and the containment tree 13, as shown in FIG. 10, each management object can be designated by the scope.

[0004] That is, as a method of specifying a plurality of management objects by the scope, (1) only the base object 21, (2) only the first level management object 22, and (3) the n-th management object 21 There are five ways of specifying only the management object 23: (4) all management objects 24 up to the nth from the base object 21, and (5) all management objects 25 under the base object 21.

[0005] Further, as a method of specifying a plurality of management objects by a filter, (1) the value of a specified attribute is equal to the specified value, or (2) a character specified as a part of the specified attribute. Whether the column is included, (3) the value of the specified attribute is greater than or equal to the specified value, (4) the value of the specified attribute is less than or equal to the specified value, or (5) all the attributes of the object are Whether it exists in the object, (6) it has the specified attribute, (7) all the attributes of the object exist in the specified attribute, or (8) one or more of the specified attributes There are eight ways to specify whether the attribute exists in the management object.

When a manager makes a GET request by combining the above-mentioned scope and filter, the agent returns a GET response as shown in FIG. 11 to the GET request.

[0007] For example, if the manager 31
That reads each of the managed objects A, B, and C
When a T request is made to the agent 32, the agent 32
Reads the information of each of the managed objects A, B, and C that meet the specified conditions of the scope and the filter from the inclusion tree 33, and obtains three types of GET responses of the managed object A, GET responses of the managed object B, and GET responses of the managed object C. A GET response is returned to the manager 31.

[0008]

In the conventional attribute reading method of a managed object described above, a scope and a filter are used to collectively read a plurality of attributes of a managed object. Becomes complicated, the programs of the manager and the agent become complicated.

In this case, the processing time becomes slow because the agent's GET response to the GET request from the manager must be returned by the number of objects matching the conditions specified by the scope and the filter.

Therefore, an object of the present invention is to solve the above-mentioned problems, to read out a plurality of attribute values collectively by a single operation, and to speed up the processing. Is to provide.

[0011]

An attribute reading device according to the present invention is an attribute reading device for a managed object generated by an agent assigning an attribute in advance based on designation information from a manager. the attribute is small when reading attributes of objects
Both are determined and determining means for determining whether or not a virtual attribute defined as an attribute of the self managed objects based on any attribute other managed objects and self managed object, and the virtual attributes in the determination unit The other managed object activated at the time and defined in the virtual attribute
Procedure means for reading the attribute of the self-managed object, and determining that the attribute is not the virtual attribute by the determining means
To read the attributes of the corresponding managed object when
And a step .

Another attribute reading apparatus for a managed object according to the present invention, in addition to the above configuration, further comprises means for activating the procedure means when the determination means determines the virtual attribute.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS First, the operation of the present invention will be described below.

A virtual attribute that is defined without having its own attribute value and has an attribute of another management object or its own management object as a value is defined in the management object.
As a result, a plurality of attributes can be read by one operation only by reading the virtual attributes.

Further, by making it possible to arbitrarily define an attribute value defined as an entity of a virtual attribute, complicated processing such as designating a relationship on an inclusion tree when a conventional scope or filter function is used. Becomes unnecessary.

Further, since the virtual attribute is handled as one attribute, only one GET response to the GET request from the manager is required, so that the process of reading a plurality of attributes of the management object at once can be speeded up. . Therefore, a plurality of attribute values can be read at once by one operation, and the processing can be speeded up.

Next, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing the configuration of one embodiment of the present invention. In the figure, a manager 1 issues a GET request such as a generation / setting / change / read request specifying management objects 3 to 6 and attributes to an agent 2, and the agent 2 manages the agent 2 in response to a GET request from the manager 1. Manipulate objects 3-6.

The management object 3 has attributes A and Z, the management object 4 has attributes B and C,
The management object 5 has an attribute D and an attribute E, and the management object 6 has an attribute F and an attribute G. The procedure (Procedure) means 7 has a virtual attribute of GE.
Automatically activated when requested.

Here, the attribute Z is a virtual attribute. The virtual attribute does not have its own attribute value, and the attributes B to G of the defined other management objects 4 to 6 or the attributes A of the self management object 3 are defined. It is an attribute that has a value.

FIG. 2 is a flowchart showing the operation according to one embodiment of the present invention. An operation of reading a virtual attribute according to an embodiment of the present invention will be described with reference to FIGS.

The manager 1 sends G to the agent 2
When making an ET request (step S1 in FIG. 2), the agent 2 determines whether the attribute requested by the GET is a virtual attribute (step S2 in FIG. 2).

If the attribute requested by the GET is not a virtual attribute, the agent 2 reads the attribute value of the specified management object among the management objects 3 to 6 (step S3 in FIG. 2), and sends the attribute value to the manager 1. Get
A response is returned (step S4 in FIG. 2).

If the attribute requested by the GET is a virtual attribute, the procedure means 7 is automatically started in response to the reading of the virtual attribute (step S5 in FIG. 2). The defined attribute values of the managed objects 3 to 6 are read and passed to the agent 2 (step S6 in FIG. 2).

The agent 2 returns the passed attribute value as a GET response to the manager 1 (step S in FIG. 2).
4). Therefore, manager 1 receives G from agent 2
By the ET response, the attribute value of the management object that has issued the GET request to the agent 2 can be known.

FIG. 3 is a diagram showing a definition example of an attribute Z which is a virtual attribute of the management object 3 of FIG. In the figure,
The attribute Z which is a virtual attribute is the attribute B of the management object 4.
The attribute D of the management object 5 and the attributes F and G of the management object 6 are defined in the procedure means 7 as an attribute group. The definition of the virtual attribute to the procedure means 7 is performed at the time of generation of the management object 3 by using a predetermined specific value indicating the virtual attribute.

FIG. 4 is a flowchart showing the operation of the procedure means 7 of FIG. The reading operation by the procedure means 7 will be described with reference to FIGS.

The procedure means 7 is such that the agent 2
When automatically activated by determining the attribute requested by the ET as a virtual attribute (step S11 in FIG. 4), the storage location of the defined virtual attribute, that is, the attribute of the management object 4 which is a defined attribute group The information indicating B, the attribute D of the management object 5, and the attributes F and G of the management object 6 are read (step S12 in FIG. 4).

The procedure means 7 stores the attribute value of the attribute B from the management object 4, the attribute value of the attribute D from the management object 5, and the management object 6 based on the information of the storage destination (defined attribute group) of the virtual attribute. , The attribute value of the attribute F and the attribute value of the attribute G are read (step S13 in FIG. 4).
To S16), and pass the read attribute values to the agent 2 (step S17 in FIG. 4).

In this case, the procedure means 7 stores information on the storage location of the virtual attribute, that is, information indicating the attribute B of the management object 4, information indicating the attribute D of the management object 5, and attributes F and G of the management object 6. Are used as address information, and the respective attribute values are read from the managed objects 4 to 6.

FIG. 5 is a diagram showing a specific example of attributes defined for the managed objects 3 to 6 in FIG. In the figure, the management object 3 has an attribute A1, an attribute A2, an attribute A3, an attribute A4, an attribute A5, and an attribute A6, and the values of the attributes are attribute A1 = Tokyo, attribute A2 = 100, attribute A3 = large, attribute A4 = east, attribute A5 = virtual attribute 1, attribute A6 = virtual attribute 2 are defined.

The management object 4 has attributes B1 and B2.
And attribute B3, and the value of each attribute is defined as attribute B1 = left, attribute B2 = Osaka, and attribute B3 = 39. The management object 5 has an attribute D1 and an attribute D2, and the value of each attribute is defined as attribute D1 = 95 and attribute D2 = north.
The management object 6 has an attribute F1, an attribute F2, and an attribute F3, and the value of each attribute is attribute F1 = Sapporo, attribute F2 = down,
Attribute F3 = high-speed type is defined.

FIG. 6 is a diagram showing a specific example of the definition of the attribute A5 in FIG. In the figure, an attribute 5 is a virtual attribute, and is defined as an attribute group in which an attribute B2 of the management object 4, an attribute B3 of the management object 4, an attribute D2 of the management object 5, and an attribute F1 of the management object 6 are respectively defined. .

When the attributes are defined as described above,
When the manager 1 makes a GET request for the attribute A5 of the management object 3 to the agent 2, the procedure means 7 is started because the attribute A5 is a virtual attribute.

The procedure means 7 reads the value of each attribute defined in FIG. 6 from each of the management objects 4 to 6 and passes "attribute A5 = Osaka, 39, North, Sapporo" to the agent 2 as the attribute value of the attribute A5. .

The agent 2 sets the attribute "A5 = Osaka, 3
9, north, Sapporo ”as a value of the attribute 5 of the management object 3 and a GET response is sent to the manager 1. Therefore, the manager 1 can know the attribute values of the managed objects 4 to 6 defined in the attribute by one operation only by making a GET request for one attribute.

FIG. 7 is a diagram showing a specific definition example of a virtual attribute according to another embodiment of the present invention. In the figure, an attribute 6 is a virtual attribute, and all the attributes other than the virtual attributes (attributes A5 and A6) of the management object 3, that is, the attribute A1 of the management object 3, the attribute A2 of the management object 3, and the attribute A3 of the management object 3 , An attribute A4 of the management object 3 is defined as an attribute group.

When the attributes are defined as described above,
When the manager 1 makes a GET request for the attribute A6 of the management object 3 to the agent 2, the procedure means 7 is started because the attribute A6 is a virtual attribute.

The procedure means 7 reads the value of each attribute defined in FIG.
6 = Tokyo, 100, large, east ”is passed to the agent 2 as the attribute value of the attribute A6.

The agent 2 sets "Attribute A6 = Tokyo, 10
GET response to the manager 1 with "0, large, east" as the value of the attribute 6 of the management object 3. Therefore, the manager 1 can know the attribute values of the managed objects 4 to 6 defined in the attribute by one operation only by making a GET request for one attribute.

FIG. 8 is a diagram showing a specific definition example of a virtual attribute according to another embodiment of the present invention. In the figure, the attribute 6 is a virtual attribute, and all attributes other than the attribute A6 of the management object 3, that is, the attributes A1 and
Attribute A2 of management object 3, attribute A3 of management object 3, attribute A4 of management object 3, and attribute A5 of management object 3 are defined as an attribute group.

If the attributes are defined as described above,
When the manager 1 makes a GET request for the attribute A6 of the management object 3 to the agent 2, the procedure means 7 is started because the attribute A6 is a virtual attribute.

The procedure means 7 reads the value of each attribute defined in FIG.
= Tokyo, 100, large, east, Osaka, 39, north, Sapporo "to the agent 2 as the attribute value of the attribute A6.

The agent 2 sets "Attribute A6 = Tokyo, 10
"0, large, east, Osaka, 39, north, Sapporo" as a value of the attribute 6 of the management object 3 to the GET response to the manager 1. Therefore, a plurality of management objects 3
Virtual attributes (attribute A5) in addition to the plurality of attributes of
Can also be defined.

In the above description, one embodiment of the present invention is described.
Although reading of the virtual attribute according to another embodiment of the present invention and another embodiment of the present invention has been described, reading of attributes other than the virtual attribute can also be performed as follows.

That is, the manager 1 is the agent 2
When the agent 2 makes a GET request for the attribute D2 of the management object 5, the agent 2 reads “attribute D2 = north” from the management object 5 as the attribute value of the attribute D2 because the attribute D2 is not a virtual attribute. = North ”as the value of the attribute D2 of the management object 5,
Answer T. Therefore, the attribute D2 defined by the entity of the attribute A5, which is a virtual attribute, can be directly requested directly.

As described above, by defining in the management object 3 a virtual attribute which is defined without having its own attribute value and which has an attribute of the other management objects 4 to 6 or the self-management object 3 as a value, the virtual attribute is defined. A plurality of attributes can be read by one operation only by reading the attributes.

Further, by making it possible to arbitrarily define an attribute value defined as an entity of a virtual attribute, complicated processing such as designating a relationship on an inclusion tree when a conventional scope or filter function is used is used. Becomes unnecessary.

Further, since the virtual attribute is also treated as one attribute, only one GET response to the GET request from the manager 1 is required, so that the process of reading a plurality of attributes of the managed objects 3 to 6 collectively is accelerated. can do.
Therefore, a plurality of attribute values can be read at once by one operation, and the processing can be speeded up.

[0049]

As described above, according to the present invention, in an attribute reading device for a managed object, which is generated by assigning an attribute in advance by an agent based on designation information from a manager, the agent reads the attribute of the managed object. When the attribute is determined to be a virtual attribute defined as an attribute of the self-managed object based on one of the attributes of the other managed object and the self-managed object, another management is performed based on the definition content of the virtual attribute. By activating the procedure means for reading the corresponding attribute from the object, a plurality of attribute values can be read at once by one operation, and the processing can be speeded up.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention.

FIG. 2 is a flowchart illustrating an operation according to an embodiment of the present invention.

FIG. 3 is a diagram illustrating a definition example of virtual attributes of the management object in FIG. 1;

FIG. 4 is a flowchart showing the operation of the procedure means of FIG. 1;

FIG. 5 is a diagram showing a specific example of attributes defined for each management object in FIG. 1;

FIG. 6 is a diagram showing a specific definition example of virtual attributes in FIG. 5;

FIG. 7 is a diagram showing a specific definition example of a virtual attribute according to another embodiment of the present invention.

FIG. 8 is a diagram showing a specific definition example of a virtual attribute according to another embodiment of the present invention.

FIG. 9 is a block diagram showing a configuration of a conventional example.

FIG. 10 is a diagram showing a configuration of a conventional containment tree.

FIG. 11 is a flowchart showing attribute reading processing of a conventional example.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Manager 2 Agent 3-6 Management object 7 Procedure means A-G, A1-A4, B1-B3, C1, C2, D1-D3 Attribute Z, A5, A6 Virtual attribute

──────────────────────────────────────────────────続 き Continuation of front page (58) Field surveyed (Int.Cl. ⁶ , DB name) G06F 12/00 G06F 13/00

Claims (5)

(57) [Claims] 1. An attribute reading device for a managed object generated by an agent by assigning an attribute in advance based on designation information from a manager, wherein the attribute is read when the agent reads the attribute of the managed object.
A determining unit that determines whether or not the attribute is a virtual attribute defined as an attribute of the self-managed object based on at least one of the attributes of the other managed object and the self-managed object; The other management objects activated at the time and defined in the virtual attribute
Procedure means for reading the object and the attribute of the self-managed object, and the determination means determines that the attribute is not the virtual attribute.
Read the attribute of the corresponding managed object when
Attribute reading apparatus characterized by having means to issue. 2. The attribute reading device according to claim 1, further comprising: means for activating said procedure means when said determination means determines said virtual attribute. 3. The virtual attribute includes only the attribute of the other management object and the value of the attribute of the self-management object.
Attributes reading apparatus according to claim 1 or claim 2, wherein the to have it. 4. The virtual attribute uses only the attribute of the self-managed object as a value of the attribute of the self-managed object.
Attributes reading apparatus according to claim 1 or claim 2, wherein the having Te. 5. The virtual attribute may be any attribute of the other managed object and the self-managed object and another virtual attribute as an attribute value of the self-managed object.
Attributes reading apparatus according to claim 1 or claim 2, wherein the having Te.