JP2021006940A - Update management apparatus, update management system and update management program - Google Patents

Abstract

To provide an update management apparatus, an update management system and an update management program capable of preventing an occurrence of failure due to differences in software version between a plurality of bases.SOLUTION: In an update management system 1, a public information DB 47 stores information of a version number of software (BIOS, firmware and driver, for example) of a web site 2 at each base, as public version number information. When a management apparatus 3 updates software of a business server 3a, an update judgement unit 43 of an update management apparatus 4 determines whether or not update is possible based on the public version number information, and instructs the management apparatus 3 to hold the update if the update is not possible. The management apparatus 3 holds the update of the software based on the instruction.SELECTED DRAWING: Figure 1

Description

The present invention relates to an update management device, an update management system, and an update management program.

Multiple softwares are installed in computers such as servers and personal computers. The plurality of software includes, for example, a BIOS (Basic Input Output System), firmware, and a device driver. The BIOS is software that performs initial settings of a computer and the like. Firmware is software that performs basic control of a computer. A device driver is software for controlling a device such as an option card.

Multiple softwares are revised as appropriate at different timings. For example, the BIOS, firmware, and device driver are appropriately revised at different timings in order to support a new OS (Operating System), support new hardware, and fix problems. The revised data is published and provided on a computer-dedicated Web site (hereinafter referred to as a Web site). The administrator of the computer manages the computer to operate normally with the latest version of the software by updating to the new software published on the website.

Regarding software download, there is a conventional technique for reducing the processing load at the time of download. In this prior art, when there is no software for download in the first data center used by the user, the management device that manages the data center gives an instruction to download from the second data center that holds the software. Send to your data center.

In addition, there is a conventional technique for avoiding problems caused by updating firmware and drivers. In this prior art, the firmware execution device includes a combination information storage unit that stores combination information including dependency information indicating a dependency between firmware functional modules and driver versions. Further, the firmware execution device includes a driver version storage unit that stores the current driver version and a firmware storage unit that stores functional modules that can be used for each driver version. In addition, the firmware execution device includes a dependency determination unit that determines whether or not there is a dependency inconsistency between the current firmware and the current driver version at startup and whether or not the inconsistency is resolved by updating the firmware. .. Further, the firmware execution device includes a firmware update unit and a function module selection unit in which either of them functions according to the determination result.

Further, regarding firmware update, there is a conventional technique for simultaneously realizing recovery at the time of interruption of update and saving of non-volatile memory capacity used for backup and storage of differential data. In addition to the old and new firmware, this conventional technique includes intermediate data that always holds the state of the firmware being rewritten. Then, this prior art sequentially compares the intermediate data with the block of the new firmware in the case of updating all the blocks constituting the firmware in an arbitrary order. Then, this conventional technology calculates the data address for recovery at the time of update interruption and the backup capacity required for it, extracts the difference data to be distributed, calculates the capacity, and creates the update procedure to obtain the backup capacity. Derive the processing order that minimizes the total difference data capacity.

Further, as a conventional technique, there is a system that automatically updates a firmware program that controls internal processing of a mobile phone via a network used for the mobile phone network. This system implements a firmware update program on a mobile phone terminal and distributes an update firmware module from a firmware distribution server. When this system receives the update firmware module, the program of the mobile phone terminal automatically updates the firmware of its own terminal. In this system, the update process is performed by using a dedicated power supply for firmware update provided separately from the main power supply used for normal operation.

Japanese Unexamined Patent Publication No. 2017-54318 Japanese Unexamined Patent Publication No. 2018-136608 Japanese Unexamined Patent Publication No. 2011-44087 Japanese Unexamined Patent Publication No. 2003-209510

When a computer is used at a plurality of bases in a plurality of countries or regions, the revised data is published on the website of each base, but the release timing of the latest version may differ for each base. For example, websites in a plurality of countries may take a long time to translate due to differences in languages, and the timing of publication may differ. For this reason, there are bases where it is possible to update to the latest version and bases where it is not possible, and when using computers at multiple bases, if the software is updated at only one base, the version number will differ between the bases. There is a problem that failures may occur. For example, when an application running on multiple computers uses a driver, a failure may occur if the driver version differs between the computers.

One aspect of the present invention is to prevent the occurrence of a failure due to a difference in software version between a plurality of bases.

In one aspect, the update management device has a public information storage unit and an update determination unit. The public information storage unit stores public version information indicating the version number of software provided to each of a plurality of information processing devices that are arranged at a plurality of bases and are commonly used by users. When the first information processing device among the plurality of information processing devices updates the software to a new version, the update determination unit determines whether or not the update condition regarding the update to the new version is satisfied. Judgment is made based on the public version information stored in the public information storage unit. Then, if the update determination unit does not satisfy the update condition, the update is suspended until the update condition is satisfied.

In one aspect, the present invention can prevent the occurrence of failures due to differences in software versions between a plurality of bases.

FIG. 1 is a diagram showing a configuration of an update management system according to an embodiment. FIG. 2 is a diagram showing an example of the correspondence information DB. FIG. 3 is a diagram showing an example of a computer information DB. FIG. 4 is a diagram showing an example of the public information DB. FIG. 5 is a diagram showing an example of the management information DB. FIG. 6 is a diagram showing a process when the update of the FW is suspended depending on the publication status of the website of another country. FIG. 7 is a diagram showing processing when a FW waiting to be released is released. FIG. 8A is a first diagram showing a sequence of update processing. FIG. 8B is a second diagram showing a sequence of update processing. FIG. 9 is a diagram showing a sequence of processing when a failure occurs due to a version mismatch between the FWs of Japan and the United States. FIG. 10 is a diagram showing a sequence of processes for registering computer information of a business server. FIG. 11 is a diagram showing a sequence of processes for collecting combination specification information. FIG. 12 is a diagram showing a sequence of processes for collecting public information of the FW of the website. FIG. 13 is a diagram showing a hardware configuration of a computer that executes the update management program according to the embodiment.

Hereinafter, examples of the update management device, update management system, and update management program disclosed in the present application will be described in detail with reference to the drawings. It should be noted that this embodiment does not limit the disclosed technology. Further, in the following, "firmware" is referred to as "firmware" or "FW", and the device driver is referred to as "driver" or "Drv".

First, the configuration of the update management system according to the embodiment will be described. FIG. 1 is a diagram showing a configuration of an update management system according to an embodiment. As shown in FIG. 1, the update management system 1 according to the embodiment includes a website 2 represented by a US website and a Japanese website, a management device 3 of company A in the US, and B in the US and Japan. It has a management device 3 of the company and an update management device 4. The US website is in the US and the Japanese website is in Japan.

The two websites 2, the three management devices 3, and the update management device 4 are connected by a network 5. The management device 3 and the website 2 may be located outside the United States and Japan, and the management device 3 of another company may be provided in the United States and Japan.

The website 2 stores and publishes the BIOS update data 21, the FW update data 22, and the Drv update data 23 together with the version number.

The management device 3 of company A in the United States manages the business server (information processing device) 3a of company A in the United States, and the management device 3 of company B in the United States manages the business server 3a of company B in the United States. The management device 3 of company B in Japan manages the business server 3a of company B in Japan.

The management device 3 has a server management unit 30. The server management unit 30 manages the computer information of the user's business server 3a. The computer information includes the installed BIOS, FW and Drv version, OS information, the name and configuration of the business server 3a, and the country of installation. When the business server 3a is added, the server management unit 30 collects computer information of the business server 3a and notifies the update management device 4.

The server management unit 30 manages the BIOS, FW, and driver of the business server 3a. The server management unit 30 has an update processing unit 31 and an update management DB 32.

When the administrator starts updating the BIOS, FW, or Drv of the business server 3, the update processing unit 31 makes an inquiry to the update management device 4 whether or not the update is possible, and follows the instructions from the update management device 4 to the BIOS, FW, or Drv. Controls updates or pending updates. When updating the BIOS, FW, or Drv, the update processing unit 31 saves the old version when the update management device 4 instructs to save the old version. Further, when the update management device 4 instructs the update processing unit 31 to cancel the saving of the old version, the update processing unit 31 deletes the saved old version. Further, when the update management device 4 instructs the update processing unit 31 to update the held update, the update processing unit 31 executes the update.

Further, when the update processing unit 31 detects the occurrence of a failure due to the version mismatch of the BIOS, FW, and Drv, it inquires the update management device 4 for downgrade (return to the old version), and when instructed by the update management device 4, it goes down. Do the grade.

The update management DB 32 manages computer information of the business server 3a and data of BIOS, FW, and Drv.

The update management device 4 cooperates with the management device 3 to control the update of the BIOS, FW, and Drv, the update hold, the release of the held update, and the like. The update management device 4 has an information collection unit 41, an information generation unit 42, an update determination unit 43, a notification unit 44, a correspondence information DB 45, a computer information DB 46, a public information DB 47, and a management information DB 48. ..

The information collecting unit 41 collects computer information managed by the server management unit 30, public version information managed by the development department, and combination specification information. Here, the public version information is information on the version numbers of BIOS, FW, and Drv of the website 2 of each country. Further, the combination specification information is information indicating whether or not the version numbers of BIOS, FW, and Drv can be combined.

The information generation unit 42 generates and updates the correspondence information DB 45 based on the combination specification information collected by the information collection unit 41. The information generation unit 42 generates and updates the computer information DB 46 based on the computer information collected by the information collection unit 41. The information generation unit 42 generates and updates the public information DB 47 based on the public version number information collected by the information collection unit 41.

The update determination unit 43 determines update, update hold, old version save, hold release, save release of BIOS, FW and Drv using the corresponding information DB 45, the computer information DB 46, the public information DB 47 and the management information DB 48. Then, the update determination unit 43 gives an instruction to the management device 3 and updates the public information DB 47 and the management information DB 48 based on the determination result. Hereinafter, the case of updating the FW will be specifically described as an example, but the update determination unit 43 also performs the same process when updating the BIOS and Drv.

The update determination unit 43 updates the FW when there is a business server 3a in another country, the same version of the FW has already been published on the website 2 of the other country, and the update causes a version difference from the other business server 3a. It is judged that it is possible and the old version needs to be saved. Then, the update determination unit 43 registers the update waiting flag and the old version save flag of the FW of the business server 3a in which the difference occurs.

Here, registering the update waiting flag of the FW means registering the version number of the FW to be updated in the "FW" of the "waiting for update" of the management information DB 48. Further, registering the old version save flag of the FW means registering the version number of the FW before the update in the "FW" of the "old version of the save" of the management information DB 48.

If the update determination unit 43 has a business server 3a in another country, the same version of the FW has already been published on the website 2 of the other country, and the update does not cause a version difference from the other business server 3a, the update determination unit 43 has a version difference. It is judged that the FW can be updated. Further, the update determination unit 43 determines that the FW update is possible when the business server 3a does not exist in another country.

If the update determination unit 43 has a business server 3a in another country and the same version of the FW has not been published on the website 2 of the other country, the update determination unit 43 determines that the FW update is pending, and updates the website release waiting flag and the FW. Register the hold flag. Further, the update determination unit 43 determines that the FW update is pending even when the combination of the BIOS, FW, and Drv versions is not permitted by updating the FW, and registers the website release waiting flag and the FW update suspension flag. To do.

Here, registering the website publication waiting flag means registering the number of editions waiting to be published in the "waiting for publication" of the "driver", "farm", or "BIOS" of the public information DB 47. When the release of the driver is awaited, the version number of the driver for which the release is awaited is registered in the "waiting for release" of the "driver" of the public information DB 47. When the publication of the BIOS is awaited, the version number of the BIOS for which the publication is awaited is registered in the "waiting for publication" of the "BIOS" of the public information DB 47. When the publication of the farm is awaited, the version number of the farm to be released is registered in the "waiting for publication" of the "farm" of the public information DB 47. Further, registering the update hold flag of the FW means registering the version number of the FW to be updated in the "FW" of the "update hold" of the management information DB 48.

For example, when the latest version of the BIOS is not published, the update determination unit 43 does not permit the update to the latest version of the FW based on the combination specification information in which only the combination of the latest version is permitted. At this time, the update determination unit 43 registers the version number of the BIOS awaiting publication in the "waiting for publication" of the "BIOS" of the public information DB 47, and updates it to the "FW" of the "holding update" of the management information DB 48. Register the version of FW.

Further, the update determination unit 43 manages the business server 3a related to the failure when the business server 3a related to the failure has the old version save flag of the FW when a failure occurs due to the version mismatch of the FW. Instruct the management device 3 to downgrade the FW to the old version.

Further, when the public information of the website 2 is updated, the update determination unit 43 deletes the public waiting flag of the updated BIOS, FW or Drv, and the update is suspended based on the update hold flag. Instructs the update execution of FW and Drv. Then, when the update is completed, the update determination unit 43 deletes the update hold flag.

The notification unit 44 notifies the management device 3 of the determination result by the update determination unit 43. That is, the notification unit 44 notifies the management device 3 corresponding to the update, update hold, old version save, hold release, and save release of the BIOS, FW, and Drv.

The correspondence information DB 45 stores correspondence information based on the combination specification information collected by the information collecting unit 41. FIG. 2 is a diagram showing an example of the correspondence information DB 45. As shown in FIG. 2, the correspondence information DB 45 stores the "applicable condition ID", the "BIOS / FW / Drv", and the "condition" in association with each other for each combination of the BIOS, FW, and Drv editions. ..

The "applicable condition ID" is an identifier that identifies each entry. "BIOS / FW / Drv" indicates the version number of BIOS, FW and Drv, "# 1" indicates the version number of BIOS, "# 2" indicates the version number of FW, and "# 3" indicates the version number of Drv. Indicates the version number of. "Condition" indicates whether or not the combination of BIOS, FW and Drv version numbers is prohibited. "Prohibited" means that the combination of BIOS, FW and Drv editions is prohibited, and "Recommended" means that the combination of BIOS, FW and Drv editions is allowed without being prohibited. Shown. For example, the combination of the BIOS version "BIOS01", the FW version "FW01", and the Drv version "Drv01" is identified by "ID001" and is not prohibited.

The computer information DB 46 stores the computer information collected by the information collecting unit 41. FIG. 3 is a diagram showing an example of the computer information DB 46. As shown in FIG. 3, the computer information DB 46 associates a "user", a "country", a "server", a "driver", a "farm", a "Bios", and an "OS". Stored for each business server 3a.

The "user" is a name that identifies a user of the business server 3a. "Country" is a name that identifies the country in which the business server 3a is located. The "server name" is a name that identifies the business server 3a. The "driver" is the version number of the driver of the business server 3a. “Farm” is the version number of the farm of the business server 3a. "BIOS" is the version number of the BIOS of the business server 3a. "OS" is the OS version of the business server 3a.

For example, the user of the business server 3a identified by "A-US1" is "Company A". For the business server 3a identified by "A-US1", the country where it is located is "US", the driver version is "Drv01", and the farm version is "FW02". The BIOS version is "BIOS02" and the OS version is "WS16".

The public information DB 47 stores the public version number information. That is, the public information DB 47 stores the version numbers of the driver, the farm, and the BIOS published on the website 2 of the country where the business server 3a is located. FIG. 4 is a diagram showing an example of the public information DB 47. As shown in FIG. 4, the public information DB 47 stores "country", "driver", "farm", and "BIOS" in association with each website 2.

The "country" is the country where the website 2 is located. "Driver" is the version number of the driver, "current status" is the version number of the latest driver published by website 2, and "waiting for publication" is waiting for the driver to be published on website 2. It is the number of editions. "Farm" is the version number of the farm, "current status" is the latest version of the farm published by website 2, and "waiting for publication" is waiting for publication of the farm on website 2. It is the number of editions. "Bios" is the version of BIOS, "current status" is the latest version of BIOS published by website 2, and "waiting for publication" is waiting for publication of BIOS on website 2. It is the number of editions.

For example, the latest version of the driver published on Japanese website 2 is "Drv03", the latest version of the farm is "FW02", and the latest version of BIOS is "BIOS03". Also, there is no driver, farm, or BIOS version that is awaited to be released on Japanese website 2.

The "current situation" is the information collected by the information collecting unit 41, while the "waiting for publication" is the information to be updated by the update determination unit 43. Further, the public information DB 47 may store the version number of any one or more of the driver, the farm and the BIOS instead of storing the version number of the driver, the farm and the BIOS.

The management information DB 48 stores the management information used for updating the BIOS, FW, and Drv. FIG. 5 is a diagram showing an example of the management information DB 48. As shown in FIG. 5, the management information DB 48 stores "user", "country", "server name", "update hold", "update wait", and "save old version" for each business server 3a.

The "user" is a name that identifies a user of the business server 3a. "Country" is a name that identifies the country in which the business server 3a is located. The "server name" is a name that identifies the business server 3a. "Update pending" is the version number for which an update is pending. "Drv" is the version number of the driver whose update is pending, "FW" is the version number of the farm whose update is pending, and "BIOS" is the version number of the BIOS whose update is pending.

"Waiting for update" is the version number for which an update is awaited. "Drv" is the version of the driver awaiting update, "FW" is the version of the farm awaiting update, and "BIOS" is the version of BIOS awaiting update. .. The "save old version" is the number of versions of the old version that is saved when updating. "Drv" is the version number of the old version of the driver saved at the time of update, "FW" is the version number of the old version of the farm saved at the time of update, and "BIOS" is saved at the time of update. This is the version number of the old version of BIOS.

For example, the update of the farm "FW03" of "B-US1", which is the business server 3a located in "US" of "Company B", is pending.

Next, an example of suspending the update depending on the publication status of the website 2 of another country will be described with reference to FIGS. 6 and 7. FIG. 6 shows a process when the update of the FW is suspended depending on the publication status of the website 2 of another country, and FIG. 7 shows a process when the FW waiting to be released is released.

FIG. 6 shows a case where the farm is about to be updated from "FW02" to "FW03" on "B-US1", which is the US business server 3a of Company B, and "FW03" is not published on Japanese website 2. Is shown.

As shown in FIG. 6, the management device 3 in the United States of Company B downloads "FW03" (t1), and the update processing unit 31 of the management device 3 updates the "B-US1" to "FW03". Start (t2). First, the update processing unit 31 requests the update management device 4 to determine whether or not the update is possible (t3).

Then, the update determination unit 43 of the update management device 4 confirms the correspondence information DB 45 (t4). The version number of the driver of "B-US1" is "Drv03", the version number of BIOS is "BIOS03", and the combination of "BIOS03", "FW03" and "Drv03" in "ID004" of the corresponding information DB45 is Since it is not prohibited, the update is judged to be "OK".

Then, when the update determination unit 43 confirms the business server 3a of the other country of the company B by referring to the computer information DB 46 (t5), since the business server 3a is located in Japan, the update determination unit 43 refers to the public information DB 47 (t6). ). Then, since "FW03" is not published on the Japanese website 2, the update determination unit 43 determines that the update is not possible (t7), and the notification unit 44 of the update management device 4 puts the update hold on the update processing unit 31. Notify (t8). Then, the update processing unit 31 displays an update hold message (t9).

In addition, the update determination unit 43 registers "FW03" in "FW" of "update hold" of "B-US1" of management information DB48 (t10), and "farm" of "day" of public information DB47. Register "FW03" in "Waiting for release" (t11).

After that, when "FW03" is released on the Japanese website 2, as shown in FIG. 7, the information collecting unit 41 of the update management device 4 releases the public information of the BIOS, FW, and Drv of the website 2 of each country. Collect from the development department (t21). Then, the information generation unit 42 of the update management device 4 updates the "current state" of the "farm" of the "day" of the public information DB 47 to "FW03" (t22).

Then, when the update determination unit 43 confirms the "waiting for publication" of the "day" of the "farm" of the public information DB 47 (t23), since "FW03" is registered, the "update pending" of the management information DB 48 is displayed. Confirm "FW" (t24). Then, since "FW03" is registered in "B-US1" of "US" of "Company B", the notification unit 44 gives an instruction to update "FW03" of "B-US1" to "Company B". Notify the update processing unit 31 of "rice" (t25). Then, the update processing unit 31 updates the farm of "B-US1" to "FW03" (t26).

In addition, the update determination unit 43 deletes "FW03" of "waiting for publication" of "farm" of "day" of public information DB47 (t27), and "holding update" of "B-US1" of management information DB48. Delete "FW03" of "FW" (t28).

Next, the sequence of update processing will be described. 8A to 8B are diagrams showing a sequence of update processing. Although FIGS. 8A and 8B show the case where the FW is updated, the same update process is performed for the BIOS and Drv.

As shown in FIG. 8A, the administrator who manages the business server 3a in the United States accesses the website 2 (step S1) and downloads the FW (step S2). Then, the administrator instructs the management device 3 to update the FW (step S3). Then, the server management unit 30 of the management device 3 transmits an update determination request to the update management device 4 (step S4).

Then, the update management device 4 collects the computer information and updates the computer information DB 46 (step S5). Then, the update management device 4 collects the combination specification information and updates the correspondence information DB 45 (step S6). Then, the update management device 4 collects the public information of the BIOS, FW, and Drv, and updates the public information DB 47 (step S7).

Then, the update management device 4 determines whether or not the combination of the BIOS, FW, and Drv version numbers after the FW update is permitted based on the correspondence information DB 45 and the computer information DB 46 (step S8). Then, if permitted, the update management device 4 determines whether or not there are a plurality of owned business servers 3a (step S9), and if there are a plurality of owned business servers 3a, determines whether or not there is a business server 3a in another country. (Step S10).

Then, when the business server 3a is located in another country, the update management device 4 determines whether or not the same version of the FW has been published on the website 2 of the other country (step S11). Then, if it has already been published, the update management device 4 determines whether or not the update causes a version difference from the other business server 3a (step S12).

Then, when the version difference from the other business server 3a occurs due to the update, the update management device 4 registers the update waiting flag and the old version save flag of the FW of the business server 3a where the difference occurs (step S13). ..

Then, the update management device 4 notifies the management device 3 that the FW can be updated and that the old version needs to be saved as a determination result notification (step S14).

Further, in step S12, if the update does not cause a version difference from the other business server 3a, the update management device 4 notifies the management device 3 that the FW can be updated as a determination result notification (step S15). Further, in step S10, when the business server 3a does not exist in another country, the update management device 4 notifies the management device 3 that the FW can be updated as a determination result notification (step S15). Further, in step S9, the update management device 4 notifies the management device 3 that the FW can be updated as a determination result notification when there are not a plurality of owned business servers 3a (step S15).

Further, in step S11, if the same version of the FW has not been published to the website 2 of another country, the update management device 4 registers the website publication waiting flag (step S16) and registers the update hold flag of the FW. (Step S17). Then, the update management device 4 notifies the FW update hold as a determination result notification (step S18).

