FI127498B - Rack having automatic recovery function and automatic recovery method for the same - Google Patents

Abstract

A rack comprising a control module and a plurality of nodes is present. The control module comprises a rack management controller (RMC), and each of the plurality of nodes comprises a baseboard management controller (BMC). The RMC communicates with the BMCs respectively through a plurality of default communication channels, and the RMC controls the nodes and transmits necessary data thereto through the BMCs. When losing response signal from one of the BMCs, the RMC resends same signal to the non-responded BMC. If a resend threshold is achieved, the RMC sends a control signal to a reset pin of the non-responded BMC directly through a GPIO channel to force the non-responded BMC to reset.

Description

RACK HAVING AUTOMATIC RECOVERY FUNCTION AND AUTOMATIC RECOVERY METHOD FOR THE SAME

BACKGROUND OF THE INVENTION 1. Field of the Invention

The invention relates to a rack, and particularly to a rack having an automatic recovery function, and an automatic recovery method used by the rack. 2. Description of Prior Art

Generally, each server is arranged in a rack corresponding to a baseboard management controller (BMC), and the Servers respectively use the BMCs to control and maintain themselves.

The rack usually consists of a rack management controller (RMC) used to communicate with the BMCs in the Servers. The rack uses the RMC to control the Servers, collect information from the Servers, and transmit files needed by the Servers (such as updated files for updating the firmware) through the BMCs.

In related art, RMC basically communicates with BMCs through communication channels such as Intelligent Platform Management Bus (IPMB), inter-integrated circuit (IC) or local area network (LAN), and uses communication channels to transmit control command, information and files.

However, each communication channel mentioned above is bi-directional. More specific if the RMC wants to communicate with the target BMC, it needs to send an initial ASK signal to the target BMC in advance. After receiving a RESPONSE signal from the target BMC, the RMC can make sure that the communication channel is flowing, and then transmit real data to the target BMC. In other words, if the target BMC itself or the communication interface of the BMC has a problem (for example, the firmware failure or hardware signal mistake), such that the target BMC cannot respond to the ASK signal from the RMC, the RMC cannot communicate with target BMC successfully.

In the current rack, each server in the rack is configured with a watchdog function that can detect problems with the BMC and reset the BMC automatically when the BMC do have a problem. However, the watchdog function mentioned above can only detect some specific failure (for example, the whole BMC shuts down). In some situations, the watchdog function cannot accurately detect what happens to the BMC and will not reset the BMC automatically. As a result, RMC can only notify the manager of the rack by itself (for example, makes an alert via a buzzer or a LED section, sends emails or MMS to the manager, etc.).

If the manager receives the alert above, he or she will reset the BMC manually (for example, pulls the server from the rack (for interrupting the power of the BMC), and then inserts the server into the rack again (for resetting the BMC) ).

As described above, the communication problem between RMC and BMC can only be solved manually in related art, it is very inconvenient. Also, if the rack is sold to the client and the client lacks the ability to solve the above problem, the client needs to send the rack or server back to the original factory for fixing, or to ask the manager to fix the rack or the server at the client directly.

Document US5636341A discloses a system with a communication processor, where a fault occurs in the interface controller is notified of an occurrence and a failure location by means of a broad cast signal.

Document US2005223284A1 discloses a data storage system, wherein the operation of a communication subsystem is enabled to provide communication between the storage processors.

Document D3 discloses an electronic control apparatus for checking a reset function; having a main controller resting the failure signal using a test failure signal.

Document D4 discloses a networker multi-computer environment with redundant links where network interface cards (NICs) are commonly duplicated and teamed to provide a recovery mechanism when network components fail.

SUMMARY OF THE INVENTION

The object of the present invention is to provide a rack having an automatic recovery function and an automatic recovery method used by the rack that can reset a baseboard management controller (BMC) to recover the initial status when a rack management controller (RMC) is in use. the rack cannot communicate with the BMC in a node of the rack regularly.

According to the above object, the present invention discloses a rack comprising a control module and a plurality of nodes. The control module comprises the RMC, and each of the plurality of nodes comprises the BMC. The RMC communicates with the BMCs respectively through a plurality of default communication channels, and the RMC controls the nodes and transmits the necessary data thereto through the BMCs. When losing a response signal from one of the BMCs, the RMC resends the same signal to a non-responding BMC. If the resend threshold is reached, the RMC sends a control signal to the reset pin of the non-responding BMC directly through a GPIO channel to force the non-responding BMC to reset.

Comparing with related art, the present invention can force a BMC to reset and Recover to an initial status through a simple and stable hardware function whenever the BMC has a problem and cannot communicate with the RMC in the rack. The RMC can establish a communication channel with the BMC again after the BMC recovers to the initial status.

Therefore, the present invention can make sure RMC can always control all BMCs in the rack in any situation.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a schematic view of a rack of a first embodiment according to the present invention.

Fig.2 is a connection diagram of a first embodiment according to the present invention.

Fig.3 is a connection diagram of a second embodiment according to the present invention.

Fig.4 is a reset flowchart of a first embodiment according to the present invention.

DETAILED DESCRIPTION OF THE INVENTION

In cooperation with the attached drawings, the technical contents and the detailed description of the present invention are described therein according to the preferred embodiment, being not used to limit its executing scope. Any equivalent variation and modification made according to the appended claims is all covered by the claims claimed by the present invention.

Fig. 1 is a schematic view of a rack of a first embodiment according to the present invention. The present invention discloses a rack 1 which has an automatic recovery function detailed below. In particular, the rack 1 comprises a control module 2 and a plurality of nodes 3, the control module 2 at least comprises a circuit board 21 and a rack management controller (RMC) 22 electrically connected to the circuit board 21, and each of the plurality of nodes 3 respectively consists of a baseboard 31 and a baseboard management controller (BMC) 32 electrically connected to the baseboard 31. The automatic recovery function in the present invention is, for example, a reset action executed for recovering the BMCs 32 in the nodes 3 to an initial status free from communication problems.

The control module 2 and the nodes 3 are respectively arranged in the rack 1, and the control module 2 is electrically connected with each node 3. As a result, the RMC 22 in the control module 2 can communicate with each BMC 32 in each node 3 , and can control all of nodes 3, collect information from nodes 3 and transmit necessary files (for example, updated file for firmware update) to nodes 3 via BMCs 32.

Fig.2 is a connection diagram of a first embodiment according to the present invention.

As shown in Fig.2, the RMC 22 in the control module 2 is connected to the BMCs 32 in the nodes 3 respectively through a plurality of default communication channels 4. In this, the default communication channels 4 are accomplished by Intelligent Platform Management bus (IPMB), inter-integrated circuit (IC), universal Asynchronous receiver / transmitter (UART) or local area network (LAN), but not limited thereto. The RMC 22 communicates with the BMCs 32 through the plurality of default communication channels 4 respectively, and transmits files needed by the nodes 3 to the BMCs 32 through the plurality of default communication channels 4 respectively, so the BMCs 32 can use the files continually.

For example, each of the plurality of nodes 3 respectively comprises a memory 33 electrically connected to the BMC 32 therein. Each memory 33 stores a basic input / output system (BIOS) needed by the node 3 the memory 33 arranged. When the BIOSs of the nodes 3 need to be updated, the RMC 22 receives the updated file externally (for example, an “* .ISO” file), and transmits the updated file to the BMCs 32 through the default communication channels 4 respectively. Therefore, the BMCs 32 use the updated file to update the BIOSs in the Memories 33 respectively.

For completing an updating action mentioned above, the RMC 22 needs to send an ASK signal to the BMCs 32 through the default communication channels 4 respectively in advance before transmitting the files to the BMCs 32. After receiving the RESPONSE signal corresponding to the ASK signal from the BMCs 32 respectively, the RMC 22 determines that the BMCs 32 are regular and the default communication channels 4 are flowing.

Therefore, the RMC 22 can transmit the files needed by nodes 3 to the BMCs 32 through the default communication channel 4 respectively.

On the contrary, if one of the plurality of BMCs 32 does not respond to the RMC 22 (ie, the plurality of BMCs 32 comprises at least one non-responded BMC 32), the RMC 22 cannot communicate with the non-responded BMCs 32 and cannot transmit the files to the non-responding BMC 32. For solving this problem, the RMC 22 in the present invention can control the non-responding BMC 32 through another simple and stable hardware function, so as to recover the BMC 32 from a non-responded status to initial status which is regular.

Fig.3 is a connection diagram of a second embodiment according to the present invention. In Fig.3, an amount of BMCs 32 in the rack 1 is depicted by 1 for example, but not intended to limit the scope of the present invention.

The main technical characteristic of the rack 1 in the present invention is that the RMC 22 is electrically connected to the circuit board 21, the BMC 32 is electrically connected to the baseboard 31, and at least one control pin (not shown) of the RMC 22 is electrically connected to the reset pin 321 of the BMC 32 directly through the circuit board 21 and more specific to the RMC 22 in this embodiment is electrically connected to the reset pin 321 of the BMC 32 directly through a general purpose FO (GPIO), and establishes GPIO channel 5 with BMC 32.

By using the technical solution disclosed in the present invention, if the RMC 22 sends the ASK signal to the BMC 32 and does not receive the RESPONSE signal corresponding to the ASK signal from the BMC 32 after a waiting time, the BMC 32 is considered to as a non-responded BMC 32. The RMC 22 resends the same ASK signal to the non-responded BMC 32 again. If the reset time of resending the ASK signal is longer than the resend threshold, the RMC 22 determines that the non-responding BMC 32 has some problem (i.e., the non-responding BMC 32 is considered to be a problematic BMC 32).

In this, when determining the non-responding BMC 32 is the problematic BMC 32, the RMC 22 controls the problematic BMC 32 through the GPIO channel 5. In particular, the RMC 22 sends a control signal (through the control pin) to the reset pin 321 of problematic BMC 32 directly through GPIO channel 5, so as to force problematic BMC 32 to reset.

For example, the RMC 22 is set to output a low potential signal (such as "0") or not output any signal via the control pin in a normal operation, and when the above problem occurs, the RMC 22 changes to output a high potential signal (such as "1"). If the problematic BMC 32 receives the high potential signal at the reset pin 321, it is forced to reset.

However, the above description is just preferred, but not limited thereto.

As mentioned above, no matter what problem BMC 32 has and causes RMC 22 to fail to communicate with BMC 32 through default communication channel 4, RMC 22 can always force BMC 32 to reset through GPIO channel 5, so as to Recover BMC 32 to initial status. Also, the RMC 22 can establish a connection with the BMC 32 again through the default communication channel 4 after the BMC 32 is recovered to its initial status, and communicates with the recovered BMC 32 and transmits data therewith. There is no need to wait for a manager to recover the above problem manually when the RMC 22 cannot communicate with the BMC 32 regularly.

In other embodiments, the RMC 22 can interrupt the power provided for the BMC 32 and then Recover the power for the BMC 32 through the GPIO channel 5, or interrupt the power provided for the node 3 the BMC 32 arranged and then Recover the power for the node 3, so as to accomplish the purpose for resetting the BMC 32.

In particular, the rack 1 in this embodiment comprises one or more power control chips (not shown), and the power control chip is electrically connected to the plurality of nodes 3 and the power source of the rack 1. In this embodiment, the RMC 22 connects with the power control chip through the GPIO channel 5. When the RMC 22 cannot communicate with the BMC 32 through the default communication channel 4, it can send a reset command to the power control chip through the GPIO channel 5. The power control chip interrupts the power provided for the node 3 (or for the BMC 32) according to the content of the reset command, and then resend the power for the node 3 (or for the BMC 32) immediately.

Therefore, the BMC 32 can be reset, and can recover to initial status after the reset action is completed.

It should be mentioned that the power control chip in this complete can control the power provided for all of the nodes 3, if the power is interrupted without permission, it will bother the user a lot. In other embodiments, the RMC 22 can generate and display an alert signal in advance before sending the reset command, and only send the reset command to the power control chip if the user confirms the alert signal and agrees the RMC 22 to execute the reset action . However, the above description is just another preferred embodiment, not intended to limit the scope of the present invention.

Fig.4 is a reset flowchart of a first embodiment according to the present invention. As shown in Fig.4, before the RMC 22 wants to communicate with the BMCs 32, it firstly sends the ASK signal to the BMCs 32 through the default communication channels 4 respectively (step S10). Secondly, the RMC 22 determines if receiving the RESPONSE signal corresponding to the ASK signal from the BMCs 32 through the default communication

channels 4 respectively or not (step S12). After the RMC 22 receives the RESPONSE signal from the BMCs 32, it can communicate with the BMCs 32 through the default communication channels 4 respectively (step S14), and transmits data and files needed by the nodes 3 thereto.

Following the above Descriptions, if the RMC 22 does not receive the RESPONSE signal from one of the BMCs 32 during the waiting time (ie, the BMCs 32 comprises at least one non-responding BMC 32), it determines if the resend time of resending the ASK signal is longer than the resend threshold or not (step S16). If the reset time of the ASK signal is no longer than the resend threshold yet, the RMC 22 resends the ASK signal to the non-responding BMC 32 through one of the default communication channels 4 compliant to the non-responding BMC 32 again, ie , the RMC 22 re-executes step S10 to step S16.

If the resend time of the ASK signal is longer than the resend threshold, the RMC 22

determines the non-responding BMC 32 has a problem and observes the non-responding BMC 32, and sends the control signal to the reset pin 321 of the problematic BMC 32 through the GPIO channel 5, so as to force the problematic BMC 32 to reset (step S18). Furthermore, the RMC 22 Waits for the reset action of the problematic BMC 32, and communicates with the reset BMC 32 again through one of the default communication channels 4 after the reset action is completed (step S20).

By using the rack and the automatic recovery method, the present invention can make sure the RMC in the rack can always control all the BMCs and Recover all the BMCs to the initial status in any situation, so as to salvage the traditional problem that the RMC cannot communicate. with BMCs through default communication channels sometimes.

Therefore, the present invention helps the rack to solve communication problems by itself and prevent from waiting for the manager to solve the above problems manually.

As the skilled person will appreciate, various changes and modifications can be made to the described description. It 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.

Claims (10)

1. An auto-reset pad containing at least one node with a motherboard control controller (BMC); A management module electrically connected to the 5 nodes having a rack management controller (RMC) and the RMC communicating with the BMC via a default communication channel; wherein the RMC is electrically connected to the BMC via a GPIO (General Purpose PO) channel, characterized in that the rack management controller (RMC) is configured; determine whether it receives a RESPONSE signal from the BMC in response to a REQUEST signal via a default communication channel; determine whether the REQUEST signal retransmission time is longer than the retransmission threshold when no RESPONSE signal is received, to retransmit the REQUEST signal to the BMC via a default communication channel if the retransmission time is not longer than the retransmission threshold and 15, via the GPIO channel, to transmit to the BMC a control signal which forces the BMC to return to the initial state when the retransmission time is longer than the retransmission threshold. The rack of claim 1, wherein the RMC includes a guide pin, the BMC includes a return pin, and the RMC control pin is electrically connected to the BMC return pin 20 GPIO channels. The rack of claim 2, wherein the management module further includes a circuit board, the node further includes a motherboard, the RMC is electrically connected to the circuit board, the BMC is electrically connected to the motherboard, and the RMC control pin is electrically connected to the BMC reset pin. 25 A rack as claimed in claim 2, wherein the default communication channel is implemented IPMB (Intelligent platform management bus), IC (Inter-integrated circuit), 20155123 prh 12 -02- 2018 UART (Universal Asynchronous receiver / transmitter) or LAN (Local area network). The rack of claim 1, further comprising a power control circuit electrically connected to the node and the rack power supply, the RMC being connected to the power control circuit Via a GPIO channel and send a reset command to the power control circuit if it does not receive A RESPONSE signal from the BMC via the default communication channel, and the power control circuit interrupts the power supply to the node according to the contents of the return command and then returns the power supply to the node. 6. A rack automatic reset method, wherein the rack includes a management module and a node electrically connected to the management module, the management module including a rack management controller (RMC), a node including a motherboard management controller (BMC) communicating with RMC via a default communication channel, characterized in that : a) determining whether the response signal from the BMC via the default communication channel in the RMC fails; which includes al) determining whether to receive a response signal from the BMC in response A REQUEST signal through a default communication channel; a2) determining whether the REQUEST signal retransmission time is longer than the retransmission threshold when the REPLY signal is not received; a3) re-transmitting the REQUEST signal to the BMC via the default communication channel if the retransmission time is not longer than the retransmission threshold; a4) performing step b) if the retransmission time is longer than the retransmission threshold; and b) if the RMC does not receive the RESPONSE signal from the BMC via the default communication channel, the control signal is sent to the BMC via the general purpose GPIO channel I / O), forcing the reset of the BMC, where the RMC and the BMC are electrically interconnected via a GPIO channel. The automatic reset method of claim 6, wherein the RMC includes a control pin, the BMC includes a reset pin, and the RMC control pin is electrically connected 5 BMC reset pin via GPIO channel for transmitting control signal. The automatic reset method of claim 7, further comprising the step a0 preceding step a: transmitting a REQUEST message to the BMC via a default communication channel from the RMC. The automatic return method of claim 8, further comprising Step c: After step b, the BMC restore operation is awaited and after the completion of the recovery operation, the BMC is re-communicated with the default communication channel.