JP2013077331A - Disk array device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make the version number of each firmware stored in each unit of each function in a disk array device coincide with firmware to be operated.SOLUTION: A device has a plurality of units of the same kind in the device. A unit has a plurality of storage areas. Firmware for making the unit operate is stored in each of the plurality of storage areas. When the unit is mounted to the device, if the device recognizes the mounting of a first unit whose operating area is unwritable, the version number of firmware stored in each storage area of the first unit is compared with the version number of firmware stored in each storage area of a second unit operating in the device. If the version number of each firmware is not coincident in a comparison means, a storage area in which firmware executed by the first unit is coincided with each storage area of the second unit operating in the device.

Description

  The present invention relates to a disk array device. In particular, the present invention relates to maintenance technology when replacing units constituting a disk array device.

  The disk array device has a plurality of units. Each unit stores firmware for realizing the function of the unit. The disk array device operates as each unit executes the firmware. Each unit may fail. The failed unit in the disk array device is replaced.

  Since the disk array device requires continuous operation, the units of the disk array device have a redundant configuration having a plurality of units that realize the same function. In addition, the disk array device needs to avoid a decrease in operating performance of the entire disk array device after replacing the failed unit. The deterioration in performance is a state in which, for example, the unit malfunctions, the unit does not perform its original function, and affects the entire apparatus. In order to avoid a decrease in the performance of the processing of the disk array device, it is possible for the unit to be replaced to operate with the same firmware version as the other units operating in the disk array device. .

  Downloading firmware that matches the firmware version of the unit to be replaced with the firmware version of the unit operating in the disk array device as a method for incorporating the unit to be replaced into a conventional disk array device There is a way. For example, when the first unit incorporating the firmware in the apparatus is replaced with another second unit, the following method is used. First, the firmware version number of the second unit is compared with the firmware version number of the third unit operating in the apparatus. When the version numbers of the second unit and the third unit do not match, the version firmware of the third unit operating in the apparatus is downloaded to the storage area for storing the firmware of the second unit. . The second unit performs a predetermined operation according to the firmware by executing the version of firmware downloaded to the storage area (see, for example, Patent Document 1).

  If a failure occurs while the disk array device is in operation, it is necessary to reproduce the situation where the failure occurred in the disk array device in order to investigate the cause of the failure. However, the prior art does not consider firmware that the unit does not execute. Therefore, the conventional technique has a problem that the situation in which the problem occurs cannot be accurately reproduced.

Further, the conventional technology does not consider firmware that is not executed by the unit. Therefore, when a disk array device having units capable of storing a plurality of firmware in the storage area is restarted, each unit has a problem of executing firmware different from that before the restart after the restart.
JP 2005-71042 A

  In order to solve the above problems, an object of the present invention is to unify the version number of each firmware stored in each unit for each function in the disk array device and the firmware to be operated.

  The disk array device of the present invention includes a first unit, a second unit that operates in a redundant configuration with the first unit, a control unit that performs firmware update control, and a storage unit that stores firmware of each version number Each of the first unit and the second unit includes a first storage area, a second storage area, a version of firmware stored in the first storage area, and a second storage area. The third version stores the version number of the firmware stored in the storage area, and the identification number indicating whether the operation area for storing the firmware for operating the first unit and the second unit is the first storage area or the second storage area. And the operation area of the first unit is not writable, and the control unit, when the first unit is replaced due to a failure, Version number of firmware stored in the first storage area, which is the operation area of the first unit, when the identification numbers of the operation areas of both the unit and the second unit are the same indicating the first storage area Is compared with the firmware version stored in the first storage area of the second unit, and the firmware version of the operating area is different, and the operating area of the first unit is specified. Compare the version of the firmware stored in the second storage area with no firmware and the version of the firmware stored in the first storage area, which is the operation area of the second unit. Firmware corresponding to the firmware version number of the operating area of the second unit is acquired from the storage unit and stored in the second storage area of the first unit with no specified operating area. In addition, after rewriting the identification number of the operation area of the first unit from the first storage area to the second storage area, the first unit is restarted, and after the restart, the first unit to be replaced and the first unit Since the identification numbers of the operation areas of the two units are different, the firmware corresponding to the firmware version number of the operation area of the second unit is acquired from the storage unit and stored in the first storage area with no specified operation area. After rewriting the identification number of the operating area of the first unit from the second storage area to the first storage area, restarting the first unit, and operating the first unit and the second unit after restarting Since the area identification number and the firmware version number of the operating area are the same, the firmware version number of each second storage area where the operating area of the first unit and the second unit are not specified is compared. When they are different from each other, the firmware corresponding to the firmware version number stored in the second storage area of the second unit is acquired from the storage unit and stored in the second storage area of the first unit.

  According to the present invention, it is possible to unify the firmware version number of the unit to be replaced and the firmware version number of the unit operating in the disk array apparatus. Furthermore, it is possible to unify the number of the operation area of the storage means of the unit to be exchanged and the number of the operation area of the storage means of the unit to be exchanged of the unit operating in the disk array apparatus. It is possible to provide a disk array device that prevents malfunction of a unit due to a difference in the version of firmware of a unit to be replaced.

  FIG. 1 is a configuration diagram of a disk array device 1 of the present embodiment. There are many types of units constituting the disk array device 1. CM (Controller Module) units 2 and 3 control the entire disk array device 1. SVC (Service Controller) units 41 and 42 perform power source monitoring and control of the entire apparatus. CA (Channel Adapter) units 43 and 44 transmit and receive information between external devices and CMs 2 and 3. The external device is, for example, a host device. DEs (Device Enclosures) 47 and 48 store a plurality of magnetic disk devices. PBC (Port Bypass Circuit) units 45 and 46 control and monitor the DE. Power supply units (PSU) units 49 and 50 supply power to other units. BU (Battery unit) units 51 and 52 supply power in the event of a power failure. RT (Router) units 53 and 54 connect between CM2 and CM3, and between CM2 and CM3 and PBC45 and PBC46, and perform routing. Each unit is connected by a bus 4.

  The disk array device 1 is required to always operate in order to respond to the host device via CA43 and CA44. Accordingly, each unit of the disk array device 1 has a redundant configuration having a plurality of units that perform the same function. For example, the disk array device 1 has two CMs, CM2 and CM3. With this configuration, even if one of the units fails, the operation as a whole of the disk array device 1 is not stopped by the continuous operation of the unit that has not failed. In addition, between units that execute the same function, the version number of firmware stored in the unit, the firmware to be executed, and the firmware to be executed after rebooting are all set to match. Accordingly, settings between units that execute the same function are unified. Firmware is software embedded in the unit to perform basic control of the unit. It is fixedly mounted on the unit and is not changed much. It is stored in a ROM or flash memory built in the unit. Many of the firmware can be changed later to add unit functions or correct defects. The number attached to identify the revised firmware is called the version number. Therefore, units that execute firmware having different version numbers execute different processes.

The disk array device 1 has a system disk 90 and a system disk 91 in the magnetic disk devices in the DEs 47 and 48. The system disk 90 and the system disk 91 store a firmware file 92 and a file 93 to be downloaded to each unit in the disk array device 1. System disks and files are also redundant. Each unit functions by downloading firmware and operating in accordance with the firmware instruction group. The file 92 stores firmware of each version number.
Therefore, the file 92 is configured to have a plurality of versions of firmware even if they are firmware of the same unit. Each unit constituting the disk array device 1 can be classified into two types. The first type of unit is a unit capable of downloading firmware to the operation area of the storage means. The second type of unit is a unit in which firmware cannot be downloaded to the operation area of the storage means. For the following explanation, a unit to be exchanged is referred to as a unit 70, and a unit that operates in the disk array device 1 is referred to as a unit 80.

  A unit in the disk array device 1 to be exchanged in this embodiment will be described. FIG. 2 is a block diagram of the unit. The unit 60 includes an execution unit 61, a main memory 62, a storage unit 63, and an interface unit 64. The execution unit 61, the main memory 62, the storage unit 63, and the interface unit 64 are connected by a bus 65.

  The execution unit 61 executes processing according to the firmware loaded in the main memory 62. The execution unit 61 calls the firmware from the storage unit 63 and expands it in the main memory 62. The unit 60 executes processing corresponding to the firmware read out to the main memory 62. Therefore, the unit 60 executes different processes when the firmware version is different. The storage capacities of the main memory of each unit in the disk array device 1 are different. A unit equipped with a large-capacity main memory develops firmware stored in a compression format in the storage means on the main memory. A unit equipped with a large-capacity main memory operates by deploying all firmware on the main memory. The unit having a large capacity main memory is, for example, a CM. A unit having a large-capacity main memory does not generate a read process for the storage means after the firmware is expanded in the main memory. Therefore, the firmware in the storage means can be updated. Units with large capacity main memory are expensive. On the other hand, a unit equipped with a small-capacity main memory cannot deploy all the firmware stored in the storage means on the main memory. This is because the main memory capacity is insufficient. Examples of the unit equipped with the small-capacity main memory include a PBC (Port Bypass Circuit) unit which is a control unit and an SVC (Service Controller) unit which performs power source monitoring and control of the entire apparatus. Units with small capacity main memory are inexpensive. Some units equipped with a small-capacity main memory have a file system in the storage means. A unit having a file system divides and manages a plurality of firmware for each function of the unit. When the unit operates in the disk array device, the execution unit of the unit expands only the firmware necessary for the current operation of the unit from the file system in the storage unit to the main memory. Accordingly, a unit employing a file system always reads from an area in the storage unit where the operating firmware is stored while the unit is in operation.

  The main memory 62 is a memory in which the firmware stored in the storage unit 63 is expanded. For example, a RAM. The interface unit 64 is connected to CM2 and CM3. When information is received from CM2 or CM3, it is transferred to the execution unit 61. The result of processing performed by the execution unit 61 of the unit 60 is transferred to the CM 2 or CM 3.

  The storage unit 63 stores firmware. The storage means 63 has a plurality of storage areas. The storage unit 63 includes a first storage area 631, a second storage area 632, and a third storage area 633. Firmware consisting of a single unit that causes the unit 60 to function is stored in a storage area. Specifically, the storage unit 63 stores firmware in the first storage unit 631 and stores another firmware in the second storage unit 632. By storing a plurality of firmware, for example, when one of the firmware is found to be defective, it is possible to avoid the problem by executing another version of firmware stored in the unit. . Accordingly, the unit 60 can select the firmware to be expanded in the main memory 62 from the first storage area 631 or the second storage area 632 of the storage unit 63. A storage area in which firmware executed by the execution unit 61 of the unit 60 in the main memory 62 is stored as an operation area 634. On the other hand, an area in which firmware that is not expanded by the unit in the main memory is stored as a non-operation area 635. The storage area to be the operation area 634 is switched according to the number for identifying the operation area stored in the third storage unit 633. Therefore, the operation area 634 becomes either the first storage area 631 or the second storage area 632 depending on the number for identifying the operation area. The storage means 63 is, for example, a flash memory.

  For the following description, FIG. 3B shows the configuration of the unit 70 to be exchanged, and FIG. 3A shows the configuration of the unit 80 operating in the disk array device. The unit 70 to be exchanged includes an execution unit 71, a main memory 72, a storage unit 73, and an interface unit 74. The execution unit 71, main memory 72, storage unit 73, and interface unit 74 are connected by a bus 75. The storage means has a first storage area 731, a second storage area 732, and a third storage area 733. Further, the operation area is an operation area 734, and the non-operation area is a non-operation area 735. The unit 80 that operates in the disk array apparatus includes an execution unit 81, a main storage 82, a storage unit 83, and an interface unit 84. The execution unit 81, main memory 82, storage unit 83, and interface unit 84 are connected by a bus 85. The storage means has a first storage area 831, a second storage area 832, and a third storage area 833. Further, the operation area is an operation area 834, and the non-operation area is a non-operation area 835.

  Next, the CM unit will be described. The disk array device 1 has a plurality of CM units. In FIG. 1, CM2 and CM3. Hereinafter, CM2 will be described, but CM3 has the same configuration. FIG. 4 shows a configuration diagram of the CM. The CM 2 includes an execution unit 201, a main storage 202, a storage unit 203, and an interface unit 204. The execution unit 201, main memory 202, storage unit 203, and interface unit 204 are connected by a bus 205. The execution unit 201 of CM2 includes a writing determination unit, a version number determination unit, a firmware version number matching unit in the first storage area, a firmware version number matching unit in the second storage area, an operation area matching unit, and Functions as the next operation area matching unit. The execution unit 201 of the CM2 includes a writing determination program 211, a version number determination program 222, a firmware version number matching program 233 in the first storage area, and a firmware version in the second storage area stored in the storage unit 203 of the CM2. The number coincidence program 244, the operation area coincidence program 255, and the next operation area coincidence program 266 are expanded in the main memory 202 of the CM 2 and executed.

  The write discriminating unit discriminates whether or not the firmware cannot be written in the operation area 734 of the storage unit 73 of the unit 70 to be replaced.

  The version number determination unit determines the version number of the firmware stored in the storage unit 83 of the unit 80 operating in the disk array device 1 and the version number of the firmware stored in the storage unit 73 of the unit 70 to be replaced. To detect. The version number discrimination unit also identifies a number for identifying the operation area 834 of the storage unit 83 of the unit 80 operating in the disk array apparatus 1 and a number for identifying the operation area 734 of the storage unit 73 of the unit 70 to be replaced. Is detected. Also, the version number discriminating unit identifies a number for identifying the next operating area of the storage unit 83 of the unit 80 operating in the disk array apparatus 1 and a number for identifying the next operating area of the storage unit 73 of the unit 70 to be replaced. Is detected.

  The operating area matching unit identifies the identification number of the operating area 834 of the storage unit 83 of the unit 80 operating in the disk array apparatus 1 in the version number determining unit and the identification of the operating area 734 of the storage unit 73 of the unit 70 to be replaced. If the numbers do not match, the identification number corresponding to the operation area 734 of the storage means 73 of the unit 70 to be replaced and the operation area 834 of the storage means 83 of the unit 80 operating in the disk array device 1 are stored. Match the corresponding identification number.

  The firmware version number matching unit in the first storage area is a unit to be exchanged with the version number of the firmware stored in the first storage area 831 of the storage means 83 of the unit 80 operating in the disk array device 1. The version number of the firmware stored in the first storage area 731 of the storage means 73 of 70 is matched.

The firmware version number matching unit in the second storage area is the unit to be replaced with the version number of the firmware stored in the second storage area 832 of the storage means 83 of the unit 80 operating in the disk array device 1. The version number of the firmware stored in the second storage area 732 of the storage means 73 of 70 is matched.
The next operating surface side surface matching unit 26 is exchanged with an identification number corresponding to the operating area 834 of the storage means 83 in which the firmware to be expanded in the main memory 82 is stored after the unit 80 operating in the disk array device 1 is restarted. The identification number corresponding to the operation area 734 of the storage means 73 in which the firmware to be expanded in the main memory 72 is stored after the target unit 70 is restarted is matched.

  The firmware control table 27 is stored in the storage unit 203 of CM2. The firmware control table 27 stores information for managing the firmware stored in the storage means of each unit in the disk array apparatus 1 by the CM 2. Next, the firmware control table 27 will be described.

  FIG. 5 shows the configuration of the firmware control table 27 included in the CM. Note that the firmware control table 27 in FIG. 5 has only the configuration of the portion related to the features of the present invention, and the portion related to conventional firmware control is omitted. The firmware control table stores the state of the unit 80 operating in the disk array device 1, the state of the replacement target unit 70, and the setting values of the processing conditions for the replacement target unit. The firmware control table 27 includes an operation unit area 1 firmware version number 2701, an operation unit area 2 firmware version number 2702, an operation unit operation area identification number 2703, an operation unit next operation area identification number 2704, an exchange unit area 1 firmware version number 2705, The operation unit area 2 has a firmware version number 2706, an exchange unit operation area identification number 2707, and an exchange unit next operation area identification number 2708.

  The operation unit area 1 firmware version number 2701 is information on the version number of the firmware stored in the first storage area 831 of the storage unit 83 of the unit 80 operating in the disk array device 1. The operation unit area 2 firmware version number 2702 is information on the version number of the firmware stored in the second storage area 832 of the storage unit 83 of the unit 80 operating in the disk array device 1. The operation unit operation area identification number 2703 is a number for identifying a storage area corresponding to the operation area 834 of the storage unit 83 of the unit 80 operating in the disk array device 1. The operation unit next operation area identification number 2704 is a number for identifying a storage area to be an operation area after the unit 80 operating in the disk array device 1 is rebooted.

  The replacement unit area 1 firmware version number 2705 is information on the version number of the firmware stored in the first storage area 731 of the storage means 73 of the unit 70 to be replaced. The operation unit area 2 firmware version number 2706 is information on the version number of the firmware stored in the second storage area 732 of the storage unit 73 of the unit 70 to be replaced. The replacement unit operation area identification number 2707 is a number for identifying a storage area corresponding to the operation area 734 of the storage means 73 of the unit 70 to be replaced. The replacement unit next operation area identification number 2708 is a number for identifying a storage area to be an operation area after the unit 70 to be replaced is rebooted.

  This embodiment is operating in the disk array device 1 based on the operation unit area 1 firmware version number 2701, the operation unit area 2 firmware version number 2702, the operation unit operation area identification number 2703, and the operation unit next operation area identification number 2704. The version number of the firmware stored in each storage area of the storage means of all the units, the operation area of the storage means, and the operation area after the unit is rebooted are matched.

  Note that the version number of the firmware stored in each storage area of the storage means of the unit, the operating area of the storage means, and after the unit is rebooted based on the type of unit operating in the disk array device 1 In order to match the operating area, the following configuration is used. An operation unit area 1 firmware version number 2701, an operation unit area 2 firmware version number 2702, an operation unit operation area identification number 2703, and an operation unit operation area identification number 2704 are provided for each type of unit.

  The mode parameter 2709 includes a reboot BIT, an operation area change BIT, and a firmware download BIT. The reboot BIT is a bit for determining whether or not to reboot the unit 70 to be exchanged. The operating area change BIT is a bit for determining whether or not to change the operating area 734 of the storage unit 73 of the unit 70. The firmware download BIT is a bit for determining whether or not to download firmware to the first storage area 731 or the second storage area 732 of the storage unit 73 of the unit 70. The mode parameter 2709 is a flowchart of “checking the version number of the firmware in the case of a unit that can write firmware in the operating area” shown in FIG. 8, and “in the case of a unit that cannot write firmware in the operating area” shown in FIG. Is set by the execution unit 201 of CM2. The set mode parameter 2709 is used by the execution unit 201 of the CM 2 for the determination of the process during the process shown in the flowchart of “Match version of unit firmware” shown in FIG.

  The download destination designation parameter 2710 stores a number for identifying a storage area to which the firmware of the storage unit 73 of the unit 70 to be exchanged is downloaded. The version number specification parameter 2711 stores the version number of the firmware to be downloaded to the storage area of the storage unit 73 of the unit 70 to be replaced. The operating area change designation parameter 2712 is set with a number for identifying a storage area that becomes the operating area 734 after the unit 70 to be replaced is rebooted.

  FIG. 6 is a flowchart of processing when a unit is newly incorporated into the disk array device 1 according to the present invention. The entire disk array device 1 continues to operate while a new unit is incorporated. When a new unit is installed, the CM 2 of the disk array device 1 matches the following three states with the unit operating in the device. The first state is the storage means of the unit 80 that operates the version numbers of the firmware in the first storage area 731 and the second storage area 732 of the storage means 73 of the unit 70 to be exchanged in the disk array device 1. The version numbers of the firmware stored in the first storage area 831 and the second storage area 832 in FIG. Second, the operating area 734 of the storage means 73 of the unit 70 to be replaced is matched with the operating area 834 of the storage means 83 of the unit 80 operating in the disk array device 1. Third, the operation area 734 of the storage means 73 that operates after the unit 70 to be replaced is restarted, and the operation area 834 of the storage means 83 that operates after the unit 80 operating in the disk array device 1 is restarted. To match.

  The execution unit 201 of the CM2 includes a writing determination program 211, a version number determination program 222, a firmware version number matching program 233 in the first storage area, and a firmware version in the second storage area stored in the storage unit 203 of the CM2. The number coincidence program 244, the operation area coincidence program 255, and the next operation area coincidence program 266 are expanded in the main memory 202 of the CM 2 and executed. When the disk array device 1 recognizes the unit 70 to be exchanged, the CM 2 performs a write determination to match the state of the unit 70 to be exchanged with the state of the unit 80 operating in the disk array device 1. Functions as a firmware version number matching unit, a firmware version number matching unit for the first storage area, a firmware version number matching unit for the second storage area, an operation area matching unit, and a next operation area matching unit.

  First, the execution unit 201 of CM2 confirms the unit 70 to be exchanged (S301). Specifically, the execution unit 201 of CM 2 changes the storage area corresponding to the type information of the unit 70 and the operation area 734 of the storage means 73 of the unit 70 from the third storage area of the storage means 73 of the unit 70 to be replaced. A number for identifying, a number for identifying a storage area of the storage means 73 that becomes an active area after the unit 70 reboots, a version number of the firmware stored in the first storage area 731 of the storage means 73 of the unit 70, The firmware version number, the serial number of the unit 70, the OS information of the unit 70, and the file system information of the unit 70 are acquired in the second storage area 732 of the storage unit 73. The CM2 execution unit 201 registers the acquired information in the CM2 firmware control table 27.

  Next, the execution unit 201 of CM 2 can download the firmware from the OS information and the file system information acquired from the replacement target unit 70 to the operation area 734 of the storage unit 73. It is determined whether or not (S302). For example, the determination in S302 is based on information regarding whether or not the CM 2 can directly download firmware to the operating area and OS information, information on whether or not firmware can be directly downloaded to the operating area, and the file system. This is possible by storing information associated with the information in the storage means 203 in advance.

