JPH04207651A - Management data storage device - Google Patents

Abstract

PURPOSE:To reduce the processing time used for the transfer from a management resource to a management data storage device by utilizing an access means of a management object so as to read each attribute of the management resource as required. CONSTITUTION:The attribute of management resource is not set in the management object and when an access request of the attribute with respect to a management object is publicated via an external interface 310, attribute access means 330-332 are called and the attribute is directly read or written from the management resource. In this case, event detection means 340-342 are simultaneously started to check whether or not there is a fault in the attribute to be accessed. For a period when no access request is in existence to the management object, event detection means 340-342 of each management object are called periodically to detect an event. Thus, the access with respect to the attribute of the management resource from a management application processing means is processed at a high speed.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of Industrial Application The present invention is a component of a network management system,
The present invention relates to a management data storage device that is installed for each managed node and stores attribute values of management resources existing in each node.

2. Related Art Conventional management data storage devices include, for example, the Information Processing Society of Japan's 41st National Convention (3Q-3, 1990).
There is something shown in FIG. 4 shows a configuration diagram of a managed node having a conventional management data storage device. The managed nodes are composed of workstations, personal computers, etc., and are connected to the network via a transmission line 20. 400
is a communication module connected to the transmission path 20, and is composed of hardware and software for executing communication procedures of the managed notebook 10. 40 to 44 are communication modules 40
Various management resources (protocol machines, connections, counters, etc.) existing in
Stored at 0. Here, the attribute value refers to the communication module 40 such as a protocol machine, connection, counter, etc.
This refers to the name, number, and current status of each resource within 0. The management data storage device 100 stores managed objects 120 to 122 that store attribute values for each managed resource and controls access to those attribute values, and analyzes external access requests to these managed objects and performs appropriate processing. The management interface 110 interfaces with managed objects. The managed object 120 is connected to the layer management interface 50 and the management interface 110, and includes a memory 130 for holding attribute values (name, number, current processing state) regarding a particular managed resource (eg, protocol machine 40). , and an access unit 140 for accessing attribute values on the memory 130. Similarly, managed objects 121 may include specific managed resources (e.g., connections 41
), and an access unit 141 for accessing the attribute values on the memory 131, and the management object 122 holds attribute values regarding a specific management resource (for example, the counter 44). The access unit 142 includes a memory 132 for accessing attribute values on the memory 132. Reference numeral 200 denotes a management application processing means for controlling management operations in the managed node 10, and is software that operates while being connected to the communication module 30 and the management data storage device 100.

Note that the management interface 110 and access units 140 to 142 in the management data storage device 100 are realized as software.

In the conventional managed node configured as above,
The operation when the management data storage device 100 manages attribute values regarding the management resources 40 to 44 in the communication module 400 will be described. When a managed node sends and receives data to and from a management node (not shown) via the transmission path 20, the communication module 400 operates to change one of the attribute values of the management resources 40 to 44 existing therein. part changes.

Changes in these attribute values are notified to the corresponding managed objects in the management data storage device 100 via the layer management module 50 every time the communication module 30 operates.

For example, attribute values of protocol machine 40 are communicated to managed object 120 by layer management interface 50 . In the managed object 120, the access section 1
40 performs processing for storing the received attribute value in memory 130. At this time, before storing the received attribute value, the access unit 140 checks whether the data type and range of possible values of this attribute value are appropriate, or whether an event that should be reported has occurred. do. As a result of the check, if there is no abnormality, the attribute value is stored in the memory 130,
It continues to be held in the memory 130 for a period until it is updated next time. - On the other hand, if an event such as an abnormality is detected as a result of the check, this event information is sent to the access unit 14.
0 to the management interface 110, and from the management interface 110 to the management application processing means 200 in 4. Then, in response to the notified event, the management application processing means 200
Appropriate management actions will be taken.

Problems to be Solved by the Invention However, in the above configuration, the management resources 40 to 4
The attribute value of 4 is the memory 13 in the management data storage device 100.
0 to 132 and held, the number of times these attribute values are copied increases as the amount of communication increases, making the process of updating attribute values in the management data storage device 100 more difficult. As a result, there has been a problem in that the response time when the management application processing means 200 accesses the attribute values of the management data storage device 100 becomes long.

The present invention solves these problems, and aims to provide a management data storage device that can process access to attribute values of managed resources from a management application processing means at high speed even when the amount of communication increases. It is something.

Means for Solving the Problems In order to solve the above problems, the management information storage device of the present invention is installed for each managed node in a network management system in which managed nodes are managed by a management node, and the management information storage device of the present invention is installed in each managed node. a management data storage device that stores attribute values of managed resources existing in an external interface that selects and activates an access means provided by the managed object in response to an external access request to the managed object; The interface is provided with a timer that requests activation of the event detection means at fixed time intervals, and in response to a request from the timer, the external interface activates the event detection means for all managed objects, and each It is characterized by detecting events of managed resources.

