JPH08328970A - Log possessing system for equipment to be managed - Google Patents

Abstract

PURPOSE: To speedily record a log inside equipment to be managed into the storage medium of a control manager at the time of recovery even when there is any fault at the control manager or a network when the logs inside the equipment to be managed reach a prescribed number. CONSTITUTION: In the case of a log full report from equipment 30 to be managed, the start of a control manager 10 or the fault recovery of a network 20, this is recognized by a log possession timing recognizing means 11 of the control manager 10 and that log is possessed from the side of the control manager 10 to the equipment 30 to be managed by a log possession executing means 12. Thus, when the control manager 10 is turned to the state of disabling the reception of the log full report from the equipment 30 to be managed, the log is positively possessed from the control manager 10 to the equipment 30 to be managed at the recovery time of that state so that the log stored in the equipment 30 to be managed can be prevented from being lost by overwrite without being possessed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a managed device log acquisition method, and more particularly to a managed device log acquisition method for acquiring a log of occurrence inside a managed device connected to a management manager via a network. Regarding

[0002]

2. Description of the Related Art Conventionally, in a system configured by connecting a management manager and a managed device via a network, when an error occurs in the managed device, error information is logged each time. Due to the memory limitation in the managed device, the number of logs that can be held by the device is limited, and it is not possible to hold more than a certain number (maximum number of logs).
Therefore, the log is transferred to the management manager before the memory is full, and the error information generated in the managed device is stored / saved in the storage medium of the management manager.

As a method of notifying the management manager of error information from the managed device, for example, Japanese Patent Laid-Open No. 3-19 is available.
An example is described in Japanese Patent No. 5142. According to this publication, if the failure information that has occurred in the transmission device is held and a fixed number of failures have occurred, or if a fixed time has elapsed from the notification before that, the failure information that has been held Is collectively described to another transmission device connected via a transmission line.

[0004]

However, as disclosed in the above-mentioned Japanese Patent Laid-Open No. 3-195142, when a certain number of failures occur, or when a certain time has passed from the previous notification, the hold In the method of collectively transferring the fault information that has been stored to another transmission device, if some fault occurs in the transfer destination device and the transmission line at the time of transferring the fault information, the transfer source device transfers the fault information again. Unless it is done, there is a problem that the failure information may be lost.

The present invention has been made in view of the above circumstances, and when the number of logs in the managed device reaches a predetermined number and it becomes necessary to transfer the logs to the management manager, the management manager is stopped or When neither the notification that the number of logs has reached a predetermined number nor the transfer of logs can be performed due to a failure or a failure in the network, the logs in the managed device are not lost to the storage medium of the management manager. It is an object of the present invention to provide a log acquisition method of a managed device that enables recording.

[0006]

In order to solve the above problems, the present invention provides a log acquisition method for a managed device that acquires a log of occurrence inside a managed device connected to a management manager via a network. In the above, in the management manager, the log acquisition timing recognition means (11) for recognizing the timing for acquiring the log accumulated in the managed device and outputting the log acquisition trigger, and the log acquisition by the log acquisition timing recognition means A log acquisition method for a managed device, comprising: a log acquisition executing unit (12) that collects and stores logs accumulated in the managed device in response to a trigger output. To be done.

[0007]

According to the above-mentioned means, the timing for the log acquisition timing recognizing means (11) to acquire the logs accumulated in the managed device can be determined, for example, by receiving a log full notification from the managed device, or on the network. Alternatively, when the management manager recognizes the error recovery, the process for log acquisition is started. The log accumulated in the managed device is acquired by the log acquisition executing means (12).
This allows the managed device to send logs to the management manager instead of sending logs unilaterally regardless of the state of the network or the management manager, so the managed device notifies the management manager of the log full. Even if there is a failure in the network or the management manager when you do this, you can get the log after the failure is recovered, and the management manager will surely acquire the log and save it in the recording medium. It is possible to go.

[0008]

An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram showing the configuration of a log acquisition method of a managed device according to the present invention.

