A computer-implemented method enables global throttling of processing nodes in a rack-configured information handling system (RIHS). A rack-level management controller receives power-usage data and operating parameters associated with processing nodes within separately-controlled blocks of the RIHS. A power subsystem of the RIHS regulates an amount of power supplied to the processing nodes of the RIHS based on the power-usage data and operating parameters for the processing nodes and a total amount of available power for distribution within the RIHS. In response to detecting a condition that reduces the total amount of available power for distribution within the IHS, the management controller autonomously initiates global throttling of the processing nodes within the IHS to reduce power consumption by at least one of the processing nodes. The global throttling is completed via a signal transfer over a select Ethernet cable wire to connected block controllers that control the processing nodes.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A computer implemented method that implements rack-level power control of processing nodes in a rack-configured information handling system, the method comprising: receiving, at a rack-level management controller, power-usage data, operating parameters, and settings information associated with one or more processing nodes within one or more separately-controlled blocks of the information handling system (IHS); triggering a power subsystem of the IHS to regulate an amount of power supplied to one or more of the processing nodes of the information handling system based on the received information for the one or more processing nodes and a total amount of available power for distribution within the IHS; and in response to detecting a condition that reduces the total amount of available power for distribution within the IHS, the rack-level management controller autonomously initiating global throttling of power allocation within the IHS to reduce power consumption by at least one of the processing nodes via a separate block controller, wherein the global throttling is triggered by asserting a global throttle wire that is a subset of available wires within an Ethernet cable interconnecting the rack-level management controller and one or more block-level controllers; wherein the communication between the management controller and each of the one or more block controllers occurs over an Ethernet cable, which has a subset of individual signal wires assigned for general system and network communication between an infrastructure manager and the one or more block controllers, based in part on triggering commands received from the management controller; wherein at least one signal wire in the Ethernet cable is assigned as a global throttle wire for a specific connected one of the one or more block controllers to provide communication of a GTPR signal from the infrastructure controller to the specific block controller; and wherein at least one other signal wire in the Ethernet cable is assigned as a global reset wire for a specific connected one of the one or more block controllers to allow for expedient communication of a reset signal from the management controller via the infrastructure controller to the specific block controller.
A computer system manages power in a server rack. A central controller receives power usage and settings from individual blocks within the rack. The controller tells the power system how much power each block can use, based on available power. If the total available power drops, the central controller automatically throttles power to the blocks to reduce overall consumption. This throttling happens by sending a signal over a dedicated wire within a standard Ethernet cable that connects the central controller to block controllers managing individual nodes. Other wires in the cable handle normal communication and a global reset signal.
2. The method of claim 1 , further comprising: initializing the management controller during start up configuration of the IHS; establishing communication between the management controller, the power subsystem, and one or more block controllers that each control block-level operations of processing nodes within a corresponding block; retrieving power profile data for each block within the IHS, the power profile data comprising the power-usage data and settings information of the individual processing nodes within the particular block; generating a power allocation for each block based on the received power profile data; and triggering the power subsystem to supply power to each block and by extension to each of the nodes based on the power allocation for that block.
The power management system initializes by setting up the central controller, establishing communication with the power system and block controllers. It retrieves power profiles (usage and settings) for each block, then calculates a power allocation for each. The system then tells the power subsystem to provide power to each block based on its allocation. This allows fine-grained control over power distribution within the server rack (building on the method described in claim 1 where power is throttled via a dedicated ethernet wire).
3. The method of claim 1 , wherein the condition is one of a power supply unit (PSU) failure and an AC input power failure, and the method further comprises: determining which condition has occurred; in response to determining that the PSU failure has occurred, transmitting a signal to at least one of the block controllers to reduce power to at least one of the nodes, wherein an overall power is reduced by a first amount correlated to a loss of a PSU; and in response to determining that the AC input power failure has occurred, transmitting a signal to at least one of the block controllers to reduce power to at least one of the nodes, wherein an overall power is reduced by a second amount correlated to a loss of an AC input.
This system reduces power in response to specific failures (building on the method described in claim 1 where power is throttled via a dedicated ethernet wire). If a power supply unit fails or AC power is lost, the system determines which failure occurred. It then sends a signal to block controllers to reduce power to nodes. The amount of power reduced depends on the type of failure (e.g., losing a PSU reduces power by a set amount, and losing AC input reduces power by a different amount).
4. The method of claim 3 , further comprising: determining via at least one block controller, which processing nodes of the corresponding block are to be throttled in order to reduce power consumption by the corresponding block; and the at least one of the block controller subsequently throttling operations of the processing nodes that are to be throttled within the corresponding blocks.
This system intelligently chooses which nodes to throttle to save power (building on the methods described in claims 1 and 3 where power is reduced in response to system failures and throttled via a dedicated ethernet wire). Each block controller decides which processing nodes within its block should be throttled. The block controller then reduces the operation of those specific nodes to lower the overall power consumption of the block.
5. The method of claim 1 , further comprising: establishing a maximum power capacity for the information handing system; monitoring a total power usage and demand across the IHS; and in response to determining that a current power demand across the IHS is greater than the maximum power capacity, transmitting a signal to at least one of the block controllers to reduce power to at least one of the nodes.
The system monitors and limits overall power usage (building on the method described in claim 1 where power is throttled via a dedicated ethernet wire). The system defines a maximum power capacity for the entire server rack. It constantly monitors the total power demand across the rack. If the demand exceeds the capacity, the system sends signals to block controllers to reduce power to nodes, ensuring the rack doesn't exceed its power limit.
6. The method of claim 1 , wherein initiating global throttling of power allocation within the IHS to reduce power consumption by at least one of the processing nodes via an associated block controller comprises generating a signal on a global throttle wire allocated within each Ethernet cable directly connecting each block controller within the IHS with the management controller, wherein the block controllers within the IHS are pre-programmed to respond to an assertion of a signal on the global throttle wire by the management controller by immediately throttling operations of one or more processing nodes within a respective block being controlled by the block controller.
Power throttling is achieved by a dedicated signal line (building on the method described in claim 1). To throttle power, the central controller sends a signal on a specific "global throttle wire" within the Ethernet cable directly connecting each block controller. Block controllers are pre-programmed to respond to this signal by immediately reducing the operation of one or more processing nodes within their block, thus reducing power consumption.
7. The method of claim 1 , further comprising: in response to detecting that the overall thermal readings of the IHS are above a system thermal threshold, identifying at least one block drawing large amounts of power and contributing to higher than normal thermal threshold readings; and transmitting a signal to at least each block controller corresponding to the identified at least one block to reduce power consumption by the at least one node.
The system also manages power based on temperature (building on the method described in claim 1 where power is throttled via a dedicated ethernet wire). If the rack's overall temperature exceeds a threshold, the system identifies blocks drawing excessive power. It then signals the corresponding block controllers to reduce power consumption in their nodes, mitigating overheating.
8. The method of claim 1 , further comprising: determining whether the condition remains present after reducing power to at least one of the nodes; and in response to the condition remaining present, triggering at least one of the block controllers to shut down at least one of the nodes.
This system responds to power reduction failures (building on the method described in claim 1 where power is throttled via a dedicated ethernet wire). After reducing power to nodes, the system checks if the original problem (e.g., low available power) still exists. If the problem persists, the system instructs block controllers to completely shut down some nodes to further reduce power consumption.
9. The method of claim 1 , further comprising: determining whether at least one of an infrastructure manager or the block controllers are to be reset; in response to determining that at least one of the infrastructure manager or the block controllers are to be reset, generating a reset signal on a reset wire allocated within each Ethernet cable directly connecting the management controller with the infrastructure manager and the block controllers, wherein the reset signal triggers at least one of the infrastructure manager or the block controllers to reset.
The system includes a reset mechanism (building on the method described in claim 1 where power is throttled via a dedicated ethernet wire). If the system needs to reset the infrastructure manager or block controllers, it sends a reset signal on a dedicated "reset wire" within the Ethernet cable connecting the management controller to these components. This signal triggers the affected components to reset.
10. A rack-level power control system comprising: a rack-level management controller having a processor and a memory coupled to the processor via a system interconnect; a power subsystem communicatively coupled to the rack-level management controller; a cooling subsystem communicatively coupled to the rack-level management controller; one or more blocks communicatively coupled to the rack-level management controller, the blocks having at least one block controller communicatively coupled to the rack-level management controller and each of the blocks having one or more processing nodes; and an Ethernet cable connected between the rack-level management controller and at least one of the block controllers, wherein: at least one of the wires in the Ethernet cable allocated as a global throttle wire to provide communication of a global throttle power reduction signal from the rack-level management controller to at least one of the block controllers and at least one of the nodes allowing an immediate reduction in power usage by the processing nodes upon receipt of the global throttle power reduction signal; a subset of individual signal wires within the Ethernet cable is assigned for general system and network communication between an infrastructure manager and the one or more block controllers, based in part on triggering commands received from the management controller; and at least one other signal wire in the Ethernet cable is assigned as a global reset wire for a specific connected one of the one or more block controllers to allow for expedient communication of a reset signal from the management controller via the infrastructure controller to the specific block controller.
A rack-level power control system includes a central management controller with a processor and memory. It connects to a power subsystem and a cooling subsystem. It also connects to blocks of processing nodes, each block managed by a block controller. Ethernet cables connect the central controller to the block controllers. One wire in the Ethernet cable is dedicated to sending a "global throttle power reduction signal" to immediately reduce node power consumption. Other wires handle general communication and a global reset signal.
11. The rack-level power control system of claim 10 , further comprising: an infrastructure manager communicatively connected via the Ethernet cable between the rack-level management controller and at least one of the block controllers, the infrastructure manager comprising a switch communicatively coupled to an infrastructure controller.
The rack-level power control system from the previous description also includes an infrastructure manager connected via the Ethernet cable between the central controller and at least one block controller. The infrastructure manager includes a switch and an infrastructure controller. This allows for more complex communication and control within the rack.
12. The rack-level power control system of claim 11 , wherein the infrastructure controller selectively routes the global throttle power reduction signal via the Ethernet cable to at least one selected block controller.
In the rack-level power control system (building on the description in claims 10 and 11), the infrastructure controller can selectively route the global throttle power reduction signal to specific block controllers via the Ethernet cable. This allows for targeted power throttling of only certain blocks within the system.
13. The rack-level power control system of claim 11 , wherein the Ethernet cable further comprises: a rack-level Ethernet cable connected between the management controller and the infrastructure manager, the rack-level Ethernet cable having a first global throttle to provide communication of the global throttle power reduction signal from the rack-level management controller to the infrastructure manager; and at least one block level Ethernet cable connected between the infrastructure manager and at least one of the block controllers, the block level Ethernet cable having a second global throttle wire to provide communication of the global throttle power reduction signal from the infrastructure manager to at least one of the block controllers.
The Ethernet cabling in the rack-level power control system is split (building on the description in claims 10 and 11). There's a "rack-level" Ethernet cable between the central controller and the infrastructure manager, with a "first global throttle wire." Then, there's a "block-level" Ethernet cable between the infrastructure manager and block controllers, with a "second global throttle wire." This allows the infrastructure manager to selectively forward the throttle signal.
14. The rack-level power control system of claim 10 , wherein the power subsystem further comprises: at least one power supply unit communicatively coupled to the management controller, the management controller receiving power supply unit data and settings from the at least one power supply unit; and an AC switch connected to the at least one power supply unit to supply power to the at least one power supply unit, the AC switch communicatively coupled to the management controller, the management controller receiving AC power data and settings from the AC switch.
This power control system for a rack of equipment includes power supplies and an AC switch, both connected to a central controller that monitors their settings and data to manage power distribution.
15. The rack-level power control system of claim 14 , further comprising: at least one backup battery connected to at least one of the power supply units, wherein the management controller has firmware executing thereon that configures the rack-level management controller to: in response to determining that an AC input power failure has occurred, transmitting a signal to at least one of the block controllers to reduce power to at least one of the nodes in order to extend operating life of the backup battery.
This rack-level power control system includes backup batteries (building on the description in claim 14, which describes the power subsystem). If AC power fails, the system uses backup batteries. The management controller detects the AC power failure and signals block controllers to reduce node power to extend the battery life.
16. The rack-level power control system of claim 10 , wherein the block controller further comprises: a field programmable gate array that contains pre-determined processing node global throttle data designating at least one of the processing nodes to reduce power in response to receiving the global throttle power reduction signal.
The rack-level power control system's block controller uses an FPGA for throttling (building on the description in claim 10). The block controller contains a Field Programmable Gate Array (FPGA) that stores "global throttle data." This data pre-determines which processing nodes should reduce power when the block controller receives the global throttle power reduction signal, allowing for immediate and efficient power management.
17. The rack-level power control system of claim 10 , wherein the cooling subsystem further comprises: at least one temperature sensor that is communicatively coupled to the rack-level management controller, wherein the management controller has firmware executing thereon that configures the rack-level management controller to, in response to receiving a signal from a temperature sensor indicating that the overall thermal readings of the IHS are above a system thermal threshold: identify at least one block drawing large amounts of power and contributing to higher than normal thermal threshold readings; and transmit a signal to at least each block controller corresponding to the identified at least one block to reduce power consumption by the at least one node.
The cooling subsystem in the rack-level power control system includes temperature sensors (building on the description in claim 10). If a temperature sensor indicates that the rack is overheating, the management controller identifies blocks drawing excessive power. It then signals the corresponding block controllers to reduce power consumption in their nodes to lower the temperature.
18. The rack-level power control system of claim 10 , wherein the management controller has firmware executing thereon that configures the rack-level management controller to: in response to reducing power to at least one of the nodes, determine whether a condition that reduces the total amount of available power for distribution within the IHS remains; and in response to the condition remaining, trigger at least one of the block controllers to shut down at least one of the nodes.
The rack-level power control system detects and responds to persistent power issues (building on the description in claim 10). After reducing power to nodes, the management controller checks if the original power issue (e.g., low available power) is resolved. If not, it instructs block controllers to shut down nodes to further reduce power.
19. The rack-level power control system of claim 10 , wherein the management controller has firmware executing thereon that configures the rack-level management controller to: determine whether at least one of an infrastructure manager or the block controllers are to be reset; in response to determining that at least one of the infrastructure manager or the block controllers are to be reset, generate a reset signal on a reset wire allocated within each Ethernet cable directly connecting the management controller with the infrastructure manager and the block controllers, wherein the reset signal triggers at least one of the of the infrastructure manager or the block controllers to reset.
The rack-level power control system has a reset mechanism (building on the description in claim 10). The management controller can determine if the infrastructure manager or block controllers need to be reset. If so, it sends a reset signal over a dedicated wire in the Ethernet cable to trigger a reset of the affected components.
20. An information handling system (IHS) comprising: a rack having a plurality of block chasses; one or more blocks located within respective ones of the plurality of block chassis, the blocks having at least one block controller and each of the blocks having one or more processing nodes; a rack-level management controller having a processor a memory coupled to the processor via a system interconnect, the rack-level management controller communicatively coupled to the blocks, the block controllers and the processing nodes; a power subsystem communicatively coupled to the rack-level management controller; a cooling subsystem communicatively coupled to the rack-level management controller; and an Ethernet cable connected between the rack-level management controller and at least one of the block controllers, wherein: at least one of the wires in the Ethernet cable allocated as a global throttle wire to provide communication of a global throttle power reduction signal from the rack-level management controller to at least one of the block controllers and at least one of the nodes allowing an immediate reduction in power usage by the processing nodes upon receipt of the global throttle power reduction signal; a subset of individual signal wires within the Ethernet cable is assigned for general system and network communication between an infrastructure manager and the one or more block controllers, based in part on triggering commands received from the management controller; and at least one other signal wire in the Ethernet cable is assigned as a global reset wire for a specific connected one of the one or more block controllers to allow for expedient communication of a reset signal from the management controller via the infrastructure controller to the specific block controller.
An information handling system contains a server rack with multiple blocks of processing nodes, each block managed by a block controller. A central controller manages the blocks and their nodes. A power subsystem and cooling subsystem are connected. Ethernet cables connect the central controller to the block controllers. One wire is dedicated to sending a "global throttle power reduction signal" for immediate power reduction. Other wires handle general communication and a global reset signal.
21. The information handling system of claim 20 , further comprising: an infrastructure manager communicatively connected via the Ethernet cable between the rack-level management controller and at least one of the block controllers, the infrastructure manager comprising a switch communicatively coupled to an infrastructure controller.
The information handling system described in claim 20 also includes an infrastructure manager connected via the Ethernet cable between the central controller and at least one block controller. The infrastructure manager comprises a switch and an infrastructure controller.
22. The information handling system of claim 21 , wherein the infrastructure controller selectively routes the global throttle power reduction signal via the Ethernet cable to at least one selected block controller.
In the information handling system, the infrastructure controller can selectively route the global throttle power reduction signal (building on the descriptions in claims 20 and 21). This means power can be throttled to specific blocks via the Ethernet cable.
23. The information handling system of claim 21 , wherein the Ethernet cable further comprises: a rack-level Ethernet cable connected between the management controller and the infrastructure manager, the rack-level Ethernet cable having a first global throttle to provide communication of the global throttle power reduction signal from the rack-level management controller to the infrastructure manager; and at least one block level Ethernet cable connected between the infrastructure manager and at least one of the block controllers, the block level Ethernet cable having a second global throttle wire to provide communication of the global throttle power reduction signal from the infrastructure manager to at least one of the block controllers.
The information handling system's Ethernet cabling is split (building on the descriptions in claims 20 and 21). A rack-level cable connects the central controller to the infrastructure manager with a first throttle wire. Block-level cables connect the infrastructure manager to block controllers with a second throttle wire, enabling selective forwarding of the throttle signal.
24. The information handling system of claim 20 , wherein the power subsystem further comprises: at least one power supply unit communicatively coupled to the management controller, the management controller receiving power supply unit data and settings from the at least one power supply unit; and an AC switch connected to the at least one power supply unit to supply power to the at least one power supply unit, the AC switch communicatively coupled to the management controller, the management controller receiving AC power data and settings from the AC switch.
The information handling system's power subsystem (building on the description in claim 20) includes power supply units (PSUs) and an AC switch. The central controller receives data and settings from these components for monitoring and control.
25. The information handling system of claim 24 , further comprising: at least one backup battery connected to at least one of the power supply units, wherein the management controller has firmware executing thereon that configures the rack-level management controller to: in response to determining that an AC input power failure has occurred, transmitting a signal to at least one of the block controllers to reduce power to at least one of the nodes in order to extend operating life of the backup battery.
The information handling system also uses backup batteries (building on the description in claim 24). When AC power fails, the controller instructs block controllers to reduce node power to extend battery life.
26. The information handling system of claim 20 , wherein the block controller further comprises: a field programmable gate array that contains pre-determined processing node global throttle data designating at least one of the processing nodes to reduce power in response to receiving the global throttle power reduction signal.
The information handling system's block controller uses an FPGA for throttling (building on the description in claim 20). This FPGA stores throttle data that pre-determines which processing nodes to reduce power on when a global throttle signal is received.
27. The information handling system of claim 20 , wherein the cooling subsystem further comprises: at least one temperature sensor that is communicatively coupled to the rack-level management controller, wherein the management controller has firmware executing thereon that configures the rack-level management controller to: in response to receiving a signal from temperature sensor that the overall thermal readings of the IHS are above a system thermal threshold, identify at least one block drawing large amounts of power and contributing to higher than normal thermal threshold readings; and transmit a signal to at least each block controller corresponding to the identified at least one block to reduce power consumption by the at least one node.
The cooling subsystem in the information handling system (building on the description in claim 20) includes temperature sensors. If the rack overheats, the controller identifies high-power blocks and signals their block controllers to reduce node power to lower the temperature.
28. The information handling system of claim 20 , wherein the management controller has firmware executing thereon that configures the rack-level management controller to: in response to reducing power to at least one of the nodes, determine whether a condition that reduces the total amount of available power for distribution within the IHS remains; and in response to the condition remaining, trigger at least one of the block controllers to shut down at least one of the nodes.
The information handling system manages persistent power issues (building on the description in claim 20). After reducing power, the controller checks if the original issue is resolved. If not, it instructs block controllers to shut down nodes to further reduce power.
29. The information handling system of claim 20 , wherein the management controller has firmware executing thereon that configures the rack-level management controller to: determine whether at least one of an infrastructure manager or the block controllers are to be reset; in response to determining that at least one of the infrastructure manager or the block controllers are to be reset, generate a reset signal on a reset wire allocated within each Ethernet cable directly connecting the management controller with the infrastructure manager and the block controllers, wherein the reset signal triggers at least one of the of the infrastructure manager or the block controllers to reset.
The information handling system has a reset mechanism (building on the description in claim 20). If the infrastructure manager or block controllers need to be reset, the controller sends a reset signal over a dedicated wire in the Ethernet cable to trigger their reset.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
December 23, 2013
April 18, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.