A server system startup method, device, equipment and medium

Abstract

The present application discloses a server system startup method, apparatus, device and medium, which relates to the technical field of computer system startup, including setting the priority of hardware feature information of each dimension corresponding to the matching system image file; matching the hardware feature information of each dimension to the corresponding system image file according to the priority; sequentially judging whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and obtaining the sub-item feature value of the hardware feature information of each dimension according to the judgment result; determining the comprehensive feature value according to the sub-item feature value of the hardware feature of each dimension and the corresponding sub-item feature weight; verifying the comprehensive feature value to determine the target system image file to be started by the system server to be installed; and starting the system server to be installed through the target system image file. The technology of the present application can realize the precise boot matching of the server system based on multi-dimensional hardware features, reducing manual intervention.

Description

Technical Field

[0001] The present application relates to the technical field of computer system startup, and in particular to a server system startup method, apparatus, device, and medium. Background Art

[0002] Currently, by configuring multiple servers, each server boots the system based on only one hardware feature, dividing the physical network into several subnets, thereby achieving customized boot requirements. This boot method is costly and greatly increases the difficulty of network management. If the network cable is plugged in incorrectly, it may cause network crosstalk, which in turn causes the business network to be paralyzed.

[0003] Production line testing at server assembly plants currently mostly boots the system based on only one hardware characteristic dimension. To boot a specific operating system, the server powers on and enters the default operating system. Then, a shell script queries the MAC (Media Access Control address) of the current network card. A customized boot system image file is generated based on the MAC address and uploaded to the server. The server is then restarted, and the customized operating system is entered the next time it is started. This method requires entering another system in advance for operation. However, for hardware with a new architecture and platform, using the default designated boot system may result in incompatibility, causing automatic boot failure.

[0004] At the same time, when deploying cluster servers in large data centers, if you rely on the network card MAC address information provided by the server manufacturer, and then generate a single boot configuration file one by one based on the network card MAC address information, flexibility is reduced and the configuration and maintenance costs are high. Summary of the Invention

[0005] The present application provides a server system startup method, device, equipment and medium, the method includes creating a system image file set on the system server to be installed according to the business type; obtaining the hardware feature information of the system server to be installed in multiple dimensions; setting the priority of the hardware feature information of each dimension corresponding to the matching system image file according to the accuracy of the hardware feature information; matching the hardware feature information of each dimension to the corresponding system image file according to the priority of the hardware feature information of each dimension; sequentially judging whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and obtaining the sub-item feature value of the hardware feature information of each dimension according to the judgment result; determining the comprehensive feature value according to the sub-item feature value of the hardware feature of each dimension and the corresponding sub-item feature weight; verifying the comprehensive feature value to determine the target system image file to be started for the system server to be installed; and starting the system server to be installed through the target system image file. The technology of the present application can realize the precise boot matching of the server system based on the multi-dimensional hardware features, reduce manual intervention, and improve the efficiency of the server system startup.

[0006] This application provides a server system startup method, the method comprising:

[0007] Create a system image file set on the system server to be installed according to the business type;

[0008] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0009] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0010] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0011] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0012] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0013] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0014] Start the system server to be installed through the target system image file.

[0015] The present application also provides a server system startup device, comprising:

[0016] A creation module is used to create a system image file set on the system server to be installed according to the business type;

[0017] The acquisition module is used to obtain the hardware feature information of the system server to be installed in multiple dimensions;

[0018] A setting module is used to set the priority of hardware feature information of each dimension corresponding to the matching system image file according to the accuracy of the hardware feature information;

[0019] A matching module, configured to match the hardware feature information of each dimension to the corresponding system image file according to the priority of the hardware feature information of each dimension corresponding to the matching system image file;

[0020] A judgment module is used to judge in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and obtain the sub-item feature value of the hardware feature information of each dimension according to the judgment result;

[0021] A determination module is used to determine a comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0022] A verification module is used to verify the comprehensive characteristic value and determine the target system image file to be started by the system server to be installed;

[0023] The startup module is used to start the system server to be installed through the target system image file.

[0024] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of a server system startup method when executing the computer program, the method comprising:

[0025] Create a system image file set on the system server to be installed according to the business type;

[0026] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0027] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0028] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0029] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0030] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0031] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0032] Start the system server to be installed through the target system image file.

[0033] The present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the server system startup method are implemented, and the method includes:

[0034] Create a system image file set on the system server to be installed according to the business type;

[0035] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0036] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0037] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0038] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0039] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0040] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0041] Start the system server to be installed through the target system image file.

[0042] The present application also provides a computer program product, including a computer program. When the computer program is executed by a processor, the steps of the server system startup method are implemented. The method includes:

[0043] Create a system image file set on the system server to be installed according to the business type;

[0044] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0045] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0046] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0047] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0048] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0049] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0050] Start the system server to be installed through the target system image file.

[0051] Through the present application, the method includes creating a system image file set on the system server to be installed according to the business type; obtaining the hardware feature information of the system server to be installed in multiple dimensions; setting the priority of the hardware feature information of each dimension corresponding to the matching system image file according to the accuracy of the hardware feature information; matching the hardware feature information of each dimension to the corresponding system image file according to the priority of the hardware feature information of each dimension; sequentially judging whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and obtaining the sub-item feature value of the hardware feature information of each dimension according to the judgment result; determining the comprehensive feature value according to the sub-item feature value of the hardware feature of each dimension and the corresponding sub-item feature weight; verifying the comprehensive feature value to determine the target system image file to be started by the system server to be installed; and starting the system server to be installed through the target system image file. Therefore, the technology of the present application can realize the precise boot matching of the server system based on the multi-dimensional hardware features, reduce manual intervention, and improve the efficiency of the server system startup.

[0052] The technical solution of this application supports image file matching with more than 7 dimensions of hardware features, which can cover more than 95% of heterogeneous device scenarios, reducing the server system startup error rate to 0; the technology of this application realizes "zero-touch deployment", reducing manual configuration time by 90%, and is especially suitable for ultra-large-scale cluster servers (such as thousands of nodes); it can quickly adapt to new hardware (such as RISC-V), at which time it is necessary to update the policy file library without modifying the boot program; when the server is expanded, there is no need to manually reconfigure the network, avoiding the paralysis of the entire network due to manual configuration errors; and the booting of illegal servers is suspended, and an alert is issued for manual processing. The technical solution of this application improves the efficiency of pre-booting of large cluster servers, and automatically uploads comprehensive feature information to the server for engineers to monitor in the background. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] 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.

[0054] Figure 1 A first flow chart of the server system startup method provided in an embodiment of the present application;