According to the above-described configuration, the present invention does not hold the attribute value of the managed resource in the managed object, but calls the attribute value access means when an attribute value access request to the managed object is issued via the external interface, Read or write attribute values directly from managed resources. At this time, the event detection means is activated at the same time to check whether there is any abnormality in the accessed attribute value. Furthermore, during a period when there is no access request to a managed object, the event detection means of each managed object is periodically called up by input from a timer to perform event detection.

EXAMPLE An example of the present invention will be described below based on the drawings. Second
The figure shows a schematic configuration of a network management system to which the present invention is applied. In the figure, 1 is a management node that is a management device, and 2.3 is a managed node that is a managed device.

The management node 1 sends management operation messages indicating management operation instructions to each of the managed nodes 2 and 3, while each of the managed nodes 2 and 3 sends management information and information to the management node 1 according to the management operation message. Management operation response messages such as management operation completion information and notification messages for notifying occurrences of failures, changes in status, etc. are transmitted.

The management node 1 and the managed nodes 2 and 3 each have a configuration as shown in FIG. 3.

In FIG. 3, 200 is a management application processing means, 1b and 4oo are communication modules, and 300 is a management data storage device.

The communication module lb, 400 functions to perform various protocol processing, GET command processing and SET command processing for requesting management information etc. from the managed node 2, and is composed of a protocol machine, a connection, a counter, etc.

Network management by this management system is performed as follows. For example, when the management notebook 1 requests the managed nodes 2 and 3 to send management information using a GET command, the management application processing means 1a sends the GET command to the command processing function section of the communication module by starting the management application program. Output management operation instructions. As a result, the management service is output by processing the GET command in the command processing library. Then, based on the management service, a management operation message indicating a GET command is transmitted to the managed nodes 2 and 3 through predetermined communication protocol processing in the communication protocol processing library.

In the managed nodes 2 and 3, the communication module 400 extracts the management service from the received management operation message,
The management operation instruction of the command output from the management application processing means 1a is restored and output to the management application processing means 200.

The management application processing means 200 performs processing based on the management operation instructions, and the management data storage device 300
Outputs the management data obtained from the management data as a management operation response. This management operation response is output as a management operation response message via the communication module 400, and is sent to the management node 1.
The information is sent to the management application processing means 1a via the communication module 1b.

FIG. 1 shows a detailed configuration of the management data storage means 300. Note that components corresponding to those of the conventional management data storage device shown in FIG. 4 are given the same numbers, and detailed explanations are omitted. The management data storage device 300 is a device that manages the attribute values of the managed resources 40 to 44 in the managed nodes 2 and 3, and includes a managed object 320 that includes access means for attribute values for each managed resource and means for detecting events. ~
322, an external interface 310 that analyzes requests from management nodes (not shown) for these managed objects and interfaces with the timer 350 or appropriate managed objects, and a set time period for the external interface 310. The timer 350 requests event detection regarding the management resources 40 to 44 at each time. The managed object 330 includes an access unit 330 that reads or writes attribute values related to a specific managed resource (for example, the protocol machine 40) according to instructions from the external interface 310, and an event detection unit that detects errors and events related to the attribute values. 340. Similarly, the managed object 331 includes an access unit 331 that reads or writes attribute values related to a specific managed resource (for example, connection 41) according to instructions from the external interface 310, and an event unit that detects errors and events related to the attribute values. The management object 332 includes an access unit 332 that reads or writes attribute values related to a specific management resource (for example, the counter 44) according to instructions from the external interface 310, and an access unit 332 that reads or writes attribute values related to the attribute values in accordance with instructions from the external interface 310. An event detection unit 342 that detects
It is equipped with

Note that each component within the management data storage device 300 is implemented as software.

Next, the operation of the management data storage device having the above configuration will be explained.

When the managed nodes 2 and 3 transmit and receive data to and from the outside via the transmission path 20, the management resources 40 to 4 existing therein are transmitted and received by the communication module 400.
The attribute value of 4 changes. The result of updating these attribute values is
The management data storage device 300 is not notified and the management resource 4
It is held internally between 0 and 44. The attribute value of the managed resource is notified from the managed resource to the managed data storage device 300 only when the management application processing means 200 issues an access request to the managed data storage device 300. For example, when the management application processing means 200 issues a read request for attribute values regarding the managed resource 40 to the management data storage device 300, this read request is analyzed by the external interface 310,
As a result, the managed object 3 corresponding to the managed resource 40
20 access unit 330 and event detection unit 340 are called.The access unit 330 directly reads the attribute value from the managed resource 40 and passes the value to the event detection unit 340.The event detection unit 340 reads the attribute value. Checks whether the type and range of possible values are appropriate, or whether an event that should be reported has occurred, and if there is no abnormality, the read attribute value is sent to the management application processing means via the external interface 310. 200.

On the other hand, if an event such as an abnormality is detected as a result of the check, the event information is sent to the external interface 31.
0 to the management application processing means 200.

A time period for issuing an event detection request is set in the timer 350 by the management application processing means 200, and the timer 350 periodically notifies the external interface 310 of the event detection request at that period.