Further, in step S8, when the combination of the BIOS, FW, and Drv version numbers after the FW update is not permitted, the update management device 4 registers the website release waiting flag (step S16) and suspends the update of the FW. Register the flag (step S17). Then, the update management device 4 notifies the FW update hold as a determination result notification (step S18).

As shown in FIG. 8B, the server management unit 30 determines whether or not the FW update is possible when the determination result notification is received (step S19), and saves the FW update data 22 when the FW update is not possible (step S19). Step S20), report the update suspension to the administrator (step S21).

On the other hand, if the FW can be updated, the server management unit 30 determines whether or not the old version needs to be saved (step S22), and if the old version needs to be saved, the FW old version is saved (step S23). Then, the server management unit 30 executes the FW update (step S24) and updates the computer information (step S25). Then, the server management unit 30 transmits a FW update execution completion notification to the update management device 4 (step S26), and reports the update execution completion to the administrator (step S27).

Upon receiving the FW update execution completion notification, the update management device 4 updates the computer information DB 46 (step S28), and determines whether or not there is a FW update waiting flag (step S29). Then, when there is no FW update waiting flag, the update management device 4 ends the process. On the other hand, when there is a FW update waiting flag, the update management device 4 deletes the FW update waiting flag (step S30), and transmits a related save old version deletion instruction to the management device 3 (step S31).

When the server management unit 30 receives the related save old version deletion instruction, it deletes the FW save old version (step S32) and transmits the FW old version deletion completion report to the update management device 4 (step S33). When the update management device 4 receives the FW old version deletion completion report, the update management device 4 deletes the old version save flag (step S34).

In this way, when the update management device 4 determines whether or not the FW can be updated, it is possible to prevent the occurrence of a failure due to the difference in the software version between the plurality of bases.

Next, a sequence of processing when a failure occurs due to a FW version mismatch between Japan and the United States will be described. FIG. 9 is a diagram showing a sequence of processing when a failure occurs due to a version mismatch between the FWs of Japan and the United States. Note that FIG. 9 shows the case where a failure occurs due to the FW version mismatch, but the same processing is performed for the BIOS and Drv.

As shown in FIG. 9, when a failure occurs in the business server 3a due to a version mismatch between the Japanese and US FW versions (step S41), the server management unit 30 transmits a downgrade determination request to the update management device 4 (step S41). Step S42).

Upon receiving the downgrade determination request, the update management device 4 determines whether or not there is an old version save flag of the FW of the business server 3a related to the failure (step S43), and if not, ends the process. On the other hand, when there is an old version save flag of the FW of the business server 3a related to the failure, the update management device 4 sends the management device 3 that manages the business server 3a having the old version save flag of the FW to the old version of the save of the FW. Is instructed to downgrade (step S44). In FIG. 9, for convenience of explanation, the management device 3 that has transmitted the downgrade determination request is instructed, but the update management device 4 instructs the management device 3 that manages the business server 3a having the old version save flag of the FW. ..

When the management device 3 that manages the business server 3a having the FW old version save flag is instructed to downgrade to the FW save old version, the management device 3 executes the downgrade to the FW save old version (step S45). Then, the management device 3 transmits the FW downgrade completion notification to the update management device 4 (step S46).

When the update management device 4 receives the FW downgrade completion notification, it deletes the old version save flag of the FW (step S47) and updates the computer information DB 46 (step S48).

In this way, the update management device 4 can recover the failure due to the FW version mismatch by instructing the downgrade of the FW when there is an old version save flag of the FW of the business server 3a related to the failure. ..

Next, a sequence of processes for registering computer information of the business server 3a will be described. FIG. 10 is a diagram showing a sequence of processes for registering computer information of the business server 3a. As shown in FIG. 10, the administrator adds a business server 3a and turns on the power (step S51). Then, the administrator instructs the management device 3 to set the expansion (step S52).

When instructed to set the expansion, the server management unit 30 collects computer information (step S53) and requests the update management device 4 to register the collected computer information (step S54). When the update management device 4 is requested to register the computer information, the update management device 4 updates the computer information DB 46 (step S55) and transmits a computer information registration completion notification to the management device 3 (step S56). Upon receiving the computer information registration completion notification, the management device 3 reports the business server registration completion to the administrator (step S57).

In this way, when the business server 3a is added, the server management unit 30 collects the computer information and requests the update management device 4 to register. Therefore, the update management device 4 is the business server 3a added to the computer information DB 46. Computer information can be reflected.

