US-12619446-B2 - Systems and methods to identify peer nodes in a multi-node enclosure

US12619446B2US 12619446 B2US12619446 B2US 12619446B2US-12619446-B2

Abstract

Systems and methods to identify peer nodes in a multi-node enclosure are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a baseboard management controller (BMC) or a Datacenter-Secure Control Module (DC-SCM); and a memory coupled to or integrated with the BMC or DC-SCM, where the memory includes program instructions stored thereon that, upon execution by the BMC or DC-SCM, cause the IHS to: obtain configuration information associated with a first compute node of a multi-node enclosure; write the configuration information associated with the first compute node to a shared storage device that is accessible to other compute nodes of the multi-node enclosure; and obtain other configuration information associated with one or more other compute nodes of the multi-node enclosure from the shared storage device.

Inventors

Douglas E. Messick
Kyle E. Cross
BINAY A. KURUVILA
Thomas Foxworth Archer

Assignees

DELL PRODUCTS L.P.

Dates

Publication Date: 20260505
Application Date: 20240125

Claims (17)

1 . An Information Handling System (IHS), comprising: a baseboard management controller (BMC) or a Datacenter-Secure Control Module (DC-SCM); and a memory coupled to or integrated with the BMC or DC-SCM, wherein the memory comprises program instructions stored thereon that, upon execution by the BMC or DC-SCM, cause the IHS to: obtain configuration information associated with a first compute node of a multi-node enclosure; identify a location of the first compute node within the multi-node enclosure; write the configuration information associated with the first compute node to a memory location of a shared storage device that is accessible to other compute nodes of the multi-node enclosure, wherein the memory location is determined, based, at least in part, on the identified location of the first compute node; and obtain other configuration information associated with one or more other compute nodes of the multi-node enclosure from the shared storage device.
2 . The IHS of claim 1 , wherein each node of the multi-node enclosure writes configuration information to a different memory location of the shared storage device.
3 . The IHS of claim 1 , wherein to identify the location of the first compute node within the multi-node enclosure, the program instructions further cause the IHS to: obtain a bus address of a first hot swap controller (HSC) associated with the first compute node; and determine a physical location identifier of the first compute node based, at least in part, on the bus address of the first HSC.
4 . The IHS of claim 3 , wherein the bus address is an address of an Inter-Integrated Circuit (I 2 C) bus.
5 . The IHS of claim 3 , wherein to determine the physical location identifier of the first compute node, the program instructions further cause the IHS to: use a pre-programmed table or map to match the bus address of the first HSC to the physical location identifier of the first compute node.
6 . The IHS of claim 1 , wherein the shared storage device is located on a power distribution board (PDB) of the multi-node enclosure.
7 . The IHS of claim 6 , wherein the configuration information associated with the first compute node is written to the shared storage device via an Inter-Integrated Circuit (I 2 C) bus between the PDB and the BMC or DC-SCM.
8 . The IHS of claim 6 , wherein the PDB further comprises a service indicator component, and wherein the program instructions further cause the IHS to: determine that the first compute node requires service; identify a location of the first compute node within the multi-node enclosure; and provide to the service indicator component of the PDB the location of the first compute node.
9 . The IHS of claim 8 , wherein the service indicator component comprises at least one of: an e-reader, an LED indicator, an electro-mechanical motor, or an unpowered RFID reader.
10 . The IHS of claim 1 , wherein the BMC or DC-SCM is associated with the first compute node.
11 . The IHS of claim 1 , wherein the shared storage device is an electrically erasable programmable read-only memory (EEPROM).
12 . The IHS of claim 1 , wherein a first host processor module (HPM) comprises the first compute node, and wherein the configuration information comprises at least one of: a physical location of the first HPM, a serial number of the HPM, a serial number of the BMC or DC-SCM, a unique identifier of the HPM, a unique identifier of the BMC or DC-SCM, a model number of the HPM, a model number of the BMC or DC-SCM, a service tag of the HPM, or a service tag of the BMC or DC-SCM.
13 . The IHS of claim 1 , wherein the program instructions further cause the IHS to: periodically access the shared storage device to check for updates to the other configuration information.
14 . One or more non-transitory computer-readable storage media storing program instructions that when executed on or across one or more processors of an Information Handling System (IHS), cause the one or more processors to: obtain configuration information associated with a first compute node of a multi-node enclosure; identify a location of the first compute node within the multi-node enclosure; write the configuration information associated with the first compute node to a memory location of a shared storage device that is accessible to other compute nodes of the multi-node enclosure, wherein the memory location is determined, based at least in part, on the identified location of the first compute node; and obtain other configuration information associated with one or more other compute nodes of the multi-node enclosure from the shared storage device.
15 . The one or more non-transitory computer-readable storage media of claim 14 , wherein to identify the location of the first compute node within a multi-node enclosure, the program instructions further cause the one or more processors to: obtain a bus address of a first hot swap controller (HSC) associated with the first compute node; and determine a physical location identifier of the first compute node based, at least in part, on the bus address of the first HSC.
16 . A method, comprising: obtaining, by a baseboard management controller (BMC) or a Datacenter-Secure Control Module (DC-SCM) of a first compute node of a multi-node enclosure, configuration information associated with the first compute node; identifying, by the BMC or DC-SCM, a location of the first compute node within the multi-node enclosure; writing, by the BMC or DC-SCM, the configuration information associated with the first compute node to a memory location of a shared storage device that is accessible to other compute nodes of the multi-node enclosure, wherein the memory location is determined based at least in part on the identified location of the first compute node; and obtaining, by the BMC or DC-SCM, other configuration information associated with one or more other compute nodes of the multi-node enclosure from the shared storage device.
17 . The method of claim 16 , wherein identifying the location of the first compute node within the multi-node enclosure further comprises: obtaining, by the BMC or DC-SCM, a bus address of a first hot swap controller (HSC) associated with the first compute node; and determining, by the BMC or DC-SCM, a physical location identifier of the first compute node based, at least in part, on the bus address of the first HSC.

Description

FIELD This disclosure relates generally to Information Handling Systems (IHSs), and more specifically, to systems and methods to identify peer nodes in a multi-node enclosure. BACKGROUND As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store it. One option available to users is an Information Handling System (IHS). An IHS generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, IHSs may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. Variations in IHSs allow for IHSs to be general or configured for a specific user or specific use, such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, IHSs may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems. Groups of IHSs can be housed in server racks of data centers. A data center is a building, a dedicated space within a building, or a group of buildings used to house computer systems and associated components, such as telecommunications and storage systems. Since IT operations are crucial for business continuity, it generally includes redundant or backup components and infrastructure for power supply, data communication connections, environmental controls (e.g., air conditioning, fire suppression), and various security devices. A large data center is an industrial-scale operation using as much electricity as a small town. A server rack, or simply “rack”, is a frame or enclosure, with one or more dimensions typically standardized, for mounting multiple electronic equipment modules. Each module has a front panel that typically has a standardized width, which sometimes is 19 inches wide, for example. The standardized width (e.g., 19-inches) dimension includes the edges or ears that protrude from each side of the equipment, allowing the module to be fastened to the rack frame with screws or bolts. Common uses include computer servers, telecommunications equipment and networking hardware, audiovisual production gear, music production equipment, and scientific equipment. Equipment designed to be placed in a rack is typically described as rack-mount, rack-mount instrument, a rack-mounted system, a rack-mount chassis, subrack, rack cabinet, rack-mountable, or occasionally simply shelf. Each rack-mountable equipment module has a front panel that is typically a standardized width, (e.g., 19 inches wide). The standardized width can include the edges or ears that protrude from each side of the equipment, allowing the module to be fastened to the rack frame with screws or bolts. The height of the electronic modules is also typically standardized as multiples of 1.75 inches, which is one rack unit (“RU” or more typically just “U”). The industry-standard rack cabinet is 42 RU tall, however, 45 RU racks are also common. Racks (e.g., nineteen-inch racks) in two-post or four-post form hold most equipment in modern data centers, ISP facilities, and professionally designed corporate server rooms. They allow for dense hardware configurations without occupying excessive floor space or requiring shelving. Racks can also be used to house professional audio and video equipment, including amplifiers, effects units, interfaces, headphone amplifiers, and even small-scale audio mixers. A third common use for rack-mounted equipment is industrial power, control, and automation hardware. Rack-mountable equipment can be mounted by bolting or clipping its front panel to the server rack. Within the IT industry, it is common for network/communications equipment to have multiple mounting positions, including tabletop and wall mounting, so rack-mountable equipment will often feature L-brackets that must be screwed or bolted to the equipment prior to mounting in a server rack, such as for example, a 19-inch rack. SUMMARY Systems and methods to identify peer nodes in a multi-node enclosure are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a baseboard management controller (BMC) or a Datacenter-Secure Control Module (DC-SCM); and a memory coupled to or integrated with the BMC or DC-SCM, where the memory includes program instructions stored thereon that, upon execution by the BMC or DC-SCM, cause the IHS to: obtain configuration information associated with a first compute node of a multi-node enclosure; write the confi