A blade server setting method, device and readable storage medium

Abstract

The application discloses a blade server setting method and device and a readable storage medium, and relates to the field of electronic information. The blade server setting method provided by the application sets the SMBUS as a slave mode through initialization of an SMBUS register, receives request data sent by other blade servers, and analyzes the request data to confirm that the request data belongs to an IPMB protocol or a PMBUS protocol. If the request data belongs to the IPMB protocol, the SMBUS is adjusted as a master mode, and the analysis result is sent to the other blade servers. The principle is that the PMBUS protocol and the IPMB protocol are both functions realized based on the SMBUS, and compared with the original management module added with a BMC, the SMBUS in the device used in the application is self-provided in the power supply blade, so that the cost is saved under the condition that the power supply blade can support the PMBUS and the IPMB protocol simultaneously.

Description

Technical Field

[0001] This application relates to the field of information technology, and in particular to a blade server setup method, apparatus, and readable storage medium. Background Technology

[0002] In recent years, with the development of information technology, blade servers have been used more and more. Their main structure is a large chassis, inside which many "blades" can be inserted, such as computing blades, storage blades, and switching blades. These blades also include one or more power blades to provide power to the entire chassis. These power blades often need to be managed by switching blades or other management units in order to obtain basic information about the power blades and realize various functions such as remote power on / off. The power blades may also need to communicate with other blades in the chassis.

[0003] Existing power blades generally only support the Power Management Bus (PMBUS) protocol for information access. However, to enable direct access and control of power devices through application tools such as the Intelligent Platform Management Interface (IPMI) and the Intelligent Platform Management Bus (IPMB), the power blade needs to support the IPMB bus. The current management method is to add an external Baseboard Manager Controller (BMC) to support the IPMB bus. However, adding a BMC management module or BMC chip requires redesigning the circuit, remaking the printed circuit board (PCB), and redesigning and developing the product chip structure layout, resulting in high development costs.

[0004] Given the above-mentioned technologies, finding a low-cost management method for power blades that can simultaneously support PMBUS and IPMB protocols is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a blade server setup method to solve the problem that current power blades need to add an external BMC to support both IPMB bus and PMBUS bus, which leads to excessive costs due to circuit redesign and PCB rework.

[0006] To address the aforementioned technical problems, this application provides a blade server configuration method, comprising:

[0007] Initialize the SMBUS register and set the SMBUS to slave mode;

[0008] Receive request data sent by other blade servers and confirm that the request data belongs to the IPMB protocol or the PMBUS protocol;

[0009] Based on the confirmation result, either the IPMB protocol or the PMBUS protocol is selected to parse the request data;

[0010] If the requested data belongs to the IPMB protocol, then the SMBUS is switched to master mode, and the obtained parsing result is sent to the other blade servers.

[0011] Preferably, it further includes:

[0012] When the SMBUS is in master mode, it edits the initial data using the IPMB protocol and sends the initial data to the other blade servers.

[0013] Preferably, after confirming that the requested data belongs to the IPMB protocol or the PMBUS protocol, the method further includes:

[0014] If the requested data belongs to the PMBUS protocol, then the SMBUS is kept in slave mode to respond to the requested data so that the other blade servers can retrieve the response information.

[0015] Preferably, confirming that the requested data belongs to the IPMB protocol or the PMBUS protocol includes:

[0016] Retrieve the address from the requested data;

[0017] The request data is matched against the SMBUS address, and the matching result determines whether the request data belongs to the IPMB protocol or the PMBUS protocol.

[0018] Preferably, after receiving request data sent by other blade servers and before confirming that the request data belongs to the IPMB protocol or the PMBUS protocol, the method further includes:

[0019] Determine whether the request information meets the preset requirements;

[0020] If the preset requirements are met, proceed to the step of confirming that the requested data belongs to the IPMB protocol or the PMBUS protocol;

[0021] If the preset requirements are not met, the requested data will be intercepted.

[0022] Preferably, after selecting the IPMB protocol or the PMBUS protocol to parse the request data based on the confirmation result, the method further includes:

[0023] Determine whether the requested data requires a response:

[0024] If the requested data requires a response, then according to the protocol corresponding to the requested data, the steps of adjusting the SMBUS to master mode and sending the obtained parsing result to the other blade servers or keeping the SMBUS in slave mode to respond to the requested data so that the other blade servers can retrieve the response information are entered.

[0025] Preferably, after adjusting the SMBUS to primary mode and sending the obtained parsing result to the other blade servers, the method further includes:

[0026] Return to the step of initializing the SMBUS and setting the SMBUS to slave mode.

[0027] To address the aforementioned problems, this application also provides a blade server setup apparatus, comprising:

[0028] An initialization module is used to initialize the SMBUS register and set the SMBUS to slave mode;

[0029] The receiving module is used to receive request data sent by other blade servers and confirm that the request data belongs to the IPMB protocol or the PMBUS protocol.

[0030] The parsing module is used to select either the IPMB protocol or the PMBUS protocol to parse the request data based on the confirmation result;

[0031] The sending module is activated when the requested data belongs to the IPMB protocol. It is used to adjust the SMBUS to the main mode and send the obtained parsing result to the other blade servers.

[0032] To address the aforementioned issues, this application also provides a blade server setup device, including a memory for storing computer programs;

[0033] A processor, used to execute the computer program to implement the steps of the blade server setup method as described above.

[0034] To address the aforementioned issues, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the blade server setup method described above.

[0035] The blade server configuration method provided in this application initializes the SMBUS, sets it to slave mode, receives request data sent by other blade servers, parses the request data, and confirms whether the request data belongs to the IPMB protocol or the PMBUS protocol. If the request data belongs to the IPMB protocol, the SMBUS is switched to master mode, and the parsing result is sent to other blade servers. The principle is that since both the PMBUS and IPMB protocols are based on SMBUS, and the power blade has its own SMBUS, master-slave mode selection is performed through SMBUS, which can simultaneously respond to IPMB protocol request data and SMBUS request data response requests. Compared with the original method of adding an external BMC management module, since the SMBUS in the device used in this application is built into the power blade, there is no need to add other devices, redesign the PCB, or redesign and develop the product structure layout. This saves costs while ensuring that the power blade can support both PMBUS and IPMB protocols.

[0036] The blade server setup device and computer-readable storage medium provided in this application correspond to the blade server setup method described above, and have the same beneficial effects. Attached Figure Description

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

[0038] Figure 1 A flowchart illustrating a blade server setup method provided in this application embodiment;

[0039] Figure 2 A structural diagram of a blade server system communication provided in an embodiment of this application;

[0040] Figure 3 This is a schematic diagram of a blade server setup device provided in an embodiment of this application;

[0041] Figure 4 This is a structural diagram of a blade server setup device provided in another embodiment of this application. Detailed Implementation

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

[0043] The core of this application is to provide a blade server setup method to solve the problem that current power blades need to add an external BMC to support both IPMB bus and PMBUS bus, which leads to excessive costs due to circuit redesign and PCB rework.

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

[0045] Figure 1 A flowchart illustrating a blade server setup method provided in this application embodiment is shown below. Figure 1 As shown, the method includes:

[0046] S10: Initialize the SMBUS register and set SMBUS to slave mode;

[0047] The System Management Bus (SMBUS) is a low-speed communication system used in mobile and desktop computer systems. It aims to control devices on the motherboard and collect relevant information via a low-cost and powerful bus (consisting of two wires). In this application, the basic functions of IPMB and PMBUS are implemented based on the SMBUS bus. Registers are components within the microcontroller. Registers are high-speed storage devices with limited storage capacity; they can be used to temporarily store instructions, data, and addresses. Therefore, SMBUS represents the corresponding logic unit that controls the SMBUS, playing the role of controlling the SMBUS.