It should be noted that the determination in S302 is performed when it is possible to determine whether or not the unit can download firmware to the operation area 734 of the storage unit 73 of the unit 70 only by the type of the unit 70 to be replaced. It is also possible to use information associating information on the type of the target unit 70 with information on whether or not firmware can be downloaded directly into the operation area. Also, the type and version number of the unit 70 to be replaced If it is possible to determine whether the firmware can be downloaded to the operation area 734 of the storage means 73 of the unit 70 to be replaced by a combination of information and serial number, the unit to be replaced It is also possible to determine by a combination of 70 types, version number information, serial number, etc. .

  The writing determination unit determines whether the firmware can be written to the operation area of the unit 70 to be exchanged from the OS information and the file system information of the unit 70 to be exchanged. Therefore, if the OS information and file system information registered in advance are within the range, the unit specifications change during development of the unit that can be written to the operation area of the storage means, and the unit cannot be written to the operation area of the storage means. Even if this happens, there is no effect on the firmware download control program.

  When the replacement target unit 70 can download the firmware to the operation area 734 of the storage unit 73, the CM2 execution unit 201 performs the “version check of the unit whose firmware can be written to the operation area” process (S303). Run. Details of the processing of S303 are shown in FIG. On the other hand, if the unit 70 to be exchanged cannot download the firmware to the operation area 734 of the storage unit 73, the CM2 execution unit 201 “checks the version number of the unit in which the firmware cannot be written to the operation area”. Processing (S304) is executed. Details of the process of S304 are shown in FIG.

  The CM2 execution unit 201 refers to the CM2 firmware control table 27 when the check of the firmware version of the unit 70 to be replaced is completed in S303 or S304. The CM2 execution unit 201 determines whether the firmware download BIT of the mode parameter 2709 of the firmware control table 27 is ON (S305).

  When the firmware download BIT is ON (S305: Yes), the CM2 execution unit 201 downloads the download destination designation parameter to the storage area of the storage unit 73 of the unit 70 to be exchanged specified by the version number designation parameter 2711. The firmware specified by 2710 is downloaded (S306).

  Next, the CM2 execution unit 201 determines whether the operation area change BIT of the mode parameter 2709 is ON (S307). When the operating area change BIT is ON (S307: Yes), the execution unit 201 sets the storage area corresponding to the identification number that matches the operating area change designation parameter 2712 of the storage means 73 of the unit 70 to be replaced. It changes to 734 (S308). Specifically, the execution unit 201 of CM 2 transmits the setting information to the unit 70 to be exchanged. The execution unit 71 of the unit 70 stores the received setting information in the third storage area 733.

  Next, the CM2 execution unit 201 determines whether the reboot BIT of the mode parameter 2709 is ON (S309). If the reboot BIT is ON (S309: Yes), the execution unit 201 sends a reboot instruction to the unit 70 to be exchanged (S310). If the reboot BIT is OFF (S309: No), the execution unit 201 ends the process. Therefore, when the reboot BIT of the mode parameter 2709 is ON, the execution unit 201 of the CM 2 executes again the processing from S301 to S309 after the unit 70 to be replaced is rebooted. The execution unit 201 of CM2 executes until the reboot BIT of the mode parameter 2709 is not turned ON.

  If the replacement target unit 70 can download the firmware to the operation area 734 of the storage unit 73, the replacement target unit 80 and the replacement target unit 80 in the disk array device 1 can be replaced by a single reboot. The firmware version number stored in each storage area of the storage means and the operation area of the storage means can be matched with the unit 70. If the unit 70 to be exchanged cannot download the firmware to the operation area 734 of the storage unit 73, the unit 80 to be exchanged with the unit 80 that is operating in the disk array device 1 by rebooting up to two times. The firmware version number stored in each storage area of the storage means and the operation area of the storage means can be matched with the unit 70.

  Therefore, when the flowchart of FIG. 6 is executed and the reboot BIT of the mode parameter 2709 is ON even when the maximum number of reboots has been exceeded, the unit 70 to be replaced has the firmware version as expected. There is a possibility that the number and the surface of the storage means cannot be matched with the unit 80 operating in the disk array device 1. Therefore, it is also possible to detect the unit 70 to be exchanged as an abnormality as an abnormality.

  FIG. 7 is a flowchart of processing for checking the version number of the firmware when the firmware cannot be downloaded to the operation area 734 of the storage unit 73 of the unit 70 to be replaced. Each notation of the flowchart of FIG. 7 will be described. “70” indicates a unit attached to the apparatus. “80” indicates a unit operating in the apparatus. An “operation area 734” indicates an area in which firmware for operating a unit attached to the apparatus is stored. The “operation area 834” indicates an area in which firmware that operates a unit that operates in the apparatus is stored. “Operating version number 70” indicates the version number of the firmware stored in the operating area 734. “Operating version number 80” indicates the version number of the firmware stored in the operating area 834. “Non-operating version number 70” indicates the version number of the firmware stored in an area that is not the operating area in the storage area of the unit attached to the apparatus. “Non-operating version number 80” indicates the version number of the firmware stored in the non-operating area of the storage area of the units operating in the apparatus. The “next operation area 70” indicates an area in which firmware that operates after the unit 70 is restarted is stored. “Next operation area 80” indicates an area in which firmware that operates after the unit 80 is restarted is stored.

  The execution unit 201 of CM2 compares the operation unit operation area identification number 2703 registered in the firmware control table 27 with the replacement unit operation area identification number 2707 (S401). If the numbers compared in S401 match, the execution unit executes the process of S407.

  The execution unit 201 of CM2 turns on the reboot BIT of the mode parameter 2709 of the firmware control table 27 (S402). Currently, since the identification number corresponding to the operation area 734 of the unit 70 to be exchanged is different from the identification number corresponding to the operation area 834 of the unit 80 operating in the disk array device 1, the process of rebooting the unit 70 is performed. Because it is necessary.

  Next, the execution unit 201 of CM2 determines whether the operation unit operation area identification number 2703 and the replacement unit next operation area identification number 2708 match (S403). When it is determined in S403 that the numbers to be compared do not match (S403: Yes), the CM2 execution unit 201 sets the operation of the unit 80 operating in the disk array device 1 in the operation area change designation parameter 2712 of the firmware control table 27. An identification number corresponding to the area 834 is set (S404). This is because the identification number corresponding to the operation area 734 of the unit 70 to be replaced is different from the identification number corresponding to the operation area 834 of the unit 80 operating in the disk array device 1. Also, the execution unit 201 of CM2 turns on the operation area change BIT of the mode parameter 2709 (S404). This is to change the storage area corresponding to the operation area 734 of the unit 70 to be exchanged.

  Next, the execution unit 201 of CM 2 stores the version number of the firmware stored in the non-operating area 735 of the storage unit 73 of the unit 70 to be replaced and the operating area 834 of the unit 80 operating in the disk array device 1. It is determined whether or not the version number of the firmware that has been matched matches (S405).

  Specifically, the version number of the firmware in the non-operating area 735 of the unit 70 to be replaced is stored in the storage unit 73 of the unit 70 to be replaced when the replacement unit operating area identification number 2707 is “1”. The version number of the firmware stored in the second storage area 732.

  Also, the firmware version number of the non-operating area 735 of the unit 70 to be replaced is the first version of the storage means 73 of the unit 70 to be replaced when the replacement unit operating area identification number 2707 is “2”. The firmware version stored in the storage area 731 is the firmware version of the non-operating area 735 of the unit 70 to be replaced. When the operation unit operating area identification number 2703 is “1”, the firmware version of the non-operating area 835 of the unit 80 operating in the disk array apparatus 1 is the unit operating in the disk array apparatus 1. This is the version number of the firmware stored in the second storage area 832 of the 80 storage means 83. When the operation unit operating area identification number is “2”, the firmware version number of the non-operating area 835 of the unit 80 operating in the disk array apparatus 1 is the unit 80 operating in the disk array apparatus 1. Is the version number of the firmware stored in the first storage area 831 of the storage means 83.

  If the firmware versions compared in S405 do not match, the CM2 execution unit 201 sets an identification number corresponding to the non-operating area 735 of the unit 70 to be replaced in the download destination designation parameter 2710 of the firmware control table 27. . Further, the execution unit 201 sets the version number of the firmware stored in the identification number corresponding to the operation area 834 of the unit 80 operating in the disk array device 1 in the version number specification parameter 2711. The execution unit 201 downloads the firmware of the mode parameter 2709 in order to download the version firmware stored in the operation area 834 of the unit 80 operating in the disk array device 1 to the non-operation area 735 of the unit 70 to be replaced. BIT is set to ON (S406).

  Next, processing when the determination result of S401 matches the identification number corresponding to the unit 70 operation area 734 to be exchanged with the identification number corresponding to the operation area 834 of the unit 80 operating in the disk array device 1. explain.

  When the operation unit operation area identification number 2703 and the replacement unit operation area identification number 2707 in the firmware control table 27 match (S401: No), the CM2 execution unit 201 is stored in the operation area 734 of the unit 70 to be replaced. The firmware version number and the firmware version number stored in the operation area 834 of the unit 80 operating in the disk array device 1 are compared (S407). If the firmware version numbers of the operation area 734 of the unit 70 and the operation area 834 of the unit 80 match, the unit 70 that is to be replaced and the unit that operates in the disk array device 1 are not rebooted. This is because 80 states can be matched. The state is the version number of the firmware stored in the first storage area 731 and the second storage area 732 of the storage means 73 of the unit 70, the operation area 734 of the storage means 73 of the unit 70, and after the unit 70 is rebooted It is a number that identifies the storage area to be expanded.

  If the version numbers to be compared in S407 do not match (S407: Yes), the CM2 execution unit 201 turns on the reboot BIT of the mode parameter 2709 in the firmware control table 27 (S408). This is because it is necessary to reboot the unit 70 after the subsequent setting. That is, the unit 70 performs reboot processing, and the operating area 734 of the unit 70 before rebooting is set as the non-operating area 735 after rebooting, and the firmware of the operating area 834 of the unit 80 operating in the disk array device 1 is stored in the non-operating area 735 Because it is necessary to write.

  Next, the execution unit 201 of CM 2 sets the identification number that the unit 70 to be replaced becomes the operation area 734 after rebooting, and the identification number corresponding to the operation area 834 of the storage unit 83 of the unit 80 operating in the disk array device 1. It is determined whether or not. The execution unit 201 determines whether the replacement unit next operation area identification number 2708 in the firmware control table 27 matches the operation unit operation area identification number 2703 (S409).

  If the numbers compared in S409 match, the execution unit 201 of CM2 sets the operation area change designation parameter 2712 of the firmware control table 27 to the non-operation area 835 of the storage unit 83 of the unit 80 operating in the disk array device 1. Set the corresponding identification number. The execution unit 201 sets the operation area change BIT of the mode parameter 2709 to ON (S410).

  Next, the execution unit 201 of CM 2 stores the version number of the firmware stored in the non-operating area 735 of the unit 70 to be replaced and the version of the firmware stored in the operating area 834 of the unit 80 operating in the disk array device 1. It is determined whether the numbers match (S411). The execution unit 201 updates the firmware of the non-operating area 735 of the unit 70 to be replaced from the replacement unit area 1 firmware version number 2705 or the replacement unit area 2 firmware version number 2706 corresponding to the identification number that is not the replacement unit operating area identification number 2707. Specify the version number of. Further, the execution unit 201 determines the operation area 834 of the unit 80 operating in the disk array device 1 from the operation unit area 1 firmware version number 2701 or the operation unit area 2 firmware version number 2702 corresponding to the operation unit operation area identification number 2703. Specify the firmware version of.

  If the version numbers to be compared in S411 do not match, the CM2 execution unit 201 sets an identification number corresponding to the non-operating area 735 of the unit 70 to be replaced in the download destination designation parameter 2710 of the firmware control table 27. . The execution unit 201 sets the version number of the firmware stored in the operation area 834 of the unit 80 operating in the disk array device 1 in the version number specification parameter 2711. The execution unit 201 sets the firmware download BIT of the mode parameter 2709 to ON (S412).

  Next, the processing when the version numbers to be compared in S407 match will be described. When the version numbers compared in S407 match (S407: No), the execution unit 201 of CM2 determines the firmware version number of the non-operating area 735 of the unit 70 to be replaced and the unit operating in the disk array device 1. It is determined whether the firmware version numbers in the 80 non-operating area 835 match (S413). If the version numbers compared in S413 match, the execution unit 201 of CM2 executes S415. When the version numbers compared in S413 do not match, the execution unit 201 of CM2 sets an identification number corresponding to the non-operating area 735 of the unit 70 to be replaced in the download destination designation parameter 2710 of the firmware control table 27. . The identification number corresponding to the non-operating area 735 is different from the replacement unit operating area identification number 2707 of the firmware control table 27. The execution unit 201 sets the version number of the firmware stored in the non-operation area 835 of the unit 80 operating in the disk array device 1 in the version number specification parameter 2711 of the firmware control table 27. The execution unit 201 sets the firmware download BIT of the mode parameter 2709 to ON (S414).

  Next, the execution unit 201 identifies the storage area identification number used as the operation area 734 after rebooting the unit 70 to be replaced, and the storage area identification number used as the operation area 834 after the unit 80 operating in the disk array device 1 reboots. Are matched (S415). Specifically, the execution unit 201 determines whether the operation unit next operation area identification number 2704 and the replacement unit next operation area identification number 2708 match. The execution unit 201 ends the process if the numbers to be compared in S415 match. If the numbers to be compared in S415 do not match, the execution unit 201 sets the operation unit next operation area identification number in the operation area change designation parameter 2712 of the firmware control table 27. Further, the execution unit 201 sets the operation area change BIT of the mode parameter 2709 to ON (S416). FIG. 8 is a flowchart of processing for checking the version number of firmware when the unit can download firmware to the operation area of the storage unit of the unit. Each notation of the flowchart of FIG. 8 will be described. “70” indicates a unit attached to the apparatus. “80” indicates a unit operating in the apparatus. An “operation area 734” indicates an area in which firmware for operating a unit attached to the apparatus is stored. The “operation area 834” indicates an area in which firmware that operates a unit that operates in the apparatus is stored. “Operating version number 70” indicates the version number of the firmware stored in the operating area 734. “Operating version number 80” indicates the version number of the firmware stored in the operating area 834. “Non-operating version number 70” indicates the version number of the firmware stored in an area that is not the operating area in the storage area of the unit attached to the apparatus. “Non-operating version number 80” indicates the version number of the firmware stored in the non-operating area of the storage area of the units operating in the apparatus. The “next operation area 70” indicates an area in which firmware that operates after the unit 70 is restarted is stored. “Next operation area 80” indicates an area in which firmware that operates after the unit 80 is restarted is stored.

  The execution unit 201 of CM 2 compares the identification number corresponding to the operation area 734 of the unit 70 to be replaced with the identification number corresponding to the operation area 834 of the unit 80 operating in the disk array device 1 (S501). When the numbers compared in S501 match, the execution unit 201 executes the process of S507.

  On the other hand, when the numbers compared in S501 do not match, the execution unit 201 executes the processing after S502. First, the execution unit 201 sets the reboot BIT of the mode parameter 2709 in the firmware control table 27 to ON (S502). Next, the execution unit 201 determines whether the replacement unit next working area identification number 2708 and the working unit working area identification number 2703 match (S503). If the numbers compared in S503 match, the execution unit executes the process of S505. On the other hand, when the numbers compared in S503 do not match, the execution unit 201 sets the operation unit operation area identification number 2703 in the operation area change designation parameter 2712 of the firmware control table 27. The execution unit sets the operation area change BIT of the mode parameter 2709 to ON (S504).

  Next, the execution unit 201 of CM 2 stores the version number of the firmware stored in the non-operating area 735 of the unit 70 to be exchanged and the firmware stored in the operating area 834 of the unit 80 operating in the disk array device 1. It is determined whether the version number matches (S505). The execution unit 201 extracts the firmware version number of the non-operation area 735 corresponding to the identification number that is not the replacement unit operation area identification number 2707 from the replacement unit area 1 firmware version number 2705 or the replacement unit area 2 firmware version number 2706. Further, the execution unit 201 sets the firmware version of the operation area 834 of the unit 80 operating in the disk array device 1 corresponding to the operation unit operation area identification number 2703 as the operation unit area 1 firmware version number 2701 or the operation unit area 2 firmware. Extracted from the version number 2702.

  The execution unit 201 of CM2 ends the process if the version numbers compared in S505 match. On the other hand, if the version numbers compared in S505 do not match, the execution unit 201 sets an identification number corresponding to the non-operating area 735 of the unit 70 to be replaced in the download destination designation parameter 2710 of the firmware control table 27. Further, the execution unit 201 sets the version number of the firmware in the operation area 734 corresponding to the operation unit operation area identification number 2703 in the version number specification parameter 2711. Also, the execution unit 201 sets the firmware download BIT of the mode parameter 2709 to ON (S506). Thereafter, the process ends.

  As a result of the determination in S501, the execution unit 201 matches the identification number corresponding to the operation area 734 of the unit 70 to be exchanged with the identification number corresponding to the operation area 834 of the unit 80 operating in the disk array device 1. The execution unit 201 determines the version number of the firmware stored in the operation area 734 of the unit 70 to be replaced and the version number of the firmware stored in the operation area 834 of the unit 80 operating in the disk array device 1. Determination is made (S507).

  The execution unit 201 performs the processing of S511 when the version numbers compared in S507 match. On the other hand, if the version numbers compared in S507 do not match, the execution unit 201 sets an identification number corresponding to the operation area 734 of the unit 70 to be replaced in the download destination designation parameter 2710 of the firmware control table 27. The execution unit 201 also operates the operation area of the unit 80 operating in the disk array device 1 identified from the operation unit operation area identification number 2703, the operation unit area 1 firmware version number 2701, and the operation unit area 2 firmware version number 2702. The firmware version stored in 834 is set in the version designation parameter 2711. Furthermore, the execution unit 201 sets the firmware download BIT and reboot BIT of the mode parameter 2709 to ON (S508).

  Next, the execution unit 201 determines whether the replacement unit next operation area identification number 2708 matches the identification number corresponding to the operation area 834 of the unit 80 operating in the disk array device 1 (S509).

  The execution unit 201 ends the process if the numbers compared in S509 match. On the other hand, if the numbers compared in S509 do not match, the execution unit 201 sets the operation unit operation area identification number 2703 in the operation area change designation parameter 2712 of the firmware control table 27. The execution unit 201 sets the operation area change BIT of the mode parameter 2709 to ON (S510). Thereafter, the process ends.

  Next, as a result of the determination in S507, the version number of the firmware stored in the operation area 734 of the unit 70 to be exchanged and the version number of the firmware stored in the operation area 834 of the unit 80 operating in the disk array device 1 The case where and match will be described.

  The execution unit 201 of CM 2 stores the version number of the firmware stored in the non-operating area 735 of the unit 70 to be exchanged and the version number of the firmware stored in the non-operating area 835 of the unit 80 operating in the disk array device 1. Is matched (S511). The execution unit 201 performs the processing of S513 if the version numbers compared in S511 match. When the version numbers compared in S511 do not match, the execution unit 201 sets an identification number corresponding to the non-operating area 735 of the unit 70 to be replaced in the download destination designation parameter 2710 of the firmware control table 27. The execution unit 201 sets the version number of the firmware stored in the non-operating area 835 of the unit 80 operating in the disk array device 1 in the version number designation parameter 2711. The execution unit 201 sets the firmware download BIT of the mode parameter 2709 to ON (S512). Next, the execution unit 201 determines whether the replacement unit next operation area identification number 2708 matches the operation unit next operation area identification number 2704 (S513). The execution unit 201 ends the process if the numbers compared in S513 match. On the other hand, if the numbers compared in S513 do not match, the execution unit 201 sets the operation unit next operation area identification number 2704 in the operation area change designation parameter 2712 of the firmware control table 27. Further, the execution unit 201 sets the operation area change BIT of the mode parameter 2709 to ON (S514). Thereafter, the process ends.

  With the above processing, in the operation of replacing the unit in which the disk array device 1 is operating, the unit that can download the firmware to the operating area and the unit that cannot download the firmware to the operating area Even when the disk array device 1 is mixed, the version numbers of firmware stored in the storage areas of the unit 70 to be replaced and the unit 80 operating in the disk array device 1 can be made to coincide. In addition, the identification numbers corresponding to the operation areas 834 of the storage means 83 of the units 80 operating in the disk array device 1 match, and the storage areas that the replacement target unit 70 uses as the operation areas 734 after rebooting also match. In general, a unit stores a new version of firmware in an operating area and an old version of firmware in a non-operating area. Therefore, for example, when a failure occurs, the firmware version of the entire disk array device 1 can be easily switched.

  In the present embodiment, the configuration is not such that a plurality of units in the disk array device 1 are simultaneously replaced. In order to be able to exchange a plurality of units simultaneously, the following configuration is adopted. Operation unit area 1 firmware version number 2701, operation unit area 2 firmware version number 2702, operation unit operation area identification number 2703, operation unit next operation area identification number 2704, replacement unit area 1 firmware version number 2705, replacement of the firmware control table 27 Unit area 2 firmware version number 2706, replacement unit operation area identification number 2707, replacement unit next operation area identification number 2708, mode parameter 2709, download destination designation parameter 2710, version number designation parameter 2711, and operation area change designation parameter 2712 Prepare information specific to each unit. When the execution unit 201 of CM2 refers to the firmware control table 27, it refers to the part of the unique information acquired from the unit 70 to be exchanged that is the current processing target. With the above configuration, a plurality of units can be exchanged at the same time.

  The storage means of the unit of the present invention has an area for storing a plurality of firmware. When there is a writable unit in the operating area of the unit storage means and a non-writable unit in the operating area of the unit storage means, and the firmware version number of the unit in operation in the disk array device is replaced. If the firmware version number of the target unit does not match, the CM writes the firmware having the same firmware version number of the unit operating in the disk array device in the non-operating side area of the storage means. Thereafter, the CM switches the operating side area and the non-operating side area of the unit to be replaced, and the firmware stored in the non-operating side is used as the firmware of the operating side area. A method of matching the version number of the firmware stored in the firmware and the version number of the firmware stored in the operation area of the unit to be replaced can be considered. However, the conventional technology does not consider the alignment of the identification numbers of the operation areas of the storage means. A disk array device may be equipped with 100 or more units. When developing a disk array device, download the firmware to all units of the disk array device, and after rebooting the disk array device, determine whether the unit has really started up before storing the unit. It is necessary to determine in which area of the means the processing was executed by comparing each unit. It is unclear in which area of the storage means the process was executed before the unit was restarted. When comparing in which area of the storage means the process is actually executed, a great deal of labor is required. Since the present invention has a configuration in which operation areas are aligned, debugging work efficiency is improved.

  Also, in the prior art, when the unit is restarted after downloading the firmware to the storage means of the unit to be replaced, the disk array device may not operate when the unit executes a process according to the downloaded firmware. For example, in the case of firmware at the time of development of a disk array device, even the unit firmware may have a problem that the entire disk array device does not start. Accordingly, in order to restore the disk array device, an operation of returning the operation area of the storage means of each unit to the state before the device reboot occurs, which requires a great deal of labor. In the present invention, the area of the storage means that operates after the restart is also made to coincide. Therefore, even after the device is restarted, it is easy to return each unit to the state before the restart.

