JP2012068729A - Information processor and management device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system capable of promptly detecting a situation in which a packet does not reach a transmission destination, when the packet does not reach the transmission destination due to a failure in a communication pathway.SOLUTION: When a failure occurs, a server device 1 transmits a failure occurrence notification packet for making notification of the failure to a call center device 6 and counts transmission frequency of failure occurrence notification packets. The call center device 6 counts reception frequency of failure occurrence notification packets every time when receiving a failure occurrence notification packet. The server device 1 notifies the call center device 6 of the transmission frequency of failure occurrence notification packets in a predetermined period. The call center device 6 compares the reception frequency counted by itself with the transmission frequency received from the server device 1. When the reception frequency is smaller than the transmission frequency, it is determined that a failure occurrence notification packet does not reach the call center device 6 due to a failure in a communication pathway.

Description

  The present invention relates to a technique for notifying occurrence of a failure to a notification destination such as a call center when a failure occurs in a server device or the like.

  A conventional failure notification method will be described with reference to FIG.

In FIG. 18, reference numeral 100 denotes a server device to be monitored.
Reference numeral 2 denotes a monitoring unit that monitors the occurrence of a failure in the server apparatus 100.
A failure detection unit 21 detects a failure.
Reference numeral 22 denotes a notification notification creation unit that generates a failure occurrence notification packet for reporting the occurrence of a failure.
Reference numeral 23 denotes a notification notification transmission unit that transmits a failure occurrence notification packet.
30 to 3 m are component groups of the server device 100.
Reference numerals 40 to 4m are failure detection signal groups.
Reference numeral 5 denotes a communication line.
Reference numeral 50 denotes a server side router.
Reference numeral 600 denotes a call center device that receives a failure occurrence notification packet.
Reference numeral 60 denotes a center side router.
A control unit 61 performs overall control of the call center device 600.
Reference numeral 62 denotes a notification notification receiving unit that receives a failure occurrence notification packet.
63 is a notification creation unit that analyzes the failure occurrence notification packet and generates a notification message 66 described later.
A notification storage unit 64 stores the notification message 66.
A notification output unit 65 outputs a notification message 66.
Reference numeral 66 denotes a notification message for notifying the details of the failure in the server apparatus 100, for example, an e-mail.
Reference numeral 7 denotes a maintenance center that performs maintenance of the server apparatus 100.
71 is a maintenance worker.
9 is a communication line.

Next, the operation will be described.
Here, a case where a failure occurs in the component 30 of the server apparatus 100 will be described as an example.
When a failure occurs in the component 30, the failure detection signal 40 becomes significant in the server device 100, and the server monitoring unit 2 that detects the failure detection signal 21 generates a failure occurrence notification packet in the notification notification creation unit 22. Then, the information is transmitted to the call center device 600 via the notification notification transmission unit 23.
The failure occurrence notification packet reaches the call center device 600 via the server side router 50, the communication line 5, and the center side router 60.
In the call center device 600, the notification notification receiving unit 62 receives and analyzes the failure occurrence notification packet, and generates a notification message 66 for notifying the content of the failure to the maintenance center 7 near the installation location of the server device 100 where the failure has occurred. 63.
The notification message 66 is a message that can be understood by a person, and is, for example, an e-mail.
In the call center device 600, after the notification message 66 is stored in the notification storage unit 64, the notification output unit 65 transmits it to the maintenance center.
In the maintenance center 7 that has received the notification message, the maintenance staff 71 who carries the replacement parts of the components of the server apparatus 100 goes to the server installation location from the contents of the notification and replaces the failed parts of the server apparatus 100.
In this way, the server apparatus 100 can return to a normal state.

  Further, for example, in Patent Document 1, when a failure notification (A) is received, the notification history DB is checked, and if there is a failure notification (B) from the same customer in the past within a predetermined time, the failure notification (A, B) If the combination is registered in the related notification DB, and this combination is registered in the related notification DB, the failure notification (A) is set as the related notification for the failure notification (B) and the notification is omitted or reference information. As a notification method.

JP 2007-80035 A

In the conventional failure notification method described with reference to FIG. 18 and also in the method of Patent Document 1, for example, when the server-side router 50 is out of order, a failure occurs in the component 30 of the server device 100. Even when the server device 100 generates and transmits a failure occurrence notification packet, the failure notification packet does not reach the call center device 600 because the server-side router 50 has failed, and the failure to the maintenance center 7 occurs. No occurrence notification is made.
Therefore, for example, there is a problem that the server failure state continues until the administrator of the server apparatus 100 notices the server failure and manually notifies the maintenance center or the like, thereby reducing the reliability of the system.

  One of the main objects of the present invention is to solve the above-described problems. Even when the notification does not reach the notification destination due to a failure in the communication path, it is early notice that the notification does not reach the notification destination. The main purpose is to realize a system that can detect the failure.

An information processing apparatus according to the present invention includes:
An event notification generator for generating an event notification for notifying the occurrence of an event when a predetermined event occurs;
An event notification transmitter for transmitting the event notification generated by the event notification generator to a predetermined management device;
Each time an event notification is transmitted by the event notification transmission unit, an event notification transmission number counting unit that counts the number of event notification transmissions,
A transmission frequency notification generating unit for generating a transmission frequency notification for notifying the transmission frequency of the event notification counted by the event notification transmission frequency counting unit at a predetermined interval;
A transmission frequency notification transmission unit configured to transmit the transmission frequency notification generated by the transmission frequency notification generation unit to the management apparatus.

  According to the present invention, the information processing device counts the number of event notification transmissions every time an event notification is transmitted to the management device, and notifies the management device of the counted number of event notification transmissions. By comparing the number of received event notifications with the number of event notification transmissions notified from the information processing device, it is possible to detect early that the event notification has not reached the management device.

FIG. 3 is a diagram showing a system configuration example according to the first and second embodiments. FIG. 3 shows a configuration example of a server apparatus according to the first embodiment. FIG. 3 shows a configuration example of a call center device according to the first embodiment. FIG. 6 is a diagram illustrating a configuration example of a failure occurrence notification packet according to the first embodiment. FIG. 4 is a diagram illustrating a configuration example of a failure occurrence count notification packet according to the first embodiment. FIG. 4 is a diagram illustrating a configuration example of a call center device according to a second embodiment. FIG. 10 is a diagram illustrating a configuration example of a call center device according to a third embodiment. FIG. 4 is a flowchart showing a procedure example of a failure occurrence notification process of the server device according to the first embodiment. FIG. 3 is a flowchart showing an example of a procedure of failure occurrence count notification processing of the server device according to the first embodiment. FIG. 3 is a flowchart showing an example of a procedure for notification-related processing of the call center device according to the first embodiment. FIG. 3 is a flowchart showing a procedure example of a failure occurrence notification process of the call center device according to the first embodiment. FIG. 3 is a flowchart showing a procedure example of failure occurrence frequency notification processing of the call center device according to the first embodiment. The flowchart figure which shows the example of a procedure of the report related process of the call center apparatus which concerns on Embodiment 2 and 3. FIG. FIG. 10 is a flowchart showing a procedure example of a failure occurrence notification process of the call center device according to the third embodiment. FIG. 10 is a flowchart showing a procedure example of failure occurrence frequency notification processing of the call center device according to the third embodiment. FIG. 10 is a flowchart showing a procedure example of a route failure confirmation process of the call center device according to the third embodiment. The figure which shows the hardware structural example of the server apparatus 1 and the call center apparatus 6 which concern on Embodiment 1-3. The figure which shows the system structural example of a prior art.

