A server

Abstract

The present application discloses a server, which relates to the field of computers and includes: a baseboard management controller, a server interface and multiple server hardware. The baseboard management controller includes: a link controller and multiple transmitters. The multiple transmitters are connected to the multiple server hardware in a one-to-one correspondence, and the server interface is connected to the link controller; the link controller is used to detect the target server hardware to be controlled from the target control request currently received by the server interface, and control the target transmitter among the multiple transmitters to establish a communication link with the server interface; the target transmitter among the multiple transmitters is used to obtain the target control request from the server interface through the communication link, and transmit the target control request to the target server hardware, which solves the technical problem that the control process of the server hardware is highly dependent on complex programmable logic devices.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computers, and in particular, to a server. Background Art

[0002] In related technologies, server hardware control relies on complex programmable logic devices (CPLDs). These devices are used to parse control instructions from the server hardware and transmit them to the corresponding server hardware. However, this CPLD-dependent server hardware control method not only increases the difficulty of system design, but also, because CPLD resources are limited, the more logical resources allocated to parsing and transmitting control instructions, the less resources are left for other server functions. The logical resources occupied by parsing and transmitting control instructions may limit the expansion capabilities of other server functions, which, to a certain extent, affects the overall performance of the server.

[0003] In response to technical issues in related technologies, such as the high dependence of the control process of server hardware on complex programmable logic devices, no effective solutions have been proposed. Summary of the Invention

[0004] An embodiment of the present application provides a server to at least solve technical problems in related technologies, such as the high dependence of the control process of server hardware on complex programmable logic devices.

[0005] According to one embodiment of the embodiments of the present application, a server is provided, comprising: a baseboard management controller, a server interface and multiple server hardware, the baseboard management controller comprising: a link controller and multiple transmitters, the multiple transmitters being connected one-to-one with the multiple server hardware, the server interface being connected to the link controller, wherein the server interface is used to receive a control request, wherein the control request is used to request execution of a corresponding control operation on the corresponding server hardware; the link controller is used to detect the target server hardware currently to be controlled from the target control request currently received by the server interface, and to control the target transmitter among the multiple transmitters to establish a communication link with the server interface, wherein the target transmitter is a transmitter connected to the target server hardware; the target transmitter among the multiple transmitters is used to obtain the target control request from the server interface via the communication link, and transmit the target control request to the target server hardware, wherein the target server hardware is used to execute the target control operation indicated by the target control request.

[0006] In this application, the link controller in the baseboard management controller can detect the target server hardware to be controlled from the control request received by the server interface, and build a communication link between the target transmitter and the server interface. The target transmitter can transmit the control request to the target server hardware through this communication link, triggering the target server hardware to perform the target control operation. That is, this solution directly builds the communication link between the target transmitter and the server interface through the link controller in the baseboard management controller, without the need to rely on complex programmable logic devices to build the communication link between the target transmitter and the server interface. Therefore, it can solve the technical problems in related technologies such as the high dependence of the control process of server hardware on complex programmable logic devices, and achieve the technical effect of reducing the dependence of the control process of server hardware on complex programmable logic devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0008] Figure 1 is an architectural diagram of an optional server according to an embodiment of the present application;

[0009] Figure 2 is a schematic diagram of an optional construction of a communication link between a target transmitter and a server interface according to an embodiment of the present application;

[0010] Figure 3 This is a schematic diagram of an optional internal routing of a transmitter according to an embodiment of the present application. Figure 1 ;

[0011] Figure 4 is a schematic diagram of an optional internal routing of a transmitter using a MUX according to an embodiment of the present application;

[0012] Figure 5 This is a schematic diagram of the internal routing of a transmitter in an optional dual-node server system according to an embodiment of the present application. Figure 1 ;

[0013] Figure 6 This is a schematic diagram of internal routing of a transmitter in an optional dual-node server system using a MUX according to an embodiment of the present application;

[0014] Figure 7 This is a schematic diagram of an optional internal routing of a transmitter according to an embodiment of the present application. Figure 2 ;

[0015] Figure 8 This is a schematic diagram of the internal routing of a transmitter in an optional dual-node server system according to an embodiment of the present application. Figure 2 . DETAILED DESCRIPTION

[0016] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0017] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0018] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0019] First, the terms involved in the embodiments of this application are explained as follows:

[0020] BMC: Baseboard Management Controller, a dedicated controller chip used to monitor and manage servers;

[0021] UART: Universal Asynchronous Receiver / Transmitter, is a commonly used serial communication interface, widely used for data transmission between embedded systems, microcontrollers and computers;

[0022] CPLD: Complex Programmable Logic Device, a complex programmable logic device, is widely used in digital circuit design to implement complex logic functions;

[0023] SOL: Serial Over LAN, is a technology for serial communication over a network (LAN), commonly used for remote management of servers or other devices. It allows users to access the serial console of a device over a network connection as if they were directly connected to the device's serial port;

[0024] BIOS: Basic Input / Output System, is the first software to run during the computer hardware startup process. It is responsible for initializing the hardware devices and guiding the operating system to start;

[0025] ESPI: Enhanced Serial Peripheral Interface, a communication protocol launched by Intel and widely used in x86 platforms for connecting to baseboard management controllers (BMCs);

[0026] SMART NIC: A smart network interface card (NIC) is an advanced network interface card (NIC) that offloads network processing tasks from the host CPU (central processing unit) by adding additional processing power and intelligent features to a traditional NIC.

[0027] I2C: Inter-Integrated Circuit, a two-wire serial bus, is a widely used serial communication protocol, mainly used for short-distance, low-speed communication between devices;

[0028] MUX: Multiplexer, a multiplexer chip, is an integrated circuit used to select one output from multiple input signals. It is widely used in digital communication systems and electronic circuit design.

[0029] Micro USB: Micro Universal Serial Bus, micro universal serial bus interface.

[0030] In this embodiment, a server is provided, including: a baseboard management controller, a server interface and multiple server hardware, the baseboard management controller includes: a link controller and multiple transmitters, the multiple transmitters are connected to the multiple server hardware in a one-to-one correspondence, and the server interface is connected to the link controller, wherein the server interface is used to receive a control request, wherein the control request is used to request to perform a corresponding control operation on the corresponding server hardware; the link controller is used to detect the target server hardware to be currently controlled from the target control request currently received by the server interface, and control the target transmitter among the multiple transmitters to establish a communication link with the server interface, wherein the target transmitter is a transmitter connected to the target server hardware; the target transmitter among the multiple transmitters is used to obtain the target control request from the server interface through the communication link, and transmit the target control request to the target server hardware, wherein the target server hardware is used to perform the target control operation indicated by the target control request.

[0031] Figure 1 This is an optional server architecture diagram according to an embodiment of the present application, such as Figure 1 As shown, taking multiple server hardware including server hardware 103, server hardware 104 and server hardware 105, and multiple transmitters including transmitter 101-1, transmitter 101-2 and transmitter 101-3 as an example, the server includes a baseboard management controller 101, a server interface 102, server hardware 103, server hardware 104 and server hardware 105, the baseboard management controller 101 includes: a link controller 101-4 and transmitter 101-1, transmitter 101-2 and transmitter 101-3, transmitter 101-1 is connected to server hardware 103, transmitter 101-2 is connected to server hardware 104, transmitter 101-3 is connected to server hardware 105, and the server interface 102 is connected to the link controller 101-4.

[0032] Optionally, in this embodiment, the server interface may be used to receive a control request, and the server interface may include a local interface (eg, an external Micro USB interface or a TYPE C interface) and a remote interface (eg, an SOL function interface).

[0033] Optionally, in this embodiment, the link controller may include a local controller and a remote controller.

[0034] Optionally, in this embodiment, the server hardware may include hardware for storing logs, executing core operations, or providing network resources, such as information storage, processors, and network devices.

[0035] Optionally, in this embodiment, the transmitter may include a transmitter for obtaining a target control request from a server interface through a communication link and transmitting the target control request to target server hardware, for example, a UART transmitter.

[0036] Optionally, in this embodiment, the control operation may include reading fault information of the server hardware, reading log information of the server hardware, or debugging and managing the server hardware, etc.

[0037] Optionally, in this embodiment, the target control request may carry, but is not limited to, the target server hardware and the target control operation performed on the target server hardware. For example, the target control request may carry, but is not limited to, the target server being a processor, and the target control operation being to read the processor's log information.

[0038] Optionally, in this embodiment, Figure 2This is a schematic diagram of an optional construction of a communication link between a target transmitter and a server interface according to an embodiment of the present application. Taking a target control request as an example of requesting to perform an operation of reading log information of server hardware 103 on server hardware 103, the server includes a baseboard management controller 101, a server interface 102, server hardware 103, server hardware 104 and server hardware 105. The baseboard management controller includes: a link controller 101-4 and a transmitter 101-1, a transmitter 101-2 and a transmitter 101-3. The transmitter 101-1 is connected to the server hardware 103, the transmitter 101-2 is connected to the server hardware 104, the transmitter 101-3 is connected to the service hardware 105, and the server interface 102 is connected to the link controller 101-4. The link controller 101-4 can detect from the target control request currently received by the server interface 102 that the target server hardware to be controlled is the server hardware 103, and control the target transmitter 101-1 to establish a communication link with the server interface 102. The target transmitter 101-1 obtains the target control request from the server interface 102 through the communication link, and transmits the target control request to the target server hardware 103. The target server hardware 103 executes an operation to read the log information of the server hardware 103.

[0039] Through the embodiments of the present application, the link controller in the baseboard management controller can detect the target server hardware to be controlled from the control request received by the server interface, and build a communication link between the target transmitter and the server interface. The target transmitter can transmit the control request to the target server hardware through this communication link, triggering the target server hardware to perform the target control operation. That is, this solution directly builds the communication link between the target transmitter and the server interface through the link controller in the baseboard management controller, without the need to rely on complex programmable logic devices to build the communication link between the target transmitter and the server interface. Therefore, it can solve the technical problems in related technologies such as the high dependence of the control process of server hardware on complex programmable logic devices, and achieve the technical effect of reducing the dependence of the control process of server hardware on complex programmable logic devices.

[0040] As an optional solution, the server interface includes a local interface, and the link controller includes a local controller, wherein the local interface is used to receive a local control request, wherein the local control request is a control request initiated locally to request to perform a corresponding control operation on the corresponding server hardware; the local controller is used to detect the target server hardware to be controlled from the target local control request currently received by the local interface, and control the establishment of a communication link between the target transmitter among multiple transmitters and the local interface.

[0041] Optionally, in this embodiment, the local interface may be a physical interface directly located on the server, such as a Micro USB interface or a Type-C interface. The local interface allows operation and maintenance personnel to directly access the server for control and management operations.

[0042] Optionally, in this embodiment, the local control request may include a request to execute operations such as reading fault information of the server hardware, reading log information of the server hardware, or debugging and managing the server hardware on the corresponding server hardware.

[0043] As an optional solution, multiple server hardware includes: a network device, a processor and an information storage device, and multiple transmitters include: a first transmitter, a second transmitter and a third transmitter, the network device is connected to the first transmitter, the processor is connected to the second transmitter, and the information storage device is connected to the third transmitter, wherein the local controller is used to control the establishment of a communication link between the first transmitter among the multiple transmitters and the local interface when the target server hardware is a network device, wherein the network device is used to provide network resources for the server; the local controller is used to control the establishment of a communication link between the second transmitter among the multiple transmitters and the local interface when the target server hardware is a processor, wherein the processor is used to run the server system in the server; the local controller is used to control the establishment of a communication link between the third transmitter among the multiple transmitters and the local interface when the target server hardware is an information storage device, wherein the information storage device is used to store controller information of the baseboard management controller, and the controller information is used to indicate the operation status of the baseboard management controller.

[0044] Optionally, in this embodiment, the network device may include a device that provides network resources for the server system. For example, the network device may include a smart network interface card (SMART NIC) or a traditional network interface card (NIC), etc.

[0045] Optionally, in this embodiment, the processor may be used to run a server system in the server, and the server system may include a BIOS.

[0046] Optionally, in this embodiment, the information storage device may be used to store controller information of the baseboard management controller. For example, the information storage device may include a solid state drive (SSD), a random access memory (RAM), and the like.

[0047] As an optional solution, the first transmitter includes a first controller and a first serial port, and the third transmitter includes a third controller and a third serial port. The first serial port in the first transmitter is connected to the network device, and the third serial port in the third transmitter is connected to the local interface. The local controller is used to control the establishment of a communication link between the first transmitter and the local interface among the multiple transmitters through the following steps: controlling the establishment of a first communication link between the third serial port and the first serial port, wherein the third serial port is used to receive a control request from the local interface, and the first communication link is used to transmit the control request received by the third serial port to the first serial port; controlling the establishment of a second communication link between the first serial port and the first controller, wherein the second communication link is used to transmit the control request received by the first serial port to the first controller, and the first controller is used to transmit the received control request to the network device; and determining the first communication link and the second communication link as the communication link between the first transmitter and the local interface.

[0048] Optionally, in this embodiment, the transmitter is divided into two parts, namely the UART controller (equivalent to the controller) and the IO interface (equivalent to the serial port). For a UART transmitter, the IO interface and the UART controller are not necessarily strongly bound, that is, an IO interface can be connected to different UART controllers.

[0049] Figure 3 This is a schematic diagram of an optional internal routing of a transmitter according to an embodiment of the present application. Figure 1 ,like Figure 3 As shown, when the target transmitter is the first transmitter, the first transmitter includes UART3 (equivalent to the first controller) and IO3 (equivalent to the first serial port), the third transmitter includes UART5 (equivalent to the third controller) and IO5 (equivalent to the third serial port), IO3 is connected to the network device connected to the SMART NIC UART interface, and IO5 is connected to the Micro USB interface or TYPEC interface (equivalent to the local interface), wherein the local controller is used to control the first transmitter among the multiple transmitters to establish a communication link with the MicroUSB interface or TYPEC interface through the following steps: controlling the establishment of a first communication link between IO5 and IO3, wherein IO5 is used to receive a control request from the Micro USB interface or TYPEC interface, and the first communication link is used to transmit the control request received by IO5 to IO3; controlling the establishment of a second communication link between IO3 and UART3, wherein the second communication link is used to transmit the control request received by IO3 to UART3, and UART3 is used to transmit the received control request to the network device; and determining the first communication link and the second communication link as the communication link between the first transmitter and the Micro USB interface or TYPEC interface.

[0050] As an optional solution, the third transmitter includes a third controller and a third serial port, and the third serial port in the third transmitter is connected to the local interface, wherein the local controller is used to control the establishment of a communication link between the second transmitter among the multiple transmitters and the local interface through the following steps: controlling the establishment of a third communication link between the third serial port and the second transmitter, wherein the third serial port is used to receive a control request from the local interface, the third communication link is used to transmit the control request received by the third serial port to the second transmitter, and the second transmitter is used to transmit the received control request to the processor; and the third communication link is determined as the communication link between the second transmitter and the local interface.

[0051] Optionally, in this embodiment, if Figure 3 As shown, when the target transmitter is the second transmitter, the third transmitter includes UART5 (equivalent to the third controller) and IO5 (equivalent to the third serial port), and IO5 in the third transmitter is connected to the Micro USB interface or TYPEC interface (equivalent to the local interface), wherein the local controller is used to control the second transmitter among the multiple transmitters to establish a communication link with the Micro USB interface or TYPEC interface through the following steps: control the establishment of a third communication link between IO5 and UART0, wherein IO5 is used to receive a control request from the Micro USB interface or TYPEC interface, the third communication link is used to transmit the control request received by IO5 to UART0, and UART0 is used to transmit the received control request to BIOS (equivalent to the processor); the third communication link is determined as the communication link between UART0 and the Micro USB interface or TYPEC interface.

[0052] As an optional solution, the third transmitter includes a third controller and a third serial port, and the third serial port in the third transmitter is connected to the local interface, wherein the local controller is used to control the establishment of a communication link between the third transmitter among the multiple transmitters and the local interface through the following steps: controlling the establishment of a fourth communication link between the third serial port and the third controller, wherein the third serial port is used to receive a control request from the local interface, the fourth communication link is used to transmit the control request received by the third serial port to the third controller, and the third controller is used to transmit the received control request to the information storage; the fourth communication link is determined as the communication link between the third transmitter and the local interface.

[0053] Optionally, in this embodiment, if Figure 3As shown, when the target transmitter is the third transmitter, the third transmitter includes UART5 (equivalent to the third controller) and IO5 (equivalent to the third serial port), and IO5 in the third transmitter is connected to the Micro USB interface or TYPEC interface (equivalent to the local interface), wherein the local controller is used to control the third transmitter among the multiple transmitters to establish a communication link with the Micro USB interface or TYPEC interface through the following steps: control the establishment of a fourth communication link between IO5 and UART5, wherein IO5 is used to receive a control request from the Micro USB interface or TYPEC interface, the fourth communication link is used to transmit the control request received by IO5 to UART5, and UART5 is used to transmit the received control request to RAM (equivalent to information storage); the fourth communication link is determined as the communication link between the third transmitter and the Micro USB interface or TYPEC interface.

[0054] When reading different UART serial port information through an external Micro USB or Type-C interface, the external Micro USB or Type-C interface is connected to the IO5 interface. The IO5 interface can be connected to the IO3 interface within the BMC, which can be connected to an external Smart NIC (equivalent to a network device), allowing the external Micro USB or Type-C interface to manage (equivalent to control) the external Smart NIC. The external Micro USB or Type-C interface is connected to the IO5 interface. The IO5 interface can be connected to the UART0 controller within the BMC, allowing the external Micro USB or Type-C interface to read BIOS log information (equivalent to control operations). The external Micro USB or Type-C interface is connected to the IO5 interface. The IO5 interface can be connected to the UART5 controller within the BMC, allowing the external Micro USB or Type-C interface to read BMC log information (equivalent to control operations). By default, the IO5 interface is connected to the UART5 controller, and the IO3 interface is connected to the UART3 controller.

[0055] It should be noted that Figure 3 The connection relationship between the local controller and the local interface is not shown. Since there may be multiple ways to connect the local controller and the local interface, for example, the local controller may be directly connected to the local interface at one end and connected to multiple transmitters at the other end, or it may be connected only to the local interface. This application does not limit this and will not be repeated in the following embodiments.

[0056] Through the embodiments of the present application, the transmitter is divided into two parts: a controller and a serial port. Multiple controllers can be connected through a single serial port, and a single serial port can serve as a communication bridge between multiple controllers, significantly reducing the complexity of the server's internal communication links while maintaining high efficiency and accuracy in signal transmission. At the same time, the local controller can control the establishment of communication links between multiple transmitters and local interfaces, and establish communication between the local interface and network devices, processors, and information storage. It no longer relies on traditional CPLDs to build and switch communication links, allowing the CPLD to have more space to perform other critical tasks, such as more complex logical operations, additional security functions, or optimized power management, thereby improving the overall performance of the server.

[0057] As an optional solution, the server further includes a first selector and a standby controller, the second transmitter includes a second controller and a second serial port, the third transmitter includes a third controller and a third serial port, the second serial port is connected to the processor through the second controller, the third serial port is connected to the information storage through the third controller, and the first selector is connected to the local interface, wherein the first selector is used to control the communication link between the local interface and the second serial port to be connected, and to control the communication link between the local interface and the third serial port to be disconnected when the first link switching signal is not received, wherein the local interface is used to transmit the processor control request to the processor through the communication link between the local interface and the second serial port. The processor control request is used to request control of the server system running in the processor; the first selector is also used to control the communication link between the local interface and the third serial port to be connected, and to control the communication link between the local interface and the second serial port to be disconnected when a first link switching signal is received, wherein the local interface is used to transmit the memory control request to the information memory through the communication link connected between the local interface and the third serial port, and the memory control request is used to request to obtain fault information stored in the information memory, and the fault information is used to indicate the cause of the baseboard management controller failure; the standby controller is used to send a first link switching signal to the first selector when the baseboard management controller fails.

[0058] Optionally, in this embodiment, the first selector can be a device with a selective conduction function, such as a MUX, and the first selector can be used to selectively establish or cut off the communication link between the local interface and the second serial port or to establish or cut off the communication link between the local interface and the third serial port.

[0059] Optionally, in this embodiment, the standby controller may be configured to send the first link switching signal to the first selector when the baseboard management controller fails. For example, the standby controller may include a CPLD or an MCU (MicroController Unit).

[0060] Optionally, in this embodiment, the first link switching signal may include a TTL (Transistor-Transistor Logic Pulse Signal) signal. For example, the first link switching signal may be a low-level pulse signal that lasts for at least a specific threshold duration, such as 100ms, to ensure that the low-level pulse signal is correctly received and processed by the first selector. The first selector may be used to control the communication link between the local interface and the third serial port to be connected, and to control the communication link between the local interface and the second serial port to be disconnected when the low-level pulse signal is received.

[0061] Optionally, in this embodiment, when a BMC (baseboard management controller) experiences an abnormality or failure (commonly referred to as a "hang" state), a BMC hang message can be sent to the backup controller via a Micro USB or Type-C interface (equivalent to a local interface), informing the backup controller of the BMC hang. Upon receiving the BMC hang message, the backup controller sends a first link switch signal to the first selector. Alternatively, the backup controller can periodically monitor the BMC's operational status, for example, using a heartbeat signal to monitor BMC operation. If the BMC response delay exceeds a predetermined threshold, or if the BMC responds without a response at all, the BMC is deemed abnormal or faulty. By sending a BMC hang message to the backup controller upon a BMC failure, or by the backup controller proactively detecting and responding to the BMC status, the system can rapidly respond to BMC failures without impacting the server's primary operations, reducing server unavailability due to BMC failures. Furthermore, by rapidly switching the communication link to an information storage device, administrators can quickly obtain detailed information before and after the BMC failure, accelerating fault location and repair, reducing server downtime, and improving service continuity.

[0062] Optionally, in this embodiment, Figure 4 is a schematic diagram of an optional internal routing of a transmitter using MUX according to an embodiment of the present application, such as Figure 4As shown, the server also includes a MUX (equivalent to a first selector) and a CPLD (equivalent to a standby controller), the second transmitter includes UART0 (equivalent to a second controller) and IO0 (equivalent to a second serial port), the third transmitter includes UART5 (equivalent to a third controller) and IO5 (equivalent to a third serial port), IO0 is connected to the BIOS (equivalent to a processor) through UART0, IO5 is connected to the RAM (equivalent to an information storage device) through UART5, and the MUX is connected to the Micro USB interface or the TYPEC interface (equivalent to a local interface), wherein the MUX is used to control the communication link between the Micro USB interface or the TYPEC interface and IO0 to be connected, and to control the communication link between the Micro USB interface or the TYPEC interface and IO5 to be disconnected when the MUX_SEL (equivalent to a first link switching signal) is not received, wherein the Micro USB interface or the TYPEC interface is used to transmit a BIOS control request to the BIOS through the communication link between the Micro USB interface or the TYPEC interface and IO0, and the BIOS control request is used to request control of the server system running in the BIOS; the MUX is also used to control the Micro USB interface or the TYPEC interface to be disconnected when the MUX_SEL (equivalent to a first link switching signal) is received. The communication link between the USB interface or TYPEC interface and IO5 is connected, and the communication link between the MicroUSB interface or TYPEC interface and IO0 is controlled to be disconnected, wherein the Micro USB interface or TYPEC interface is used to transmit the RAM control request to the RAM through the communication link between the Micro USB interface or TYPEC interface and IO5, and the RAM control request is used to request to obtain the fault information stored in the RAM, and the fault information is used to indicate the cause of the baseboard management controller failure; the CPLD is used to send MUX_SEL to the MUX in the event of a baseboard management controller failure.

[0063] As an optional solution, the first transmitter includes a first controller and a first serial port, and the first serial port in the first transmitter is connected to the network device, wherein the local controller is used to control the establishment of a communication link between the first transmitter among the multiple transmitters and the local interface through the following steps: controlling the establishment of a fifth communication link between the second serial port and the first serial port, wherein the second serial port is used to receive a control request from the local interface through the first selector, and the fifth communication link is used to transmit the control request received by the second serial port to the first serial port; controlling the establishment of a sixth communication link between the first serial port and the first controller, wherein the sixth communication link is used to transmit the control request received by the first serial port to the first controller, and the first controller is used to transmit the received control request to the network device; and determining the fifth communication link and the sixth communication link as the communication links between the first transmitter and the local interface.

[0064] Optionally, in this embodiment, if Figure 4 As shown, the first transmitter includes UART3 (equivalent to the first controller) and IO3 (equivalent to the first serial port), and IO3 in the first transmitter is connected to the network device connected to the SMART NIC UART interface, wherein the local controller is used to control the first transmitter among the multiple transmitters to establish a communication link with the Micro USB interface or TYPEC interface (equivalent to the local interface) through the following steps: controlling IO0 (equivalent to the second serial port) and IO3 (equivalent to the first serial port) to establish a fifth communication link, wherein IO0 is used to receive a control request from the MicroUSB interface or TYPEC interface through the MUX (equivalent to the first selector), and the fifth communication link is used to transmit the control request received by IO0 to IO3; controlling IO3 to establish a sixth communication link with UART3, wherein the sixth communication link is used to transmit the control request received by IO3 to UART3, and UART3 is used to transmit the received control request to the network device; and determining the fifth communication link and the sixth communication link as the communication links between the first transmitter and the Micro USB interface or TYPEC interface.

[0065] like Figure 3 The schematic diagram of the transmitter's internal routing shows an unmet requirement: the external Micro USB or Type-C interface must be connected to the UART0 controller by default to transmit the BIOS log. If the BMC hangs, it should switch to UART5 to transmit the BMC log for analysis of the cause of the BMC hang. Figure 3 The IO5 interface connected to the Micro USB or TYPEC port is connected to the UART5 controller by default, which does not meet the requirements. If the IO5 interface is set to be connected to UART0 by default, it also cannot meet the requirements, because the switching of the IO interface to different UART controllers inside the BMC is completed by the BMC itself. When the IO5 interface is set to be connected to UART0 by default, after the BMC is hung, the BMC function fails, IO5 cannot be controlled by the BMC itself to connect to the UART5 controller, and the BMC log information cannot be transmitted through IO5, thereby analyzing the cause of the BMC hanging. In order to meet this requirement, the following is proposed Figure 4In the example shown, the internal routing scheme for the transmitter uses a multiplexer. A Micro USB or Type-C port can be connected to the BMC's IO0 and IO5 ports, respectively, via a multiplexer chip. The specific implementation logic is as follows: The Micro USB or Type-C port is connected to the IO0 port via the multiplexer chip. The IO0 port is connected to the UART0 controller within the BMC, enabling reading of BIOS log information. The Micro USB or Type-C port is connected to the IO0 port via the multiplexer chip. The IO0 port is connected to the IO3 port within the BMC, which is connected to the Smart NIC (equivalent to a network device) for Smart NIC management. The Micro USB or Type-C port is connected to the IO5 port via the multiplexer chip. The IO5 port is connected to the UART5 controller within the BMC, enabling reading of BMC log information. The MUX chip's selection logic is as follows: By default, the MUX chip selects the Micro USB or Type-C port to connect to the IO0 port, thereby satisfying the default transmission of BIOS log information. If the BMC crashes, the information is sent to the CPLD via the Micro USB or Type-C port. The CPLD controls the MUX through the MUX_SEL signal, selecting the Micro USB or Type-C port to connect to the IO5 port. This is used to read BMC log information and analyze the cause of the BMC crash. Internally, the IO3 port is connected to the UART3 controller by default, the IO0 port is connected to the UART0 controller by default, and the IO5 port is connected to the UART5 controller by default.

[0066] Optionally, in this embodiment, if the user requires that the Micro USB or Type-C interface is connected to the UART5 controller by default through IO5 for reading and transmitting BMC log information, you can select Figure 3 If the user requires that the Micro USB or Type-C interface is connected to the UART0 controller via IO0 by default for reading and transmitting BIOS log information, then the following options can be selected: Figure 4 The internal routing scheme of the transmitter using MUX is shown.

[0067] Through the embodiments of the present application, a first selector and a backup controller are introduced. When the BMC hangs, the backup controller can intervene in time and send a first link switching signal to the first selector, thereby achieving seamless switching of the communication path of the local interface to the information storage device, that is, switching from the original communication with UART0 (the UART for transmitting the BIOS log) to direct communication with UART5 (the UART for transmitting the BMC log). This ensures that during a BMC failure, users or maintenance personnel can still read the BMC fault log through the local interface and accurately locate and analyze the cause of the BMC failure. Although this solution also involves the use of a backup controller, the role of the backup controller in this solution is limited to sending the first link switching signal, rather than assuming all the functions of the baseboard management controller, reducing dependence on the backup controller.

[0068] As an optional solution, when the server runs the first server system and the second server system, the multiple server hardware includes: a first processor running the first server system, a first network device providing network resources for the first server system, a second processor running the second server system, a second network device providing network resources for the second server system, and an information storage device corresponding to the baseboard management controller, and the multiple transmitters include: a first transmitter, a second transmitter, a third transmitter, a fourth transmitter and a fifth transmitter, the first network device is connected to the first transmitter, the first processor is connected to the second transmitter, the information storage device is connected to the third transmitter, the second processor is connected to the fourth transmitter, the second network device is connected to the fifth transmitter, and the local interface is connected to the third transmitter, wherein the local controller is used to detect the target server hardware to be controlled from the target local control request currently received by the local interface, and control the target transmitter among the multiple transmitters to establish a communication link with the third transmitter.

[0069] Optionally, in this embodiment, Figure 5 This is a schematic diagram of the internal routing of a transmitter in an optional dual-node server system according to an embodiment of the present application. Figure 1 ,like Figure 5As shown, in the case where the server runs the first server system and the second server system, the multiple server hardware includes: BIOS0 (equivalent to the first processor) running the first server system, a first network device connected through the SMART NIC 0 UART interface to provide network resources for the first server system, BIOS1 (equivalent to the second processor) running the second server system, a second network device providing network resources for the second server system through the SMART NIC 1 UART interface, and RAM (equivalent to information storage) corresponding to the baseboard management controller (BMC), and multiple transmitters include: a first transmitter composed of UART 3 and IO3, UART 0 (equivalent to the second transmitter), a third transmitter composed of UART 5 and IO5, UART1 (equivalent to the fourth transmitter) and a fifth transmitter composed of UART4 and IO4, the first network device is connected to UART 3 through IO3, BIOS0 is connected to UART 0, the information storage is connected to UART 5, BIOS1 is connected to UART1, the second network device is connected through IO4 and UART4, and a Micro USB or Type-C interface (equivalent to the local interface) is connected to IO5 in the third transmitter, wherein the local controller is used to receive data from Micro The target server hardware to be controlled is detected in the target local control request currently received by the USB or Type-C interface, and a communication link is established between the target transmitter in the multiple transmitters and the IO5 in the third transmitter.

[0070] As an optional solution, the third transmitter includes a third controller and a third serial port, and the local interface is connected to the third serial port of the third transmitter, wherein the local controller is used to control the target transmitter among the multiple transmitters and the third transmitter to establish a communication link in the following manner: when the target server hardware is a first network device, controlling the first transmitter to establish a communication link with the third serial port, wherein the target transmitter includes the first transmitter; or, when the target server hardware is a first processor, controlling the second transmitter to establish a communication link with the third serial port, wherein the target transmitter includes the second transmitter; or, when the target server hardware is an information storage device, controlling the third controller to establish a communication link with the third serial port, wherein the target transmitter includes the third transmitter; or, when the target server hardware is a second processor, controlling the fourth transmitter to establish a communication link with the third serial port, wherein the target transmitter includes the fourth transmitter; or, when the target server hardware is a second network device, controlling the fifth transmitter to establish a communication link with the third serial port, wherein the target transmitter includes the fifth transmitter.

[0071] Optionally, in this embodiment, if Figure 5As shown, the third transmitter includes UART5 (equivalent to a third controller) and IO5 (equivalent to a third serial port), and a Micro USB or Type-C interface (equivalent to a local interface) is connected to IO5 of the third transmitter, wherein the local controller is used to control the target transmitter among the multiple transmitters to establish a communication link with the third transmitter in the following manner: when the target server hardware is a first network device (i.e., a network device accessed through the SMART NIC 0 UART interface), control the first transmitter consisting of UART3 and IO3 to establish a communication link with IO5; or, when the target server hardware is BIOS0 (equivalent to a first processor), control the communication link between UART0 (equivalent to a second transmitter) and IO5; or, when the target server hardware is RAM (equivalent to an information storage device), control the communication link between UART5 and IO5; or, when the target server hardware is BIOS1 (equivalent to a second processor), control the communication link between UART1 (equivalent to a fourth transmitter) and IO5; or, when the target server hardware is a second network device (i.e., a network device accessed through the SMART NIC 1 UART interface), control the communication link between UART1 and IO5. In the case of a network device connected to the interface), a communication link is established between the fifth transmitter composed of UART4 and IO4 and IO5.

