Multi-mode starting automatic management and control method and system based on PC Farm array server

Abstract

The invention discloses a multi-mode starting automatic control method and system based on a PC Farm array server, and relates to the technical field of server cluster management.The method comprises the steps that a central node creates a fine-grained strategy instruction and a corresponding mirror image instruction according to deployment requirements, and the fine-grained strategy instruction and the corresponding mirror image instruction are compressed into a mirror image compressed package through LZMA; the edge node extracts the verification label from the mirror image compressed package, analyzes the verification label through quantum error correction control, repairs a bit flipping error, and generates an anti-interference standardized instruction stream; based on the anti-interference standardized instruction stream, generating a quantum code stream data block through Hamming code coding, writing the quantum code stream data block into a configuration interface address, and correcting signal deviation to trigger a reset command; and executing the reset command, collecting a BIOS startup log, and comparing the BIOS startup log with pre-stored features to generate a startup state verification report. According to the method, accurate calibration and sequential control of hardware configuration are realized, the accuracy of starting parameters is ensured, and the high efficiency and stability of automatic deployment are improved.

Description

Technical Field

[0001] This invention relates to the field of server cluster management technology, and in particular to a multi-mode startup automated control method and system based on PC Farm array servers. Background Technology

[0002] In the field of server cluster management, multi-mode startup control of PC Farm array servers typically employs a centralized control architecture combined with standard remote management protocols. The conventional approach involves issuing basic startup commands through a central control node, utilizing a pre-built policy library to match different deployment scenarios, and relying on hardware management interfaces to switch startup modes for batch nodes. Existing technologies have formed relatively mature automation frameworks capable of supporting operating system image distribution and basic startup parameter configuration, meeting the basic requirements of large-scale cluster deployments.

[0003] In the field of automated management and control of multi-mode boot based on PC Farm array servers, existing methods lack dynamic protection against underlying physical interference during command transmission, especially in long-distance transmission or high electromagnetic interference environments. Furthermore, boot status verification relies on manual log analysis or simple keyword matching, failing to analyze the multi-dimensional state characteristics of the BIOS boot phase in real time, leading to delays in deployment strategy adjustments. These shortcomings limit the deployment accuracy and reliability in complex heterogeneous environments. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a multi-mode startup automation management method based on PC Farm array servers to solve the problems of insufficient command anti-interference and delayed startup status verification.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] In a first aspect, the present invention provides a multi-mode startup automated management and control method based on a PC Farm array server, which includes,

[0008] The central node creates fine-grained policy instructions and corresponding image instructions based on deployment requirements, and compresses them into image archives using LZMA;

[0009] Edge nodes extract verification tags from the image archive, parse the verification tags through quantum error correction control, and repair bit flip errors to generate an anti-interference standardized instruction stream;

[0010] Based on the anti-interference standardized instruction stream, quantum code stream data blocks are generated by Hamming code encoding, written to the configuration interface address, and signal deviation is corrected to trigger a reset command.

[0011] Execute the reset command and collect the BIOS boot log, compare it with the pre-stored features to generate a boot status verification report;

[0012] Based on the startup status verification report, perform differentiated automated deployment operations and generate node ready signals.

[0013] As a preferred embodiment of the multi-mode startup automated management method based on a PC Farm array server described in this invention, the central node creates fine-grained policy instructions and corresponding image instructions according to deployment requirements, as follows:

[0014] The central node receives and parses the operation request from the target node, and generates the deployment requirement parameters for the target node.

[0015] Based on the deployment requirements parameters of the target node, fine-grained policy instructions are generated through field mapping;

[0016] Execute fine-grained policy instructions and obtain the operating system image instructions after the script is injected.

[0017] As a preferred embodiment of the multi-mode boot automation management method based on PC Farm array servers described in this invention, the step of compressing the image into an image package using LZMA is as follows:

[0018] The operating system image instructions injected by the script are compressed to generate a compressed binary data packet.

[0019] Verify the compressed binary data packet and generate an image compressed package.

[0020] As a preferred embodiment of the multi-mode startup automated management and control method based on PC Farm array server described in this invention, the step of the edge node extracting the verification tag from the image compressed package means that the edge node separates the verification tag from the image compressed package using the LZMA decompression algorithm.

[0021] As a preferred embodiment of the multi-mode startup automated management method based on a PC Farm array server described in this invention, the steps of parsing and verifying the tag through quantum error correction control, repairing bit flip errors, and generating an anti-interference standardized instruction stream are as follows:

[0022] Calculate the current checksum of the binary data packet, compare the current checksum with the checksum tag, and locate the bit flip error address;

[0023] Based on the bit-flip error address, binary data packets are mapped to the logical qubit encoding space, error modes are detected, and bit-flip correction sequences are generated;

[0024] Repair faulty blocks in binary data packets, verify their integrity, and generate a resistant, standardized instruction stream.

[0025] As a preferred embodiment of the multi-mode startup automated management method based on a PC Farm array server described in this invention, the steps of generating quantum code stream data blocks through Hamming code encoding based on anti-interference standardized instruction streams, writing them to the configuration interface address, and correcting signal deviations to trigger a reset command are as follows:

[0026] Adding redundant error correction to the anti-interference standardized instruction stream using Hamming code encoding generates a quantum code stream data block with additional redundant error correction bits;

[0027] Extract the target policy parameter value from the quantum code stream data block, write the target policy parameter value into the target network interface selection configuration interface, and generate the current value of the configuration interface;

[0028] The current value of the configuration interface is compared and verified bit by bit with the target policy parameter value, and the verification pass flag is recorded as a prerequisite for triggering the reset command.

[0029] By monitoring the timing status of the clock signal with an oscilloscope and obtaining the time interval between adjacent rising edges, clock deviation events exceeding the interval threshold are identified, and a reset command is generated based on the preconditions for triggering the reset command.

[0030] As a preferred embodiment of the multi-mode boot automation management method based on a PC Farm array server described in this invention, the steps of executing the reset command and collecting BIOS boot logs are as follows:

[0031] Execute the reset command and monitor power status change signals;

[0032] Based on power state change signals, the BIOS boot sequence is executed, and the BIOS boot log is captured simultaneously.

[0033] As a preferred embodiment of the multi-mode startup automation management method based on a PC Farm array server described in this invention, the steps for generating a startup status verification report by comparing pre-stored features are as follows:

[0034] Based on the BIOS boot log, a pre-stored boot feature rule library is loaded through memory mapping, and a set of feature word matching positions is generated;

[0035] Based on the feature word matching location set, the BIOS boot phase achievement status is analyzed and converted into a boot status verification report.

[0036] As a preferred embodiment of the multi-mode startup automation management method based on PC Farm array servers described in this invention, the steps of performing differentiated automated deployment operations based on the startup status verification report and generating a node ready signal are as follows:

[0037] Based on the startup status verification report, the deployment scenario type is identified, operation commands are generated, and transmitted to the target node BMC through the edge node interface;

[0038] The target node BMC extracts the deployment scenario type parameter value from the operation command and executes differentiated operation commands based on the deployment scenario type parameter value;

[0039] After the operation command is executed, the target node activates the ready status signal. The central node captures the node ready status signal and converts it into a continuous high-level node ready signal output.

[0040] Secondly, this invention provides a multi-mode startup automated management and control system based on a PC Farm array server, including:

[0041] The policy compression module is used by the central node to create fine-grained policy instructions and corresponding image instructions according to deployment requirements, and compress them into image compressed packages using LZMA.

[0042] The quantum error correction module is used by edge nodes to extract verification tags from the image compressed package, parse the verification tags through quantum error correction control, repair bit flip errors, and generate an anti-interference standardized instruction stream;

[0043] The anti-interference coding module is used to generate quantum code stream data blocks based on the anti-interference standardized instruction stream using Hamming code encoding, write them to the configuration interface address, and correct signal deviations to trigger a reset command.

[0044] The status verification module is used to execute reset commands, collect BIOS boot logs, compare them with pre-stored features, and generate a boot status verification report.

[0045] The differential deployment module is used to perform differentiated automated deployment operations based on the startup status verification report and generate node ready signals.

[0046] The beneficial effects of this invention are as follows: by using quantum error correction control to analyze and verify the tag and repair bit flip errors, error detection and repair during instruction transmission are realized, ensuring data integrity under interference environments; by writing the configuration interface address and correcting signal deviations to trigger a reset command, precise calibration and timing control of hardware configuration are realized, ensuring the accuracy of startup parameters and improving the efficiency and stability of automated deployment. Attached Figure Description

