FI127566B - Rack having multiple rack management modules and firmware updating method for the same - Google Patents

Rack having multiple rack management modules and firmware updating method for the same Download PDF

Info

Publication number
FI127566B
FI127566B FI20155207A FI20155207A FI127566B FI 127566 B FI127566 B FI 127566B FI 20155207 A FI20155207 A FI 20155207A FI 20155207 A FI20155207 A FI 20155207A FI 127566 B FI127566 B FI 127566B
Authority
FI
Finland
Prior art keywords
rmc
firmware
switch
memory
rack
Prior art date
Application number
FI20155207A
Other languages
Finnish (fi)
Swedish (sv)
Other versions
FI20155207A (en
Inventor
Yen-Yu Chen
Shih-Chieh Hsu
Original Assignee
Aic Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Aic Inc filed Critical Aic Inc
Publication of FI20155207A publication Critical patent/FI20155207A/en
Application granted granted Critical
Publication of FI127566B publication Critical patent/FI127566B/en

Links

Classifications

    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/20—Modifications to facilitate cooling, ventilating, or heating
    • H05K7/20709—Modifications to facilitate cooling, ventilating, or heating for server racks or cabinets; for data centers, e.g. 19-inch computer racks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16—Constructional details or arrangements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Computer Hardware Design (AREA)
  • Thermal Sciences (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Stored Programmes (AREA)

Abstract

A rack having multiple rack management modules is disclosed. Each rack management module respectively comprises a Rack Management Controller (RMC), a switch and a memory, wherein the switch of each rack management module is interconnected, a firmware is saved on each memory respectively. When the RMC receives a firmware update image and an updating command uploaded externally, the RMC sends a switching instruction to the switch for enabling the switch to switch and connect to the memory of another rack management module. When the RMC executes a firmware updating procedure, the firmware in the memory of another rack management module is updated via switch connection. The present invention can effectively avoid the issue that the RMC is not able to boot normally after the firmware updating fails leading to that the rack is not able to re-update the firmware.

Description

(54) Keksinnön nimitys - Uppfinningens benämning
USEILLA TELINEHALLINTAMODUULEILLA VARUSTETTU TELINE JA LAITEOHJELMISTON PÄIVITYSMENETELMÄ SITÄ VARTEN
Rack med ett flertal rackhanteringsmoduler samt förfarande för uppdatering av fasta program därför
RACK HAVING MULTIPLE RACK MANAGEMENT MODULES AND FIRMWARE UPDATING METHOD FOR THE SAME (56) Viitejulkaisut - Anförda publikationer
US 2007174601 A1, WO 2014161986 A1, US 2005071837 A1, US 2005257213 A1 (57) Tiivistelmä - Sammandrag
A rack having multiple rack management modules is disclosed. Each rack management module respectively comprises a Rack Management Controller (RMC), a switch and a memory, wherein the switch of each rack management module is interconnected, a firmware is saved on each memory respectively. When the RMC receives a firmware update image and an updating command uploaded externally, the RMC sends a switching instruction to the switch for enabling the switch to switch and connect to the memory of another rack management module. When the RMC executes a firmware updating procedure, the firmware in the memory of another rack management module is updated via switch connection. The present invention can effectively avoid the issue that the RMC is not able to boot normally after the firmware updating fails leading to that the rack is not able to re-update the firmware.
Keksinnön kohteena on teline, jossa on useita telineen hallintamoduuleita. Kussakin telineen hallintamoduulissa on telineen hallintaohjain (RMC), kytkin ja muisti, jossa kunkin telineen hallintamoduulin kytkimet on yhdistetty toisiinsa ja kuhunkin muistiin on tallennettu laiteohjelmisto. Kun RMC vastaanottaa laiteohjelmiston päivitysnäköistiedoston ja ulkoisesti ladatun päivityskäskyn, RMC lähettää kytkimelle kytkentäkäskyn, jotta kytkin voi kytkeä ja muodostaa yhteyden toisen telineen hallintamoduulin muistiin. Kun RMC suorittaa laiteohjelmiston päivitysmenettelyn, toisen telineen hallintamoduulin muistissa oleva laiteohjelmisto päivitetään kytkinyhteyden välityksellä. Keksinnön ansiosta voidaan tehokkaasti välttää tilanne, jossa RMC ei pysty käynnistymään normaalisti laiteohjelmiston päivityksen epäonnistumisen jälkeen, minkä seurauksena teline ei pysty päivittämään laiteohjelmistoa uudelleen.
2
Figure FI127566B_D0001
20155207 prh 14-08- 2018
RACK HAVING MULTIPLE RACK MANAGEMENT MODULES AND FIRMWARE
UPDATING METHOD FOR THE SAME
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to a rack, in particularly to a rack according to the preamble of claim 1.
2. Description of Prior Art
Traditionally, a server rack receives a plurality of servers and a Rack Management Controller (RMC). The rack administrators collect server information and control the servers via connecting the RMC to the servers.
The RMC is a kind of System on Chip (SoC) with memories, and is booted via firmware. As a result, similar to Central Processing Units (CPUs) of the servers, the rack administrators have to perform updates on firmware of the RMC from time to time.
Generally, the RMC receives firmware update images, and performs an update automatically on the firmware. Yet if the updating procedure is accidentally interrupted during execution (for example the servers crashed or the rack power is off), or the incorrect firmware is used in the updating procedure, after the RMC restarted, the RMC may not be able to boot normally. In the prior art, each rack is equipped with one
RMC, accordingly if the RMC fails to boot normally, then all servers in the rack fail to function normally which is not desirable to server users.
Further, since the RMC cannot boot normally after firmware update fails, the rack is not able to re-update the firmware without external support (for example update manually by the rack administrators) for resolving the issue.
Document US2007174601A1 presents an apparatus for updating firmware to a plurality of memory devices. The primary controller copies the firmware image to
20155207 prh 14-08- 2018 another memory device residing in a secondary controller.
Documents WO2014/161986A1 and US2005257213A1 present a system improving redundant process control in a data processing apparatus.
In view of this, it is an object to people who skills in the art to provide solutions where the RMC is able to re-update the firmware without external support after the firmware update fails and assures that the RMC is able to boot normally.
SUMMARY OF THE INVENTION
The primary objective of the present invention is to provide a rack having multiple rack management modules and a firmware updating method for the same. The rack 10 enables the rack management module to perform update on firmware of other rack management modules in order to avoid the issue that the rack management module is not able to boot normally after the firmware update fails, and further the rack is not able to re-update the firmware.
The other objective of the present invention is to provide a rack having multiple 15 rack management modules and a firmware updating method for the same, where the multiple rack modules perform heartbeat detection with each other, and provide backup solutions when other rack management modules is detected operating abnormally.
In order to achieve the above goals, the rack disclosed in the present invention 20 has the features of claim 1. In the multiple rack management modules, each rack management module respectively comprises a rack management controller (RMC), a switch and a memory, wherein the switch of each rack management module is interconnected and respectively firmware is saved in each memory. When the RMC receives external uploaded firmware update images, the RMC sends a switching instruction to the switch for enabling the switch to switch and connect to the memory of another rack management module. When the RMC executes a firmware updating
20155207 prh 14-08- 2018 procedure, the RMC perform an update on the firmware in the memory of another rack management module via switch connection.
Comparing with related art, the RMC of the present invention does not perform update on the firmware of the same rack management module. Accordingly, even if the firmware updating procedure is accidentally interrupted leading to update failure, the RMC is able to boot normally after being reset regardless of the firmware update failure. Accordingly, even if the firmware updating procedure of the firmware fails, the RMC still is able to perform update on the firmware again until an update succeeds. Thus, the risk that the administrators are required to manually fix the RMC which is not able to boot normally due to firmware update failure is lowered.
In addition, according to the present invention, multiple management modules are provided in one rack and each rack management module is interconnected and performs heartbeat detection of each other. Thus, when abnormal operation of one of the rack management modules is detected, other rack management modules can be used to provide backup operation solutions. Accordingly, the issue that the whole rack is not able to function normally after the rack management modules have errors is excluded.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a schematic view of a rack in the first embodiment according to the present invention;
Fig. 2 is a connection schematic view of a rack in the first embodiment according to the present invention;
Fig. 3 is a schematic view of a firmware update operation in the first embodiment according to the present invention;
Fig. 4 is a schematic view of a firmware update operation in the second embodiment according to the present invention;
20155207 prh 14-08- 2018
Fig. 5 is a flow chart for obtaining an updated image in the first embodiment according to the present invention;
Fig. 6 is a flow chart for firmware update in the first embodiment according to the present invention; and
Fig. 7 is a backup flowchart in the first embodiment according to the present invention.
DETAILED DESCRIPTION OF THE INVENTION
In cooperation with the attached drawings, the technical contents and detailed description of the present invention are described thereinafter according to a 10 preferable embodiment, being not used to limit its executing scope. Any equivalent variation and modification made according to appended claims is all covered by the claims claimed by the present invention.
Fig. 1 is a schematic view of a rack in the first embodiment according to the present invention. In Fig. 1, the rack 1 has multiple receiving slots for receiving 15 multiple nodes 4. The rack 1 also has multiple rack management modules, respectively and electrically connected with the nodes 4 used for collecting the information of the nodes 4, and control the nodes 4. In the embodiment, a first rack management module 2 and a second rack management module 3 are used for illustrating the multiple rack management modules and the quantity is not limited thereto.
In the present invention, each rack management module has a rack management controller (RMC), a switch and a memory. The RMC connects with the memory via the switch, and a firmware is saved in the memory and used by the RMC for booting.
Fig. 2 is a connection schematic view of a rack in the first embodiment according 25 to the present invention. As shown in Fig. 2, the above first rack management module 2 has a first RMC 21, a first switch 22 and a first memory 23. The first RMC21
20155207 prh 14-08- 2018 connects to the first switch 22, and connects to the first memory 23 via the first switch
22. A first firmware 231 is saved in the first memory 23 and is used by the first RMC 21
In addition, the second rack management module 3 has a second RMC 31, a second switch 32 and a second memory 33. The second RMC 31 connects to the second switch 32, and connects to the second memory 33 via the second switch 32. A second firmware 331 is saved in the second memory 33 and is used by the second RMC 31. In the embodiment, the first memory 23 and the second memory 33 is implemented as a Read Only Memory (ROM) and is not limited thereto.
As shown in Fig. 2, the first switch 22 connects to the first memory 23 via a first access channel L1, the second switch 32 connects to the second memory 33 via a second access channel L2. When the first RMC 21 boots, the first RMC 21 retrieves the first memory 23 via the first access channel L1 with the connection to the first switch 22 and executes the first firmware 231 for finishing the booting procedure. Similarly, when the second RMC 31 performs a boot, the second RMC 31 retrieves the second memory 33 via the second access channel L2 with the connection to the second switch 32, and executes the second firmware 331 for finishing the booting procedure.
In the present invention, the switches of the multiple rack management modules are interconnected. In the embodiment shown in Fig. 2, the first switch 22 and the second switch 32 are interconnected. Further in details, in the embodiment, the first switch 22 and the second switch 32 are connected via a third access channel L3.
The main technical characteristic of the present invention is that when the first RMC 21 executes a firmware updating procedure, the first RMC 21 performs an update on the second firmware 331 in the the second memory 33. When the second 25 RMC 31 executes the firmware updating procedure, the second RMC 31 performs an update on the first firmware 231 in the first memory 23. Accordingly, the first RMC 21
20155207 prh 14-08- 2018 is able to boot normally after being reset because of the update on the first firmware
231 performed by itself fails. Similarly, the second RMC 31 is able to boot normally after being reset because of the update on the second firmware 331 performed by itself fails.
Further in details, the first RMC 21 also connects to the first switch 22 via a first instruction transmission interface 11; the second RMC 31 also connects to the second switch 32 via a second instruction transmission interface I2. When the first RMC 21 executes the updating procedure, the first RMC 21 transmits a switching instruction to the first switch 22 via the first instruction transmission interface 11. The first switch 22 performs switching according to the switching instruction in order to connect to the second switch 32 via the third access channel L3, and connects to the second memory 33 via the second access channel L2. As a result, the first RMC 21 retrieves the second memory 33 respectively via the first switch 22, the third access channel L3, the second switch 32 and the second access channel L2, so as to perform the updating procedure on the second firmware 331.
Similarly, when the second RMC 31 executes the updating procedure, the second
RMC 31 sends a switching instruction to the second switch 32 via the second instruction transmission interface I2. The second switch 32 performs switching according to the switching instruction in order to connect to the first switch 22 via the third access channel L3, and then connects to the first memory 23 via the first access channel L1. As a result, the second RMC31 retrieves the first memory23 respectively via the second switch 32, the third access channel L3, the first switch 22 and the first access channel L1, so as to perform the updating procedure on the first firmware 231. It should be noted that, the RMCs of the multiple rack management modules are interconnected according to the present invention. In Fig. 2, the first RMC 21 and the second RMC 31 of the embodiment are interconnected. Further in details, the first
20155207 prh 14-08- 2018
RMC 21 and the second RMC 31 are connected via a communicating interface IO. In the embodiment, the communicating interface IO is a General Purpose I/O (GPIO) interface, a Universal Asynchronous Receiver/Transmitter (UART) interface, an
Inter-Integrated Circuit (l2C) interface, an Intelligent Platform Management Bus (IPMB) interface, a Local Area Network (LAN) interface etc., and is not limited thereto.
In the present invention, the first RMC 21 and the second RMC 31 perform heartbeat detection with each other via the communicating interface IO, and provide a backup operation solution. In details, each RMC 21,31 detects abnormal heartbeat of another RMC via the communicating interface IO, the RMC is able to enforce the reset 10 of the another RMC via sending an instruction through the communicating interface 10 if an abnormal heartbeat of the another RMC is detected, and assign itself as an active RMC in the rack 1. As a result, when one of the RMCs in the rack 1 operates abnormally, another RMC is able to perform backup operation. After the abnormal RMC is reset, then the operation is recovered to the original. The above technical 15 solution can effectively avoid the issue that the multiple nodes in the rack are not able to operate normally when the only one RMC disposed in a rack has errors.
Fig. 3 is a schematic view of a firmware update operation in the first embodiment according to the present invention. Fig. 3 is used for illustrating the operation flow of the first rack management module 2.
When the first RMC 21 boots, the first RMC 21 retrieves the first firmware 231 in the first memory 23 via the first switch 22 and the first access channel L1, and executes the first firmware 231 to finish the booting procedure.
When the first RMC 21 receives a firmware update image F1 and a updating command transmitted externally, the first RMC 21 sends a first switching instruction 25 C1 to the first switch 22 via the first instruction transmission interface 11, the first switch 22 switches and connects to the second switch 32 of the second rack
20155207 prh 14-08- 2018 management module 3 according to the first switching instruction C1. Thus, the first
RMC21 retrieves the second memory33 via the first switch 22, the third access channel L3, the second switch 32 and the second access channel L2, and the first
RMC21 performs an update on the second firmware 331.
After the update is finished, the first RMC 21 is reset, and the first switch 22 is recovered to the initial settings (i.e., connect to the first memory 23 via the first access channel L1). Thus, after the first RMC 21 is reset, the booting procedure is still finished by executing the first firmware 231 in the first memory 23. In other words, even if the updating procedure execution fails last time, the booting operation of the 10 first RMC 21 is not affected because the failed updating procedure is performed on the second firmware 331.
It should be noted that, the first RMC 21 is installed with a first storage unit 211 for temporarily saving the externally transmitted firmware update image F1. When the first RMC 21 performs the updating procedure on the second firmware 331, the 15 firmware update image F1 temporarily saved in the first storage unit 211 is recorded to the second memory33 in order to finish the updating procedure. In the embodiment, the first storage unit 211 is a Random Access Memory (RAM) or a Flash Memory etc., and is not limited thereto.
Fig. 4 is a schematic view of a firmware update operation in the second 20 embodiment according to the present invention. Fig. 4 is used for illustrating the operation flow of the second rack management module 3.
When the second RMC 31 boots, the second RMC 31 retrieves the second firmware 331 in the second memory 33 via the second switch 32 and the second access channel L2 and the booting procedure is finished by executing the second firmware 331.
When the second RMC 31 receives the firmware update image F1 and the
20155207 prh 14-08- 2018 updating command, the second RMC 31 sends a second switching instruction C2 to the second switch 32 via the second instruction transmission interface I2, the second switch 32 switches and connects to the first switch 22 of the first rack management module 2 according to the second switching instruction C2. Thus, the second RMC 31 retrieves the first memory 23 via the second switch 32, the third access channel L3, the first switch 22 and the first access channel L1, and performs the updating procedure on the first firmware 231.
Similarly, after the updating procedure execution finishes, the second RMC 31 is reset, and the second switch 32 is recovered to the initial settings (i.e., connect to the 10 second memory 33 via the second access channel L2). Thus, after the second RMC 31 is reset, the booting procedure is still finished by executing the second firmware 331 in the second memory33. Similarly, even if the updating procedure execution fails last time, the booting operation of the second RMC 31 is not affected because the failed updating procedure is performed on the first firmware 231 15 Similar to the above mentioned first storage unit 211, a second storage unit 311 is installed in the second RMC 31 for temporarily saving the firmware update image F1. When the second RMC 31 performs the updating procedure on the first firmware 231, the firmware update image F1 temporarily saved in the second storage unit 311 is recorded to the first memory 23 in order to finish the updating procedure. In embodiment, the second storage unit 311 is a RAM or a Flash Memory, and is not limited thereto.
As mentioned above, after the first RMC 21 performs the update on the second firmware 331, the first RMC 21 still boots via the first firmware 231 which is not updated; and after the second RMC 31 performs an update on the first firmware 231, 25 the second RMC 31 still boots via the second firmware 331 which is not updated.
Accordingly, in a preferred embodiment, the multiple rack management modules of
20155207 prh 14-08- 2018 the rack 1 simultaneously receives the externally transmitted firmware update image
F1 and the updating command for respectively updating the firmware of the multiple rack management modules which assures that the firmware version is consistent.
Nonetheless, the above is one of the preferred embodiments according to the present invention and is not limited thereto.
Fig. 5 is a flow chart for obtaining an updated image in the first embodiment according to the present invention. As shown in Fig. 5, when the firmware of multiple RMCs of the rack 1 (only one RMC is used as an example in the following illustration) need to be updated, the rack 1 is connected to an external update tool (for example a 10 personal computer or a cloud server etc. not shown in the diagrams). The update tool sends a control command to the RMC in rack 1 via an interface (for example sends an IPMI command via an IPMI Interface) for enabling the RMC to enter an updating mode (step S10).
Next, the RMC receives the firmware update image F1 via the update tool (step 15 S12). The RMC temporarily saves the received firmware update image F1 in an internal storage unit (step S14), and check if the firmware update image F1 is correct. If the firmware update image F1 is correct, the RMC executes the updating procedure according to the temporarily saved firmware update image F1 (step S16). In the above mentioned embodiment, the first RMC 21 and the second RMC 31 both start to execute the updating procedure by following the above steps S10 to step S16.
Fig. 6 is a flow chart for firmware update in the first embodiment according to the present invention. In the present invention, the firmware update flow of the present invention is used in a rack with at least two rack management modules. First, the RMC in one of the rack management modules of the rack 1 (for example the first RMC 25 21 in the first rack management module 2) receives the above mentioned updating command (step S20). Next, the RMC sends the switching instruction to the switch of
20155207 prh 14-08- 2018 the same rack management module (for example the first switch 22) for enabling the switch to switch and connect to the memory of another rack management module (for example the second memory 33 in the second rack management module 3) (step
S22).
After the switch finishes switching, the RMC performs updating procedure on firmware in the memory of another rack management module according to the firmware update image F1 temporarily saved in the installed storage unit (step S24). After the updating procedures execution finishes, the RMC is reset, and the switch of the same the rack management module is recovered to the initial settings (step S26), 10 wherein, the switch connects to the memory of the same rack management module based on the initial settings after the step S26.
After the RMC which executes the updating procedure in the step S24 is reset, it connects to the memory of the same rack management module via the switch of the same rack management module, and executes the firmware in the memory to finish the booting procedure (step S28). Lastly, the RMC determines if the previous updating procedure execution succeeds (step S30). If the update fails, the step returns to step S22, and re-update the firmware of another rack management module. On the other hand, if the update succeeds, the RMC finishes the updating procedure.
The updating method of the present invention can effectively avoid the issue that the RMC is not able to boot normally after the firmware updating procedure fails.
Fig. 7 is a backup flowchart in the first embodiment according to the present invention. The backup flow of the present invention is implemented on the rack with at least two rack management modules. Firstly, the RMCs of the at least two rack management modules in the rack 1 are interconnected via the communicating interface I0, and performs a heartbeat detection via the communicating interface I0 with each other (step S40).
During the heartbeat detection, each RMC respectively determines if the heartbeat of another RMC is abnormal (step S42). If the heartbeat of another RMC is normal, the step S40 is executed again in order to keep performing heartbeat detection on another RMC.
On the other hand, if the heartbeat of another RMC is abnormal after the detection, the RMC with normal heartbeat sends the instruction via the communicating interface 10 to enforce a reset of the RMC with abnormal heartbeat, and enable itself as the active RMC in the rack 1 (step S44). With the backup operation solution, when one of the RMCs in the rack 1 operates abnormally, another
RMC then performs backup operation temporarily, and recovered to the original operation after the RMC operates abnormally is reset. As a result, it is avoided that multiple nodes in the rack 1 are not able to operate normally after certain RMCs have errors.
As the skilled person will appreciate, various changes and modifications can be madetothedescribedembodiment.lt is intended to include all such variations, modifications and equivalents which fall within the scope of the present invention, as defined in the accompanying claims.
20155207 prh 14-08- 2018
20155207 prh 11 -05- 2018
Patent claims
1. A rack (1), comprising:
a plurality of receiving slots;
a plurality of nodes (4), respectively disposed in the plurality of receiving slots;
two rack management modules (2,3), electrically connected with the plurality of nodes (4), each rack management module (2,3) respectively having a rack management controller (RMC) (21,31), a switch (22,32) and a memory (23,33) having a firmware (231,331), wherein the RMC (21,31) is arranged to connect to the memory (23,33) via the switch (22,33), and the firmware (231,331) is arranged for booting by the RMC (21,31) saved in the memory (23,33), characterized in that said two rack management modules (2,3) comprise:
a first rack management module (2) electrically connected with the plurality of nodes (4), comprising a first RMC (21), a first switch (22) and a first memory (23) having a first firmware (231), wherein the first switch (22) is arranged to connect to the first memory (23) via a first access channel (LI), the first RMC (21) is arranged to connect to the first memory (23) through the first switch (22), and the first firmware (231) is arranged for booting by the first RMC (21) and a second rack management module (3) electrically connected with the plurality of nodes (4), comprising a second RMC (31), a second switch (32) and a second memory (33) having a second firmware (331), wherein the second switch (32) is arranged to connect to the second memory (33) via a second access channel (L2), the second RMC (31) is arranged to connect to the second memory (33) through the second switch (32), and the second firmware (331) is arranged for booting by the second RMC (31), wherein the first switch (22) and the second switch (32) are interconnected via a third access channel (L3);
wherein, the first RMC (21) is arranged to connect to the first switch (22) via a first instruction transmission interface (11), and the second RMC (31) is arranged to connect to the second switch (32) via a second instruction transmission interface (12);
wherein, when only receiving a firmware update image (Fl) at the first RMC (21), the first RMC (21) is arranged to send a switch instruction (Cl) to the first switch (22) through the first instruction transmission interface (11) for enabling the first switch (22) to switch and to connect to the second memory (33) through the third access channel (L3), the second switch (32) and the second access channel (L2), and the first RMC (21) then performing an
20155207 prh 11 -05- 2018 updating procedure on the second memory (33) for updating the second firmware (331) of the second memory (33) according to the firmware update image (Fl);
wherein, when only receiving the firmware update image (Fl) at the second RMC (31), the second RMC (31) is arranged to send the switch instruction (C2) to the second switch (32) through the second instruction transmission interface (12) for enabling the second switch (32) to switch and to connect to the first memory (23) through the third access channel (L3), the first switch (22) and the first access channel (LI), and the second RMC (31) then performing the updating procedure on the first memory (23) for updating the first firmware (231) of the first memory (23) according to the firmware update image (Fl).
2. The rack (1) according to claim 1, wherein the first RMC (21) has a first storage unit (211) for temporarily saving the firmware update image (Fl), when the first RMC (21) is arranged to execute the updating procedure, the firmware update image (Fl) temporarily saved in the first storage unit (211) is arranged to be recorded to the second memory (33) in order to finish the updating procedure.
3. The rack (1) according to claim 1, wherein second RMC (31) has a second storage unit (311) for temporarily saving the firmware update image (Fl), when the second RMC (31) is arranged to execute the updating procedure, the firmware update image (Fl) temporarily saved in the second storage unit (311) is arranged to be recorded to the first memory (23) in order to finish the updating procedure.
4. The rack (1) according to claim 1, wherein the first RMC (21) and the second RMC (31) are arranged to interconnect via a communicating interface (10), and to detect heartbeats of each other via the communicating interface (10), wherein the communicating interface (10) is a General Purpose I/O (GPIO) interface, an Universal Asynchronous Receiver/Transmitter (UART) interface, an Inter-Integrated Circuit (l2C) interface, an Intelligent Platform Management Bus (IPMB) interface or a Local Area Network (LAN) interface.
5. A firmware updating method used by the rack (1) according to claim 1, comprising:
a) receiving the firmware update image (Fl) by the first RMC (21);
b) sending the switching instruction (Cl) to the first switch (22) through the first instruction transmission interface (11) for enabling the first switch (22) to switch and connect to the second memory (33) of the second rack management (3) by the first RMC (21) after
20155207 prh 14-08- 2018 receiving the firmware update image (Fl);
c) performing the updating procedure on the second firmware (331) in the second memory (33) of the second rack management module (3) according to the firmware update image (Fl) by the first RMC (21);
d) performing a reset of the first RMC (21) after the updating procedure and the first switch (22) is recovered to initial settings, wherein the first switch (22) switches and connects to the first memory (23) based on the initial settings; and
e) after the first RMC (21) reset, executing a booting procedure via the first firmware (231) in the first memory (23) by the first RMC (21).
6. The firmware updating method according to claim 5, further comprising:
f) receiving the firmware update image (Fl) by the second RMC (31);
g) sending the switching instruction (C2) to the second switch (32) through the second instruction transmission interface (12) for enabling the second switch (32) to switch and connect to the first memory (23) of the first rack management (2) by the second RMC (31) after receiving the firmware update image (Fl);
h) performing the updating procedure on the first firmware (231) in the first memory (23) of the first rack management module (2) according to the firmware update image (Fl) by the second RMC (31);
i) performing a reset of the second RMC (31) after the updating procedure and the second switch (32) is recovered to initial settings, wherein the second switch (32) switches and connects to the second memory (33) based on the initial settings; and
j) after the second RMC (31) reset, executing the booting procedure via the second firmware (331) in the second memory (33) by the second RMC (31).
7. The firmware updating method according to claim 5, wherein the step a) comprises following steps:
aOl) receiving the firmware update image (Fl) and an updating command; a02) entering an updating mode; and a03) temporarily saving the firmware update image (Fl) in a storage unit (211) of the first RMC (21).
8. The firmware updating method according to claim 5, wherein the method comprises following steps:
20155207 prh 14-08- 2018
k) after the step e, determining if the updating procedure succeeds by the first RMC (21); and
l) following the step k, if the updating procedure fails, re-executing the step b to the step e.
9. The firmware updating method according to claim 6, wherein the step f) comprises following steps:
fOl) receiving the firmware update image (Fl) and an updating command; f02) entering an updating mode; and f03) temporarily saving the firmware update image (Fl) in a storage unit (311) of the second RMC (31).
10. The firmware updating method according to claim 6, wherein the method comprises following steps:
m) after the step j, determining if the updating procedure succeeds by the second
RMC (31); and
n) following the step m, if the updating procedure fails, re-executing the step g to the step j.
11. The firmware updating method according to claim 5, wherein the method comprises following steps:
o) performing heartbeat detection by the first RMC (21) and the second RMC (31) via a communicating interface (10);
p) determining if heartbeats of another RMC is normal; and
q) when the heartbeats of the another RMC is abnormal, sending instructions by the RMC with normal heartbeats to enforce a reset of the RMC with abnormal heartbeats and enabling itself to be an active RMC in the rack (1).
20155207 prh 14-08- 2018

Claims (11)

PatenttivaatimuksetThe claims 1. Teline (1), jossa on useita vastaanottoaukkoja;A rack (1) having a plurality of receiving openings; 5 useita solmuja (4), jotka on sijoitettu useisiin vastaanottoaukkoihin;A plurality of nodes (4) disposed in a plurality of receiving apertures; kaksi telineen hallintamoduulia (2, 3), jotka on yhdistetty sähköisesti useisiin solmuihin (4), ja kussakin telineen hallintamoduulissa (2, 3) on telineen hallintaohjain (RMC) (21, 31), kytkin (22, 32) ja laiteohjelmiston (231, 331) käsittävä muisti (23, 33), jossatwo rack management modules (2, 3) electrically connected to a plurality of nodes (4), and each rack management module (2, 3) has a rack management controller (RMC) (21, 31), a switch (22, 32) and firmware (231). , 331) memory (23, 33), wherein 10 RMC (21, 31) on järjestetty siten, että se yhdistyy muistiin (23, 33) kytkimen (22,The RMC (21, 31) is arranged to connect to the memory (23, 33) of the switch (22, 33) välityksellä, ja laiteohjelmisto (231, 331) on järjestetty käynnistettäväksi RMC:llä (21, 31) ja tallennettu muistiin (23, 33), tunnettu siitä, että sanotut kaksi telineen hallintamoduulia (2, 3) käsittävät33), and the firmware (231, 331) is arranged to be started by the RMC (21, 31) and stored in the memory (23, 33), characterized in that said two rack control modules (2, 3) comprise 15 ensimmäinen telineen hallintamoduulin (2), joka on yhdistetty sähköisesti useisiin solmuihin (4) ja joka käsittää ensimmäisen RMC:n (21), ensimmäisen kytkimen (22) ja ensimmäisen muistin (23), joka sisältää ensimmäisen laiteohjelmiston (231), jossa ensimmäinen kytkin (22) on järjestetty muodostamaan yhteyden ensimmäiseen muistiin (23) ensimmäisen liittymäkanavan (LI) välityksellä, ensimmäinen RMC (21) on järjestettyA first rack control module (2) electrically connected to a plurality of nodes (4) comprising a first RMC (21), a first switch (22) and a first memory (23) containing a first firmware (231), wherein the first the switch (22) being arranged to connect to the first memory (23) via the first access channel (LI), the first RMC (21) being arranged 20 muodostamaan yhteyden ensimmäiseen muistiin (23) ensimmäisen kytkimen (22) välityksellä ja ensimmäinen laiteohjelmisto (231) on järjestetty käynnistettäväksi ensimmäisellä RMC:llä (21), ja toisen telineen hallintamoduulin (3), joka on yhdistetty sähköisesti useisiin solmuihin (4) ja joka käsittää toisen RMC:n (31), toisen kytkimen (32) ja toisen muistin (33),20, communicating with the first memory (23) via the first switch (22), and the first firmware (231) being arranged to be started by the first RMC (21) and a second rack control module (3) electrically connected to the plurality of nodes (4); comprising a second RMC (31), a second switch (32) and a second memory (33), 25 joka sisältää toisen laiteohjelmiston (331), jossa toinen kytkin (32) on järjestetty muodostamaan yhteyden toiseen muistiin (33) toisen liittymäkanavan (L2) välityksellä, toinen RMC (31) on järjestetty muodostamaan yhteyden toiseen muistiin (33) toisen kytkimen (32) välityksellä ja toinen laiteohjelmisto (331) on järjestetty käynnistettäväksi toisella RMC:lla (31), jossa ensimmäinen kytkin (22) ja toinen kytkin (32) on yhdistetty25 including second firmware (331), wherein one switch (32) is configured to connect to a second memory (33) via a second access channel (L2), a second RMC (31) being configured to connect to a second memory (33), a second switch (32). and the second firmware (331) is arranged to be started on the second RMC (31), wherein the first switch (22) and the second switch (32) are connected 30 toisiinsa kolmannen liittymäkanavan (L3) välityksellä;30 interconnected via a third access channel (L3); jossa ensimmäinen RMC (21) on järjestetty muodostamaan yhteyden ensimmäiseen kytkimeen (22) ensimmäisen käskyjen lähetysrajapinnan (11) välityksellä ja toinen RMC (31) on järjestetty muodostamaan yhteyden toiseen kytkimeen (32) toisen käskyjen lähetysrajapinnan (12) välityksellä;wherein the first RMC (21) is configured to communicate with the first switch (22) via a first command transmission interface (11) and the second RMC (31) is configured to communicate with the second switch (32) via a second command transmission interface (12); 35 jossa vain ensimmäisen RMC:n (21) vastaanottaessa laiteohjelmiston35 where only the first RMC (21) receives firmware 20155207 prh 14-08- 2018 päivitysnäköistiedoston (Fl) ensimmäinen RMC (21) on järjestetty lähettämään kytkentä käskyn (Cl) ensimmäiselle kytkimelle (22) ensimmäisen käskyjen lähetysrajapinnan (11) välityksellä, jotta ensimmäinen kytkin (22) voi kytkeä ja muodostaa yhteyden toiseen muistiin (33) kolmannen liittymäkanavan (L3), toisen kytkimen (32) ja toisen liittymäkanavan20155207 prh 14-08-2018 The first RMC (21) of the update visualization file (F1) is arranged to send the switch to the first switch (22) of the instruction (Cl) via the first command transmission interface (11) so that the first switch (22) can connect and connect to the second memory. (33) a third access channel (L3), a second switch (32) and a second access channel 5 (L2) välityksellä, ja ensimmäinen RMC (21) suorittaa sitten päivitysmenettelyn toisessa muistissa (33) toisen muistin (33) toisen laiteohjelmiston (331) päivittämistä varten laiteohjelmiston päivitysnäköistiedoston (Fl) mukaisesti;5 (L2), and the first RMC (21) then performs an update procedure in the second memory (33) for updating the second firmware (331) according to the firmware update image (F1); jossa vain toisen RMC:n (31) vastaanottaessa laiteohjelmiston päivitysnäköistiedoston (Fl) toinen RMC (31) järjestetty lähettämään kytkentäkäskyn (C2) toiselle kytkimelle (32)wherein, when only one RMC (31) receives the firmware update image file (F1), the other RMC (31) is arranged to send a switch command (C2) to the second switch (32). 10 toisen käskyjen lähetysrajapinnan (12) välityksellä, jotta toinen kytkin (32) voi kytkeä ja muodostaa yhteyden ensimmäiseen muistiin (23) kolmannen liittymäkanavan (L3), ensimmäisen kytkimen (22) ja ensimmäisen liittymäkanavan (LI) välityksellä, ja toinen RMC (31) suorittaa sitten päivitysmenettelyn ensimmäisessä muistissa (23) ensimmäisen muistin (23) ensimmäisen laiteohjelmiston (231) päivittämistä varten laiteohjelmiston10 via a second command transmission interface (12) for the second switch (32) to connect and connect to the first memory (23) via a third access channel (L3), a first switch (22) and a first access channel (L1), and a second RMC (31). then performing an update procedure in the first memory (23) for updating the first firmware (231) of the first memory (23) with the firmware 15 päivitysnäköistiedoston (Fl) mukaisesti.15 according to the update image (Fl). 2. Vaatimuksen 1 mukainen teline (1), jossa ensimmäisessä RMC:ssä (21) on ensimmäinen muistiyksikkö (211) laiteohjelmiston päivitysnäköistiedoston (Fl) väliaikaista tallennusta varten, ja ensimmäinen RMC (21) on järjestetty suorittamaan päivitysmenettely,The rack (1) of claim 1, wherein the first RMC (21) has a first memory unit (211) for temporarily storing a firmware update image file (F1), and the first RMC (21) is configured to perform an update procedure, 20 ja ensimmäiseen muistiyksikköön (211) väliaikaisesti tallennettu laiteohjelmiston päivitysnäköistiedosto (Fl) on järjestetty tallennettavaksi toiseen muistiin (33) päivitysmenettelyn saattamiseksi päätökseen.20 and a firmware update image file (F1) temporarily stored in the first memory unit (211) is arranged to be stored in the second memory (33) to complete the update procedure. 3. Vaatimuksen 1 mukainen teline (1), jossa toisessa RMC:ssä (31) on toinenThe rack (1) of claim 1, wherein the second RMC (31) has another 25 muistiyksikkö (311) laiteohjelmiston päivitysnäköistiedoston (Fl) väliaikaista tallennusta varten, ja toinen RMC (31) on järjestetty suorittamaan päivitysmenettely, ja toiseen muistiyksikköön (311) väliaikaisesti tallennettu laiteohjelmiston päivitysnäköistiedosto (Fl) on järjestetty tallennettavaksi ensimmäiseen muistiin (23) päivitysmenettelyn saattamiseksi päätökseen.A 25 memory unit (311) for temporarily storing a firmware update image (F1), and a second RMC (31) arranged to perform an update procedure, and a second firmware (311) temporarily stored in the second memory unit (311) arranged to be stored in the first memory (23). 4. Vaatimuksen 1 mukainen teline (1), jossa ensimmäinen RMC (21) ja toinen RMC (31) on järjestetty muodostamaan yhteyden toisiinsa viestintärajapinnan (10) välityksellä ja tunnistamaan toistensa sykkeen viestintärajapinnan (10) välityksellä, jossa viestintärajapinta (10) on GPIO-rajapinta (General Purpose I/O), UART-rajapinta (Universal AsynchronousThe rack (1) of claim 1, wherein the first RMC (21) and the second RMC (31) are arranged to communicate with one another via a communication interface (10) and to identify each other's heart rate via a communication interface (10), wherein the communication interface (10) interface (General Purpose I / O), UART (Universal Asynchronous 20155207 prh 14-08- 201820155207 prh 14-08- 2018 Receiver/Transmitter), l2C-rajapinta (Inter-Integrated Circuit), IPMB-rajapinta (IntelligentReceiver / Transmitter), l 2 C Interface (Inter-Integrated Circuit), IPMB Interface (Intelligent) Platform Management Bus) tai LAN-rajapinta (lähiverkko).Platform Management Bus) or LAN interface (LAN). 5. Laiteohjelmiston päivitysmenetelmä, jota käytetään vaatimuksen 1 mukaisessa 5 telineessä (1) ja joka käsittää seuraavat vaiheet:A firmware upgrade method for use in the 5 racks (1) of claim 1, comprising the steps of: a) ensimmäinen RMC (21) vastaanottaa laiteohjelmiston päivitysnäköistiedoston (Fl);a) the first RMC (21) receives the firmware update image file (F1); b) ensimmäinen RMC (21) lähettää kytkentäkäskyn (Cl) ensimmäiselle kytkimelle (22) ensimmäisen käskyjen lähetysrajapinnan (11) välityksellä, jotta ensimmäinen kytkin (22)b) the first RMC (21) transmits the switching instruction (Cl) to the first switch (22) via the first command transmission interface (11) so that the first switch (22) 10 voi kytkeä ja muodostaa yhteyden toisen telineen hallinnan (3) toiseen muistiin (33) laiteohjelmiston päivitysnäköistiedoston (Fl) vastaanottamisen jälkeen;10 may connect and connect to a second memory (33) of the second rack manager (3) after receiving the firmware update visualization file (F1); c) ensimmäinen RMC (21) suorittaa toisen laiteohjelmiston (331) päivitysmenettelyn toisen telineen hallintamoduulin (3) toisessa muistissa (33) laiteohjelmiston päivitysnäköistiedoston (Fl) mukaisesti;c) a first RMC (21) performing a procedure for updating the second firmware (331) in the second memory (33) of the second rack management module (3) according to the firmware update visualization file (F1); 15 d) ensimmäinen RMC (21) nollataan päivitysmenettelyn jälkeen ja ensimmäisen kytkimen (22) alkuasetukset palautetaan, ja ensimmäinen kytkin (22) kytkee ja muodostaa yhteyden ensimmäiseen muistiin (23) alkuasetusten perusteella; jaD) resetting the first RMC (21) after the update procedure and resetting the first switch (22), and switching and connecting the first switch (22) to the first memory (23) based on the initial settings; and e) ensimmäisen RMC:n (21) nollauksen jälkeen ensimmäinen RMC (21) suorittaa käynnistysmenettelyn ensimmäisen laiteohjelmiston (231) välityksellä ensimmäisessäe) after resetting the first RMC (21), the first RMC (21) performs the boot procedure via the first firmware (231) in the first 20 muistissa (23).20 in memory (23). 6. Vaatimuksen 5 mukainen laiteohjelmiston päivitysmenetelmä, joka käsittää lisäksi seuraavat vaiheet:The firmware update method of claim 5, further comprising the steps of: f) toinen RMC (31) vastaanottaa laiteohjelmiston päivitysnäköistiedoston (Fl);f) the second RMC (31) receives the firmware update image file (F1); 25 g) toinen RMC (31) lähettää kytkentäkäskyn (C2) toiselle kytkimelle (32) toisen käskyjen lähetysrajapinnan (12) välityksellä, jotta toinen kytkin (32) voi kytkeä ja muodostaa yhteyden ensimmäisen telineen hallinnan (2) ensimmäiseen muistiin (23) laiteohjelmiston päivitysnäköistiedoston (Fl) vastaanottamisen jälkeen;G) the second RMC (31) transmits the switch command (C2) to the second switch (32) via the second command transmission interface (12) so that the second switch (32) can connect and connect to the first memory (23) of the firmware update image (Fl) after receipt; h) toinen RMC (31) suorittaa ensimmäisen laiteohjelmiston (231)h) the second RMC (31) executes the first firmware (231) 30 päivitysmenettelyn ensimmäisen telineen hallintamoduulin (2) ensimmäisessä muistissa (23) laiteohjelmiston päivitysnäköistiedoston (Fl) mukaisesti;An update procedure in the first memory (23) of the first rack management module (2) according to the firmware update image (F1); i) toinen RMC (31) nollataan päivitysmenettelyn jälkeen ja toisen kytkimen (32) alkuasetukset palautetaan, ja toinen kytkin (32) kytkee ja muodostaa yhteyden toiseen muistiin (33) alkuasetusten perusteella; jai) resetting one RMC (31) after the update procedure and resetting the second switch (32), and switching and connecting the second switch (32) to the second memory (33) based on the initial settings; and 20155207 prh 14-08- 201820155207 prh 14-08- 2018 j) toisen RMC:n (31) nollauksen jälkeen toinen RMC (31) suorittaa käynnistysmenettelyn toisen laiteohjelmiston (331) välityksellä toisessa muistissa (33).j) after resetting the second RMC (31), the second RMC (31) performs the boot procedure through the second firmware (331) in the second memory (33). 7. Vaatimuksen 5 mukainen laiteohjelmiston päivitysmenetelmä, jossa vaihe a sisältää 5 seuraavat vaiheet:The firmware update method of claim 5, wherein step a comprises 5 of the following steps: aOl) laiteohjelmiston päivitysnäköistiedoston (Fl) ja päivityskäskyn vastaanottaminen;aOl) receiving a firmware update visualization file (F1) and an update command; a02) päivitystilaan siirtyminen; ja a03) laiteohjelmiston päivitysnäköistiedoston (Fl) väliaikainen tallentaminen 10 ensimmäisen RMC:n (21) muistiyksikköön (211).a02) entering upgrade mode; and a03) temporarily storing a firmware update image (F1) in the memory unit (211) of the first RMC (21). 8. Vaatimuksen 5 mukainen laiteohjelmiston päivitysmenetelmä, joka käsittää seuraavat vaiheet:The firmware update method according to claim 5, comprising the steps of: k) vaiheen e jälkeen sen määrittäminen, onnistuuko ensimmäisen RMC:n (21)k) after step e, determining whether the first RMC succeeds (21) 15 päivitysmenettely; ja15 upgrade procedure; and l) vaiheen k jälkeen, jos päivitysmenettely epäonnistuu, vaiheiden b-e suorittaminen uudelleen.l) after step k, if the update procedure fails, repeating steps b to e. 9. Vaatimuksen 6 mukainen laiteohjelmiston päivitysmenetelmä, jossa vaihe f) sisältää 20 seuraavat vaiheet:The firmware update method according to claim 6, wherein step f) comprises the following 20 steps: fOl) laiteohjelmiston päivitysnäköistiedoston (Fl) ja päivityskäskyn vastaanottaminen;fOl) receiving a firmware update visualization file (F1) and an update command; f02) päivitystilaan siirtyminen; ja f03) laiteohjelmiston päivitysnäköistiedoston (Fl) väliaikainen tallentaminen 25 toisen RMC:n (31) muistiyksikköön (311).f02) entering update mode; and f03) temporarily storing a firmware update image (F1) in the memory unit (311) of the second RMC (31). 10. Vaatimuksen 6 mukainen laiteohjelmiston päivitysmenetelmä, joka käsittää seuraavat vaiheet:The firmware update method according to claim 6, comprising the steps of: m) vaiheen j jälkeen sen määrittäminen, onnistuuko toisen RMC:n (31)m) after step j, determining whether the second RMC succeeds (31) 30 päivitysmenettely; ja30 upgrade procedure; and n) vaiheen m jälkeen, jos päivitysmenettely epäonnistuu, vaiheiden g-j suorittaminen uudelleen.n) after step m, if the update procedure fails, repeat steps g to j. 11. Vaatimuksen 5 mukainen laiteohjelmiston päivitysmenetelmä, joka käsittää seuraavat vaiheet:The firmware update method according to claim 5, comprising the steps of: o) ensimmäisen RMC:n (21) ja toisen RMC:n (31) suorittama sykkeen tunnistus viestintärajapinnan (10) välityksellä;o) heart rate detection by the first RMC (21) and the second RMC (31) via the communication interface (10); p) sen määrittäminen, onko toisen RMC:n syke normaali; jap) determining whether the second RMC has a normal heart rate; and 5 q) kun toisen RMC:n syke on epänormaali, sykkeeltään normaali RMC lähettää käskyn, jolla suoritetaan sykkeeltään epänormaalin RMC:n nollaus ja jolla siitä tulee telineen (1) aktiivinen RMC.Q) When the second RMC's heart rate is abnormal, the normal heart rate RMC sends an instruction to reset the abnormal heart rate RMC and becomes the active RMC of the rack (1). 20155207 prh 14-08- 201820155207 prh 14-08- 2018 20155207 prh 24-03- 201520155207 prh 24-03- 2015
FI20155207A 2015-01-05 2015-03-24 Rack having multiple rack management modules and firmware updating method for the same FI127566B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW104100072A TWI576682B (en) 2015-01-05 2015-01-05 Rack havng multi-rmms and firmware updating method for the rack

Publications (2)

Publication Number Publication Date
FI20155207A FI20155207A (en) 2016-07-06
FI127566B true FI127566B (en) 2018-09-14

Family

ID=56590387

Family Applications (1)

Application Number Title Priority Date Filing Date
FI20155207A FI127566B (en) 2015-01-05 2015-03-24 Rack having multiple rack management modules and firmware updating method for the same

Country Status (3)

Country Link
FI (1) FI127566B (en)
RU (1) RU2602378C9 (en)
TW (1) TWI576682B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10489136B2 (en) * 2017-04-27 2019-11-26 Quanta Computer Inc. Automatic firmware and custom setting provision for server device
TWI655582B (en) * 2017-09-12 2019-04-01 神雲科技股份有限公司 Server with dual firmware storage space and firmware update method thereof
RU2697745C1 (en) * 2018-04-18 2019-08-19 ЭйАйСи ИНК. Intelligent rack and method of managing ip-addresses used therein
RU2710288C1 (en) * 2019-04-09 2019-12-25 ЭйАйСи ИНК. Method of remote abnormal state reset of racks used in data center
RU2711469C1 (en) * 2019-04-09 2020-01-17 ЭйАйСи ИНК. Method of remote abnormal state reset of racks used in data center
RU2709677C1 (en) * 2019-04-09 2019-12-19 ЭйАйСи ИНК. Method of remote abnormal state reset of racks used in data center
TWI726434B (en) * 2019-10-03 2021-05-01 神雲科技股份有限公司 Control method for solving abnormal operation of me
CN113687998A (en) * 2020-05-19 2021-11-23 佛山市顺德区顺达电脑厂有限公司 Control method for eliminating abnormal operation of management engine

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7222339B2 (en) * 2003-06-13 2007-05-22 Intel Corporation Method for distributed update of firmware across a clustered platform infrastructure
US7849454B2 (en) * 2006-01-13 2010-12-07 Dell Products L.P. Automatic firmware corruption recovery and update
TWI326408B (en) * 2006-11-15 2010-06-21 Inventec Corp Method of updating an image file
RU2389058C2 (en) * 2008-06-07 2010-05-10 Открытое акционерное общество "Т-Платформы" Server platform
US9547575B2 (en) * 2011-08-30 2017-01-17 Amazon Technologies, Inc. Managing host computing devices
TWI462691B (en) * 2011-12-26 2014-11-21 Inventec Corp Rack server and management method of the same
TW201345362A (en) * 2012-04-26 2013-11-01 Acer Inc Devices and methods for rack system management
CN103793238A (en) * 2012-10-31 2014-05-14 英业达科技有限公司 Rack and method for simultaneously updating multiple basic input output systems thereof

Also Published As

Publication number Publication date
TWI576682B (en) 2017-04-01
RU2602378C1 (en) 2016-11-20
FI20155207A (en) 2016-07-06
TW201626134A (en) 2016-07-16
RU2602378C9 (en) 2017-01-31

Similar Documents

Publication Publication Date Title
FI127566B (en) Rack having multiple rack management modules and firmware updating method for the same
EP2375323A1 (en) Firmware image update and management
US20170109235A1 (en) Baseboard management controller recovery
US20160306623A1 (en) Control module of node and firmware updating method for the control module
CN107209671A (en) The dynamic auto monitoring and control of start-up operation in computer
WO2016206514A1 (en) Startup processing method and device
US20130117518A1 (en) System controller, information processing system and method of saving and restoring data in the information processing system
US10922071B2 (en) Centralized off-board flash memory for server devices
US10880153B2 (en) Method and system for providing service redundancy between a master server and a slave server
CN105988844A (en) Control module of endpoint server and firmware update method thereof
US20170132102A1 (en) Computer readable non-transitory recording medium storing pseudo failure generation program, generation method, and generation apparatus
US9385920B1 (en) Rack having multiple rack management modules and firmware updating method for the same
CN112433769A (en) BMC starting method and device, computer equipment and storage medium
CN105843336B (en) Cabinet and its firmware updating method with more cabinet management modules
RU2600101C1 (en) Assembly control module and method of firmware updating for this control module
CN115437674B (en) Firmware upgrading method, device, medium and electronic equipment
US9798608B2 (en) Recovery program using diagnostic results
CN113867812B (en) Method, system, equipment and medium for BMC to acquire link information
TWI777664B (en) Booting method of embedded system
CN115168146A (en) Anomaly detection method and device
CN113377425A (en) BMC firmware generation method and device, BMC starting method and device and storage medium
KR20130070512A (en) Storage system, control device, and storage system control method of controlling storage system
JP6331505B2 (en) Startup control device, startup control method, and startup control program
TWI726434B (en) Control method for solving abnormal operation of me
CN107451035B (en) Error state data providing method for computer device

Legal Events

Date Code Title Description
FG Patent granted

Ref document number: 127566

Country of ref document: FI

Kind code of ref document: B

MM Patent lapsed