[0072] Optionally, in this embodiment, an internal routing solution for a transmitter in a dual-node system is proposed. A dual-node system means that one BMC chip can manage two nodes, namely two mainboards, corresponding to two BIOSes and two SmartNICs. Since there is only one BMC chip, there is still only one UART corresponding to transmitting the BMC log. When accessing different UART interfaces through the Micro USB or TYPEC interface: the Micro USB interface or TYPEC interface is connected to the IO5 interface, the IO5 interface can be connected to the IO3 interface inside the BMC, and the IO3 interface is connected to Smart NIC0, so that the Micro USB interface or TYPEC interface manages Smart NIC0 (equivalent to the first network device); the Micro USB interface or TYPEC interface is connected to the IO5 interface, and the IO5 interface can be connected to the UART0 controller inside the BMC, so that the Micro USB interface or TYPEC interface outputs the log information of BIOS0; the Micro USB interface or TYPEC interface is connected to the IO5 interface, and the IO5 interface can be connected to the UART5 controller inside the BMC, so that the Micro USB interface or TYPEC interface outputs the log information of BMC; the Micro USB interface or TYPEC interface is connected to the IO5 interface, and the IO5 interface can be connected to the UART1 controller inside the BMC, so that the Micro USB interface or TYPEC interface outputs the log information of BIOS1; the Micro USB interface or TYPEC interface is connected to the IO5 interface, and the IO5 interface can be connected to the IO4 interface inside the BMC, and the IO4 interface is connected to Smart NIC1 (equivalent to the second network device), so that the Micro The USB port or Type C port manages Smart NIC 1. Inside the BMC, the IO3 port is connected to the UART3 controller by default, the IO5 port is connected to the UART5 controller by default, and the IO4 port is connected to the UART4 controller by default.

[0073] As an optional solution, the server further includes a second selector, a third selector and a standby controller, the second transmitter further includes a second controller and a second serial port, the fourth transmitter further includes a fourth controller and a fourth serial port, the second serial port is connected to the first processor via the second controller, the fourth serial port is connected to the second processor via the fourth controller, the third serial port is connected to the information storage via the third controller, and the third selector is connected to the local interface, wherein the second selector is used to control the communication link between the third selector and the second serial port to be turned on and the communication link between the third selector and the fourth serial port to be turned off when the second link switching signal is not received; the second selector is used to control the communication link between the third selector and the second serial port to be turned on and the communication link between the third selector and the fourth serial port to be turned off when the second link switching signal is received. the third selector is used to control the communication link between the local interface and the second serial port to be connected, and to control the communication link between the local interface and the third serial port to be disconnected when the third link switching signal is not received; the third selector is used to control the communication link between the local interface and the second serial port to be connected, and to control the communication link between the local interface and the third serial port to be disconnected when the third link switching signal is received; the standby controller is used to send a third link switching signal to the third selector in the event of a baseboard management controller failure.

[0074] Optionally, in this embodiment, the second selector can be a device with a selective conduction function, such as a MUX, and the second selector can be used to selectively establish or cut off the communication link between the third selector and the second serial port, or selectively establish or cut off the communication link between the third selector and the fourth serial port.

[0075] Optionally, in this embodiment, the third selector can be a device with a selective conduction function, such as a MUX, and the third selector can be used to selectively establish or cut off the communication link between the control local interface and the second selector, or selectively establish or cut off the communication link between the local interface and the third serial port.

[0076] Optionally, in this embodiment, the standby controller may be configured to send a third link switching signal to the third selector when the baseboard management controller fails. For example, the standby controller may include a CPLD or an MCU.

[0077] Optionally, in this embodiment, the local controller in the baseboard management controller may be configured to send a second link switching signal to the second gate.

[0078] Optionally, in this embodiment, the second link switching signal may include a TTL pulse signal. For example, the second link switching signal may be a low-level pulse signal that lasts for at least a specific threshold duration, such as 100ms, to ensure that the low-level pulse signal is correctly received and processed by the second selector. The second selector may be used to control the communication link between the third selector and the fourth serial port to be connected, and to control the communication link between the third selector and the second serial port to be disconnected when receiving the low-level pulse signal.

[0079] Optionally, in this embodiment, the third link switching signal may include a TTL pulse signal. For example, the third link switching signal may be a low-level pulse signal that lasts for at least a specific threshold duration, such as 100 ms, to ensure that the low-level pulse signal is correctly received and processed by the third selector. The third selector may be used to control the communication link between the local interface and the third serial port to be connected, and to control the communication link between the local interface and the second selector to be disconnected when the low-level pulse signal is received.

[0080] As an optional solution, the local interface is used to transmit a memory control request to the information memory through the communication link between the local interface and the third serial port when the third selector receives a third link switching signal. The memory control request is used to request to obtain fault information stored in the information memory, and the fault information is used to indicate the cause of the baseboard management controller failure.

[0081] Optionally, in this embodiment, Figure 6 FIG. 1 is a schematic diagram of an optional internal routing of a transmitter in a dual-node server system using MUX according to an embodiment of the present application. Figure 6As shown, the server also includes MUX1 (equivalent to the second selector), MUX2 (equivalent to the third selector) and CPLD (equivalent to the standby controller), the second transmitter also includes UART0 (equivalent to the second controller) and IO0 (equivalent to the second serial port), the fourth transmitter also includes UART1 (equivalent to the fourth controller) and IO1 (equivalent to the fourth serial port), IO0 is connected to BIOS0 (equivalent to the first processor) through UART0, IO1 is connected to BIOS1 (equivalent to the second processor) through UART1, IO5 (equivalent to the third serial port) is connected to RAM (equivalent to information storage) through UART5 (equivalent to the third controller), MUX2 and Micro A USB or TYPEC interface (equivalent to a local interface) is connected, wherein MUX1 is used to control the communication link between MUX2 and IO0 to be connected, and to control the communication link between MUX2 and IO1 to be disconnected, if MUX1_SEL (equivalent to a second link switching signal) is not received. MUX1 is used to control the communication link between MUX2 and IO1 to be connected, and to control the communication link between MUX2 and IO0 to be disconnected, if MUX1_SEL is received. MUX2 is used to control the communication link between the Micro USB or TYPEC interface and MUX1 to be connected, and to control the communication link between the Micro USB or TYPEC interface and IO5 to be disconnected, if MUX2_SEL is not received. MUX2 is used to control the communication link between the Micro USB or TYPEC interface and IO5 to be connected, and to control the communication link between the Micro USB or TYPEC interface and MUX1 to be disconnected, if MUX2_SEL is received. The CPLD is used to send MUX2_SEL to MUX2 in the event of a baseboard management controller (BMC) failure. The Micro USB or TYPEC interface is used to transmit a RAM control request to the RAM through the communication link between the Micro USB or TYPEC interface and IO5 when MUX2 receives MUX2_SEL. The RAM control request is used to request to obtain the fault information stored in the RAM. The fault information is used to indicate the cause of the baseboard management controller failure.

[0082] Optionally, in this embodiment, in order to better understand the process of internal routing of the transmitter in the above-mentioned dual-node system using MUX, the process of internal routing of the transmitter in the above-mentioned dual-node system using MUX is described below in combination with an optional embodiment, but it is not used to limit the technical solution of the embodiment of this application.

[0083] In the internal routing scheme of the transmitter under the dual-node system using MUX, the Micro USB interface or TYPEC interface is connected to the IO0 interface through MUX2 and MUX1, the IO0 interface can be connected to the IO3 interface inside the BMC, and the IO3 interface is connected to Smart NIC0, so that the Micro USB interface or TYPEC interface manages Smart NIC0; the Micro USB interface or TYPEC interface is connected to the IO0 interface through MUX2 and MUX1, and the IO0 interface can be connected to the UART0 controller inside the BMC, so that the Micro USB interface or TYPEC interface outputs the log information of BIOS0; the Micro USB interface or TYPEC interface is connected to the IO5 interface through MUX2 and MUX1, and the IO5 interface can be connected to the UART5 controller inside the BMC, so that the Micro USB interface or TYPEC interface outputs the log information of BMC; the Micro USB interface or TYPEC interface is connected to the IO1 interface through MUX2 and MUX1, and the IO1 interface can be connected to the UART1 controller inside the BMC, so that the Micro USB interface or TYPEC interface outputs the log information of BIOS1; Micro The USB interface or Type C interface is connected to the IO1 interface through MUX2 and MUX1. The IO1 interface can be connected to the IO4 interface inside the BMC, and the IO4 interface is connected to the Smart NIC1. This allows the Micro USB interface or Type C interface to manage the Smart NIC1. The switching logic of the two MUXs is as follows: MUX1 selects IO0 and IO1 of node 0, and selects IO0 by default. The switching control is completed by BMC. MUX2 selects IO5 of node 1 and the signal after MUX1 is selected. The default selection is to the signal after MUX1 is selected. The switching is completed by CPLD. In the default state, the Micro USB interface or TYPEC interface is connected to IO0 to read the log information of BIOS0. If the log of BIOS1 needs to be read, BMC controls MUX1 to switch to IO1 through the MUX1_SEL instruction. The Micro USB interface or TYPEC interface can read the log of BIOS1. When the BMC is hung, information is sent to CPLD through the Micro USB or TYPEC port. The CPLD controls MUX2 through the MUX2_SEL signal to select the Micro USB or TYPEC port and connect it to the IO5 interface for reading the BMC log information and analyzing the cause of the BMC hang. Inside the BMC, the IO3 interface is connected to the UART3 controller by default, the IO5 interface is connected to the UART5 controller by default, the IO4 interface is connected to the UART4 controller by default, the IO0 interface is connected to the UART0 controller by default, and IO1 is connected to the UART1 controller by default.

[0084] Optionally, in this embodiment, in a dual-node server system, if the user requires that the Micro USB or Type-C interface is connected to the UART5 controller via IO5 by default for reading and transmitting BMC log information, then you can select Figure 5 The internal routing scheme of the transmitter in the dual-node server system shown in the figure is as follows. If the user requires that the Micro USB or Type-C interface is connected to the UART0 controller via IO0 by default for reading and transmitting BIOS0 log information, you can choose Figure 6 The figure shows the internal routing scheme of the transmitter in a dual-node server system using MUX.

[0085] Through the embodiments of the present application, through the collaborative work of MUX1 and MUX2, even if the BMC is hung, a direct communication link can be established between the Micro USB or TYPEC interface and the UART5 controller, so that the RAM control request can be transmitted to the RAM without hindrance, and the fault information of the BMC stored in the RAM can be obtained, which significantly improves the operation and maintenance efficiency and fault recovery speed of the server.

[0086] As an optional solution, the server interface includes a remote interface, and the link controller includes a remote controller, wherein the remote interface is used to receive a remote control request, wherein the remote control request is a control request initiated remotely to request execution of a corresponding control operation on the corresponding server hardware; the remote controller is used to detect the target server hardware to be controlled from the target remote control request currently received by the remote interface, and control the establishment of a communication link between the target transmitter among multiple transmitters and the remote interface.

[0087] Optionally, in this embodiment, the remote interface may be a virtual communication interface, such as a SOL function interface, which allows a remote user to directly access the server through a network to control and manage the server without a physical connection.

[0088] Optionally, in this embodiment, the remote control request may include a request to execute operations such as reading fault information of the server hardware, reading log information of the server hardware, or debugging and managing the server hardware on the corresponding server hardware.

[0089] As an optional solution, multiple server hardware includes: a network device, a processor and an information storage device, and multiple transmitters include: a first transmitter, a second transmitter and a third transmitter, the network device is connected to the first transmitter, the processor is connected to the second transmitter, and the information storage device is connected to the third transmitter, wherein the remote controller is used to control the establishment of a communication link between the first transmitter among the multiple transmitters and the remote interface when the target server hardware is a network device, wherein the network device is used to provide network resources for the server; the remote controller is used to control the establishment of a communication link between the second transmitter among the multiple transmitters and the remote interface when the target server hardware is a processor, wherein the processor is used to run the server system in the server; the remote controller is used to control the establishment of a communication link between the third transmitter among the multiple transmitters and the remote interface when the target server hardware is an information storage device, wherein the information storage device is used to store controller information of the baseboard management controller, and the controller information is used to indicate the operation status of the baseboard management controller.

[0090] Optionally, in this embodiment, Figure 7 This is a schematic diagram of an optional internal routing of a transmitter according to an embodiment of the present application. Figure 2 ,like Figure 7 As shown, the network device accessed through the SMART NICUART interface is connected to UART3 through IO3, the BIOS (equivalent to the processor) is connected to UART0, and the RAM (equivalent to the information storage) is connected to UART5. A UART controller of the BMC (baseboard management controller) is set as Sever tty (equivalent to the remote controller). This solution is set to the UART9 controller. UART9, namely Sever tty, can be regarded as the transit interface for UART internal routing when the BMC implements the SOL function. The SOL interface (equivalent to the remote interface) of the server can be connected to the UART3 controller (equivalent to the first transmitter), UART0 controller (equivalent to the second transmitter) and UART5 controller (equivalent to the third transmitter) through UART9, namely Sever tty. The UART3 controller is used to manage the Smart Nic (equivalent to the network device), the UART0 controller is used to receive the BIOS log transmitted with the BIOS (equivalent to the processor) through ESPI, and the UART5 controller transmits the BMC log. When implementing the SOL function of the server, the SOL interface can be connected to the UART3 controller through UART9 to read the Smart NIC information at this time. The SOL interface can be connected to the UART0 controller through UART9 to read the BIOS log information. The SOL interface can be connected to the UART5 controller through UART9 to read the BMC log information.

[0091] As an optional solution, when the server runs the first server system and the second server system, the multiple server hardware includes: a first processor running the first server system, a first network device providing network resources for the first server system, a second processor running the second server system, a second network device providing network resources for the second server system, and an information storage device corresponding to the baseboard management controller; the multiple transmitters include: a first transmitter, a second transmitter, a third transmitter, a fourth transmitter and a fifth transmitter; the first network device is connected to the first transmitter, the first processor is connected to the second transmitter, the information storage device is connected to the third transmitter, the second processor is connected to the fourth transmitter, and the second network device is connected to the fifth transmitter. The transmitter is connected, and the remote controller includes a first remote controller and a second remote controller, wherein the first remote controller is used to detect the target server hardware to be currently controlled from the target remote control request currently received by the remote interface when the target server hardware is a first network device, a first processor and an information storage device, and control the target transmitter among multiple transmitters to establish a communication link with the remote interface; the second remote controller is used to detect the target server hardware to be currently controlled from the target remote control request currently received by the remote interface when the target server hardware is a second network device, a second processor and an information storage device, and control the target transmitter among multiple transmitters to establish a communication link with the remote interface.

[0092] Optionally, in this embodiment, Figure 8 This is a schematic diagram of the internal routing of a transmitter in an optional dual-node server system according to an embodiment of the present application. Figure 2 ,like Figure 8As shown, when the server runs the first server system and the second server system, the multiple server hardware includes: BIOS0 (equivalent to the first processor) running the first server system, a first network device connected through the SMART NIC 0 UART interface to provide network resources for the first server system, BIOS1 (equivalent to the second processor) running the second server system, a second network device connected through the SMART NIC 1 UART interface to provide network resources for the second server system, and RAM (equivalent to information storage) corresponding to the baseboard management controller, and multiple transmitters include: a first transmitter composed of UART3 and IO3, UART0 (equivalent to the second transmitter), a third transmitter composed of UART5 and IO5, UART1 (equivalent to the fourth transmitter), and a fifth transmitter composed of UART4 and IO4, the first network device is connected to the first transmitter composed of UART3 and IO3, BIOS0 is connected to UART0, RAM is connected to UART5, BIOS1 is connected to UART1, the second network device is connected to UART4 through IO4, and the remote controller includes UART9 (equivalent to the fourth transmitter). A remote controller) and UART10 (equivalent to a second remote controller), wherein UART9 is used to detect the target server hardware to be currently controlled from the target remote control request currently received by the SOL interface (equivalent to the remote interface) when the target server hardware is the first network device, BIOS0 and RAM, and to control the target transmitter among the multiple transmitters to establish a communication link with the SOL interface; UART10 is used to detect the target server hardware to be currently controlled from the target remote control request currently received by the SOL interface when the target server hardware is the second network device, BIOS1 and RAM, and to control the target transmitter among the multiple transmitters to establish a communication link with the SOL interface.

[0093] Optionally, in this embodiment, when the target server hardware is an information storage device, a communication link can be established between the target transmitter among multiple transmitters and the SOL interface by controlling the first controller, or a communication link can be established between the target transmitter among multiple transmitters and the SOL interface by controlling the second controller.

[0094] Through the embodiments of the present application, the SOL function is designed with two UART controllers for Server tty. The UART controller corresponding to the Server tty (server teletypewriter) of node 0 is the UART9 controller, and the UART controller corresponding to the Server tty of node 1 is the UART10 controller. When implementing the SOL function, the SOL interface can connect to the UART3 controller via UART9 to output relevant information of Smart NIC0 (equivalent to the first network device). The SOL interface can connect to the UART0 controller via UART9 to output BIOS0 log information. The SOL interface can connect to the UART5 controller via UART9 to output BMC log information. The SOL interface can connect to the UART4 controller via UART10 to output relevant information of SmartNIC1 (equivalent to the second network device). The SOL interface can connect to the UART1 controller via UART10 to output relevant information of BIOS1. The SOL interface can achieve remote access and control of the server's internal hardware information through the UART9 and UART10 controllers without relying on the assistance of external chips, such as traditional CPLDs. This series of designs not only significantly improves the flexibility and efficiency of remote management, reduces dependence on external CPLDs, and lowers hardware design costs, but also enables switching between node 0 and node 1 in a dual-node server system, obtaining their respective BIOS logs, managing and debugging smart network cards, and obtaining BMC operation logs. It also enhances system stability and security, ensuring efficient operation and maintenance of servers in complex environments.

[0095] It should be noted that the solution of this application needs to be implemented when the BMC's UART serial port for transmitting logs allows routing within the BMC.

[0096] Through this application, a solution for internal routing of the UART interface of a BMC management chip is provided. In a single-node server scenario, by setting a UART controller inside the BMC as a signal relay, the SOL function is implemented to manage and read information of BIOS logs, BMC logs, and network card management. Then, by separating the UART controller and the IO interface, the local interface is implemented to read and manage BIOS logs, BMC logs, and network card information. In the face of a BMC failure, if there is a Micro USB interface or a TYPEC interface that needs to be connected to the UART controller that transmits the BIOS log by default, it will automatically switch to the UART controller that transmits the BMC log after the BMC fails to assist in the needs of fault analysis. This solution ensures that the Micro USB interface or the TYPEC interface can switch from connecting to the UART controller that transmits the BIOS log to connecting to the UART controller that transmits the BMC log for fault analysis through the coordinated control of the external MUX chip and the CPLD. In a dual-node server scenario, this solution configures an independent UART controller for each node, such as UART9 of node 0 and UART10 of node 1, to ensure that the SOL function can read and manage the BIOS logs, BMC logs, and network cards of different nodes respectively. At the same time, the method of separating the UART controller from the IO interface is also adopted, so that the Micro USB or Type-C interface can be connected to the UART controllers of different nodes to realize BIOS log reading, network card management and BMC log reading. In the face of BMC failure scenarios, this solution introduces the collaborative work of two external MUX chips and CPLD to cope with the situation where the Micro USB or Type-C interface needs to be connected to the UART controller that transmits the BIOS0 log by default, and automatically switches to the UART controller that transmits the BMC log after a BMC failure to assist in fault analysis. Through this application, the internal routing of the UART interface in the BMC chip is realized, without going through a programmable logic device such as CPLD or reducing the dependence on programmable logic devices such as CPLD, thereby reducing the complexity of the entire BMCUART interface system, reducing application costs, and improving reliability.

Claims

1. A server, characterized in that: include: A baseboard management controller, a server interface and multiple server hardware, the baseboard management controller includes: a link controller and multiple transmitters, multiple transmitters are connected to multiple server hardware in a one-to-one correspondence, the server interface is connected to the link controller, wherein, The server interface is configured to receive a control request, wherein the control request is configured to request execution of a corresponding control operation on the corresponding server hardware; The link controller is configured to detect the target server hardware to be controlled from the target control request currently received by the server interface, and control a target transmitter among the plurality of transmitters to establish a communication link with the server interface, wherein the target transmitter is the transmitter connected to the target server hardware; The target transmitter among the plurality of transmitters is configured to obtain the target control request from the server interface via the communication link, and transmit the target control request to the target server hardware, wherein the target server hardware is configured to execute the target control operation indicated by the target control request; The server interface includes a local interface, and the link controller includes a local controller. The local interface is used to receive a local control request, wherein the local control request is a control request initiated locally to request execution of a corresponding control operation on the corresponding server hardware. The local controller is used to detect the target server hardware to be controlled from the target local control request currently received by the local interface, and control the target transmitter among the multiple transmitters to establish a communication link with the local interface. The plurality of server hardware includes: an information storage device; the plurality of transmitters includes: a third transmitter; the information storage device is connected to the third transmitter; the local controller is configured to control the third transmitter in the plurality of transmitters to establish a communication link with the local interface when the target server hardware is the information storage device; the information storage device is configured to store controller information of the baseboard management controller; the controller information is configured to indicate an operation status of the baseboard management controller; In which, the server also includes a backup controller. In the event of a failure of the baseboard management controller, the backup controller sends information indicating that the baseboard management controller is hanging to the backup controller through the local interface. After receiving the information indicating that the baseboard management controller is hanging, the backup controller controls the third transmitter among the multiple transmitters to establish a communication link with the local interface to transmit the memory control request to the information memory, where the memory control request is used to request to obtain the fault information stored in the information memory, where the fault information is used to indicate the cause of the failure of the baseboard management controller; or, the backup controller monitors the operating status of the baseboard management controller through a heartbeat signal, and when it detects that the response delay of the baseboard management controller exceeds a predetermined threshold, or there is no response at all, controls the third transmitter to establish a communication link with the local interface to transmit the memory control request to the information memory.

2. The server according to claim 1, wherein: The plurality of server hardware further comprises: a network device, a processor, and the plurality of transmitters further comprises: a first transmitter and a second transmitter, the network device is connected to the first transmitter, and the processor is connected to the second transmitter, wherein, The local controller is further configured to control the establishment of a communication link between the first transmitter among the plurality of transmitters and the local interface when the target server hardware is the network device, wherein the network device is configured to provide network resources for the server; The local controller is further configured to control the establishment of a communication link between the second transmitter among the plurality of transmitters and the local interface when the target server hardware is the processor, wherein the processor is configured to run the server system in the server.

3. The server according to claim 2, wherein: The first transmitter includes a first controller and a first serial port, the third transmitter includes a third controller and a third serial port, the first serial port in the first transmitter is connected to the network device, and the third serial port in the third transmitter is connected to the local interface, wherein, The local controller is configured to control the first transmitter among the plurality of transmitters to establish a communication link with the local interface through the following steps: controlling a first communication link to be established between the third serial port and the first serial port, wherein the third serial port is used to receive a control request from the local interface, and the first communication link is used to transmit the control request received by the third serial port to the first serial port; controlling establishment of a second communication link between the first serial port and the first controller, wherein the second communication link is used to transmit a control request received by the first serial port to the first controller, and the first controller is used to transmit the received control request to the network device; The first communication link and the second communication link are determined as communication links between the first transmitter and the local interface.

4. The server according to claim 2, wherein: The third transmitter includes a third controller and a third serial port, and the third serial port in the third transmitter is connected to the local interface, wherein: The local controller is configured to control the second transmitter among the plurality of transmitters to establish a communication link with the local interface through the following steps: controlling the establishment of a third communication link between the third serial port and the second transmitter, wherein the third serial port is used to receive a control request from the local interface, the third communication link is used to transmit the control request received by the third serial port to the second transmitter, and the second transmitter is used to transmit the received control request to the processor; The third communication link is determined to be a communication link between the second transmitter and the local interface.