[0048] Figure 2 A structural diagram of a blade server system communication provided in an embodiment of this application is shown below. Figure 2 As shown, different blades are connected via SMBUS, and the two SMBUS buses are backups of each other, as follows. Figure 2 As shown in the diagram, the power blade can communicate not only with other power blades, but also with switching blades and other functional blade servers via SMBUS. This embodiment does not impose special hardware requirements on the blade servers; generally, blade servers possess features such as… Figure 2The hardware components shown have different IPMB and PMBUS addresses for the power blades, depending on their slot number and the bus they are connected to.

[0049] It is understandable that in production and daily life, besides the SMBUS bus, there is also an I2C (Inter-Integrated Circuit) bus with similar functions. However, there are some differences in timing characteristics between SMBUS and I2C. First, SMBUS requires a certain data hold time, while the I2C bus extends the data hold time internally. In the solution provided in this application, the I2C bus can also be used to replace SMBUS for subsequent related processes. The basic principle of the solution is the same; it simply replaces SMBUS with I2C, so it will not be elaborated upon here.

[0050] It is understood that SMBUS operates in master-slave mode, meaning that in master mode it is the sender of information and in slave mode it is the receiver of information. In this embodiment, there are no restrictions on the specific data and types of SMBUS.

[0051] S11: Receive request data sent by other blade servers and confirm whether the request data belongs to the IPMB protocol or the PMBUS protocol. If the request data belongs to the PMBUS protocol, proceed to S12; if the request data belongs to the IPMB protocol, proceed to S13.

[0052] It should be noted that blade servers typically house multiple card-type server units within a chassis, achieving high availability and high density. They are a low-cost, high-availability, high-density (HAHD) server platform. Since this embodiment refers to a blade module within a blade server chassis, the specific types of other blade server modules are not limited in this embodiment. For example, they could be power blades, compute blades, storage blades, etc. Similarly, the specific type of requested data is not limited in this embodiment; it could be a single data segment sent by a single blade server, or a combination of multiple data segments sent by multiple blade servers.

[0053] It should be noted that this embodiment does not limit the specific method of the protocol for confirming the request data. It can be understood that data identification can be performed by establishing a data model, or the protocol type of the data can be confirmed by searching the transmission log, etc.

[0054] S12: Select the PMBUS protocol to parse the request data;

[0055] S13: Select the IPMB protocol to parse the request data and proceed to S14;

[0056] It should be noted that the above steps involve selecting the corresponding protocol to parse the request data based on the confirmed result. In this embodiment, the specific parsing process is not limited. It can be understood that the parsed result is also not limited, for example, the parsed result can be a program, a specific instruction or other related file, etc.

[0057] S14: Switch SMBUS to master mode and send the obtained parsing results to other blade servers.

[0058] It should be noted that this step is performed when the protocol type for requesting data is IPMB. It can be understood that after switching SMBUS to primary mode, the current power blade changes from a receiver to a sender. In this embodiment, sending the obtained parsing result to other blade servers can mean sending the parsing result or further processing of the parsing result. For example, if the parsing result is a program representing the current blade server's operating status, then in this embodiment, the power blade may send the original parsing result (i.e., the program) or it may directly send the representation result (i.e., the current power blade's operating parameters). Both are applicable in this embodiment. It should also be noted that this… In this embodiment, the recipient of the request is not limited to other blade servers. It can be the blade server that sent the request command mentioned in the previous steps. In this case, it is the feedback information for the request command. Alternatively, the parsing result can be sent to other blade servers other than the one that sent the request command. There can be one or more other blade servers in this step. For example, the computing blade server A first sends a request command to the power blade B to obtain the operating parameters of the power blade. After the power blade B processes the request command, it sends the operating parameters to the computing blade server A and the storage blade server C at the same time, thereby simultaneously achieving the function of monitoring and recording the operating parameters of the power blade B.

[0059] The blade server setup method provided in this embodiment initializes the SMBUS, sets it to slave mode, receives request data sent by other blade servers, parses the request data, and confirms whether the request data belongs to the IPMB protocol or the PMBUS protocol. If the request data belongs to the IPMB protocol, the SMBUS is adjusted to master mode, and the parsing result is sent to other blade servers. The principle is that since both the PMBUS and IPMB protocols are based on SMBUS, and the power blade has its own SMBUS, master-slave mode selection is performed through SMBUS, which can simultaneously respond to IPMB protocol request data and SMBUS request data response requests. Compared with the original method of adding an external BMC management module, since the SMBUS in the device used in this application is built into the power blade, there is no need to add other devices, redesign the PCB, or redesign and develop the product structure layout. This saves costs while ensuring that the power blade can support both PMBUS and IPMB protocols.

[0060] Considering that the power blade, when supporting the IPMB protocol, can not only receive instructions and provide feedback, but also act as a requester to send request instructions, a preferred solution is proposed here. This method further includes:

[0061] When SMBUS is in master mode, it edits the initial data using the IPMB protocol and sends the initial data to other blade servers.

[0062] It should be noted that this embodiment does not limit the specific type of other blade servers. By editing the initial data using the IPMB protocol, the data can be sent to any blade server that supports the IPMB protocol. It is understood that the initial data in this embodiment is the same type of data as the request data in the above embodiment. The request data is data edited and sent to this blade server by other blade servers as the starting point, while the initial data is data edited and sent to other blade servers by this blade server as the starting point. Furthermore, this embodiment does not limit the specific method of setting SMBUS to main mode. It is understood that it can be manually debugged by the user to switch SMBUS to main mode, or it can be the main mode entered after receiving the request data of the IPMB protocol in the above scheme.

[0063] This embodiment demonstrates that SMBUS, in master mode, can send initial request data via IPMB, thereby acting as the requester on the server and improving the overall applicability of the power blade.

[0064] Considering that after receiving the PMBUS protocol data, further processing of the request information is required in slave mode, after confirming that the request data belongs to the IPMB or PMBUS protocol, the following steps are also included:

[0065] If the requested data is in PMBUS protocol mode, then SMBUS will remain in slave mode to respond to the requested data so that other blade servers can retrieve the response information.

[0066] By responding to data in the PMBUS protocol while in slave mode, the integrity of the entire process is ensured, preventing requests from failing to retrieve processing data under the PMBUS protocol.

[0067] The above embodiments do not limit how to determine which protocol the requested data belongs to. A preferred solution is provided here, which includes confirming whether the requested data belongs to the IPMB or PMBUS protocol:

[0068] Retrieve the address from the requested data;

[0069] The system matches the SMBUS address of the requested data and determines whether the requested data belongs to the IPMB or PMBUS protocol based on the matching results.

[0070] Considering the possibility of request information errors due to information security and signal fluctuations during transmission, after receiving request data from other blade servers and before confirming whether the request data belongs to the IPMB or PMBUS protocol, the following steps are also taken:

[0071] Determine whether the request information meets the preset requirements;

[0072] If the preset requirements are met, proceed to the step of confirming whether the requested data belongs to the IPMB protocol or the PMBUS protocol;

[0073] If the preset requirements are not met, the requested data will be intercepted.

[0074] In this embodiment, the specific circumstances of the preset requirements are not limited. It can be understood that the main purpose of this embodiment is to screen whether the request information is safe and correct. For example, by filtering the address, information sent by blade servers that are not in the preset list of addresses can be intercepted. Alternatively, by reviewing whether the data log in the request information is complete, the integrity of the request data can be determined, thereby intercepting incomplete request data caused by signal fluctuations and other issues. Therefore, the preset requirements can be set based on the blade server address that sent the request information and special characters in the request information. If the preset requirements are met, the subsequent steps are performed; if the preset requirements are not met, the request is intercepted. The processing method after interception can be recorded and stored in a dedicated server for subsequent processing.

[0075] In this embodiment, preset requirements are set to review the request information. By limiting the preset requirements, the function of intercepting abnormal standard request information is achieved, thereby preventing attack information or erroneous garbled information from being sent to the power blade, ensuring the security of the power blade, and also improving the operating efficiency of the power blade.

[0076] Considering that some request data only needs to be received and does not require a response, a preferred solution is proposed. After selecting either the IPMB protocol or the PMBUS protocol to parse the request data based on the confirmation result, the solution also includes:

[0077] Determine whether a response is needed for the requested data:

[0078] If a response is required for the requested data, then according to the protocol corresponding to the requested data, the process proceeds to either switch the SMBUS to master mode and send the obtained parsing results to other blade servers, or keep the SMBUS in slave mode to respond to the requested data so that other blade servers can retrieve the response information.

[0079] During business operations, some request data only needs to be received and does not require a response, such as information receiving instructions. Therefore, after parsing the request data, it is determined whether a response is needed. If no response is needed, no response is given; if a response is needed, the subsequent response steps are entered. This prevents the power blade from processing request data that does not require a response, thereby reducing the power blade's power consumption and increasing operating efficiency.

[0080] To facilitate timely responses from the power blades to other request commands, a preferred solution is proposed. After switching SMBUS to primary mode and sending the obtained parsed results to other blade servers, the following steps are also included:

[0081] Return to the steps of initializing the SMBUS register and setting SMBUS to slave mode.

[0082] That is, after the power blade sends the parsing result, the SMBUS is switched from master mode back to slave mode, so as to ensure that the SMBUS is in slave mode when in standby mode, so as to receive the requested data as soon as possible, speed up the operation efficiency of the power blade, and thus prevent data redundancy.

[0083] In the above embodiments, the blade server setup method has been described in detail. This application also provides embodiments corresponding to the blade server setup device. It should be noted that this application describes the embodiments of the device part from two perspectives: one is based on the functional module, and the other is based on the hardware.

[0084] Figure 3This is a schematic diagram of a blade server setup device provided in an embodiment of this application, as shown below. Figure 3 The device shown includes:

[0085] Initialization module 10 is used to initialize SMBUS and set SMBUS to slave mode;

[0086] The receiving module 11 is used to receive request data sent by other blade servers and to confirm whether the request data belongs to the IPMB protocol or the PMBUS protocol.

[0087] Parsing module 12 is used to select either IPMB protocol or PMBUS protocol to parse request data based on the confirmation result;

[0088] The sending module 13 is started when the requested data belongs to the IPMB protocol. It is used to switch SMBUS to the main mode and send the obtained parsing results to other blade servers.

[0089] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus and their corresponding beneficial effects, which will not be repeated here.

[0090] Figure 4 A structural diagram of a blade server setup apparatus provided in another embodiment of this application is shown below. Figure 4 As shown, the blade server setup includes: a memory 20 for storing computer programs;

[0091] The processor 21 is used to execute computer programs to implement the steps of the blade server setup method mentioned in the above embodiments.

[0092] The blade server setup device provided in this embodiment may include, but is not limited to, smartphones, tablets, laptops, or desktop computers.

[0093] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one hardware form selected from Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as the Central Processing Unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an Artificial Intelligence (AI) processor, which handles computational operations related to machine learning.

[0094] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 20 is used to store at least the following computer program 201, which, after being loaded and executed by the processor 21, is capable of implementing the relevant steps of the blade server setup method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, and the storage method may be temporary or permanent storage. The operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, the data involved in the blade server setup method mentioned in the above embodiments.

[0095] In some embodiments, the blade server setup may further include a display screen 22, an input / output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.

[0096] Those skilled in the art will understand that Figure 4 The structure shown does not constitute a limitation on the blade server setup and may include more or fewer components than illustrated.

[0097] The blade server setup apparatus provided in this application includes a memory and a processor. When the processor executes the program stored in the memory, it can implement the following method: the blade server setup method mentioned in the above embodiments.

[0098] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus and their corresponding beneficial effects, which will not be repeated here.

[0099] Finally, this application also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps described in the above method embodiments.

[0100] It is understood that if the methods in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0101] Since the embodiments of the readable storage medium portion correspond to the embodiments of the method portion, the embodiments of the apparatus portion and their corresponding beneficial effects are described in the description of the embodiments of the method portion, and will not be repeated here.