The network system for implementing the present invention comprises a management manager 10, a network 20, and a managed device 30. The log acquisition method of the managed device of the present invention is based on the management manager 10 side.
Log acquisition time recognition means 11 and log acquisition execution means 12
And a trap interval setting means 13 and a management manager address setting means 14. With respect to the configuration on the management manager 10 side, the managed device 30 provides a logfull notification means 31 for performing a logfull notification when a log is registered in excess of a predetermined value.
A log transmitting means 32 for transmitting the accumulated logs to the management manager side, and a trap interval changing means 33 for changing the trap interval value in response to a setting change request from the trap interval setting means 13 of the management manager 10. , Management manager address registration means 34 for registering a notification destination management manager for log full notification in response to a setting change request from the management manager address setting means 14 of the management manager 10.

In the above structure, the logs generated in the managed device 30 are sequentially logged in the memory, and when the number of logs exceeds the value set by the trap interval changing means 33, the log full notifying means 31. As a result, the management manager 10 is notified of the log full. When the log acquisition time recognition means 11 of the management manager 10 receives the log full notification from the managed device 30, the log acquisition execution means 12 is activated, and the log acquisition execution means 12 issues a log acquisition request to the managed device 30. . In response to this, the log transmitting means 32 of the managed device 30 transmits the untransmitted log to the management manager 10. The log acquisition execution means 12 stores the transmitted log in a recording medium such as a hard disk and saves it.

The log acquisition timing recognizing means 11 of the management manager 10 also recovers when a failure occurs in the network 20 or the management manager 10, or when the management manager 10 is brought up from the stopped state. Recognize that. When the log acquisition time recognizing means 11 recognizes the recovery from the failure, there may have been a log full notification from the managed device 30 during the occurrence of the failure. Therefore, the log acquisition executing means 12 is activated and stored in the managed device 30. Try to get the log. As a result, not only when the log full notification is normally received, but also when the log full notification cannot be normally received, the managed device 3
It becomes possible to record all the logs of 0 in the recording medium of the management manager 10.

In the preferred embodiment, the management manager 10 can be a network management system and the managed device 30 can be a printer, and although not shown, a plurality of computers for using the printer are used for the network 20 connecting them. , A document processing device, etc. are connected.

FIG. 2 is a flowchart showing the trap interval value changing process. In the managed device 30, the log-full notifying means 31 notifies the management manager 10 that the log has become full when a certain number of logs have been logged. The maximum number of logs that can be logged is determined by the memory capacity that saves the generated logs. The log full notification is given to the management manager 10 when a certain number of logs smaller than the maximum number are saved. The number of logs from the last log full notification trap to the next log full notification trap is called the trap interval. The managed device 30 has a certain value as the value of this trap interval, but the response of the managed device 30 to the log acquisition request, the memory capacity, that is, the maximum number of logs that can be held, the log occurrence frequency, etc. In consideration of the above, the value of the trap interval can be changed from the management manager 10 side. The value of the trap interval is changed by the trap interval setting unit 13 of the management manager 10 and the trap interval changing unit 33 of the managed device 30.

In the flowchart shown in the figure, when a setting change request is issued from the management manager 10 side (step S11), the trap interval changing means 33 of the managed device 30 judges whether the trap interval value is correct or not. (Step S12). That is,
It is determined whether or not the notified value is less than or equal to the maximum number of logs determined from the capacity of the memory that the managed device 30 has for storing logs. Here, the notified value is not a value that can be taken as the trap interval value. If it is determined that the value is ended without changing the value, and if it is determined to be a possible value, a process of changing the value is performed (step S13).

FIG. 3 is a flow chart showing the flow of management address setting processing. When the managed device 30 stores a certain number of logs or more, it notifies the management manager 10 that the log is full, but when there are a plurality of management managers 10, which management manager is notified. It can be set in the managed device 30. The setting of the management manager of this notification destination can also be set from the management manager side, and is executed by the management manager address setting means 14 of the management manager 10 and the management manager address registration means 34 of the managed device 30.