5. The server according to claim 2, wherein: The third transmitter includes a third controller and a third serial port, and the third serial port in the third transmitter is connected to the local interface, wherein: The local controller is configured to control the third transmitter among the plurality of transmitters to establish a communication link with the local interface through the following steps: controlling a fourth communication link to be established between the third serial port and the third controller, wherein the third serial port is used to receive a control request from the local interface, the fourth communication link is used to transmit the control request received by the third serial port to the third controller, and the third controller is used to transmit the received control request to the information storage; The fourth communication link is determined to be a communication link between the third transmitter and the local interface.

6. The server according to claim 2, wherein: The server further includes a first selector and a standby controller, the second transmitter includes a second controller and a second serial port, the third transmitter includes a third controller and a third serial port, the second serial port is connected to the processor via the second controller, the third serial port is connected to the information storage via the third controller, and the first selector is connected to the local interface, wherein: The first selector is configured to, when not receiving the first link switching signal, control the communication link between the local interface and the second serial port to be connected, and control the communication link between the local interface and the third serial port to be disconnected, wherein the local interface is configured to transmit the processor control request to the processor via the communication link connected between the local interface and the second serial port, wherein the processor control request is used to request control of the server system running on the processor; The first selector is further configured to, upon receiving the first link switching signal, control the communication link between the local interface and the third serial port to be connected, and control the communication link between the local interface and the second serial port to be disconnected, wherein the local interface is configured to transmit the memory control request to the information memory via the communication link connected between the local interface and the third serial port, wherein the memory control request is configured to request to obtain fault information stored in the information memory, wherein the fault information is configured to indicate a cause of a fault of the baseboard management controller; The standby controller is configured to send the first link switching signal to the first gate when the baseboard management controller fails.

7. The server according to claim 6, wherein: The first transmitter includes a first controller and a first serial port, and the first serial port in the first transmitter is connected to the network device, wherein: The local controller is configured to control the first transmitter among the plurality of transmitters to establish a communication link with the local interface through the following steps: controlling the establishment of a fifth communication link between the second serial port and the first serial port, wherein the second serial port is used to receive a control request from the local interface through the first selector, and the fifth communication link is used to transmit the control request received by the second serial port to the first serial port; controlling a sixth communication link to be established between the first serial port and the first controller, wherein the sixth communication link is used to transmit a control request received by the first serial port to the first controller, and the first controller is used to transmit the received control request to the network device; The fifth communication link and the sixth communication link are determined as communication links between the first transmitter and the local interface.

8. The server according to claim 1, wherein: In the case where the server runs a first server system and a second server system, the multiple server hardware includes: a first processor running the first server system, a first network device providing network resources for the first server system, a second processor running the second server system, a second network device providing network resources for the second server system, and an information storage device corresponding to the baseboard management controller; the multiple transmitters include: a first transmitter, a second transmitter, a third transmitter, a fourth transmitter and a fifth transmitter; the first network device is connected to the first transmitter, the first processor is connected to the second transmitter, the information storage device is connected to the third transmitter, the second processor is connected to the fourth transmitter, the second network device is connected to the fifth transmitter, and the local interface is connected to the third transmitter, wherein, The local controller is configured to detect the target server hardware to be controlled from the target local control request currently received by the local interface, and control the target transmitter among the plurality of transmitters to establish a communication link with the third transmitter.

9. The server according to claim 8, wherein: The third transmitter includes a third controller and a third serial port, and the local interface is connected to the third serial port of the third transmitter. The local controller is configured to control the target transmitter among the plurality of transmitters to establish a communication link with the third transmitter in the following manner: In a case where the target server hardware is the first network device, controlling the first transmitter to establish a communication link with the third serial port, wherein the target transmitter includes the first transmitter; or When the target server hardware is the first processor, controlling the second transmitter to establish a communication link with the third serial port, wherein the target transmitter includes the second transmitter; or In the case where the target server hardware is the information storage, controlling the third controller to establish a communication link with the third serial port, wherein the target transmitter includes the third transmitter; or In a case where the target server hardware is the second processor, controlling the fourth transmitter to establish a communication link with the third serial port, wherein the target transmitter includes the fourth transmitter; or In a case where the target server hardware is the second network device, a communication link is controlled to be established between the fifth transmitter and the third serial port, wherein the target transmitter includes the fifth transmitter.

10. The server according to claim 9, wherein: The server further includes a second selector, a third selector, and a standby controller. The second transmitter further includes a second controller and a second serial port. The fourth transmitter further includes a fourth controller and a fourth serial port. The second serial port is connected to the first processor via the second controller. The fourth serial port is connected to the second processor via the fourth controller. The third serial port is connected to the information storage via the third controller. The third selector is connected to the local interface. The second gate is configured to control the communication link between the third gate and the second serial port to be connected, and control the communication link between the third gate and the fourth serial port to be disconnected when the second link switching signal is not received; The second gate is configured to control the communication link between the third gate and the fourth serial port to be connected, and control the communication link between the third gate and the second serial port to be disconnected, upon receiving the second link switching signal; The third selector is configured to control the communication link between the local interface and the second selector to be connected, and control the communication link between the local interface and the third serial port to be disconnected when the third link switching signal is not received; The third gate is configured to control the communication link between the local interface and the third serial port to be connected, and control the communication link between the local interface and the second gate to be disconnected, upon receiving a third link switching signal; The standby controller is configured to send the third link switching signal to the third gate when the baseboard management controller fails.

11. The server according to claim 10, wherein: The local interface is used to transmit the memory control request to the information memory through the communication link between the local interface and the third serial port when the third selector receives the third link switching signal, wherein the memory control request is used to request to obtain fault information stored in the information memory, and the fault information is used to indicate the cause of the failure of the baseboard management controller.

12. The server according to claim 1, wherein: The server interface includes a remote interface, and the link controller includes a remote controller, wherein The remote interface is configured to receive a remote control request, wherein the remote control request is a control request initiated remotely to request execution of a corresponding control operation on the corresponding server hardware; The remote controller is used to detect the target server hardware to be controlled from the target remote control request currently received by the remote interface, and control the target transmitter among the multiple transmitters to establish a communication link with the remote interface.

13. The server according to claim 12, wherein: The plurality of server hardware includes: a network device, a processor and an information storage device; the plurality of transmitters include: a first transmitter, a second transmitter and a third transmitter; the network device is connected to the first transmitter; the processor is connected to the second transmitter; the information storage device is connected to the third transmitter; wherein, The remote controller is configured to control the establishment of a communication link between the first transmitter among the plurality of transmitters and the remote interface when the target server hardware is the network device, wherein the network device is configured to provide network resources for the server; The remote controller is configured to control the second transmitter among the plurality of transmitters to establish a communication link with the remote interface when the target server hardware is the processor, wherein the processor is configured to operate a server system in the server; The remote controller is used to control the third transmitter among the multiple transmitters to establish a communication link with the remote interface when the target server hardware is the information storage device, wherein the information storage device is used to store controller information of the baseboard management controller, and the controller information is used to indicate the operation status of the baseboard management controller.

14. The server according to claim 12, wherein: In the case where the server runs a first server system and a second server system, the multiple server hardware includes: a first processor running the first server system, a first network device providing network resources for the first server system, a second processor running the second server system, a second network device providing network resources for the second server system, and an information storage device corresponding to the baseboard management controller; the multiple transmitters include: a first transmitter, a second transmitter, a third transmitter, a fourth transmitter and a fifth transmitter; the first network device is connected to the first transmitter, the first processor is connected to the second transmitter, the information storage device is connected to the third transmitter, the second processor is connected to the fourth transmitter, the second network device is connected to the fifth transmitter; the remote controller includes a first remote controller and a second remote controller, wherein, The first remote controller is configured to, when the target server hardware is the first network device, the first processor, and the information storage device, detect the target server hardware to be controlled from the target remote control request currently received by the remote interface, and control the target transmitter among the plurality of transmitters to establish a communication link with the remote interface; The second remote controller is used to detect the target server hardware to be controlled from the target remote control request currently received by the remote interface when the target server hardware is the second network device, the second processor and the information storage device, and to control the target transmitter among the multiple transmitters to establish a communication link with the remote interface.

Images