Also, if a problem occurs while the disk array device is in operation, it is necessary to investigate the cause of the problem. In order to reproduce the situation in which a failure has occurred in the disk array device, it is necessary to match the state of the disk array device when the failure has occurred. Therefore, it is necessary to match the operation area of the storage means of each unit of the disk array apparatus. It takes a lot of labor and time for humans to analyze the situation in which a failure occurs in a disk array device. According to the present invention, the version number of each firmware stored in the operation area, the firmware to be operated, and the firmware to be executed after restart can be matched. In addition, the operation area of each unit also operates in agreement. Therefore, it is possible to reduce the number of operations for reproducing the state at the time of debugging.
(Appendix 1)
A method of controlling a disk array device using a plurality of units storing a plurality of firmware, wherein the plurality of firmware versions of a plurality of units executing the same function of the disk array device are unified, and the plurality of units A method for controlling a disk array device, characterized in that the firmware executed in the above is unified.
(Appendix 2)
Information on the version numbers of a plurality of firmware of a plurality of units that execute the same function of the disk array device is acquired, and when the information on the version numbers of the acquired firmware is different, the plurality of units have the same version number. Transmitting firmware, obtaining information of firmware executed by a plurality of units that execute the same function of the disk array device, and information for executing the same firmware when the information of the firmware to be executed is different; The method of controlling a disk array device according to appendix 1, wherein the disk array device is transmitted to a unit.
(Appendix 3)
The disk array device control method according to appendix 1, wherein the plurality of units have storage means, and the areas for storing the plurality of firmware in the storage means of the plurality of units are unified.
(Appendix 4)
When the disk array device newly recognizes a unit, the version numbers of a plurality of firmware between units that perform the same function as the newly recognized unit of the disk array device are unified, and the newly recognized unit is recognized. 2. The disk array apparatus control method according to appendix 1, wherein the firmware executed in the unit and the firmware executed between the units executing the same function are unified.
(Appendix 5)
When the disk array device newly recognizes a unit, it unifies the version numbers of a plurality of firmware of a plurality of units that execute the same function of the disk array device, and the firmware executed by the newly recognized unit is changed to the disk 5. The disk array device control method according to appendix 4, wherein the firmware is executed by a plurality of units that execute the same function of the array device.
(Appendix 6)
In the case where the newly recognized unit is a unit that cannot be downloaded to the storage area in which the firmware being executed is stored, the storage area of the newly recognized unit storage area in which the firmware that is not in execution is stored and the disk array device The firmware of the version executed by the unit executing the same function is unified with the firmware of the version executed by the unit executing the same function, and the newly recognized unit is executed by the firmware of the version executed by the unit executing the same function of the disk array device after the change After the restart, the storage area of the newly recognized unit storage area is unified with the firmware version memory executed by the unit executing the same function of the disk array device. The method for controlling a disk array device according to appendix 1, wherein:
(Appendix 7)
2. The disk array device control method according to appendix 1, wherein firmware executed when a plurality of units executing the same function of the disk array device are restarted is unified.
(Appendix 8)
A disk array device using a plurality of units storing a plurality of firmware, and a unit for unifying the version numbers of a plurality of firmware of a plurality of units that execute the same function of the disk array device; And a second unifying unit for unifying firmware to be executed.
(Appendix 9)
A control program for a computer of a disk array device that uses a plurality of units that store a plurality of firmware, wherein the computer unifies the version numbers of the firmware of the units that perform the same function of the disk array device And a disk array apparatus control program that functions as a second unit for unifying firmware executed by the plurality of units.

