DEVICE INFORMATION COLLECTION MANAGEMENT DEVICE, DEVICE INFORMATION COLLECTION MANAGEMENT SYSTEM, DEVICE INFORMATION COLLECTION MANAGEMENT METHOD AND PROGRAM

Abstract

With regard to information processing devices and the like, only necessary and sufficient information can be efficiently collected. [Solution] The device information collection and management device comprises a support information list management unit that manages a support information list in which support information items, which are information items to be supported, are registered in correspondence with the configuration of the device, a device configuration identification unit that identifies the configuration of a target device, which is the device from which information is to be collected, and a collection information list management unit that creates and manages a collection information list in which collection information items, which are information items to be collected of the target device, are registered, using the support information items registered in the support information list in correspondence with the configuration of the target device identified by the device configuration identification unit.

Description

[Technical field]

[0001] The present invention relates to a device information collection management device, a device information collection management system, a device information collection management method, and a program. [Background technology]

[0002] There are device information collection tools that automatically collect information required for troubleshooting and maintenance of devices such as information processing devices. However, as the specifications of information processing devices and the like have become more diverse and their architectures have become more complex, the amount of information to be collected has increased and become more diverse, making it difficult to collect sufficient information from the target information processing devices and the like.

[0003] For example, there is a setting information collection support system that collects setting information of each server in a computer system to which various servers with assigned roles are connected in order to facilitate computer recovery management. In this setting information collection support system, information collection items according to the role of the target server for which information is to be collected are stored in a collected information storage table as registry IDs and registry values, and the implementation SEQ number refers to the registry IDs and registry values ​​to collect setting information of the target server, thereby collecting setting information according to the server type (for example, see Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2008-77546 A Summary of the Invention [Problem to be solved by the invention]

[0005] The following analysis has been provided by the inventors of the present invention.

[0006] Depending on the information processing device, etc., there may be hardware that is not mounted or software that is not installed. Furthermore, previously mounted hardware may be removed, previously installed software may be deleted, and the configuration is constantly changing. However, the technology disclosed in Patent Document 1 does not take these into consideration. Therefore, depending on the information processing device, etc., information that is not necessary for information analysis (not mounted or not installed) may be collected. This results in wasted man-hours, such as checking unnecessary information.

[0007] The present invention has been made in consideration of the above circumstances, and has an object to provide a technique for supporting efficient collection of only necessary and sufficient information in an information processing device or the like. [Means for solving the problem]

[0008] According to a first aspect of the present invention, a support information list management unit that manages a support information list in which support information items, which are information items to be supported, are registered in association with the configuration of the device; a device configuration identification unit that identifies a configuration of a target device, which is a device from which information is to be collected; There is provided a device information collection and management device including: a collection information list management unit that creates and manages a collection information list in which collection information items, which are information items to be collected of the target device, are registered, using the support information items registered in the support information list in correspondence with the configuration of the target device identified by the device configuration identification unit.

[0009] According to a second aspect of the present invention, a support information list management device that manages a support information list in which support information items, which are information items to be supported, are registered in association with the configuration of the device; a collection information list management device that manages a collection information list in which collection information items, which are information items to be collected, of a target device, which is a device from which information is collected; an information collection device that collects information of the target device according to the collected information list and obtains configuration information that can identify a latest configuration of the target device; An apparatus information collection management system is provided in which the collection information list management device acquires the support information items to be registered in the support information list in correspondence with the latest configuration of the target device identified by the configuration information acquired by the information collection device, and creates the collection information list of the target device using the support information items.

[0010] According to a third aspect of the present invention, 1. A device information collection and management method executed by a computer, comprising: A configuration identification step of identifying a configuration of a target device which is a device from which information is to be collected; The present invention provides a device information collection and management method, which includes a collection information list management step of creating a collection information list in which collection information items, which are information items to be collected of the target device, are registered using support information items, which are information items supported by the configuration of the identified target device, which are registered in advance in correspondence with the configuration of the identified target device.

[0011] According to a fourth aspect of the present invention, On the computer, A configuration identification step of identifying a configuration of a target device, which is a device from which information is to be collected; A program is provided for executing a collection information list management procedure that creates a collection information list that registers collection information items, which are information items to be collected for the target device, using support information items, which are information items supported by the configuration of the identified target device, that are pre-registered in correspondence with the configuration of the target device.

[0012] The program can be recorded on a computer-readable storage medium. The storage medium can be a non-transient medium such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, etc. The present invention can also be embodied as a computer program product. Effect of the Invention

[0013] According to the present invention, only necessary and sufficient information can be efficiently collected from an information processing device or the like. [Brief description of the drawings]

[0014] [Figure 1] FIG. 2A is an overall view of an example of a device information collection management system of the present disclosure, and FIG. 2B is a functional block diagram of an example of a device information collection management device of the present disclosure. [Diagram 2] FIG. 13A is an explanatory diagram for explaining an example of a support information list of the present disclosure, and FIG. 13B is an explanatory diagram for explaining an example of a collection information list of the present disclosure. [Diagram 3] 1 is an overall view of an example of a device information collection management system according to the present disclosure. [Figure 4] 13 is a flowchart of an example of a list update process of the present disclosure. [Diagram 5] FIG. 13 is an overall view of an example of an apparatus information collection and management system according to a modified example of the present disclosure. [Figure 6] FIG. 13 is an overall view of an example of an apparatus information collection and management system according to a modified example of the present disclosure. [Figure 7] FIG. 13 is an overall view of an example of a server diagnostic chart service system according to a modified example of the present disclosure. [Figure 8] FIG. 13 is an explanatory diagram for explaining an example of a support information list according to a modified example of the present disclosure. [Figure 9] 2 is a diagram illustrating an example of a hardware configuration of a device information collection and management device according to the present disclosure. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] An outline of one embodiment of the present invention (hereinafter, referred to as the present embodiment) will be described below with reference to the drawings. Note that the reference symbols in the drawings are given to each element for convenience as an example to aid understanding, and are not intended to limit the present invention to the illustrated form. Furthermore, the connection lines between blocks in the drawings and the like referred to in the following description include both bidirectional and unidirectional lines. Unidirectional arrows are used to diagrammatically indicate the flow of the main signal (data), and do not exclude bidirectionality.

[0016] In addition, although there are ports and interfaces at the connection points of input and output of each block in the figure, they are not shown in the figure. In the following explanation, "A and / or B" means A or B, or A and B.

[0017] <<First embodiment>> First, a first embodiment of the present invention will be described. As shown in Fig. 1(a), an apparatus information collection management system 101 of this embodiment includes an apparatus information collection management device 100 and one or more target devices 500. The target devices 500 are information processing devices or the like from which information is collected. The apparatus information collection management device 100 and each target device 500 are connected, for example, via a network 102 or the like.

[0018] The target device 500 of this embodiment collects information about its own device according to a collected information list managed by the device information collection management device 100. The collected information list is a list in which collected information items, which are information items to be collected, are registered.

[0019] The device information collection management device 100 manages a support information list separately from the collected information list. The support information list is a list in which support information items, which are information items to be supported, are registered in association with the configurations (device configurations) of various devices. The support information list is always kept up to date.

[0020] The device information collection management device 100 identifies the latest device configuration of the target device 500, and generates a collected information list for the target device 500 using support information items registered in the support information list in association with the device configuration.

[0021] Fig. 1(b) shows functional blocks of the device information collection management device 100 of this embodiment that realizes the above. As shown in this figure, the device information collection management device 100 of this embodiment includes a support information list management unit 110, a device configuration identification unit 120, and a collected information list management unit 130. It may further include a storage unit 180. A support information list 200 and a collected information list 300 are stored in the storage unit 180.

[0022] The support information list 200 and / or the collected information list 300 may be stored in an external storage device capable of transmitting and receiving data to and from the device information collection management device 100. For example, the support information list 200 and / or the collected information list 300 may be stored in a data lake on a cloud server.

[0023] The support information list management unit 110 manages the support information list 200. As described above, the support information list 200 is a list in which support information items are registered in association with the configuration of the device. The configuration of the device is specified, for example, by the implemented hardware (HW) and the installed software (SW).

[0024] 2(a) shows an example of the support information list 200. As shown in this figure, support information items 230, which are items of information supported by the configuration (combination of HW and SW), are registered in the support information list 200 in association with information identifying HW (HW ID 210) and information identifying each SW (SW ID 220). The information supported by the configuration is information that should be collected when collecting information.

[0025] The support information list management unit 110 manages the support information list 200 according to instructions from a user. For example, the support information list 200 is updated every time new HW or new SW is introduced. Also, even for the same HW or SW, the support information list 200 is updated every time the supporting information is changed. In this embodiment, the support information list 200 is constantly updated and maintained in the latest state.

[0026] The device configuration identifying unit 120 identifies the latest configuration of the information processing device (target device 500) from which information is collected. The identified configuration is implemented HW and installed SW. The identified SW here is SW related to the operation of the entire device, such as an OS (Operation System). In this embodiment, for example, an execution log that acquires information on each HW and SW of the device information collected (collected) by the target device 500 is referenced, and the configuration of the target device 500 is identified based on the execution log.

[0027] The collected information list management unit 130 manages the collected information list 300. For example, the collected information list 300 is managed according to the identification result of the device configuration identification unit 120.

[0028] 2(b) shows an example of the collected information list 300. As described above, collected information items, which are items of information to be collected of the target device 500, are registered in the collected information list 300. As shown in this figure, the collected information list 300 includes information for identifying the target device 500 (device ID 310), information for identifying the device configuration of the target device 500 (HW ID and SW ID 320), and collected information items 330.

