EP1720097A1

EP1720097A1 - Firmware version managing method and computer system

Info

Publication number: EP1720097A1
Application number: EP05253488A
Authority: EP
Inventors: Kazuhiro Fujitsu Limited Yuuki
Original assignee: Fujitsu Ltd
Current assignee: Fujitsu Ltd
Priority date: 2005-03-18
Filing date: 2005-06-07
Publication date: 2006-11-08
Anticipated expiration: 2025-06-07
Also published as: US20060225069A1; JP4791061B2; JP2006260330A; EP1720097B1; US7681191B2

Abstract

Automated update to the firmware of the optimum version can be performed, for instance, when a system board 16 is exchanged. When a system board 16 is exchanged, a version change unit 15 compares the version of the firmware of the system board 16 with the version of the firmware of the corresponding partition stored in the partition-specific version storage unit 12. When they do not match, the version of the firmware of the system board 16 is updated to the same version stored in the partition-specific version storage unit 12.

Description

Background

The present invention relates to a firmware version managing method of a computer system having a plurality of partitions in which a plurality of operation systems can be operated, and an information processing device having a plurality of partitions in which a plurality of operation systems can be operated.
With a computer system for basic operations, it is essential to exchange hardware and load new firmware in an active state.
There are two methods for changing the function of a computer system, that is, exchanging a system board and loading new firmware of a system board.
The first method of exchanging a system board is to design a new board, necessarily exchanging the entire hardware, and require a larger number of steps than the second method of loading new firmware in designing and loading processes. Normally, when a board is exchanged or new firmware is loaded after a computer system is implemented and then modified, loading new firmware requires a shorter processing time.
In a computer system having a plurality of partitions in which a plurality of operating systems can be simultaneously operated, different versions of firmware can be used in the respective partitions. If a different version of firmware is used in each partition, it is necessary that the same version be used between the firmware of the replacing system board and the firmware of the partition to be used. Conventionally, in this case, the version of the firmware of each partition is checked by a person who exchanges a system board to ensure use of the same version.
Furthermore, when a partition is newly generated and a system board is expanded, it is desired that the firmware to be implemented in the system board is the latest version. However, it is not necessarily the latest version of firmware implemented in the current system board.
Reference is made to Patent Document 1, Japanese Published patent Application No. 2002-358209 , and Patent Document 2, Japanese Published Patent Application No. 2004-21463 .
Patent Document 1 describes the method of efficiently performing a rewriting operation to update the version of firmware by determining whether or not the existing version and the latest version of the firmware for control of the output of information equipment match each other, updating the version to the latest version when they do not match, and selecting the latest version or the existing version and performing output processing depending on a result of the update.
Patent Document 2 describes the method of loading the optimum replacing firmware in the system configuration of the current peripheral device and the host computer from an automatically specified place when the driver is activated so that the firmware can be optimally updated.

Summary of the Invention

