Distributed intelligent platform management interface (D-IPMI) system and method thereof

Certain aspects direct a distributed Intelligent Platform Management Interface (D-IPMI) system. The system includes a computing device and a distributed management device. The distributed management device includes a first management device and at least one second management device physically separated from each other. A stack interface connects the first management device and the second management device to perform an internal communication between the first management device and the second management device. The first management device may be used to perform time critical functions related to the computing device, and the second management device may be used to perform non-critical functions. For example, the first management device may perform system power control of the computing device, monitor system components and obtaining system information of the computing device, and perform system communication with the computing device. The second management device may perform an external communication through the external interface.

FIELD

The present disclosure relates generally to baseboard management technology, and more particularly to distributed Intelligent Platform Management Interface (D-IPMI) systems and methods thereof.

BACKGROUND

Intelligent Platform Management Interface (IPMI) is an industry standard for system monitoring and event recovery. Currently, baseboard management controller (BMC) chips fully support the IPMI Specification version 2.0 (hereinafter the IPMI v2.0), which is publicly available from INTEL CORPORATION, and is incorporated herein by reference. The IPMI v2.0 provides a common message-based interface for accessing all of the manageable features in a compatible computer. However, with more IPMI based functionalities being put into the BMC, it becomes more challenging for all of the components running on the single BMC chip to meet the strict system requirements.

Therefore, an unaddressed need exists in the art to address the aforementioned deficiencies and inadequacies.

SUMMARY

Certain aspects of the disclosure direct to a distributed Intelligent Platform Management Interface (D-IPMI) system. In certain embodiments, the system includes a computing device and a distributed management device. The distributed management device includes a first management device, at least one second management device, and a stack interface connecting the first management device and the at least one second management device to perform an internal communication between the first management device and the second management device. The first management device includes a first processor, a system interface, and a first non-volatile memory storing first IPMI related computer executable code. The second management device includes a second processor, an external interface, and a second non-volatile memory storing second IPMI related computer executable code. The first IPMI related computer executable code, when executed at the first processor, is configured to perform a plurality of time critical functions related to the computing device; and perform the internal communication with the at least one second management device through the stack interface. The second IPMI related computer executable code, when executed at the second processor, is configured to: perform an external communication through the external interface; perform a plurality of non-critical functions related to the computing device; and perform the internal communication with the first management device through the stack interface.

In certain embodiments, the time critical functions related to the computing device includes: performing system power control of the computing device; monitoring system components of the computing device and obtaining system information of the computing device; and performing a system communication with the computing device through the system interface.

In certain embodiments, each of the first management device and the at least one second management device is a system on a chip (SoC) physically separated from each other.

In certain embodiments, the system interface is an IPMI standardized interface. In certain embodiments, the IPMI standardized interface includes a keyboard controller style (KCS) interface, a system management interface chip (SMIC) interface, and a block transfer (BT) interface.

In certain embodiments, the second IPMI related computer executable code, when executed at the second processor, is configured to perform the external communication with a remote computing device through the external interface.

In certain embodiments, the stack interface is an Inter-Integrated Circuit (I2C) interface, a system management bus (SMB) interface, or a local area network (LAN).

In certain embodiments, the second IPMI related computer executable code, when executed at the second processor, is further configured to: request the system information of the computing device from the first management device through the stack interface; and receive the requested system information of the computing device from the first management device through the stack interface.

In certain embodiments, the first processor is an external processor of the computing device and shared by the first management device, and the first non-volatile memory is a non-volatile memory of the computing device and shared by the first management device. In certain embodiments, the first IPMI related computer executable code is uploaded to the non-volatile memory of the computing device to form the first management device of the distributed management device in the computing device.

Certain aspects of the disclosure direct to a method for performing distributed Intelligent Platform Management Interface (D-IPMI) in a system. In certain embodiments, the method includes:

providing a distributed management device to a computing device, where the distributed management device includes:a first management device including a first processor, a system interface, and a first non-volatile memory storing first IPMI related computer executable code;at least one second management device including a second processor, an external interface, and a second non-volatile memory storing second IPMI related computer executable code; anda stack interface connecting the first management device and the at least one second management device to perform an internal communication between the first management device and the second management device;

performing, by the first IPMI related computer executable code executed at the first processor of the first management device, a plurality of time critical functions related to the computing device;

performing, by the second IPMI related computer executable code executed at the first processor of the at least one second management device, an external communication through the external interface;

performing, by the second IPMI related computer executable code executed at the second processor of the at least one second management device, a plurality of non-critical functions related to the computing device; and

performing the internal communication between the first management device and the at least one second management device through a stack interface.

In certain embodiments, the time critical functions related to the computing device includes: performing system power control of the computing device; monitoring system components of the computing device and obtaining system information of the computing device; and performing a system communication with the computing device through the system interface.

In certain embodiments, each of the first management device and the at least one second management device is a system on a chip (SoC) physically separated from each other.

In certain embodiments, the system interface is an IPMI standardized interface, and the IPMI standardized interface includes a keyboard controller style (KCS) interface, a system management interface chip (SMIC) interface, and a block transfer (BT) interface.

In certain embodiments, the at least one second management device is configured to perform the external communication with a remote computing device through the external interface.

In certain embodiments, the stack interface is an Inter-Integrated Circuit (I2C) interface, a system management bus (SMB) interface, or a local area network (LAN).

In certain embodiments, the method further includes:

requesting, by the second IPMI related computer executable code executed at the second processor of the at least one second management device, the system information of the computing device from the first management device through the stack interface; and

receiving, by the second IPMI related computer executable code executed at the second processor of the at least one second management device, the requested system information of the computing device from the first management device through the stack interface.

In certain embodiments, the first processor is an external processor of the computing device and shared by the first management device, and the first non-volatile memory is a non-volatile memory of the computing device and shared by the first management device. In certain embodiments, the method further includes: uploading the first IPMI related computer executable code to the non-volatile memory of the computing device to form the first management device of the distributed management device in the computing device.

Certain aspects of the disclosure direct to at least one non-transitory computer readable medium storing first Intelligent Platform Management Interface (IPMI) related computer executable code and second IPMI related computer executable code. The first IPMI related computer executable code, when executed at a first processor of a first management device of a distributed management device, is configured to: perform a plurality of time critical functions related to a computing device; and perform an internal communication with at least one second management device of the distributed management device through a stack interface. The second IPMI related computer executable code, when executed at a second processor of the at least one second management device of the distributed management device, is configured to: perform an external communication through an external interface; perform a plurality of non-critical functions related to the computing device; and perform the internal communication with the first management device through the stack interface. In certain embodiments, the second management device is physically separated from the first management device.

In certain embodiments, the time critical functions related to the computing device include: performing system power control of the computing device; monitoring system components of the computing device and obtaining system information of the computing device; and performing a system communication with the computing device through the system interface.

In certain embodiments, each of the first management device and the at least one second management device is a system on a chip (SoC) physically separated from each other.

In certain embodiments, the stack interface is an Inter-Integrated Circuit (I2C) interface, a system management bus (SMB) interface, or a local area network (LAN).

In certain embodiments, the second IPMI related computer executable code, when executed at the second processor, is further configured to: request the system information of the computing device from the first management device through the stack interface; and receive the requested system information of the computing device from the first management device through the stack interface.

In certain embodiments, the first processor is an external processor of the computing device and shared by the first management device, and the first non-volatile memory is a non-volatile memory of the computing device and shared by the first management device. In certain embodiments, the first IPMI related computer executable code is uploaded to the non-volatile memory of the computing device to form the first management device of the distributed management device in the computing device.

DETAILED DESCRIPTION

As used herein, “plurality” means two or more.

As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A or B or C), using a non-exclusive logical OR. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure.

As used herein, the term “headless system” or “headless machine” generally refers to the computer system or machine that has been configured to operate without a monitor (the missing “head”), keyboard, and mouse.

The term “interface”, as used herein, generally refers to a communication tool or means at a point of interaction between components for performing data communication between the components. Generally, an interface may be applicable at the level of both hardware and software, and may be uni-directional or bi-directional interface. Examples of physical hardware interface may include electrical connectors, buses, ports, cables, terminals, and other I/O devices or components. The components in communication with the interface may be, for example, multiple components or peripheral devices of a computer system.

The terms “chip” or “computer chip”, as used herein, generally refer to a hardware electronic component, and may refer to or include a small electronic circuit unit, also known as an integrated circuit (IC), or a combination of electronic circuits or ICs.

The terms “node” or “computing node”, as used herein, generally refer to a basic unit of computer systems. A node may be implemented by a physical device or a virtual device. For example, a computing device such as a personal computer, a laptop computer, a tablet or a mobile device may function as a node. A peripheral device such as a printer, a scanner or a system on chip (SoC) may also function as a node. A virtual device, such as a virtual machine (VM), may also function as a node. When defining nodes on the Internet, a node refers to a device or a data point having an IP address.

The term “cluster”, as used herein, generally refers to a set of loosely or tightly connected computing devices (or more precisely, computing nodes) that work together such that, in many respects, they can be viewed as a single system. The components of a cluster are usually connected to each other through a network, with each node of the cluster being set to perform certain tasks.

The present disclosure relates to computer systems. As depicted in the drawings, computer components may include physical hardware components, which are shown as solid line blocks, and virtual software components, which are shown as dashed line blocks. One of ordinary skill in the art would appreciate that, unless otherwise indicated, these computer components may be implemented in, but not limited to, the forms of software, firmware or hardware components, or a combination thereof.

One aspect of the present disclosure is directed to a distributed Intelligent Platform Management Interface (D-IPMI) system. As discussed above, with more IPMI based functionalities being put into the BMC, it becomes more challenging for all of the components running on the single BMC chip to meet the strict system requirements. In certain embodiments, for better performance, the D-IPMI system may include multiple management devices (such as multiple computer chips), in which one management devices maintains a certain subset of the BMC functionalities, and a different subset of the BMC functionalities may be offloaded to another management device. In other words, the D-IPMI system may include two or more split BMC stacks, which are physically separated as the multiple management devices, and each of the split BMC stacks may run on a separate processor in an individually separate management device. For example, one subset of the BMC functionalities may include system critical functionalities, such as functionalities related system power control, system component monitoring, system communication and time critical functions related to the host computer. The other subset of the BMC functionalities may include the rest of the complete BMC functionalities. Certain communication mechanisms between the management devices may be established between the different processors of the management devices, such that the BMC firmware portions running on each of the processor may collectively provide a single BMC stack representation to the external clients of the system. Thus, the workload of the system may be distributed among the management devices. Further, the system critical functionalities, which are generally time critical, may work within the given time constraints.

FIG. 1schematically depicts a D-IPMI system according to certain embodiments of the present disclosure. The system100is capable of providing BMC functionalities in a plurality of split BMC stacks, with one subset of the BMC functionalities including time critical functions, and the other subset of the BMC functionalities including the rest of the non-critical functions. As shown inFIG. 1, the system100includes a computing device110, a first management device120, and a second management device130. The first management device120and the second management device130, collectively, functions as a distributed management device140. In other words, the distributed management device140includes the first management device120and the second management device130. The first management device120is connected to the computing device via a system interface150. Further, the distributed management device140includes a stack interface160, which connects the first management device120and the second management device130. Moreover, the computing device110and the second management device130are communicatively interconnected by a network170. The network170may be a wired or wireless network, and may be of various forms, such as a public network and a private network. Examples of the network170may include, but not limited to, a local area network (LAN) or wide area network (WAN) including the Internet. In certain embodiments, two or more different networks170may be applied such that the computing device110and the second management device130may be respectively connected to one or more of the different networks170. In certain embodiments, for example, the system100may include three types of network170: a heartbeat network, the Internet, and a virtual machine network. A remote computing device180is also connected to the network170.

The computing device110serves as a host computer of the distributed management device140. In certain embodiments, the computing device110may be a general purpose computer server system or a headless server. Examples of the computing device110may include, but not limited to, a personal computer, a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet device, a mobile device, or any other computing devices that may function as the host computer. In certain embodiments, the computing device110may function as a server or a client in a client-server system.

In certain embodiments, the computing device110may include necessary hardware and software components to perform certain predetermined tasks. For example, as shown inFIG. 1, the computing device110has a processor112, a memory114, a storage device116, and any other necessary hardware components enabling the computing device110to operate.

The processor112is configured to control operation of the computing device110. In certain embodiments, the processor112may be a central processing unit (CPU). The processor112can execute any computer executable code or instructions, such as an operating system (OS)118, or other applications of the computing device110. In certain embodiments, the computing device110may run on more than one processor, such as two processors, four processors, eight processors, or any suitable number of processors.

The memory114may be a volatile memory, such as the random-access memory (RAM), for storing the data and information during the operation of the computing device110. In certain embodiments, the memory114may be a volatile memory array.

The storage device116is a non-volatile data storage media for storing the OS118and other applications (not shown) of the computing device110. The storage device116may store the OS118and any other necessary software or firmware components in the form of computer executable code or instructions, which may be executed at the processor112.

In certain embodiments, the distributed management device140has two management devices, including the first management device120and the second management device130. In certain embodiments, the distributed management device140may include more than two management devices. For example, the distributed management device140may include one first management device120and two or more second management devices130, or may include two or more first management devices and one second management device130. In certain embodiments, the distributed management device140may include two or more first management devices120and two or more second management devices130.

The first management device120is the management device that includes one subset of the BMC functionalities to control time critical functionalities. In certain embodiments, the first management device120may be a system on a chip (SoC). As shown inFIG. 1, the first management device120has a processor122, a memory124, a non-volatile memory126storing the firmware128therein, and any other necessary hardware components enabling the first management device120to operate. Further, the system interface150may be a part of the first management device120. In certain embodiments, the system interface150may be an IPMI standardized interface, which may include, without being limited to, a keyboard controller style (KCS) interface, a system management interface chip (SMIC) interface, and a block transfer (BT) interface.

The processor122is configured to control operation of the first management device120. In certain embodiments, the processor122may be a CPU. The processor122can execute any computer executable code or instructions, such as the firmware128stored in the non-volatile memory126, or other software or firmware applications of the first management device120. In certain embodiments, the first management device120may run on more than one processor, such as two processors, four processors, eight processors, or any suitable number of processors.

The memory124can be a volatile memory, such as the RAM, for storing the data and information during the operation of the first management device120. In certain embodiments, the memory124may be a volatile memory array.

The non-volatile memory126is a non-volatile data storage media for storing the firmware128and any other necessary software or firmware components of the first management device120. Examples of the non-volatile memory126may include flash memory, memory cards, USB drives, hard drives, floppy disks, optical drives, or any other types of data storage devices. As shown inFIG. 1, the firmware128includes a critical function management stack129, which includes first IPMI related computer executable code or instructions that may be executed at the processor122to perform a plurality of time critical functions related to the computing device110. For example, one of the time critical functions may include performing system power control of the computing device110. In addition, one of the time critical functions may include monitoring system components of the computing device110and obtaining system information of the computing device110. Moreover, one of the time critical functions may include performing a system communication with the computing device110through the system interface150.

As disclosed above, in certain embodiments, the first management device120may be a SoC. Examples of the BMC related SoC may include Pilot or Aspeed. In this case, the processor122of the first management device120may be a secondary processor built into the SoC, which is a separate controller. In other words, the first management device120is thus independent from the computing device110without sharing any resources of the computing device110. Alternatively, in certain embodiments, the first management device120may be implemented by components of the computing device110. For example, the processor122may be an external processor (the term “external” means that the processor is not originally an integral part of the distributed management device140) of the computing device110, which is shared by the first management device120. In this case, the non-volatile memory124may also be a non-volatile memory of the computing device110, which is shared by the first management device120. In this case, the resources of the computing device110are shared by the first management device120. One example of such configuration is the concept of Innovation Engine introduced by Intel Corporation, which provides a new microarchitecture linked with silicon process technology. In the model proposed by Intel, a common processor architecture is provided with multiple complete execution cores in one physical processor. Thus, the different execution cores of the processor may be used to run different code or instructions to provide certain functionalities independently.

FIG. 2schematically depicts a configuration process of the first management device using an external processor of the computing device having multiple execution cores according to certain embodiments of the present disclosure. Using the processor112of the computing device110as an example, the processor112and the non-volatile memory114of the computing device110may be formed as a CPU chip. Thus, at procedure210, a system administrator of the system100may upload the first IPMI related computer executable code or instructions (i.e., the critical function management stack129) to the processor112of the CPU chip of the computing device110from, for example, a remote computing device180through the network170. Then, at procedure220, the uploaded first IPMI related computer executable code or instructions are stored in a reserved area (e.g., the non-volatile memory114) of the CPU chip. In this case, one execution core of the processor112and the reserved area (e.g., the non-volatile memory114) of the CPU chip may be used to form the first management device120of the distributed management device140in the computing device110, and the other execution core of the processor112may perform operation of the computing device110. Since the two execution cores may operate independently, the first management device120may operate independently from the operation of the computing device110. Further, since both execution cores are provided in the same physical processor112, it may be easier for the first management device120(which is implemented by one of the execution cores) to perform the time critical functions, such as performing system power control of the computing device110, monitoring system components of the computing device110, obtaining system information of the computing device110, and performing system communication with the computing device110.

The second management device130is the management device that includes the other subset of the BMC functionalities to control non-critical functionalities. In certain embodiments, the second management device130may also be a SoC, which is physically separated from the first management device120. In certain embodiments, the second management device130may or may not have identical hardware components to the first management device120. As shown inFIG. 1, the second management device130has a processor132, a memory134, a network interface card (NIC)135, a non-volatile memory136storing the firmware138therein, and any other necessary hardware components enabling the second management device130to operate. In certain embodiments, although not shown inFIG. 1, the second management device130may also be connected to the system interface150such that the second management device130may have access to the computing device110.

The processor132is configured to control operation of the second management device130. In certain embodiments, the processor132may be a central processing unit (CPU). The processor132can execute any computer executable code or instructions, such as the firmware138stored in the non-volatile memory136, or other software or firmware applications of the second management device130. In certain embodiments, the second management device130may run on more than one processor, such as two processors, four processors, eight processors, or any suitable number of processors.

The memory134can be a volatile memory, such as the RAM, for storing the data and information during the operation of the second management device130. In certain embodiments, the memory134may be a volatile memory array.

The NIC135, sometimes referred to as a network interface controller, is a computer hardware component that functions as an external interface, which may be used to connect the second management device130to the network170. As shown inFIG. 1, the second management device130includes one NIC135. In certain embodiments, each of the first management device120and the second management device130may include one or more NICs. For example, when the system100includes multiple networks170, each of the first management device120and the second management device130may require multiple NICs, such that they may be respectively connected to the different networks170via each of the NICs. In this case, each of the NICs of the first management device120and the second management device130may either function as an external interface or an internal interface of the distributed management device140. For each of the first management device120and the second management device130, the number of the NICs may be determined based on the types of network being provided in the system100.

The non-volatile memory136is a non-volatile data storage media for storing the firmware138and any other necessary software or firmware components of the second management device130. Examples of the non-volatile memory136may include flash memory, memory cards, USB drives, hard drives, floppy disks, optical drives, or any other types of data storage devices. As shown inFIG. 1, the firmware138includes a non-function management stack139, which includes second IPMI related computer executable code or instructions that may be executed at the processor132to perform a plurality of non-critical functions related to the computing device110. Specifically, the non-critical functions are functions that are not as time essential as the time critical functions performed by the first management device120. In other words, among all BMC functionalities, the functions that are not the time critical functions performed by the first management device120may be categorized as the non-critical functions. In certain embodiments, the non-critical functions may include may include performing an external communication with the remote computing device180via the network170through the NIC135(i.e., the external interface of the second management device130). For example, the non-function management stack139may be used to provide a web server and its related management functions, which may be used to perform a variety of BMC functionalities using a web connection through the network170.

In certain embodiments, the firmware128(including the first IPMI related computer executable code or instructions) and the firmware138(including the second IPMI related computer executable code or instructions) may each have the flat liner code or a thin real-time OS (RTOS) based firmware, depending upon the level of abstraction of the functionalities of the time critical functions and non-critical functions.

