CN116841820A - Baseboard management control system, controller, server and supervision method - Google Patents

Baseboard management control system, controller, server and supervision method Download PDF

Info

Publication number
CN116841820A
CN116841820A CN202310646508.8A CN202310646508A CN116841820A CN 116841820 A CN116841820 A CN 116841820A CN 202310646508 A CN202310646508 A CN 202310646508A CN 116841820 A CN116841820 A CN 116841820A
Authority
CN
China
Prior art keywords
firmware
hardware
server
independent hardware
independent
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310646508.8A
Other languages
Chinese (zh)
Inventor
王魁英
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202310646508.8A priority Critical patent/CN116841820A/en
Publication of CN116841820A publication Critical patent/CN116841820A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources

Abstract

One or more embodiments of the present disclosure provide a baseboard management control system, a controller, a server, and a supervision method, where the system is disposed on the baseboard management controller, and the baseboard management controller is configured to supervise hardware on the server, and the system includes: the independent hardware firmware is used for supervising different hardware on the server respectively; and a supervisory operating system for allocating resources of the baseboard management controller to the plurality of independent hardware firmware.

Description

Baseboard management control system, controller, server and supervision method
Technical Field
One or more embodiments of the present disclosure relate to the field of operation and maintenance, and more particularly, to a baseboard management control system, a controller, a server, and a supervision method.
Background
BMC is called baseboard management controller (Baseboard Management Controller), divide into BMC chip and BMC firmware two parts, and BMC chip is the chip of integration on the mainboard of server. BMC firmware is a software program running on a BMC chip that starts running when the server is powered on, and is used to monitor the hardware on the server.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide a baseboard management control system, a controller, a server, and a supervision method, which can solve the deficiencies in the related art.
In order to achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
according to a first aspect of one or more embodiments of the present specification, there is provided a baseboard management control system deployed on a baseboard management controller for supervising hardware on a server, the system comprising:
the independent hardware firmware is used for supervising different hardware on the server respectively;
and a supervisory operating system for allocating resources of the baseboard management controller to the plurality of independent hardware firmware.
According to a second aspect of one or more embodiments of the present specification, there is provided a server supervision method based on a baseboard management controller, including:
determining a plurality of independent hardware firmware deployed on the baseboard manager, the plurality of independent hardware firmware corresponding to different hardware on a server, respectively;
and distributing the resources of the baseboard management controller to the plurality of independent hardware firmware so that at least one independent hardware firmware supervises corresponding hardware on the server.
According to a third aspect of one or more embodiments of the present specification, there is provided a server supervision method based on a baseboard management controller, including:
determining corresponding hardware of any independent hardware firmware deployed on the baseboard manager on a server; the substrate manager is provided with a plurality of independent hardware firmware, and the independent hardware firmware corresponds to different hardware on the server respectively;
utilizing resources from the baseboard management controller allocated to any one of the independent hardware firmware to supervise the determined hardware; wherein the resources of the baseboard management controller are respectively allocated to the plurality of independent hardware firmware.
According to a fourth aspect of one or more embodiments of the present specification, there is provided a baseboard management controller having disposed thereon a system as described in the first aspect.
According to a fifth aspect of one or more embodiments of the present specification, a server is presented, having disposed thereon a baseboard management controller, the baseboard management controller having disposed thereon a system according to the first aspect.
As can be seen from the above technical solutions, the baseboard management control system provided in one or more embodiments of the present disclosure splits a BMC firmware into multiple independent hardware firmware and a supervisory operating system, on one hand, different hardware on a server is respectively supervised by multiple independent hardware firmware, so that a supervisory task originally borne by one BMC firmware is split into multiple independent hardware firmware, decoupling between different hardware firmware is implemented, and thus, when updating and upgrading, updating and upgrading can be performed for a single independent hardware firmware, thereby improving firmware upgrading efficiency; on the other hand, the resource of the baseboard management controller is distributed to the independent hardware firmware through the supervision operation system, so that the resource used by the independent hardware firmware can be effectively managed, and the problem of efficiency reduction caused by uneven resource distribution is avoided.
Drawings
Fig. 1 is a schematic diagram of a baseboard management controller supervision server according to an exemplary embodiment.
Fig. 2 is a block diagram of a baseboard management control system according to an exemplary embodiment.
FIG. 3 is a schematic diagram of a supervisory operating system allocation of resources, as provided by an example embodiment.
Fig. 4 is a schematic diagram of a cloud operation system supervision hardware according to an exemplary embodiment.
Fig. 5 is a schematic diagram of a baseboard management control system including device management firmware according to an exemplary embodiment.
FIG. 6 is a schematic diagram of a separate hardware firmware reboot provided by an example embodiment.
Fig. 7 is a flowchart of a server supervision method based on a baseboard management controller according to an exemplary embodiment.
Fig. 8 is a flow chart of another server administration method based on a baseboard management controller according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with aspects of one or more embodiments of the present description as detailed in the accompanying claims.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.
The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of related data is required to comply with the relevant laws and regulations and standards of the relevant country and region, and is provided with corresponding operation entries for the user to select authorization or rejection.
For further description of one or more embodiments of the present specification, the following embodiments are provided:
BMC is called baseboard management controller, and is divided into BMC chip and BMC firmware, and BMC chip is the chip of loading on the mainboard of server. BMC firmware is a software program running on a BMC chip that starts running when the server is powered on, and is used to monitor the hardware on the server. The content of BMC supervision mainly comprises four parts: and (3) managing server information, monitoring and managing server hardware, remotely controlling and managing the server, and maintaining and managing the server. Wherein the server information management includes: recording server information (model, manufacturer, date, production and technology information of each component, chassis information, main board information, etc.), BMC information (server hostname, IP address (Internet Protocol Address, internet protocol address), BMC firmware version, etc.); server hardware monitoring management includes: detecting health states such as temperature, voltage and the like of different hardware (such as a CPU (Central processing Unit), a memory, a hard disk, a fan, a machine frame and the like) on the server, and simultaneously adjusting the rotating speed of the fan in real time according to the conditions of all temperature acquisition points to ensure that the server does not generate over-temperature and the overall power consumption is controlled not to be too high; if any abnormality occurs in the single-board component, the information is timely reported to an upper network manager through various industry universal specifications such as IPMI (Intelligent Platform Management Interface ) protocol, redfish (red fish) protocol and the like; the remote control management of the server comprises: powering on and powering off, restarting, firmware updating, system installation and the like of the server; the server maintenance management includes: log management, user management, BIOS management, alarm management, etc.
Fig. 1 is a schematic diagram of a baseboard management controller supervision server according to an exemplary embodiment, as shown in fig. 1, a BMC firmware 12 is running on a BMC chip 11, where the BMC firmware 12 is configured to supervise hardware 14-hardware 16 on a server 13.
In the related art, the BMC firmware 12 is an integral firmware corresponding to a plurality of hardware on the server 13, which results in that when a firmware portion corresponding to a single hardware needs to be updated, the entire BMC firmware 12 needs to be updated. For example: in the case where the firmware portion corresponding to the hardware 14 needs to be updated, the BMC firmware 12 needs to be updated entirely even if the firmware portion corresponding to the hardware 15 does not need to be updated. The integral upgrading mode is low in upgrading efficiency, faults and errors are easy to occur in the upgrading process, and upgrading risks are high.
In order to solve the problems in the related art, the present disclosure proposes a baseboard management control system, which decouples the BMC firmware 12 into a plurality of independent hardware firmware, wherein the plurality of independent hardware firmware respectively corresponds to different hardware on a server, and the supervisory operating system allocates the resources of the BMC chip to the plurality of independent hardware firmware.
Fig. 2 is a schematic diagram of a baseboard management control system according to an exemplary embodiment, as shown in fig. 2, where the schematic diagram includes: a baseboard management controller 21 and a server 22.
Baseboard management controller 21 operates independently of other hardware on server 22 (e.g., hardware 205-hardware 207) for policing the hardware on server 22 (baseboard management controller 21 may be deployed on server 22, and baseboard management controller 21 and server 22 are depicted separately in fig. 2 for clarity in terms of the concept of baseboard management controller 21 operating independently).
Baseboard management control system 201 running on baseboard management controller 21 includes independent hardware firmware 202, independent hardware firmware 203, independent hardware firmware 204, and supervisory operating system 201. Independent hardware firmware 202-independent hardware firmware 204 corresponds to hardware 205-hardware 207 on server 22, where independent hardware firmware 202 corresponds to hardware 205, independent hardware firmware 203 corresponds to hardware 206, and independent hardware firmware 204 corresponds to hardware 207.
And the plurality of independent hardware firmware are respectively used for supervising different hardware on the server.
The independent hardware firmware is a program running on the baseboard management controller, and different independent hardware firmware corresponds to different hardware on the server. Each independent hardware firmware is used to supervise the corresponding hardware on the server when the baseboard management control system is running.
The independent hardware firmware may include at least one of: fan firmware, log firmware, sensor firmware, virtual media firmware, power supply firmware, network firmware, BIOS configuration firmware, redfish background firmware, IPMI background firmware, webUI firmware.
The interaction between the separate hardware firmware may be, for example: the fan firmware can be used for monitoring the condition of the fan on the server, the sensor firmware can be used for managing the temperature of different hardware on the server, at the moment, the sensor firmware needs the temperature information of the fan monitored by the fan firmware, and the sensor firmware can send a temperature information acquisition request to the fan firmware to acquire the temperature information. Of course, the independent hardware firmware may not directly interact, but indirectly interact through a specific firmware, which will be described in detail later, and will not be described here again.
An independent hardware firmware may only supervise one hardware, for example: the fan firmware only monitors the fans on the server, and the information monitored by the fan firmware may include: rotational speed, voltage, power consumption, etc. of the fan; an independent hardware firmware may also govern a portion of the content of multiple hardware, such as: the sensor firmware can monitor the temperatures of a plurality of hardware such as a fan, a CPU, a memory, etc., and the manner of acquiring the temperatures of different hardware will be described in detail later in this specification, which is not repeated here.
The log firmware is used for managing the logs of the server except the fan firmware; the sensor firmware is used for monitoring the temperatures of different hardware on the server; the virtual media firmware is used for supervising the optical disk, the mobile hard disk and the like; the power firmware is used for supervising the power on the server; the network firmware is used for supervising the network of the server; the BIOS (Basic Input Output System, basic input/output) is configured to monitor a bus controlling input/output on the server; the IPMI background firmware monitors hardware on a server based on the IPMI standard; the Redfish background firmware monitors hardware on a server based on the Redfish specification; webUI (Website User Interface, web product interface design) firmware is the front-end interface module of the baseboard management control system.
A supervisory operating system 201 for allocating resources of the baseboard management controller to the plurality of independent hardware firmware. An operating system is a computer program that manages computer hardware and software resources. Firmware is a device "driver" stored inside the device. Through the firmware, the operating system can realize the operation of the specific machine according to the standard device driver, such as an optical drive, a CD-ROM, a CD-RW, etc. all have internal firmware. And the computer resources used by the different firmware also need to be allocated by the operating system. For example, the supervisory operating system 201 may be built based on u-boot Bootloader, linux kernel, systemized service, and DBUS (a message bus system, message bus system). The Bootloader is a first code segment executed by the operating system after power-up, and through the code segment, the operating system can initialize the supervision and management controller to acquire information of resources such as a memory, a processor and the like. The u-boot Bootloader, the Linux kernel and the systemized service are all software programs needed by the supervision operating system, and the DBUS is a data bus for realizing data transmission by the supervision management controller. Of course, the supervisory operating system may also be constructed based on other types of software programs, and the present disclosure is not limited to the manner in which the operating system is constructed.
Under the condition that the BMC firmware is not split into a plurality of independent hardware firmware, the resources of the baseboard management controller are used for supporting the running of the BMC firmware, and an operating system does not need to be supervised for resource allocation management. However, in the baseboard management control system proposed in the present specification, the BMC firmware is decoupled into a plurality of independent hardware firmware, and at this time, the supervisory operating system needs to allocate the resources of the baseboard management controller to the plurality of independent hardware firmware, so that the resources used by the plurality of independent hardware firmware can be effectively managed, thereby avoiding the problem of reduced efficiency caused by uneven allocation of the resources.
As shown in fig. 3, the supervisory operating system 201 may split the resources of the baseboard management controller into three parts, resource 1, resource 2, and resource 3. Wherein resource 1 is allocated to independent hardware firmware 202, resource 2 is allocated to independent hardware firmware 203, and resource 3 is allocated to independent hardware firmware 204. Similar to a general operating system, the resources allocated by the supervisory operating system 201 include hardware resources and software resources, but are allocated to the resources of the baseboard management controller, not to the resources of the server.
The resources of the baseboard management controller may include at least one of: processor resources, memory resources, input/output resources.
The processor is a central processor of the baseboard management controller, and serves as an operation and control core of the baseboard management controller, and the resource represents the computing resource of the baseboard management controller. The memory resource is a memory resource of the baseboard management controller. Since the buses on the baseboard management controller for data transmission are limited, the input/output rate is limited, which means that the input/output resources of the baseboard management controller are limited. Taking processor resources as an example, the supervisory operating system may limit the processor utilization of the power firmware to less than 10% so that the power firmware may baseboard manage at most 10% of the computing resources of the processor of the controller. Similarly, the supervisory operating system can limit the processor utilization of other independent hardware firmware, and limit the sum of the processor utilization of all independent hardware firmware to be not more than 90%, so as to prevent the processor of the baseboard management controller from overload work for a long time, and further prolong the service life of the processor.
In the embodiment, on one hand, different hardware on the server is respectively supervised through a plurality of independent hardware firmware, so that the supervision task originally borne by one BMC firmware is split into the plurality of independent hardware firmware, decoupling among the different hardware firmware is realized, and further, when updating and upgrading are carried out, updating and upgrading can be carried out on the single independent hardware firmware, and therefore, the upgrading efficiency of the firmware is improved; on the other hand, the resource of the baseboard management controller is distributed to the independent hardware firmware through the supervision operation system, so that the resource used by the independent hardware firmware can be effectively managed, and the problem of efficiency reduction caused by uneven resource distribution is avoided.
In an embodiment, the plurality of independent hardware firmware is connected to the cloud operation and maintenance system, and the plurality of independent hardware firmware is further configured to: and receiving a management instruction issued by the cloud operation and maintenance system, and supervising corresponding hardware on the server according to the management instruction.
Referring to fig. 4, fig. 4 is a schematic diagram of a cloud operation system supervision hardware according to an exemplary embodiment, as shown in fig. 4, where a plurality of independent hardware firmware in fig. 2 is connected to a cloud operation system 41.
The cloud operation and maintenance system 41 may be deployed on a target server different from the server 22, and the target server may monitor hardware on the server 22 and update and upgrade independent hardware firmware on the baseboard management controller 21 through the cloud operation and maintenance system 41. The cloud operation and maintenance system 41 may issue a management instruction to the independent hardware firmware 202, and the independent hardware firmware 202 monitors the hardware 205 according to the management instruction.
The management instructions may include attribute information adjustment instructions and hardware update instructions. The attribute information adjustment instruction is used for adjusting the attribute of the hardware, and the hardware update instruction is used for updating the version of the hardware.
In one case, the management instructions may include attribute information adjustment instructions for hardware on the server. The plurality of independent hardware firmware is to: and receiving the attribute information adjustment instruction issued by the cloud operation and maintenance system, and adjusting the attribute information of the corresponding hardware on the server according to the attribute information adjustment instruction. Taking a fan as an example, the cloud operation and maintenance system may issue an attribute information adjustment instruction to the sensor firmware for the fan, the instruction requiring that the rotational speed of the fan be adjusted from 15000RPM (rotational speed per minute) to 5000RPM. After receiving the attribute information adjustment instruction, the fan firmware can adjust the rotation speed of the fan according to the instruction.
In another case, the management instructions may include hardware update instructions for hardware on the server. The plurality of independent hardware firmware is to: and receiving the hardware updating instruction issued by the cloud operation and maintenance system, and updating and upgrading corresponding hardware on the server according to the hardware updating instruction.
In the embodiment, the cloud operation and maintenance system issues the management instruction to the independent hardware firmware, so that the independent hardware firmware can monitor the corresponding hardware on the server according to the management instruction, and the use safety of the hardware on the server is ensured.
According to the embodiment, the attribute information of the hardware is adjusted based on the instruction issued by the cloud operation and maintenance system, and the independent hardware firmware can also adjust the attribute information of the hardware.
In an embodiment, the independent hardware firmware itself may be configured with a management policy based on which the independent hardware firmware may adjust the attribute information of the corresponding hardware.
Taking the sensor firmware as an example, the management policy configured by the sensor firmware for the fan may be: when the CPU temperature reaches a first preset temperature threshold (30 ℃ for example), the rotating speed of the fan is increased to a first rotating speed (10000 RPM for example); when the CPU temperature reaches a second preset temperature threshold (e.g., 40 degrees Celsius), the fan speed is increased to a second speed (e.g., 15000 RPM). As described above, the sensor firmware may acquire temperature information of the CPU from the device management firmware, and in the case where the acquired temperature information reaches the first temperature threshold, the sensor firmware may increase the rotation speed of the fan to the first rotation speed; under the condition that the acquired temperature information reaches a second temperature threshold value, the sensor firmware can increase the rotating speed of the fan to the second rotating speed, so that the purposes of reducing the CPU temperature and preventing the CPU temperature from being too high are achieved.
In the embodiment, the independent hardware firmware adjusts the attribute information of the corresponding hardware through the self-configured management strategy, so that the independent hardware firmware realizes autonomous adjustment without issuing an instruction by the cloud operation and maintenance system, thereby saving the cost and improving the adjustment efficiency.
Similar to hardware, the independent hardware firmware can be updated and upgraded based on the cloud operation and maintenance system.
In an embodiment, the plurality of independent hardware firmware is connected to the cloud operation and maintenance system, and the plurality of independent hardware firmware is further configured to: and receiving an updating instruction aiming at any independent hardware firmware issued by the cloud operation and maintenance system, and updating any independent hardware firmware according to an updating data packet carried in the updating instruction.
As shown in fig. 4, the cloud operation maintenance system 41 may send an update instruction to the independent hardware firmware 204, where the update instruction may include an update data packet corresponding to the version to be updated. The independent hardware firmware 204 may be updated from the current version to the version to be updated according to the update data packet carried in the update instruction.
An update instruction may carry not only an update packet of an independent hardware firmware, but also update packets for a plurality of independent hardware firmware. Different update packages are named according to the independent hardware firmware for which they are intended, for example: the update package for the independent hardware firmware 204 may be named "204-10.1", meaning an update package for version 10.1 of the independent hardware firmware 204.
In the embodiment, the update instruction is issued to the independent hardware firmware, so that the independent hardware firmware can be updated according to the update instruction, and the situation that the independent hardware firmware cannot support the supervision of hardware due to the backward version is avoided.
As noted above, the different independent hardware firmware may interact directly or may remain independent of each other. If different independent hardware firmware does not directly interact with each other, the update and upgrade of the single independent hardware firmware will not interfere with other independent hardware firmware (the program needs to be restarted when the firmware is upgraded, and other firmware interacting with the firmware may be interfered).
In an embodiment, the system further comprises: the device management firmware is used for maintaining the attribute information of the hardware on the server and returning the attribute information of the target hardware to any independent hardware firmware under the condition that the attribute information acquisition request for the target hardware sent by any independent hardware firmware is received; wherein the target hardware is any one of a plurality of hardware on the server.
This embodiment is described in detail below with reference to fig. 5, where fig. 5 adds a device management firmware 208 to the baseboard management controller 21 of fig. 2. As shown in FIG. 5, the device management firmware 208 is identical to the independent hardware firmware, receives resource allocations for the supervisory operating system, and the device management firmware 208 is coupled to each of the independent hardware firmware.
The device management firmware maintains the attribute information of the hardware on the server, and is used for returning the attribute information of the target hardware to any independent hardware firmware under the condition that the attribute information acquisition request for the target hardware sent by any independent hardware firmware is received; wherein the target hardware is any one of a plurality of hardware on the server.
The device management firmware can register the attribute information of different hardware maintained by the device management firmware on the DBUS, and the DBUS is connected with each independent hardware firmware, so that the device management firmware can become a transfer station for information interaction between the independent hardware firmware based on the DBUS.
The attribute information of the hardware may include basic information and state information of the hardware. The basic information of the hardware may include: the model number of the hardware, the manufacturer, the date, the production and technical information of each component, etc. Depending on the hardware, the state information of the hardware is different, for example: in the case where the hardware is a fan, the status information may include the rotational speed and power of the fan; in the case that the hardware is a CPU, the state information may include a temperature, power, and usage rate of the CPU; in the case where the hardware is a power supply, the state information may include power, power consumption, voltage of the power supply.
Although the different independent hardware firmware are independent of each other and do not interact directly, there are cases where one independent hardware firmware needs information of hardware managed by another independent hardware firmware, for example: the sensor firmware is used for supervising the temperature of different hardware, which requires temperature information of different hardware. At this time, the independent hardware firmware requiring information may send an attribute information acquisition request to the device management firmware, and since the device management firmware maintains attribute information of different hardware, the device management firmware may return the attribute information of the hardware targeted by the attribute information acquisition request to the independent hardware firmware sending the request, so that the independent hardware firmware may acquire the attribute information of the hardware supervised by other independent hardware firmware without direct interaction between the independent hardware firmware.
Under the condition that the independent hardware firmware is kept independent from each other, the single independent hardware firmware is restarted when updated and upgraded, and interference to other independent hardware firmware is avoided. As shown in fig. 6, a device management firmware 601 and an independent hardware firmware 602-independent hardware firmware 604 are provided at an upper layer of the monitor operating system 605. The supervisory operating system 605 is built based on u-boot Bootloader, linux kernel, systerd, and DBUS, among others. According to arrow "(2)", the independent hardware firmware 602-independent hardware firmware 604 can only interact indirectly through the device management firmware 601, but cannot interact directly, so that the independent hardware firmware 602-independent hardware firmware 604 is restarted (as shown by arrow "(1)") without affecting other independent hardware firmware.
In this embodiment, the attribute information of the hardware on the server maintained by the device management firmware is fed back to the independent hardware firmware sending the request, so that the independent hardware firmware can acquire the attribute information of the hardware supervised by other independent hardware firmware without direct interaction. On one hand, the function of the independent hardware firmware supervision hardware is not influenced; on the other hand, the independence among different independent hardware firmware is ensured, so that the baseboard management control system can update and upgrade the independent hardware firmware, and the upgrade efficiency of the firmware is improved.
Further, the plurality of independent hardware firmware is further configured to: when attribute information of any one of a plurality of pieces of hardware on the server is changed, the changed attribute information of any piece of hardware is issued to the device management firmware.
The device management firmware can maintain the attribute information of different hardware on the server, because the independent hardware firmware can issue the attribute information of the hardware supervised by the independent hardware firmware to the device management firmware, and when the attribute information of the hardware changes, the independent hardware firmware can issue the changed attribute information to the device management firmware so as to update the attribute information of the hardware maintained by the device management firmware.
As for the manner of distribution of information, attribute information may be actively acquired by the device management firmware, for example: the device management firmware can be configured with a timing task which requires the device management firmware to send information acquisition requests to each independent hardware firmware at fixed time, so that the independent hardware firmware which receives the requests sends the attribute information of the hardware supervised by the independent hardware firmware to the device management firmware; attribute information may also be actively sent by separate hardware firmware, such as: the independent hardware firmware can send the attribute information of the hardware supervised by the independent hardware firmware to the equipment management firmware at regular time, the equipment management firmware can compare the attribute information with the attribute information maintained by the independent hardware firmware after receiving the attribute information, if the attribute information is consistent with the equipment management firmware, the updating is not needed, and if the attribute information is inconsistent with the equipment management firmware, the attribute information maintained by the equipment management firmware is updated into the attribute information sent by the independent hardware firmware.
In the embodiment, the changed attribute information is issued to the device management firmware through the independent hardware firmware, so that the device management firmware can acquire the attribute information of different hardware, and the real-time property of the attribute information is ensured.
Fig. 7 is a server supervision diagram based on a baseboard management controller according to an exemplary embodiment, and as shown in fig. 7, the method at least includes the following steps:
step 702, determining a plurality of independent hardware firmware deployed on the baseboard manager, the plurality of independent hardware firmware respectively corresponding to different hardware on a server;
and step 704, allocating the resources of the baseboard management controller to the plurality of independent hardware firmware, so that at least one independent hardware firmware supervises corresponding hardware on the server.
In the embodiment, on one hand, different hardware on the server is respectively supervised through a plurality of independent hardware firmware, so that the supervision task originally borne by one BMC firmware is split into the plurality of independent hardware firmware, decoupling among the different hardware firmware is realized, and further, when updating and upgrading are carried out, updating and upgrading can be carried out on the single independent hardware firmware, and therefore, the upgrading efficiency of the firmware is improved; on the other hand, the resource of the baseboard management controller is distributed to the independent hardware firmware through the supervision operation system, so that the resource used by the independent hardware firmware can be effectively managed, and the problem of efficiency reduction caused by uneven resource distribution is avoided.
In an embodiment, the method further comprises: determining equipment management firmware deployed on the baseboard manager, wherein the equipment management firmware maintains attribute information of hardware on the server; the resource of the baseboard management controller is distributed to the equipment management firmware, so that the equipment management firmware returns the attribute information of the target hardware to any independent hardware firmware under the condition that the equipment management firmware receives the attribute information acquisition request for the target hardware sent by the independent hardware firmware; wherein the target hardware is any one of a plurality of hardware on the server.
In this embodiment, the attribute information of the hardware on the server maintained by the device management firmware is fed back to the independent hardware firmware sending the request, so that the independent hardware firmware can acquire the attribute information of the hardware supervised by other independent hardware firmware without direct interaction. On one hand, the function of the independent hardware firmware supervision hardware is not influenced; on the other hand, the independence among different independent hardware firmware is ensured, so that the baseboard management control system can update and upgrade the independent hardware firmware, and the upgrade efficiency of the firmware is improved.
Fig. 8 is a flowchart of another server supervision method based on a baseboard management controller according to an exemplary embodiment, and as shown in fig. 8, the method at least includes the following steps:
step 802, determining corresponding hardware of any independent hardware firmware deployed on the baseboard manager on a server; the substrate manager is provided with a plurality of independent hardware firmware, and the independent hardware firmware corresponds to different hardware on the server respectively;
step 804, utilizing the resources from the baseboard management controller allocated to any one of the independent hardware firmware to supervise the determined hardware; wherein the resources of the baseboard management controller are respectively allocated to the plurality of independent hardware firmware.
In the embodiment, on one hand, different hardware on the server is respectively supervised through a plurality of independent hardware firmware, so that the supervision task originally borne by one BMC firmware is split into the plurality of independent hardware firmware, decoupling among the different hardware firmware is realized, and further, when updating and upgrading are carried out, updating and upgrading can be carried out on the single independent hardware firmware, and therefore, the upgrading efficiency of the firmware is improved; on the other hand, the resource of the baseboard management controller is distributed to the independent hardware firmware through the supervision operation system, so that the resource used by the independent hardware firmware can be effectively managed, and the problem of efficiency reduction caused by uneven resource distribution is avoided.
In an embodiment, the resources of the baseboard management controller are further allocated to device management firmware deployed on the baseboard manager, the device management firmware maintaining attribute information of hardware on the server; the method further comprises the steps of: sending an attribute information acquisition request for target hardware to the equipment management firmware, and receiving attribute information of the target hardware returned by the equipment management firmware; wherein the target hardware is any one of a plurality of hardware on the server.
In this embodiment, the attribute information of the hardware on the server maintained by the device management firmware is fed back to the independent hardware firmware sending the request, so that the independent hardware firmware can acquire the attribute information of the hardware supervised by other independent hardware firmware without direct interaction. On one hand, the function of the independent hardware firmware supervision hardware is not influenced; on the other hand, the independence among different independent hardware firmware is ensured, so that the baseboard management control system can update and upgrade the independent hardware firmware, and the upgrade efficiency of the firmware is improved.
In an embodiment, the method further comprises: receiving a management instruction issued by a cloud operation and maintenance system aiming at any independent hardware firmware, and supervising corresponding hardware on the server according to the management instruction; and/or receiving an update instruction aiming at any independent hardware firmware issued by the cloud operation and maintenance system, and updating any independent hardware firmware according to an update data packet carried in the update instruction.
In the embodiment, on one hand, a management instruction is issued to the independent hardware firmware through the cloud operation and maintenance system, so that the independent hardware firmware can supervise corresponding hardware on the server according to the management instruction, and the use safety of the hardware on the server is ensured; on the other hand, by issuing the update instruction to the independent hardware firmware, the independent hardware firmware can be updated according to the update instruction, so that the problem that the independent hardware firmware cannot support the supervision of hardware due to the backward version is avoided.
The present disclosure further provides a baseboard management controller, where the baseboard management control system in one or more embodiments is disposed on the baseboard management controller, so as to implement the technical solution of the present disclosure.
The present disclosure further provides a server, where a baseboard management controller is disposed on the server, and the baseboard management controller is disposed on the baseboard management controller, so as to implement the technical solution of the present disclosure.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present application, and it is not intended to limit the embodiment(s) of the present application to the particular embodiment(s) described.

Claims (14)

1. A baseboard management control system, wherein the system is disposed in a baseboard management controller, the baseboard management controller is configured to supervise hardware on a server, the system comprises:
the independent hardware firmware is used for supervising different hardware on the server respectively;
and a supervisory operating system for allocating resources of the baseboard management controller to the plurality of independent hardware firmware.
2. The system of claim 1, wherein the system further comprises:
the device management firmware is used for maintaining the attribute information of the hardware on the server and returning the attribute information of the target hardware to any independent hardware firmware under the condition that the attribute information acquisition request for the target hardware sent by any independent hardware firmware is received; wherein the target hardware is any one of a plurality of hardware on the server.
3. The system of claim 2, wherein the plurality of independent hardware firmware is further to:
when attribute information of any one of a plurality of pieces of hardware on the server is changed, the changed attribute information of any piece of hardware is issued to the device management firmware.
4. The system of claim 1, wherein the plurality of independent hardware firmware is coupled to the cloud operation and maintenance system, the plurality of independent hardware firmware further configured to:
receiving a management instruction issued by the cloud operation and maintenance system, and supervising corresponding hardware on the server according to the management instruction; and/or the number of the groups of groups,
and receiving an updating instruction aiming at any independent hardware firmware issued by the cloud operation and maintenance system, and updating any independent hardware firmware according to an updating data packet carried in the updating instruction.
5. The system of claim 4, wherein the management instructions comprise attribute information adjustment instructions, the plurality of independent hardware firmware to:
and receiving the attribute information adjustment instruction issued by the cloud operation and maintenance system, and adjusting the attribute information of the corresponding hardware on the server according to the attribute information adjustment instruction.
6. The system of claim 1, wherein the plurality of independent hardware firmware comprises at least one of:
fan firmware, log firmware, sensor firmware, virtual media firmware, power supply firmware, network firmware, BIOS configuration firmware, redfish background firmware, IPMI background firmware, webUI firmware.
7. The system of claim 1, wherein the resources of the baseboard management controller include at least one of:
processor resources, memory resources, input/output resources.
8. A method for supervising a server based on a baseboard management controller, comprising:
determining a plurality of independent hardware firmware deployed on the baseboard manager, the plurality of independent hardware firmware corresponding to different hardware on a server, respectively;
and distributing the resources of the baseboard management controller to the plurality of independent hardware firmware so that at least one independent hardware firmware supervises corresponding hardware on the server.
9. The method of claim 8, wherein the method further comprises:
determining equipment management firmware deployed on the baseboard manager, wherein the equipment management firmware maintains attribute information of hardware on the server;
the resource of the baseboard management controller is distributed to the equipment management firmware, so that the equipment management firmware returns the attribute information of the target hardware to any independent hardware firmware under the condition that the equipment management firmware receives the attribute information acquisition request for the target hardware sent by the independent hardware firmware; wherein the target hardware is any one of a plurality of hardware on the server.
10. A method for supervising a server based on a baseboard management controller, comprising:
determining corresponding hardware of any independent hardware firmware deployed on the baseboard manager on a server; the substrate manager is provided with a plurality of independent hardware firmware, and the independent hardware firmware corresponds to different hardware on the server respectively;
utilizing resources from the baseboard management controller allocated to any one of the independent hardware firmware to supervise the determined hardware; wherein the resources of the baseboard management controller are respectively allocated to the plurality of independent hardware firmware.
11. The method of claim 10, wherein the baseboard management controller's resources are further allocated to device management firmware deployed on the baseboard manager, the device management firmware maintaining attribute information of hardware on the server; the method further comprises the steps of:
sending an attribute information acquisition request for target hardware to the equipment management firmware, and receiving attribute information of the target hardware returned by the equipment management firmware; wherein the target hardware is any one of a plurality of hardware on the server.
12. The method as recited in claim 10, further comprising:
receiving a management instruction issued by a cloud operation and maintenance system aiming at any independent hardware firmware, and supervising corresponding hardware on the server according to the management instruction; and/or the number of the groups of groups,
and receiving an updating instruction aiming at any independent hardware firmware issued by the cloud operation and maintenance system, and updating any independent hardware firmware according to an updating data packet carried in the updating instruction.
13. A baseboard management controller having disposed thereon the system of any one of claims 1-7.
14. A server having disposed thereon a baseboard management controller having disposed thereon the system of any one of claims 1-7.
CN202310646508.8A 2023-06-01 2023-06-01 Baseboard management control system, controller, server and supervision method Pending CN116841820A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310646508.8A CN116841820A (en) 2023-06-01 2023-06-01 Baseboard management control system, controller, server and supervision method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310646508.8A CN116841820A (en) 2023-06-01 2023-06-01 Baseboard management control system, controller, server and supervision method