Embodiment 1 FIG.
FIG. 1 shows a system configuration example according to the present embodiment.

In FIG. 1, the server device 1 is connected to the call center device 6 via a server side router 50, a communication line 5, and a center side router 60.
The call center device 6 is connected to a maintenance center device 70 in the maintenance center 7 via a communication line 9.
As described with reference to FIG. 18, when a failure occurs in a component of the server device 1, a failure occurrence notification packet is transmitted from the server device 1 via the server side router 50, the communication line 5, and the center side router 60. It is transmitted to the call center device 6.
The call center device 6 analyzes the failure occurrence notification packet, generates a notification message 66 for notifying the failure content, and transmits it to the maintenance center device 70.
In the maintenance center 7 that has received the notification message, the maintenance staff 71 carrying the replacement parts of the components of the server apparatus 1 goes to the server installation location from the contents of the notification and replaces the failed parts of the server apparatus 1.
The server device 1 is an example of an information processing device, and the call center device 6 is an example of a management device.

FIG. 2 shows a configuration example of the server apparatus 1 according to the present embodiment.
In FIG. 2, the elements other than the failure notification transmission counter 24, the transmission interval setting unit 25, the transmission interval measurement timer 26, and the request signal 27 are the same as those shown in FIG.
However, the notification notification creation unit 22 and the notification notification transmission unit 23 have functions different from those in FIG.
In the following, the notification notification creation unit 22, the notification notification transmission unit 23, the failure notification transmission counter 24, the transmission interval setting unit 25, the transmission interval measurement timer 26, and the request signal 27 will be described, and description of other elements will be omitted.

In the present embodiment, the notification notification creation unit 22 notifies the occurrence of a failure (occurrence of a failure detection event) when a failure detection event by the failure detection unit 21 (failure detection event) occurs. (Event notification) is generated, and a failure occurrence frequency notification packet (transmission frequency notification) is sent at a predetermined interval to notify a failure occurrence notification packet (event notification) transmission count counted by a failure notification transmission counter 24 described later. Generate.
The notification notification creation unit 22 is an example of an event notification generation unit and a transmission count notification generation unit.

The notification notification transmission unit 23 transmits the failure occurrence notification packet and the failure occurrence frequency notification packet generated by the notification notification creation unit 22 to the call center device 6.
The notification notification transmission unit 23 is an example of an event notification transmission unit and a transmission frequency notification transmission unit.

The failure notification transmission counter 24 counts the number of transmissions of the failure occurrence notification packet every time a failure occurrence notification packet (event notification) is transmitted by the notification notification transmission unit 23.
The failure notification transmission counter 24 is an example of an event notification transmission count counter.

  The transmission interval setting unit 25 sets an interval (period) at which the notification notification creating unit 22 generates a failure occurrence frequency notification packet and the notification notification transmission unit 23 transmits the failure occurrence frequency notification packet in a transmission interval measurement timer 26 described later. To do.

  The transmission interval measurement timer 26 is a timer that outputs a request signal 27 to the notification notification creation unit 22 at intervals (cycles) set by the transmission interval setting unit 25.

FIG. 3 shows a configuration example of the call center device 6 according to the present embodiment.
In FIG. 3, the elements other than the elements in the notification confirmation unit 8 are the same as the elements shown in FIG.
However, the notification notification receiving unit 62, the notification generation unit 63, and the notification output unit 65 have functions different from those in FIG.
Below, the element in the notification notification receiving part 62, the notification production | generation part 63, the notification output part 65, and the notification confirmation part 8 is demonstrated, and description of another element is abbreviate | omitted.

The notification notification receiving unit 62 receives a failure occurrence notification packet (event notification) transmitted from the server device 1 and receives a failure occurrence frequency notification packet transmitted from the server device 1 at a predetermined interval.
As described above, the failure occurrence frequency notification packet is a packet for notifying the number of transmissions of the failure occurrence notification packet counted by the server device 1.
The notification notification receiving unit 62 is an example of an event notification receiving unit and a transmission count notification receiving unit.

The notification notification analysis unit 80 determines whether the packet received by the notification notification reception unit 62 is a failure occurrence notification packet or a failure occurrence frequency notification packet.
If it is a failure occurrence notification packet, the notification notification analysis unit 80 transfers the failure occurrence notification packet to the notification generation unit 63 and notifies the failure notification reception counter 81 that the failure occurrence notification packet has been received.
Further, in the case of the failure occurrence frequency notification packet, the notification notification analysis unit 80 sends the numerical value in the failure occurrence frequency notification packet (the transmission frequency of the failure occurrence notification packet counted by the server device 1) to the failure notification transmission frequency reception unit 82. Output.

The failure report reception counter 81 counts the number of times the failure report packet is received every time a notification that the failure report packet is received from the report notification analysis unit 80.
The failure notification reception counter 81 is an example of an event notification reception count counter.

  The failure notification transmission frequency reception unit 82 receives the numerical value (the number of transmissions of the failure occurrence notification packet counted by the server device 1) in the failure occurrence frequency notification packet from the notification notification analysis unit 80 and outputs it to the comparison unit 83.

When the comparison unit 83 inputs a numerical value in the failure occurrence frequency notification packet from the failure notification transmission frequency reception unit 82 (that is, when the notification notification reception unit 62 receives the failure occurrence frequency notification packet), The numerical value input from the receiving unit 82 (the number of transmissions of the failure occurrence notification packet counted by the server device 1) is compared with the number of receptions counted by the failure notification reception counter 81.
Then, the comparison unit 83 instructs the notification generation unit 63 to generate a warning message that warns of the possibility of occurrence of an abnormality in the communication path when the number of transmissions and the number of receptions do not match as a result of the comparison.

When a failure occurrence notification packet is input from the notification notification analysis unit 80, the notification generation unit 63 generates a notification message 66 for notifying the failure content as in the case of FIG. 18, and also generates a warning message from the comparison unit 83. Generate warning messages when instructions are entered.
The comparison unit 83 is an example of a warning message generation unit.

The notification output unit 65 transmits the notification message 66 generated by the notification generation unit 63 to the maintenance center device 70. When the warning message is generated by the notification generation unit 63, the notification output unit 65 transmits the warning message to the maintenance center device 70. Send to.
The notification output unit 65 is an example of a warning message output unit.

FIG. 4 shows a configuration example of a failure occurrence notification packet transmitted from the server monitoring unit 2 to the call center device 6.
The failure occurrence notification packet includes a transmission destination address portion in which the address of the call center device 6 that is the destination is set, a transmission source address portion in which the address of the server monitoring unit 2 that is the transmission source is set, and a command that indicates a failure notification It consists of a command part in which a code is set and a data part in which a code indicating a failure occurrence location (type) is set.

FIG. 5 shows a configuration example of a failure occurrence frequency notification packet transmitted from the server monitoring unit 2 to the call center device 6.
The failure occurrence frequency notification packet is a transmission destination address portion in which the address of the call center device 6 that is the destination is set, a transmission source address portion in which the address of the server monitoring unit 2 that is the transmission source is set, and a failure occurrence frequency notification. A command part in which a command code indicating the above is set, and a data part in which the number of transmissions of the failure occurrence notification packet transmitted from the server monitoring part 2 to the call center device 6 is set.

Next, the operation will be described with reference to FIGS.
FIG. 8 shows a procedure example of failure occurrence notification processing in which the server device 1 notifies the call center device 6 that a failure has occurred.
FIG. 9 shows a procedure example of the failure frequency notification process in which the server device 1 notifies the call center device of the transmission frequency of the failure occurrence notification packet.
FIG. 10 shows an example of a procedure of notification-related processing that is periodically executed in the call center device 6.
FIG. 11 is a procedure example of failure occurrence notification processing when the call center device 6 according to the present embodiment receives a failure occurrence notification, and shows details of ST210 in FIG.
FIG. 12 is a procedure example of the failure occurrence frequency notification process when the call center device 6 according to the present embodiment receives the failure occurrence frequency notification, and shows details of ST220 in FIG.
In the following description, the case where a failure occurs in the component 30 of the server device 1 will be described as an example.

When a failure occurs in the component 30 of the server device 1 (YES in ST101 in FIG. 8), the failure detection signal 40 becomes significant, and the server monitoring unit 2 that has detected this by the failure detection unit 21 sends a failure occurrence notification packet. Generated by the notification notification creation unit 22 (ST102) (event notification generation processing).
Next, the notification notification transmission unit 23 transmits a failure occurrence notification packet to the call center device 6 (ST103) (event notification transmission processing).
At this time, the value of the failure notification transmission counter 24 is incremented (+1) (ST104) (event notification transmission count counting process).

The failure occurrence notification packet reaches the call center device 6 via the server side router 50, the communication line 5, and the center side router 60.
In the call center device 6, the notification notification receiving unit 62 receives the failure occurrence notification packet (YES in ST201 in FIG. 10) (event notification reception processing), and is analyzed by the notification notification analysis unit 80.
More specifically, in the call center device 6, the notification notification analysis unit 80 extracts the command portion from the packet received by the notification notification reception portion 62 (ST202), analyzes the command portion, and the received packet is a failure occurrence notification packet. It is determined whether there is a failure occurrence count notification packet (ST203).
Here, since the received packet is a failure occurrence notification packet, failure occurrence notification processing (ST210) is performed.

In the failure occurrence notification process (ST210), the failure notification reception counter 81 notifies the failure notification reception unit 81 that the failure occurrence notification packet has been received, and the notification notification analysis portion 80 notifies the failure generation notification to the notification generation unit 63. The packet is forwarded.
Then, when notified that the failure notification packet is received from the notification notification analysis unit 80, the failure notification reception counter 81 increments (+1) the counter value (ST211 in FIG. 11) (event notification reception count processing) ).
Moreover, the notification production | generation part 63 produces | generates the notification message 66 using at least the transmission origin address and data part of a failure generation notification packet (ST212).
Next, the notification storage unit 64 stores the notification message 66 generated by the notification generation unit 63 (ST213 in FIG. 11), and the notification output unit 65 transmits the notification message 66 to the maintenance center device 70 of the maintenance center 7. (ST214).

In the maintenance center 7 that has received the notification message 66, the maintenance staff 71 carrying the replacement parts of the component 30 of the server apparatus 1 goes to the server installation location from the contents of the notification and replaces the failed part of the server apparatus 1.
In this way, the server apparatus 1 can return to a normal state.

Further, while no failure has occurred in the server device 1, the transmission interval measurement timer 26 continues to measure time for the time set by the transmission interval setting unit 25.
When the set time has elapsed and the notification timing of the number of failures has occurred (YES in ST111 in FIG. 9), the transmission interval measurement timer 26 makes the request signal 27 significant.
When the request signal 27 becomes significant, the notification notification creation unit 22 detects that the request signal 27 has become significant, and the notification notification creation unit 22 generates a failure occurrence count notification packet (ST112) (transmission count notification generation processing) ).
Specifically, the notification notification creation unit 22 reads the counter value of the failure notification transmission counter 24 and generates a failure occurrence frequency notification packet in which the counter value is set.
Next, the notification notification transmission unit 23 transmits a failure occurrence frequency notification packet to the call center device 6 (ST113) (transmission frequency notification transmission processing).

The failure occurrence frequency notification packet reaches the call center device 6 via the server side router 50, the communication line 5, and the center side router 60.
In the call center device 6, the notification notification receiving unit 62 receives the failure occurrence number notification packet (YES in ST 201 of FIG. 10) (transmission number notification reception processing), and is analyzed by the notification notification analysis unit 80.
More specifically, in the call center device 6, the notification notification analysis unit 80 extracts the command portion from the packet received by the notification notification reception portion 62 (ST202), analyzes the command portion, and the received packet is a failure occurrence notification packet. It is determined whether there is a failure occurrence count notification packet (ST203 and S204).
Here, since the received packet is a failure occurrence count notification packet, failure occurrence count notification processing (ST220) is performed.

In the failure occurrence frequency notification process (ST220), the notification notification analysis unit 80 notifies the failure notification reception counter 81 that the failure occurrence frequency notification packet has been received, and the notification notification analysis unit 80 notifies the failure notification transmission frequency reception unit 82. The numerical value set in the data part of the failure occurrence frequency notification packet (number of failure occurrences) is output.
The failure notification reception counter 81 outputs the current counter value to the comparison unit 83, and the failure notification transmission count reception unit 82 outputs the numerical value (failure occurrence count) of the data portion of the failure occurrence count notification packet to the comparison unit 83. To do.
When the failure occurrence count notification packet is received, the value of the failure notification reception counter 81 does not change.

The comparison unit 83 compares the numerical value (failure occurrence number) of the data part of the failure occurrence frequency notification packet output from the failure notification transmission frequency reception unit 82 with the counter value output from the failure notification reception counter 81 (FIG. 12). ST221) (comparison processing).
If both values match as a result of the comparison (YES in ST222), all of the failure notification packets from the server monitoring unit 2 have been processed normally, so no new processing is performed. Absent.
On the other hand, when the two values do not match (NO in ST222), the comparison unit 83 notifies the notification generation unit 63 of a possibility that an abnormality has occurred in the communication path or a possibility that an abnormality has occurred. Is generated, and the notification generation unit 63 generates such a notification message (warning message) (ST223) (warning message generation processing).
Next, the notification storage unit 64 stores the warning message generated by the notification generation unit 63 (ST224), and the notification output unit 65 transmits the warning message to the maintenance center device 70 of the maintenance center 7 (ST225) ( Warning message transmission processing).
Then, in preparation for the next comparison, the value of the failure notification transmission count reception unit 82 is set in the failure notification reception counter 81 (ST226).

If any failure occurs in the server device 1 while the server side router 50 is temporarily stopped due to a failure, if the value of the failure notification transmission counter 24 is N before the failure occurs, Although the failure occurrence notification packet does not reach the device 6, since the failure occurrence notification packet is transmitted from the server device 1, the value of the failure notification transmission counter 24 becomes N + 1.
Thereafter, when the server-side router 50 recovers from the failure, a failure notification frequency notification packet in which N + 1 is set in the data portion is transmitted to the call center device 6 when the time just set in the transmission interval measurement timer 26 has elapsed.
In the call center device 6 that has received the failure notification frequency notification packet, the content N of the failure notification reception counter 81 that has counted the number of failure notifications received so far, and the numerical value N + 1 extracted from the failure notification frequency notification packet Are compared by the comparison unit 83.
In this case, since the output indicates a mismatch, a warning that warns of the possibility of a failure occurring on the communication path (server side router 50, communication line 5, center side router 60) of the failure occurrence notification. A message is transmitted to the maintenance center device 70.
Then, in preparation for the next comparison, the numerical value N + 1 extracted from the failure notification frequency notification packet is set in the failure notification reception counter 81.

Receiving the warning message, the maintenance center 7 informs the administrator of the server apparatus 1 that there is a possibility that an abnormality has occurred in the communication path from the contents of the notification, and what is the failure that has not been reported as a failure occurrence notification packet. Therefore, the maintenance staff 71 goes to the server installation location, analyzes the log and the like, identifies the failure location, and replaces the parts, so that the server device 1 is restored to the normal state.
As described above, even when there is an abnormality in the failure occurrence notification path, the failure occurrence in the server device 1 can be reliably reported, and the time until recovery can be prevented from being prolonged, so that the reliability is high. A system can be constructed.

  In the above description, an example in which a communication path for delivering a failure occurrence notification packet to the call center device 6 and a communication route for delivering a failure occurrence frequency notification packet to the call center device 6 are the same is described. The communication path for delivering the notification packet to the call center apparatus 6 and the communication path for delivering the failure occurrence frequency notification packet to the call center apparatus 6 may be different paths.

Embodiment 2. FIG.
In the system according to the first embodiment, when the communication path for delivering the failure occurrence notification packet to the call center apparatus 6 and the communication path for delivering the failure occurrence frequency notification packet to the call center apparatus 6 are the same, the communication path Does not recover from the failure, the failure occurrence frequency notification packet does not reach the call center device 6.
For this reason, when it takes a long time to recover the communication path, it takes a long time for the call center device 6 to confirm the presence of the failure notification packet that has not been delivered.
In the present embodiment, a call center device 6 capable of coping with such a situation and confirming the presence of a failure occurrence notification packet that has not arrived at an early stage will be described.

FIG. 6 shows a configuration example of the call center device 6 according to the present embodiment.
Since elements other than the call center apparatus 6 are the same as those shown in the first embodiment, description of elements other than the call center apparatus 6 is omitted.

In FIG. 6, a notification reception interval measurement timer 84 and a reception interval setting unit 85 are added as compared with the configuration of FIG.
The reception interval setting unit 85 sets a time interval longer than the transmission interval setting unit 25.
The notification reception interval measurement timer 84 sets a value set in the reception interval setting unit 85 when receiving the failure occurrence count notification packet, and then counts down the set value as time passes.
That is, the notification reception interval measurement timer 84 measures the elapsed time since the notification notification receiving unit 62 received the failure occurrence frequency notification packet, and the elapsed time exceeds the value set by the reception interval setting unit 85. In addition, the notification generation unit 63 is notified that the elapsed time has exceeded the set value of the reception interval setting unit 85.
The notification reception interval measurement timer 84 is an example of an elapsed time measurement unit.
In the present embodiment, the notification generation unit 63 generates a warning message when notified from the notification reception interval measurement timer 84 that the elapsed time has exceeded the set value of the reception interval setting unit 85.

Next, the operation will be described.
The operation in the server device 1 is as shown in FIGS.
That is, while no failure has occurred in the server device 1, the failure occurrence frequency notification packet is transmitted from the server monitoring unit 2 to the server side router 50, the communication line 5, and the time interval set in the transmission interval setting unit 25. It is transmitted to the call center device 6 via the center side router 60.

The operation of the call center device 6 according to the present embodiment is as shown in FIG.
In FIG. 13, compared with FIG. 10, S205 and ST230 are added, and other processes are the same as those of FIG.
Hereinafter, S205 and ST230 will be described.
In FIG. 13, ST300, ST400, and ST500 are also described, but ST300, ST400, and ST500 will be described in Embodiment 3.

In the present embodiment, when the notification notification analysis unit 80 determines that the packet received by the notification notification reception unit 62 is a failure occurrence frequency notification packet, the value set in the reception interval setting unit 85 is the notification reception interval. The notification reception interval measurement timer 84 is set in the measurement timer 84 and starts to count down the set value.
That is, the notification reception interval measurement timer 84 measures the elapsed time from the reception time of the failure occurrence frequency notification packet.
If no failure occurs in the communication path, the server monitoring unit 2 generates a failure at the time interval set in the transmission interval setting unit 25 of the server device 1 before the value of the notification reception interval measurement timer 84 becomes zero. Send a count notification packet.
For this reason, if a failure does not occur in the communication path, the notification notification receiving unit 62 receives the failure occurrence count notification packet before the value of the notification reception interval measurement timer 84 becomes zero, and the notification notification analysis unit 80 Confirm that the occurrence frequency notification packet has been received.
When the notification notification analysis unit 80 confirms reception of the failure occurrence count notification packet, the notification reception interval measurement timer 84 is set again in the time set in the reception interval setting unit 85, and then the countdown is started again.
In the end, if the communication path is normal, the notification reception interval resetting → countdown → notification reception interval resetting → countdown is repeated, and the notification reception interval measurement timer 84 does not become zero.
Here, if a failure occurs in the server side router 50, the notification reception interval measurement timer 84 counts down because the failure occurrence frequency notification packet from the server monitoring unit 2 is not received, and the notification reception interval measurement timer 84 The value becomes zero.
Explaining in accordance with FIG. 13, the notification reception interval measurement timer 84 performs a failure path confirmation process (ST230) every unit time (ST205), advances the countdown, and when the counter value becomes zero, the notification generation unit 63 generates a warning message, and the notification output unit 65 transmits the warning message.
Here, the failure path confirmation process (ST230) will be described using an example in which the unit time of ST205 is 1 second and the reception interval set by the reception interval setting unit 85 in the notification reception interval measurement timer 84 is 1000 seconds.

In ST205, a path failure confirmation process (ST230) is started every second, and the notification reception interval measurement timer 84 decrements the counter value. If the counter value is not zero, the path failure confirmation process (ST230) is terminated. Wait for the next second to elapse.
On the other hand, if the counter value becomes zero as a result of decrementing the counter value (if the time during which no failure occurrence notification packet is received exceeds the threshold value of 1000 seconds), the notification reception interval measurement timer 84 notifies the notification generator 63. Notify that the counter value has become zero.
The notification generation unit 63 receives a notification from the notification reception interval measurement timer 84, generates a warning message that warns of the possibility of abnormality in the communication path, and after being stored in the notification output unit 65, the notification output unit 65 A warning message is transmitted to the maintenance center device 70.

  Upon receiving the warning message, the maintenance center 7 informs the administrator of the server apparatus 1 that there is an abnormality in the failure notification path from the content of the notification, confirms the failure location of the communication path, and is not notified as a failure occurrence notification packet. In order to confirm that there is no failure, the maintenance staff 71 goes to the server installation location, identifies the failure of the server side router 50, replaces it, and confirms that there is no failure in the server device 1 itself. Will return the system to normal.

  In this way, even when there is an abnormality in the failure occurrence notification path, it is possible to prevent the failure occurrence notification from reaching the call center when a failure occurs in the server device, and to build a highly reliable system be able to.

Embodiment 3 FIG.
In the present embodiment, a call center device 6 corresponding to a plurality of server devices 1 and a plurality of maintenance centers 7 will be described.

FIG. 7 shows a configuration example of the call center device 6 according to the present embodiment.
Although not shown, the call center device 6 according to the present embodiment is connected to a plurality of server devices 1 via a network.
Further, the call center device 6 according to the present embodiment is connected to a plurality of maintenance centers 7 through a network.

FIG. 7 shows an example in which the notification confirmation unit 8 shown in FIG. 6 is realized as software.
That is, in the server group monitoring information storage unit 800, a storage block is provided for each server device, and data for realizing the notification confirmation unit 8 shown in FIG. 6 is stored in each storage block.
The server 1 correspondence information block 810 is a storage block for the server device 1 with the server number 1, and the server n correspondence information block 8n0 is a storage block for the server device 1 with the server number n.
Hereinafter, the configuration in the storage block will be described using the server 1 correspondence information block 810 as an example.

The failure notification reception counter 811 operates in the same manner as the failure notification reception counter 81 shown in FIG. 6, and counts the number of receptions of the failure occurrence notification packet.
The failure notification transmission frequency reception unit 812 operates in the same manner as the failure notification transmission frequency reception unit 82 shown in FIG. 6, and stores the numerical value (failure occurrence frequency) of the data portion of the failure occurrence frequency notification packet from the notification notification analysis unit 80. To do.
The notification reception interval measurement timer 814 operates in the same manner as the notification reception interval measurement timer 84 shown in FIG. 6, and measures the elapsed time after receiving the failure occurrence frequency notification packet.
The reception interval setting unit 815 operates in the same manner as the reception interval setting unit 85 illustrated in FIG. 6 and sets the measurement time of the notification reception interval measurement timer 814.
The address setting unit 816 stores the communication address of the server device 1 with the server number 1.
The server 1 neighboring maintenance center address 817 stores the communication address of the maintenance center device 70 of the maintenance center 7 installed in the vicinity of the server device 1 with the server number 1.
The server 1 validity flag 818 indicates that the server 1 correspondence information block 810 has been registered and is valid.

In the present embodiment, it is assumed that the operation of the comparison unit 83 shown in FIG.
That is, in the present embodiment, for example, in the case of the server device 1 with the server number 1, the control unit 61 compares the counter value of the failure notification reception counter 811 with the value of the failure notification transmission count reception unit 812.
The other elements of the call center device 6 are the same as those in FIG.

Next, the operation will be described.
The notification when a failure occurs in each server device 1 and the notification of the number of occurrences of failure at normal times are performed in the same manner as in the first embodiment.
Here, with reference to FIGS. 13 to 16, the operation in the call center device 6 that has received the notification and notification will be mainly described.
FIG. 13 shows an example of a procedure of notification-related processing that is periodically executed in the call center device 6 according to the present embodiment.
FIG. 14 is a procedure example of the failure occurrence notification process when the call center device 6 according to the present embodiment receives the failure occurrence notification, and shows details of ST300 in FIG.
FIG. 15 is a procedure example of the failure occurrence frequency notification process when the call center device 6 according to the present embodiment receives the failure occurrence frequency notification, and shows details of ST400 in FIG.
FIG. 16 is a procedure example of the route failure confirmation process of the call center device 6 according to the present embodiment, and an operation for periodically checking whether a notification reception timeout due to a communication route failure has occurred in all server devices. Indicates.
FIG. 16 shows details of ST500 in FIG.

When the failure notification packet from server device 1 is received by notification notification receiver 62 (YES in ST201 in FIG. 13), notification notification analyzer 80 extracts the command part of the packet (ST202), analyzes the packet, It is confirmed that the packet is an occurrence notification packet (YES in ST203).
For this reason, failure occurrence notification processing (ST300) (FIG. 14) is performed.

In the failure occurrence notification process (ST300), the control unit 61 reads out the transmission source address of the failure occurrence notification packet (ST301 in FIG. 14), and in the order of storage block arrangement in the server group monitoring information storage unit 800, the address setting unit 816. .. 8n6 is read (ST302 and ST303), and the address of the read address setting unit is compared with the transmission source address of the faulty communication packet (ST304).
If they do not match (NO in ST304), the address setting unit of the next storage block is read (ST309, ST310, ST303) and compared with the source address of the failure notification packet (ST304).

On the other hand, in the case of YES in ST304, this is a notification from the server device 1 corresponding to the storage block in which the address setting unit is included, and the control unit 61 selects the storage block.
In the following description, it is assumed that the server 1 correspondence information block 810 has been selected.
The control unit 61 increments (+1) the contents of the failure notification reception counter 811 and addresses the maintenance center 7 in the vicinity of the server device 1 with the server number 1 stored in the server 1 neighboring maintenance center address 817 (maintenance). The address of the center device 70) is notified to the notification generation unit 63 as the transmission destination of the notification message 66 (ST305).
In addition, control unit 61 notifies notification generation unit 63 of a code indicating the location of the failure occurrence in the data portion of the failure occurrence notification packet (ST306).
In addition, if there is other data necessary for the notification generation unit 63 to generate the notification message 66, the control unit 61 notifies the notification generation unit 63 of the data (ST307).
Next, after the notification generation unit 63 generates the notification message 66 and stores it in the notification storage unit 64, the notification output unit 65 transmits the notification message 66 (ST308).
The transmission destination of the notification message 66 is the maintenance center device 70 of the maintenance center 7 in the vicinity of the server device 1 with the server number 1 extracted in ST305.

  Thereafter, a maintenance staff is dispatched from the maintenance center 7 that has received the notification of the occurrence of the failure to the installation location of the server device 1, the location of the failure is replaced, and the system returns to normal.