The present invention aims at automatically updating the firmware to the optimum version when the system board is exchanged, etc.
The present invention envisages a firmware version managing method of a system board of a computer system having a plurality of partitions in which a plurality of operating systems can be operated and each partition is configured by one or more system boards, associates the version of the firmware being used in each partition with each partition and stores the association result in a partition-specific version storage unit, determines when the system board is exchanged whether or not the version of the firmware of the newly used system board matches the version of the firmware of the corresponding partition stored in the partition-specific version storage unit, and updates the firmware of the newly used system board to the same version as the firmware of the partition stored in the partition-specific version storage unit.
According to embodiments of the present invention, when a system board is exchanged, the firmware of the system board can be automatically updated to the version of the firmware of the partition in which the system board is used.
In firmware version managing methods using the present invention, when the information about the partition assigned to each system board is stored in the system board configuration information storage unit, and the system board is exchanged, the information in the system board configuration information storage unit is referred and the partition of the system board to be exchanged is designated, the version of the firmware of the designated partition is obtained from the partition-specific version storage unit, and the firmware of the newly used system board is changed to the same version as the obtained firmware.
With the above-mentioned configuration, when a system board is exchanged, the partition assigned to the system board to be exchanged is designated according to the information stored in the system board configuration information storage unit in order automatically to update to the firmware of the version which is the same as the version of the firmware being used in the designated partition.
In firmware version managing methods using the present invention, when the board identification information for identification of the system board is stored in the system board configuration information storage unit, the firmware of the latest version is stored in the latest version storage unit, and the new partition is set and the new system board is used, the board identification information about the newly used system board is compared with the board identification information stored in the system board configuration information storage unit and it is determined whether or not the system board has not been registered. If the newly used system board has not been registered, then the firmware of the newly used system board is changed to the firmware of the latest version stored in the latest version storage unit.
With the above-mentioned configuration, when a new partition is set and a new system board is implemented, the firmware of the system board can be automatically updated to the firmware of the latest version.
In firmware version managing methods using the invention, the system board includes a first non-volatile memory storing the firmware of the version being used in the currently assigned partition, and a second non-volatile memory storing the firmware of the version used in the exchanged-to partition, and exchanges between the first and second non-volatile memory when the assigned-to partition of the system board is exchanged.
With the above-mentioned configuration, by exchanging the non-volatile memory loaded into the system board, the firmware of the version adapted to the exchanged-to partition can be quickly adopted.
In firmware version managing methods of the present invention, if an abnormal operation occurs as a result of updating the version of the firmware of the system board of the specific partition, then the version of the firmware of the system board of the specific partition in which the abnormal operation occurs is returned to the old version of the firmware of the specific partition stored in the partition-specific version storage unit with each partition kept in the active state.
With the above-mentioned configuration, if an abnormal operation occurs as a result of changing the version of the firmware, then the version before the change can be recovered to the original state.
In firmware version managing methods using the above-mentioned invention, when the firmware of a plurality of versions is stored in the backup storage unit, and the system board is exchanged, the version of the firmware of the newly used system board is compared with the version of the firmware of the corresponding partition stored in the partition-specific version storage unit. If the versions do not match each other, the version of the firmware of the partition is obtained from the partition-specific version storage unit, the firmware of the version is read from the backup storage unit, and the firmware of the newly used system board is changed to the firmware of the version read from the backup storage unit.
With the above-mentioned configuration, if a system board is exchanged and the version of the firmware of the newly used system board is different from the version of the firmware of the partition assigned to the system board, then the update can be performed to the optimum version using the firmware stored in the backup storage unit.

Brief Description of the Drawings

For a better understanding of the invention embodiments of it will now be described, by way of example, with reference to the accompanying drawings, in which:

Fig. 1: shows the basic configuration of a computer system;
Fig. 2: shows the configuration of the computer according to an embodiment of the present invention;
Fig. 3A: shows partition-specific respective version number information;
Fig. 3B: shows system board configuration information;
Fig. 3C: shows the configuration of OBP backup information;
Fig. 4: is a flowchart of an automated update process on the version number when a system board is exchanged;
Fig. 5: is an explanatory view showing the automated update process when a system board is exchanged;
Fig. 6: is a flowchart of the automated update process on the version number of the system board of a new partition;
Fig. 7: is a flowchart of the automated update process when the configuration of a partition is changed;
Fig. 8: is an explanatory view showing the exchange of a bank; and
Fig. 9: is a flowchart of the process of returning to an old version.

Description of Embodiments

The embodiments of the present invention are described below by referring to the attached drawings. Fig. 1 shows the basic configuration of a computer system 11 relating to the present invention.
The computer system 11 has a plurality of partitions in which a plurality of operating systems can be simultaneously operated, and each partition is configured by one or more system boards 16a - 16n in which firmware is implemented.
The computer system 11 shown in Fig. 1 comprises: a partition-specific version storage unit 12 for storing each partition as associated with the versions of the firmware of the system boards 16a - 16n assigned to each partition; a system board configuration information storage unit 13 for storing a partition assigned to a system board associated with the board identification information for identification a system board; and a latest version storage unit 14 for storing firmware of the latest version.
It further comprises a version change unit 15 for updating the version of the firmware of the system boards 16a - 16n. When a system board is exchanged, the version change unit 15 compares the version of the firmware implemented in a newly used system board with the version of the firmware of the corresponding partition stored in the partition-specific version storage unit 12. If they do not match, the firmware of the newly used system board is changed to the same version as the firmware of the corresponding partition stored in the partition-specific version storage unit 12.
When a new partition is set, the version change unit 15 compares the board identification information about the newly used system board with the board identification information stored in the system board configuration information storage unit 13, and determines whether or not the system board has not been registered. If it has not been registered, the firmware of the newly used system board is updated to the latest version.
Fig. 2 shows the configuration of the central portion of a computer 21 (information processing device) according to an embodiment of the present invention. The computer 21 has a plurality of partitions in which a plurality of operating systems can be simultaneously operated.
The computer 21 comprises a service processor board 22, and one or more system boards 23a, 23b, 23c, ... configuring a plurality of partitions. The system boards 23a, 23b, 23c, ... are loaded with a CPU, memory, a controller, etc.
The service processor board 22 comprises a service processor (CPU) 24; rewritable non-volatile memory (FMEM) 25 comprising flash memory, etc. for storing a control program executed by the service processor 24; main storage memory 26; rewritable non-volatile memory 27 which comprises a disk device or flash memory, etc. and stores management information about the system boards 23a, 23b, 23c, ...; and a controller 28 for controlling the communication of data with the system boards 23a, 23b, 23c, ....
In the following explanation, a system board 23 refers to all the system boards 23a, 23b, 23c ... or a specific system board.
The system board 23 is loaded with two rewritable non-volatile memory (FRAM) 29a and 29b such as flash memory, etc. The two non-volatile memories (FRAM) 29a and 29b store an initialization program (open boot program (OBP)) of the same or different versions. The initialization program (OBP, firmware) performs a diagnosis on a system board, initialization, download of an OS from the disk device not shown in the attached drawings, etc.
Thus, by having two non-volatile memory 29a and 29b, for example, when a partition to which a system board is assigned is exchanged, the initialization program of the version being used in the currently assigned partition is stored in the non-volatile memory 29a, and the initialization program of the version used in the exchanged-to partition is stored in the other non-volatile memory 29b. By switching between the non-volatile memory 29a and 29b, a quick exchange can be made to the version of the initialization program being used in the exchanged-to partition.
The non-volatile memory 27 of the service processor board 22 is configured by a partition-specific respective version number information storage unit 31, a system configuration information storage unit 32, a latest HCP (hardware control program) storage unit 33, and an initialization program (OBP) backup storage unit 34.
The partition-specific respective version number information storage unit 31 stores the information about the version (version number) of the initialization program used in each partition as associated with the partition number.
Fig. 3A shows the configuration of a partition-specific respective version number information 41 stored in the partition-specific respective version number information storage unit 31.
As shown in Fig. 3A, the partition-specific respective version number information 41 is configured by a set of data including: a partition number; a current version number of the initialization program of the system board 23 assigned to each partition; a bank-specific version number of an initialization program stored in the two non-volatile memory 29a and 29b of the system board 23; a current bank number indicating a bank 0 or 1 of the currently used bank; and the previous version number in the initialization program stored in the two banks.
By referring to the partition-specific respective version number information 41, for example, the version of the current initialization program of the partition of the partition number of 0 is A, the two banks of the system board 23 assigned to the partition store the initialization program of the same version A, and the currently used bank is the bank 1, and no previous version number is stored. Additionally, the version of the current initialization program of the partition of the partition number of 1 is A, the bank 0 (for example, corresponding to the non-volatile memory 29a) stores the initialization program of the version A, the bank 1 (for example, corresponding to the non-volatile memory 29b) stores the initialization program of the version B, the currently used bank is the bank 1, and the version A is the previous version.
Fig. 3B shows the configuration of system board configuration information 42 stored in the system configuration information storage unit 32.
As shown in Fig. 3B, the system board configuration information 42 is configured by a set of data including: a system board number (SB number) designated in dependence on the position into which the system board 23 is inserted; a partition number assigned to each system board 23; and a board serial number (board identification information) uniquely assigned to each system board 23.
By referring to the board serial number of the system board configuration information 42, for example, it is determined whether or not the system board 23 inserted into the position of a specific system board number is a new system board 23.
The latest hardware control program (HCP) storage unit 33 stores the initialization program of the latest version, the latest firmware of the service processor board 22, etc.
The initialization program (OBP) backup storage unit 34 stores several generations of initialization programs for backup.
Fig. 3C shows the configuration of an OBP backup information 43 stored in the OBP backup storage unit 34.
As shown in Fig. 3C, the OBP backup information 43 is configured as a set of data including: version number information indicating the version of an initialization program; "valid" indicating whether or not the initialization program can be rewritten; and an initialization program (firm information). In Fig. 3C, 'x' indicates data can be rewritten, and 'o' indicates data cannot be rewritten.
By reading an initialization program of a specific version of the OBP backup information 43 and writing the read initialization program to the non-volatile memory 29a or 29b of the system board 23, the initialization program implemented in the system board 23 can be rewritten into a desired version. The initialization program of the version number not to be stored any more is set the validity as "invalid", thereby allowing the area to be overwritten when the storage capacity of the initialization program (OBP) backup storage unit 34 becomes short.
Next, the processing operation of the computer 21 with the above-mentioned configuration is explained below by referring to the flowchart shown in Figs. 4, 6, 7 and 9. The process described below is performed by the service processor 24 of the service processor board 22.
First, the process of automatically updating the initialization program implemented in the system board 23 to the optimum version when the system board 23 is exchanged is explained below by referring to the flowchart shown in Fig. 4.
When the insertion of the system board 23 is detected and a system board exchanging event is received (S11 in Fig. 4), control is passed to step S12, and the following process is performed.
The system board number (for example, corresponding to the insertion position of the system board 23) is recognized from the position of the inserted system board 23, the system board configuration information 42 is referred to, and the board serial number corresponding to the system board number is obtained. Since the board serial number points to the board serial number of the system board 23 before the exchange, the serial number is compared with the input serial number of the system board 23.
In the next step S13, it is determined whether or not the serial numbers match. If the serial numbers do not match (NO in S13), control is passed to step S14, the system board configuration information 42 is referred to, and the partition number corresponding to the system board number is obtained. Then, the version number (version) of the initialization program corresponding to the partition number obtained by referring to the partition-specific respective version number information 41 is obtained.
In the next step S15, it is determined whether or not the version number of the initialization program implemented in the inserted system board 23 matches the version number of the initialization program being used in the corresponding partition.
When the version numbers do not match (NO in S15), control is passed to step S16, the initialization program of the same version number as the initialization program being used in the corresponding partition is retrieved from the initialization program (OBP) backup storage unit 34, and the initialization program of the version number obtained in the retrieval is written to the non-volatile memory 29a or 29b of the newly inserted system board 23, thereby updating the initialization program.
By the above-mentioned process in steps S11 to S16, when the system board 23 is exchanged, the version number of the initialization program of the newly inserted system board 23 can be automatically updated so that the version number can match the version number of the initialization program of the partition assigned to the system board. Thus, the operation of matching the version numbers of the initialization program is not required when the system board 23 is exchanged. Additionally, the occurrence of a malfunction caused by the non-matching version numbers of the initialization program of the system board 23 in the same partition can be prevented.
The process of updating the initialization program of the system board 23 to the optimum version number is explained below, referring to Fig. 5.
When the exchange of a specific system board 23 is detected, the partition number of the system board 23 is obtained from the system board configuration information 42. If it is found that the partition number is, for example, a partition number #0, then the version number of the initialization program (OBP) of the partition number #0 is obtained by referring to the partition-specific respective version number information 41 of the partition-specific respective version number information storage unit 31. If the version number of the initialization program is obtained, then the initialization program of the corresponding version number is downloaded from the initialization program (OBP) backup storage unit 34 (OBP of the version 1 in Fig. 5). Then, the initialization program of the version 1 downloaded to the non-volatile memory 29a or 29b of the system board 23 to be exchanged is written.
Thus, the version number of the initialization program of the system board 23 to be exchanged can be automatically updated so that it matches the version number of the initialization program being used in the partition to which the system board 23 is assigned.
Fig. 6 is a flowchart of the automated update process of the initialization program when a new partition is generated, and the system board 23 used in the new partition is expanded.
When a system board 23 insertion event indicating that the system board 23 has been inserted is received (S21 shown in Fig. 6), the board serial number of the inverted system board 23 is compared with the board serial number of the system board number of the system board configuration information 42 (S22).
It is determined whether or not the inserted system board is a new system board depending on whether or not the board serial numbers match (S23).
If a new system board 23 is inserted (YES in S23), then control is passed to step S24, the version number of the initialization program (OBP) stored in the non-volatile memory (EMEM) 29a or 29b of the inserted system board 23 is read, and the version number of the initialization program is compared with the latest version of the initialization program stored in the latest HCP storage unit 33. Then, in the next step S25, it is determined whether or not the version numbers match.
If the version number of the initialization program of the newly inserted system board 23 does not match the latest version number (NO in S25), then control is passed to step S26, the initialization program of the latest version stored in the latest HCP storage unit 33 is read, and the initialization program of the latest version is written to the non-volatile memory 29a or 29b of the system board 23, thereby updating the initialization program.
If it is determined in step S23 that it is not the newly inserted system board 23 (NO in S23), or if it is determined in step S25 that the version number of the initialization program of the newly inserted system board 23 matches the version number of the latest version (YES in S25), the process terminates immediately.
If a partition is newly generated by the process in steps S21 through S26, and a new system board 23 is inserted, then the new system board 23 can be automatically updated to the initialization program of the latest version number. Thus, when a partition is updated, the initialization program implemented in the system board 23 being used in the partition can be set to the latest version number.
Fig. 7 is a flowchart of the automated update process on the version number of the initialization program when a standby system board or the system board 23 assigned to a specific partition is dynamically exchanged to another partition in the active state.
When a transfer event of exchanging a partition of the system board 23 is received (S31 in Fig. 7), the version number of the initialization program of the system board 23 to be transferred is obtained by referring to the system board configuration information 42, and further by referring to the partition-specific respective version number information 41, the version number of the initialization program of the transferred-to (exchanged-to) partition is obtained to compare them (S32). In the next step S33, it is determined whether or not the version number of the initialization program of the system board 23 to be transferred matches the version number of the initialization program of the transferred-to partition.
If the version numbers do not match (NO in S33), then control is passed to step S34, the initialization program having the same version number as the initialization program of the transferred-to partition is read from the OBP backup storage unit 34, and the initialization program is written to the non-volatile memory of the system board 23 to be transferred.
According to the present embodiment, since the system board 23 is loaded with the two non-volatile memories 29a and 29b as the current bank and the reserve bank, the initialization program of the version number of the transferred-to partition is written to the non-volatile memory 29b of the reserve bank.
If the initialization program of the same version number as the transferred-to partition has already been stored in the non-volatile memory 29b of the reserved bank, then the process in step S35, not in step S34, is performed. In the process in step S35, the program is exchanged to the initialization program stored in the reserved bank as a result of exchange in bank. Thus, when the partition assigned to the system board 23 is exchanged, the necessity to download the initialization program of the same version number as the exchanged-to partition, and write it to the non-volatile memory 29a (or 29b) on the system board 23 is eliminated, thereby shortening the time required to exchange the partition.
Fig. 9 is a flowchart of the process of returning to the previous version when an abnormal operation occurs as a result of updating an initialization program.
If a system become inoperable or a user detects an abnormal operation as a result of updating the initialization program (OBP) of a specific partition (S41 in Fig. 9), the user performs an operation of returning the initialization program to the previous version (S42).
When the operation of returning the initialization program to the previous version is detected, the partition-specific respective version number information 41 is referred to in step S43, and the previous version number of the initialization program of the partition is obtained. If the previous version is stored in the reserved bank of the system board 23, the current bank is exchanged to the reserved bank to switch the version number of the initialization program. If the previous version is not stored in the reserved bank, the previous version is read from the OBP backup storage unit 34, and written to the reserved bank of the system board 23. Then, the bank is switched to the reserved bank.
If an abnormal condition occurs as a result of updating the initialization program of the system board of a specific partition in the processes in steps S41 through S43, the version number of the previous version of the partition is obtained from the partition-specific respective version number information 41, and the initialization program of the system board is rewritten to the initialization program of the previous version, thereby returning to the previous state.
The present invention can also be applied to other firmware, and is not limited to initialization programs.
In the present embodiment, the partition-specific respective version number information 41 and the system board configuration information 42 are stored as separate information, but they can be configured as a single set of information.
Using the present invention, when a system board is exchanged, the firmware of the system board can be automatically updated to the version applicable to the partition in which the system board is used.

Claims

A firmware version managing method of a system board of a computer system having a plurality of partitions in which a plurality of operating systems can be operated, and each partition is configured by one or more system boards (16; 23), wherein:
a version of the firmware used in each partition is associated with each partition and stored in a partition-specific version storage unit (12); and

when the system board (16) is exchanged, it is determined whether or not a version of the firmware of a newly used system board (16) matches a version of the firmware of a corresponding partition stored in the partition-specific version storage unit (12), and when the versions do not match, the firmware of the newly used system board (16) is changed to the same version as the firmware of the partition stored in the partition-specific version storage unit (12).
A method according to claim 1, wherein:
information about the partition assigned to each system board is stored in a system board configuration information storage unit (13); and

when the system board (16) is exchanged, the information in the system board configuration information storage unit (13) is referred to in designating a partition of the system board (16) to be exchanged, the version of the firmware of the designated partition is obtained from the partition-specific version storage unit (12), and the version of the firmware of the newly used system board (16) is changed to the same version as the obtained firmware.
A method according to claim 1 or 2, wherein:
board identification information for identification of the system board is stored in a system board configuration information storage unit (13);

firmware of a latest version is stored in a latest version storage unit (14); and

when a new partition is set and a new system board (16) is used, board identification information about the newly used system board (16) is compared with board identification information stored in the system board configuration information storage unit (13) and it is determined whether or not the system board (16) has not been registered, and when the newly used system board (16) has not been registered, the firmware of the newly used system board (16) is changed to the firmware of the latest version stored in the latest version storage unit (14).
A method according to any preceding claim, wherein:
the system board (16) comprises first non-volatile memory (29a) storing the firmware of the version used in a currently assigned partition, and a second non-volatile memory (29b) storing the firmware of the version being used in an exchanged-to partition; and

when an assigned-to partition of the system board (16) is exchanged, the first and second non-volatile memory (29a) (29b) are switched to each other.
A method according to any preceding claim, wherein:
when an abnormal operation occurs as a result of updating the version of the firmware of the system board (16) of the specific partition, the version of the firmware of the system board (16) of the specific partition in which the abnormal operation has occurred is returned to a previous version of the firmware of the specific partition stored in the partition-specific version storage unit (12) with each partition kept in an active state.
A method according to any preceding claim, wherein:
firmware of a plurality of versions is stored in a backup storage unit; and

when the system board (16) is exchanged, the version of the firmware of the newly used system board (16) is compared with the version of the firmware of the corresponding partition stored in the partition-specific version storage unit (12), when the versions do not match, the firmware of the version of the corresponding partition stored in the partition-specific version storage unit (12) is read from the backup storage unit, and the firmware of the newly used system board (16) is changed to the firmware of the version read from the backup storage unit.
An information-processing device having a plurality of partitions in which a plurality of operating systems can be operated, each partition being configured by one or more system boards (16; 23) in which firmware is implemented, comprising:
a partition-specific version storage unit (12) storing a version of the firmware used in each partition associated with each partition; and

a version change unit (15) determining, when the system board (16) is exchanged, whether or not a version of the firmware of a newly used system board (16) matches a version of the firmware of a corresponding partition stored in the partition-specific version storage unit (12), and changing, when the versions do not match, the firmware of the newly used system board (16) to a same version as the firmware of the partition stored in the partition-specific version storage unit (12).
An information-processing device according to claim 7, further comprising:
a system board configuration information storage unit (13) storing information about the partition assigned to each system board (16), wherein