Publications (1)

Publication Number Publication Date
CN116841820A true CN116841820A (en) 2023-10-03

Family

ID=88169631

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310646508.8A Pending CN116841820A (en) 2023-06-01 2023-06-01 Baseboard management control system, controller, server and supervision method

Country Status (1)

Country Link
CN (1) CN116841820A (en)

Similar Documents

Publication Publication Date Title
US7783907B2 (en) Power management of multi-processor servers
US7934121B2 (en) Transparent replacement of a system processor
EP1763726B1 (en) A method and apparatus for managing power consumption of a server
US8020016B2 (en) Method for controlling electric power of computer system
US7321927B2 (en) Controlling method, computer system, and processing program of booting up a computer
US8171321B2 (en) Method and apparatus for cost and power efficient, scalable operating system independent services
US8327169B2 (en) Power management to maximize reduced power state for virtual machine platforms
US8046520B2 (en) Compound computer system and method for sharing PCI devices thereof
US8307367B2 (en) Smart scheduling of automatic partition migration by the use of timers
CN106980529B (en) Computer system for managing resources of baseboard management controller
US20210247903A1 (en) Dynamically adjusting storage capacity
KR20140008363A (en) Non-intrusive power management
US8677160B2 (en) Managing power consumption of a computer
US10429909B2 (en) Managing power in a high performance computing system for resiliency and cooling
US20210365301A1 (en) System and method for power and thermal management of disaggregated server subsystems
EP4027241A1 (en) Method and system for optimizing rack server resources
EP3295275A2 (en) Managing power in a high performance cpmputing system for resiliency and cooling
US10996942B1 (en) System and method for graphics processing unit firmware updates
CN116841820A (en) Baseboard management control system, controller, server and supervision method
US8312126B2 (en) Managing at least one computer node
CN115657838A (en) Power supply control method and computing equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination