JP6958925B2 - Fault notification devices, systems, methods and programs - Google Patents

Description

The present invention relates to fault notification devices, systems, methods and programs, and in particular to fault notification devices, systems, methods and programs for remote maintenance.

In the field of computer fault monitoring, remote maintenance has been mainly used so far. Patent Document 1 discloses a technique for notifying an external remote maintenance system of a failure that occurs between the power-on of a system and the start-up of an application by a network interface. The technique according to Patent Document 1 acquires system log information for investigating the cause of a failure at the same time as a failure occurs, and notifies the remote maintenance management server by e-mail.

Japanese Unexamined Patent Publication No. 2001-325124

However, in Patent Document 1, it is necessary to always connect the remote maintenance system managed by an external maintenance company that is not the operator of the target system in operation to the system in operation, which raises a security concern for the operator. .. On the other hand, even if the operator tries to perform maintenance on behalf of the maintenance company, high expertise is required for the maintenance work of the target system, so we decided to give the operator the same access authority as the maintenance worker. There is also concern about.

The present disclosure has been made to solve such problems, and provides a failure notification device, system, method, and program for realizing failure notification of a target system in remote monitoring while ensuring security. The purpose is to do.

The failure notification device according to the first aspect of the present disclosure is
A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
An input / output restriction unit that limits input / output by the second input / output unit in advance,
An acquisition unit that acquires failure information related to a failure detected by the monitored device and the operating state of the OS at the time of the detection from the monitored device.
With
The input / output limiting unit is
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit is used to output the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit is used to send the second failure notification information based on the failure information to the terminal. Output.

The failure notification system according to the second aspect of the present disclosure is
Monitored devices running the OS (Operating System) and
With the terminal
A failure notification device connected to the terminal via a communication line,
With
The monitored device is
When a failure is detected by the self-diagnosis of the monitored device, it is provided with a self-diagnosis unit that collects the failure information related to the failure and the operating state of the OS at the time of the detection and notifies the failure notification device.
The failure notification device is
With respect to the first input / output data with the OS, the first input / output unit that inputs / outputs with the terminal and
Regarding the second input / output data related to the control of the monitored device by the failure notification device, the second input / output unit that inputs / outputs to / from the terminal, and the second input / output unit.
An acquisition unit that acquires the failure information and the operating state from the self-diagnosis unit, and
An input / output restriction unit that limits input / output by the second input / output unit in advance,
With
The input / output limiting unit is
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit is used to output the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit is used to send the second failure notification information based on the failure information to the terminal. Output.

The failure notification method according to the third aspect of the present disclosure is
A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
The failure notification device equipped with
Limiting the input / output by the second input / output unit,
The failure information regarding the failure detected by the monitored device and the operating state of the OS at the time of the detection are acquired from the monitored device.
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit outputs first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit outputs second failure notification information based on the failure information to the terminal. ..

The failure notification program according to the fourth aspect of the present disclosure is
A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
To a computer equipped with
The process of limiting the input / output by the second input / output unit and
A process of acquiring the failure information related to the failure detected by the monitored device and the operating state of the OS at the time of the detection from the monitored device.
A process of determining whether the OS is running or stopped based on the operating state,
When the OS is operating, the first input / output unit outputs the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the process of releasing the restriction of the second input / output unit and the process of releasing the restriction.
After the release, the second input / output unit outputs the second failure notification information based on the failure information to the terminal.
To execute.

According to the present disclosure, it is possible to provide a failure notification device, system, method and program for realizing failure notification of a target system in remote monitoring while ensuring security.

It is a block diagram which shows the whole structure of the trouble notification system which concerns on Embodiment 1. It is a flowchart which shows the flow of the trouble notification method which concerns on Embodiment 1. It is a block diagram which shows the structure of the trouble notification system which concerns on Embodiment 2 of this invention. It is a block diagram which shows the internal structure of the main body system apparatus and SVP apparatus which concerns on Embodiment 2. It is a block diagram which shows the internal structure of the SVP apparatus and the operator system which concerns on Embodiment 2. It is a sequence diagram which shows the flow of the trouble notification processing by DGP which concerns on Embodiment 2. It is a flowchart which shows the flow of the trouble notification processing in the SVP apparatus which concerns on Embodiment 2.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals, and duplicate explanations are omitted as necessary for the sake of clarity of explanation.

<Embodiment 1>
FIG. 1 is a block diagram showing an overall configuration of the failure notification system 1000 according to the first embodiment. The failure notification system 1000 includes a monitoring target device 10, a failure notification device 20, and a terminal 30. The monitored device 10 and the failure notification device 20 are connected by a communication line or the like. The failure notification device 20 and the terminal 30 are connected via a communication line. The communication line includes a public line, a network such as the Internet, and the like.

The terminal 30 is an information processing device operated by the person in charge of operation of the failure notification system 1000 to remotely monitor the monitored device 10. The terminal 30 includes a general input device and an output device (display device, screen) as a configuration (not shown). In addition, the terminal 30 operates a terminal emulator to input / output data transmitted / received to / from the failure notification device 20 via a communication line. For example, the terminal 30 displays (outputs) on the screen the data received from the failure notification device 20 via the communication line. Further, the terminal 30 transmits (outputs) the data input from the input device by the operator to the failure notification device 20 via the communication line.

The monitoring target device 10 is an information processing device to be monitored by the failure notification system 1000, and may be two or more computers. Further, the monitored device 10 is operated by the OS (Operating System) 11 and includes a self-diagnosis unit 12. The self-diagnosis unit 12 is a functional block that performs self-diagnosis for each configuration in the monitored device 10 including the OS 11. Since a known technique can be used for the self-diagnosis process, detailed description thereof will be omitted. The self-diagnosis unit 12 is, for example, a DGP (DiaGnostic Processor), but is not limited thereto. When a failure is detected by the self-diagnosis of the monitored device 10, the self-diagnosis unit 12 collects the failure information related to the failure and the operating state of the OS 11 at the time of the detection, and notifies the failure notification device 20. Here, the "operating state" is information indicating whether the OS 11 is operating or stopped. Further, the operating state may be information indicating whether or not the OS 11 is operating.

The failure notification device 20 is an information processing device that monitors and controls the monitored device 10 and notifies the terminal 30 when a failure of the monitored device 10 is detected. The failure notification device 20 is, for example, an SVP (SerVice Processor), but is not limited thereto. The failure notification device 20 includes a first input / output unit 21, a second input / output unit 22, an input / output restriction unit 23, and an acquisition unit 24.

The first input / output unit 21 inputs / outputs the first input / output data to / from the OS 11 via a communication line with the terminal 30. The first input / output data is, for example, console data for the OS such as a message output from the OS 11, screen data, or a command input to the OS 11 from a terminal 30 or the like. Further, the first input / output data includes the first failure notification information described later.

The second input / output unit 22 inputs / outputs the second input / output data related to the control of the monitored device 10 by the own device (fault notification device 20) to / from the terminal 30 via the communication line. The second input / output data includes the control command of the monitored device 10 input from the terminal 30 or the like to the failure notification device 20, the output data from the monitored device 10 as the execution result of the control command, and the like. Console data. The second input / output data may include, for example, control commands for operating the configuration of the monitored device 10 and the change of the operating speed. Further, the second input / output data includes the second failure notification information described later. Here, the first input / output unit 21 and the second input / output unit 22 transmit / receive (input / output) console data to / from the terminal emulator of the terminal 30 via a communication line.

The input / output restriction unit 23 limits the input / output by the second input / output unit 22 and releases the restriction. When the input / output is restricted, the second input / output unit 22 cannot input / output the second input / output data to / from the terminal 30. Here, the input / output limiting unit 23 shall limit the input / output by the second input / output unit 22 in advance at the start of fault monitoring.

The acquisition unit 24 acquires the failure information related to the failure detected by the monitored device 10 (self-diagnosis unit 12) and the operating state of the OS 11 at the time of the detection from the monitored device 10 (self-diagnosis unit 12). do.

Here, the input / output restriction unit 23 determines whether the OS 11 is operating or stopped based on the operating state acquired by the acquisition unit 24. Then, when the OS 11 is operating, the input / output restriction unit 23 uses the first input / output unit 21 to output the first failure notification information based on the failure information to the terminal 30. Further, the input / output limiting unit 23 releases the restriction of the second input / output unit 22 when the OS 11 is stopped, and uses the second input / output unit 22 to perform a second failure based on the failure information. Output the notification information to the terminal. Here, the first failure notification information may include detailed information on the failure detected by the OS 11. Further, the second failure notification information may be at least notifying the operator that there is a failure.

FIG. 2 is a flowchart showing the flow of the failure notification method according to the first embodiment. First, the input / output limiting unit 23 limits the input / output by the second input / output unit 22 (S1). Next, the acquisition unit 24 acquires the failure information regarding the failure detected by the monitored device 10 and the operating state of the OS 11 at the time of the detection from the monitored device 10 (S2).

Then, the input / output restriction unit 23 determines whether the OS 11 is operating or stopped based on the operating state acquired in step S2 (S3). When the OS 11 is in operation, the input / output restriction unit 23 outputs the first failure notification information based on the failure information to the terminal 30 via the communication line by the first input / output unit 21 (S4). Further, when the OS 11 is stopped, the input / output restriction unit 23 releases the restriction of the second input / output unit 22 (S5). Then, the input / output restriction unit 23 outputs the second failure notification information based on the failure information to the terminal 30 via the communication line by the second input / output unit 22 (S6).

As described above, in the present embodiment, the failure notification device 20 is provided with two types of input / output means (first input / output unit 21 and second input / output unit 22) for performing data communication with the terminal 30. ing. Here, the first input / output unit 21 mediates the input / output between the OS 11 running on the monitored device 10 and the terminal 30. Therefore, it is easy for the person in charge of operation of the terminal 30 to operate and to grasp the output contents from the OS 11. Therefore, remote monitoring can be performed smoothly. In addition, security can be ensured by assigning individual access privileges to the login account on OS11 for each person in charge of operation. On the other hand, the second input / output unit 22 mediates the input / output between the failure notification device 20 and the terminal 30, and the failure notification device 20 may perform various controls on the entire monitored device 10. can. Therefore, the person in charge of operation of the terminal 30 can also perform highly specialized operations such as changing the configuration of the monitored device 10 via the second input / output unit 22. Therefore, if the access to the monitored device 10 from the terminal 30 via the second input / output unit 22 is normally permitted, there is a concern that there will be many effects when an operation error is made. Therefore, in the first embodiment, security is usually ensured by limiting the input / output by the second input / output unit 22.

On top of that, in the remote monitoring of the monitored device 10, since the failure can be detected to some extent by the OS 11, it is conceivable that the OS 11 notifies the terminal 30 of the failure. However, when a failure related to OS 11 occurs and OS 11 is stopped, there is a limit to the failure notification by OS 11. For example, detailed failure information when the OS 11 is stopped cannot be notified by the OS 11 itself, and further, a failure of another configuration that occurs secondarily in the monitored device 10 while the OS 11 is stopped cannot be notified.

Therefore, in the present embodiment, the failure information notified by the self-diagnosis unit 12 or the like in the monitored device 10 and the operating state of the OS 11 are used, and when the operating state indicates that the OS is stopped, it is temporary. The restriction of the second input / output unit 22 is released, and the notification based on the failure information is performed. As a result, the person in charge of operation of the terminal 30 can make an inquiry to the maintenance company as needed from the failure notification information, so that the maintenance company can respond promptly. From the above, according to the present embodiment, it is possible to realize failure notification of the target system in remote monitoring while ensuring security.

The failure notification device 20 includes a processor, a memory, and a storage device as a configuration (not shown). Further, the storage device stores a computer program in which the processing of the failure notification method according to the present embodiment is implemented. Then, the processor reads the computer program from the storage device into the memory and executes the computer program. As a result, the processor realizes the functions of the first input / output unit 21, the second input / output unit 22, the input / output limiting unit 23, and the acquisition unit 24 described above.

Alternatively, the first input / output unit 21, the second input / output unit 22, the input / output limiting unit 23, and the acquisition unit 24 may be realized by dedicated hardware. Further, a part or all of each component may be realized by a general-purpose or dedicated circuitry, a processor, or a combination thereof. These may be composed of a single chip or may be composed of a plurality of chips connected via a bus. A part or all of each component may be realized by a combination of the above-mentioned circuit or the like and a program. Further, as a processor, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (field-programmable gate array), or the like can be used.

<Embodiment 2>
Here, the problems to be solved by the present disclosure will be described in detail again.
Until now, remote maintenance has mainly been used for computer fault monitoring systems. Here, "remote maintenance" is performed using automatic notification and remote diagnosis. In the "automatic notification", first, when a failure occurs in the main body system device, the built-in diagnostic control processor (for example, DGP) detects the failure and notifies the service processor (for example, SVP) to that effect. Then, the SVP logs to a fixed disk and reports the failure content to the maintenance center system via the public line.

In the maintenance center system that receives the automatic report, specialized maintenance personnel constantly monitor the failure, quickly identify the cause of the failure and the remedy when a failure occurs, and instruct the maintenance base where the user (operation staff) is located. By doing this, high maintenance quality was maintained. In addition, if it is not possible to determine the cause of the failure and the remedy method only by automatic notification, the maintenance staff can remotely control the user's computer equipment and collect the information necessary to identify the cause. I was giving work instructions. This is called "remote diagnosis".

However, since the above-mentioned remote maintenance takes the form of directly connecting the computer equipment and the maintenance center system, the number of users who feel that it is a risk and do not use the remote maintenance has increased. Computer equipment that is premised on remote maintenance has ensured maintainability, so if remote maintenance is not used, it will not be possible to quickly identify suspects and arrange replacement parts, and recovery will be delayed in the event of a failure.

Therefore, as an alternative method when remote maintenance is not used, a system called an operating system (OS) notification has been used in order to maintain maintainability close to that. The "OS notification system" is an operator (operator) by displaying the details of a failure in a message on the screen area (OS screen) for the OS of the remote operator station (hereinafter referred to as remote OPS) when a failure occurs. ) Is a notification system. Then, when the operator who received the notification called the maintenance staff, the maintenance staff responded on-site for the first time. However, if the OS is stopped due to a failure of a peripheral device or an intermittent failure due to a soft error, output to the OS screen becomes impossible. Therefore, there is a problem that the user cannot immediately know the occurrence of the failure depending on the type of the failure, and the maintenance staff cannot deal with the failure.

Therefore, the second embodiment is a specific embodiment of the first embodiment described above, and a method for solving at least a part of the above-mentioned problems will be described below. For example, the second input / output unit according to the present embodiment uses identification information for identifying the type of failure specified based on the failure information as the second failure notification information after the restriction is released. It is output to the terminal. As a result, the content of the failure can be easily identified from the identification information displayed on the terminal.

Further, after the restriction is released, the second input / output unit removes the content of the failure from the failure information, identifies the identification information, and includes the identification information and a predetermined message. It is desirable to generate the failure notification information of the above and output the second failure notification information to the terminal. For example, if the operator who confirms the display content of the terminal does not disclose the details of the failure content and the operator conveys the identification information to the maintenance staff, the maintenance staff can easily identify the failure content from the identification information.

Further, when the self-diagnosis unit detects a failure other than the OS by the self-diagnosis in the stopped state of the OS, the self-diagnosis unit may collect the failure information and the operating state and notify the failure notification device. desirable. In other words, when the OS is stopped and a failure other than the OS is detected by the self-diagnosis unit of the monitored device, the acquisition unit acquires the failure information and the operating state from the self-diagnosis unit. It is desirable to do. As a result, it is possible to acquire and notify the failure information even for the failure that occurred while the OS was stopped.

Further, when the OS is operating and the restriction of the second input / output unit is released, the input / output restriction unit again restricts the second input / output unit. It is preferable to output the first failure notification information to the terminal by using the first input / output unit. As a result, security can be ensured after the failure notification. Alternatively, the input / output restriction unit may restrict the second input / output unit again after the second input / output unit outputs the second failure notification information to the terminal. good. This also ensures security after a failure notification.

Here, the input / output restriction unit releases the restriction on the output to the terminal when the restriction on the second input / output unit is released, but it is preferable to maintain the restriction on the input from the terminal. As a result, it is possible to realize a failure notification in the OS stopped state while preventing the reception of operation mistakes from the terminal side.

Further, the failure notification device further includes a display unit, and the second input / output unit further displays the second input / output data on the display unit. In this case, it is desirable that the input / output limiting unit limits the input / output to / from the terminal among the input / output by the second input / output unit, and does not limit the output to the display unit. .. As a result, the maintenance staff who arrives at the site where the failure notification device is installed can confirm various detailed information from the display contents of the display unit.