External interface 310, which has received this request, calls event detection units 340-342 to instruct all managed objects 320-322 to detect events. The event detection unit 340 uses the access unit 330 to read the attribute value of the management fee a40, checks the value, and notifies the external interface 310 of the result.

Similarly, the event detection unit 341 uses the access unit 331 to read the attribute value of the managed resource 41, checks the value, and notifies the external interface 310 of the result, and the event detection unit 342 uses the access unit 332 to The attribute value of the managed resource 44 is read out, the value is checked, and the result is notified to the external interface 310. These results are sent to the external interface 31 if there are any events to report.
0 to the management application processing means 200.

As described above, according to this embodiment, the attribute values of the managed resources 40 to 44 are notified to the corresponding managed objects in the management data storage device 300 only when the management application processing means 200 accesses them, so The interference between the module 400 and the management data storage device 300 is reduced, and as a result, the management data storage device 300
The processing load will be reduced. Furthermore, since events related to the managed resources 40 to 44 are periodically checked by the operation of the timer 350, no abnormal state of the attribute value of the managed resources is left undiscovered.

Effects of the Invention As described above, according to the present invention, individual attribute values of managed resources are not copied into the management data storage device;
Since the structure is such that reading is performed using the access means of the managed object as necessary, the data to be moved from the managed resource to the managed data storage device is limited to the minimum necessary, and the processing time spent on the movement can be reduced. Furthermore, since no actual data is stored in the management data storage device, the structure of the management data storage device is simplified. Furthermore, since the C2 attribute values are periodically checked using a timer, it is possible to prevent the risk of management resources being left in an abnormal state, which has a great practical effect.

[Brief explanation of the drawing]

FIG. 1 is a configuration diagram of a managed node having a management data storage device showing one embodiment of the present invention, FIG. 2 is a diagram showing a schematic configuration of a network management system to which the present invention is applied, and FIG.
This figure shows the overall configuration of a management node and a managed node in a network management system, and FIG. 4 is a configuration diagram of a managed node having a conventional management data storage device. 2.3...Managed node, 20...Transmission path, 40~
44... Management resource, 50... Layer management interface, 200... Management application processing means, 30
0... Management data storage device, 310... External interface, 320-322... Management object, 3
30-332... access section, 340-342...
Event detection unit, 350... Timer, 400...
Communication module. Agent: Shiro Nakajima, Patent Attorney Figure 2 Proceedings, 1991 Patent Attorney No. 337925, 1991, Patent Attorney No. 337925, 1990, Invention Name Management Data Storage Device 3, Person Making Amendment Case and Relationship Patent applicant address 1006 Kadoma, Kadoma City, Osaka Prefecture Name (58
2) Reply by Matsushita Electric Industrial Co., Ltd. Representative Voluntary Disclosure 6, Power of attorney to be amended and “Detailed Description of the Invention” column 7 of the specification, Contents of the amendment (1) As per the appendix to the power of attorney (2) Invention Detailed explanation ■The statement "Communication module 30" on page 4, line 14 of the specification will be corrected to "1 communication module 400." ■Correct "Communication module 30" to "Communication module 400" on page 5, line 8 of the statement. ■On page 9, lines 18 to 19 of the specification, the phrase ``Communication...processing'' has been corrected to ``Communication module lb, 400, management nodes 1 to j.'' ■Page 9 of the specification Insert "for 1" after "to node 2" on the 19th line of the page. ■Insert "Acquisition j" after "Management information, etc." on page 9, line 19 of the statement. ■Process the rGET command on page 9, line 20 of the statement.
Insert "Request settings for management information, etc." after . ■In the first line of page 10 of the specification, it says ``It is something to be done...'' which is corrected to 1 as it is a device that performs various protocol processing functions to give r instructions. ■In the second line of page 10 of the statement, the phrase ``consisting of'' will be corrected to ``includes r managed resources.'' ■Correct the statement ``Management node (not shown)'' on page 11, lines 19-20 of the statement to r management application 2001. [Phase] Correct "Managed Object 330" in lines 5 and 6 on page 12 of the statement to r managed object 3201. ■Correct "Managed Object 331" on page 12, lines 11-12 of the statement to r managed object 3211. ■On page 12, line 17 of the statement, “Managed object 33
Correct 2J to r managed object 3221. (3) Replace Figures 3 and 4 attached to the drawing application with the attached drawings.

Claims (1)

[Claims] (1) A management data storage device that is installed for each managed node in a network management system in which managed nodes are managed by a management node and stores attribute values of management resources existing in the managed node, A managed object having an access means for reading or writing an attribute value of a resource, and an event detection means for inspecting the attribute value read or written using the access means and reporting an event such as an error; an external interface that selects and activates the access means provided by the managed object in response to an external access request to the object; and a timer that requests the external interface to activate the event detection means at fixed time intervals. A management data storage device, characterized in that, in response to a request from a timer, the external interface activates the event detection means for all managed objects to detect events for each managed resource.