The stack interface160is provided to connect the first management device120and the second management device130to perform an internal communication between the first management device120and the second management device130. In certain embodiments, the internal communication may be an IPMI based communication, or may be a communication under any other data exchange protocols or self-defined data exchange models. In certain embodiments, the stack interface160may be an Inter-Integrated Circuit (I2C) interface, a system management bus (SMB) interface, a local area network (LAN), or any other physical interface or medium. In certain embodiments, each of the first management device120and the second management device130may respectively perform the internal communications with each other through the stack interface160.

FIG. 3schematically depicts an internal communication between the first management device and the second management device according to certain embodiments of the present disclosure. In this embodiment, the distributed management device140includes one first management device120and one second management device130with the stack interface160interconnecting the two management devices, and only the first management device120is connected to the computing device110through the system150. In certain embodiments, the internal communication may be an IPMI based communication, or may be a communication under any other data exchange protocols or self-defined data exchange models.

At procedure310, when the firmware138of the second management device130is executing, the second IPMI related computer executable code or instructions (i.e., the non-critical function management stack139) may perform one of the non-critical functions that requires certain system information of the computing device110. In this case, at procedure320, the firmware138may perform the internal communication with the first management device120through the stack interface160to request the required system information of the computing device110from the first management device120. When the first management device120receives the request, at procedure330, the firmware128of the first management device120performs the time-critical functions to request the system information of the computing device110. At procedure340, the firmware128of the first management device120obtains the requested system information. It should be noted that, in certain embodiments, the firmware128of the first management device120may already have obtained the required system information of the computing device110. In this case, the procedure330may be omitted.

Then, at procedure350, the firmware128may perform the internal communication with the second management device130through the stack interface160to send the system information to the second management device130. Thus, at procedure360, the firmware138of the second management device130may receive the requested system information of the computing device110from the first management device120through the stack interface160, and then use the requested system information to perform the corresponding functions.

As described above, the two management devices of the distributed management device140may be synchronized by communicating over the connection using the stack interface160. The first management device120may handle the time critical aspects of the BMC, such as handling local system interfaces and system power control of the computing device110. Meanwhile, the second management device130may be used to support the rest of the non-critical functionalities of the BMC, such as server management functions.

With the D-IPMI system100, the two management devices are physically separated and operated individually in the distributed way, so the first management device120may be used to implement quick, tightly controlled functionalities to help resolving system contention issues. For example, when the computing device110is a server, there will be an advantage to reduce the time taken by the server in booting before the first video screen of the server appears. In this case, the first management device120may be used to implement quick, tightly controlled server bring-up sequence to speed up the server boot time tremendously.

Further, the D-IPMI system100may help in simplifying the complex server system designs in certain cases. For example, in a system, certain system information may be easily available in a certain part of the hardware components of the system, and the other system information may be more easily accessible in a different part of the system. By distributing the management devices into two or more devices each having an individually operable stack, the whole distributed management device140may still provide the same common IPMI based server management solution, which make be used to easily take care of complex server management requirements.

A further aspect of the present disclosure is directed to a method for performing distributed IPMI in a system. In certain embodiments, the method includes: providing a distributed management device140as shown inFIG. 1to a computing device110, where the computing device110functions as a host computer. In this case, the first IPMI related computer executable code executed at the first processor122of the first management device120may be used to perform a plurality of time critical functions related to the computing device110, and the second IPMI related computer executable code executed at the second processor132of the second management device130may be used to perform an external communication through the external interface, and to perform a plurality of non-critical functions related to the computing device110. For example, the time critical functions may include performing system power control of the computing device110; monitoring system components of the computing device110and obtaining system information of the computing device110; and performing a system communication with the computing device110through the system interface150. Further, an internal communication may be performed between the first management device120and the at least one second management device130through the stack interface160.

In certain embodiments, each of the first management device120and the second management device130may be a SoC physically separated from each other.

In a further aspect, the present disclosure is related to at least one non-transitory computer readable medium storing the first IPMI related computer executable code and second IPMI related computer executable code respectively. The first and second IPMI related computer executable code may be respectively executed at one or more processor of the first management device120and the second management device130to perform the corresponding functions as described above. In certain embodiments, the non-transitory computer readable medium may include, but not limited to, any physical or virtual storage media. In certain embodiments, the non-transitory computer readable medium may be implemented as the non-volatile memory126of the first management device120and the non-volatile memory136of the second management device130as shown inFIG. 1.