JP2001222431A - Resource managing device and program recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a resource managing device for allowing computers under the control of a resource managing device itself to simultaneously use a revised resource to be used by those computers according to automation constitution when the computers are constituted of the mixture of different kinds of devices. SOLUTION: When each computer under the control of this recourse managing device itself is constituted of the mixture of different kinds of devices, the edition number information of a resource to be used by those computers to be designated according to the combination of the kinds of devices is obtained, and notified to each computer, and when it is confirmed that the desired resource is down-loaded to each computer in response to the notification, end batch switching to the down-loaded resource is instructed so that the switching to the resource can be executed. Thus, each computer can simultaneously use the revised resource prepared for each kind of device for guaranteing the matching of the whole system without depending on the manual work of a maintenance staff without any error.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention realizes that, when computers under its own device are composed of a mixture of different types, the revised resources to be used by these computers are used synchronously according to an automatic configuration. The present invention relates to a resource management device and a program recording area in which a program used to realize the device is recorded.

In a computer system composed of a plurality of computers connected by a LAN or the like, resources such as firmware may be revised due to bugs or addition of functions. At this time, each computer is updated. It is necessary to use resources synchronously.

When all the computers constituting the computer system are no longer the same model,
Since it is necessary to download and use the revised resources prepared for each model that guarantees the consistency of the entire system, complicated work is forced.
From now on, the construction of technology to realize this work automation is called for.

[0004]

2. Description of the Related Art Firmware downloaded to a computer system constituted by connecting a plurality of computers via a LAN or the like will be revised at a remote maintenance center or the like connected via a public line or the like. .

In the prior art, when the firmware is updated at a remote maintenance center or the like, the maintenance person receives the notification and downloads the updated firmware to each computer to use the firmware.

In other words, in the prior art, the updated firmware is manually downloaded to each computer and processed by a maintenance person to use the computer.

[0007]

However, according to such a conventional technique, there is a problem that a work load of a maintenance person increases and a work error occurs.

That is, when all the computers constituting the computer system are of the same model, the same revised resources need to be downloaded to each computer, so that the workload of the maintenance staff is also very large. There is almost no work error.

However, when the computers constituting the computer system are not all the same model, that is, when the computers are composed of a mixture of different types of computers, a model that guarantees the consistency of the entire system for each computer. Since it is necessary to download the revised resources prepared for each time, the work load of the maintenance staff increases, and work errors frequently occur.

The present invention has been made in view of the above circumstances, and when computers under its own device are composed of a mixture of different types, the revised resources to be used by those computers are synchronized in accordance with an automated configuration. The purpose of the present invention is to provide a new resource management device for realizing the use of the device and a new program recording medium on which a program used for realizing the device is recorded.

[0011]

FIG. 1 shows the principle configuration of the present invention.

In the figure, reference numeral 1 denotes a resource management apparatus equipped with the present invention, which is used when computers 2-i (i = 1 to n) belonging to the own apparatus are composed of a mixture of different types of computers. 2-i realizes that the revised resources to be used are synchronously used according to the automation configuration.

In order to realize this processing, the resource management device 1 of the present invention obtains a means 10, a notification means 11, a collection means 12, an instruction means 13, a reception means 14, and a second instruction means. 15 and transmission means 16.

The obtaining means 10 obtains version number information of resources to be used by the computers 2-i specified by the combination of the models of the computers 2-i under its own device. The notifying unit 11 notifies each computer 2-i under its own device of the version number information of the resource to be downloaded according to the version number information obtained by the obtaining unit 10.

The collection means 12 is provided for each computer 2 under its own device.
-i, the version information of the resources downloaded by the computers 2-i in response to the version information notified by the notifying means 11 is collected. When the version number information collected by the collection unit 12 matches the version number information obtained by the obtaining unit 10, the instruction unit 13 sends a notification from the notification unit 11 to each computer 2-i under its own device. In response, an instruction is given to switch to the downloaded resource.