[0055] Figure 2 This is an overall flow chart of the server system startup method provided in an embodiment of the present application;

[0056] Figure 3 A second flow chart of the server system startup method provided in an embodiment of the present application;

[0057] Figure 4 A flow chart of the dynamic policy matching system image file provided in an embodiment of the present application;

[0058] Figure 5 A specific flow chart of the server system startup method provided in an embodiment of the present application;

[0059] Figure 6 A structural diagram of a server system startup device provided in an embodiment of the present application;

[0060] Figure 7 The exemplary systems provided for the embodiments of the present application can be used to implement the various embodiments described in the present application. DETAILED DESCRIPTION

[0061] 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.

[0062] 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.

[0063] 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.

[0064] In conjunction with the specific application environment architecture or specific hardware architecture on which the execution of the server system startup method depends, the specific application environment architecture or specific hardware architecture is described here.

[0065] Production line testing at server assembly plants can only specify one hardware feature by default to boot a specific operating system (OS), making customization impossible. With the proliferation of ARM architectures and processors from various manufacturers, each with its own operating system targeting, it is necessary to intelligently identify and boot the system based on multiple hardware features. A single static boot configuration is no longer sufficient.

[0066] PXE (Preboot eXecution Environment) is a preboot technology that loads operating system images from a remote server over the network. It is widely used in data centers, cloud computing platforms, and industrial automation scenarios. Traditional boot loaders (such as GRUB and UEFI) typically rely on static configuration files (such as grub.cfg) to manage boot items, requiring manual configuration of information such as the operating system path and kernel parameters. However, this technology has significant drawbacks in the following scenarios:

[0067] Hardware heterogeneity: When the device hardware (such as CPU architecture, network card model, and package) changes, the boot item needs to be reconfigured;

[0068] Device uniqueness management: Automatically match the corresponding operating system or configuration based on the device's unique identifier (SN, MAC address).

[0069] The relevant technical solutions mainly rely on the following methods:

[0070] Single hardware identifier matching: For example, only the MAC address or motherboard UUID is used to associate the boot image file;

[0071] Static configuration table management: pre-define the mapping relationship between hardware features and system image files in the DHCP server or TFTP server directory;

[0072] Limited hardware support: Only common hardware (such as X86 architecture processors) is supported, and there is a lack of dynamic adaptation capabilities for heterogeneous hardware.

[0073] The current common pre-boot configuration method cannot verify the legitimacy of the system. When files are tampered with or the configuration is invalid, the system can still be booted, which will lead to an illegal system and cause network anomalies of the entire cluster.

[0074] It is understandable that traditional pre-boot solutions rely on a single MAC address or IP address match, which cannot meet the multi-dimensional hardware feature requirements; single hardware identifier match, such as associating the boot image only by MAC address or motherboard UUID.

[0075] Lack of flexibility: A single feature (such as the MAC address) cannot handle complex scenarios. For example, the boot system 1 has been configured according to the MAC address, but due to testing, verification, and maintenance scenarios, the network card is removed and installed on another server. At this time, manual configuration and modification of the boot file are required. For another example, different CPU manufacturers or models (ARMv8 vs. ARMv9) with the same architecture require different kernel programs.

[0076] High configuration and maintenance costs: Related technologies require manual maintenance of a large mapping table between hardware features and image files, which is prone to errors due to hardware updates or configuration changes. For example, adding a new motherboard model or replacing a machine with a component requires manual updating of the DHCP server configuration, which is inefficient and prone to omissions. If manual errors occur, the entire network may be paralyzed. New server machines also require frequent additional maintenance, which consumes a lot of manpower and energy.

[0077] Poor scalability: Unable to automatically adapt to new hardware (such as RISC-V architecture devices) or mixed architecture clusters (such as X86 and ARM coexistence scenarios).

[0078] Poor security: When the boot file is tampered with, it may cause batch system boot errors in the entire large cluster server, causing economic losses.

[0079] Difficulty in monitoring the overall deployment progress: In large clusters of servers, the progress of PXE pre-booting is not clearly monitored. Installation progress can only be viewed manually by plugging in a monitor or using BMCKVM. This can easily lead to omissions. For example, if there are five or six abnormal servers in a server cluster of 1,000 servers, manual inspection may be required to locate the abnormal machines one by one.

[0080] The embodiment of the present application provides a server system startup method, such as Figure 1 、 Figure 2 As shown, the method includes:

[0081] Create a system image file set on the system server to be installed according to the business type;

[0082] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0083] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0084] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0085] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0086] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0087] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0088] Start the system server to be installed through the target system image file.

[0089] It is understood that this application relates to a PXE (Pre-boot Execution Environment) network boot technology based on the Unified Extensible Firmware Interface (UEFI), and in particular to a method for dynamically and intelligently matching PXE boot items by deeply integrating the grubaa64.efi boot program and combining multi-dimensional hardware features (including network card MAC address, motherboard part number, motherboard PN, motherboard package number, CPU model, CPU manufacturer, and architecture type, etc.), thereby reducing manual intervention. The multi-dimensional hardware feature collection engine hwscan is used to intelligently collect hardware feature information in multiple dimensions, and a comprehensive feature value is calculated based on the weighted feature values of the individual feature values of the hardware feature information dimensions to ensure the security of server booting. In this application, by uploading the calculated comprehensive feature value to the server, engineers only need to monitor the background, achieving zero-touch deployment.

[0090] During the boot phase, device hardware information (MAC address, SN, PN, CPU, architecture, etc.) is dynamically collected and automatically matched to the corresponding operating system or configuration based on a preset matching strategy to generate a dynamic boot menu, reducing manual intervention. This application designs a dynamic matching policy engine that automatically selects the optimal server boot item based on hardware characteristics, supporting priority configuration and nested policy configuration. It also supports interactive debugging and policy management of GRUB Shell scripts, improving the flexibility, maintainability, compatibility, and scalability of system startup.

[0091] This application designs a method to obtain a comprehensive characteristic value by weighted calculation of the sub-item characteristic values based on the characteristic information of each hardware. The security of the server boot is ensured by verifying the comprehensive characteristic value, and abnormal boot can be promptly warned to enable engineers to manually intervene to analyze and solve the problem.

[0092] When deploying large cluster servers, engineers can effectively monitor the correctness and legality of pre-boot boot, avoiding the traditional method of plugging and unplugging monitors to monitor whether the server boots normally.

[0093] The embodiment of the present application provides a server system startup method, such as Figure 3 As shown, the method includes:

[0094] Multi-dimensional hardware feature identification: supports joint matching of server network card MAC address, motherboard part number (Part Number), motherboard PN (Product Number), motherboard bundle number (Bundle Number), CPU model, CPU manufacturer and architecture;

[0095] Dynamic policy engine: Automatically selects the optimal server startup program based on hardware characteristics, supporting priority configuration and policy nesting;

[0096] Zero-touch deployment: Reduces manual intervention and improves system deployment efficiency for heterogeneous server clusters.

[0097] Step S01, creating a system image file set on the system server to be installed according to the business type;

[0098] Step S011, configuring the system image files involved in all business types in the configuration file of the system server to be installed, and obtaining a system image file boot list;

[0099] Set the system image file boot list to the system image file set;

[0100] The system image file set includes system image files that match the hardware feature information in each dimension.

[0101] Here, all service types involving the operating system OS boot list are configured in the grub.cfg file of the DHCP server, and the system image files involved in all service types are configured in the grub.cfg file; a system image file boot list is established for subsequent dynamic calling.

[0102] Among them, business types include storage, computing, database, etc.

[0103] Step S02: Acquire hardware feature information of the server to be installed with the system from multiple dimensions.

[0104] Specifically, the multi-dimensional hardware feature collection engine hwscan is integrated into grubaa64.efi. During the GRUB boot phase, it dynamically collects device hardware feature information, obtains hardware feature information through EFI running services, SMBIOS, and ACPI tables; during the UEFI pre-boot phase, it obtains hardware feature information by calling commands in the grubshell script and assigns it to feature variables:

[0105] A. Network card MAC address: Read directly from the network card firmware:

[0106] net_ls_addr;

[0107] B. Host serial number SN: Get the host serial number (Serial Number) through the SMBIOS table:

[0108] smbios--type1--get-string7--setSerialNumber;

[0109] B. Motherboard Product Number: Get the motherboard product number through the SMBIOS table:

[0110] smbios--type2--get-string6--setBoardProductName;

[0111] D. Motherboard Bundle Number BN: Get the motherboard bundle number through the SMBIOS table:

[0112] smbios--type2--get-string5--setBundleNumber;

[0113] E. Model Product Name PN: Get the model product name through the SMBIOS table:

[0114] smbios--type1--get-string5--setProductName;

[0115] F. Processor CPU Manufacturer: Get CPU manufacturer information through the SMBIOS table CPU Manufacturer:

[0116] smbios--type4--get-string7--setCPUManufacturer;

[0117] G. Architecture type: Get the architecture Aarch through the CPUID instruction:

[0118] Echo $grub_cpu;

[0119] Step S03 : setting the priority of the hardware feature information in each dimension corresponding to the matching system image file according to the accuracy of the hardware feature information.

[0120] Step S031, according to the hardware feature information of each dimension corresponding to the hardware feature information of the system image file, the priority is server network card MAC address, server host serial number, server motherboard material number, server motherboard package number, server model product name, server processor manufacturer, and server system architecture type.

[0121] Specifically, a dynamic policy matching engine is defined. The policy engine selects the corresponding image file according to the priority matching rules; if—elif—else—fi uses conditional branches to match according to priority and sets the default boot item to the optimal boot item.

[0122] The priority for matching image files based on hardware feature information dimensions is: network card MAC address -> host serial number SN -> motherboard material number PN -> motherboard package number BN -> model product name PN -> CPU manufacturer -> architecture type, a total of 7 dimensions; sub-item feature values are generated based on the hardware feature information of each dimension for subsequent verification.

[0123] Step S04 , matching the hardware feature information in each dimension to the corresponding system image file according to the priority of the hardware feature information in each dimension to the matching system image file.

[0124] Step S041, as Figure 4 As shown, create a file directory for each hardware feature information dimension;

[0125] According to the priority of the hardware feature information, namely, the server network card MAC address, the server host serial number, the server motherboard material number, the server motherboard package number, the server model product name, the server processor manufacturer, and the server system architecture type, it is determined whether a configuration file named after the hardware feature information of the current dimension can be matched in the file directory of the hardware feature information of the current dimension;

[0126] If so, determine that the startup parameter value of the configuration file named by the current dimension hardware feature information is the system image file name corresponding to the current dimension hardware feature information; if not, judge whether the configuration file named by the hardware feature information can be matched in the file directory of the next dimension hardware feature information.

[0127] Specifically, seven hardware feature information directories are created, corresponding to the above seven dimensions. You only need to configure a cfg file in the corresponding hardware feature information directory according to the corresponding feature information. For example, according to the model PN, the model PN is NF5280M5, and the configured cfg file is NF5280M5.cfg. The content of this file only needs to state "default=system image name". The system image name is the corresponding system image name in the boot list of the grub.cfg file. The complicated configuration content is simplified to the parameter assignment "default=system image name", which reduces the possibility of static single boot system image file being tampered with.

[0128] Automatically matches the operating system or configuration corresponding to the hardware characteristics according to the preset matching priority strategy to generate a dynamic boot menu.

[0129] Generates a GRUB (boot loader) boot menu based on the matching image file results, supports nested submenus, dynamically generates the configuration file grub.cfg and loads the image, without manual intervention. The boot menu is displayed, and the default item matching the hardware feature configuration file is selected by default.

[0130] Match the corresponding system image file according to the priority strategy based on the corresponding hardware feature information.

[0131] Step S05 , determining in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set.

[0132] Step S06, obtaining the itemized feature values of the hardware feature information of each dimension according to the judgment result;

[0133] Step S061, when the system image file matched according to the hardware feature information does not exist in the system image file set, setting the item feature value of the hardware feature information to a first preset value;

[0134] When the system image file corresponding to the hardware feature information is present in the system image file set, the sub-item feature value of the hardware feature information is set to a second preset value;

[0135] When the system image file matched according to the hardware feature information does not match the content of the system image file corresponding to the hardware feature information in the system image file set, the itemized feature value of the hardware feature information is set to a third preset value.

[0136] Specifically, the legitimacy of the comprehensive feature value is verified to prevent the system image file from being tampered with.

[0137] Obtain the cfg configuration files from the TFTP (DHCP) server based on the following priorities: network card MAC address, host serial number (SN), motherboard part number (PN), motherboard package number (BN), model product name (PN), CPU manufacturer (CPU manufacturer), and architecture type. Check whether the default values of each dimension of the cfg configuration file are included in the system image file set, and define the feature values and weights of each item.

[0138] If the default value of the cfg configuration file corresponding to any hardware feature dimension is not in the system image file set, it means that there is no cfg file named according to the hardware feature information value in the image file set, and the sub-item feature value of the hardware feature dimension is assigned to 0;

[0139] When the default value of the cfg configuration file corresponding to any hardware feature dimension is in the system image file set, it means that there is a cfg file named according to the hardware feature information value in the image file set, and the content of the cfg configuration file corresponding to the hardware feature dimension is consistent with the content of the system image file boot list, then the sub-item feature value of the hardware feature dimension is 1;

[0140] If the default value of the cfg configuration file corresponding to any hardware feature dimension does not match the system image file set, this means that the image file set contains a cfg file named according to the hardware feature information value, but the content of the cfg configuration file corresponding to the hardware feature dimension does not match the content of the system image file boot list. In this case, the sub-item feature value of this hardware feature dimension is 2.

[0141] Among them, the first preset value is 0, the second preset value is 1, and the third preset value is 2.

[0142] The definitions of the sub-item feature values corresponding to the hardware feature information of each dimension are shown in Table 1:

[0143] Table 1

[0144]

[0145] Step S07: determining a comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights.

[0146] Specifically, the sub-item weights corresponding to the hardware features of each dimension are defined as shown in Table 2:

[0147] Table 2

[0148]

[0149] Here, the sub-item weights corresponding to the hardware features of each dimension are arranged according to the priority of the hardware feature information of each dimension corresponding to the matching system image file. The sub-item weights corresponding to the hardware features of each dimension are a geometric progression with a common ratio of 10, and the weight of each sub-item is 10 times the weight of the previous sub-item.

[0150] General formula: an =10 n-1 ( n ≥1), where a is the sub-item weight corresponding to the hardware features of each dimension, and n is an integer ≥ 1.

[0151] Step S071, obtaining the sub-item feature weight WM corresponding to the server network card MAC address, and the sub-item feature value M corresponding to the server network card MAC address; the sub-item feature weight WS of the server host serial number, and the sub-item feature value S of the server host serial number; obtaining the sub-item feature weight WP1 corresponding to the server motherboard material number, and the sub-item feature value P1 corresponding to the server motherboard material number;

[0152] Get the sub-item feature weight WB corresponding to the server motherboard package number, and the sub-item feature value B corresponding to the server motherboard package number; get the sub-item feature weight WP2 corresponding to the server model product name, and the sub-item feature value P2 corresponding to the server model product name; get the sub-item feature weight WC corresponding to the server processor manufacturer, and the sub-item feature value C corresponding to the server processor manufacturer;

[0153] Obtain the sub-item feature weight WA and the sub-item feature value A corresponding to the server system architecture type;

[0154] The comprehensive eigenvalue N is calculated using the formula: N=WM×M+WS×S+WP1×P1+WB×B+WP2×P2+WC×C+WA×A.

[0155] Step S08, verifying the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0156] Start the system server to be installed through the target system image file.

[0157] Step S081, verifying the comprehensive characteristic value to determine whether the comprehensive characteristic value is a first preset value;

[0158] If yes, then import the new architecture type on the server where the system is to be installed, and match the system image file corresponding to the new architecture in the startup directory of the new architecture type; if no, then verify the sub-item eigenvalues corresponding to the comprehensive eigenvalues bit by bit from right to left according to the decimal sequence;

[0159] Verify the item eigenvalues corresponding to the comprehensive eigenvalues bit by bit from right to left according to the decimal sequence, including:

[0160] When the sub-item feature value corresponding to the comprehensive feature value is the second preset value for the first time, the hardware feature information dimension corresponding to the sub-item feature value is used as the target hardware feature information dimension, and the system server to be installed is started by matching the corresponding system image file with the target hardware feature information dimension;

[0161] When the sub-item feature value corresponding to the comprehensive feature value is the third preset value, there is a modified record in the system image file matched by the hardware feature information dimension corresponding to the sub-item feature value.

[0162] Specifically, the calculated comprehensive characteristic value is verified. If the comprehensive characteristic value is 0, it means that the server encounters a new configuration and a new architecture, and the default boot is not defined. The engineer is reminded to manually intervene, enter the new architecture type, and define the cfg file corresponding to the new architecture in the AarchBoot startup directory.

[0163] The comprehensive feature value is checked bit by bit. If the sub-item feature value of the comprehensive feature value is 2, it means that the boot image file has been tampered with or the configuration is invalid, and the engineer is prompted to manually intervene.

[0164] Record the server SN and comprehensive feature value in the checksum.cfg file on the PXE server for engineers to monitor in the background. For example, if the server's comprehensive feature value is 1010020, the server is booted preferentially according to the system image file corresponding to the hardware feature dimension with the lowest sub-item feature value of 1 in the decimal sequence. That is, the server is booted according to the boot item corresponding to the hardware feature dimension of the fifth digit of the model product name PN. In this case, the second sub-item feature value is 2, indicating that the boot item definition based on the host serial number SN is illegal. In other words, there is a possibility that the system image file corresponding to the host serial number SN has been tampered with. This is for engineers to analyze and monitor the overall progress later.

[0165] Step S082, obtaining the target system image file;

[0166] Use the installation tool to write the target system image file to the server physical media;

[0167] Set the installation mode corresponding to the target system image file in the operating system of the system server to be installed;

[0168] Adjust the boot sequence of the hardware of the system server to be installed, and set the USB disk or CD as the first boot item of the system server to be installed;

[0169] Save the settings and restart the server. The system server to be installed will start from the target system image file.

[0170] When the target system image file is a Linux image file, the system will enter the installation interface or provide server rescue mode;

[0171] Repair the server boot file using the Linux chroot tool (repair tool) in the target system image file.

[0172] Here, as Figure 5 As shown, this application collects network card MAC address, motherboard material number, motherboard PN, motherboard package number, CPU model, CPU manufacturer and architecture information in the UEFI pre-boot phase; matches the system startup item corresponding to the optimal hardware feature dimension through a dynamic policy engine; dynamically generates the corresponding GRUB configuration file and loads and executes it through the grubaa64.efi engine, realizing a very flexible intelligent boot management system;

[0173] Multi-dimensional hardware feature information fusion: The first to combine network card MAC address, motherboard material number, motherboard PN, motherboard package number, CPU model, CPU manufacturer and architecture information as the basis for image file matching;

[0174] Dynamic policy engine: supports nested priority rules, logical operator combinations, and remote policy updates, enabling highly flexible configuration management.

[0175] Deep GRUB integration: This eliminates source code modifications to the grubaa64.efi file and directly uses the released grubaa64.efi file. This allows for in-depth implementation of the newly added hardware feature information collection and matching policy parsing modules using grubshell scripts.

[0176] Secure boot execution: By calculating and verifying comprehensive feature values to verify and warn the legitimacy of PXE boot options, secure boot execution is performed and the comprehensive feature value information is uploaded to the server for engineers to monitor in the background, improving the security of server PXE pre-boot.

[0177] The dynamic policy matching engine supports the following functions:

[0178] Priority rules are nested and combined with logical operators (AND / OR); the policy library is pulled and updated from the remote server; and modifications to the grubaa64.efi file include: adding hardware feature collection interfaces (such as the hwscan() function) and integrating a policy parsing module.

[0179] In addition, the server system startup method further includes:

[0180] When the comprehensive characteristic value is verified to determine the target system image file for starting the system server to be installed, and when a failure occurs in the method of starting the system server to be installed through the target system image file, the system server to be installed is booted and started through the network pre-start program;

[0181] Boot the server to be installed using the network pre-boot program, including:

[0182] Allocate an IP address to the server to be installed using the DHCP protocol server (the first server);

[0183] Download the boot file of the system server to be installed through the TFTP protocol server (second server);

[0184] Configure the DHCP protocol server and TFTP protocol server;

[0185] Create the root directory of the TFTP server and copy the boot file to it, start the TFTP service (File Transfer Protocol service), and set the server startup options for the system to be installed.

[0186] Mount the system image file and copy the system image file to the Web server, and start the Apache software of the Web server;

[0187] After the client obtains the IP address, it downloads the core file for network booting from the TFTP protocol server (second server) and displays the installation menu;

[0188] After selecting the installation menu option, the core file and root file are loaded, and the system server to be installed is automatically started through the system image file.

[0189] After the system server to be installed is booted through the network pre-boot program, including:

[0190] Troubleshoot the server's boot system through the network pre-boot program;

[0191] When the client cannot obtain an IP address, it detects whether the DHCP protocol server (first server) is running and / or whether the firewall of the DHCP protocol server has UDP port 67 / 68 (preset port) enabled;

[0192] When the kernel file fails to load, check whether the path in the startup parameter is correct;

[0193] When the automated installation of the system server to be installed using the system image file is interrupted, the KS configuration file verification tool is used to check whether the syntax of the automated installation configuration file is correct.

[0194] The core of PXE pre-boot technology is the collaboration of a DHCP server, a TFTP server, and an installation source. Through automated tools (such as Kickstart / Cobbler), server systems can be deployed on a large scale. For production environments, it is recommended to isolate the PXE network using VLANs and firewall rules to improve security.

[0195] It can be understood that: 1. Configure the DHCP server to assign an IP address to the system server to be installed;

[0196] Configuration items:

[0197] Define a scope to specify the range of IP addresses available for allocation;

[0198] Set network parameters such as default gateway, subnet mask, etc.

[0199] Specify the location of the TFTP server so that the client can find the startup file;

[0200] 2. Configure the TFTP server to provide boot files for the client to download;

[0201] Create a TFTP root directory and copy necessary boot files (such as PXELINUX or GRUB2 boot files) to this directory;

[0202] Start the TFTP service and ensure it is running properly;

[0203] Set the BIOS / UEFI boot option of the server where the system is to be installed to support booting from the network;

[0204] 3. Prepare the system image file so that the client can access the system image through the network for installation;

[0205] Mount the system image file and copy it to the document root directory of the web server;

[0206] Make sure Apache or other web server software is installed and configured correctly;

[0207] Start the web server service;

[0208] 4. Client startup and installation process:

[0209] Obtaining an IP address: When a client starts up through the network, it first requests an IP address and other network setting information from a DHCP (Dynamic Host Configuration Protocol) server.

[0210] Downloading boot files: Based on the information provided by the DHCP server, the client contacts the Trivial File Transfer Protocol (TFTP) server to download the core files for network booting.

[0211] Show installation menu: After the core file is loaded, an installation menu will be displayed, allowing users to select different installation options;

[0212] Start installation: Once the installation option is selected, the system will load the corresponding kernel and initialize the RAM disk, and then download the complete system image file from the web server via HTTP protocol to perform the automated installation process.

[0213] This process makes full use of existing network protocols (DHCP, TFTP, and HTTP) to achieve automated deployment of operating systems without the need for physical media, greatly facilitating the management and maintenance of large-scale systems.

[0214] Troubleshoot the server's boot system using the network preboot program:

[0215] When the client cannot obtain an IP address:

[0216] Check whether the DHCP server is running: First, confirm whether the DHCP server is working properly. This can be done by executing relevant commands or checking the service status on the DHCP server. For example, in Linux, use systemctl status dhcpd (for ISC DHCP server) to view its status.

[0217] Check the firewall settings: Make sure that the DHCP server's firewall allows communication through UDP ports 67 and 68. You can check and modify the firewall rules using the following commands:

[0218] For firewalld: sudo firewall-cmd --list-all to view the current rules, and add the necessary ports with sudofirewall-cmd --add-port=67 / udp --permanent;

[0219] For iptables: You can use sud oiptables-Lvn to view the existing rules and add corresponding rules to allow traffic to pass;

[0220] When the kernel file fails to load:

[0221] Verify path correctness: If kernel file loading fails, it is usually because the path provided by the TFTP server is incorrect or the file does not exist. You need to check whether the path in the boot parameters passed to the client is correct, including but not limited to:

[0222] Check whether the correct kernel file (such as vmlinuz) and initial RAM disk file (such as initrd.img) exist in the TFTP root directory.

[0223] Confirm that the path specified in the startup configuration file (such as pxelinux.cfg / default or the GRUB configuration file) is consistent with the actual storage location;

[0224] When an automated installation is interrupted:

[0225] Check the syntax of the Kickstart configuration file: When the automated installation process is interrupted due to a configuration error, you can use a special tool to verify the syntax correctness of the Kickstart (KS) configuration file; Red Hat and its derivative distributions provide a tool called ksvalidator that can be used for this purpose; the sample command is as follows:

[0226] ksvalidator / path / to / your / kickstart.cfg;

[0227] If you don't have the ksvalidator tool, you can also try to manually check the configuration file for syntax errors or logical inconsistencies, such as partitioning schemes, software package selections, and other parts.

[0228] The preceding steps can effectively locate and resolve various issues encountered in the network pre-boot environment. Each step provides specific troubleshooting instructions for a specific type of fault, helping to quickly restore the system to normal deployment process.

[0229] The method for starting the server system provided in the embodiment of the present application can also be improved and optimized without departing from the technical solution of the present application, and these improvements and optimizations should also be regarded as the scope of protection of the present application.

[0230] This technical solution can be applied in complex application environment networks such as large data centers, heterogeneous computing, and cloud computing.

[0231] The beneficial effects of the technical solution provided by the embodiments of the present application are:

[0232] The technology of this application can achieve precise guidance and matching of server systems based on multi-dimensional hardware features, reduce manual intervention, and improve the efficiency of server system startup.

[0233] The technical solution of this application supports image file matching with more than 7 dimensions of hardware features, which can cover more than 95% of heterogeneous device scenarios, reducing the server system startup error rate to 0; the technology of this application realizes "zero-touch deployment", reducing manual configuration time by 90%, and is especially suitable for ultra-large-scale cluster servers (such as thousands of nodes); it can quickly adapt to new hardware (such as RISC-V), at which time it is necessary to update the policy file library without modifying the boot program; when the server is expanded, there is no need to manually reconfigure the network, avoiding the paralysis of the entire network due to manual configuration errors; and the booting of illegal servers is suspended, and an alert is issued for manual processing. The technical solution of this application improves the efficiency of pre-booting of large cluster servers, and automatically uploads comprehensive feature information to the server for engineers to monitor in the background.

[0234] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0235] The embodiment of the present application also provides a server system startup device, such as Figure 6 As shown, the device includes: a creation module, an acquisition module, a setting module, a matching module, a judgment module, a determination module, a verification module, and a startup module.

[0236] In this embodiment, the creation module is used to create a system image file set on the system server to be installed according to the business type;

[0237] The acquisition module is used to obtain the hardware feature information of the system server to be installed in multiple dimensions;

[0238] A setting module is used to set the priority of hardware feature information of each dimension corresponding to the matching system image file according to the accuracy of the hardware feature information;

[0239] A matching module, configured to match the hardware feature information of each dimension to the corresponding system image file according to the priority of the hardware feature information of each dimension corresponding to the matching system image file;

[0240] A judgment module is used to judge in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and obtain the sub-item feature value of the hardware feature information of each dimension according to the judgment result;

[0241] A determination module is used to determine a comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0242] A verification module is used to verify the comprehensive characteristic value and determine the target system image file to be started by the system server to be installed;

[0243] The startup module is used to start the system server to be installed through the target system image file.

[0244] In this embodiment, the setting module is used to match the hardware feature information of the system image file according to the hardware feature information of each dimension, and the priority is server network card MAC address, server host serial number, server motherboard material number, server motherboard package number, server model product name, server processor manufacturer, and server system architecture type.

[0245] In one embodiment, the matching module is used to create a file directory for each hardware feature information dimension;

[0246] According to the priority of the hardware feature information, namely, the server network card MAC address, the server host serial number, the server motherboard material number, the server motherboard package number, the server model product name, the server processor manufacturer, and the server system architecture type, it is determined whether a configuration file named after the hardware feature information of the current dimension can be matched in the file directory of the hardware feature information of the current dimension;

[0247] If so, determine that the startup parameter value of the configuration file named by the current dimension hardware feature information is the system image file name corresponding to the current dimension hardware feature information; if not, judge whether the configuration file named by the hardware feature information can be matched in the file directory of the next dimension hardware feature information.

[0248] In one embodiment, the judgment module is configured to set the itemized feature value of the hardware feature information to a first preset value when the system image file matched according to the hardware feature information does not exist in the system image file set;

[0249] When the system image file corresponding to the hardware feature information is present in the system image file set, the sub-item feature value of the hardware feature information is set to a second preset value;

[0250] When the system image file matched according to the hardware feature information does not match the content of the system image file corresponding to the hardware feature information in the system image file set, the itemized feature value of the hardware feature information is set to a third preset value.

[0251] In one embodiment, the determination module is used to obtain the sub-item feature weight WM corresponding to the server network card MAC address, the sub-item feature value M corresponding to the server network card MAC address; the sub-item feature weight WS of the server host serial number, the sub-item feature value S of the server host serial number; obtain the sub-item feature weight WP1 corresponding to the server motherboard material number, and the sub-item feature value P1 corresponding to the server motherboard material number;

[0252] Get the sub-item feature weight WB corresponding to the server motherboard package number, and the sub-item feature value B corresponding to the server motherboard package number; get the sub-item feature weight WP2 corresponding to the server model product name, and the sub-item feature value P2 corresponding to the server model product name; get the sub-item feature weight WC corresponding to the server processor manufacturer, and the sub-item feature value C corresponding to the server processor manufacturer;

[0253] Obtain the sub-item feature weight WA and the sub-item feature value A corresponding to the server system architecture type;

[0254] The comprehensive eigenvalue N is calculated using the formula: N=WM×M+WS×S+WP1×P1+WB×B+WP2×P2+WC×C+WA×A.

[0255] In one embodiment, the determination module is configured to arrange the sub-item weights corresponding to the hardware features of each dimension according to the priority of the hardware feature information of each dimension corresponding to the matching system image file, and the sub-item weights corresponding to the hardware features of each dimension are a geometric progression with a common ratio of 10;

[0256] The general formula for a geometric sequence is: an =10 n-1 ,in, a is the sub-item weight corresponding to the hardware features of each dimension, and n is an integer ≥ 1.

[0257] In one embodiment, the verification module is used to verify the comprehensive characteristic value to determine whether the comprehensive characteristic value is a first preset value;

[0258] If yes, then import the new architecture type on the server where the system is to be installed, and match the system image file corresponding to the new architecture in the startup directory of the new architecture type; if no, then verify the sub-item eigenvalues corresponding to the comprehensive eigenvalues bit by bit from right to left according to the decimal sequence;

[0259] Verify the item eigenvalues corresponding to the comprehensive eigenvalues bit by bit from right to left according to the decimal sequence, including:

[0260] When the sub-item feature value corresponding to the comprehensive feature value is the second preset value for the first time, the hardware feature information dimension corresponding to the sub-item feature value is used as the target hardware feature information dimension, and the system server to be installed is started by matching the corresponding system image file with the target hardware feature information dimension;

[0261] When the sub-item feature value corresponding to the comprehensive feature value is the third preset value, there is a modified record in the system image file matched by the hardware feature information dimension corresponding to the sub-item feature value.

[0262] In one embodiment, a startup module is used to obtain a target system image file;

[0263] Use the installation tool to write the target system image file to the server physical media;

[0264] Set the installation mode corresponding to the target system image file in the operating system of the system server to be installed;

[0265] Adjust the boot sequence of the hardware of the system server to be installed, and set the USB disk or CD as the first boot item of the system server to be installed;

[0266] Save the settings and restart the server. The system server to be installed will start from the target system image file.

[0267] When the target system image file is a Linux image file, the system will enter the installation interface or provide server rescue mode;

[0268] Repair the server boot file using the Linux chroot tool in the target system image file.

[0269] In one embodiment, a module is created for configuring system image files involved in all business types in a configuration file of a system server to be installed, and obtaining a system image file boot list;

[0270] Set the system image file boot list to the system image file set;

[0271] The system image file set includes system image files that match the hardware feature information in each dimension.

[0272] In one embodiment, the startup module is further configured to allocate an IP address to the system server to be installed via a DHCP protocol server;

[0273] Download the boot file of the system server to be installed through the TFTP protocol server;

[0274] Configure the DHCP protocol server and TFTP protocol server;

[0275] Create the root directory of the TFTP server and copy the boot file to it, start the TFTP service, and set the server startup options for the system to be installed.

[0276] Mount the system image file and copy the system image file to the Web server, and start the Apache software of the Web server;

[0277] After the client obtains the IP address, it downloads the core file for network booting from the TFTP server and displays the installation menu;

[0278] After selecting the installation menu option, the core file and root file are loaded, and the system server to be installed is automatically started through the system image file.

[0279] In one embodiment, the startup module is further configured to troubleshoot a boot system of the server through a network pre-startup program;

[0280] When the client cannot obtain an IP address, it checks whether the DHCP server is running and / or whether the firewall of the DHCP server has UDP port 67 / 68 enabled;

[0281] When the kernel file fails to load, check whether the path in the startup parameter is correct;

[0282] When the automated installation of the system server to be installed using the system image file is interrupted, the KS configuration file verification tool is used to check whether the syntax of the automated installation configuration file is correct.

[0283] The beneficial effects of the technical solution provided by the embodiments of the present application are:

[0284] The technology of this application can achieve precise guidance and matching of server systems based on multi-dimensional hardware features, reduce manual intervention, and improve the efficiency of server system startup.

[0285] The technical solution of this application supports image file matching with more than 7 dimensions of hardware features, which can cover more than 95% of heterogeneous device scenarios, reducing the server system startup error rate to 0; the technology of this application realizes "zero-touch deployment", reducing manual configuration time by 90%, and is especially suitable for ultra-large-scale cluster servers (such as thousands of nodes); it can quickly adapt to new hardware (such as RISC-V), at which time it is necessary to update the policy file library without modifying the boot program; when the server is expanded, there is no need to manually reconfigure the network, avoiding the paralysis of the entire network due to manual configuration errors; and the booting of illegal servers is suspended, and an alert is issued for manual processing. The technical solution of this application improves the efficiency of pre-booting of large cluster servers, and automatically uploads comprehensive feature information to the server for engineers to monitor in the background.

[0286] For the description of the features in the embodiment corresponding to the server system startup device, please refer to the relevant description of the embodiment corresponding to the server system startup method, and no further details will be given here.

[0287] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps of an embodiment of a server system startup method, the method comprising:

[0288] Create a system image file set on the system server to be installed according to the business type;

[0289] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0290] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0291] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0292] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0293] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0294] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0295] Start the system server to be installed through the target system image file.

[0296] like Figure 7 As shown, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the steps of an embodiment of a server system startup method when running, the method comprising:

[0297] Create a system image file set on the system server to be installed according to the business type;

[0298] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0299] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0300] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0301] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0302] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0303] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0304] Start the system server to be installed through the target system image file.

[0305] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0306] An embodiment of the present application further provides a computer program product, the computer program product including a computer program. When the computer program is executed by a processor, the steps of the server system startup method embodiment are implemented. The method includes:

[0307] Create a system image file set on the system server to be installed according to the business type;

[0308] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0309] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0310] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0311] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0312] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0313] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0314] Start the system server to be installed through the target system image file.

[0315] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, implementing the steps in the server system startup method embodiment, the method including:

[0316] Create a system image file set on the system server to be installed according to the business type;

[0317] Obtain hardware feature information of the system server to be installed from multiple dimensions;

[0318] According to the accuracy of hardware feature information, the priority of hardware feature information in each dimension corresponding to the matching system image file is set;

[0319] Match the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file;

[0320] It is judged in turn whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and the sub-item feature value of the hardware feature information of each dimension is obtained according to the judgment result;

[0321] Determine the comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights;

[0322] Verify the comprehensive characteristic value to determine the target system image file to be started by the system server to be installed;

[0323] Start the system server to be installed through the target system image file.

[0324] The technical solution of this application supports image file matching with more than 7 dimensions of hardware features, which can cover more than 95% of heterogeneous device scenarios, reducing the server system startup error rate to 0; the technology of this application realizes "zero-touch deployment", reducing manual configuration time by 90%, and is especially suitable for ultra-large-scale cluster servers (such as thousands of nodes); it can quickly adapt to new hardware (such as RISC-V), at which time it is necessary to update the policy file library without modifying the boot program; when the server is expanded, there is no need to manually reconfigure the network, avoiding the paralysis of the entire network due to manual configuration errors; and the booting of illegal servers is suspended, and an alert is issued for manual processing. The technical solution of this application improves the efficiency of pre-booting of large cluster servers, and automatically uploads comprehensive feature information to the server for engineers to monitor in the background.

[0325] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0326] The above is a detailed introduction to the server system startup method, device, equipment and medium provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A server system startup method, characterized in that: The method comprises: Create a system image file set on the system server to be installed according to the business type; Acquire hardware feature information of the server to be installed system from multiple dimensions; Setting the priority of the hardware feature information in each dimension corresponding to the matching system image file according to the accuracy of the hardware feature information; Matching the hardware feature information of each dimension to the corresponding system image file according to the priority of the corresponding matching system image file of the hardware feature information of each dimension; Determine in sequence whether the system image file corresponding to the hardware feature information of each dimension exists in the system image file set, and obtain the itemized feature value of the hardware feature information of each dimension according to the determination result; Determine a comprehensive feature value based on the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights; Verifying the comprehensive characteristic value to determine the target system image file to be started on the system server to be installed; Starting the system server to be installed through the target system image file; The matching of the hardware feature information in each dimension to the corresponding system image file according to the priority of the hardware feature information in each dimension to the corresponding system image file includes: Create file directories for each hardware feature information dimension; According to the priority of the hardware feature information, namely, the server network card MAC address, the server host serial number, the server motherboard material number, the server motherboard package number, the server model product name, the server processor manufacturer, and the server system architecture type, it is determined in the file directory of the hardware feature information of the current dimension whether a configuration file named after the hardware feature information of the current dimension can be matched; If so, determine that the startup parameter value of the configuration file named by the current dimension hardware feature information is the system image file name corresponding to the current dimension hardware feature information; if not, judge whether the configuration file named by the hardware feature information can be matched in the file directory of the next dimension hardware feature information.

2. The server system startup method according to claim 1, characterized in that: The step of setting the priority of the hardware feature information in each dimension corresponding to the matching system image file according to the accuracy of the hardware feature information includes: According to the hardware feature information of each dimension, the priority of the hardware feature information corresponding to the matching system image file is server network card MAC address, server host serial number, server motherboard material number, server motherboard package number, server model product name, server processor manufacturer, and server system architecture type.

3. The server system startup method according to claim 2, characterized in that: The step of sequentially judging whether the system image file corresponding to each dimension of hardware feature information exists in the system image file set and obtaining the itemized feature value of each dimension of hardware feature information according to the judgment result includes: When the system image file matched according to the hardware feature information does not exist in the system image file set, setting the item feature value of the hardware feature information to a first preset value; When the system image file corresponding to the hardware feature information is present in the system image file set, setting the item feature value of the hardware feature information to a second preset value; When the system image file matched according to the hardware feature information does not match the content of the system image file corresponding to the hardware feature information in the system image file set, the item feature value of the hardware feature information is set to a third preset value.

4. The server system startup method according to claim 3, characterized in that: The determining of the comprehensive feature value according to the sub-item feature values of the hardware features in each dimension and the corresponding sub-item feature weights includes: Get the sub-item feature weight WM and sub-item feature value M corresponding to the server network card MAC address; the sub-item feature weight WS and sub-item feature value S of the server host serial number; get the sub-item feature weight WP1 and sub-item feature value P1 corresponding to the server motherboard material number; Get the sub-item feature weight WB corresponding to the server motherboard package number, and the sub-item feature value B corresponding to the server motherboard package number; get the sub-item feature weight WP2 corresponding to the server model product name, and the sub-item feature value P2 corresponding to the server model product name; get the sub-item feature weight WC corresponding to the server processor manufacturer, and the sub-item feature value C corresponding to the server processor manufacturer; Obtain the sub-item feature weight WA and the sub-item feature value A corresponding to the server system architecture type; The comprehensive eigenvalue N is calculated using the formula: N=WM×M+WS×S+WP1×P1+WB×B+WP2×P2+WC×C+WA×A.

5. The server system startup method according to claim 4, characterized in that: Arrange the sub-item weights corresponding to the hardware features of each dimension according to the priority of the matching system image file corresponding to the hardware feature information of each dimension, wherein the sub-item weights corresponding to the hardware features of each dimension are a geometric progression with a common ratio of 10; The general formula of the geometric progression is: an =10 n-1 ,in, a is the sub-item weight corresponding to the hardware features of each dimension, and n is an integer ≥ 1.

6. The server system startup method according to claim 4, characterized in that: The step of verifying the comprehensive characteristic value to determine the target system image file to be started on the system server to be installed includes: Verifying the comprehensive characteristic value to determine whether the comprehensive characteristic value is a first preset value; If so, import the new architecture type on the server of the system to be installed, and match the system image file corresponding to the new architecture in the new architecture type startup directory; if not, verify the sub-item feature values corresponding to the comprehensive feature value bit by bit from right to left according to the decimal sequence.

7. The server system startup method according to claim 6, characterized in that: The checking of the sub-item eigenvalues corresponding to the comprehensive eigenvalues bit by bit from right to left according to the decimal sequence includes: When the sub-item feature value corresponding to the comprehensive feature value is the second preset value for the first time, the hardware feature information dimension corresponding to the sub-item feature value is used as the target hardware feature information dimension, and the system server to be installed is started by matching the target hardware feature information dimension with the corresponding system image file; When the sub-item feature value corresponding to the comprehensive feature value is a third preset value, it is determined that a modified record exists in the system image file matched by the hardware feature information dimension corresponding to the sub-item feature value.

8. The server system startup method according to claim 1, characterized in that: The starting the system server to be installed by using the target system image file includes: Obtaining the target system image file; Writing the target system image file into the server physical medium through the installation tool; Setting an installation mode corresponding to the target system image file in the operating system of the system server to be installed; Adjust the boot sequence of the hardware of the system server to be installed, and set the USB flash drive or CD as the first boot item of the system server to be installed; Save the settings and restart the server, and the system server to be installed starts from the target system image file; When the target system image file is a Linux image file, the installation interface is entered or the server rescue mode is provided; Repair the server boot file using the Linux repair tool in the target system image file.

9. The server system startup method according to claim 1, characterized in that: The step of creating a system image file set on the system server to be installed according to the business type includes: Storing system image files corresponding to all service types in the configuration file of the system server to be installed, and obtaining a system image file boot list; Setting the system image file boot list to a system image file set; The system image file set includes system image files that correspond to and match hardware feature information in each dimension.

10. The server system startup method according to claim 1, characterized in that: The method further comprises: When the comprehensive characteristic value is verified to determine the target system image file to be started by the system server to be installed, and when a failure occurs in the method of starting the system server to be installed through the target system image file, the system server to be installed is booted and started through the network pre-start program; The booting and starting of the system server to be installed by the network pre-start program includes: Allocate an IP address to the server of the system to be installed by the first server; Downloading the boot file of the system server to be installed through the second server; configuring the first server and the second server; Creating a root directory of the second server and copying the boot file, starting the file transfer protocol service, and setting the startup options of the system server to be installed; Mounting the system image file and copying the system image file to the Web server, and starting the software of the Web server; After obtaining the IP address, the client downloads the core file of the network boot from the second server and displays the installation menu; After selecting the installation menu option, the core file and the root file are loaded, and the system server to be installed is automatically started through the system image file.

11. The server system startup method according to claim 10, characterized in that: After the system server to be installed is booted and started by the network pre-start program, the following steps are included: Troubleshoot the server's boot system through the network pre-boot program; When the client cannot obtain the IP address, it detects whether the first server is running and / or whether the firewall of the first server has a preset port enabled; When the kernel file fails to load, check whether the path in the startup parameter is correct; When the automatic installation of the system server to be installed is interrupted by using the system image file, a configuration file verification tool is used to check whether the syntax of the automatic installation configuration file is correct.

12. An electronic device, characterized in that: include: memory for storing computer programs; A processor, configured to implement the steps of the server system startup method according to any one of claims 1 to 11 when executing the computer program.

13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the server system startup method according to any one of claims 1 to 11 are implemented.

14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the server system startup method according to any one of claims 1 to 11 are implemented.

Images