Overall configuration diagram of the embodiment Unit configuration diagram Configuration diagram of unit 70 to be exchanged and unit 80 operating in the disk array device CM2 configuration diagram Configuration diagram of firmware control table 27 Active maintenance firmware version match processing flowchart Flow chart for version check for maintenance units that cannot write firmware to the operating side Flow chart for checking the version number of maintenance units that can write firmware to the operating side

1 Disk array device 2, 3 CM
41, 42 SVC
43, 44 CA
47, 48 DE
45, 46 PBC
49, 50 PSU
51, 52 BU
53, 54 RT
60 Unit 61 Execution unit 62 Main memory 63 Storage unit 631 First storage area 632 Second storage area 633 Third storage area 634 Operation area 635 Non-operation area 64 Interface section 65 Bus 70 Unit 71 Execution section 72 Main storage 73 Storage means 731 First storage area 732 Second storage area 733 Third storage area 734 Operation area 735 Non-operation area 74 Interface section 75 Bus 80 Unit 81 Execution section 82 Main storage 83 Storage means 831 First storage area 832 Second storage area 833 Third storage area 834 Active area 835 Non-active area 84 Interface unit 85 Bus 90, 91 System disk 92, 93 Firmware file 201 Execution unit 202 Main memory 203 Storage means 204 Interface unit 205 Bus 211 Write Discriminator Gram 222 Version identification program 233 Firmware version matching program 244 in the first storage area Firmware version matching program 255 in the second storage area 255 Operation area matching program 266 Next operation area matching program 27 Firmware control table 2701 Operation unit Area 1 firmware version number 2702 Operation unit area 2 firmware version number 2703 Operation unit operation area identification number 2704 Operation unit next operation area identification number 2705 Replacement unit area 1 firmware version number 2706 Replacement unit area 2 firmware version number 2707 Replacement unit operation area identification Number 2708 Replacement unit next operation area identification number 2709 Mode parameter 2710 Download destination specification parameter 2711 Version number specification parameter 2712 Operation area change specification Parameter