when the system board (16) is exchanged, the version change unit (14) refers to the information in the system board configuration information storage unit (13) in designating a partition of the system board (16) to be exchanged, obtains the version of the firmware of the designated partition from the partition-specific version storage unit (12), and changes the version of the firmware of the newly used system board (16) to the same version as the obtained firmware.
An information-processing device according to claim 7 or 8, further comprising:
a system board configuration information storage unit (13) storing board identification information for identification of the system board (16); and

a latest version storage unit (14) storing firmware of a latest version, wherein

when a new partition is set and a new system board (16) is used, the version change unit (15) compares board identification information about the newly used system board (16) with the board identification information stored in the system board configuration information storage unit (13), determines whether or not the system board (16) has not been registered, and when the newly used system board (16) has not been registered, changes the firmware of the newly used system board (16) to the firmware of the latest version stored in the latest version storage unit (14).
An information-processing device according to claim 7, 8 or 9, wherein:
the system board (16) comprises a first non-volatile memory (29a) storing the firmware of the version used in a currently assigned partition, and a second non-volatile memory (29b) storing the firmware of the version being used in an exchanged-to partition; and

when a partition assigned to the system board (16) is exchanged, the first and second non-volatile memory (29a, 29b) are switched to each other.
An information processing device according to any of claims 7 to 10, wherein:
when an abnormal operation occurs as a result of updating the version of the firmware of the system board (16) of the specific partition, the version change unit (15) returns the version of the firmware of the system board (16) of the specific partition in which the abnormal operation has occurred to a previous version of the firmware of the specific partition stored in the partition-specific version storage unit (12) with each partition kept in an active state.