[0047] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a flowchart of a multi-mode startup automation management method based on a PC Farm array server.

[0049] Figure 2 This is a schematic diagram of a multi-mode startup automated management and control system based on a PC Farm array server.

[0050] Figure 3 A flowchart for a multi-mode startup automated control method.

[0051] Figure 4 This is a flowchart of BMC-BIOS collaborative control. Detailed Implementation

[0052] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0053] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0054] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0055] Reference Figures 1-4 As one embodiment of the present invention, this embodiment provides a multi-mode startup automated management and control method based on a PC Farm array server, including the following steps:

[0056] S1. The central node creates fine-grained policy instructions and corresponding image instructions based on deployment requirements, and compresses them into an image archive using LZMA.

[0057] The central node receives and parses the operation request from the target node, and generates the deployment requirement parameters for the target node.

[0058] Furthermore, the central node directly receives operation requests from the target node, which are transmitted in string format; and searches the target node operation request string by string pattern matching to obtain the keyword structure, identify and extract the target node deployment requirement parameters, including deployment scenario type and hardware configuration values.

[0059] It should be noted that the central node is the core control center of the entire PCFarm array server automated management and control system. It is responsible for creating fine-grained policy instructions and compressed image packages according to deployment requirements, and coordinating edge nodes to execute startup operations. The target nodes are individual server nodes and hardware devices in the PCFarm array. They receive instructions from the central node through their BMC, execute specific startup configurations, and provide feedback status signals.

[0060] Based on the deployment requirements parameters of the target node, fine-grained policy instructions are generated through field mapping;

[0061] Furthermore, based on the target node deployment requirement parameters, the field names prefixed with the target node deployment requirement parameters and the values ​​after the equals sign are identified by the key-value pair parsing method to generate the deployment scenario type field and hardware configuration value field; and combined with the predefined field mapping relationship table, the deployment scenario type field and hardware configuration value field are mapped to the target policy field, and a fine-grained policy instruction containing all policy fields is generated by concatenating key-value pairs.

[0062] It should be noted that the field mapping table is a data structure used to store the correspondence between source fields (such as the deployment scenario type field parsed from the deployment requirement parameters of the target node) and target policy fields (e.g., HW_CONFIG_VALUE = 8G -> MEMORY_ALLOC_SIZE = 8192). The field mapping table is based on the configuration policy data of the central node and is built by writing a structured configuration file or directly in the database. The target policy field refers to the operation parameters used to execute hardware configuration in the fine-grained policy instructions (such as startup order and memory allocation value). By querying the field mapping table, the parsed deployment scenario type field value is mapped to the hardware configuration value field value and concatenated to generate the target policy field.

[0063] Execute fine-grained policy instructions and obtain the operating system image instructions after the script is injected;

[0064] Furthermore, fine-grained policy instructions are executed, and a preset script is injected. The key-value pairs in the fine-grained policy instructions are extracted through mapping rules. The corresponding operating system image instruction file path is selected according to the deployment scenario type field specified by the fine-grained policy instructions. The image file is loaded from the preset image resource library of the central node through file input operations, and the operating system image instructions after the script is injected are obtained.

[0065] It should be noted that the image resource library is based on the correspondence between deployment scenario types and image files. By maintaining configuration files, it clarifies the image files and storage paths required for each scenario according to different deployment needs. These mapping relationships are written into the configuration files in a structured format and stored in the central node. The scripts are pre-written automated scripts based on deployment scenario requirements (such as environment configuration, software installation, service startup, etc.). The mapping rules refer to the key-value pair conversion logic, which converts the fields in the fine-grained policy instructions into the parameters required for loading the operating system image (such as the image path / images / pxe_boot.img). The key-value pair content refers to the set of structured policy parameters parsed from the fine-grained policy instructions (for example, {"SCENE_TYPE":"PXE","MEM_SIZE":"8G"}).

[0066] The LZMA compression algorithm is used to compress the operating system image instructions injected into the script, generating a compressed binary data packet.

[0067] Furthermore, the central node reads the operating system image instructions after the script is injected through file byte stream operations, converts the operating system image instructions after the script is injected into a binary data stream; uses the LZMA compression algorithm to perform multi-level dictionary compression processing on the binary data stream, and uses the LZMA encoder to generate compressed blocks according to the dictionary size setting of the compressed binary data stream; in the entropy encoding stage, the compressed blocks are processed using a probability interval encoder to generate compressed binary data packets.

