Power-on and power-off method of whole-cabinet server and power supply system of whole-cabinet server

Abstract

This application discloses a power-on / off method and a power supply system for a rack server, relating to the field of rack server technology. The method includes receiving a command reception notification from a power management controller, wherein the command reception notification is sent by the power management controller to a power-on / off controller in response to a power-on / off command sent by a user terminal; determining whether power-on / off operation of the rack server is required based on the command reception notification; and if so, simultaneously sending power-on / off commands to each power management controller in the rack server, so that each power management controller controls its corresponding power supply unit to power off first and then power on. The embodiments of this application can improve the problem of power supply abnormalities that easily occur when rack servers are powered on and off.

Description

Technical Field

[0001] This application relates to the field of rack server technology, and in particular to a power-on / off method for a rack server and a power supply system for a rack server. Background Technology

[0002] In traditional rack server management, when powering on or off the rack servers is required, the administrator needs to physically go to the data center, walk to the rack, and press the physical power button or manually unplug and plug in the power cord. This method is acceptable when rack servers are small and close together, but it has become unsustainable with the development of data centers becoming larger and more geographically dispersed, the need for automated operation and maintenance, unattended operation, and remote work.

[0003] However, current methods for remotely controlling the power on and off of rack servers can easily lead to abnormal power supply to the rack servers. Summary of the Invention

[0004] This application provides a power-on / off method for a rack server and a power supply system for a rack server, so as to at least solve the problem of power supply abnormalities that are prone to occur when rack servers are powered on or off in the related art.

[0005] This application provides a power-on / off method for a rack-mount server, applied to a power-on / off controller in a rack-mount server power supply system. The power supply system further includes: multiple power supply frames, each power supply frame including a power management controller and a power supply unit. The method includes:

[0006] Receive command reception notifications sent by the power management controller, wherein the command reception notifications are sent by the power management controller to the power-on / off controller in response to the power-on / off command sent by the user terminal;

[0007] Based on the command received notification, determine whether it is necessary to power on or off the entire rack server;

[0008] If so, power-on / off commands are sent to each power management controller in the rack server at the same time, so that each power management controller controls the corresponding power unit to power off first and then power on.

[0009] This application also provides a power supply system for a rack server, including: a power-on / off controller and multiple power supply frames, each power supply frame including a power management controller and a power supply unit;

[0010] The power management controller is used to send commands to the power-on / off controller and receive notifications in response to power-on / off commands sent by the user.

[0011] The power-on / off controller is used to receive notifications based on commands to determine whether the rack server needs to be powered on or off. If so, it sends power-on / off commands to each power management controller so that each power management controller controls the corresponding power unit to power off first and then power on.

[0012] The power supply unit is used to power the entire rack of servers.

[0013] This application allows users to remotely control the power supply of a rack server. When a user wishes to power on or off a rack server, they can send a power-on / off command to the power management controller (HMD) in the server's power supply system. Upon receiving the command, the HMD sends a command reception notification to the power-on / off controllers within the power supply system. These controllers, after determining that power-on / off is necessary, simultaneously send power-on / off commands to each HMD in the rack server. This ensures that each HMD controls its corresponding power unit to power off first and then power on, thus achieving remote control of the rack server's power supply. Therefore, this application enables remote power-on / off control of rack servers. Furthermore, because the power-on / off controller can simultaneously send commands to each HMD in the rack server, each HMD can simultaneously control its corresponding power unit to power off first and then power on, ensuring near-synchronous power-on / off of all power units in the rack server. This mitigates the problem of power supply anomalies that often occur when powering on or off rack servers. Attached Figure Description

[0014] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 This is a flowchart of a power-on / off method for a rack server provided in an embodiment of this application;

[0016] Figure 2 This is a schematic diagram of the power supply system for a rack server provided in an embodiment of this application;

[0017] Figure 3 This is a logic diagram for counting the number of power management controllers in place, provided in an embodiment of this application.

[0018] Figure 4 This is a logic diagram of the interaction between a user terminal, PMC, MCU, and PSU provided in an embodiment of this application;

[0019] Figure 5This is a flowchart illustrating a power-on / off example of a rack server provided in an embodiment of this application. Detailed Implementation

[0020] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0021] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0022] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0023] In traditional server management, physical operations such as powering on and off servers are essential. When powering on a rack-wide server requires an administrator to physically be present in the data center, walk to the rack, and press the physical power button or manually unplug and plug the power cord. This method is acceptable when rack-wide servers are small and geographically dispersed, but it has become unsustainable with the increasing scale and geographical dispersion of data centers, the demand for automated operations and maintenance, unattended operation, and remote work. Therefore, there is an urgent need for a method that allows for remote powering on and off rack-wide servers.

[0024] Currently, rack-mount servers typically have multiple power supply frames, each with a corresponding power management controller and multiple power supply units. The power management controller manages the power supply units within its frame, and these controllers are distributed and do not communicate with each other. Therefore, when remotely controlling the power-on / off of a rack-mount server, power-on / off commands need to be sent to each power management controller individually. Each power management controller then sends corresponding instructions to the power supply units it controls, thus completing the power-on / off of the entire rack. However, this method of remotely controlling the power-on / off of rack-mount servers has the following drawbacks: First, sending power-on / off commands to multiple power management controllers must be simultaneous or at very short intervals. If the interval between sending power-on / off commands to multiple power management controllers is long, there will be inconsistencies in the power-on / off sequence of all power supply units. When power units fail, some units may have already failed while others remain active. If some units fail first, the remaining units may not have enough power to supply all server nodes, causing an abnormal power-down of the entire rack server. Subsequently, the rack server cannot power on automatically and must be powered on in-person at the data center. Conversely, when power units fail to fail, some units may fail, causing all server nodes to power on simultaneously. If the already active units lack sufficient power, this can also lead to an abnormal power-down, preventing the rack server from powering on automatically and requiring in-person power-on at the data center. Secondly, if only one power management controller is accidentally sent a power-on / off command, it can also cause the rack server to fail to power on after a failure. In this case, all power units managed by that controller will fail first and then power on. However, after the power supply unit is powered down, the power supply units in other power racks continue to supply power. Since some power supply units are no longer providing power, the total power is insufficient to power all server nodes normally, ultimately leading to abnormal power-down of the entire rack server and its inability to automatically power on. It is evident that this method of remotely controlling the power-up and power-down of rack servers has the following problems: the time interval requirements for power-up and power-down commands sent by the user to multiple power management controllers are extremely stringent; improper user operation or asynchronous power-up and power-down of power supply units can introduce power instability issues, leading to abnormal power-down of the entire rack server and its inability to automatically power on. In view of this, this application provides a method for powering up and down a rack server and a power supply system for rack servers.

[0025] Figure 1This is a flowchart illustrating a power-on / off method for a rack server according to an embodiment of this application. This method can be executed by a power-on / off controller in the rack server's power supply system. The power supply system for the rack server includes a power-on / off controller and multiple power supply frames, each power supply frame including a power management controller and a power supply unit.

[0026] Specifically, the power-on / off controller can be any device capable of executing the power-on / off method for the entire rack server, such as a microcontroller unit (MCU), but is not limited to this.

[0027] Specifically, a power supply frame is a modular hardware unit in a rack-mount server used for centralized provisioning, distribution, and management of power. It typically includes a power management controller and multiple power supply units, providing unified power to multiple nodes within the rack-mount server. The specific number of power supply frames in the power supply system can be set by those skilled in the art according to actual conditions, and is not limited here.

[0028] Specifically, the power management controller can be any device that can control the power supply units in its power box to power on and off, such as a powershelf management controller (PMC), but it is not limited to this.

[0029] Specifically, the exact number of power supply units in each power supply frame can be set by those skilled in the art according to the actual situation, and is not limited here. In addition, the power-on / off controller can be any device capable of supplying power to the server, such as a power supply unit (PSU), but is not limited to this.

[0030] For example, Figure 2 This is a schematic diagram of the power supply system for a rack-mount server provided in an embodiment of this application. Figure 2 As shown, an MCU is deployed on a rack server, and the MCU is deployed at the center of its circuit board (or multiple PMCs are distributed on both sides of the MCU). Hardware connections are established with multiple PMCs, and each PMC manages the PSUs in its power supply frame.

[0031] like Figure 1 As shown, the method provided in this embodiment includes the following steps:

[0032] S110, Receive command reception notification sent by power management controller, wherein the command reception notification is sent by power management controller to power-on / off controller in response to power-on / off command sent by user terminal.

[0033] In this embodiment of the application, when a user wants to power on or off the rack server, the user terminal can remotely send a power-on or power-off command to the power management controller. After receiving the power-on or power-off command, the power management controller can send a command receiving notification to the power-on or power-off controller in the power supply system.

[0034] Specifically, the user terminal can be any device capable of sending power-on / off commands to the power management controller in response to user operations; there are no limitations on this. Furthermore, the power management controller and the power-on / off controller can pre-agree on the information to be exchanged, such as command reception notifications, ID reporting notifications, power-on / off instructions, power-on / off failure notifications, first confirmation notifications, second confirmation notifications, remaining operation time prompts, and a list of missing power management controllers, but are not limited to these.

[0035] S120. Receive the notification according to the command and determine whether it is necessary to power on or off the entire rack server.

[0036] In some embodiments, determining whether the rack server needs to be powered on or off based on the command receiving notification includes: detecting whether the command receiving notification includes a power-on / off identifier for the rack server; if the command receiving notification includes a power-on / off identifier for the rack server, determining that the rack server needs to be powered on or off.

[0037] In this embodiment, the power-on / off command can include a target field. A value of 1 in the target field indicates that the power-on / off command applies to all power units within the rack service (i.e., powering on / off the rack server). A value of 0 in the target field indicates that the power-on / off command applies to the power units managed by the power management controller that received the command. Upon receiving the power-on / off command, the power management controller can detect the value in the target field. If the value is the first value, it can include the rack server power-on / off identifier in the command reception notification. Thus, when the power management controller detects the rack server power-on / off identifier in the command reception notification, it can determine that the rack server needs to be powered on / off. If the value is the second value, the command reception notification can include power-on / off identifiers for some power units or simply omit the rack server power-on / off identifier. Thus, when the power-on / off management controller detects that the command reception notification carries power-on / off identifiers for some power units or does not carry power-on / off identifiers for the entire rack server, it can determine that it only needs to power on / off the power units managed by the power management controller that received the power-on / off command.

[0038] Specifically, when a user wants to power on or off the rack server, the user can remotely send a "power-on / off command with the value of the first value in the target field" to at least one power management controller, so that at least one power management controller can send a command receiving notification carrying the rack server's power-on / off identifier to the power-on / off controller.

[0039] Understandably, by detecting whether the rack server's power-on / off status is included in the received command notification, the system determines whether the rack server needs to be powered on or off. This eliminates the need for users to remotely send power-on / off commands to all power management controllers from their client. Even if users do send such commands, the process doesn't require sending them to all controllers within a short time interval. This simplifies the process for users remotely powering on and off the rack server.

[0040] In other embodiments, determining whether the rack server needs to be powered on or off based on the command receiving notification includes: counting the first total number of command receiving notifications received within the current timing period, wherein the current timing period refers to the time period extending backward by a first preset duration from the current timing start time, and the current timing start time refers to the moment when the first command receiving notification is received after the end of the previous timing period; if the first total number meets a preset condition at the end of the current timing period, it is determined that the rack server needs to be powered on or off.

[0041] In this embodiment, after the rack server is powered on, when the power-on / off controller receives the first command reception notification, the moment of receiving the first command reception notification is taken as the current timing start time corresponding to the current timing period, and timing begins. Timing ends after a first preset duration. Similarly, after the previous timing period ends, when the power-on / off controller receives the first command reception notification, the moment of receiving the first command reception notification is taken as the current timing start time corresponding to the current timing period, and timing begins. Timing ends after a first preset duration. It should be noted that the specific value of the first preset duration can be set by those skilled in the art according to actual conditions, and is not limited here. For example, the first preset duration can be any value between 40 and 80 seconds, but is not limited to this.

[0042] In some examples, the initial value of the first total for each timing period is 0. The first total number of command reception notifications received within the current timing period is counted, including: for each command reception notification received by the power-on / off controller within the current timing period, the first total number is incremented by 1.

[0043] In other examples, the initial value of the first total for each timing period is 0. The first total number of command reception notifications received within the current timing period is counted, including: within the current timing period, for each command reception notification received by the power-on / off controller, the power management controller ID carried in the command reception notification is extracted. If no command reception notification is received from the power management controller corresponding to the power management controller ID within the current timing period, the first total number is incremented by 1.

[0044] In some other examples, the initial value of the first total for each timing period is 0. The first total number of command reception notifications received within the current timing period is counted, including: within the current timing period, each time the power-on / off controller receives a command reception notification, the link address of the power management controller is obtained. If no command reception notification is received from the power management controller corresponding to the link address within the current timing period, the first total number is incremented by 1.

[0045] In some examples, the preset condition is that the first total number is equal to the second total number of power management controllers currently in place.

[0046] Optionally, the method further includes: periodically counting the number of power management controllers in place after the rack server is powered on, to obtain a second total.

[0047] For example, Figure 3 This is a logic diagram for counting the number of power management controllers in place, provided in an embodiment of this application. Figure 3 As shown, after the rack server is powered on, all power management controllers (such as PMC0-PMC3) can determine their own power management controller ID based on the GPIO signal, and actively and periodically send their own power management controller ID to the power-on / off controller (such as MCU). If the power management controller ID is carried in the ID reporting notification, the power-on / off controller can establish or update the mapping relationship between the power management controller ID corresponding to the power management controller and the link address of the power management controller ID based on the received ID reporting notification. At the same time, the power-on / off controller can also calculate the number of power management controllers in place (i.e., the second total number).

[0048] Understandably, by periodically counting the number of power management controllers in place, the second total count can be made to match the actual number of power management controllers in place. This helps to accurately determine whether the entire rack server needs to be powered on or off.

[0049] Understandably, the decision to power on / off the entire rack server is made only when the first total number equals the second total number of currently in-place power management controllers. This simplifies the logic for determining whether power on / off the entire rack server is necessary, and helps to reduce the development cycle of power-on / off methods for rack servers.

[0050] In other examples, the preset condition is that the first total number is greater than the second total number of currently in-place power management controllers as a percentage of the first total number, where the preset percentage threshold is positively correlated with the third number of server nodes in-place.

[0051] Understandably, the system determines whether to power on or off the entire rack server only when the first set of preset conditions is met. This prevents the entire rack server from being powered on or off even if a user accidentally sends a power-on / off command to only one power management controller, thus avoiding power instability issues. Furthermore, when a user sends power-on / off commands to multiple power management controllers, the time interval does not need to be limited to a few seconds; it only needs to be completed within the first preset duration. This simplifies the process for users to remotely power on and off the entire rack server.

[0052] S130. If so, simultaneously send power-on / off commands to each power management controller in the rack server, so that each power management controller controls the corresponding power unit to power off first and then power on.

[0053] Specifically, if not, no power-on / off commands will be sent to any power management controller in the rack server.

[0054] Specifically, "simultaneously" here refers to the timing difference between sending power-on / off commands to each power management controller being less than a set synchronization threshold. It should be noted that the specific value of the synchronization threshold can be set by those skilled in the art according to actual conditions, and is not limited here. For example, the synchronization threshold can take any value between 0 and 5 seconds, but is not limited to this.

[0055] For example, Figure 4 This is a logic diagram of the interaction between a user terminal, PMC, MCU, and PSU provided in an embodiment of this application. Figure 5 This is a flowchart illustrating a power-on / off example of a rack-mount server provided in an embodiment of this application. Figure 4 and Figure 5As shown, when a user needs to remotely power on / off the rack server, they only need to send power-on / off commands to all power management controllers (such as PMCs) within a first preset duration (e.g., 60 seconds). For each power management controller, upon receiving the power-on / off command, it sends a command reception notification to the power-on / off controller (such as the MCU), informing it that it has received the command. After receiving the first command reception notification within the current time period, the power-on / off controller starts a timer for the first preset duration. Furthermore, upon receiving the command reception notification from the power management controller, the power-on / off controller determines the power management controller ID based on the sending address and sets the power-on / off flag of that power management controller to 1. After the timer expires, if the power-on / off flags of all in-situ power management controllers are set to 1, it indicates that all in-situ power management controllers have received the power-on / off command. At this point, the power-on / off controller processes the command with the highest priority, sending power-on / off commands to all in-situ power management controllers simultaneously. During initialization, the power management controller listens for power-on / off commands sent by the power-on / off controllers. Upon receiving a command, it processes it with the highest priority, sending a power-on / off notification to all power units (such as PSUs) within the power supply rack. Upon receiving the notification, each power unit initially cuts off its output current and resumes power supply after a few seconds. If the user does not send power-on / off commands to all in-situ power management controllers within the first preset time period, after the timer expires, the power-on / off flags of all in-situ power management controllers will not all be set to 1. The power management controllers will not receive power-on / off commands, and the rack-wide server will not experience abnormal power supply issues due to remote power-on / off. Furthermore, the power-on / off controller sends a power-on / off failure notification to the power management controllers and clears the power-on / off flags of all power management controllers to 0.

[0056] In this embodiment, when a user wants to power on or off a rack server, they can remotely send a power-on / off command to the power management controller in the rack server's power supply system via a user terminal. Upon receiving the command, the power management controller sends a command reception notification to the power-on / off controller in the power supply system. After determining that the rack server needs to be powered on or off based on the command reception notification, the power-on / off controller simultaneously sends power-on / off instructions to each power management controller within the rack server. This allows each power management controller to control its corresponding power unit to power off first and then power on, thus achieving remote control of the rack server's power-on / off. Therefore, this application can remotely power on and off rack servers. Furthermore, because the power-on / off controller can simultaneously send power-on / off instructions to each power management controller within the rack server, each power management controller can simultaneously control its corresponding power unit to power off first and then power on. This ensures that the power-on / off of each power unit in the rack server is essentially synchronized, thereby improving the problem of power supply anomalies that easily occur when rack servers are powered on or off.

[0057] In another embodiment of this application, after receiving a command reception notification sent by the power management controller, the method further includes: sending a first confirmation notification to the power management controller that sent the command reception notification, so that the power management controller sends a second confirmation notification to the user terminal, so that the user terminal displays the identification information of the power management controller that has not sent a second confirmation notification within the current time period.

[0058] In this embodiment, after receiving a command reception notification from the power management controller, the power-on / off controller sends a first confirmation notification to the power management controller, informing it that the command reception notification has been received. Then, the power management controller sends a second confirmation notification to the user terminal, informing it that it has successfully informed the power-on / off controller that the power-on / off command has been received. Thus, the user terminal can display in real-time the identification information of power management controllers that have not sent a second confirmation notification within the current time period. This prompts the user to specify which power management controllers to send power-on / off commands to, effectively avoiding duplicate power-on / off commands to the same power management controller or omitting power-on / off commands to certain power management controllers.

[0059] In another embodiment of this application, after receiving the command reception notification sent by the power management controller, the method further includes: if the first total does not meet the preset condition after a second preset time period from the current timing start time, sending a remaining operation time prompt to the target power management controller so that the target power management controller forwards the remaining operation time prompt to the user terminal so that the user terminal displays the remaining operation time prompt, wherein the second preset time period is less than the first preset time period.

[0060] In this embodiment, the power-on / off controller starts timing from the current start time (i.e., the time when the first command reception notification is received within the current timing period), counts for a second preset duration, and then checks whether the first total count meets a preset condition. If not, it sends a remaining operation time prompt (carrying the difference between the first and second preset durations) to the target power management controller. The target power management controller can then forward the remaining operation time prompt to the user terminal. In this way, the user terminal can display the remaining operation time prompt, prompting the user to promptly send power-on / off commands to the power management controller that has not yet sent power-on / off commands, thereby improving the success rate of remotely controlling the power-on / off of the rack server.

[0061] In some examples, the target power management controller is selected from candidate power management controllers, which are those that have sent command reception notifications within the current timing period; that is, the senders of command reception notifications received within the current timing period. This increases the probability that the power-on / off management controller successfully sends the remaining operation time indicator to the target power management controller, thereby increasing the probability that the remaining operation time indicator is successfully displayed on the user's device.

[0062] In other examples, the target power management controller is either pre-specified by the user or randomly selected from all power management controllers.

[0063] It should be noted that the specific value of the second preset duration can be set by those skilled in the art according to the actual situation, and is not limited here. For example, the ratio of the second preset duration to the first preset duration can be arbitrarily taken within the range of 0.5 to 0.8, but is not limited thereto.

[0064] In another embodiment of this application, the method further includes: if the first total does not meet a preset condition at the end of the current time period, sending a list of missing power management controllers to the target power management controller, so that the target power management controller forwards the list of missing power management controllers to the user terminal, so that the user terminal displays the list of missing power management controllers, wherein the list of missing power management controllers includes identification information of at least one missing power management controller, and the missing power management controller refers to a power management controller that has not received a power-on / off command during the current time period; receiving a command reception notification sent by the missing power management controller; counting a third total of command reception notifications received during the new current time period; if the sum of the first total and the third total meets a preset condition at the end of the new current time period, determining that the entire rack server needs to be powered on / off; and simultaneously sending power-on / off commands to each power management controller, so that each power management controller controls the corresponding power unit to power off first and then power on.

[0065] Specifically, the identification information of the missing power management controller may include its DI and / or link address, but is not limited to this.

[0066] For a detailed understanding of the target power management controller, please refer to the previous text, which will not be repeated here.

[0067] In this embodiment, if the first total number does not meet a preset condition at the end of the current time period, the power-on / off management controller can summarize the power management controllers that did not receive power-on / off commands during the current time period, thereby generating a list of missing power management controllers, and then sending the list of missing power management controllers to the target management controller. The target management controller can forward the list of missing power management controllers to the user terminal so that the user terminal can display the list of missing power management controllers. In this way, the user can remotely operate the user terminal to resend power-on / off commands to the missing power management controllers. After receiving the power-on / off commands, the missing power management controllers send a command receiving notification to the power-on / off management controller. After receiving the first resent power-on / off command, the power-on / off management controller starts a new current time period. If the sum of the first total number and the third total number meets a preset condition at the end of the new current time period, it is determined that the entire rack server needs to be powered on or off. At this time, power-on / off commands are sent to each power management controller simultaneously, so that each power management controller controls the corresponding power unit to power off first and then power on. In this way, users can simply send power-on / off commands to the power management controller remotely through the user terminal during the new time period, without having to send the commands again to the power management controller that sent them during the previous time period, thus improving the user experience.

[0068] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0069] Embodiments of this application also provide a power supply system for a rack server, including: a power-on / off controller and multiple power supply frames, each power supply frame including a power management controller and a power supply unit;

[0070] The power management controller is used to send commands to the power-on / off controller and receive notifications in response to power-on / off commands sent by the user.

[0071] The power-on / off controller is used to receive notifications based on commands to determine whether the rack server needs to be powered on or off. If so, it sends power-on / off commands to each power management controller so that each power management controller controls the corresponding power unit to power off first and then power on.

[0072] The power supply unit is used to power the entire rack of servers.

[0073] For a description of the features of the power supply system of the rack server in the corresponding embodiment, please refer to the relevant description of the power-on and power-off method of the rack server in the corresponding embodiment, which will not be repeated here.

[0074] Embodiments of this application also provide a power-on / off device for a rack-mount server, comprising:

[0075] The first receiving module is used to receive command receiving notifications sent by the power management controller. The command receiving notifications are sent by the power management controller to the power-on / off controller in response to the power-on / off command sent by the user.

[0076] The first determination module is used to determine whether the rack server needs to be powered on or off based on the command received notification.

[0077] The first sending module is used to send power-on / off commands to each power management controller in the rack server if it is determined that the rack server needs to be powered on or off, so that each power management controller controls the corresponding power unit to power off first and then power on.

[0078] For a description of the features of the power-on / off device of the rack server in the corresponding embodiment, please refer to the relevant description of the power-on / off method of the rack server in the corresponding embodiment, which will not be repeated here.

[0079] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above embodiments of the power-on / off method for a rack server.

[0080] Embodiments of this application also provide a computer-readable storage medium storing a computer program configured to execute the steps in any of the above embodiments of the power-on / off method for a rack server.

[0081] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0082] The embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above embodiments of the power-on / off method for a rack server.

[0083] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above embodiments of the power-on / off method for a rack server.

