CN116841944A - Out-of-band management system of multi-platform fusion server - Google Patents
Out-of-band management system of multi-platform fusion server Download PDFInfo
- Publication number
- CN116841944A CN116841944A CN202310771604.5A CN202310771604A CN116841944A CN 116841944 A CN116841944 A CN 116841944A CN 202310771604 A CN202310771604 A CN 202310771604A CN 116841944 A CN116841944 A CN 116841944A
- Authority
- CN
- China
- Prior art keywords
- message
- interface
- ipmb
- bmc
- serial
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000004927 fusion Effects 0.000 title claims abstract description 15
- 238000013461 design Methods 0.000 claims abstract description 9
- 238000000034 method Methods 0.000 claims description 45
- 238000012545 processing Methods 0.000 claims description 38
- 230000004044 response Effects 0.000 claims description 36
- 230000010365 information processing Effects 0.000 claims description 29
- 230000006870 function Effects 0.000 claims description 9
- 238000012795 verification Methods 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 5
- 238000004891 communication Methods 0.000 claims description 4
- 230000008571 general function Effects 0.000 claims description 3
- 108010028984 3-isopropylmalate dehydratase Proteins 0.000 claims 3
- 230000036541 health Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
- G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F2213/0016—Inter-integrated circuit (I2C)
Abstract
The invention relates to a multi-platform fusion server out-of-band management system, and belongs to the field of server management. According to the invention, the BMC and the service module are mutually independent in the design of the single-board hardware, so that independent power supply of the BMC is ensured, and the BMC is preferentially electrified and started. The single board in the case comprises: the power panel, the function panel and the computing panel, wherein the power panel and the function panel select a GD32 singlechip as a slave BMC, one computing panel selects an AST2400 chip as a master BMC, and the rest computing panels select AST2400 chips as slave BMCs. BMCs of the individual boards are interconnected by an IPMB bus. The master BMC is connected to the management computer through a serial port or a network port. The server finally interconnects the BMCs of different hardware platforms on each single board in a compatible mode, and gathers the information of all the slave BMCs to the master BMC in a mode of one master and multiple slaves, so that a manager can inquire the management information of all the boards in the server only through the master BMC, the topology is clear, and the fault position can be rapidly positioned.
Description
Technical Field
The invention belongs to the field of server management, and particularly relates to a multi-platform fusion server out-of-band management system.
Background
The fault location of the server depends on real-time monitoring of the health state of the server, the traditional health management system adopts an in-band management mode, the service and the management are not independent, the management system occupies the resources of the service system, the fault of the service system affects the management system, and the fault analysis is difficult, so that a design method of out-of-band management needs to be introduced.
The core idea of out-of-band management is to isolate the main service module from the management module on the software and hardware, and the main service module and the management module run completely independently and are not affected by each other. Wherein the management module is called BMC. BMC (Baseboard Management Controller) baseboard management controller is a core element of each single board management in the server, and is responsible for the functions of respective board state monitoring, alarm log, power management, remote control and the like. The BMCs of the boards communicate with each other in the server via IPMB (Intelligent Platform Management Bus) intelligent platform management bus (I2C based serial bus), and the communication protocol complies with IPMI (Intelligent Platform Management Interface) intelligent platform management interface standard.
Disclosure of Invention
First, the technical problem to be solved
The technical problem to be solved by the invention is how to provide a multi-platform fusion server out-of-band management system so as to solve the problems that the service is not independent of management, and the management system is not available when the service system fails, so that the failure cannot be positioned, and the BMCs of various platforms cannot be compatible with each other.
(II) technical scheme
In order to solve the technical problems, the invention provides a multi-platform fusion server out-of-band management system, which enables BMC and a service module to be mutually independent on the design of single board hardware, ensures independent power supply of the BMC and is preferentially powered on and started;
the single board in the chassis of the system comprises: the power panel, the function panel and the computing panel select GD32 single chip microcomputer as a slave BMC, one computing panel selects AST2400 chip as a master BMC, and the rest computing panels select AST2400 chip as the slave BMC; BMCs of the single boards are interconnected through an IPMB bus, and a master BMC is connected to the management computer through a serial port or a network port;
the firmware of the master BMC and the firmware of the slave BMC realize general functions; for the requirements of interface communication protocols, the main BMC firmware is required to realize IPMI2.0 standard protocols of IPMB, serial port and network port interfaces, and can be used as bridging equipment to forward an upper computer protocol message received by the serial port or the network port of the main BMC to a corresponding auxiliary BMC according to an I2C address; the slave BMC then only needs to implement the standard protocol for the IPMB interface.
Further, the master BMC is connected to the local management computer through a serial port.
Further, the master BMC is connected to the remote management computer through a portal.
Further, the computing main board selects an AST2400 chip, leads out an I2C, VGA, USB, LPC, ENET interface, is used as a display card, and performs iKVM remote desktop control.
Further, the GD32 singlechip leads out an I2C, serial interface.
Further, the general functions include: temperature voltage monitoring, fan control, and power management.
Further, the slave BMC firmware architecture adopts a multitasking mode.
Further, the workflow from the BMC includes the following steps:
s21, initializing an IPMB interface message receiving thread RecvIPMBPkt, IPMB interface message processing thread IPMB bifcTask, an information processing core thread MsgHndlr, IPMB interface request message queue IPMB_primary_IFC_ Q, IPMB interface response message queue IPMB_primary_RES_Q, an information processing queue MSG_HNDLR_Q, a dequeuing method GetMsg and an enqueuing method PostMsg;
s22, after receiving the message, the IPMB interface message receiving thread RecIPMB BPkt can perform simple verification processing according to the protocol header of the interface, and if the message is correct, an enqueuing method PostMsg is called to add the message into an IPMB interface request message queue IPMB_PRIMARY_IFC_Q;
s23, then the IPMB interface message processing thread can call a dequeuing method GetMsg to acquire the message from an IPMB interface request message queue IPMB_primary_IFC_Q, and call an enqueuing method PostMsg to add the message into the information processing queue MSG_HNDLR_Q, and then the IPMB interface message processing thread IPMB interface can block waiting for a response message on the IPMB interface response message queue IPMB_primary_RES_Q;
s24, calling a dequeue method GetMsg by the information processing core thread MsgHndlr to obtain a message from an information processing queue MSG_HNDLR_Q, processing the message according to an IPMI protocol, and calling a dequeue method PostMsg to add the generated response message to an IPMB interface response message queue IPMB_primary_RES_Q;
s25, finally, the IPMB interface message processing thread IPMB interface message processing task sends out the response message.
Furthermore, the main BMC firmware architecture adopts a multi-task mode, and needs to implement IPMB, serial port and Internet port IPMI protocols, wherein the work flow of the IPMB interface is the same as the specific flow of the slave BMC.
Further, the serial port/network port specific workflow includes the following steps:
s31, initializing a SERIAL port/network port interface message receiving thread RecvSerialPkt/RecvNetPkt, a SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask, an information processing core thread MsgHndlr, a SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q, a SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q, an information processing queue MSG_HNDLR_Q, a queuing method GetMsg and an enqueuing method PostMsg;
s32, after receiving the message, the message receiving thread RecvSerialPkt/RecvNetPkt of the SERIAL port/network port interface can carry out simple verification processing according to the protocol header of the interface, and if the message is correct, the enqueuing method PostMsg is called to add the message into the corresponding SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q;
s33, then, a SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask calls a queuing method GetMsg to acquire the message from a corresponding SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q, calls an enqueuing method PostMsg to add the message to an information processing queue MSG_HNDLR_Q, and then, the SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask waits for a response message on a corresponding SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q;
s34, calling a dequeue method GetMsg by an information processing core thread MsgHndlr to obtain a message from an information processing queue MSG_HNDLR_Q, processing the message according to an IPMI protocol, and calling an enqueue method PostMsg to add the generated response message to a corresponding SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q;
and S35, finally, the corresponding serial interface/network interface message processing thread serialfctask/NetIfctask sends out a response message.
(III) beneficial effects
The invention provides a multi-platform fusion server out-of-band management system, which aims to solve the problems, and uses the design idea of out-of-band management for each single board in a server, separates management from service, ensures independent power supply, and selects a BMC platform suitable for self according to service functions and management requirements. And finally, the server compatibly interconnects BMCs of different hardware platforms on each single board, and in a form of one master and multiple slaves, the information of all the slaves is collected to the master BMC, so that a manager can inquire the management information of all the boards in the server only through the master BMC, the topology is clear, and the fault position can be rapidly positioned.
The invention can realize real out-of-band management, and the management system can independently operate and monitor the operation state of the service system. The BMC module can be selected according to different requirements, the computing main board selects an AST2400 platform, and the computing main board can go out to interfaces such as I2C, VGA, USB, LPC, ENET, can be used as a display card and performs iKVM remote desktop control; other functional board cards can select GD32 MCU platform, and it can go out I2C, serial interface, and the design is simple, and the cost is lower.
Drawings
FIG. 1 is a hardware topology of the present invention;
FIG. 2 is a schematic diagram of a slave BMC software design architecture according to the present invention;
FIG. 3 is a block diagram of a master BMC software design architecture according to the present invention.
Detailed Description
To make the objects, contents and advantages of the present invention more apparent, the following detailed description of the present invention will be given with reference to the accompanying drawings and examples.
The invention belongs to the field of server management, and particularly relates to a server out-of-band health management and remote control system integrating a GD32 MCU platform and an AST2400 platform.
Fig. 1 is a hardware topology architecture of the present invention, in which a single board hardware is designed to enable a BMC and a service module to be independent of each other, ensure independent power supply of the BMC, and give priority to power-on startup. The single board in the case comprises: the power panel, the function panel and the computing panel, wherein the power panel and the function panel select a GD32 singlechip as a slave BMC, one computing panel selects an AST2400 chip as a master BMC, and the rest computing panels select AST2400 chips as slave BMCs. BMCs of the individual boards are interconnected by an IPMB bus. The master BMC is connected to the management computer through a serial port or a network port.
Further, the master BMC is connected to the local management computer through a serial port.
Further, the master BMC is connected to the remote management computer through a portal.
Further, the computing main board selects an AST2400 platform, can go out of interfaces such as I2C, VGA, USB, LPC, ENET, can be used as a display card, and performs iKVM remote desktop control; other functional board cards can select GD32 MCU platform, and it can go out I2C, serial interface, and the design is simple, and the cost is lower.
The firmware of the master BMC and the slave BMC are required to realize the common functions of temperature and voltage monitoring, fan control, power management and the like. For the requirements of interface communication protocols, the master BMC and the slave BMC are different, the master BMC firmware is required to realize the IPMB, serial port, network port and other interfaces IPMI2.0 standard protocols, and can be used as bridging equipment to forward the upper computer protocol messages received by the serial port or the network port to the corresponding slave BMC according to the I2C address, and the slave BMC only needs to realize the IPMB interface standard protocol.
FIG. 2 is a slave BMC software design architecture of the present invention, employing a multi-tasking mode from the BMC firmware architecture. The specific workflow comprises the following steps:
s21, initializing an IPMB interface message receiving thread RecvIPMBPkt, IPMB interface message processing thread IPMB bifcTask, an information processing core thread MsgHndlr, IPMB interface request message queue IPMB_PRIMARY_IFC_ Q, IPMB interface response message queue IPMB_PRIMARY_RES_Q, an information processing queue MSG_HNDLR_Q, a dequeuing method GetMsg and an enqueuing method PostMsg.
S22, after receiving the message, the IPMB interface message receiving thread RecIPMB BPkt can perform simple verification processing according to the protocol header of the interface, and if the message is correct, an enqueuing method PostMsg is called to add the message into an IPMB interface request message queue IPMB_PRIMARY_IFC_Q.
S23, then the IPMB interface message processing thread IPMB switch calls a dequeuing method GetMsg to acquire the message from the IPMB interface request message queue IPMB_primary_IFC_Q, and calls an enqueuing method PostMsg to add the message to the message processing queue MSG_HNDLR_Q, and then the IPMB interface message processing thread IPMB switch blocks waiting for a response message on the IPMB interface response message queue IPMB_primary_RES_Q.
S24, the information processing core thread MsgHndlr calls a dequeue method GetMsg to obtain a message from an information processing queue MSG_HNDLR_Q, processes the message according to an IPMI protocol, and calls a dequeue method PostMsg to add the generated response message to an IPMB interface response message queue IPMB_primary_RES_Q.
S25, finally, the IPMB interface message processing thread IPMB interface message processing task sends out the response message.
FIG. 3 is a software design architecture of a master BMC according to the present invention, where the master BMC firmware architecture adopts a multi-tasking mode, and needs to implement IPMB, serial port, and Internet port IPMI protocols, where the workflow of the IPMB interface is the same as the specific flow of the slave BMC.
The serial port/network port specific workflow comprises the following steps:
s31, initializing a SERIAL port/network port interface message receiving thread RecvSerialPkt/RecvNetPkt, a SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask, an information processing core thread MsgHndlr, a SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q, a SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q, an information processing queue MSG_HNDLR_Q, a queuing method GetMsg and an enqueuing method PostMsg.
S32, after receiving the message, the message receiving thread RecvSerialPkt/RecvNetPkt of the SERIAL port/network port interface can carry out simple verification processing according to the protocol header of the interface, and if the message is correct, the enqueuing method PostMsg is called to add the message into the corresponding SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q.
S33, then the SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask calls a queuing method GetMsg to acquire the message from a corresponding SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q, calls an enqueuing method PostMsg to add the message to an information processing queue MSG_HNDLR_Q, and then the SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask waits for a response message on a corresponding SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q.
S34, the information processing core thread MsgHndlr calls a queuing method GetMsg to obtain a message from an information processing queue MSG_HNDLR_Q, processes the message according to an IPMI protocol, and calls a queuing method PostMsg to add the generated response message to a corresponding SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q.
And S35, finally, the corresponding serial interface/network interface message processing thread serialfctask/NetIfctask sends out a response message.
In order to solve the above problem, the design concept of out-of-band management is used for each single board in the server, so that management and service are separated, and a BMC platform suitable for itself is selected according to service functions and management requirements. And finally, the server compatibly interconnects BMCs of different hardware platforms on each single board, and in a form of one master and multiple slaves, the information of all the slaves is collected to the master BMC, so that a manager can inquire the management information of all the boards in the server only through the master BMC, the topology is clear, and the fault position can be rapidly positioned.
The invention can realize real out-of-band management, and the management system can independently operate and monitor the operation state of the service system. The BMC module can be selected according to different requirements, the computing main board selects an AST2400 platform, and the computing main board can go out to interfaces such as I2C, VGA, USB, LPC, ENET, can be used as a display card and performs iKVM remote desktop control; other functional board cards can select GD32 MCU platform, and it can go out I2C, serial interface, and the design is simple, and the cost is lower.
The foregoing is merely a preferred embodiment of the present invention, and it should be noted that modifications and variations could be made by those skilled in the art without departing from the technical principles of the present invention, and such modifications and variations should also be regarded as being within the scope of the invention.
Claims (10)
1. The multi-platform fusion server out-of-band management system is characterized in that the system enables a BMC and a service module to be mutually independent on the design of single-board hardware, ensures independent power supply of the BMC and is preferentially electrified and started;
the single board in the chassis of the system comprises: the power panel, the function panel and the computing panel select GD32 single chip microcomputer as a slave BMC, one computing panel selects AST2400 chip as a master BMC, and the rest computing panels select AST2400 chip as the slave BMC; BMCs of the single boards are interconnected through an IPMB bus, and a master BMC is connected to the management computer through a serial port or a network port;
the firmware of the master BMC and the firmware of the slave BMC realize general functions; for the requirements of interface communication protocols, the main BMC firmware is required to realize IPMI2.0 standard protocols of IPMB, serial port and network port interfaces, and can be used as bridging equipment to forward an upper computer protocol message received by the serial port or the network port of the main BMC to a corresponding auxiliary BMC according to an I2C address; the slave BMC then only needs to implement the standard protocol for the IPMB interface.
2. The multi-platform fusion server out-of-band management system of claim 1, wherein the master BMC is connected to the local management computer through a serial port.
3. The multi-platform fusion server out-of-band management system of claim 1, wherein the master BMC is connected to the remote management computer through a portal.
4. The multi-platform fusion server out-of-band management system of claim 1, wherein the computing motherboard selects an AST2400 chip, draws out an I2C, VGA, USB, LPC, ENET interface, uses it as a graphics card, and performs iKVM remote desktop control.
5. The multi-platform fusion server out-of-band management system of claim 1, wherein the GD32 single-chip microcomputer brings out an I2C, serial interface.
6. The multi-platform fusion server out-of-band management system of claim 1, wherein the generic functions comprise: temperature voltage monitoring, fan control, and power management.
7. The multi-platform fusion server out-of-band management system of any of claims 1-6, wherein the slave BMC firmware architecture employs a multi-tasking mode.
8. The multi-platform converged server out-of-band management system of claim 7, wherein the workflow from the BMC comprises the steps of:
s21, initializing an IPMB interface message receiving thread RecvIPMBPkt, IPMB interface message processing thread IPMB bifcTask, an information processing core thread MsgHndlr, IPMB interface request message queue IPMB_primary_IFC_ Q, IPMB interface response message queue IPMB_primary_RES_Q, an information processing queue MSG_HNDLR_Q, a dequeuing method GetMsg and an enqueuing method PostMsg;
s22, after receiving the message, the IPMB interface message receiving thread RecIPMB BPkt can perform simple verification processing according to the protocol header of the interface, and if the message is correct, an enqueuing method PostMsg is called to add the message into an IPMB interface request message queue IPMB_PRIMARY_IFC_Q;
s23, then the IPMB interface message processing thread can call a dequeuing method GetMsg to acquire the message from an IPMB interface request message queue IPMB_primary_IFC_Q, and call an enqueuing method PostMsg to add the message into the information processing queue MSG_HNDLR_Q, and then the IPMB interface message processing thread IPMB interface can block waiting for a response message on the IPMB interface response message queue IPMB_primary_RES_Q;
s24, calling a dequeue method GetMsg by the information processing core thread MsgHndlr to obtain a message from an information processing queue MSG_HNDLR_Q, processing the message according to an IPMI protocol, and calling a dequeue method PostMsg to add the generated response message to an IPMB interface response message queue IPMB_primary_RES_Q;
s25, finally, the IPMB interface message processing thread IPMB interface message processing task sends out the response message.
9. The multi-platform fusion server out-of-band management system of claim 8, wherein the master BMC firmware architecture adopts a multi-tasking mode requiring implementation of IPMB, serial, and Internet IPMI protocols, wherein the workflow of the IPMB interface is the same as the specific flow of the slave BMC.
10. The multi-platform converged server out-of-band management system of claim 9, wherein the serial port/web port specific workflow comprises the steps of:
s31, initializing a SERIAL port/network port interface message receiving thread RecvSerialPkt/RecvNetPkt, a SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask, an information processing core thread MsgHndlr, a SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q, a SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q, an information processing queue MSG_HNDLR_Q, a queuing method GetMsg and an enqueuing method PostMsg;
s32, after receiving the message, the message receiving thread RecvSerialPkt/RecvNetPkt of the SERIAL port/network port interface can carry out simple verification processing according to the protocol header of the interface, and if the message is correct, the enqueuing method PostMsg is called to add the message into the corresponding SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q;
s33, then, a SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask calls a queuing method GetMsg to acquire the message from a corresponding SERIAL port/network port interface request message queue SERIAL_IFC_Q/NET_IFC_Q, calls an enqueuing method PostMsg to add the message to an information processing queue MSG_HNDLR_Q, and then, the SERIAL port/network port interface message processing thread SerialIfcTask/NetIfcTask waits for a response message on a corresponding SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q;
s34, calling a dequeue method GetMsg by an information processing core thread MsgHndlr to obtain a message from an information processing queue MSG_HNDLR_Q, processing the message according to an IPMI protocol, and calling an enqueue method PostMsg to add the generated response message to a corresponding SERIAL port/network port interface response message queue SERIAL_RES_Q/NET_RES_Q;
and S35, finally, the corresponding serial interface/network interface message processing thread serialfctask/NetIfctask sends out a response message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310771604.5A CN116841944A (en) | 2023-06-28 | 2023-06-28 | Out-of-band management system of multi-platform fusion server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310771604.5A CN116841944A (en) | 2023-06-28 | 2023-06-28 | Out-of-band management system of multi-platform fusion server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116841944A true CN116841944A (en) | 2023-10-03 |
Family
ID=88159279
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310771604.5A Pending CN116841944A (en) | 2023-06-28 | 2023-06-28 | Out-of-band management system of multi-platform fusion server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116841944A (en) |
-
2023
- 2023-06-28 CN CN202310771604.5A patent/CN116841944A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7139861B2 (en) | Input/output unit access switching system and method | |
| US7305494B2 (en) | Multiplexed computer peripheral device connection switching interface | |
| US20080043769A1 (en) | Clustering system and system management architecture thereof | |
| US7966402B2 (en) | Switch to selectively couple any of a plurality of video modules to any of a plurality of blades | |
| US20070233833A1 (en) | Data transmission system for electronic devices with server units | |
| US8397053B2 (en) | Multi-motherboard server system | |
| CN101739287A (en) | Device, system and method for managing virtual machines | |
| CN115794313B (en) | Virtual machine debugging method, system, electronic device and storage medium | |
| CN111679911A (en) | Management method, device, equipment and medium for GPU (graphics processing Unit) card in cloud environment | |
| CN112491980B (en) | Cloud host service management method, system, terminal and storage medium | |
| CN103490945A (en) | Method for detecting maximum telnet user quantity | |
| CN113658351B (en) | Method and device for producing product, electronic equipment and storage medium | |
| CN115022109A (en) | Data management method for intelligent edge all-in-one machine and station cloud system | |
| US11308002B2 (en) | Systems and methods for detecting expected user intervention across multiple blades during a keyboard, video, and mouse (KVM) session | |
| CN105677589A (en) | Access control method, access control device and access control system | |
| CN116723198A (en) | Multi-node server host control method, device, equipment and storage medium | |
| CN116841944A (en) | Out-of-band management system of multi-platform fusion server | |
| CN101000572A (en) | Mainframe management system and method | |
| CN104951346A (en) | Process management method for embedded system as well as system | |
| CN115168141A (en) | Optical interface management system, method, device, programmable logic device and storage medium | |
| CN111290793B (en) | Method for initializing MOST network | |
| WO2021138846A1 (en) | Method and system for realizing fpga server | |
| CN111195919B (en) | Robot teaching platform and construction method thereof | |
| US10649941B2 (en) | Server system and method for managing two baseboard management controllers | |
| CN114095343A (en) | Disaster recovery method, device, equipment and storage medium based on double-active system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |