JP6224985B2 - Notification device and notification method - Google Patents

Description

  The present invention relates to a notification device and a notification method.

  Conventionally, as a technology to realize software redundancy cluster and increase system availability, by making software redundant, even if a failure occurs in the working hardware where the software operates, the hardware that operates the software A technique for continuing the operation of the system by switching is known (for example, see Non-Patent Document 1).

  In such a technology, in order to detect a failure of the active hardware with the standby hardware, the high-availability cluster software that configures the same cluster sends and receives alive monitoring packets to each other. Monitors software for failures.

  In addition, a software operation monitoring agent is arranged at each node in the cluster, and the operation state of the software on the node is monitored and notified to the external device, so that the operation time of the software is managed by the external device.

“Development of OSS middle Heartbeat to improve service availability”, [online], [October 11, 2013 search], Internet <http://www.ntt.co.jp/journal/0903/files/jn20090346 .pdf> “Crane -Management Solution from NTT R & D-”, [online], [searched on October 11, 2013], Internet <http://www.oss.ecl.ntt.co.jp/ossc/download/Crane. pdf>

  However, the conventional technique has a problem that the operating time of the software cannot be properly notified to the external device. In other words, if a failure occurs in the active hardware, it is not guaranteed that the hardware is broken and the operation of the monitoring agent and the operating status can be notified externally. There was a case that could not be.

  As a method for confirming the operating status of software, for example, there is a technique in which a monitoring system other than a high availability cluster measures the operating time of a logical resource and monitors the operating status of software (see Non-Patent Document 2). However, in accordance with the scale of the system for providing the service, the cost required for monitoring the operation status of the software by the monitoring system increases. In addition, since the method of monitoring the operating status differs for each software, the monitoring system needs to change the monitoring method for each software to be redundant.

  Therefore, an object of the present invention is to appropriately notify the external device of the operating time of the software without reducing the monitoring method for each software and to reduce the monitoring cost.

  In order to solve the above-described problems and achieve the object, the disclosed notification device relates to the software in a cluster system that activates software running on the active node in the standby node when the active node fails. A notification device that notifies an external device of information, and when a failure of the active node is detected by the standby node, a first time that is a time when the standby node detects a failure of the active node A failure time detection unit to detect; a startup time detection unit that detects a second time that is a time when the activation of the software is completed when the activation of the software is completed in the standby node; and the first time And a notification unit that notifies the external device of the second time.

  The disclosed notification method is executed by a notification device that notifies the external device of information related to the software in a cluster system that activates software running on the active node on the standby node when the active node fails. And a failure time detection for detecting a first time when the standby node detects a failure of the active node when a failure of the active node is detected by the standby node. A start time detecting step of detecting a second time that is a time when the start of the software is completed when the start of the software is completed in the standby node, the first time, and the second time And a notification step of notifying an external device.

  The notification device and the notification method disclosed in the present application can appropriately notify the operating time of software to an external device without changing the monitoring method for each software, and can reduce the monitoring cost.

FIG. 1 is a diagram illustrating an example of a configuration of a system according to the first embodiment. FIG. 2 is a diagram illustrating an example of the configuration of the active node and the standby node in the system according to the first embodiment. FIG. 3 is a block diagram showing the configuration of the software operating time notification device according to the first embodiment. FIG. 4 is a diagram illustrating an example of information stored in the failure detection information storage unit according to the first embodiment. FIG. 5 is a diagram illustrating an example of information stored in the software activation time storage unit according to the first embodiment. FIG. 6 is a diagram illustrating an overview of notification processing in the software operating time notification device according to the first embodiment. FIG. 7 is a flowchart for explaining a flow of notification processing in the software operating time notification device according to the first embodiment. FIG. 8 is a diagram illustrating a computer that executes a notification program.

  Hereinafter, embodiments of a notification device and a notification method according to the present invention will be described in detail with reference to the drawings. In addition, this invention is not limited by this embodiment.

[First embodiment]
In the following embodiments, the configuration of the system according to the first embodiment, the configuration of the software operating time notification device, and the flow of processing by the analysis device will be described in order, and finally the effects of the first embodiment will be described.

[System configuration]
First, an example of a system configuration according to the first embodiment will be described. FIG. 1 is a diagram illustrating an example of a configuration of a system according to the first embodiment. As shown in FIG. 1, in the system according to the first embodiment, a plurality of software clusters 50 </ b> A and 50 </ b> B that make software redundant to increase availability, and an external notification destination monitoring system that monitors software running in the software cluster 50 40, and the software clusters 50A, 50B and the external notification destination monitoring system 40 are connected via a network 60.

  FIG. 1 illustrates the case where there are two software clusters 50A and 50B and one external notification destination monitoring system 40. However, the number of software clusters and the number of external notification destination monitoring systems are not limited to this. It is not limited. Further, when the software clusters 50A and 50B are described without particular distinction, they are referred to as software clusters 50.

  The software clusters 50A and 50B each have an active node 50a and a standby node 50b. The active node 50a and the standby node 50b include software operating time notification devices 10a and 10b. Here, the active node 50a and the software operating time notification device 10a may be configured with a common hardware resource or may be configured with separate hardware resources. The same applies to the standby node 50b and the software operating time notification device 10b.

  The active node 50a operates software (hereinafter referred to as operation time notification target software 20a). Further, when detecting a failure of the active node 50a, the standby node 50b activates the operation time notification target software 20a and operates the operation time notification target software 20a instead of the failed active node 50a. The software operating time notification devices 10a and 10b will be referred to as the software operating time notification device 10 when they are described without particular distinction.

  When the failure of the active node 50a is detected by the standby node 50b, the software operating time notification device 10b detects the time when the standby node 50b detects the failure of the active node 50a. Further, when the activation of software is completed in the standby node 50b, the software operating time notification device 10b detects the time when the activation of the software is completed.

  Then, the software operating time notification device 10b notifies the external notification destination monitoring system 40 of the time when the standby node 50b detects the failure of the active node 50a and the time when the activation of the software is completed in the standby node 50b. .

  Next, the configuration of the active node 50a and the standby node 50b will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of the configuration of the active node and the standby node in the system according to the first embodiment. In the following example, a case where the external notification destination monitoring system 40 and the software cluster 50 have a one-to-one relationship will be described as an example. However, the present invention is not limited to this and may be one-to-multiple or multi-to-multiple. For example, a plurality of software clusters 50 may exist for one external notification destination monitoring system 40.

  The software cluster 50 is a unit of a server managed by the high availability cluster software 30. The active node 50a on which the operation time notification target software 20a, which is the redundancy target software, operates, and the operation time notification target software 20a operates. Instead, when the failure occurs in the active node 50a, the standby node 50b is the switching destination of the operating time notification target software.

  The active node 50a and the standby node 50b can each have a plurality of nodes in the software cluster 50. The software cluster 50 can have a plurality of software clusters 50 with respect to the external notification destination monitoring system 40.

  In the active node 50a, the operating time notification target software 20a and the high availability cluster software 30a are operating. The operating time notification target software 20a is software that is operating on the active node 50a, and is software that is to be monitored for operating status.

  The high availability cluster software 30b is running on the standby node 50b. When a failure occurs in the active node 50a, the operation time notification target software 20b is activated in the standby node 50b, and the operation time notification target software 20b is operated instead of the active node 50a.

  The high availability cluster software 30a, 30b is existing software used for creating a high availability cluster. The high availability cluster software 30a and 30b monitor the hardware on which the software operates and the operating state of the software, and confirm whether there is a failure in the hardware and software.

  In addition, the high-availability cluster software 30a and 30b belonging to the same cluster periodically send and receive alive monitoring packets to check whether software operating on other hardware has failed, whether other hardware has failed, high availability The cluster software 30a and 30b themselves monitor each other for failures.

  The operating time notification target software 20a is software to be made redundant, and is the target software whose operating time is notified to the external notification destination monitoring system 40 by the software operating time notification device 10b of the present invention.

[Configuration of Software Operation Time Notification Device]
Next, the configuration of the software operating time notification device according to the first embodiment will be described with reference to FIG. FIG. 3 is a block diagram showing the configuration of the software operating time notification device according to the first embodiment. As illustrated in FIG. 3, the software operating time notification device 10 includes a communication processing unit 11, a storage unit 12, and a control unit 13.

  The communication processing unit 11 controls communication regarding various information exchanged with the connected external notification destination monitoring system 40. For example, the communication processing unit 11 transmits the time when the standby node 50b detects the failure of the active node 50a and the time when the activation of the software is completed in the standby node 50b to the external notification destination monitoring system 40.

  As shown in FIG. 3, the storage unit 12 includes a failure time storage unit 12a and a startup time storage unit 12b. The storage unit 12 is, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk.

  The failure time storage unit 12a stores the time when the standby node 50b detects a failure of the active node 50a. For example, as illustrated in FIG. 4, the failure time storage unit 12a includes a “node ID” that uniquely identifies the failed active node 50a, and a time when the standby node 50b detects a failure of the active node 50a. A certain “failure detection time” is stored in association with each other. FIG. 4 is a diagram illustrating an example of information stored in the failure detection information storage unit according to the first embodiment.

  For example, the failure time storage unit 12a stores a node ID “1” and a failure detection time “2013/10/10 10:22” in association with each other. .

  The activation time storage unit 12b stores the time when the activation of the software is completed by the standby node 50b. For example, as illustrated in FIG. 5, the activation time storage unit 12b includes a “software ID” that uniquely identifies the operation time notification target software 20 activated by the standby node 50b, and software activation by the standby node 50b. Is stored in association with the “start-up completion time” that is the time at which is completed. FIG. 5 is a diagram illustrating an example of information stored in the software activation time storage unit according to the first embodiment.

  Referring to the example of FIG. 5, for example, the activation time storage unit 12b stores “A” that is a software ID and “2013/10/10 13:10” that is an activation completion time in association with each other. .

  Returning to FIG. 3, the control unit 13 includes a failure time detection unit 13a, a startup time detection unit 13b, and a notification unit 13c. Here, the controller 13 is an electronic circuit such as a CPU (Central Processing Unit) or MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

  When the failure of the active node 50a is detected by the standby node 50b, the failure time detector 13a detects the time when the standby node 50b detects the failure of the active node 50a. Specifically, when the failure time detection unit 13a detects a time when the standby node 50b detects a failure of the active node 50a, the failure time detection unit 13a stores the time in the failure time storage unit 12a.

  Further, the failure time detection unit 13a, when the high availability cluster software 30b of the standby node 50b detects a failure of the active node 50a using a life / death monitoring packet also called a heartbeat packet, the standby node 50b Detects the time when the failure of the active node 50a is detected.

  Here, a method will be described in which the high availability cluster software 30b of the standby node 50b detects a failure of the active node 50a using the alive monitoring packet. In the following description, the hardware of the active node 50a before the occurrence of the failure is described as hardware A, and the hardware of the standby node 50b is described as hardware B. In addition, as a method for the high availability cluster software 30b of the standby node 50b to detect a failure of the active node node 50a using the alive monitoring packet, a method in which a failure is detected by hardware other than the failed hardware and a failure There is a method of detecting a failure of its own hardware by the active node 50a itself.

  First, an example of a method for detecting a failure by hardware other than the failed hardware will be described. The high availability cluster software 30b periodically transmits alive monitoring packets (hereinafter referred to as “heartbeat packets” as appropriate) to other high availability cluster software 30a belonging to the same cluster at regular intervals.

  When the high-availability cluster software 30a receives the heartbeat packet, it returns a monitoring result related to the hardware and software on which it operates. Here, when the hardware A receives the heartbeat packet, the result of the software state monitoring and the result of the hardware A state monitoring are included in the heartbeat packet and a response is returned to the hardware B. Even when the hardware B receives the heartbeat packet, the hardware B returns a response to the hardware A status monitoring result as described above.

  When there is no response to the heartbeat packet transmitted by the high availability cluster software 30b, or when the response includes failure information, the standby node 50b determines the hardware of the active node 50a. The wear A detects that a failure has occurred.

  Next, an example of a method for detecting a failure of the own hardware by the failed active node 50a itself will be described. As a method of detecting a failure of the own hardware by the failed active node 50a itself, there are a failure detection method by software and a failure detection method by hardware.

  For example, as a failure detection method by software, access to redundancy target software, such as confirmation of response by HTTP or confirmation of connection of database, confirms that the software is operating, and sends an appropriate response If it cannot be obtained, it is judged as a failure.

  Moreover, as a failure detection method by hardware, monitoring by hardware such as icmp is performed to check whether the hardware is operating, and when there is no response, a failure is determined.

  As described above, when the failure of the own hardware is detected by the failed active node 50a itself, the high availability cluster software 30a transmits the heartbeat packet transmitted to other hardware or the heartbeat packet from other hardware. Is used to notify the other high availability cluster software 30b in the same cluster of the failure.

  Further, when detecting a hardware or software failure, the high availability cluster software 30b notifies the hardware of information indicating that the failure recorded as a log has been detected. Here, the failure time detection unit 13a detects the time when the standby node 50b detects the failure of the active node 50a when a log indicating that the active node 50a has failed is recorded. That is, the time when the high availability cluster software 30 detects the failure is recorded in the failure time report storage unit 12a when information indicating that the failure is detected by the high availability cluster software 30b is recorded as a log.

  When the activation of the operation time notification target software 20b is completed in the standby node 50b, the activation time detection unit 13b detects the time when the activation of the operation time notification target software 20b is completed. Specifically, when the activation time detection unit 13b detects the time when the activation of the operating time notification target software 20b is completed, the activation time detection unit 13b stores the time in the activation time storage unit 12b.

  For example, when the activation time detection unit 13b detects the activation completion of the operation time notification target software 20b, the activation time detection unit 13b stores the activation time of the operation time notification target software 20 in the activation time storage unit 12a.

  The notification unit 13c notifies the external notification destination monitoring system 40 of the time detected by the failure time detection unit 13a and the time detected by the activation time detection unit 13b. For example, the notification unit 13c requests the communication processing unit 11 to perform notification to the external notification destination monitoring system 40, and the standby node 50b detects a failure of the active node 50a via the communication processing unit 11. The external notification destination monitoring system 40 is notified of the time and the time when the activation of the software is completed in the standby node 50b.

  Here, referring to FIG. 6, when a failure occurs in the hardware of the active node 50a in the software cluster 50, the time when the standby node 50b detects the failure of the active node 50a, and the standby node 50b The overall flow of notification processing for notifying the external notification destination monitoring system 40 of the time when the activation of the software is completed will be described. FIG. 6 is a diagram illustrating an overview of notification processing in the software operating time notification device according to the first embodiment.

  For example, as illustrated in FIG. 6, when a failure occurs in the operation time notification target software 20a, as described above, the high availability cluster software 30b detects the failure of the operation time notification target software 20a from the heartbeat packet. To do. Then, when the failure of the active node 50a is detected by the standby node 50b, the failure time detector 13a detects the time when the standby node 50b detects the failure of the active node 50a.

  Subsequently, the standby node 50b activates the operation time notification target software 20b. When the activation of the operating time notification target software 20b is completed in the standby node 50b, the activation time detection unit 13b detects the time when the activation of the operation time notification target software 20b is completed. Thereafter, the notification unit 13c of the software operating time notification device 10b notifies the external notification destination monitoring system 40 of the time detected by the failure time detection unit 13a and the time detected by the activation time detection unit 13b.

[Processing by software operating time notification device]
Next, with reference to FIG. 7, a flow from detection of a failure of the operation time notification target software 20 by the high availability cluster software 30 to execution of notification to the external notification destination monitoring system 40 by the software operation time notification device 10 will be described. . FIG. 7 is a flowchart for explaining a flow of notification processing in the software operating time notification device according to the first embodiment.

  As shown in FIG. 7, when the high availability cluster software 30b of the standby node 50b detects a failure of the operation time notification target software 20 in the cluster (Yes in step S101), a failure time detection unit of the software operation time notification device 10 13a detects the time when the high availability cluster software 30 of the standby node 50b detects the failure of the active node 50a, and records the time in the failure time storage unit 12a (step S102).

  For example, the failure time detection unit 13a detects the time when the standby node 50b detects a failure of the active node 50a when a log indicating that the active node 50a has failed is recorded. That is, the time when the high availability cluster software 30b detects the failure is recorded in the failure time report storage unit 12a when the information indicating that the failure is detected by the high availability cluster software 30b is recorded as a log.

  Then, the standby node 50b starts activation of the operating time notification target software 20, which is monitoring target software, and monitoring of the activation time by the activation time detection unit 13b (step S103). Subsequently, the activation time detection unit 13b monitors a process operating in the node and determines whether activation of the operation time notification target software 20 is detected (step S104).

  As a result, when the activation time detection unit 13b detects activation of the operation time notification target software 20 (Yes in Step S104), the activation time of the monitoring target software is recorded in the activation time storage unit 12b (Step S105). Thereafter, the notification unit 13c transmits the failure time when the high availability cluster software 30b detects the failure and the activation time of the operation time notification target software 20 to the external notification destination monitoring system 40 (step S106), and the software operation time notification The notification process by the device 10 ends.

  In the description of the above-described series of processing flow, the case where the operation time notification target software 20 is started in the own node in the standby node 50b has been described. However, the operation time notification target software 20 is started in the other node. Sometimes it is done.

  In such a case, for example, when the high availability cluster software 30 detects the activation of the operation time notification target software 20 in another standby node 50b, the detected information is notified to the node using a log or the like. Then, the activation time detection unit 13b detects the activation of the operation time notification target software 20 in another node, and instructs the activation time detection unit 13b to end the monitoring of the operation time notification target software 20. Thereafter, the notification process by the software operating time notification device 10 is terminated.

[Effect of the first embodiment]
As described above, the software operating time notification device 10 according to the first embodiment is the same as the software operating time notification device 10 when the failure of the active node 50a is detected by the standby node 50b. When the time when the node 50b detects the failure of the active node 50a is detected and the activation of the operation time notification target software 20 is completed in the standby node 50b, the time when the activation of the operation time notification target software 20 is completed To detect. Then, the software operating time notification device 10 notifies the external notification destination monitoring system 40 of the time when the standby node 50b detects the failure of the active node 50a and the time when the activation of the software is completed in the standby node 50b. . Accordingly, it is possible to appropriately notify the external device of the operation time of the software and to reduce the monitoring cost without changing the monitoring method for each software.

  In addition, since the software operation time notification device 10 notifies the operation time of the operation time notification target software 20 to the external notification destination monitoring system 40, the operation time notification target software is switched without depending on the function of the external notification destination monitoring system 40. It is possible to notify the time required for.

  In addition, since the software operating time notification device 10 operating in the standby node 50b notifies the external notification destination monitoring system 40, even if a failure occurs in the communication function of the active node 50a, the external notification destination monitoring system 40 operates. The operating time of the time notification target software 20 can be notified.

  In addition, when a failure occurs in the active node 50a, the software operating time notification device 10 operating in the standby node 50b to which the operating time notification target software 20 is switched is notified to the external notification destination monitoring system 40. Even if the number of time notification target software 20 increases, the monitoring cost does not increase, and the monitoring cost can be reduced.

[System configuration, etc.]
Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the failure time detection unit 13a and the activation time detection unit 13b may be integrated. Further, all or any part of each processing function performed in each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

  In addition, among the processes described in the present embodiment, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

[program]
Moreover, it is also possible to create a program in which the processing executed by the software operating time notification device 10 described in the above embodiment is described in a language that can be executed by a computer. For example, it is possible to create a notification program in which the processing executed by the software operating time notification device 10 according to the first embodiment is described in a language that can be executed by a computer. In this case, when the computer executes the notification program, the same effect as in the above embodiment can be obtained. Furthermore, the same processing as in the first embodiment may be realized by recording such a notification program on a computer-readable recording medium, and recording the notification program recorded on the recording medium and causing the computer to read and execute the notification program. Good. Hereinafter, an example of a computer that executes a notification program that realizes the same function as the software operating time notification device 10 illustrated in FIG. 3 will be described.

  FIG. 8 is a diagram illustrating a computer 1000 that executes a notification program. As illustrated in FIG. 8, the computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1031 as illustrated in FIG. The disk drive interface 1040 is connected to the disk drive 1041 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1041. The serial port interface 1050 is connected to, for example, a mouse 1051 and a keyboard 1052 as illustrated in FIG. The video adapter 1060 is connected to a display 1061, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 8, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the above notification program is stored in, for example, the hard disk drive 1031 as a program module in which a command to be executed by the computer 1000 is described.

  The various data described in the above embodiment is stored as program data, for example, in the memory 1010 or the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1031 to the RAM 1012 as necessary, and executes various processing procedures.

  Note that the program module 1093 and the program data 1094 related to the notification program are not limited to being stored in the hard disk drive 1031, but may be stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive or the like. Good. Alternatively, the program module 1093 and the program data 1094 related to the notification program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and via the network interface 1070. May be read by the CPU 1020.

10, 10a, 10b Software operating time notification device 11 Communication processing unit 12 Storage unit 12a Failure time storage unit 12b Startup time storage unit 13 Control unit 13a Failure time detection unit 13b Startup time detection unit 13c Notification unit 13 Storage unit 13a Failure time storage Unit 13b Startup time storage unit 20, 20a, 20b Operation time notification target software 30, 30a, 30b High availability cluster software 40 External notification destination monitoring system

Claims (6)

A notification device included in the standby node that notifies the external device of information related to the software in a cluster system that activates software running on the active node on the standby node when the active node fails. ,
When the failure of the active node is detected by the standby node, the log indicating that the active node has failed is recorded by the high availability cluster software of the standby node. the time recorded, and the failure time detecting unit for detecting a first time is a time at which該待machine system node detects a failure of the active system node,
After the first time is detected by the failure time detection unit, the process that operates in the standby node is monitored, the activation of the software in the standby node is detected, and the activation of the software in the standby node A start time detecting unit for detecting a second time that is a time when the start of the software is completed,
A notification unit for notifying an external device of the first time and the second time;
A notification device comprising: A failure time storage unit for storing the first time;
A startup time storage unit for storing the second time,
When the failure time detection unit detects the first time, the failure time detection unit stores the first time in the failure time storage unit,
The activation time detection unit, when detecting the second time, stores the second time in the activation time storage unit,
The notification device according to claim 1, wherein the notification unit notifies an external device of a first time stored in the failure time storage unit and a second time stored in the activation time storage unit. . 3. The notification according to claim 1, wherein the activation time detection unit detects the first time when the standby node detects a failure of the active node using an alive packet. 4. apparatus. In the cluster system that activates the software running on the active node in the standby node when the active node fails, it is executed by the notification device of the standby node that notifies the external device of information related to the software. Notification method,
When the failure of the active node is detected by the standby node, the log indicating that the active node has failed is recorded by the high availability cluster software of the standby node. the time recorded, and the failure time detection step of detecting a first time is a time at which該待machine system node detects a failure of the active system node,
After the first time is detected by the failure time detection step, the process that operates in the standby node is monitored, the activation of the software in the standby node is detected, and the activation of the software in the standby node A start time detecting step of detecting a second time that is a time when the start of the software is completed,
A notification step of notifying the external device of the first time and the second time;
The notification method characterized by including. In the failure time detection step, when the first time is detected, the first time is stored in the failure time storage unit,
In the activation time detecting step, when the second time is detected, the second time is stored in an activation time storage unit,
5. The notification method according to claim 4 , wherein the notifying step notifies an external device of a first time stored in the failure time storage unit and a second time stored in the activation time storage unit. . 6. The notification method according to claim 4, wherein the activation time detecting step detects the first time when the standby node detects a failure of the active node using a life / death packet. .

Images