Device information collection management apparatus, device information collection management system, device information collection management method and program

Abstract

To efficiently collect only necessary and sufficient information regarding an information processing apparatus, and the like.SOLUTION: A device information collection management apparatus includes: a support information list management unit which manages a support information list formed by registering support information items, which are information items to be supported, in association with the configuration of a device; a device configuration specifying unit which specifies the configuration of a target device which is the device for which information is collected; and a collected information list management unit which creates and manages a collected information list formed by registering collection information items, which are information items to be collected, of the target device, using the support information items registered in the support information list in association with the configuration of the target device specified by the device configuration specifying unit.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an apparatus information collection management apparatus, an apparatus information collection management system, an apparatus information collection management method, and a program.

Background Art

[0002] There is an apparatus information collection tool that automatically collects information necessary for troubleshooting and maintenance of apparatuses such as information processing apparatuses. However, due to the diversification of the specifications of information processing apparatuses and the like and the complication of the architecture, the amount of information to be collected has increased and diversified, making it difficult to collect sufficient information necessary for the target information processing apparatuses and the like.

[0003] For example, in order to facilitate the recovery management of a computer, there is a setting information collection support system that collects the setting information of each server in a computer system to which various servers having set functions are connected. In this setting information collection support system, information collection items corresponding to the role of the target server for collecting information are stored in a collection information storage table as registry IDs and registry values, and the setting information of the target server is collected by referring to the registry IDs and registry values for the execution SEQ number, thereby collecting setting information according to the server type (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The following analysis is provided by the inventor of the present invention.

[0006] Depending on the information processing device or the like, there may be unimplemented hardware or uninstalled software. Also, the hardware that was implemented in the past may be removed, or the installed software may be deleted, and the configuration is constantly changing. However, in the technology disclosed in Patent Document 1, these are not considered. Therefore, depending on the information processing device or the like, information that is unnecessary (unimplemented / uninstalled) for information analysis may be collected. This results in wasted man-hours such as checking unnecessary information.

[0007] The present invention has been made in view of the above circumstances, and an object thereof is to provide a technology for efficiently collecting only necessary and sufficient information with respect to an information processing device or the like.

Means for Solving the Problems

[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 specifying unit that specifies the configuration of a target device, which is the device for which information is to be collected; 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 from the target device, are registered using the support information items registered in the support information list in association with the configuration of the target device specified by the device configuration specifying unit. An apparatus information collection management apparatus is provided.

[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 from a target device, which is the device for which information is to be collected, are registered; An information collection device that collects information on the target device and acquires configuration information that can identify the latest configuration of the target device according to the collected information list. The collected information list management device acquires the support information items registered in the support information list in association with the latest configuration of the target device specified by the configuration information acquired by the information collection device, and creates the collected information list of the target device using the support information items. An apparatus information collection management system is provided.

[0010] According to a third aspect of the present invention, An apparatus information collection management method executed by a computer, A configuration specifying step of specifying the configuration of a target device which is a device for collecting information, A collected information list management step of creating a collected information list in which collected information items, which are information items to be collected for the target device, are registered using support information items which are information items supported by the registered configuration in association with the specified configuration of the target device. An apparatus information collection management method is provided.

[0011] According to a fourth aspect of the present invention, A program for causing a computer to Execute a configuration specifying procedure for specifying the configuration of a target device which is a device for collecting information, And a collected information list management procedure for creating a collected information list in which collected information items, which are information items to be collected for the target device, are registered using support information items which are information items supported by the registered configuration in association with the specified configuration of the target device is provided.

[0012] Note that this program can be recorded on a computer-readable storage medium. The storage medium can be a non-transient one 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, regarding an information processing apparatus and the like, only necessary and sufficient information can be efficiently collected. [Brief Description of the Drawings]

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

[0015] Hereinafter, an overview of an embodiment of the present invention (hereinafter referred to as this embodiment) will be described with reference to the drawings. Note that the reference numerals in the drawings are appended to each element for convenience as an example to aid understanding, and are not intended to limit the present invention to the illustrated embodiments. Also, the connection lines between blocks in the drawings and the like referred to in the following description include both bidirectional and unidirectional ones. The one-way arrow schematically shows the flow of the main signal (data) and does not exclude bidirectionality.

[0016] Also, ports and interfaces exist at the connection points of the inputs and outputs of each block in the figure, but their illustration is omitted. Also, in the following description, "A and / or B" is used to mean A or B, or A and B.

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

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

[0019] The device information collection and management device 100 manages a support information list separately from the collection 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 maintained in the latest state.

[0020] In the device information collection and management device 100, the latest device configuration of the target device 500 is identified, and the collection information list of the target device 500 is generated using the support information items registered in the support information list corresponding to the device configuration.

[0021] The functional blocks of the device information collection and management device 100 of the present embodiment that achieve the above are shown in FIG. 1(b). As shown in this figure, the device information collection and management device 100 of the present embodiment includes a support information list management unit 110, a device configuration identification unit 120, and a collection information list management unit 130. Further, a storage unit 180 may be provided. The storage unit 180 stores a support information list 200 and a collection information list 300.

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

[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 corresponding to the configuration of the device. The configuration of the device is specified by, for example, the installed hardware (HW) and the installed software (SW).

[0024] An example of the support information list 200 is shown in FIG. 2(a). As shown in this figure, in the support information list 200, support information items 230, which are items of information supported by the configuration (combination of HW and SW), are registered corresponding to the information (HW ID 210) for specifying the HW and the information (SW ID 220) for specifying each SW. The information supported by the configuration is the information to be collected during information collection.

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

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

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

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

[0029] The acquisition information list management unit 130 registers the acquisition information items 330 of the target device 500 by using, for example, 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 specified by the device configuration specifying unit 120. That is, the support information items 230 registered in association with the implemented HW and installed SW specified by the device configuration specifying unit 120 are acquired from the support information list 200. Using these, an acquisition information list 300 is created.

[0030] As described above, according to the present embodiment, the information to be acquired for each device configuration (HW and SW) is centrally managed as the support information list 200. For each target device 500, an acquisition information list 300 that is always up-to-date can be automatically obtained from the support information list 200 according to its HW and SW configurations. In the target device 500, by acquiring information according to this acquisition information list 300, the optimal information in the current device configuration can be acquired.

[0031] Generally, when an information acquisition tool is installed in each individual target device 500, it is necessary to install the information acquisition tool individually every time the configuration of the target device 500 changes. However, according to the present embodiment, there is no need to manage the information acquisition tool for each individual device. It is only necessary to keep the support information list 200 in which the support information items 230 are registered up-to-date for each combination of HW and SW. For this reason, the labor on the administrator side is not increased.

[0032] According to the present embodiment, it is possible to efficiently support the acquisition of only necessary and sufficient information for each information processing device and the like.

[0033] <<Second Embodiment>> Next, a second embodiment of the present embodiment will be described. In this embodiment, based on the configuration of the target device 500, an existing list is checked, and if necessary, the support information list 200 and the acquisition information list 300 of the target device 510 are updated.

[0034] An example of the device information collection and management system 101a according to this embodiment is shown in FIG. 3. As shown in this figure, the device information collection and management system 101a according to this embodiment includes a device information collection and management device 100 and a target device 510. Both are connected by a network 102 or the like. Here, as an example, the case where one target device 510 is provided is shown, but 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 and management device 100. The transmitted device information includes information (configuration information) that can identify the configuration (HW and SW) of the own device (target device 510). Note that the device information may be transmitted to the device information collection and management device 100 every time it is collected (acquired), or the collection timing and the transmission timing to the device information collection and management device 100 may be asynchronous. The device information collection and management device 100 updates the support information list 200 and the acquisition information list 300 according to the configuration information.

[0036] The target device 510 includes a device information collection utility 511 that collects the device information of the own device.

[0037] The device information collection utility 511 collects the device information of the own device according to the acquisition information list 300 registered for the own device in the device information collection and management device 100. For example, it accesses the device information collection and management device 100, extracts and uses the acquisition information list 300 in which the device ID of the own device is registered in the device ID 310.

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

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

[0040] When the device configuration specifying unit 120 of this embodiment receives device information including configuration information, it specifies the HW installed in the target device 510 of the transmission source and the SW installed.

[0041] When the device configuration specifying unit 120 of this embodiment specifies HW and SW from the configuration information, the support information list management unit 110 of this embodiment 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. And if it is not registered, it adds the (default) support information item 230 prepared in advance with the combination to the support information list 200. Note that, for example, it notifies the collection information list management unit 130 of the addition. The default support information item 230 may include, for example, all collectable information.

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

[0043] Specifically, the collection information list management unit 130, similar to the first embodiment, acquires the support information item 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 510 specified by the device configuration specifying unit 120.

[0044] Then, it is compared with the existing collection information items 330 of the collection information list 300 to be managed, and the presence or absence of differences is determined. In this embodiment, the collection information items 330 of the collection information list 300 whose device ID matches the device ID 310 assigned to the configuration information are compared. If there is no difference, the collection information list 300 of the target device 510 is maintained as it is. On the other hand, if there is a difference, the acquired support information item 230 is set as the collection information item 330 of the collection information list 300 of the target device 510. That is, the collection information item 330 is replaced with the acquired support information item 230, and the collection information list 300 is updated.

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

[0046] First, the device configuration specifying unit 120 specifies the HW and SW of the source target device 510 (step S1101).

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

[0048] Here, if it is not registered (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 specified in step S1101. The process proceeds to step S1103 described later.

[0049] On the one hand, if it is registered (S1102; Yes), the collection 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] In addition, the collection information list management unit 130 determines whether there is a registration of the collection information list 300 having the device ID received together with the configuration information (step S1104).

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

[0052] If there is a difference between the two (S1106; Yes), the collection information list management unit 130 updates the collection information list 300 (step S1107) and ends the process. Here, the collection information item 330 of the current collection 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 collection information list management unit 130 maintains the collection information list 300 as it is (step S1108) and ends the process.

[0054] Also, if it is determined in step S1104 that there is no registration (S1104; No), the collection information list management unit 130 newly creates the collection 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 identified in step S1101 is used for the HW ID and SW ID 320, and the extracted support information item 230 is used for the collection information item 330.

[0055] As described above, according to this embodiment, similar to the first embodiment, for each target device 510, the collection information list 300 listing the collection information items 330 can be automatically and always kept up-to-date according to the latest HW and SW configurations. The target device 510 can always collect optimal information by collecting information according to the latest collection information list 300.

[0056] Also, according to this embodiment, every time the configuration of the target device 510 changes, it is not necessary to individually install the information collection tool. Also, it is not necessary to manage the information collection tool for each individual device. It is only necessary to keep the support information list 200, which lists the items of collection information for each combination of HW and SW, in the latest state. For example, even when the target device 510 is installed at multiple locations, the work of individually applying it becomes unnecessary. As a result, the man-hours required for application are reduced, and it becomes possible to respond without being conscious of the operation state of the target device 510.

[0057] Furthermore, according to this embodiment, even when a new device is added as the target device 510, the support information list 200 is automatically updated. Therefore, the labor on the administrator side is not increased, and the information items to be collected for each individual target device 510 can be maintained as optimal ones.

[0058] That is, according to this embodiment, by flexibly creating (updating) the collection information list 300 for each device to be collected (target device 510), only the optimal (necessary) information can be collected for the target device 510. As a result, the capacity of the information to be collected can be reduced and the collection time can be shortened. Also, wasteful man-hours such as checking information that is unnecessary (not implemented / not installed) for information analysis can be prevented. Therefore, information can be collected efficiently, and the collected information can be used efficiently.

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

[0060] <Modification Example 1> In the above embodiment, the device information collection and management device 100 is an independent device, but it is not limited to this. For example, the device information collection and 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 and management device 100 may be incorporated and used in an existing system composed of the management server 710 and the target device 510.

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

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

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

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

[0066] In this modified example, during the list update process, the collection information list management unit 130 accesses the target device 510a, collects the current collection information list 300, and performs processing. Then, after updating or creating the collection information list 300, it delivers it to the target device 510a.

[0067] Note that in this modified example, the device information collection and management unit 100a does not necessarily need to compare with the current collection information list 300 as in the first embodiment. In this case, every time configuration information is received from the target device 510a, the latest collection information list 300 may be created using the support information items 230 registered in association, and delivered to the target device 510a.

[0068] <Modified Example 2> Furthermore, the target device 510b may have yet other functions of the device information collection and management apparatus 100. An example of the device information collection and management system 702 when the functions are distributed is shown in FIG. 6.

[0069] As shown in this figure, the device information collection and management system 702 includes a management server 720 and a target device 510b. The two are connected by, for example, a network 102 or the like. Note that also in this modified example, the number of target devices 510b is not limited. In FIG. 6, the portion surrounded by the dashed line corresponds to the device information collection and management apparatus 100 of 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 modified example includes a device configuration identification unit 120 and a collection information list management unit 130. Also, the target device 510b includes a collection information list 300 in a storage device or the like. The device configuration identification unit 120 and the collection information list management unit 130 have basically the same functions as the components with the same names in each of the above embodiments.

[0071] On the one hand, the management server 720 includes a support information list management unit 110, and for example, its storage device or the like includes a support information list 200. The support information list management unit 110 also has basically the same functions as the components with the same names in 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 processes after step S1105 of the above list update process by using the acquired support information items 230. Thereby, the collected information list 300 that is optimal for the current configuration of the target device 510b can always be maintained.

[0074] Thereafter, the device information collection utility 511b collects device information according to the updated (created) collected information list 300.

[0075] <Modification Example 3> In addition, the functions of the device information collection management device 100 may be incorporated into other systems. For example, an example of cooperation with an existing service, the server diagnosis medical record service, will be described. FIG. 7 is an overall view of the server diagnosis medical record service system 600 of this modification example.

[0076] The server diagnosis medical record service is a service that visualizes "behavior different from usual" occurring in system operation and provides information periodically as a diagnosis medical record, and supports the stable operation of the target device 500. For example, it is possible to easily check the application status of an OS update program that is often overlooked and comprehensive diagnosis comments according to the operation status of the target device 500, and it can be used for the implementation of early countermeasures and the operation management of the IT system.

[0077] The server diagnosis medical record 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 via a network, for example.

[0078] The management server 610 collects information on the target device 500 and reports it when an abnormality is detected. The device information collection and management device 100 of this modification example is realized as a part of the management server 610. Hereinafter, in this modification example, since the function of the device information collection and management device 100 is incorporated into the management server 610 and used, it is referred to as the device information collection and 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 and 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 reception function.

[0080] The device management function is responsible for the 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). In addition, it reports abnormalities that lead to system downtime or failures, and obtains various information for cause investigation in the event of a failure. Furthermore, it monitors the usage status of the server (target device 500), such as the CPU load rate, disk free 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) at a predetermined time interval, for example, and stores it in the data lake of the cloud server 630. Note that it is not limited to a predetermined time interval. For example, the configuration information may be acquired in response to an instruction from the user.

[0082] The notification log reception function receives the logs of notifications by the failure 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 being processed. For example, device information, execution logs, etc. of the target device 500 are stored in the data lake. These are accumulated in association with the acquisition time. Also, in this modification example, a collection information list 300 created and updated by the device information collection management unit 100c may be included. The collection information list 300 is registered for each target device 500 in association with information for identifying the target device 500.

[0084] The device information collection management unit 100c realizes the same functions as the device information collection management device 100 of the above-described embodiments. Since each function is basically the same as that of the same name in the above-described embodiments, the description thereof is omitted.

[0085] However, in this modification example, 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] Also, the support information list 200 is stored, for example, in the storage device of the management server 610 or the like.

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

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

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

[0090] As in this modification example, by cooperating with the functions of the server diagnosis medical record service system 600, the device information collection management unit 100c periodically updates (creates) the collection information list 300. And in the server diagnosis medical record service system 600, the optimal information according to the latest device configuration can be automatically collected.

[0091] <Modification Example 4> Also, in the above embodiment, the support information list 200 is created for each HW, but it is not limited to this. For example, HWs with the same collection 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 grouped for each piece of information (HW ID 291) identifying the HW and is assigned a group number 292.

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

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

[0096] At this time, as shown in this figure, for example, regarding an optional card (PCI (Peripheral Component Interconnect) Device), support information items 230 may be managed for each piece of information (PCI ID 240) to be identified.

[0097] The device configuration identification unit 120 checks the PCI device information from the configuration information and discriminates whether each is implemented or not. And when it is implemented, the acquisition information list management unit 130 extracts the corresponding support information item 230 from the support information list 201.

[0098] <Modification Example 5> Note that 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, it is not limited to this. For example, the purpose may be further considered. For example, it is at the time of failure occurrence, maintenance inspection, etc. Also, at the time of failure occurrence, the support information lists 200 and 201 may be configured in more detail according to the location where the failure occurs.

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

[0100] <Modification Example 6> In the above-described embodiment, when the combination of HW and SW specified from the configuration information is not registered in the support information list 200, the default collection information is registered as the support information item 230, but the present invention is not limited to this.

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

[0102] Also, when the support information list 200 is updated, it may be configured to notify the administrator (user). The user can receive the notification and maintain the support information list 200 in an optimal state.

[0103] Also, in the above-described embodiment, at the time of the list update process, the collection information item 330 of the current collection information list 300 is compared with the support information item 230, but it may be compared with the items included in the transmitted device information.

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

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

[0106] The CPU 691 realizes the above-described respective functions and comprehensively controls the entire device information collection management device 100 by, for example, loading the program stored in the auxiliary storage device 693 into the main storage device 692 and executing it. Note that one or more processors such as an MPU (Micro Processing Unit) may be used instead of the CPU 691.

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

[0108] The auxiliary storage device 693 is, for example, a ROM (Read Only Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like. The auxiliary storage device 693 stores various programs executed by the device information collection and management device 100. Note that 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, or the like.

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

[0110] The communication I / F 694 is an interface for input / output of signals and data by wire or wirelessly. Note that the communication I / F 694 may not be provided.

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

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

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

[0114] Note that the hardware configuration of the device information collection and management device 100 is not limited to this. It may include hardware not shown in the figures.

[0115] Also, the program for realizing each of the above functions of the device information collection and management device 100 of the present embodiment can be recorded on a computer-readable storage medium. The storage medium can be a non-transient one 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.

[0116] Also, 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] Also, the management server 710 and the target device 500 are similarly realized by a general-purpose information processing device shown in FIG. 9 or a dedicated circuit or the like.

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

[0119] As described above, each embodiment and modification example of the present invention have been explained. However, the present invention is not limited to the above-described embodiments, and various changes that can be understood by those skilled in the art can be made. And each embodiment and modification example can be combined with other embodiments as appropriate. Also, for example, the network configuration and the configuration of each element shown in each drawing are examples for helping the understanding of the present invention, and are not limited to the configurations shown in these drawings.

[0120] Finally, the preferred embodiments of the present invention are summarized. Some or all of the above embodiments may be described as follows, but are not limited thereto. (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 specifying unit that specifies the configuration of a target device, which is the device for which information is to be collected; 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 from the target device, are registered using the support information items registered in the support information list in association with the configuration of the target device specified by the device configuration specifying unit. An apparatus information collection management apparatus comprising: (Appendix 2) In the apparatus information collection management apparatus according to Appendix 1, The collection information list management unit 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 association with the configuration of the target device. When there is a difference, it is desirable to update the collection information items in the collection information list that it manages with the support information items. (Appendix 3) In the apparatus information collection management apparatus according to Appendix 1 or 2, The collection information list management unit 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 association with the configuration of the target device. When there is no difference, it is desirable to maintain the collection information list that it manages. (Appendix 4) In the apparatus information collection management apparatus according to any one of Appendices 1 to 3, When the support information item is not registered in the support information list in association with the configuration of the target device, the support information list management unit registers, in association with the configuration of the target device, a pre-prepared information item as the support information item in the support information list. This is desirable. (Appendix 5) In the device information collection and management device according to any one of Appendices 1 to 4, it is desirable that the configuration of the device includes hardware installed in the device and software installed in the device. (Appendix 6) In the device information collection and management device according to any one of Appendices 1 to 5, it is desirable that the configuration of the device further includes a device connected to 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, are registered for the target device, which is the device for which information is to be collected, An information collection device that collects information of the target device according to the collection information list and acquires configuration information that can identify the latest configuration of the target device, and is provided with, The collection information list management device acquires the support information items registered in the support information list in association with the latest configuration of the target device specified by the configuration information acquired by the information collection device, and uses the support information items to create the collection information list of the target device. An apparatus information collection management system. (Appendix 8) A device information collection management method executed by a computer, A configuration specifying step of specifying the configuration of a target device, which is a device for which information is to be collected, A collection information list management step of creating a collection information list in which collection information items, which are information items to be collected, are registered for the target device, using support information items, which are information items supported by the registered configuration, in association with the specified configuration of the target device. A device information collection management method comprising. (Appendix 9) On the computer, A configuration identification procedure for identifying the configuration of a target device, which is the device for which information is to be collected, and A collection information list management procedure for creating a collection information list in which collection information items, which are information items to be collected from the target device, are registered using support information items, which are information items supported by the registered configuration associated with the identified configuration of the target device, and a program for causing the procedures to be executed. Note that Forms 8 and 9 can be developed into Forms 2 - 6 in the same manner as Form 1.

[0121] Note that each disclosure of the above patent documents and the like is incorporated herein by reference. Within the scope of the entire disclosure of the present invention (including the claims), further changes and adjustments of the embodiments or variations can be made based on the basic technical idea. Also, within the scope of the disclosure of the present invention, various combinations or selections of various disclosure elements (including each element of each claim, each element of each embodiment or variation, each element of each drawing, etc.) are possible. That is, the present invention naturally includes all disclosures including the claims, and various modifications and corrections that could be made by those skilled in the art according to the technical idea. In particular, for the numerical ranges described in this document, any numerical value or small range included within the range should be construed as specifically described even without separate description.

Explanation of Reference Numerals

[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: Collection 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: Acquisition Information List, 310: Device ID, 320: HW ID and SW ID, 330: Acquisition Information Items, 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 Diagnosis Medical Record Service System, 610: Management Server, 620: Management Department, 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 specifying unit that specifies the configuration of a target device, which is the device from which information is to be collected; 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 from the target device, are registered, using the support information items registered in the support information list in association with the configuration of the target device specified by the device configuration specifying unit. An apparatus information collection management apparatus comprising:

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

3. The apparatus information collection management apparatus according to claim 1, wherein the collection information list management unit compares the collection information items of the collection information list of the target device, which it manages, with the support information items registered in the support information list in association with the configuration of the target device, and if there is no difference, maintains the collection information list that it manages. An apparatus information collection management apparatus.

4. The apparatus information collection management apparatus according to claim 1, wherein when the support information items are not registered in the support information list in association with the configuration of the target device, the support information list management unit registers, in the support information list in association with the configuration of the target device, information items prepared in advance as the support information items. An apparatus information collection management apparatus.

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

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

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 a 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, are registered for the target device, which is the device for collecting information. An information collection device that collects information on the target device according to the collection information list and obtains configuration information that can identify the latest configuration of the target device. The collection information list management device obtains the support information items registered in the support information list in association with the latest configuration of the target device specified by the configuration information obtained by the information collection device, and uses the support information items to create the collection information list for the target device. An apparatus information collection management system.

8. A device information collection management method executed by a computer, comprising: A configuration specifying step of specifying the configuration of a target device, which is a device for collecting information; A collection information list management step of creating a collection information list in which collection information items, which are information items to be collected for the target device, are registered using support information items, which are information items supported by the pre-registered configuration, in association with the specified configuration of the target device. A device information collection management method.

9. A program for causing a computer to Execute a configuration specifying procedure for specifying the configuration of a target device, which is a device for collecting information; Execute a collection information list management procedure for creating a collection information list in which collection information items, which are information items to be collected for the target device, are registered using support information items, which are information items supported by the pre-registered configuration, in association with the specified configuration of the target device.

Images