If any failure occurs in the server device 1 while the server side router 50 is temporarily stopped due to a failure, if the value of the failure notification transmission counter 24 is N before the failure occurs, Although the failure occurrence notification packet does not reach the device 6, since the failure occurrence notification packet is transmitted from the server device 1, the value of the failure notification transmission counter 24 becomes N + 1.
Thereafter, when the server-side router 50 recovers from the failure, a failure notification frequency notification packet in which N + 1 is set in the data portion is transmitted to the call center device 6 when the time just set in the transmission interval measurement timer 26 has elapsed.

In the call center device 6 that has received the failure notification count notification packet, when the failure notification packet from the server device 1 is received by the notification notification receiving unit 62 (YES in ST201 of FIG. 13), the notification notification analysis unit 80 uses the packet command. (ST202), the packet is analyzed, and it is confirmed that it is a failure occurrence frequency notification packet (NO in ST203, YES in ST204).
Therefore, the failure occurrence frequency notification process (ST400) (FIG. 15) is performed.

In the failure occurrence frequency notification process (ST400), the control unit 61 reads the transmission source address of the failure occurrence frequency notification packet (ST401 in FIG. 15) and addresses setting units in the order of storage blocks in the server group monitoring information storage unit 800. 816... 8n6 are read (ST402, ST403), and the read address setting unit address is compared with the source address of the failure occurrence frequency notification packet (ST404).
If they do not match (NO in ST404), the address setting unit of the next storage block is read (ST414, ST415, ST403) and compared with the source address of the failure occurrence frequency notification packet (ST404).

On the other hand, in the case of YES in ST404, it is a notification from the server device 1 corresponding to the storage block including the address setting unit, and the control unit 61 selects the storage block.
In the following description, it is assumed that the server 1 correspondence information block 810 has been selected.
Next, control unit 61 sets the value of the reception interval stored in reception interval setting unit 815 in notification reception interval measurement timer 814, and starts the countdown of notification reception interval measurement timer 814 (ST405).
Next, control unit 61 reads the number of failure occurrences stored in the data part of the failure occurrence count notification packet, and stores the read failure occurrence count in failure report transmission count reception unit 812 (ST406).
Then, control unit 61 reads the counter value from failure notification reception counter 811 (ST407), reads the number of failure occurrences from failure notification transmission frequency reception unit 812, and compares the two (ST408).
If the content of failure notification reception counter 811 is equal to the content of failure notification transmission count reception unit 812 (YES in ST408), control unit 61 ends the process.
On the other hand, if the value of the failure notification reception counter 811 is N and the value of the failure notification transmission count reception unit 812 is N + 1, there is a mismatch (NO in ST408), and the control unit 61 determines that the server 1 neighbor maintenance center address 817 The address of the maintenance center 7 in the vicinity of the server apparatus 1 with the server number 1 stored in (the address of the maintenance center apparatus 70) is notified to the notification generation unit 63 as a warning message transmission destination (ST409).
Further, control unit 61 notifies message generation unit 63 of a message indicating a communication path failure (ST410).
In addition, if there is other data necessary for the notification generation unit 63 to generate the warning message, the control unit 61 notifies the notification generation unit 63 of the data (ST411).
Next, after the notification generation unit 63 generates a warning message and stores it in the notification storage unit 64, the notification output unit 65 transmits the warning message (ST412).
The transmission destination of the warning message is the maintenance center device 70 of the maintenance center 7 in the vicinity of the server device 1 with the server number 1 extracted in ST409.
Then, in preparation for the next comparison, the value N + 1 of the failure notification transmission count reception unit 812 is set in the failure notification reception counter 811 (ST413).

Thereafter, in the maintenance center 7 that has received the notification, the administrator of the server device 1 indicates that there is a failure in the failure notification path from the content of the notification and that there is a possibility that the server device 1 with the server number 1 has a failure. In order to confirm the failure that was not reported as a failure occurrence notification packet, the maintenance staff 71 goes to the server installation location, analyzes the log, etc., identifies the failure location, and replaces the parts. The server is restored to normal status.
Further, the server side router 50 is also replaced, and the system returns to a normal state.

Even when no failure has occurred in the server device 1, the content of the notification reception interval measurement timer in the storage block corresponding to each server stored in the server group monitoring information storage unit 800 of the call center device 6 is constant. Will count down.
When a failure occurrence frequency notification packet is received from a certain server device 1, it is analyzed by the notification notification analysis unit 80, and the content of the reception interval setting unit in the corresponding storage block is set in the notification reception interval measurement timer.
If there is no failure in the communication path, the notification reception interval measurement timer corresponding to each server device repeats counting down → resetting the contents of the receiving interval setting unit → counting down → resetting the contents of the receiving interval setting unit.
Here, if a failure occurs in the server-side router 50, the failure reception frequency notification packet from the server monitoring unit 2 is not received, so the countdown of the notification reception interval measurement timer proceeds and the value becomes zero.
Describing according to FIG. 13, the control unit 61 performs the failure path confirmation process (ST500) every unit time (ST205), advances the countdown of the notification reception interval measurement timer, and when the counter value becomes zero, The notification generation unit 63 generates a warning message, and the notification output unit 65 transmits the warning message.
Here, in the example where the unit time of ST205 is 1 second commonly for all server devices, and the reception interval set in the notification reception interval measurement timer by the reception interval setting unit is 1000 seconds commonly for all server devices, the failure path confirmation processing (ST500) will be described.

A route failure confirmation process (ST500) is started every second by ST205.
In the route failure confirmation process (ST500), the control unit 61 reads the server 1 valid flag 818... 8n8 in the order of storage block arrangement in the server group monitoring information storage unit 800 (ST501 and ST502 in FIG. 16) and makes the flag valid. The counter value of the notification reception interval measurement timer 814... 8n4 of the memory block in question is decremented (−1) (ST503), and if the counter value is not zero (NO in ST504), the next memory block The valid flag is confirmed (ST509, ST510, ST502).
When processing is completed for all storage blocks (YES in ST509), control unit 61 ends path failure confirmation processing (ST500) and waits for the next one second to elapse.
On the other hand, if the counter value becomes zero as a result of decrementing the counter value (if the time during which no failure occurrence notification packet is received exceeds the threshold value of 1000 seconds) (YES in ST504), the control unit 61 proceeds to S505. Proceed with the process.
Here, when the counter value of the notification reception interval measurement timer 814 of the server 1 correspondence information block 810 becomes zero, that is, the failure occurrence frequency notification packet from the server device 1 of the server number 1 has not been received for 1000 seconds or more. A case will be described as an example.
Control unit 61 notifies notification generation unit 63 of the address of maintenance center 7 in the vicinity of server device 1 stored in server 1 neighboring maintenance center address 817 (ST505).
Further, control unit 61 notifies message generation unit 63 of a message indicating a communication path failure (ST506).
In addition, if there is other data necessary for notification generation unit 63 to generate a warning message, control unit 61 notifies notification generation unit 63 of the data (ST507).
Next, after the notification generation unit 63 generates a warning message and stores it in the notification storage unit 64, the notification output unit 65 transmits the warning message (ST508).
The destination of the warning message is the maintenance center device 70 of the maintenance center 7 in the vicinity of the server device 1 with the server number 1 extracted in ST505.
In parallel with the transmission of the warning message by the notification generation unit 63 and the transmission of the warning message by the notification output unit 65, the control unit 61 proceeds with the processing after ST509, and when the processing is completed for all the storage blocks (YES in ST509). ), The control unit 61 ends the route failure confirmation process (ST500) and waits for the next one second to elapse.

  When the warning message is transmitted by the notification output unit 65, the maintenance center 7 that has received the notification informs the administrator of the server apparatus 1 that there is an abnormality in the failure notification path from the content of the notification, and also indicates the location of the failure in the communication path. In order to check whether there is a failure that has not been reported, the maintenance staff 71 goes to the server installation location, identifies the failure of the server side router 50, replaces it, and the server device 1 itself has a failure. Confirm that there is no error, and the system will return to normal.

  As described above, even when an abnormality occurs in the server device or the failure occurrence notification path for a plurality of server devices, the occurrence of the failure can be detected, and in some cases, when the failure occurs in the server device, the failure occurrence notification is sent to the call center. Therefore, it is possible to construct a highly reliable system.

As described above, in the first to third embodiments,
The server monitoring unit that monitors the occurrence of a failure in the server device is provided with a failure notification transmission counter, and the call center device that receives the failure notification is provided with a failure notification reception counter for each server device to detect that a failure has occurred in the server device. The monitoring unit increments the trouble report transmission counter by +1 every time it reports the occurrence of a trouble, and the call center device side increments the trouble report reception counter by +1 each time a trouble report is received.
The server monitoring unit periodically transmits the content of the failure notification transmission counter to the call center device, and the call center device compares the content of the failure notification transmission counter transmitted from the server monitoring unit with the content of the failure notification reception counter. ,
If the call center device detects that the two do not match, it can detect that a failure has occurred in the communication path between the monitored server device and the call center device or that there is an error in the settings, and can notify the maintenance center. A system that can quickly detect and deal with the occurrence of a failure such as a communication path interruption and improve the reliability of the system has been described.

In the above description, an example in which the occurrence of a failure in the server device 1 is notified to the call center device 6 has been described. However, the content to be notified is not limited to the occurrence of a failure.
In a system configuration in which an event notification for notifying the occurrence of a predetermined event in the server device 1 is transmitted to the call center device 6, the server device 1 counts the number of event notification transmissions, and the call center device 6 counts the number of event notification receptions. The server device 1 may notify the number of event notification transmissions at predetermined intervals.
Further, the device that transmits and receives the event notification is not limited to the server device 1 and the call center device 6.

Finally, hardware configuration examples of the server device 1 and the call center device 6 described in the first to third embodiments will be described.
FIG. 17 is a diagram illustrating an example of hardware resources of the server device 1 and the call center device 6 described in the first to third embodiments.
The configuration in FIG. 17 is merely an example of the hardware configuration of the server device 1 and the call center device 6, and the hardware configuration of the server device 1 and the call center device 6 is not limited to the configuration described in FIG. Other configurations may be used.

In FIG. 17, the server device 1 and the call center device 6 include a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program.
The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an SSD (Solid State Drive), an optical disk device, or a memory card (registered trademark) read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
The notification storage unit 64 or the server group monitoring information storage unit 800 described in the first to third embodiments is realized by the RAM 914, the magnetic disk device 920, and the like.
A communication board 915, a keyboard 902, a mouse 903, a scanner device 907, an FDD 904, and the like are examples of input devices.
The communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.

As shown in FIG. 1, the communication board 915 is connected to a network.
For example, the communication board 915 may be connected to a LAN (local area network), the Internet, a WAN (wide area network), a SAN (storage area network), or the like.

The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
The programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.

The RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
The RAM 914 stores various data necessary for processing by the CPU 911.

The ROM 913 stores a BIOS (Basic Input Output System) program, and the magnetic disk device 920 stores a boot program.
When the server device 1 and the call center device 6 are activated, the BIOS program in the ROM 913 and the boot program in the magnetic disk device 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.

  The program group 923 stores a program that executes a function described as “˜unit” (except for the notification accumulation unit 64 and the server group monitoring information storage unit 800) in the description of the first to third embodiments. Has been. The program is read and executed by the CPU 911.

In the file group 924, in the description of the first to third embodiments, “determination of”, “calculation of”, “comparison of”, “reading of”, “update of”, and “setting of” are set. ”,“ Registration of ”,“ selection of ”,“ input of ”,“ output of ”, etc., information, data, signal values, variable values, and parameters indicating the results of the processing are“ It is stored as each item of "~ file" and "~ database".
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory.
Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit.
The read information, data, signal value, variable value, and parameter are used for CPU operations such as extraction, search, reference, comparison, calculation, calculation, processing, editing, output, printing, and display.
Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
In addition, the arrows in the flowcharts described in Embodiments 1 to 3 mainly indicate input and output of data and signals.
Data and signal values are recorded on a recording medium such as a memory of the RAM 914, a flexible disk of the FDD 904, a compact disk of the CDD 905, a magnetic disk of the magnetic disk device 920, other optical disks, a mini disk, and a DVD.
Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

In addition, what is described as “˜unit” in the description of the first to third embodiments may be “˜circuit”, “˜device”, “˜device”, and “˜step”, It may be “˜procedure” or “˜processing”.
That is, the present invention can be grasped as a method invention by the steps, procedures, and processes shown in the flowcharts described in the first to third embodiments.
Further, what is described as “˜unit” may be realized by firmware stored in the ROM 913.
Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware.
Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD.
The program is read by the CPU 911 and executed by the CPU 911.
That is, the program causes the computer to function as “to part” in the first to third embodiments. Alternatively, the computer executes the procedure and method of “to part” in the first to third embodiments.

As described above, the server device 1 and the call center device 6 shown in the first to third embodiments have a display as an output device such as a CPU as a processing device, a memory as a storage device, a magnetic disk, a keyboard as an input device, a mouse, a communication board, and the like. A computer including a device, a communication board, and the like.
Then, as described above, the functions indicated as “˜units” are realized using these processing devices, storage devices, input devices, and output devices.

  DESCRIPTION OF SYMBOLS 1 Server apparatus, 2 Server monitoring part, 5 Communication line, 6 Call center apparatus, 7 Maintenance center, 8 Notification confirmation part, 9 Communication line, 21 Failure detection part, 22 Notification notification preparation part, 23 Notification notification transmission part, 24 Fault notification Transmission counter, 25 Transmission interval setting unit, 26 Transmission interval measurement timer, 27 Request signal, 50 Server side router, 60 Center side router, 61 Control unit, 62 Notification notification reception unit, 63 Notification generation unit, 64 Notification storage unit, 65 Notification output unit, 66 Notification message, 70 Maintenance center device, 71 Maintenance staff, 80 Report notification analysis unit, 81 Fault report reception counter, 82 Fault report transmission count reception unit, 83 Comparison unit, 84 Notification reception interval measurement timer, 85 reception Interval setting unit, 800 server group monitoring information storage unit, 810 server 1 correspondence information block, 811 Reception counter, 812 fault notification transmission number receiving section, 814 notifies reception interval measuring timer, 815 reception interval setting unit, 816 an address setting unit, 817 the server 1 close maintenance center address, 818 server 1 valid flag.

Claims (12)

An event notification generator for generating an event notification for notifying the occurrence of an event when a predetermined event occurs;
An event notification transmitter for transmitting the event notification generated by the event notification generator to a predetermined management device;
Each time an event notification is transmitted by the event notification transmission unit, an event notification transmission number counting unit that counts the number of event notification transmissions,
A transmission frequency notification generating unit for generating a transmission frequency notification for notifying the transmission frequency of the event notification counted by the event notification transmission frequency counting unit at a predetermined interval;
An information processing apparatus comprising: a transmission frequency notification transmission unit that transmits the transmission frequency notification generated by the transmission frequency notification generation unit to the management device. The information processing apparatus includes:
A fault detection unit that detects a fault in a predetermined monitoring target and generates a fault detection event;
The event notification generation unit
The information processing apparatus according to claim 1, wherein an event notification for notifying a failure detection event is generated when a failure detection event occurs by the failure detection unit. An event notification receiver for receiving an event notification for notifying the occurrence of a predetermined event in the information processing device from the information processing device;
Each time an event notification is received by the event notification receiving unit, an event notification reception number counting unit that counts the number of receptions of event notifications,
A transmission frequency notification receiving unit that receives a transmission frequency notification that is transmitted from the information processing device at a predetermined interval and that is notified of the transmission frequency of the event notification counted by the information processing device;
When the transmission number notification is received by the transmission number notification receiving unit, the event notification transmission number notified by the received transmission number notification and the event notification counted by the event notification reception number counting unit A comparison unit that compares the number of receptions;
As a result of the comparison by the comparison unit, when the number of event notification transmissions and the number of event notification receptions do not match, a warning message generation unit that generates a warning message that warns the possibility of occurrence of an abnormality,
A management apparatus comprising: a warning message output unit that outputs a warning message generated by the warning message generation unit. The management device further includes:
The transmission count notification receiving unit measures an elapsed time after receiving the transmission count notification from the information processing apparatus, and notifies that the elapsed time exceeds the threshold when the elapsed time exceeds a predetermined threshold. Has an elapsed time measurement unit,
The warning message generator
The management apparatus according to claim 3, wherein a warning message is generated when the elapsed time measurement unit notifies that the elapsed time has exceeded a threshold value. The warning message generator
The management apparatus according to claim 3 or 4, wherein a warning message is generated to warn of a possibility of occurrence of an abnormality in a communication path with the information processing apparatus. The warning message output unit
6. The management apparatus according to claim 3, wherein a warning message is output to an apparatus provided in a maintenance center that performs maintenance of the information processing apparatus. The management device
Connected to multiple information processing devices,
The event notification receiver
Each information processing device receives event notifications,
The event notification reception number counting unit
For each information processing device, count the number of event notifications received,
The transmission number notification receiving unit,
For each information processing device, receive a notification of the number of transmissions,
The comparison unit includes:
For each information processing device, compare the number of event notifications sent and the number of event notifications received,
The warning message generator
As a result of the comparison by the comparison unit, when there is an information processing device whose event notification transmission count and event notification reception count do not match, a warning message is generated to warn of the possibility of an abnormality in the information processing device. The management apparatus according to any one of claims 3 to 6, wherein: The management device further includes:
For each information processing device, if there is an information processing device that measures the elapsed time since the transmission number notification receiving unit received the transmission number notification and the elapsed time exceeds a predetermined threshold, the information processing device It has an elapsed time measurement unit that notifies that the elapsed time has exceeded the threshold,
The warning message generator
The management apparatus according to claim 7, wherein a warning message is generated for an information processing apparatus notified from the elapsed time measurement unit that the elapsed time has exceeded a threshold value. The management device further includes:
8. A warning message output unit that outputs a warning message to an apparatus provided in a maintenance center that performs maintenance of the information processing apparatus for which the warning message has been generated by the warning message generation unit. Or the management apparatus of 8. The event notification receiver
The management apparatus according to claim 3, wherein an event notification for notifying a failure detection event that has occurred in the information processing apparatus is received. An event notification generation process for generating an event notification for notifying the occurrence of an event when a predetermined event occurs;
An event notification transmission process for transmitting the event notification generated by the event notification generation process to a predetermined management device;
Each time an event notification is transmitted by the event notification transmission process, an event notification transmission number counting process for counting the number of event notification transmissions;
A transmission frequency notification generation process for generating a transmission frequency notification for notifying the transmission frequency of the event notification counted by the event notification transmission frequency counting process at a predetermined interval;
A program that causes a computer to execute a transmission frequency notification transmission process of transmitting a transmission frequency notification generated by the transmission frequency notification generation process to the management apparatus. An event notification receiving process for receiving an event notification for notifying the occurrence of a predetermined event in the information processing device from the information processing device;
Each time an event notification is received by the event notification reception process, an event notification reception count process for counting the number of event notifications received,
A transmission count notification reception process for receiving a transmission count notification to be transmitted from the information processing apparatus at a predetermined interval to be notified of the transmission count of the event notification counted by the information processing apparatus;
When the transmission count notification is received by the transmission count notification reception process, the event notification transmission count notified by the received transmission count notification and the event notification count counted by the event notification reception count counting process A comparison process for comparing the number of receptions;
As a result of the comparison by the comparison process, when the event notification transmission count and the event notification reception count do not match, a warning message generation processing that generates a warning message that warns the possibility of occurrence of an abnormality,
A program for causing a computer to execute warning message output processing for outputting a warning message generated by the warning message generation processing.

Images