The receiving means 14 is provided for each computer 2 under its own device.
-i, information about whether or not the switching of the resource indicated by the indicating means 13 has been successful is received. Second indicating means 15
Instructs the computers 2-i under its own device to switch to the resources used before the switching when the switching indicated by the instruction means 15 is not successful. When the switching instructed by the instructing unit 13 succeeds, the transmitting unit 16 transmits the version information of the resource to be used by each computer 2-i under its own device to the contact.

Here, the functions of the resource management device 1 of the present invention are specifically realized by a program, which is stored on a floppy disk or the like, or stored on a disk such as a server. The present invention is realized by installing them in the resource management device 1 and operating them on the memory.

In the resource management apparatus 1 of the present invention configured as described above, the obtaining means 10 uses the computers 2-i specified by the combination of the models of the computers 2-i under the own apparatus. Upon receiving the version information of the resource to be obtained, the notifying means 11 sends the version information of the resource to the computers 2-i under its own device in accordance with the version information obtained by the obtaining means 10.
The version information of the resource to be downloaded is notified.

Receiving this notification, each computer 2-i downloads the resource of the notified version number information. Therefore, the collection unit 12 sends the notification unit 1 from each computer 2-i under its own device.
In response to the version information notified by No. 1, the computer 2-i collects version information of the resources downloaded by the computers 2-i.

In response to this, when the version number information collected by the collection unit 12 matches the version number information obtained by the obtaining unit 10, the instruction unit 13 sends a message to each computer 2-i under its own device. Then, in response to the notification from the notifying unit 11, an instruction to switch to the downloaded resource is issued.

In response to this instruction, each computer 2-i executes switching to the downloaded resource in response to the notification from the notifying unit 11, and notifies whether or not the switching has been successful. , Receiving means 14 receives the information.

In response to this, the second instructing means 15 determines that the switching instructed by the instructing means 15 is not successful.
It instructs each computer 2-i under its own device to switch to the resource used before the switching. On the other hand, when the switching instructed by the instructing unit 13 succeeds, the transmitting unit 16 transmits the version information of the resource to be used by each computer 2-i under its own device to the contact.

As described above, the resource management device 1 of the present invention
In the case where each computer 2-i under its own device is composed of a mixture of different models, version number information of resources to be used by those computers 2-i to be specified by the combination of the models is described. Obtain, notify each computer 2-i of it, confirm that the desired resource is downloaded to each computer 2-i in response to this notification, and instruct batch switching to the downloaded resource As a result, each computer 2-i transfers the revised resources prepared for each model that guarantees the consistency of the entire system without depending on the manual work of maintenance personnel. And it can be used synchronously without error.

[0024]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail according to embodiments.

FIG. 2 shows an embodiment of a system configuration of a computer system equipped with the present invention.

In the figure, 20-i (i = 1 to N) is an SVP manager, and 30-i (i = 1 to n, m) is a computer (31 is a computer) managed by each SVP manager 20-i. Body,
32 is a service processor), and 40-i (i = 1 to N) are SVP managers 20-i and computers 30 under their control.
a remote maintenance center that updates the firmware used by the computer 30-i, and a public line network 60 that connects the remote maintenance center 50 and the SVP manager 20-i. .

As shown in FIG. 3, the SVP manager 20-i includes a gateway 200 for inputting a version number pattern set created by the remote maintenance center 50, and a gateway 2
00, a version number pattern management table 201 for managing a set of version number patterns to be input to a computer 30;
model information management table 202 for managing model information of -i
And a firmware version synchronization program 203 for controlling download of firmware to the computer 30-i managed by the own device and activation thereof.

On the other hand, as shown in FIG. 3, the service processor 32 of each computer 30-i stores an active HCP file 320 for storing the active firmware (HCP).
And a standby HCP file 321 for storing standby firmware, and a firmware switching program 322 for executing processing such as switching control of firmware from the standby system to the active system.

Here, the firmware version number synchronization program 203 developed on the SVP manager 20-i and the firmware switching program 322 developed on the service processor 32 are stored in a suitable recording medium such as a computer-readable semiconductor memory. Can be stored.

FIG. 4 shows an embodiment of model information managed by the model information management table 202, and FIG. 5 shows an embodiment of a version number pattern set managed by the version number management table 201.

As shown in FIG. 4 (a), the model information management table 202 provided in the SVP manager 20-i stores each computer 30-i under the management of the SVP manager 20-i.
In addition to managing information as to what kind of model is, as shown in FIG. 4B, it manages information as to what kind of those models are.

That is, for example, the model of the computer 30-1 with the computer number "1" is A, the model of the computer 30-2 with the computer number "2" is A, and the computer 30 with the computer number "3". The model of the computer 30-4 with the computer number "4" is A, the model of the computer 30-5 with the computer number "5" is A, and the computer of the computer number "6". The model of 30-6 is E, ..., "n"
The information that the model of the computer 30-n having the computer number of A is A is managed, and those models are A, C, and E.
It manages the information that is.

Here, the model information managed by the model information management table 202 is generated and registered according to the information collected from the service processor 32.

On the other hand, the version number pattern management table 201
As shown in FIG. 5, the version number describes that, for such a combination of computers 30-i, the version number of firmware to be used by each computer 30-i must be such. Manage a set of patterns.

For example, the version number pattern with the pattern ID “1” shown in the figure is the model A when the computer system is composed of the computers 30-i of the model A, the model C, and the model E.
Computer 30-i uses the firmware version number “0102 + 01A”, and the computer 30-i of model C uses the firmware version “0102 + 01A”.
It describes that the firmware 30 is used as the firmware version 201 + 02A, and that the computer 30-i of the model E must use the firmware version number "1020 + 01A".

The version number pattern of pattern ID "2" shown in the figure is the same as the computer 30-i of model A when the computer system is composed of computers 30-i of model A, model B and model G. i uses the firmware of version “0102 + 01A”, and the computer 30-i of model B uses the version “012 + 01A”.
02 + 01B "and the model G
Describes that the computer 30-i must use the firmware version number "0403 + 01G".

The version number described in this version number pattern is the edition level (the one described before the "+") indicating the version number of the entire firmware used by the computer 30-i.
And a release patch version number indicating the revision level with respect to the edition level (listed after “+” and has an ascending version number).

The firmware to be used by the computer 30-i is determined according to the version number composed of the edition level and the release patch version number.

For example, as shown in FIG.
If the edition level means six firmwares ~ and the release patch version number "01A" means to update the firmware to firmware 'and to update the firmware to firmware', the version "0102 + 01A" The number indicates that the firmware to be used is firmware '//
'/// meaning.

If the release patch version number “01B” issued next to the release patch version number “01A” means that the firmware is to be revised to firmware ″ and the firmware is to be revised to firmware ′. , “0102 + 01B” indicates that the firmware to be used is firmware ′ //
'' // '/.

The version pattern set managed by the version pattern management table 201 having such a data structure is created by the remote maintenance center 50 when the remote maintenance center 50 updates the firmware, and
00 will be registered.

FIGS. 7 to 9 show the SVP manager 20.
firmware version synchronization program 20 to be deployed to -i
3 and FIG. 10 and FIG.
FIG. 2 illustrates an embodiment of a processing flow executed by the firmware switching program 322 deployed in the service processor 32.

Next, the operation processing of the embodiment thus configured will be described in detail according to these processing flows.

First, the processing executed by the firmware version synchronization program 203 developed in the SVP manager 20-i will be described.

Firmware version number synchronization program 203
When the version number pattern managed by the version number pattern management table 201 is updated, as shown in the processing flow of FIG. 7 to FIG. Read a set of number patterns. That is, a set of version number patterns as shown in FIG. 5 is read.

Subsequently, in step 2, the model configuration of the computer 30-i under the management of the SVP manager 20-i is read from the model information management table 202. That is, model configuration information as shown in FIG. 4B is read.

Subsequently, in step 3, by extracting a model corresponding to the read model configuration from the read version number pattern set, the computer 30-i managed by its own SVP manager 20-i is extracted. Extract the applied version number pattern.

For example, when reading a set of version number patterns as shown in FIG. 5, when the model configuration information indicates that it is composed of computers 30-i of model A, model C and model E, The computer 30-i of the model A has the version number “01”
02 + 01A "and the model C
Computer 30-i uses the firmware version number "0201 + 02A", and the computer 30-i of model E uses the version number "1".
The version number pattern with the pattern ID “1” that describes that the firmware “020 + 01A” must be used is extracted.

Subsequently, in step 4, for all the computers 30-i under the control of the own SVP manager 20-i,
When it is determined whether a firmware download instruction has been issued or not, and it is determined that a computer 30-i to which a download instruction has not been issued remains, the process proceeds to step 5 and the computer 30-i is selected from among them. Select one.

Subsequently, in step 6, the selected computer 30 is referred to by referring to the model information management table 202.
Specify the model of -i. That is, by referring to the management data of FIG. 4A managed by the model information management table 202, the model of the selected computer 30-i is specified.

Subsequently, in step 7, the version number of the firmware to be used by the selected computer 30-i is determined by searching the version number pattern extracted in step 3 using the specified model as a search key. . That is, the firmware version number that guarantees the consistency of the entire system is determined.

For example, the computer 30-i of the model A has a version number “0”.
102 + 01A ", the computer 30-i of the model C must use the firmware of the version" 0201 + 02A ", and the computer 30-i of the model E must use the firmware of the version" 1020 + 01A ". If the specified model is A when extracting the version number pattern that describes the firmware, the firmware having the version number “0102 + 01A” is determined as the version number of the firmware to be used by the selected computer 30-i. Will do.

Subsequently, at step 8, the selected computer 3
After instructing 0-i to download the firmware of the determined version number, the process returns to step S4.

Thus, steps 4 to 8
When it is determined in step 4 that the instruction to download the firmware has been issued to all the computers 30-i in step 4, the process proceeds to step 9 (the processing flow in FIG. 8) and the destination of the download instruction is determined. Is the own SV
It waits for a report on the download instruction from each computer 30-i under the control of the P manager 20-i.

That is, when the firmware switching program 322 expanded on the service processor 32 receives the firmware download instruction, as described later, the firmware switching program 322 downloads the specified firmware from the remote maintenance center 50 and downloads the standby HCP. The firmware is stored in the file 321, and the version number of the downloaded firmware is reported.

If it is detected in step 9 that a report for the download instruction has been returned, the process proceeds to step 10 to receive the version number of the returned firmware, and in step 11 the download instruction is issued. It is determined whether or not reports have been received from all of the computers 30-i. If any of the computers 30-i have not been received yet, the process returns to step 9 to return to the report from the computers 30-i. Wait for.

On the other hand, if it is determined in step 11 that reports have been received from all the computers 30-i to which the download instruction has been issued, the process proceeds to step 12, where each computer 30-i
Compare the firmware version (the version of the firmware downloaded to the standby system) collected from -i with the firmware version indicated in step 8.

Subsequently, at step 13, it is determined whether or not the two versions match by comparison, and when it is determined that they do not match, the process proceeds to step 14, where the remote maintenance center 50 is notified. Then, the firmware version number update failure is notified, and the process ends.

On the other hand, when it is determined in step 13 that the two edition numbers match, the process proceeds to step 15 and
Each computer 30 under the control of its own SVP manager 20-i
Instruct -i to switch the firmware of the standby system to the active system.

In response to the switching instruction, the firmware switching program 322 developed in each service processor 32 performs processing for switching the standby firmware to the active firmware as described later.

Subsequently, in step 16, in accordance with the operation of the operator, the power supply is instructed to all the computers 30-i under the control of the own SVP manager 20-i.

In response to the power-off instruction, the firmware switching program 322 developed in each service processor 32 performs a power-off process as described later.

Subsequently, in step 17, in accordance with the operation of the operator, the power supply is instructed to all the computers 30-i managed by the SVP manager 20-i.

In response to the power-on instruction, the firmware switching program 322 developed in each service processor 32 performs a power-on process as described later. At this time, the newly downloaded firmware operates as the active system to start up the computer 30-i, and the firmware switching program 322 is executed.
Reports whether the computer 30-i has been started up by the processing.

In the following step 18 (the processing flow of FIG. 9), according to the report, the own SVP manager 2
It is determined whether or not all the computers 30-i under the management of 0-i have been started up. When it is determined that all the computers 30-i have been started up, the process proceeds to step 23, and the remote maintenance center 50 is notified. Then, the firmware version number update success is notified, and the process ends.

Upon receiving this success notification, the maintenance staff can obtain information required for the maintenance service as to which version of firmware each computer 30-i is operating.

On the other hand, when it is determined in step 18 that all the computers 30-i under the control of the own SVP manager 20-i have not started, the process proceeds to step 19, where the control is performed under the control of the own SVP manager 20-i. Is instructed to restore the firmware to the original system (return the firmware switched to the standby system to the active system).

In response to the switching instruction, the firmware switching program 322 developed in each service processor 32 performs processing for switching the firmware switched to the standby system to the original active system, as described later.

Subsequently, in step 20, according to the operation by the operator, the power supply is instructed to all the computers 30-i under the control of the own SVP manager 20-i.

In response to the power-off instruction, the firmware switching program 322 developed in each service processor 32 performs a power-off process as described later.

Subsequently, in step 21, according to the operation by the operator, the power supply is instructed to all the computers 30-i under the control of the own SVP manager 20-i.

In response to the power-on instruction, the firmware switching program 322 developed in each service processor 32 performs a power-on process as described later. At this time, the firmware that has been operating normally up to now operates again as the active system, so that the computer 30-i is started up.

Subsequently, in step 22, the remote maintenance center 50 is notified of the failure of updating the firmware version, and the processing is terminated.

In this way, the firmware version number synchronization program 203 determines the firmware version number that guarantees the consistency of the entire system according to the version number pattern obtained from the remote maintenance center 50, and updates each computer under management. After the firmware is downloaded to 30-i, all the computers 30-i are synchronized so that the firmware is operated.

Next, the processing executed by the firmware switching program 322 developed in the service processor 32 will be described with reference to the processing flows of FIG. 10 and FIG.

The firmware switching program 322 is
When a firmware download instruction is issued from the firmware version synchronization program 203, FIG.
As shown in the processing flow of (a), first, in step 1, the indicated firmware version is received.

Subsequently, at step 2, the remote maintenance center 5
From 0, the specified firmware is downloaded and stored in the standby HCP file 321. In the subsequent step 3, the version number of the downloaded firmware is reported to the SVP manager 20-i.

As described above, when the firmware version synchronization program 203 issues a firmware download instruction in accordance with the processing in step 8 of the processing flow of FIG. 7, the firmware switching program 322 acquires the firmware from the remote maintenance center 50. The firmware version is stored in the standby HCP file 321, and the downloaded firmware version is reported to the firmware version synchronization program 203.

The firmware switching program 32
FIG. 10B is a diagram showing a state where the firmware version number synchronization program 203 issues a firmware switching instruction.
As shown in the processing flow of FIG.
1 is switched to the active HCP file 320, and the active HCP file 320 is switched to the standby HCP file 321, so that the standby HCP file 3
The firmware stored in 21 is switched to the active system, and the firmware stored in the active HCP file 320 is switched to the standby system.

As described above, the firmware switching program 322 executes the firmware version number synchronization program 203 according to the processing of step 15 of the processing flow of FIG.
Issues a firmware switching instruction, the standby HC
Processing is performed to switch the firmware newly downloaded to the P file 321 to the active system.

The firmware switching program 32
When the power-off instruction is issued from the firmware version number synchronization program 203, the power of the corresponding computer 30-i is turned off as shown in the processing flow of FIG.

As described above, when the firmware version number synchronization program 203 issues a power-off instruction in accordance with the processing of step 16 of the processing flow of FIG. 8 or step 20 of the processing flow of FIG. The processing is performed such that the power of the computer 30-i is turned off.

The firmware switching program 32
When a power-on instruction is issued from the firmware version synchronization program 203, as shown in the processing flow of FIG. 11A, first, in step 1, the corresponding computer 30-i is turned on. I do.

Subsequently, in step 2, it is checked whether or not the corresponding computer 30-i has started according to the active firmware operating in response to the power-on, and when it is determined that the computer 30-i has started, Step 3
In step S4, the start is reported to the SVP manager 20-i, and when it is determined that the server does not start, the process proceeds to step S4, where the start is reported to the SVP manager 20-i.