Next, a sequence of processes for collecting combination specification information will be described. FIG. 11 is a diagram showing a sequence of processes for collecting combination specification information. The update management device 4 periodically performs the process shown in FIG.

As shown in FIG. 11, the update management device 4 collects the combination specification information from the development department (step S61), and compares the collected combination specification information with the correspondence information stored in the correspondence information DB 45 (step S62). Then, the update management device 4 determines whether or not there is an update difference (step S63), and if there is an update difference, updates the correspondence information DB 45 with the update difference (step S64).

By collecting the combination specification information from the development department in this way, the update management device 4 can determine whether or not the combination of the BIOS, FW, and Drv versions is permitted.

Next, a sequence of processes for collecting public information of the FW of the website 2 will be described. FIG. 12 is a diagram showing a sequence of processes for collecting public information of the FW of the website 2. Although FIG. 12 shows a case where the public information of FW is collected, the same processing is performed for the public information of BIOS and Drv. Further, the update management device 4 periodically performs the process shown in FIG.

As shown in FIG. 12, the update management device 4 collects the public information of the FW of the website 2 of each country from the development department (step S71) and compares it with the public information DB 47 (step S72). Then, the update management device 4 determines whether or not there is an update difference (step S73), and if there is no update difference, the process ends.

On the other hand, when there is an update difference, the update management device 4 updates the public information DB 47 with the update difference (step S74), and determines whether or not there is a public waiting flag of the update FW based on the public information DB 47. (Step S75). Then, the update management device 4 ends the process when there is no release waiting flag of the update FW.

On the other hand, if there is a public waiting flag of the update FW, the public waiting flag is deleted (step S76), and the management device 3 is instructed to execute the update of the FW whose update is held based on the update hold flag (step S76). S77).

Then, the server management unit 30 of the management device 3 that manages the FW whose update has been suspended executes the update of the FW whose update has been suspended (step S78), and sends an update completion notification to the update management device 4 (step). S79).

Upon receiving the update completion notification, the update management device 4 updates the computer information DB 46 (step S80) and deletes the update hold flag (step S81).

In this way, when the public information of the FW of the website 2 is updated, the update management device 4 instructs the management device 3 to update the FW waiting to be released, so that the FW whose update is suspended can be updated. it can.

As described above, in the embodiment, the public information DB 47 stores the information on the version numbers of BIOS, FW and Drv of the website 2 of each country as the public version information. Then, when the management device 3 updates the BIOS, FW, or Drv of the business server 3a, the update determination unit 43 determines whether or not the update is possible based on the public version number information, and updates if the update is not possible. Instruct the management device 3 to hold. Therefore, if the published BIOS version is different in multiple countries, the published FW version is different in multiple countries, or the published Drv version is different in multiple countries, a failure will occur. Can be prevented.

Further, in the embodiment, the update determination unit 43 suspends the update of the FW based on the public version information, for example, when the FW version of each country is different, the public version information is updated, and the public version information is updated in each country. When the FW version becomes the same, the FW update hold is released. Therefore, the update determination unit 43 can update the reserved FW. The update determination unit 43 similarly suspends and cancels the update of the BIOS and Drv.

Further, in the embodiment, for example, when a combination other than the latest version combination of BIOS, FW and Drv is prohibited by the corresponding information DB 45, the update determination unit 43 updates the FW to the latest version when updating the latest version of BIOS or Drv. If the version has not been released, the FW update will be withheld. Then, when the latest version of BIOS or Drv whose latest version has not been released is released and the latest version of all of BIOS, FW and Drv is released, the suspension of the update of FW is released. Therefore, the update determination unit 43 can update the reserved FW. The update determination unit 43 similarly suspends and cancels the update of the BIOS and Drv.

Further, in the embodiment, even if the FW version number published in each country is the same, the update determination unit 43 may use the FW version number differently in some business servers 3a due to the FW update. Instruct the management device 3 to save the FW before the update. Therefore, when a failure occurs due to a difference in the version number of the FW in the shared business server 3a, the management device 3 can quickly restore the business server 3a by using the saved FW.

Although the update management device 4 has been described in the embodiment, an update management program having the same function can be obtained by realizing the configuration of the update management device 4 by software. Therefore, a computer that executes the update management program will be described.

FIG. 13 is a diagram showing a hardware configuration of a computer that executes the update management program according to the embodiment. As shown in FIG. 13, the computer 50 includes a main memory 51, a CPU (Central Processing Unit) 52 as an example of a processor, a LAN (Local Area Network) interface 53, and an HDD (Hard Disk Drive) 54. .. Further, the computer 50 has a super IO (Input Output) 55, a DVI (Digital Visual Interface) 56, and an ODD (Optical Disk Drive) 57.

The main memory 51 is a memory for storing a program, a result during execution of the program, and the like. The CPU 52 is a central processing unit that reads a program from the main memory 51 and executes it. The CPU 52 includes a chipset having a memory controller.

The LAN interface 53 is an interface for connecting the computer 50 to another computer via a LAN. The HDD 54 is a disk device for storing programs and data, and the super IO 55 is an interface for connecting an input device such as a mouse or a keyboard. The DVI 56 is an interface for connecting a liquid crystal display device, and the ODD 57 is a device for reading and writing DVDs and CD-Rs.

The LAN interface 53 is connected to the CPU 52 by PCI Express (PCIe), and the HDD 54 and ODD 57 are connected to the CPU 52 by SATA (Serial Advanced Technology Attachment). The super IO 55 is connected to the CPU 52 by LPC (Low Pin Count).

Then, the update management program executed by the computer 50 is stored in the CD-R, which is an example of the recording medium readable by the computer 50, read from the CD-R by the ODD 57, and installed in the computer 50. Alternatively, the update management program is stored in a database or the like of another computer system connected via the LAN interface 53, read from these databases, and installed in the computer 50. Then, the installed update management program is stored in the HDD 54, read into the main memory 51, and executed by the CPU 52.

Further, in the examples, the case of updating the BIOS, FW or Drv has been described, but the present invention is not limited to this, and can be similarly applied to the case of updating other software. Further, in the embodiment, the case where the website 2 and the management device 3 are arranged in a plurality of countries has been described, but the present invention is not limited to this, and the website is not limited to this, and the website is located in a plurality of bases such as states and regions. The same can be applied when 2 or the management device 3 is arranged.

1 Update management system 2 Website 3 Management device 3a Business server 4 Update management device 5 Network 21 BIOS update data 22 FW update data 23 Drv update data 30 Server management unit 31 Update processing unit 32 Update management DB
41 Information collection unit 42 Information generation unit 43 Update judgment unit 44 Notification unit 45 Corresponding information DB
46 Computer information DB
47 Public Information DB
48 Management information DB
50 computer 51 main memory 52 CPU
53 LAN interface 54 HDD
55 Super IO
56 DVI
57 ODD

Claims (8)

A public information storage unit that stores public version information that indicates the version number of software provided to each of multiple information processing devices that are placed in multiple bases and are commonly used by users.
When the first information processing device among the plurality of information processing devices updates the software to a new version, the public information storage unit stores whether or not the update condition for updating to the new version is satisfied. An update management device characterized by having an update determination unit that makes a determination based on information on the number of published versions to be processed and, if the update condition is not satisfied, suspends the update until the update condition is satisfied. A claim characterized in that the update determination unit releases the hold when the update condition is satisfied by providing the same version of the software at the plurality of bases and updating the public information storage unit. Item 1. The update management device according to item 1. The public information storage unit stores the version numbers of a plurality of software for each base.
A claim, wherein the update determination unit releases the hold when the update condition is satisfied by providing the latest version of all of the plurality of software and updating the public information storage unit. The update management device according to 1. The update determination unit determines whether or not to save the version before the update when the update condition is satisfied, and when it is determined to save the version before the update, the first information processing apparatus is used. The update management device according to claim 1 or 2, wherein an instruction to save the version before the update is transmitted together with the update instruction. When the update of the software in the first information processing device causes a difference in version of the software between the first information processing device and another information processing device, the update determination unit is before the update. The update management device according to claim 4, wherein it is determined that the version of the software is saved. The base is a country or region, and the plurality of software includes one or more of a BIOS, firmware for basic control of an information processing device, and a device driver for controlling a device. The update management device according to claim 3, wherein the update management device is disclosed and provided on a website arranged in each country or region. The software provided to each of the plurality of information processing devices that are arranged at a plurality of bases and are commonly used by users is updated to a new version for the first information processing device among the plurality of information processing devices. A management device that has an update processing unit that requests the determination of whether or not to update
A public information storage unit that stores public version information that indicates the version number of the software for each site,
When the determination is requested from the update processing unit, it is determined whether or not the update condition for updating to the new version is satisfied based on the public version number information stored in the public information storage unit, and the update condition is determined. An update management system including an update management device having an update determination unit that determines to suspend the update until the update condition is satisfied. On the computer
We collect public version information that indicates the version number of software provided to each of the multiple information processing devices that are placed in multiple bases and are commonly used by users.
When the first information processing device among the plurality of information processing devices updates the software to a new version, whether or not the update condition for updating to the new version is satisfied is determined based on the published version information. If the update condition is not satisfied, an update management program is characterized in that a process of suspending the update is executed until the update condition is satisfied.

Images