According to the flow chart shown in the figure, when there is a request from the management manager 10 (step S21), the management manager address registration means 34 of the managed device 30.
Does the request want to newly register as a notification destination,
It is determined whether the registration is to be deleted or the registration is to be changed (step S22). If the request from the management manager 10 is determined to be registration, the management manager address registration processing is performed (step S23), and if it is determined to be deleted, the management manager address deletion processing is performed (step S24) and changed. If it is determined that the management manager address is changed (step S2)
5).

FIG. 4 is a flow chart of a judgment process of whether or not to start log acquisition. When acquiring the log stored in the managed device 30 from the management manager 10, the management manager 10 monitors the change of the event by the log acquisition time recognition means 11 as an opportunity (step S31). Here, it is detected whether a log full trap is received from the managed device 30 (step S32), the management manager 10 is started up (step S33), or recovery from a network failure (step S34) is detected. , A log acquisition trigger is generated (step S
35), if neither event change is detected, the log acquisition trigger does not occur. Next, it is determined whether or not a log acquisition trigger has occurred (step S36). If no log acquisition trigger has occurred, the process returns to step S31. If a log acquisition trigger has occurred, this processing flowchart ends,
This is the trigger for log acquisition.

FIG. 5 is a flowchart of the log full notification process. When a log is generated in the managed device 30 and the log data is stored in the memory (step S41), the number of logs accumulated from the previous log full notification to the time when the latest log is generated is calculated ( Step S42). Next, the registered trap interval value and the calculated number of logs are compared to determine whether the calculated value is larger than the trap interval value (step S43). Here, if it is determined that the calculated value is not larger than the trap interval value, this processing is ended as it is, and if it is determined that it is larger, the "log ID at log full" is updated to the latest log ID at that time (step S44). The log ID is uniquely given to the log generated from the start of use of the managed device 30, and the “log ID at log full” is changed to the log ID each time a log full trap is raised. This "log ID at log full" is a value used for calculating the number of logs in step S42. And
When the "log ID at log full" is rewritten, a log full trap is sent to the management manager 10,
This process ends (step S45).

FIG. 6 is a flowchart showing a recovery process from a network failure. In the management manager 10,
The log acquisition time recognizing means 11 periodically accesses the managed device 30 (step S51), and determines here whether an access error occurs (step S5).
2). If no access error occurs, step S51
If an access error occurs in preparation for the next access, it is assumed that the network has failed (step S
53). Next, the managed device 30 is again accessed regularly (step S54), and it is determined whether or not there is an access error (step S55). Here, if there is an access error, the procedure returns to step S54 to prepare for the next access, and if the access error disappears, it is assumed that the network failure is recovered (step S56). When this network failure recovery is detected, the management manager 1
0 is an opportunity to request the managed device 30 to acquire a log.

FIG. 7 is a diagram showing a concrete configuration example of the management manager. According to this configuration example, the management manager includes the log acquisition trigger generation unit 101 that receives a log full notification from the managed device and generates a log acquisition trigger. The log acquisition trigger generation unit 101 monitors the management manager start-up notification unit 102 for notifying that the management manager has normally started up when the management manager is activated, and whether or not a failure has occurred in the network. Is connected to the network failure recovery notifying section 103 that notifies the failure when the failure is recovered, and even if there is a notification from the management manager startup notifying section 102 or the network failure recovery notifying section 103,
The log acquisition trigger generation unit 101 generates a log acquisition trigger. In the output of the log acquisition trigger generation unit 101, the log acquisition execution unit 104 receives the generated log acquisition trigger.
Is connected. The log acquisition execution unit 104 requests the managed device to acquire the log, and when the log is transferred from the managed device in response to the request, the hard disk 105 for recording and storing the transferred log is It is connected. The management manager further includes a trap interval change request unit 106 that requests the managed device to set / change the trap interval value and a management manager address setting request unit that requests the managed device to set a logfull notification destination. And 107.