As described above, when the firmware version number synchronization program 203 issues a power-on instruction in accordance with the processing of step 17 of the processing flow of FIG. 8 or step 21 of the processing flow of FIG. Then, the power of the computer 30-i is turned on, and processing is performed so as to report to the firmware version synchronization program 203 whether the computer 30-i has started up.

The firmware switching program 32
When the firmware version number synchronization program 203 issues an instruction to return the firmware of the standby system to the active system, as shown in the processing flow of FIG.
Replace the CP file 320 with the original standby HCP file 321
By switching the standby HCP file 321 to the original active HCP file 320,
The firmware stored in the active HCP file 321 is returned to the original standby system, and the firmware stored in the standby HCP file 321 is returned to the original active system.

As described above, the firmware switching program 322 executes the firmware version number synchronization program 203 according to the processing of step 19 of the processing flow of FIG.
Issues an instruction to return the firmware of the standby system to the active system, and performs processing so that the firmware that has been operating normally until now is returned to the active system.

As described above, the firmware switching program 322 implements the processing executed by the firmware version number synchronization program 203 by executing the processing in response to the instruction issued by the firmware version number synchronization program 203. Will be processed as follows.

The present invention has been described with reference to the illustrated embodiments.
The present invention is not limited to this. For example, in the embodiments, the present invention has been described using firmware as a specific example. However, the present invention can be applied to resources other than firmware.

In the embodiment, each SVP manager 2
Although a version number pattern required by another SVP manager 20-i is also distributed to 0-i, only the version number pattern required by the SVP manager 20-i is distributed. It may be.

[0091]

As described above, according to the present invention, when each computer under its own device is composed of a mixture of different models,
Obtain the version information of the resources to be used by those computers to be specified by the combination of the models, notify each computer of it, and download the desired resources to each computer in response to this notification. After confirming that the resource is downloaded, the user is instructed to perform a batch switch to the downloaded resource, and the switch to that resource is executed.
Each computer can use the revised resources prepared for each model that guarantees the consistency of the entire system synchronously without error without relying on the manual work of maintenance personnel.

[Brief description of the drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is an embodiment of the present invention.

FIG. 3 is an embodiment of the present invention.

FIG. 4 is an example of a model information management table.

FIG. 5 is an example of a version number pattern management table.

FIG. 6 is an explanatory diagram of a firmware update process.

FIG. 7 is a processing flow of a firmware version number synchronization program.

FIG. 8 is a processing flow of a firmware version number synchronization program.

FIG. 9 is a processing flow of a firmware version number synchronization program.

FIG. 10 is a processing flow of a firmware switching program.

FIG. 11 is a processing flow of a firmware switching program.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Resource management apparatus 2 Computer 10 Acquisition means 11 Notification means 12 Collection means 13 Instruction means 14 Receiving means 15 Second instruction means 16 Transmission means

Claims (4)

[Claims] An acquisition means for acquiring version information of a resource to be used by a computer which is specified by a combination of models of computers under its own device; Notification means for notifying each computer under its own device of version information of a resource to be downloaded; and downloading from each computer under its own device in response to the version information notified by said notification means. A collection unit that collects version information of the obtained resource, and, if the version information collected by the collection unit matches the version information obtained by the acquisition unit, downloads the file to each computer under its own device. Instruction means for instructing the switching to the selected resource. 2. The resource management device according to claim 1, wherein, when the switching instructed by the instructing means does not succeed, each of the computers under its own device is switched to the resource used before the switching. A resource management device, comprising: a second instruction means for instructing. 3. The resource management device according to claim 1, wherein, when the switching instructed by the instructing means is successful, the version number information of the resource to be used by each computer under its own device is transmitted to the contact. A resource management device comprising transmission means for transmitting. 4. An acquisition process for obtaining version information of a resource to be used by a computer, which is specified by a combination of models of computers under its own device; A notification process for notifying each computer under its own device of version information of a resource to be downloaded, and a download from each computer under its own device in response to the version information notified in the above notification process. Collection process to collect the version information of the resources that have been collected, and if the version information collected in the collection process matches the version information obtained in the acquisition process, download the A program recording medium characterized by recording a program for causing a computer to execute an instruction process for instructing switching to a selected resource.