[0029] The collected information list management unit 130 registers the collected information items 330 of the target device 500, for example, by using the support information items 230 registered in the support information list 200 in association with the device configuration (HW ID 210 and SW ID 220) of the target device 500 identified by the device configuration identification unit 120. That is, the support information items 230 registered in association with the implemented HW and installed SW identified by the device configuration identification unit 120 are obtained from the support information list 200. Using these, the collected information list 300 is created.

[0030] As described above, according to this embodiment, information to be collected for each device configuration (HW and SW) is managed in a unified manner as the support information list 200. For each target device 500, a collected information list 300 that is always up to date can be automatically obtained from the support information list 200 according to the HW and SW configuration. In the target device 500, by collecting information according to this collected information list 300, optimal information can be collected for the current device configuration.

[0031] Generally, when an information collection tool is installed in each target device 500, it is necessary to install the information collection tool separately every time the configuration of the target device 500 changes. However, according to this embodiment, it is not necessary to manage the information collection tool for each individual device. It is sufficient to keep only the support information list 200, in which the support information items 230 are registered for each combination of HW and SW, up to date. This does not increase the workload of the administrator.

[0032] According to this embodiment, it is possible to assist in efficiently collecting only necessary and sufficient information regarding each information processing device or the like.

[0033] <<Second embodiment>> Next, a second embodiment of the present invention will be described. In this embodiment, the existing lists are confirmed based on the configuration of the target device 500, and the support information list 200 and the collected information list 300 of the target device 510 are updated as necessary.

[0034] An example of the device information collection management system 101a of this embodiment is shown in Fig. 3. As shown in this figure, the device information collection management system 101a of this embodiment includes a device information collection management device 100 and a target device 510. Both are connected via a network 102 or the like. Note that, although a case where one target device 510 is included is shown here as an example, the number of target devices 510 is not limited.

[0035] In this embodiment, for example, the target device 510 collects device information at a predetermined timing and transmits it to the device information collection management device 100. The transmitted device information includes information (configuration information) capable of identifying the configuration (HW and SW) of the target device 510 itself. The device information may be transmitted to the device information collection management device 100 every time it is collected (collected), or the timing of collection and the timing of transmission to the device information collection management device 100 may be asynchronous. The device information collection management device 100 updates the support information list 200 and the collected information list 300 according to the configuration information.

[0036] The target device 510 includes a device information collection utility 511 for collecting device information of the target device itself.

[0037] The device information collection utility 511 collects device information of the device itself according to the collected information list 300 registered for the device itself in the device information collection management device 100. For example, the device information collection management device 100 is accessed, and the collected information list 300 in which the device ID of the device itself is registered in the device ID 310 is extracted and used.

[0038] The device information collection utility 511 collects configuration information capable of identifying the device configuration (HW and SW) of its own device at a predetermined timing or in response to a specific event, an instruction from a user, or the like, and transmits the information together with the collected device information to the device information collection management device 100. The transmitted device information is provided with information identifying the target device 510 that is the transmission source, for example, a device ID.

[0039] The functional configuration of the device information collection management device 100 is the same as that of the first embodiment shown in Fig. 1(b) hereinafter, the device information collection management device 100 will be described with a focus on the configuration that is different from the first embodiment.

[0040] When the device configuration identifying unit 120 of this embodiment receives device information including configuration information, it identifies HW implemented in the target device 510 that is the transmission source and SW installed therein.

[0041] In this embodiment, when the device configuration specifying unit 120 specifies HW and SW from the configuration information, the support information list management unit 110 performs a support information list update process. Specifically, it determines whether the combination of HW and SW specified by the device configuration specifying unit 120 is registered in the support information list 200. If the combination is not registered, the support information list management unit 110 adds a (default) support information item 230 prepared in advance for the combination to the support information list 200. The addition is notified to, for example, the collected information list management unit 130. The default support information items 230 may include, for example, all collectable information.

[0042] In addition, when the device configuration identification unit 120 identifies HW and SW from the configuration information, the collected information list management unit 130 of this embodiment performs a collected information list update process. The collected information list update process is a process of determining whether the collected information item 330 of the target device 510 should be updated, and updating it if it should be updated.

[0043] Specifically, as in the first embodiment, the collected information list management unit 130 acquires support information items 230 that are registered in the support information list 200 in association with the device configuration (HW ID 210 and SW ID 220) of the target device 510 identified by the device configuration identification unit 120.

[0044] Then, it is compared with the existing collected information item 330 in the collected information list 300 to be managed, i.e., to determine whether there is a difference. In this embodiment, the collected information item 330 in the collected information list 300 whose device ID 310 matches the device ID assigned to the configuration information is compared. If there is no difference, the collected information list 300 of the target device 510 is maintained as is. On the other hand, if there is a difference, the acquired support information item 230 is made the collected information item 330 in the collected information list 300 of the target device 510. In other words, the collected information item 330 is replaced with the acquired support information item 230, and the collected information list 300 is updated.

[0045] [List update process] The flow of list update processing including support information list update processing and collected information list update processing by the device information collection management device 100 of this embodiment will be described. Fig. 4 shows the process flow of the list update processing of this embodiment. This processing is started when device information including configuration information is received from the target device 510.

[0046] First, the device configuration identifying unit 120 identifies the HW and SW of the target device 510 that is the transmission source (step S1101).

[0047] The support information list management unit 110 determines whether the identified combination of HW and SW is registered in the support information list 200 (step S1102).

[0048] If no registration has been made (S1102; No), the support information list management unit 110 updates the support information list 200 (step S1110). Here, the default collection information item is added to the support information list 200 as the support information item 230 in association with the combination of HW and SW identified in step S1101. The process proceeds to step S1103 described below.

[0049] On the other hand, if registered (S1102; Yes), the collected information list management unit 130 acquires (extracts) the support information item 230 registered in association with the identified combination of HW and SW from the support information list 200 (step S1103).

[0050] Furthermore, the collected information list management unit 130 determines whether or not there is a registration in the collected information list 300 having the device ID received together with the configuration information (step S1104).

[0051] If there is registration (S1104; Yes), the collected information list management unit 130 compares the collected information items 330 in the current collected information list 300 of the target device 510 with the support information items 230 (step S1105). Then, it is determined whether there is a difference (step S1106).

[0052] If there is a difference between the two (S1106; Yes), the collected information list management unit 130 updates the collected information list 300 (step S1107) and ends the process. Here, the collected information item 330 in the current collected information list 300 is replaced with the support information item 230 extracted in step S1103.

[0053] On the other hand, if there is no difference between the two (S1106; No), the collected information list management unit 130 maintains the collected information list 300 as is (step S1108), and ends the process.

[0054] If it is determined in step S1104 that there is no registration (S1104; No), the collected information list management unit 130 creates a new collected information list 300 using the extracted support information item 230 (step S1109), and ends the process. Here, the device ID received together with the configuration information is used for the device ID 310, the information specified in step S1101 is used for the HW ID and SW ID 320, and the extracted support information item 230 is used for the collected information item 330.

[0055] As described above, according to this embodiment, as in the first embodiment, the collected information list 300 in which the collected information items 330 are listed can be automatically and always updated according to the latest HW and SW configuration for each target device 510. The target device 510 can always collect optimal information by collecting information according to the latest collected information list 300.

[0056] Furthermore, according to this embodiment, it is not necessary to install an information collection tool individually every time the configuration of the target device 510 changes. Also, it is not necessary to manage an information collection tool for each individual device. It is sufficient to keep only the support information list 200, which lists the collected information items for each combination of HW and SW, up to date. For example, even if the target devices 510 are installed in multiple locations, there is no need to apply them individually. As a result, it is possible to reduce the number of work steps involved in application and to respond without being aware of the operating status of the target devices 510.

[0057] Furthermore, according to this embodiment, even when a new device is added as a target device 510, the support information list 200 is automatically updated. Therefore, the information items to be collected for each target device 510 can be maintained at an optimal level without increasing the workload of the administrator.

[0058] That is, according to this embodiment, by flexibly creating (updating) the collected information list 300 for each device (target device 510) from which information is to be collected, it is possible to collect only the information that is optimal (necessary) for the target device 510. As a result, it is possible to reduce the amount of information to be collected and shorten the collection time. It is also possible to prevent unnecessary man-hours, such as checking information that is not necessary for information analysis (not implemented or installed). Therefore, information can be collected efficiently, and the collected information can be used efficiently.

[0059] According to this embodiment, it is possible to assist the administrator in efficiently collecting only the necessary and sufficient information regarding each information processing device without increasing the workload of the administrator.

[0060] <Variation 1> In the above embodiment, the device information collection management device 100 is an independent device, but is not limited to this. For example, the device information collection management device 100 may be a function within the management server 710 that manages the target device 510.

[0061] That is, each function of the device information collection management device 100 may be incorporated into an existing system configured with the management server 710 and the target device 510 for use.

[0062] In the second embodiment, the device information collection management device 100 stores the collected information list 300 of each target device 510, but is not limited to this. For example, the collected information list 300 itself may be held by the target device 510.

[0063] The configuration of the information collection management system 701 in this case is shown in Fig. 5. As shown in this figure, the information collection management system 701 of this modified example includes a target device 510a and a management server 710. The two are connected, for example, via a network 102. Note that, even in this modified example, the number of target devices 510a connected to the management server 710 is not limited.

[0064] The management server 710 includes an apparatus information collection management unit 100a. The apparatus information collection management unit 100a basically has the same functions as the apparatus information collection management apparatus 100 of the second embodiment. As described later, the collected information list 300 is held by the target apparatus 510a, so the storage unit 180 does not hold the collected information list 300. However, the management server 710 may hold a copy of the latest collected information list 300 for each target apparatus 510a in a storage device.

[0065] On the other hand, the target device 510a includes a device information collection utility 511a. Also, the storage device includes a collected information list 300. The device information collection utility 511a collects information on items registered in the collected information list 300, just like the function of the same name described above. Also, it obtains configuration information of the target device 510a and transmits it to the management server 710.

[0066] In this modification, during list update processing, the collected information list management unit 130 accesses the target device 510a, collects and processes the current collected information list 300. Then, after updating or creating the collected information list 300, it is handed over to the target device 510a.

[0067] In this modification, like the first embodiment, the device information collection management unit 100a may not need to compare the collected information with the current collected information list 300. In this case, every time configuration information is received from the target device 510a, the latest collected information list 300 may be created using the corresponding registered support information items 230, and handed over to the target device 510a.

[0068] <Variation 2> Furthermore, the target device 510b may have further functions other than those of the device information collection management device 100. An example of a device information collection management system 702 in which the functions are distributed is shown in FIG.

[0069] As shown in the figure, the device information collection management system 702 includes a management server 720 and a target device 510b. The two are connected, for example, via a network 102. Note that, even in this modified example, the number of target devices 510b is not limited. Note that, in FIG. 6, the portion surrounded by a dashed line corresponds to the device information collection management device 100 in each of the above embodiments.

[0070] The target device 510b includes a device information collection utility 511b. The device information collection utility 511b of this modification includes a device configuration specifying unit 120 and a collected information list management unit 130. The target device 510b also includes a collected information list 300 in a storage device or the like. The device configuration specifying unit 120 and the collected information list management unit 130 have basically the same functions as the configurations of the same names in the above embodiments.

[0071] On the other hand, the management server 720 includes a support information list management unit 110, and for example, in a storage device thereof, the support information list 200. The support information list management unit 110 also has basically the same functions as the configuration of the same name in each of the above embodiments.

[0072] When the device information collection utility 511b of the target device 510b is started, it accesses the management server 720 and acquires the support information items 230 of the target device 510b.

[0073] The device configuration identification unit 120 and the collected information list management unit 130 in the device information collection utility 511b update (maintain) the collected information list 300 according to the process from step S1105 onward in the list update process using the acquired support information items 230. This allows the collected information list 300 to always be optimal for the current configuration of the target device 510b.

[0074] The device information collection utility 511b collects device information according to the collected information list 300 that has been updated (created) thereafter.

[0075] <Modification 3> The function of the device information collection and management device 100 may be incorporated into another system. For example, a case where the device cooperates with a server diagnostic chart service, which is an existing service, will be described. Fig. 7 is an overall view of a server diagnostic chart service system 600 of this modified example.

[0076] The Server Diagnostic Chart Service visualizes "unusual behavior" that occurs during system operation and periodically provides information as a diagnostic chart, thereby supporting the stable operation of the target device 500. For example, you can easily check the application status of OS update programs that are often overlooked, and comprehensive diagnostic comments according to the operating status of the target device 500, which can be used to implement early countermeasures and manage the operation of IT systems.

[0077] The server diagnostic chart service system 600 includes a target device 500, a management server 610, and a cloud server 630. The target device 500, the management server 610, and the cloud server 630 are connected, for example, via a network.

[0078] The management server 610 collects information on the target device 500, and reports any abnormality that is found. The device information collection management device 100 of this modified example is realized as part of the management server 610. In the following, since the functions of the device information collection management device 100 are incorporated into the management server 610 and used in this modified example, it is referred to as a device information collection management unit 100c.

[0079] That is, the management server 610 includes a management unit 620 that collects information and execution logs of the target device 500, and a device information collection management unit 100c. The management unit 620 accesses the target device 500 to collect device information and execution logs. Specifically, the management unit 620 realizes a device management function and a notification log receiving function.

[0080] The device management function is responsible for configuration, failure, and operation management of multiple servers (target devices 500). The device management function manages the HW configuration and SW configuration of each server (target device 500). It also reports abnormalities that may lead to system downs or failures, and acquires various information for identifying the cause in the unlikely event of a failure. It also monitors the usage status of the server (target device 500), such as the CPU load rate, free disk space, and LAN traffic.

[0081] The management unit 620 acquires configuration information including the HW configuration and SW configuration of the server (target device 500), for example, at a predetermined time interval, and stores the information in the data lake of the cloud server 630. Note that the time interval is not limited to a predetermined time interval. For example, the configuration information may be acquired in response to an instruction from a user.

[0082] The notification log receiving function receives a log of notifications sent by the fault notification service.

[0083] The cloud server 630 includes a data lake in which the information collected by the management server 610 is stored in its original form without processing. For example, device information and execution logs of the target devices 500 are stored in the data lake. These are accumulated in association with the acquisition time. In this modification, the data lake may also include a collected information list 300 created and updated by the device information collection management unit 100c. The collected information list 300 is registered for each target device 500 in association with information that identifies the target device 500.

[0084] The device information collection management unit 100c realizes the same functions as the device information collection management device 100 in each of the above embodiments. Each function is basically the same as the function with the same name in each of the above embodiments, so a description thereof will be omitted.

[0085] However, in this modification, as described above, the collection information list 300 is stored in the data lake of the cloud server 630. Note that a copy of the collection information list 300 stored in the cloud server 630 may be stored in the storage unit 180.

[0086] The support information list 200 is stored in, for example, a storage device of the management server 610.

[0087] The device configuration identifying unit 120 acquires an execution log including configuration information from the data lake of the cloud server 630. In addition, the collected information list managing unit 130 acquires the latest collected information list 300 of the target device 500 from the data lake of the cloud server 630. Note that information identifying the target device 500 is notified from the managing unit 620 to the device information collection managing unit 100c.

[0088] Furthermore, in this modification, as described above, in the server diagnostic chart service system 600, the management server 610 (management unit 620) performs configuration management. For example, the list update process may be started when the management server 610 acquires configuration information of the target device 500 and stores it in the data lake of the cloud server 630. The device configuration identification unit 120 acquires the latest configuration information of the target device 500 accumulated in the data lake of the cloud server 630, and identifies the HW and SW of the target device 500 based on the latest information.

[0089] Furthermore, when the collected information list management unit 130 updates (creates) the collected information list 300 by the list update process, the collected information list 300 is stored in the data lake of the cloud server 630 in association with information that identifies the target device 500.

[0090] As in this modified example, by linking with the function of the server diagnostic chart service system 600, the device information collection management unit 100c periodically updates (creates) the collected information list 300. Then, the server diagnostic chart service system 600 can automatically collect optimal information according to the latest device configuration.

[0091] <Modification 4> In the above embodiment, the support information list 200 is created for each HW, but is not limited to this. For example, HW having the same collected information for each SW may be grouped and prepared for each group. An example of grouping by model is shown in FIG. 8.

[0092] In this case, the support information list 200 includes a device information list 290 and a support information list 201 .

[0093] The device information list 290 is obtained by grouping information specifying HW (HW ID 291) and assigning a group number 292 to the information.

[0094] On the other hand, the support information list 201 is a list in which support information items 230 for each piece of information (SW ID 220) that identifies a SW are registered for each group. Here, as an example, the support information list 201 for the group number 292 of "2" is shown. The support information list 201 is prepared for each group in the device information list 290.

[0095] The device configuration identifying unit 120 first accesses the device information list 290 , identifies the group number 292 of the corresponding HW, and then accesses the support information list 201 of the group number 292 to acquire the support information item 230 .

[0096] At this time, as shown in the figure, for example, for option cards (PCI (Peripheral Component Interconnect) Devices), a support information item 230 may be managed for each piece of identifying information (PCI ID 240).

[0097] The device configuration specification unit 120 checks the PCI device information from the configuration information and determines whether each PCI device is installed or not. If the PCI device is installed, the collected information list management unit 130 extracts the corresponding support information item 230 from the support information list 201.

[0098] <Variation 5> In each of the above embodiments, the support information list 200 (or the support information list 201) is configured by a combination of HW and SW. However, this is not limited to this. For example, a purpose may be further taken into consideration. For example, when a failure occurs, when maintenance and inspection are performed, etc. Furthermore, when a failure occurs, the support information lists 200 and 201 may be configured in more detail according to the location of the failure.

[0099] In this case, for example, the collection information list 300 may also be created for each purpose.

[0100] <Variation 6> In the above embodiment, if a combination of HW and SW identified from the configuration information is not registered in the support information list 200, default collection information is registered as the support information item 230, but this is not limited to this.

[0101] For example, collected information items included in the transmitted device information including configuration information may be extracted and registered as the default support information items 230 (and collected information items 330).

[0102] Furthermore, a configuration may be adopted in which a notification is sent to an administrator (user) when the support information list 200 is updated. The user is notified and can maintain the support information list 200 in an optimal state.

[0103] In addition, in the above embodiment, during list update processing, the collected information items 330 in the current collected information list 300 are compared with the support information items 230, but a comparison with items included in the transmitted device information may also be made.

[0104] [Hardware configuration] The device information collection and management device 100 is realized, for example, by a general-purpose information processing device.

[0105] A general-purpose information processing device includes, for example, a CPU (Central Processing Unit) 691, a main memory device (memory) 692, an auxiliary memory device 693, a communication I / F 694, and an expansion I / F 695, which are interconnected by an internal bus, as shown in FIG.

[0106] The CPU 691, for example, loads a program stored in the auxiliary storage device 693 into the main storage device 692 and executes the program to realize the above-mentioned functions and to comprehensively control the entire device information collection and management device 100. Note that the CPU 691 may be replaced by one or more processors such as an MPU (Micro Processing Unit).

[0107] The main storage device 692 is a memory such as a RAM (Random Access Memory), etc. The main storage device 692 is a work area when the CPU 691 processes the programs executed by the device information collection management device 100, etc.

[0108] The auxiliary storage device 693 is, for example, a read only memory (ROM), a hard disk drive (HDD), a solid state drive (SSD), etc. The auxiliary storage device 693 stores various programs executed by the device information collection management device 100. The auxiliary storage device 693 may include a storage medium such as a flexible disk, a hard disk, an optical disk, a CD-ROM, a CD-R, a magnetic tape, a non-volatile memory card, a DVD, etc.

[0109] The programs stored in the auxiliary storage device 693 can be provided as program products recorded on a non-transitory computer-readable storage medium. The auxiliary storage device 693 can be used to store various programs recorded on the non-transitory computer-readable storage medium for a medium to long term.

[0110] The communication I / F 694 is an interface for inputting and outputting signals and data via wired or wireless communication. Note that the communication I / F 694 is not necessarily required.

[0111] The expansion I / F 695 is an interface for connecting a display device, an input device, etc. The display device is, for example, a liquid crystal monitor, etc. The input device is, for example, a device that accepts user operations such as a keyboard or a mouse.

[0112] Each of the above-mentioned functions (each server) of device information collection management device 100 is realized by CPU 691 loading a program stored in auxiliary storage device 693 into main storage device 692 and executing the program.

[0113] The storage unit 180 is constructed in, for example, the auxiliary storage device 693.

[0114] The hardware configuration of the device information collection and management device 100 is not limited to this, and may include hardware not shown.

[0115] In addition, a program for realizing each of the above-mentioned functions of the device information collection management device 100 of this embodiment can be recorded in a computer-readable storage medium. The storage medium can be a non-transient medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. The present invention can also be embodied as a computer program product.

[0116] In addition, each function of the device information collection and management device 100 may be implemented, for example, by an integrated circuit (IC) dedicated to each process, an application specific integrated circuit (ASIC), a system on chip (SOC), a field programmable gate array (FPGA), or the like.

[0117] Similarly, the management server 710 and the target device 500 are realized by a general-purpose information processing device shown in FIG. 9 or a dedicated circuit or the like.

[0118] In the process flow used in the above description, multiple steps (processes) are described in order, but the order of execution of each step is not limited to the order described. For example, the order of the steps shown in the figure can be changed to a range that does not affect the content, such as executing each process in parallel.

[0119] Although the embodiments and modifications of the present invention have been described above, the present invention is not limited to the above-mentioned embodiments, and various modifications that can be understood by those skilled in the art can be made. Each embodiment and modification can be appropriately combined with other embodiments. For example, the network configuration and the configuration of each element shown in each drawing are examples to help understand the present invention, and the present invention is not limited to the configurations shown in these drawings.

[0120] Finally, preferred embodiments of the present invention will be summarized as follows: A part or all of the above-described embodiments can be described as follows, but are not limited to the following. (Appendix 1) a support information list management unit that manages a support information list in which support information items, which are information items to be supported, are registered in association with the configuration of the device; a device configuration identification unit that identifies a configuration of a target device, which is a device from which information is to be collected; a collection information list management unit that creates and manages a collection information list that registers collection information items, which are information items to be collected for the target device, using the support information items registered in the support information list in correspondence with the configuration of the target device identified by the device configuration identification unit. (Appendix 2) In the device information collection and management device according to claim 1, It is desirable for the collection information list management unit to compare the collection information items in the collection information list of the target device that it manages with the support information items registered in the support information list in correspondence with the configuration of the target device, and if there is a difference, to update the collection information items in the collection information list that it manages to the support information items. (Appendix 3) In the device information collection and management device according to claim 1 or 2, It is desirable for the collection information list management unit to compare the collection information items in the collection information list of the target device that it manages with the support information items registered in the support information list in correspondence with the configuration of the target device, and if there are no differences, to maintain the collection information list that it manages. (Appendix 4) In the device information collection and management device according to any one of Supplementary Note 1 to 3, If the support information item is not registered in the support information list in correspondence with the configuration of the target device, it is desirable for the support information list management unit to register a pre-prepared information item as the support information item in the support information list in correspondence with the configuration of the target device. (Appendix 5) 5. The device information collection and management device according to claim 1, The configuration of the device preferably includes hardware implemented in the device and software installed in the device. (Appendix 6) 6. The device information collection and management device according to claim 1, It is preferable that the configuration of the device further includes a device connected to a PCI (Peripheral Component Interconnect). (Appendix 7) a support information list management device that manages a support information list in which support information items, which are information items to be supported, are registered in association with the configuration of the device; a collection information list management device that manages a collection information list in which collection information items, which are information items to be collected, of a target device, which is a device from which information is collected; an information collection device that collects information of the target device according to the collected information list and obtains configuration information that can identify a latest configuration of the target device; The collection information list management device acquires the support information items to be registered in the support information list in correspondence with the latest configuration of the target device identified by the configuration information acquired by the information collection device, and creates the collection information list of the target device using the support information items. (Appendix 8) 1. A device information collection and management method executed by a computer, comprising: A configuration identification step of identifying a configuration of a target device which is a device from which information is to be collected; A device information collection and management method comprising: a collection information list management step of creating a collection information list in which collection information items, which are information items to be collected of the target device, are registered using support information items, which are information items supported by the configuration of the identified target device, which are registered in advance in correspondence with the configuration of the identified target device. (Appendix 9) On the computer, A configuration identification step of identifying a configuration of a target device, which is a device from which information is to be collected; A program for executing a collection information list management procedure that creates a collection information list that registers collection information items, which are information items to be collected of the target device, using support information items, which are information items supported by the configuration of the identified target device, that are pre-registered in correspondence with the configuration of the identified target device. In addition, the forms of Appendices 8 and 9 can be expanded into the forms of Appendices 2-6, similar to Appendices 1.

[0121] The disclosures of the above patent documents and the like are incorporated herein by reference. Within the framework of the entire disclosure of the present invention (including the scope of claims), and further based on the basic technical idea, modifications and adjustments of the embodiments and modifications are possible. Furthermore, within the framework of the disclosure of the present invention, various combinations and selections of various disclosed elements (including each element of each claim, each element of each embodiment or modification, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes various modifications and corrections that a person skilled in the art would be able to make according to the entire disclosure including the scope of claims and the technical idea. In particular, with regard to the numerical ranges described in this specification, any numerical value or subrange included in the range should be interpreted as being specifically described even if not otherwise specified. [Explanation of symbols]

[0122] 100: device information collection management device, 100a: device information collection management unit, 100c: device information collection management unit, 101: device information collection management system, 101a: device information collection management system, 102: network, 110: support information list management unit, 120: device configuration identification unit, 130: collected information list management unit, 180: storage unit, 200: Support information list, 201: Support information list, 210: HW ID, 220: SW ID, 230: Support information item, 240: PCI ID, 290: Device information list, 291: HW ID, 292: Group number, 300: collected information list, 310: device ID, 320: HW ID and SW ID, 330: collected information item, 500: target device, 510: target device, 510a: target device, 510b: target device, 511: device information collection utility, 511a: device information collection utility, 511b: device information collection utility, 600: Server diagnostic chart service system, 610: Management server, 620: Management unit, 630: Cloud server, 691: CPU, 692: main memory device, 693: auxiliary memory device, 694: communication I / F, 695: expansion I / F, 701: information collection management system, 702: device information collection management system, 710: management server, 720: management server

Claims

1. a support information list management unit that manages a support information list in which support information items, which are information items to be supported, are registered in association with the configuration of the device; a device configuration identification unit that identifies a configuration of a target device, which is a device from which information is to be collected; a collection information list management unit that creates and manages a collection information list that registers collection information items, which are information items to be collected for the target device, using the support information items registered in the support information list in correspondence with the configuration of the target device identified by the device configuration identification unit.

2. 2. The device information collection and management device according to claim 1, The collection information list management unit of the device information collection management device compares the collection information items in the collection information list of the target device that it manages with the support information items registered in the support information list in correspondence with the configuration of the target device, and if there is a difference, updates the collection information items in the collection information list that it manages to the support information items.

3. 2. The device information collection and management device according to claim 1, The collection information list management unit of the device information collection management device compares the collection information items in the collection information list of the target device that it manages with the support information items registered in the support information list in correspondence with the configuration of the target device, and if there are no differences, maintains the collection information list that it manages.

4. 2. The device information collection and management device according to claim 1, The support information list management unit, when the support information item is not registered in the support information list in correspondence with the configuration of the target device, registers a pre-prepared information item as the support information item in the support information list in correspondence with the configuration of the target device, in a device information collection and management device.

5. 2. The device information collection and management device according to claim 1, The configuration of the device includes hardware implemented in the device and software installed in the device.

6. 6. The device information collection and management device according to claim 5, The configuration of the device further includes a device connected to a PCI (Peripheral Component Interconnect).

7. a support information list management device that manages a support information list in which support information items, which are information items to be supported, are registered in association with the configuration of the device; a collection information list management device that manages a collection information list in which collection information items, which are information items to be collected, of a target device, which is a device from which information is collected; an information collection device that collects information of the target device according to the collected information list and obtains configuration information that can identify a latest configuration of the target device; The collection information list management device acquires the support information items to be registered in the support information list in correspondence with the latest configuration of the target device identified by the configuration information acquired by the information collection device, and creates the collection information list of the target device using the support information items.

8. 1. A device information collection and management method executed by a computer, comprising: A configuration identification step of identifying a configuration of a target device which is a device from which information is to be collected; A device information collection and management method comprising: a collection information list management step of creating a collection information list in which collection information items, which are information items to be collected of the target device, are registered using support information items, which are information items supported by the configuration of the identified target device, which are registered in advance in correspondence with the configuration of the identified target device.

9. On the computer, A configuration identification step of identifying a configuration of a target device, which is a device from which information is to be collected; A program for executing a collection information list management procedure that creates a collection information list that registers collection information items, which are information items to be collected of the target device, using support information items, which are information items supported by the configuration of the identified target device, that are pre-registered in correspondence with the configuration of the identified target device.

Images