Claims (2)

The disk array device includes a first unit, a second unit that operates in a redundant configuration with the first unit, a control unit that performs firmware update control, and a storage unit that stores firmware of each version. And
The first unit and the second unit are respectively a first storage area, a second storage area,
The first storage area is the firmware version stored in the first storage area, the firmware version stored in the second storage area, and the operating area for storing the firmware for operating the first unit and the second unit. And a third storage area for storing an identification number indicating whether the second storage area, and the operating area of the first unit is not writable,
The controller is
If the first unit is replaced due to a failure,
When the identification number of each operation area of the first unit to be exchanged and the second unit is the same and indicates the first storage area, it is stored in the first storage area that is the operation area of the first unit. Compare the firmware version number of the firmware and the firmware version stored in the first storage area, which is the operating area of the second unit. Compare the firmware version stored in the second storage area with no operating area specified and the firmware version stored in the first storage area, which is the operating area of the second unit. For the first unit to be exchanged, the firmware corresponding to the firmware version number of the operating area of the second unit is obtained from the storage unit, and the second storage of the first unit with no operating area specified The first unit is reactivated from the first storage area and the first storage area is rewritten from the first storage area to the second storage area. Since the identification number of the operation area of the unit and the second unit is different, the firmware corresponding to the firmware version number of the operation area of the second unit is obtained from the storage unit, and the first storage area with no operation area specified And the first unit operation area identification number is rewritten from the second storage area to the first storage area, and then the first unit is restarted. The firmware of each second storage area where the operation area identification number of the first unit and the second unit are not specified because the identification number of the operation area of the two units and the firmware version of the operation area are the same When the numbers are different, the firmware corresponding to the firmware version number stored in the second storage area of the second unit is obtained from the storage unit and stored in the second storage area of the first unit. A disk array device characterized by that.   Compare the version number of the firmware stored in the first storage area that is the operation area of the first unit to be replaced with the version number of the firmware stored in the first storage area that is the operation area of the second unit, If the firmware version of the operating area is different, and the firmware version stored in the second storage area is not specified as the operating area of the first unit and the operating area of the second unit Compared with the firmware version stored in the storage area, if the firmware version is the same, the firmware corresponding to the firmware version of the second unit operation area is stored in the second storage area of the first unit without the operation area designation. The disk unit is characterized in that the first unit is restarted after rewriting the identification number of the operating area of the first unit from the first storage area to the second storage area. B devices.

Images