[0068] Verify the compressed binary data packet and generate an image compressed package.

[0069] Furthermore, the central node processes the compressed binary data packet byte by byte using CRC32 cyclic redundancy check. Each byte is XORed with the current CRC value to generate a multi-bit checksum. The central node creates a mirror compressed packet binary file structure, defining the mirror compressed packet header area as the checksum storage location and the mirror compressed packet content area as the compressed binary data packet storage location. The central node writes the multi-bit checksum into the mirror compressed packet header area and writes the complete compressed binary data packet into the mirror compressed packet content area, generating a mirror compressed packet containing checksum tags and compressed data. The mirror compressed packet is then transmitted to the edge nodes via the IPMI protocol.

[0070] S2. Edge nodes extract verification tags from the image compressed package, parse the verification tags through quantum error correction control, repair bit flip errors, and generate anti-interference standardized instruction streams.

[0071] Edge nodes extract verification tags from the image archive using the LZMA decompression algorithm;

[0072] Furthermore, the edge node reads the entire contents of the image compressed package through file byte stream operations; and identifies the verification tag from the entire contents of the image compressed package; the edge node extracts a fixed-length data block from the header area of ​​the image compressed package through byte positioning operations, stores it in the edge node's temporary storage area and marks it as a verification tag, and at the same time, extracts the complete data block from the content area of ​​the image compressed package, stores it in the decompression processing buffer and marks it as a compressed binary data packet.

[0073] The CRC32 algorithm is used to calculate the current check value of the binary data packet, compare the current check value with the check tag, and locate the bit flip error address.

[0074] Furthermore, the edge node calculates the compressed binary data packet byte by byte through CRC32 cyclic redundancy check to generate the current check value; the current check value is XORed with the check tag separated from the mirror compressed packet to generate a difference bitmap; when the difference bitmap is non-zero, a bit flip error is confirmed to exist and the error address is determined using the rollback location method, thus locating the bit flip error address.

[0075] Based on the bit-flip error address, binary data packets are mapped to the logical qubit encoding space, error modes are detected by measuring Steane error correction codes, and bit-flip correction sequences are generated.

[0076] Furthermore, the data segment corresponding to the bit-flip error address in the compressed binary data packet is directly accessed and extracted through memory address. The data segment corresponding to the bit-flip error address is mapped to the quantum computing ground state and packaged into a logical quantum bit state. Steane code is used to map the data packet to a multi-bit quantum bit encoding space. Stable submeasurement is achieved through CNOT gate and Hadamard gate operations, and Syndrome detection is performed to obtain multi-bit error symptom values. The symptom values ​​are queried to find the corresponding correction operation in the Steane code predefined correction table to generate a bit-flip correction sequence.

[0077] It should be noted that the correction table refers to the structure that stores the mapping relationship between quantum error symptom values ​​and correction operations. It is based on the stable substructure of Steane code and is generated by offline enumeration of all possible error modes and calculation of the optimal correction operation. The correction operation refers to the bit flip correction instruction in quantum error correction, which is set by querying the predefined correction table and matching the optimal operation with the error symptom value detected by Syndrome.

[0078] The error blocks in binary data packets are repaired by bit-flipping correction sequences, and their integrity is verified, generating an anti-interference standardized instruction stream.

[0079] Furthermore, the edge node modifies the consecutive bit segments with bit-flip errors in the compressed binary data packet bit by bit based on the bit-flip correction sequence, and flips the erroneous bits through a binary XOR operation; after repair, the edge node recalculates the new check value of the compressed binary data packet and compares it with the check tag; when the new check value is completely consistent with the check tag, the edge node confirms that the compressed binary data packet has been repaired and has passed the integrity verification, and the repaired compressed binary data packet is identified as an anti-interference standardized instruction stream.

[0080] S3. Based on the anti-interference standardized instruction stream, quantum code stream data blocks are generated by Hamming code encoding, written to the configuration interface address, and signal deviation is corrected to trigger a reset command.

[0081] Adding redundant error correction to the anti-interference standardized instruction stream using Hamming code encoding generates a quantum code stream data block with additional redundant error correction bits;

[0082] Furthermore, the anti-interference standardized instruction stream is divided into multiple fixed-length data blocks; each data block is XORed with the column vector in the Hamming code matrix specifically used for calculating the parity bit to calculate the parity bit; finally, the parity bit is inserted into the specified position of the data block to generate a quantum code stream data block with additional redundant error correction bits.

[0083] It should be noted that a Hamming code matrix is ​​a matrix used to encode raw information bits into Hamming codewords that include redundant check bits, according to the definition of Hamming code encoding.

[0084] Extract the target policy parameter value from the quantum code stream data block, write the target policy parameter value into the target network interface selection configuration interface, and generate the current value of the configuration interface through the IPMI protocol;

[0085] Furthermore, through offset positioning operations, a fixed-length binary sequence at the starting position in the quantum code stream data block is read and converted into a strategy parameter value; the target strategy parameter value is converted into a hexadecimal byte stream through the IPMI raw command writing function; the target network interface selection configuration interface register address is combined with the hexadecimal byte stream through the IPMI raw command encapsulation format to generate an encapsulated IPMI instruction; the encapsulated IPMI instruction is transmitted through the I2C bus to the storage location of the specified physical address of the target network interface selection configuration interface, and the original configuration value is overwritten to trigger hardware response behavior to generate the current value of the configuration interface.

[0086] The current value of the configuration interface is compared and verified bit by bit with the target policy parameter value, and the verification pass flag is recorded as a prerequisite for triggering the reset command.

[0087] Furthermore, the binary sequence of the current value of the configuration interface is obtained through the I2C bus; the binary sequence of the current value of the configuration interface is compared with the target policy parameter value by performing a byte length alignment check to ensure that they have the same bit width; the difference status between the two is calculated bit by bit by XOR operation and a difference bitmap is generated; when all bits of the difference bitmap are zero, the comparison result status is marked as true; when there are non-zero bits in the difference bitmap, the target policy parameter value is rewritten to the physical address storage location specified by the target network interface selection configuration interface and compared with the current value binary sequence of the configuration interface again until all bits of the difference bitmap are zero, and the verification pass flag is recorded as a prerequisite for triggering the reset command.

[0088] By monitoring the timing status of the clock signal with an oscilloscope and obtaining the time interval between adjacent rising edges, clock deviation events exceeding the interval threshold are identified, and a reset command is generated based on the preconditions for triggering the reset command.

[0089] Furthermore, by connecting the oscilloscope probe to the clock signal pin of the target network port selection configuration interface, the clock signal waveform is captured, the clock signal waveform is continuously monitored, and the time interval between adjacent rising edges is measured. When the difference in the measured time interval exceeds the interval threshold, it is identified as a clock deviation event. Combined with the prerequisite for triggering the reset command, namely the verification pass flag, when the verification pass flag is true and a clock deviation event exists, a reset command is generated through the chassis reset command encapsulated with the IPMI protocol.

[0090] It should be noted that the interval threshold is set based on the maximum clock jitter tolerance allowed by the BIOS specification, and the value range is usually 10-20 nanoseconds.

[0091] S4. Execute the reset command and collect the BIOS boot log, compare it with the pre-stored features and generate a boot status verification report;

[0092] Execute the reset command and monitor power status change signals;

[0093] Furthermore, the central node transmits the reset command to the target node's hardware interface via the I2C bus, overwriting the original configuration value and triggering a hardware reset operation on the target node. The ASP serial port pin connected to the target node continuously reads the BIOS log input stream through the serial port data stream capture function. The BIOS log data stream is parsed by matching predefined power state change keywords. When the predefined power state change keyword is successfully matched, the central node determines that the power state change signal has been monitored.

[0094] It should be noted that power state transition keywords are used to identify specific strings or event identifiers of computer system power state transition events (such as from shutdown to startup, from sleep to wake-up, etc.); power state transition keywords are used in the ACPI (Advanced Configuration and Power Interface) firmware code to predefine corresponding descriptive strings or event codes for different power state transition events.

[0095] Based on power state change signals, run the BIOS boot sequence and capture the BIOS boot log.

[0096] Furthermore, based on the power state change signal (power state change keyword matching success event), the target node executes the firmware loading program to perform boot device selection and initialization operations. At the same time, the central node connects to the target node's ASP serial port pin, continuously reads the BIOS log input stream through the serial port data stream capture function, and stores the captured data in the log buffer as the BIOS boot log.

[0097] Based on the BIOS boot log, a pre-stored boot feature rule library is loaded through memory mapping, and a feature word matching position set is generated through a multi-mode string matching algorithm.

[0098] Furthermore, based on the BIOS boot log, the central node loads the pre-stored boot feature rule base content from the storage path into the memory-mapped address area through file input operations; the central node inserts all keywords into a Trie tree through a multi-pattern string matching algorithm and the Aho-Corasick algorithm, and constructs an automaton structure by building failure pointers for each node through breadth-first search. The BIOS boot log is input into the data stream, and the automaton structure scans the BIOS boot log data stream character by character to identify the occurrence positions of keywords in all pre-stored boot feature rule bases, and records the starting offset address and occurrence frequency of each keyword to generate a set of feature word matching positions.

[0099] It should be noted that the pre-stored boot feature rule base refers to a set of keywords and matching rules predefined based on key event identifiers in the server BIOS initialization process, used to identify status events in the BIOS boot log.

[0100] Based on the feature word matching location set, the BIOS boot phase achievement status is verified and analyzed through state sequence verification, and converted into a boot state verification report.

[0101] Furthermore, the central node, based on the feature word matching location set, scans the keyword occurrence order and frequency in the feature word matching location set through the BIOS startup phase state transition rules to verify the achievement conditions of each startup phase; the verification results of each phase are converted into binary state sequences through a state encoding mapping table, and finally encapsulated into a startup state verification report containing the overall state code and detailed phase states.

[0102] It should be noted that the BIOS boot phase state transition rules refer to the sequential constraints defined by the server hardware initialization logic. The BIOS boot phase state transition rules are based on the boot process timing dependencies specified in the device manufacturer's BIOS development manual. The achievement conditions refer to the keyword appearance order and frequency requirements that each boot phase must meet. These are generated offline by statistically analyzing the frequency and position of keywords in the historical normal logs from the pre-stored boot feature rule base. The state encoding mapping table is set based on the total number of BIOS boot phases and the format requirements of the boot state verification report. An appropriate encoding scheme (such as sequential binary encoding or One-Hot encoding) is selected, and the bit width of the binary state sequence is determined. Then, a unique binary bit is assigned to each boot phase, and the meaning represented by the binary bit is clearly defined.

[0103] S5. Based on the startup status verification report, perform differentiated automated deployment operations and generate node ready signals.

[0104] Based on the startup status verification report, the deployment scenario type is identified, operation commands are generated, and transmitted to the target node BMC through the edge node interface;

[0105] Furthermore, the central node reads the detailed stage status fields from the startup status verification report, identifies the deployment scenario type (including PXE startup, disk startup, containerized startup, and secure startup) by matching the stage status sequence with the deployment scenario mapping rule table; it then queries the operation command mapping table based on the deployment scenario type to generate the operation command string content; the central node encapsulates the operation command string using the IPMI protocol and transmits it to the edge node interface; the edge node converts the command string to hexadecimal format using a hexadecimal conversion function, adds a command type field and a checksum using the IPMI instruction encapsulation function to encapsulate it into an IPMI instruction frame structure, and sends the IPMI instruction frame to the target node's BMC hardware interface instruction queue address through the edge node's internal interface to complete the transmission process.

[0106] It should be noted that the deployment scenario mapping rule table is a structured data table that defines the correspondence between startup state sequences and deployment scenario types. It is usually based on the startup phase and scenario dependency relationship specified in the device manufacturer's specifications (e.g., Dell iDRAC manual) (e.g., memory detection needs to be done after CPU initialization). The operation command mapping table is a configuration table that stores the association between deployment scenario types and operation command parameters. The operation command mapping table is generated based on the configuration policy data of the central node.

[0107] The target node BMC extracts the deployment scenario type parameter value from the operation command and executes differentiated operation commands based on the deployment scenario type parameter value;

[0108] Furthermore, the target node BMC extracts keywords from the operation command string using a string matching algorithm and identifies the fields following the keywords as deployment scenario type parameter values. Based on the deployment scenario type parameter value, the target node BMC queries the preset operation command execution rule table stored internally and executes differentiated operation commands. For example, when the deployment scenario type parameter value is PXE, it executes the operation of setting the network card boot order; when the deployment scenario type parameter value is DISK, it executes the operation of setting the hard disk boot order; and when the deployment scenario type parameter value is LINUX_WIN_CONTAINER, it executes the operation of configuring a Linux-hosted Windows container environment.

[0109] It should be noted that the operation command execution rule table is set based on the key-value pair mapping association between the deployment scenario type and the specific hardware operation command. The deployment scenario type is associated with the corresponding IPMI command (or underlying hardware register operation step) in the form of key-value pairs, and the key-value pairs are solidified into the BMC firmware and non-volatile storage for the BMC to query and execute at runtime.

[0110] After the operation command is executed, the target node activates the ready status signal. The central node captures the node ready status signal and converts it into a continuous high-level node ready signal output.

[0111] Furthermore, after the operation command is executed, the target node activates the node ready status signal through the internal hardware register of the target node BMC; the central node queries the status register value of the target node BMC through the edge node interface and uses the IPMI protocol to send IPMI commands to capture the node ready status signal; after capture, the central node performs signal conversion through a logic signal conversion method, and outputs a continuous high level when the node ready status signal voltage exceeds the preset voltage threshold, generating a continuous high level node ready signal output.

[0112] It should be noted that the voltage threshold is set based on the standard range of TTL logic high level (typically 2.0V to 5.0V), and is set by configuring the reference voltage value of the voltage comparator circuit, with a value range typically from 2.0V to 5.0V.

[0113] This embodiment also provides a multi-mode startup automation management system based on PC Farm array servers, including:

[0114] The policy compression module is used by the central node to create fine-grained policy instructions and corresponding image instructions according to deployment requirements, and compress them into image compressed packages using LZMA.

[0115] The quantum error correction module is used by edge nodes to extract verification tags from the image compressed package, parse the verification tags through quantum error correction control, repair bit flip errors, and generate an anti-interference standardized instruction stream;

[0116] The anti-interference coding module is used to generate quantum code stream data blocks based on the anti-interference standardized instruction stream using Hamming code encoding, write them to the configuration interface address, and correct signal deviations to trigger a reset command.

[0117] The status verification module is used to execute reset commands, collect BIOS boot logs, compare them with pre-stored features, and generate a boot status verification report.

[0118] The differential deployment module is used to perform differentiated automated deployment operations based on the startup status verification report and generate node ready signals.

[0119] This embodiment also provides a computer device applicable to the multi-mode boot automation management method based on a PC Farm array server, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the multi-mode boot automation management method based on a PC Farm array server as proposed in the above embodiment.

[0120] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0121] This embodiment also provides a storage medium storing a computer program. When executed by a processor, the program implements the automated control method for multi-mode booting of a PC Farm array server as proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Red-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0122] In summary, this invention achieves error detection and repair during instruction transmission by using quantum error correction control to analyze and verify tags and repair bit flip errors, ensuring data integrity under interference environments; and achieves precise calibration and timing control of hardware configuration by writing to the configuration interface address and correcting signal deviations to trigger reset commands, ensuring the accuracy of startup parameters and improving the efficiency and stability of automated deployment.

[0123] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A multi-mode startup automated management and control method based on PC Farm array servers, characterized in that: include, The central node creates fine-grained policy instructions and corresponding image instructions based on deployment requirements, and compresses them into image archives using LZMA; Edge nodes extract verification tags from the image archive, parse the verification tags through quantum error correction control, and repair bit flip errors to generate an anti-interference standardized instruction stream; Based on the anti-interference standardized instruction stream, quantum code stream data blocks are generated by Hamming code encoding, written to the configuration interface address, and signal deviation is corrected to trigger a reset command. Execute the reset command and collect the BIOS boot log, compare it with the pre-stored features to generate a boot status verification report; Based on the startup status verification report, perform differentiated automated deployment operations and generate node ready signals.

2. The multi-mode startup automated management method based on a PC Farm array server as described in claim 1, characterized in that: The central node creates fine-grained policy instructions and corresponding image instructions based on deployment requirements, as follows: The central node receives and parses the operation request from the target node, and generates the deployment requirement parameters for the target node. Based on the deployment requirements parameters of the target node, fine-grained policy instructions are generated through field mapping; Execute fine-grained policy instructions and obtain the operating system image instructions after the script is injected.

3. The multi-mode startup automated management and control method based on a PC Farm array server as described in claim 2, characterized in that: The steps for compressing the image into a compressed file using LZMA are as follows. The operating system image instructions injected by the script are compressed to generate a compressed binary data packet. Verify the compressed binary data packet and generate a mirror compressed package.

4. The automated management and control method for multi-mode startup based on a PC Farm array server as described in claim 3, characterized in that: The extraction of verification tags from the image archive by the edge node refers to the process by which the edge node extracts the verification tags from the image archive using the LZMA decompression algorithm.

5. The multi-mode startup automated management and control method based on a PC Farm array server as described in claim 4, characterized in that: The steps for parsing and verifying the tag using quantum error correction control, repairing bit flip errors, and generating an interference-resistant standardized instruction stream are as follows: Calculate the current checksum of the binary data packet, compare the current checksum with the checksum tag, and locate the bit flip error address; Based on the bit-flip error address, binary data packets are mapped to the logical qubit encoding space, error modes are detected, and bit-flip correction sequences are generated; Repair faulty blocks in binary data packets, verify their integrity, and generate a resistant, standardized instruction stream.

6. The multi-mode startup automated management method based on a PC Farm array server as described in claim 5, characterized in that: The steps for generating quantum code stream data blocks based on anti-interference standardized instruction streams using Hamming code encoding, writing them to the configuration interface address, and correcting signal deviations to trigger a reset command are as follows: Adding redundant error correction to the anti-interference standardized instruction stream using Hamming code encoding generates a quantum code stream data block with additional redundant error correction bits; Extract the target policy parameter value from the quantum code stream data block, write the target policy parameter value into the target network interface selection configuration interface, and generate the current value of the configuration interface; The current value of the configuration interface is compared and verified bit by bit with the target policy parameter value, and the verification pass flag is recorded as a prerequisite for triggering the reset command. By monitoring the timing status of the clock signal with an oscilloscope and obtaining the time interval between adjacent rising edges, clock deviation events exceeding the interval threshold are identified, and a reset command is generated based on the preconditions for triggering the reset command.

7. The multi-mode startup automated management method based on a PC Farm array server as described in claim 6, characterized in that: The steps for executing the reset command and collecting the BIOS boot log are as follows: Execute the reset command and monitor power status change signals; Based on power state change signals, the BIOS boot sequence is executed, and the BIOS boot log is captured simultaneously.

8. The automated management and control method for multi-mode startup based on a PC Farm array server as described in claim 7, characterized in that: The steps for generating a startup status verification report by comparing pre-stored features are as follows: Based on the BIOS boot log, a pre-stored boot feature rule library is loaded through memory mapping, and a set of feature word matching positions is generated; Based on the feature word matching location set, the BIOS boot phase achievement status is analyzed and converted into a boot status verification report.

9. The multi-mode startup automated management method based on a PC Farm array server as described in claim 8, characterized in that: Based on the startup status verification report, the differentiated automated deployment operation is performed to generate a node ready signal. The steps are as follows: Based on the startup status verification report, the deployment scenario type is identified, operation commands are generated, and transmitted to the target node BMC through the edge node interface; The target node BMC extracts the deployment scenario type parameter value from the operation command and executes differentiated operation commands based on the deployment scenario type parameter value; After the operation command is executed, the target node activates the ready status signal. The central node captures the node ready status signal and converts it into a continuous high-level node ready signal output.

10. A multi-mode boot automated management and control system based on a PC Farm array server, based on the multi-mode boot automated management and control method based on any one of claims 1 to 9, characterized in that: include, The policy compression module is used by the central node to create fine-grained policy instructions and corresponding image instructions according to deployment requirements, and compress them into image compressed packages using LZMA. The quantum error correction module is used by edge nodes to extract verification tags from the image compressed package, parse the verification tags through quantum error correction control, repair bit flip errors, and generate an anti-interference standardized instruction stream; The anti-interference coding module is used to generate quantum code stream data blocks based on the anti-interference standardized instruction stream using Hamming code encoding, write them to the configuration interface address, and correct signal deviations to trigger a reset command. The status verification module is used to execute reset commands, collect BIOS boot logs, compare them with pre-stored features, and generate a boot status verification report. The differential deployment module is used to perform differentiated automated deployment operations based on the startup status verification report and generate node ready signals.

Images