[0084] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0085] The power-on / off method and power supply system for a rack-mount server provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to help understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for powering on and off a rack-mount server, characterized in that, A power-on / off controller for a power supply system used in a rack-mount server, the power supply system further comprising: multiple power supply frames, each power supply frame including a power management controller and a power supply unit, wherein the method includes: Receive a command receiving notification sent by the power management controller, wherein the command receiving notification is sent by the power management controller to the power-on / off controller in response to a power-on / off command sent by the user terminal; Based on the command, a notification is received to determine whether the rack server needs to be powered on or off. If so, power-on / off commands are sent simultaneously to each of the power management controllers in the rack server, so that each power management controller controls the corresponding power unit to power off first and then power on. After receiving the command reception notification sent by the power management controller, the method further includes: If, after a second preset duration from the current timing start time, the first total does not meet the preset condition, a remaining operation time prompt is sent to the target power management controller, so that the target power management controller forwards the remaining operation time prompt to the user terminal, so that the user terminal displays the remaining operation time prompt. Here, the current timing start time refers to the moment when the first command receiving notification is received after the end of the previous timing period, the first total is the total number of command receiving notifications received within the current timing period, and the current timing period refers to the time period extending backward by a first preset duration from the current timing start time, where the second preset duration is less than the first preset duration.

2. The power-on / off method for a rack-mount server according to claim 1, characterized in that, The step of receiving a notification based on the command to determine whether the rack server needs to be powered on or off includes: Detect whether the command receiving notification includes the power-on / off identifier of the rack server; If the command receiving notification includes the power-on / off identifier of the rack server, it is determined that the rack server needs to be powered on / off.

3. The power-on / off method for a rack-mount server according to claim 1, characterized in that, The step of receiving a notification based on the command to determine whether the rack server needs to be powered on or off includes: Calculate the first total number of command reception notifications received within the current time period; If the first total number meets the preset condition at the end of the current time period, it is determined that the rack server needs to be powered on or off.

4. The power-on / off method for a rack-mount server according to claim 3, characterized in that, The preset condition is that the first total number is equal to the second total number of the power management controllers currently in place.

5. The power-on / off method for a rack-mount server according to claim 4, characterized in that, Also includes: After the rack server is powered on, the number of power management controllers in place is periodically counted to obtain the second total number.

6. The power-on / off method for a rack-mount server according to claim 3, characterized in that, After receiving the command reception notification sent by the power management controller, the method further includes: The power management controller that sent the command to receive the notification sends a first confirmation notification, so that the power management controller sends a second confirmation notification to the user terminal, so that the user terminal displays the identification information of the power management controller that did not send the second confirmation notification within the current time period.

7. The power-on / off method for a rack-mount server according to claim 3, characterized in that, Also includes: If the first total number does not meet the preset condition at the end of the current time period, a list of missing power management controllers is sent to the target power management controller, so that the target power management controller forwards the list of missing power management controllers to the user terminal, so that the user terminal displays the list of missing power management controllers. The list of missing power management controllers includes the identification information of at least one missing power management controller, which refers to a power management controller that did not receive the power-on / off command during the current time period. Receive the command reception notification sent by the missing power management controller; The third total number of command reception notifications received within the new current time period is counted; If the sum of the first total and the third total satisfies the preset condition at the end of the new current time period, it is determined that the rack server needs to be powered on or off. Simultaneously, the power-on / off commands are sent to each of the power management controllers, so that each of the power management controllers controls the corresponding power unit to power off first and then power on.

8. The power-on / off method for a rack-mount server according to claim 6 or 7, characterized in that, The target power management controller is selected from the candidate power management controllers, which are power management controllers that have sent the command to receive the notification during the current time period.

9. A power supply system for a rack-mount server, characterized in that, include: A power-on / off controller and multiple power supply frames, each of the power supply frames including a power management controller and a power supply unit; The power management controller is used to send a command receiving notification to the power-on / off controller in response to the power-on / off command sent by the user terminal; The power-on / off controller is used to receive a notification based on the command to determine whether the rack server needs to be powered on or off. If so, it sends power-on / off commands to each of the power management controllers so that each power management controller controls the corresponding power unit to power off first and then power on. The power supply unit is used to supply power to the rack server; The power-on / off controller is further configured to, after receiving the command reception notification sent by the power management controller, if the first total does not meet the preset condition after a second preset time period from the current timing start time, send a remaining operation time prompt to the target power management controller, so that the target power management controller forwards the remaining operation time prompt to the user terminal, so that the user terminal displays the remaining operation time prompt. Here, the current timing start time refers to the moment when the first command reception notification is received after the end of the previous timing period; the first total is the total number of command reception notifications received within the current timing period; the current timing period refers to the time period extending backward by a first preset time period from the current timing start time; and the second preset time period is less than the first preset time period.

Images