[0102] The foregoing provides a detailed description of a blade server setup method, apparatus, and readable storage medium provided in this application. The various embodiments are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0103] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A blade server configuration method, characterized in that, include: Initialize the system management bus register and set the system management bus to slave mode; the system management bus acts as the sender in master mode and the receiver in slave mode. Receive request data sent by other blade servers and confirm that the request data belongs to the intelligent platform management bus protocol or the power management bus protocol; wherein, the power management bus protocol and the intelligent platform management bus protocol are both functions implemented based on the system management bus; Based on the confirmation result, either the intelligent platform management bus protocol or the power management bus protocol is selected to parse the request data; If the requested data belongs to the intelligent platform management bus protocol, then the system management bus is adjusted to the master mode, and the obtained parsing result is sent to the other blade servers; Also includes: When the system management bus is in the master mode, the initial data is edited using the intelligent platform management bus protocol, and the initial data is sent to the other blade servers; After confirming that the requested data belongs to the Intelligent Platform Management Bus Protocol or the Power Management Bus Protocol, the following steps are also included: If the requested data belongs to the power management bus protocol, the system management bus is kept in slave mode to respond to the requested data so that the other blade servers can retrieve the response information; The confirmation that the requested data belongs to the intelligent platform management bus protocol or the power management bus protocol includes: Retrieve the address from the requested data; The system management bus address of the requested data is matched, and the matching result determines whether the requested data belongs to the intelligent platform management bus protocol or the power management bus protocol.

2. The blade server configuration method according to claim 1, characterized in that, After receiving request data from other blade servers and before confirming that the request data belongs to the Intelligent Platform Management Bus Protocol or the Power Management Bus Protocol, the method further includes: Determine whether the requested data meets the preset requirements; If the preset requirements are met, proceed to the step of confirming that the requested data belongs to the intelligent platform management bus protocol or the power management bus protocol. If the preset requirements are not met, the request data will be intercepted.

3. The blade server configuration method according to claim 1, characterized in that, After parsing the request data by selecting the intelligent platform management bus protocol or the power management bus protocol based on the confirmation result, the method further includes: Determine whether the requested data requires a response: If the requested data requires a response, then according to the protocol corresponding to the requested data, the process proceeds to either adjusting the system management bus to master mode and sending the obtained parsing result to the other blade servers, or keeping the system management bus in slave mode to respond to the requested data so that the other blade servers can retrieve the response information.

4. The blade server configuration method according to claim 1, characterized in that, After adjusting the system management bus to master mode and sending the obtained parsing results to the other blade servers, the method further includes: Return to the step of initializing the system management bus and setting the system management bus to slave mode.

5. A blade server setting device, characterized in that, include: An initialization module is used to initialize the system management bus register and set the system management bus to slave mode; the system management bus is the sender in master mode and the receiver in slave mode. The receiving module is used to receive request data sent by other blade servers and confirm that the request data belongs to the intelligent platform management bus protocol or the power management bus protocol; wherein, the power management bus protocol and the intelligent platform management bus protocol are both functions implemented based on the system management bus; The parsing module is used to parse the request data by selecting either the intelligent platform management bus protocol or the power management bus protocol based on the confirmation result. The sending module is activated when the requested data belongs to the intelligent platform management bus protocol. It is used to adjust the system management bus to the master mode and send the obtained parsing results to the other blade servers. Also includes: When the system management bus is in the master mode, the initial data is edited using the intelligent platform management bus protocol, and the initial data is sent to the other blade servers; If the requested data belongs to the power management bus protocol, the system management bus is kept in slave mode to respond to the requested data so that the other blade servers can retrieve the response information; The confirmation that the requested data belongs to the intelligent platform management bus protocol or the power management bus protocol includes: Retrieve the address from the requested data; The system management bus address of the requested data is matched, and the matching result determines whether the requested data belongs to the intelligent platform management bus protocol or the power management bus protocol.

6. A blade server setup device, characterized in that, Includes memory used to store computer programs; A processor, configured to implement the steps of the blade server setup method as described in any one of claims 1 to 4 when executing the computer program.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the blade server setup method as described in any one of claims 1 to 4.

Images