JP7074294B2 - Computer system management device and management method - Google Patents

Description

The present invention relates to a management device and a management method in a computer system capable of maintaining and managing a computer system based on a support contract with a manufacturer and a maintenance company.

Patent Documents 1 and 2 are known as techniques for maintenance and replacement of parts constituting a computer system.
In the management system shown in Patent Document 1, a customer information database connected to a terminal device via a network and storing customer information of the device, component information mounted on the device, and components for which replacement is recommended for each component are recommended. There is a description that it has a product information database in which exchange-required information indicating that the product needs to be exchanged is stored.
Further, in this management system, in response to the request for device support information based on the search condition sent from the terminal, the device identification information corresponding to the search condition and the customer information are acquired from the customer database, and the acquisition is performed. It has a device support information acquisition means for acquiring component information having exchange required information of device identification information from a product information database.

As information requiring replacement, the urgency can be set according to the urgency of replacing the parts. There is a statement that the urgency of parts with minor defects is low.

Further, in the information processing apparatus shown in Patent Document 2, when the control package fails or becomes abnormal, a failure notification is transmitted to the control unit by a control signal. Then, the control unit automatically stops the power supply to the feeder line for the corresponding slot based on the control signal indicating the failure notification.

Japanese Unexamined Patent Publication No. 2011-150565 Japanese Unexamined Patent Publication No. 04-333118

By the way, although there is a description in Patent Documents 1 and 2 that the urgency of parts replacement for parts that occur frequently and have a large influence is included in the database of past replacement information, problems that occur now or in the future It is not a technology that considers the degree of impact on the system.
That is, in Patent Documents 1 and 2, since preventive measures are not taken against the risk at the time of failure, it is not possible to prevent the influence on the user's business due to the sudden failure in advance, and it is improved in this respect. Was expected.

The present invention has been made in view of the above-mentioned circumstances, and for a board having a problem, when a failure occurs, the system impact level indicating the degree of impact on the system, redundancy, etc. is set to a predetermined reference threshold value. Provided are a computer system management device and a management method capable of making a judgment based on the above and taking appropriate preventive measures.

In order to solve the above problems, the present invention proposes the following means.
In the management device of the computer system shown in the first aspect of the present invention, the component information storage unit that holds the key code of the component mounted on each board in association with the board code, the redundancy of each board, and the influence of the system. The problem lot information is included in the problem lot information by referring to the location information storage unit that holds characteristic information such as the degree in association with the board code and the component information storage unit when the problem lot information is received. It is determined whether or not a key code matching the key code of the component exists in the component information storage unit, and if the key code exists, the location information storage unit is referred to and associated with the corresponding board code. It is characterized by having a management control unit that implements preventive measures based on whether or not the system impact level showing characteristic information such as the redundancy and the degree of system impact exceeds a predetermined reference threshold. And.

In the computer system management method shown in the second aspect of the present invention, the component information storage stage of holding the key code of the component mounted on each board in association with the board code, the redundancy of each board, and the influence of the system The location information storage stage that holds characteristic information such as degree in association with the board code, and when the problem lot information is received, the key code that matches the key code of the part included in the problem lot information is stored in advance. A system impact level that indicates characteristic information such as redundancy and system impact associated with the corresponding board code is predetermined in advance. It is characterized by having a control stage in which preventive measures are taken based on whether or not a certain reference threshold is exceeded.

According to the present invention, for a board having a problem, appropriate prevention is made by determining whether or not the system impact level indicating the degree of impact on the system, redundancy, etc. exceeds a predetermined reference threshold value. You can take action.

It is a figure which shows the management apparatus of the computer system which concerns on this invention. It is a figure which shows the management apparatus of the computer system which concerns on embodiment of this invention. It is a figure which shows the example of the part information table, (A) shows the board information, (B) shows the board part information, respectively. It is a figure which shows the example of the key code table. It is a figure which shows the example of the component information. It is a figure which shows the example of the location information. It is a figure which shows the example of the problem lot information. It is a figure which shows the operation flow of a management module.

The management device A of the computer system C according to the present invention will be described with reference to FIG.
The management device A has a component information storage unit 1, a location information storage unit 2, and a management control unit 3 as main components.

The component information storage unit 1 is provided to hold the key code of the component mounted on each board B in association with the board code.
The location information storage unit 2 is provided to hold characteristic information such as the redundancy and the degree of system influence of each board B in association with the board code.

When the management control unit 3 receives the problem lot information 4 from an external remote server (not shown) or the like, the management control unit 3 refers to the component information storage unit 1 to display the parts included in the problem lot information 4. It is determined whether or not a key code matching the key code exists in the component information storage unit 1.
Further, when the component information storage unit 1 has a key code that matches the key code of the component included in the problem lot information 4, the management control unit 3 refers to the location information storage unit 2 to deal with the situation. The preventive action signal 5 is output based on whether or not the system impact level indicating characteristic information such as redundancy and system impact associated with the board code exceeds a predetermined reference threshold value. do.

That is, in the management device A configured as described above, the system influence level indicating the degree of influence on the system, the redundancy, etc. is predetermined for the substrate B having a problem of occurrence / possibility of failure. It is possible to make a judgment based on whether or not the standard threshold value has been exceeded, and to take appropriate preventive measures.
The problem lot information 4 includes phenomena such as a short failure when an abnormality occurs, an open failure, and frequent occurrence of pseudo errors.
Further, as a preventive measure, by logically and electrically separating the target parts, it is possible to prevent the user's business from being affected by the occurrence of a sudden failure in advance.

(Embodiment)
The management device A1 of the computer system C1 according to the embodiment of the present invention will be described with reference to FIGS. 2 to 8.

FIG. 2 is an overall configuration diagram of the management device A1 according to the present embodiment, and includes a computer system C1 located at the user site 91 and a remote server 10 located at the external area 90.

The computer system C1 has a management module 20 that controls the whole, and a plurality of boards 30, 40, 50 connected to the management module 20 in the system main body 92.

A component information memory 31, a control IC 33, mounted components 301, 302, and the like are mounted on the board 30.
The component information memory 31 is a non-volatile memory and stores the component information table 310.
In the component information table 310, as shown in FIGS. 3A and 3B, "the basic information 313 such as the board code and serial number, as well as the mounted components 301, 302 and the like mounted on the substrate 30" are shown. The key code 311 that can uniquely identify the product name and lot information of each component and the location code 312 that indicates the mounting position of each component on the board are recorded.

Further, the component information memory 31 has a function of transmitting the data of the component information table 310 stored in the component information table 310 to the management module 20 when the board 30 is incorporated in the computer system C1.
The user cannot specify the detailed information of the parts from the key code 311, and the maintenance staff can access the key code table 101 stored in the remote server 10 during the maintenance work to obtain the detailed information of the mounted parts. You can check. FIG. 4 shows an example of the key code table 101.

The control IC 33 controls the power ON / OFF of each component on the board 30 and the power ON / OFF control of the entire board 30 based on the control command 30c issued from the management module 20.
Although an example in which the component information memory 31, the control IC 33, the mounted components 301, 302, and the like are mounted on the board 30, the same components are mounted on the boards 40 and 50.

The management module 20 manages the component information storage unit 201 that stores the information of the entire computer system C1 based on the component information 30a transmitted from the component information memory 31 on the boards 30, 40, and 50.
Further, as the management module 20, an operating time information storage unit 202, a location information storage unit 203, a preventive action execution flag storage unit 204, and a management control unit 21 for executing various processes are provided together with the component information storage unit 201. There is.
The management control unit 21 determines whether or not the system impact level indicating characteristic information such as redundancy and system impact associated with the corresponding board code exceeds a predetermined reference threshold value. It is intended to carry out preventive measures based on the above, and details will be described later with reference to FIG.

As shown in FIG. 5, the component information storage unit 201 includes board codes 2011 for each board type for each of the boards 30, 40, 50 constituting the computer system C1, and key codes of all parts mounted on each board. 2012, location code 2013 indicating the location of each component, presence / absence of redundancy 2014, and the like are included.
The information shown as the board code 2011, the key code 2012, the location code 2013, and the redundancy 2014 is appropriately transmitted from the boards 30, 40, and 50.

Further, in the management module 20, when the board is replaced during maintenance work or when a new board is added, the component information is based on the component information 30, 40, 50 transmitted from the new board. The storage unit 201 is updated.
Similarly, the management module 20 monitors whether each board and each component is redundant, and appropriately updates the presence or absence of redundancy 2014 in the component information storage unit 201.

Further, the operating time information storage unit 202 of the management module 20 stores the operating time after the computer system C1 starts operating.
Further, in the location information storage unit 203 of the management module 20, as shown in FIG. 6, the degree of influence on the system at the time of component failure is shown for each location code 2032 together with the location code 2032 of each board 2031. Manage 2033.

Further, in the management module 20, when a new type of board is added at the time of maintenance and replacement, the maintenance staff can update the location information storage unit 203 reflecting the information of the board added from the remote server 10.
Further, the management module 20 is provided with a preventive action execution flag storage unit 204 for determining whether or not the user permits preventive action when a problem lot is found, based on a maintenance contract.
Further, the management module 20 described above has a console screen or the like for notifying users and maintenance personnel of information such as alerts, but is omitted in the drawings.

As described above, the remote server 10 is installed in an external area 90 located outside such as a site of a product business operator or a maintenance business operator.
As shown in FIG. 2, the remote server 10 is provided with a key code table 101 that is accessible to maintenance personnel during maintenance work and records component information uniquely identified from the key code of each component.
Then, in such a remote server 10, the problem lot information 10a is transmitted to the management module 20 based on the failure record in the field and the information from the component vendor. As shown in FIG. 7, the problem lot information 10a corresponds to the key code 10a1 that can uniquely identify the product name and lot number of the target part and the phenomenon at the time of abnormality (short failure, open failure, frequent pseudo error, etc.). Information such as risk level 10a2 is included.

Further, as shown in FIG. 2, when the problem lot component is found in the component component of the computer system C1, the remote server 10 receives the problem lot discovery report 10b from the management module 20. The maintenance company can start the replacement work of the target parts by receiving the problem lot discovery report 10b via the remote server 10.

Next, with reference to the flowchart of FIG. 8, the operation flow in the management control unit 21 of the management module 20 when the problem lot information 10a is received from the remote server 10 will be described for each step (S).

[Step S801] to [Step S802]
On condition that the management module 20 receives the problem lot information 10a from the remote server 10 (step S801), the component information storage unit that matches the key code 10a1 notified in the problem lot information 10a in step S802 is the component information storage unit. It is determined whether or not it exists in the key code 2012 of the component managed by 201.
If it is determined in step S802 that the key codes do not match and the parts of the target lot do not exist, the process proceeds to step S811 and the processing by this flow ends.

[Step S803]
If it is determined in step S802 that the parts of the target lot existed (the key codes match), the location where the key code 2012 of the target parts is mounted in the component information storage unit 201 in step S803. Check the code 2013.
Further, in step S803, the location information storage unit 203 confirms the system influence degree 2033 when the component of the location code 2032 fails.
Then, in step S803, the system impact level when a failure occurs is determined from the system impact degree 2033 and the risk level 10a2 of the problem lot information 10a, and it is determined whether or not the system impact level is equal to or higher than the threshold value.

The system impact level is calculated by quantifying the system impact degree 2033 and the risk level 10a2 of the problem lot information 10a.
If it is determined in step S803 that the system impact level is below the threshold value, a replacement recommendation alert is displayed on the console of the management module 20, and a problem lot discovery report 10b is sent to the remote server 10. After transmission (step S810), the process according to this flow is terminated (step S811).

[Step S804]
If it is determined in step S803 that the system impact level is equal to or higher than the threshold value, in step S804, whether or not the user permits the implementation of the preventive action from the preventive action execution flag storage unit 204. Is determined.

[Step S805]
When it is determined in step S804 that the implementation of preventive measures is permitted, it is determined from the redundancy 2014 of the component information storage unit 201 whether or not the target component is redundant (step S805), and YES. In the case of NO, the process proceeds to step S806, and in the case of NO, the process proceeds to step S810.

[Step S806]
When it is determined in step S805 that the redundancy is achieved, it is determined in step S806 whether or not the operating time information storage unit 202 is equal to or greater than the threshold value, and if YES, the process proceeds to step S807 and NO. In the case of, the process proceeds to step S810.

[Step S807]
When it is determined in step S806 that the operating time is equal to or longer than the threshold value, it is determined in step S807 that there is a high risk of failure, and a confirmation message for implementing preventive measures is displayed on the console of the management module 20. At the same time, the problem lot discovery report 10b is transmitted to the remote server 10.
After that, in step S807, the user is made to execute the preventive action execution permission command on the console at an arbitrary timing that minimizes the business impact via the confirmation message.

[Step S808]
When the management module 20 confirms the permission to implement the preventive action in step S808, for example, the control command 30c is issued to the control IC 33 on the target board.
Based on the control command 30c, the control IC 33 issues a power OFF command to the target component or the entire board 30, and electrically separates the problem lot component. At this time, when issuing a power OFF command to the entire board 30, a command is issued to the management software in advance to logically disconnect the target board 30 from the system.

[Step S809]
In step S809, after the management module 20 issues the control command 30c, the remote server 10 is notified that the preventive action has been executed. Then, the maintenance company is dispatched to replace the target parts when the problem lot discovery report 10b is received.

[Step S810] to [Step S811]
If NO is determined in steps S803, S804, S805, and S806, a replacement recommendation alert is displayed on the console of the management module 20, and a problem lot discovery report 10b is sent to the remote server 10 (step S810). , The process according to this flow is terminated (step S811).

In the management device A1 of the computer system C1 configured as described above, when the management control unit 21 receives the problem lot information 10a via the external remote server 10 managed by the maintenance personnel, it is a component component. By referring to the information storage unit 201, it is determined whether or not a key code matching the key code included in the problem lot information 4 exists in the component information storage unit 201 (steps S801 to S802). ..

At this time, when the management control unit 21 determines that the key code matching the key code included in the problem lot information 10a exists in the component information storage unit 201, the location information storage unit 203 is referred to and the corresponding response is made. Preventive measures are taken based on whether or not the system impact level indicating characteristic information such as redundancy and system impact associated with the board code exceeds a predetermined reference threshold value (step S803). -Step S810).
That is, in the management device A1, the system influence level indicating the degree of influence on the system, the redundancy, etc. is a predetermined standard for the boards 30, 40, and 50 having a problem of occurrence / possibility of failure. Judgment is made based on whether or not the threshold value has been exceeded (steps S803 to S806), which makes it possible to take appropriate preventive measures.

Further, in the management device A1, when a problem lot part is found, the management module 20 determines the failure risk based on the system operating time and the degree of influence on the system corresponding to the place where the target part is used. At this time, in the management device A1, when the risk is high, the management module 20 is made to perform logical / electrical disconnection of the target component at an arbitrary timing of the user.
That is, in the management device A1 shown in the present embodiment, when the target part of the problem lot is found in the computer system C1, the risk is predicted from the degree of influence on the system and the operating time, and if the risk is high, the risk is predicted. By logically and electrically separating the target parts, it is possible to prevent the user's business from being affected by the occurrence of a sudden failure in advance. Further, in the management device A1, the influence on the user's business can be minimized by executing the separation of the target component at an arbitrary timing of the user.

In the above embodiment, the control flow shown in FIG. 8 is carried out by the management control unit 21 of the management module 20, but the place of implementation is not limited to the control ICs of the boards 30, 40, and 50. May be carried out.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment and includes design changes and the like within a range not deviating from the gist of the present invention.

The present invention relates to a management device and a management method capable of maintaining and managing a computer system based on a support contract or the like with a manufacturer or a maintenance company.

1 Component information storage unit 2 Location information storage unit 3 Management control unit 21 Management control unit 30 Board 40 Board 50 Board 201 Component component information storage unit 203 Location information storage unit A Management device A1 Management device B Board C Computer system C1 Computer system

Claims (4)

A component information storage unit that holds the key code and redundancy of the parts mounted on each board in association with the board code.
A location information storage unit that holds the system impact of each board in association with the board code,
When the problem lot information is received, by referring to the component information storage unit, does the component information storage unit have a key code that matches the key code of the component included in the problem lot information? If it is determined and the key code exists,
It is determined whether the system impact level calculated from the system impact level stored in the location information storage unit and the risk level included in the problem lot information is equal to or higher than a predetermined threshold value, and is equal to or higher than the threshold value. In the case of
It is determined from the redundancy associated with the corresponding board code stored in the component information storage unit whether or not the target component is redundant, and when it is determined that the target component is redundant, the target is used. Take preventive measures to logically and electrically separate parts,
Replacement is recommended when the system impact level is equal to or higher than the threshold value and it is not determined to be redundant, or when it is determined that the system impact level is not equal to or higher than a predetermined threshold value. Display an alert and send a problem lot discovery report to the remote server to finish the process.
A computer system management device including a management control unit that terminates processing when it is determined that the key code does not exist in the component information storage unit. The computer system management according to claim 1, wherein a control IC for turning off the power of the board corresponding to the board code is connected to the management control unit when the preventive measures are taken. Device. One of claims 1 or 2, wherein the management control unit is connected to a remote server that is accessed by maintenance personnel and outputs problem lot information including the product name and lot number of the target part. The computer system management device according to item 1. The component information storage stage that holds the key code and redundancy of the parts mounted on each board in association with the board code,
The location information storage stage that holds the system impact of each board in association with the board code,
When the problem lot information is received, it is determined whether the key code matching the key code of the part included in the problem lot information exists in the information stored in advance, and if the key code exists,
A stage for determining whether the system impact level calculated from the system impact level stored in the location information storage unit and the risk level included in the problem lot information is equal to or higher than a predetermined threshold value.
When it is determined that the threshold value is exceeded, it is determined from the redundancy associated with the corresponding board code stored in the component information storage unit whether or not the target component is redundant, and the redundancy is achieved. At the stage of implementing preventive measures to logically and electrically separate the target part when it is judged that it has been done,
Replacement is recommended when the system impact level is equal to or higher than the threshold value and it is not determined to be redundant, or when it is determined that the system impact level is not equal to or higher than a predetermined threshold value. At the stage of displaying an alert and sending a problem lot discovery report to the remote server to end the process,
The stage of ending the process when it is determined that the key code does not exist in the component information storage unit, and
A method of managing a computer system, characterized in that it has.

Images