FIG. 3 is a block diagram showing the configuration of the failure notification system 2000 according to the second embodiment. The failure notification system 2000 includes a main body system device 100, an SVP device 200, and an operator system 300. Here, the main body system device 100 and the SVP device 200 are installed in a machine room 400 such as a data center, and are directly connected by a communication cable or the like. On the other hand, the operator system 300 is installed in the operator system 300 located at a remote location from the machine room 400. The SVP device 200 and the operator system 300 are connected via a communication line. That is, the SVP device 200 can notify both the OPS 220 and the remote OPS 310 of the failure of the main body device 100. Then, in the operator system 300, the display contents are confirmed by the operator OP and input is performed by operation. Here, it is assumed that the operator OP is a person in charge of operating the main body system device 100, but is not a maintenance person of a maintenance company for equipment or the like. Then, when the operator OP confirms the failure notification of the main body system device 100 from the SVP device 200 by the operator system 300, the operator OP notifies the maintenance staff to that effect. The maintenance staff heads to the machine room 400 and uses the SVP device 200 to perform maintenance work on the main body system device 100. On the other hand, by strictly managing the operation authority of the OPS 220 of the SVP device 200 in the machine room 400, it is assumed that the system down due to the operation error of the operator OP is prevented.

FIG. 4 is a block diagram showing an internal configuration of the main body system device 100 and the SVP device 200 according to the second embodiment. The system device 100 is an example of the above-mentioned monitoring target device 10, and includes a CPU 110, an MMU (Memory Management Unit) 120, and a DGP 130. The number of CPU 110 and MMU 120 may be two or more.

The CPU 110 is an example of the configuration of the main body system device 100 that starts and executes the OS 111. That is, the OS 111 operates on the main body system device 100. Although the OS 111 illustrates the state of being executed by the CPU 110, it may be expressed that the OS 111 exists in the MMU 120 because most of the program code of the OS 111 is held in the MMU 120.

The MMU 120 is a memory management unit and is an example of the configuration of the main body system device 100. The MMU 120 stores an execution instruction for the OS 111 and an execution result of the OS 111.

The DGP 130 is an example of the self-diagnosis unit 12 described above, and is connected to the CPU 110 and the MMU 120 to periodically perform a self-diagnosis on the CPU 110 and the MMU 120. The DGP 130 includes an information collecting unit 131 and a failure information creating unit 132. The information collecting unit 131 is connected to various configurations (devices) in the main body apparatus 100 including the CPU 110 and MMU 120 to diagnose each configuration, collect the diagnosis results, and extract the operating information (OS operating information) of the OS 111. conduct. The failure information creation unit 132 connects to the information collection unit 131, creates failure information and information indicating the operating status of the OS based on the diagnosis result and OS operation information collected by the information collection unit 131, and sends the SVP device 200 to the failure information creation unit 132. Send.

The SVP device 200 is an example of the above-mentioned failure notification device 20, which monitors the main body device 100 and notifies the operator system 300 of the detected failure via the communication line. The SVP device 200 includes a console data input / output device 210, an OPS (OPerator Station) 220, and a display device 230. The console data input / output device 210 inputs / outputs console data to / from the operator system 300. The console data input / output device 210 includes an acquisition unit 211, a storage unit 212, an input / output restriction unit 213, an OS console data input / output unit 214, and an SVP console data input / output unit 215.

The acquisition unit 211 is an example of the acquisition unit 24 described above, and receives the failure information and the operating state information of the OS from the failure information creation unit 132 of the DGP 130 and stores them in the storage unit 212. The storage unit 212 is a storage area for storing the operating state 2121 and the failure information 2122.

The input / output restriction unit 213 is an example of the input / output restriction unit 23 described above, and is an input / output of the OS console data input / output unit 214 and the SVP console data input / output unit 215 based on the operating state 2121 stored in the storage unit 212. Set or remove restrictions. Further, the input / output restriction unit 213 controls the failure notification based on the failure information 2122 by using the OS console data input / output unit 214 or the SVP console data input / output unit 215 based on the operating state 2121.

FIG. 5 is a block diagram showing an internal configuration of the SVP device 200 and the operator system 300 according to the second embodiment.

The OS console data input / output unit 214 is an example of the first input / output unit 21 described above, and is an example of the OS console data input / output unit 221 of the OPS 220 and the OS console data input / output unit 311 of the remote OPS 310 described later in the operator system 300. Connect with. That is, it can be said that the OS console data input / output unit 214 has a communication path for inputting / outputting data to / from the OS console data input / output unit 221 and the OS console data input / output unit 311.

The OS console data input / output unit 214 receives or generates OS console data from OS 111, and transmits (outputs) OS console data to the OPS 220 and the operator system 300. Further, the OS console data input / output unit 214 receives the OS console data from the OPS 220 and the operator system 300, and outputs the OS console data to the OS 111. The OS console data is an example of the above-mentioned first input / output data. That is, the OS console data is data generated by the OS 111 running on the CPU 110 of the main unit device 100 and output to the SVP device 200. The OS console data is data generated by the SVP device 200 or the operator system 300 and output to the OS 111.

The SVP console data input / output unit 215 is an example of the second input / output unit 22 described above, and is an example of the SVP console data input / output unit 222 of the OPS 220 and the SVP console data input / output unit 312 described later of the remote OPS 310 of the operator system 300. Connect with. That is, it can be said that the SVP console data input / output unit 215 has a communication path for inputting / outputting data to / from the SVP console data input / output unit 222 and the SVP console data input / output unit 312.