FIG. 8 is a diagram showing a specific configuration example of the managed device. The managed device illustrated here is a log full notifying unit 210 that gives a log full notification to the management manager.
A data storage unit 220 for storing data such as a log generated in the managed device and a value set / registered by a request from the management manager side; and a data storage unit 220 held by the data storage unit 220 according to a request from the management manager. Log transmitting unit 230 for transferring the log data, the trap interval value changing unit 240 for changing the value of the trap interval according to the request from the management manager, and the registration / deletion / change of the notification destination management manager according to the request from the management manager. The management manager address registration unit 250 is provided.

The data storage unit 220 is a log data storage unit 2 in which a log ID is added and stored every time a log is generated.
21, a log ID storage unit 222 at the time of log full storing the log ID when the log full notification is performed, a trap interval value storage unit 223 storing the value changed by the trap interval value changing unit 240, and a management manager It has a management manager address storage unit 224 in which the value registered by the address registration unit 250 is stored. The log data storage unit 221 is configured to overwrite (wrap up) the log with the oldest log ID when the number of logs exceeds the maximum number of logs that can be stored.

The log-full notifying unit 210 has the latest log ID of the log data storage unit 221 and the log I at the log-full time of the previous notification stored in the log ID storage unit 222 at the log-full time.
D, trap interval value of trap interval value storage unit 223, and management manager address storage unit 2
It has a log-full determination unit 211 that determines whether or not the log is full by referring to the 24 management manager address.

The above-mentioned management manager of FIG. 7 and FIG.
Based on the configuration of the managed device of
It will be described according to the following flowchart. FIG. 9 is a flowchart showing log acquisition processing on the management manager side and the managed device side.

First, on the side of the management manager, the log acquisition trigger generation unit 101 notifies the log-full notification from the managed device, the notification from the management manager start-up notification unit 102,
Alternatively, when a notification is received from the network failure recovery notification unit 103, a log acquisition trigger is generated (step S6).
1). Then, the log acquisition execution unit 104 requests the managed device to acquire the logs of the log ID (N) and the subsequent logs based on the log ID (N) of the log transferred last time (step S62). Wait for log data reception (step S6)
3).

On the other hand, when the managed device receives the log acquisition request from the management manager (step S64), it substitutes "N" for "S" of the log ID (S) (step S).
65). Log I was the last one transferred in the previous log transfer.
Since it is the log of D (N), the log to be transmitted from now is the log of the next log ID. Therefore, here, the value of "S" is incremented by one (step S6
6), the log data of the log ID is stored in the log data storage unit 2
21 is transmitted to the management manager by the log transmission unit 230 (step S67). At this time, the management manager is waiting for data reception.
When the log data is transmitted from the managed device side, the log acquisition execution unit 104 acquires the log data and records and holds the log data in the hard disk 105 (step S68).

On the managed device side, when the transmission of the log data of a certain log ID is completed, it is judged whether the transmitted log data is the data having the latest log ID (step S69), and if it is not the latest log data. , Step S66
Then, the log data having the next log ID will be transmitted and processed. If the transmitted log data is the latest, the log data end is transmitted to the management manager, and the log acquisition process on the managed device side ends (step S70). Upon receipt of the log data end notification, the management manager side ends the current log acquisition process (step S71). In this step S71,
If the end of log data is not notified, the process returns to step S63 to wait for reception of the next log data.

Here, a specific example will be described.
The log data storage unit 221 of the data storage unit 220 can store, for example, 50 logs, and the trap interval value set in the trap interval value storage unit 223 is 40. It is assumed that the log ID starts from “0” and increases by one each time a log is generated, and that the log ID storage unit 222 at the time of log full initially contains “0”. Further, the hard disk 105 of the management manager has no log ID because the log of this managed device has not been recorded yet.

The logs are accumulated and the log ID is 40.
When the log is generated, the log data storage unit 221 reads 4
Since one piece of log data has been accumulated, the number of accumulated logs becomes larger than the trap interval value. At this point, the value of the log ID storage unit 222 when the log is full is "4.
It is changed to "0", a log full trap is sent to the management manager, and the management manager starts acquisition of log data. At this time, since no log data is recorded on the management manager side, the log acquisition request from the management manager is all log data. Log transmission unit 230 of managed device
Sequentially transmits from the log having the log ID “0” to the management manager, and transmits up to the log having the log ID 40. The sent log is stored in the hard disk of the management manager.

Subsequently, when a log is generated, this time the log having the log ID = 41 is held in the log data storage unit 221. When the log with the log ID = 49 is held and the log data storage unit 221 becomes full, the next log with the log ID = 50 is overwritten and held in the oldest log storage position with the log ID = 0. In this way, log ID = 80
When the log of No. is retained, the number of logs newly accumulated from the previous log full notification becomes equal to the trap interval value of 40, and when the log of the next log ID = 81 occurs,
The value of the log ID storage unit 222 at the time of log full is changed to “81”, and the log full trap is sent to the management manager. Then, the management manager issues a log acquisition request to the managed device side together with the log ID = 40 of the latest log among the logs recorded on the hard disk. On the managed device side, the log having the log ID = 41 next to the notified log ID is sequentially transmitted to the management manager side. When the log with the log ID = 81 is transmitted, the log transfer ends.

Similarly, the next generated log is log I
The log data is sequentially held from D = 82 in the log data storage unit 221, and when the log becomes full, the process of acquiring all the logs in the managed device after the log ID at the previous log full from the management manager is repeated. In addition to the log full notification, the management manager performs the same log acquisition processing as when the log full notification is issued, when the management manager is started up or when the network failure is recovered.

Next, considering the performance of the management manager,
It is considered that the response of the managed device to the log acquisition request of the management manager is early or late. If the response to the log acquisition request from the management manager is fast, it can be recorded in a short time after the log full notification is sent until the management manager records the log on the hard disk, so the trap interval value is set to the maximum number of logs that the device can hold. A close value is good. However, if the response to the log acquisition request from the management manager is slow,
It takes a long time for the manager to record the log on the hard disk after the log full notification is sent.
Therefore, between the log full notification and the recording of the log by the management manager, the untransferred log is overwritten by the newly generated log in the managed device. It is necessary to prevent it from disappearing from the log data storage unit 221 of the management device. In order to avoid such a situation, the management manager can change the trap interval value of the managed device to an optimum value in consideration of the log acquisition response, and the trap interval value is changed according to the flowchart shown in FIG. It

FIG. 10 is a diagram showing another configuration example of the log acquisition method of the managed device. According to the illustrated configuration example, the first management manager 300 and the second management manager 400 are connected to the first to fourth managed devices 600, 700, 800, 900 via the network 500. First management manager 300 and second management manager 40
0 is provided with hard disks 310 and 410 for respectively recording logs, and the first to fourth managed devices 600 to 9 are provided.
00 is the management manager address storage unit 610,
710, 810, 910. Further, the first management manager 300 monitors the free space of the hard disk 310, and when the free space runs out, manages the logs generated in the first to fourth managed devices 600 to 900 by another management manager. It has a log acquisition switching unit 320 that performs the process of transferring to.

Here, the first to fourth managed devices 600
˜900 are managed by the first management manager 300. Therefore, the management manager address storage unit 61 of the first to fourth managed devices 600 to 900.
It is assumed that the addresses of the first management manager 300 are registered in 0, 710, 810, and 910 as the management managers of the log-full notification destination. Therefore, the first
Or, when a log is generated in the fourth managed devices 600 to 900, the log is held in each log data storage unit, and when the log becomes full, the log is transferred to the hard disk 310 of the first management manager 300 and recorded.

When the hard disk 310 for storing logs of the first management manager 300 becomes full, the log acquisition switching unit 320 detects this and shifts the log management to the second management manager 400. At this time, the log of the first managed device 600 is recorded on the hard disk 310 as log I.
A log of D = N is recorded, a log of the second managed device 700 is recorded to a log of log ID = M, a log of the third managed device 800 is recorded to a log of log ID = L, and a fourth
It is assumed that the managed device 900 logs are recorded up to the log ID = K.

The log acquisition switching unit 320 firstly causes the management manager address setting requesting unit to perform the first to fourth operations.
For the managed devices 600 to 900, those management manager address storage units 610, 710, 810, 910
The log-full notification destination set to No. 1 is changed from the first management manager 300 to the second management manager 400, and the second management manager 400 is notified of the start log ID necessary for log acquisition. That is, the hard disk 310
The log ID of the last recorded log recorded in is notified, and the first
Log ID of managed device 600 = N, second managed device 70
0 log ID = M, 3rd managed device 800 log ID =
L and the log ID = K of the fourth managed device 900 are notified.

When a log-full trap occurs on the managed device side, the second management manager 400 recognizes the trap and starts the log acquisition process. In the hard disk 410 of the second management manager 400, the first
The log ID = N + 1 for the managed device 600, the log ID = M + 1 for the second managed device 700, the log ID = L + 1 for the third managed device 800, and the fourth.
For the managed device 900, recording is started from the log of log ID = K + 1.

As a result, even if the log recording area in one management manager becomes full, log recording can be continued by temporarily transferring the log recording to another management manager.

[0039]

As described above, according to the present invention, the log acquisition is acquired from the management manager when the managed device receives the log-full notification, the management manager starts up, or the network failure is recovered. Configured to go to. Therefore, when there is a log full notification of the managed device, even if the management manager cannot recognize this notification, the log will be acquired from the management manager when the log becomes available. Therefore, the log accumulated in the managed device will not be lost by being overwritten without being acquired.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of a log acquisition method of a managed device according to the present invention.

FIG. 2 is a flowchart showing a trap interval value changing process.

FIG. 3 is a flowchart showing a flow of management address setting processing.

FIG. 4 is a flowchart of a determination process of whether to start log acquisition.

FIG. 5 is a flowchart of a log full notification process.

FIG. 6 is a flowchart showing a recovery process from a network failure.

FIG. 7 is a diagram illustrating a specific configuration example of a management manager.

FIG. 8 is a diagram illustrating a specific configuration example of a managed device.

FIG. 9 is a flowchart showing log acquisition processing on the management manager side and the managed device side.

FIG. 10 is a diagram showing another configuration example of the log acquisition method of the managed device.

[Explanation of symbols]

 10 management manager 11 log acquisition timing recognition means 12 log acquisition execution means 13 trap interval setting means 14 management manager address setting means 20 network 30 managed device 31 log full notification means 32 log transmission means 33 trap interval changing means 34 management manager address registration means

Claims (5)

[Claims] 1. In a managed device log acquisition method for acquiring a log of an occurrence inside a managed device connected to a management manager via a network, a log accumulated in the managed device by the management manager. Log acquisition timing recognition means for recognizing the timing for acquiring a log acquisition trigger, and a log accumulated in the managed device in response to the output of the log acquisition trigger by the log acquisition timing recognition means. A log acquisition method for a managed device, comprising: a log acquisition execution unit that collects and stores the log. 2. The log acquisition timing recognizing means receives a log full notification from the managed device indicating that the number of logs generated in the managed device exceeds a predetermined value, or manages the log. When the manager or the network recovers from the state where it cannot receive the notification that the number of logs generated in the managed device exceeds a certain predetermined value, it outputs the log acquisition trigger. It is comprised, It is characterized by the above-mentioned.
Log acquisition method for the managed device described. 3. The number of logs accumulated from the log full notification to the log acquisition time recognition means until the next log full notification, that is, a request for changing the constant value is managed. 2. The managed device log acquisition method according to claim 1, further comprising a trap interval setting means for the manager to perform management on the managed device. 4. The management manager issues a request to the managed device for setting a management manager of the other party who notifies the log full when the number of logs exceeds the value of the trap interval and is newly accumulated. 2. The managed device log acquisition method according to claim 1, further comprising management manager address setting means. 5. In response to a medium for recording and storing a log being filled by a certain management manager, a management manager for log-full notification set in the managed device is preset by the management manager address setting means. 5. The log acquisition switching means for changing to the designated management manager and for notifying the predetermined management manager of the log ID of each managed device which starts recording, further comprising: Log acquisition method for the managed device.