However, as will be described later, it is assumed that the SVP console data input / output unit 215 is normally restricted from input / output to / from the remote OPS 310. Therefore, normally, the SVP console data input / output unit 215 generates a control command or the like of the main body system device 100 as SVP console data in response to the input from the OPS 220 operated by the maintenance staff, and controls the main body system device 100. Is issued (output). Further, the SVP console data input / output unit 215 receives the execution result of the control command from the main body system device 100 and outputs it to the OPS 220 as SVP console data. Here, the SVP console data is an example of the above-mentioned second input / output data. Since the SVP console data includes control commands for changing the configuration of the main body system device 100 and the like, it also leads to a system down of the main body system device 100. Therefore, it is desirable from the viewpoint of security that the operator OP cannot input / output SVP console data in principle.

Here, the input / output limiting unit 213 can limit and release the input / output of the OS console data input / output unit 214 and the SVP console data input / output unit 215. In other words, the input / output restriction unit 213 can limit or open the communication path of each of the OS console data input / output unit 214 and the SVP console data input / output unit 215.

It is assumed that the input / output limiting unit 213 according to the present embodiment limits the input / output by the SVP console data input / output unit 215 in advance. Specifically, it is assumed that the input / output limiting unit 213 limits the input / output between the SVP console data input / output unit 215 and the SVP console data input / output unit 312. Therefore, the SVP console data input / output unit 215 can input / output to / from the SVP console data input / output unit 222. Further, the SVP console data input / output unit 215 can input / output to / from the SVP console data input / output unit 312 if the input / output restriction is released by the input / output restriction unit 213. In particular, when the operating state indicates that the OS 111 is stopped, the input / output restriction unit 213 at least releases the restriction on the output from the SVP console data input / output unit 215 on the SVP device 200 side to the SVP console data input / output unit 312. Anything is fine. That is, the input / output restriction unit 213 may not necessarily release the restriction on the input from the SVP console data input / output unit 312 on the operator system 300 side to the SVP console data input / output unit 215. This is to prevent an operation error related to a configuration change of the main body system device 100 by the operator OP.

The OSS 220 outputs the OS console data and the SVP console data received from the console data input / output device 210 to the display device 230. The display device 230 is a display device that displays the OS console data and the SVP console data input from the OPS 220 on the display unit (screen). The OPS 220 includes an OS console data input / output unit 221 and an SVP console data input / output unit 222. Further, the display device 230 includes an OS console data display unit 231 and an SVP console data display unit 232.

The OS console data input / output unit 221 outputs the OS console data received from the OS console data input / output unit 214 to the OS console data display unit 231. The OS console data display unit 231 displays the OS console data input from the OS console data input / output unit 221. The SVP console data input / output unit 222 outputs the SVP console data received from the SVP console data input / output unit 215 to the SVP console data display unit 232. The SVP console data display unit 232 displays the SVP console data input from the SVP console data input / output unit 222.

The operator system 300 includes a remote OPS 310 and a display device 320. The remote OPS 310 outputs the OS console data and the SVP console data received from the console data input / output device 210 to the display device 320. The display device 320 is a display device that displays the OS console data and the SVP console data input from the remote OPS 310 on the display unit (screen).

The OS console data input / output unit 311 outputs the OS console data received from the OS console data input / output unit 214 to the OS console data display unit 321. The OS console data display unit 321 displays the OS console data input from the OS console data input / output unit 311. The SVP console data input / output unit 312 outputs the SVP console data received from the SVP console data input / output unit 215 to the SVP console data display unit 322. The SVP console data display unit 322 displays the SVP console data input from the SVP console data input / output unit 312.

Here, the OS console data input / output unit 214 and the SVP console data input / output unit 215 use the failure notification information as OS console data from the failure information 2122 stored in the storage unit 212 based on the instructions of the input / output restriction unit 213. It may be generated. For example, the OS console data input / output unit 214 may generate the first failure notification information based on the failure information 2122. Here, the first failure notification information may be character information indicating the same content as the failure information 2122. Further, the SVP console data input / output unit 215 may generate a second failure notification information based on the failure information 2122 as SVP console data. Here, the second failure notification information may be identification information for identifying the type of failure specified based on the failure information 2122. Here, the identification information includes, for example, data including numbers and characters such as an error code indicating a failure ID, but is not limited thereto. In this case, the SVP console data input / output unit 215 removes the content of the failure from the failure information 2122, identifies the identification information, and includes the identification information and a predetermined message after the restriction is released by the input / output restriction unit 213. Generate the second failure notification information. Then, the SVP console data input / output unit 215 outputs the generated second failure notification information to the SVP console data input / output unit 222 and the SVP console data input / output unit 312.

Here, the predetermined message may be, for example, a message informing the operator OP that a maintenance worker needs to be called. Then, the predetermined message may be stored in advance in the storage unit 212 or the like. In addition, the identification information is information used by the maintenance staff called to the site to grasp the details of the failure. For example, the maintenance staff searches the failure information database from the identification information to obtain information such as details of the failure content and countermeasures. Therefore, the identification information can be regarded as an encrypted message by suppressing the disclosure of the details of the failure content to the operator OP.

The first failure notification information or the second failure notification information may be generated by the failure information creation unit 132 of the DGP 130.

FIG. 6 is a sequence diagram showing a flow of failure notification processing by the DGP 130 according to the second embodiment. First, the information collecting unit 131 of the DGP 130 diagnoses the CPU 110 and the MMU 120 (S11). Here, the information collecting unit 131 shall start the diagnosis on a regular basis, that is, at regular time intervals. Then, the information collecting unit 131 collects the diagnosis result from the CPU 110 and the MMU 120 (S12). Here, it is assumed that the information collecting unit 131 has not detected a failure from the CPU 110, the MMU 120, or the like. That is, at this point, OS111 is running on the CPU 110.

After that, it is assumed that the OS 111 is stopped due to a failure of a peripheral device in the main body system device 100 or an intermittent failure due to a soft error. Then, after a certain period of time from step S11, the information collecting unit 131 again diagnoses the CPU 110 and the MMU 120 (S13). Then, the information collecting unit 131 collects the diagnosis result from the CPU 110 and the MMU 120. At this time, the information collecting unit 131 detects a failure of the main body system device 100 from the diagnosis result and extracts the operation information of the OS 111 (S14). For example, the information collecting unit 131 may analyze the diagnosis result and extract the OS operation information. Alternatively, the information collecting unit 131 may extract information that can determine the operating state of the OS from a predetermined storage area in the main body system device 100 as the OS operating information.

After that, the information collecting unit 131 transmits the diagnosis result and the OS operation information to the failure information creating unit 132 (S15). Then, the failure information creation unit 132 creates the failure information and the information indicating the operating state of the OS based on the diagnosis result and the OS operation information received from the information collection unit 131. Here, the failure information creation unit 132 may create failure information by analyzing the diagnosis result and converting or extracting it into information indicating the content of the failure. Further, the failure information creation unit 132 may create an operating state by converting the OS operating information into information indicating whether the OS 111 is operating or stopped. In this case, the operating state is information indicating that the OS is stopped. In addition, the failure information creation unit 132 may create failure information and the operating state of the OS by other methods. Then, the failure information creation unit 132 transmits the failure information and the operating state of the OS to the console data input / output device 210 of the SVP device 200 (S16).

Then, after a certain period of time from step S13, the information collecting unit 131 again diagnoses the CPU 110 and the MMU 120 (S13a). Then, the information collecting unit 131 collects the diagnosis result from the CPU 110 and the MMU 120, and extracts the OS operation information (S14a). For example, a failure that occurs after step S14 such as a failure that occurs in another configuration in the main body system device 100 due to the OS stop can be mentioned, but is not limited thereto. That is, it is assumed that the failure that occurred after the stop of OS111 was detected, not the failure of the stop of OS111 itself.

In this case as well, the information collection unit 131 transmits the diagnosis result and the OS operation information to the failure information creation unit 132 (S15a), and the failure information creation unit 132 transmits the failure information and the operating state of the OS to the SVP device 200. It is transmitted to the console data input / output device 210 (S16a). In this case as well, the operating state is information indicating that the OS is stopped.

Although the case where the OS is stopped (immediately after the stop and after a certain period of time has passed after the stop) has been described with reference to FIG. 6, the present embodiment can also handle a case where a failure occurs while the OS is operating. In that case, for example, when a failure occurs after step S12, the OS does not stop and the operation continues. Then, in step S14, the information collecting unit 131 detects a failure of the CPU 110 or the MMU 120, and the OS operating information extracted at that time and the operating state created by the failure information creating unit 132 indicate that the OS is operating. It becomes information.

FIG. 7 is a flowchart showing the flow of failure notification processing in the SVP device 200 according to the second embodiment. First, the acquisition unit 211 receives the failure information and the operating state of the OS from the DGP 130 (S21). Then, the acquisition unit 211 stores the received failure information and the operating state of the OS in the storage unit 212 (S22).

After that, the input / output limiting unit 213 refers to the storage unit 212 and determines whether the OS 111 is operating or stopped based on the operating state 2121 (S23). When it is determined that the OS 111 is operating, the input / output restriction unit 213 restricts the input / output of SVP console data to / from the remote OPS 310 (S24). Specifically, the input / output restriction unit 213 is used when the communication path for input / output between the SVP console data input / output unit 215 and the SVP console data input / output unit 312 is valid (when the communication path is not restricted). , Put restrictions.

Subsequently, the input / output restriction unit 213 instructs the OS console data input / output unit 214 to transmit the first failure notification information. The OS console data input / output unit 214 reads the failure information 2122 from the storage unit 212 in response to an instruction from the input / output restriction unit 213, and generates the first failure notification information as OS console data (S25). The OS console data input / output unit 214 may use the failure information 2122 itself as the first failure notification information. Then, the OS console data input / output unit 214 transmits the generated OS console data via the communication path (S26). Therefore, the OS console data is output to the OS console data input / output unit 221 and the OS console data input / output unit 311.

Therefore, the OS console data display unit 231 displays the OS console data received from the OS console data input / output unit 221. Further, the OS console data display unit 321 displays the OS console data received from the OS console data input / output unit 311. As a result, the operator OP can detect a failure during OS operation and can respond to the failure via the OS 111, as in the case of notification by the OS notification system. Alternatively, the operator OP may contact the maintenance staff to deal with the display contents of the OS console data display unit 321.

When it is determined in step S23 that the OS 111 is stopped, the input / output restriction unit 213 releases the restriction on the input / output of the SVP console data with the remote OPS 310 (S27). Specifically, the input / output restriction unit 213 enables the communication path for input / output from the SVP console data input / output unit 215 to the SVP console data input / output unit 312.

Subsequently, the input / output restriction unit 213 instructs the SVP console data input / output unit 215 to transmit the second failure notification information. The SVP console data input / output unit 215 reads the failure information 2122 from the storage unit 212 in response to an instruction from the input / output restriction unit 213 and generates a second failure notification information as SVP console data (S28). For example, the SVP console data input / output unit 215 extracts the identification information from the failure information 2122, combines the identification information with a predetermined message, and generates a second failure notification information. Then, the SVP console data input / output unit 215 transmits the generated SVP console data via the communication path (S29). Therefore, the SVP console data is output to the SVP console data input / output unit 222 and the SVP console data input / output unit 312.

Therefore, the SVP console data display unit 232 displays the SVP console data received from the SVP console data input / output unit 222. Further, the SVP console data display unit 322 displays the SVP console data received from the SVP console data input / output unit 312. As a result, it is possible to display an error code or the like for identifying the failure content that could not be notified by the OS notification system. In addition, it is possible to notify the existence of a failure that occurs after the OS is stopped. Therefore, the operator OP can detect the failure during the OS stop from the display contents of the SVP console data display unit 322, and can contact the maintenance staff to deal with the error code or the like.

In step S27, the input / output restriction unit 213 may at least release the restriction on the transmission of the SVP console data from the SVP device 200 to the operator system 300, and the transmission of the SVP console data from the operator system 300 to the SVP device 200. There is no need to lift the restriction.

Further, after step S29, the input / output restriction unit 213 may re-limit the amount released in step S27. In this case, step S24 does not have to be executed.

As described above, also in the second embodiment, it is possible to realize the failure notification of the target system in the remote monitoring while ensuring the security. In particular, since the self-diagnosis by the DGP 130 is performed periodically even after the OS is stopped, it is possible to notify the failure that occurred after the OS is stopped.

<Other embodiments>
In the above-described embodiment, the description is made as a hardware configuration, but the present invention is not limited to this. The present disclosure can also be realized by causing the CPU to execute a computer program.

In the above example, the program can be stored and supplied to a computer using various types of non-transitory computer readable medium. Non-transitory computer-readable media include various types of tangible storage media. Examples of non-temporary computer-readable media include magnetic recording media (eg, flexible discs, magnetic tapes, hard disk drives), magneto-optical recording media (eg, magneto-optical discs), CD-ROMs (Read Only Memory), CD-Rs. CD-R / W, DVD (Digital Versatile Disc), semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)) are included. The program may also be supplied to the computer by various types of transient computer readable medium. Examples of temporary computer-readable media include electrical, optical, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

The present disclosure is not limited to the above embodiment, and can be appropriately modified without departing from the spirit. Further, the present disclosure may be carried out by appropriately combining the respective embodiments.

Some or all of the above embodiments may also be described, but not limited to:
(Appendix A1)
A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
An input / output restriction unit that limits input / output by the second input / output unit in advance,
An acquisition unit that acquires failure information related to a failure detected by the monitored device and the operating state of the OS at the time of the detection from the monitored device.
With
The input / output limiting unit is
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit is used to output the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit is used to send the second failure notification information based on the failure information to the terminal. Failure notification device to output.
(Appendix A2)
The second input / output unit is
The failure notification device according to Appendix A1, which outputs identification information for identifying the type of failure specified based on the failure information to the terminal as the second failure notification information after the restriction is released.
(Appendix A3)
The second input / output unit is
After the restriction is released, the content of the failure is removed from the failure information to identify the identification information, and the second failure notification information including the identification information and a predetermined message is generated, and the second failure notification information is generated. The failure notification device according to Appendix A2, which outputs the failure notification information of the above to the terminal.
(Appendix A4)
The acquisition unit
When a failure other than the OS is detected by the self-diagnosis unit of the monitored device while the OS is stopped, the failure information and the operating state are acquired from the self-diagnosis unit. The failure notification device according to item 1.
(Appendix A5)
The input / output limiting unit is
When the OS is operating and the restriction of the second input / output unit is released, the restriction is applied to the second input / output unit again to apply the restriction to the first input / output unit. The failure notification device according to any one of Supplementary A1 to A4, wherein the first failure notification information is output to the terminal by using a unit.
(Appendix A6)
The input / output limiting unit is
The failure according to any one of Supplementary A1 to A4, wherein the second input / output unit outputs the second failure notification information to the terminal, and then again imposes the restriction on the second input / output unit. Notification device.
(Appendix A7)
The input / output limiting unit is
The item according to any one of Supplementary A1 to A6, wherein when the restriction on the second input / output unit is released, the restriction on the output to the terminal is released, but the restriction on the input from the terminal is maintained. Failure notification device.
(Appendix A8)
The failure notification device further includes a display unit.
The second input / output unit further displays the second input / output data on the display unit.
The input / output limiting unit is
Of the input / output by the second input / output unit, the input / output to / from the terminal is restricted, and the output to the display unit is not restricted. Notification device.
(Appendix B1)
Monitored devices running the OS (Operating System) and
With the terminal
A failure notification device connected to the terminal via a communication line,
With
The monitored device is
When a failure is detected by the self-diagnosis of the monitored device, it is provided with a self-diagnosis unit that collects the failure information related to the failure and the operating state of the OS at the time of the detection and notifies the failure notification device.
The failure notification device is
With respect to the first input / output data with the OS, the first input / output unit that inputs / outputs with the terminal and
Regarding the second input / output data related to the control of the monitored device by the failure notification device, the second input / output unit that inputs / outputs to / from the terminal, and the second input / output unit.
An acquisition unit that acquires the failure information and the operating state from the self-diagnosis unit, and
An input / output restriction unit that limits input / output by the second input / output unit in advance,
With
The input / output limiting unit is
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit is used to output the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit is used to send the second failure notification information based on the failure information to the terminal. Failure notification system to output.
(Appendix B2)
The self-diagnosis unit
The failure notification system according to Appendix B1, which collects the failure information and the operating state and notifies the failure notification device when a failure other than the OS is detected by the self-diagnosis in the stopped state of the OS.
(Appendix C1)
A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
The failure notification device equipped with
Limiting the input / output by the second input / output unit,
The failure information regarding the failure detected by the monitored device and the operating state of the OS at the time of the detection are acquired from the monitored device.
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit outputs first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit outputs second failure notification information based on the failure information to the terminal. Failure notification method.
(Appendix D1)
A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
To a computer equipped with
The process of limiting the input / output by the second input / output unit and
A process of acquiring the failure information related to the failure detected by the monitored device and the operating state of the OS at the time of the detection from the monitored device.
A process of determining whether the OS is running or stopped based on the operating state,
When the OS is in operation, the first input / output unit outputs the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the process of releasing the restriction of the second input / output unit and the process of releasing the restriction.
After the release, the second input / output unit outputs the second failure notification information based on the failure information to the terminal.
Failure notification program to execute.

Although the invention of the present application has been described above with reference to the embodiments (and examples), the invention of the present application is not limited to the above-described embodiments (and examples). Various changes that can be understood by those skilled in the art can be made within the scope of the present invention in terms of the structure and details of the present invention.

1000 Failure notification system 10 Monitored device 11 OS
12 Self-diagnosis unit 20 Failure notification device 21 First input / output unit 22 Second input / output unit 23 Input / output restriction unit 24 Acquisition unit 30 Terminal 2000 Failure notification system 100 System unit 110 CPU
111 OS
120 MMU
130 DGP
131 Information collection unit 132 Failure information creation unit 200 SVP device 210 Console data input / output device 211 Acquisition unit 212 Storage unit 2121 Operating status 2122 Failure information 213 Input / output restriction unit 214 OS console data input / output unit 215 SVP console data input / output unit 220 OPS
221 OS console data input / output unit 222 SVP console data input / output unit 230 Display device 231 OS console data display unit 232 SVP console data display unit 300 Operator system 310 Remote OPS
311 OS console data input / output unit 312 SVP console data input / output unit 320 Display device 321 OS console data display unit 322 SVP console data display unit 400 Machine room OP operator

Claims (9)

A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
An input / output restriction unit that limits input / output by the second input / output unit in advance,
An acquisition unit that acquires failure information related to a failure detected by the monitored device and the operating state of the OS at the time of the detection from the monitored device.
With
The input / output limiting unit is
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit is used to output the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit is used to send the second failure notification information based on the failure information to the terminal. Output ,
Wherein when releasing the restriction of the second input-output unit, but to release the restriction of the output to the terminal, to that failure notification device maintains the restriction of the input from the terminal. The second input / output unit is
The failure notification device according to claim 1, wherein after the restriction is released, identification information for identifying the type of failure specified based on the failure information is output to the terminal as the second failure notification information. The second input / output unit is
After the restriction is released, the content of the failure is removed from the failure information to identify the identification information, and the second failure notification information including the identification information and a predetermined message is generated, and the second failure notification information is generated. The failure notification device according to claim 2, which outputs the failure notification information of the above to the terminal. The acquisition unit
Any of claims 1 to 3 for acquiring the failure information and the operating state from the self-diagnosis unit when a failure other than the OS is detected by the self-diagnosis unit of the monitored device while the OS is stopped. The failure notification device according to item 1. The input / output limiting unit is
When the OS is operating and the restriction of the second input / output unit is released, the restriction is applied to the second input / output unit again to apply the restriction to the first input / output unit. The failure notification device according to any one of claims 1 to 4, wherein the unit is used to output the first failure notification information to the terminal. The input / output limiting unit is
The method according to any one of claims 1 to 4, wherein after the second input / output unit outputs the second failure notification information to the terminal, the restriction is applied to the second input / output unit again. Failure notification device. Monitored devices running the OS (Operating System) and
With the terminal
A failure notification device connected to the terminal via a communication line,
With
The monitored device is
When a failure is detected by the self-diagnosis of the monitored device, it is provided with a self-diagnosis unit that collects the failure information related to the failure and the operating state of the OS at the time of the detection and notifies the failure notification device.
The failure notification device is
With respect to the first input / output data with the OS, the first input / output unit that inputs / outputs with the terminal and
Regarding the second input / output data related to the control of the monitored device by the failure notification device, the second input / output unit that inputs / outputs to / from the terminal, and the second input / output unit.
An acquisition unit that acquires the failure information and the operating state from the self-diagnosis unit, and
An input / output restriction unit that limits input / output by the second input / output unit in advance,
With
The input / output limiting unit is
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit is used to output the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the restriction of the second input / output unit is released, and the second input / output unit is used to send the second failure notification information based on the failure information to the terminal. Output ,
Wherein when releasing the restriction of the second input-output unit, but to release the restriction of the output to the terminal, the fault notification system that maintains the restriction of the input from the terminal. A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
The failure notification device equipped with
Limiting the input / output by the second input / output unit,
The failure information regarding the failure detected by the monitored device and the operating state of the OS at the time of the detection are acquired from the monitored device.
Based on the operating state, it is determined whether the OS is operating or stopped, and
When the OS is operating, the first input / output unit outputs first failure notification information based on the failure information to the terminal.
If the OS is stopped, it releases the restriction of said second input portion, by said second output unit outputs the second failure notification information based on the failure information to the terminal ,
A failure notification method in which when the restriction on the second input / output unit is released, the restriction on the output to the terminal is released, but the restriction on the input from the terminal is maintained. A first input / output unit that inputs / outputs data to and from a terminal connected via a communication line with respect to the first input / output data with the OS (Operating System) operating in the monitored device.
Regarding the second input / output data related to the control of the monitored device by the own device, the second input / output unit that inputs / outputs to / from the terminal and the second input / output unit.
To a computer equipped with
The process of limiting the input / output by the second input / output unit and
A process of acquiring the failure information related to the failure detected by the monitored device and the operating state of the OS at the time of the detection from the monitored device.
A process of determining whether the OS is running or stopped based on the operating state,
When the OS is operating, the first input / output unit outputs the first failure notification information based on the failure information to the terminal.
When the OS is stopped, the process of releasing the restriction of the second input / output unit and the process of releasing the restriction.
After the release, the second input / output unit outputs the second failure notification information based on the failure information to the terminal.
When the restriction on the second input / output unit is released, the restriction on the output to the terminal is released, but the restriction on the input from the terminal is maintained.
Failure notification program to execute.

Images