Server Hardware Configuration Method, Apparatus, Device, Storage Medium and Product

Abstract

The present application discloses a server hardware configuration method, device, equipment, storage medium and product, relating to the technical fields of server hardware configuration and intelligent supply chain management. After selecting a target server host in a graphical interface, a database established based on hardware manufacturer compatibility rules is used to automatically load a list of compatible expansion cabinets, avoiding manual matching, reducing the dependence on technical documents and manual experience, significantly improving the configuration efficiency and reducing the error rate. At the same time, interface, resource and topology connection verification is performed during the configuration process, and global resource verification can be carried out for multi-level expansion architectures to make up for the defects of traditional single-level verification. If the verification fails, the error information is automatically determined and a predefined solution strategy is matched to quickly locate and handle configuration problems, effectively reducing hardware returns, rework and system downtime, and reducing after-sales costs.

Description

Technical Field

[0001] This application relates to the technical fields of server hardware configuration and intelligent supply chain management, and particularly to a server hardware configuration method, device, equipment, storage medium, and product. Background Art

[0002] In the technical fields of server hardware configuration and intelligent supply chain management, the efficient configuration of servers and the smooth operation of the supply chain are crucial for an enterprise's informatization construction and operation cost control. With the rapid development of information technology, the application scenarios of servers are becoming increasingly extensive, and the complexity of their hardware configuration is also continuously increasing. During the server procurement process, ensuring the compatibility between server hosts and components such as expansion cabinets, rationally configuring global resources, and achieving intelligent supply chain management have become key links. This not only affects whether the server can operate stably but also directly impacts the enterprise's operation efficiency and cost investment.

[0003] However, traditional server hardware configuration mainly relies on manual matching of compatibility parameters between server hosts and expansion cabinets, such as interface protocols, power supply power, firmware versions, etc. This method highly depends on technical documents and manual experience, not only being inefficient and time-consuming but also extremely prone to errors. At the same time, hardware manufacturers frequently update their product lines, but the recommended information lags seriously, making it difficult to meet actual needs. When facing complex multi-level expansion architectures, traditional methods can only support single-level verification and cannot effectively verify global resources such as bandwidth, heat dissipation, and power supply, affecting the overall performance and stability of the server system. In addition, problems such as hardware returns, rework, or system downtime caused by configuration errors are common. According to statistics, approximately 15% of server orders need to be processed a second time due to compatibility issues, which undoubtedly significantly increases after-sales costs. These problems severely restrict the development of server hardware configuration and intelligent supply chain management technologies and urgently require innovative technologies to solve them. Summary of the Invention

[0004] This application provides a server hardware configuration method, device, equipment, storage medium, and product to at least solve the problems of low efficiency of manual configuration, lack of dynamic compatibility, insufficient support for complex topologies, and high after-sales costs in related technologies.

[0005] The present application provides a server hardware configuration method, including: in response to a user's selection input of a target server host in a graphical interface, loading a list of expansion enclosures compatible with the target server host based on a pre-established compatibility database; the compatibility database is generated according to the compatibility rules of the hardware manufacturer's product line; in response to the user's configuration operation on the target expansion enclosure in the expansion enclosure list, determining configuration parameters and performing compatibility verification, the compatibility verification includes at least one of interface verification, resource verification, and topology connection verification; in the case of a failed compatibility verification, determining an error message and matching a solution strategy corresponding to the error message from a predefined rule library; in the case of a successful compatibility verification, generating a hardware configuration list corresponding to the target server host.

[0006] The present application further provides a server hardware configuration device, including:

[0007] A loading module, configured to, in response to a user's selection input of a target server host in a graphical interface, load a list of expansion enclosures compatible with the target server host based on a pre-established compatibility database; the compatibility database is generated according to the compatibility rules of the hardware manufacturer's product line;

[0008] A configuration and verification module, configured to, in response to the user's configuration operation on the target expansion enclosure in the expansion enclosure list, determine configuration parameters and perform compatibility verification, the compatibility verification includes at least one of interface verification, resource verification, and topology connection verification;

[0009] A verification result processing module, configured to, in the case of a failed compatibility verification, determine an error message and match a solution strategy corresponding to the error message from a predefined rule library; in the case of a successful compatibility verification, generate a hardware configuration list corresponding to the target server host.

[0010] The present application further provides an electronic device, including: a memory for storing a computer program; a processor for implementing the steps of any one of the above server hardware configuration methods when executing the computer program.

[0011] The present application further provides a computer-readable storage medium, in which a computer program is stored, and wherein the computer program implements the steps of any one of the above server hardware configuration methods when executed by a processor.

[0012] The present application further provides a computer program product, including a computer program, and the computer program implements the steps of any one of the above server hardware configuration methods when executed by a processor.

[0013] After selecting the target server host in the graphical interface, this application automatically loads the list of compatible expansion enclosures, avoiding the need for users to manually match compatibility parameters, reducing the dependence on technical documents and manual experience, significantly improving the configuration efficiency, and at the same time reducing the error probability. A compatibility database is established in advance based on the compatibility rules of the hardware manufacturer's products, which reflects the changes in the hardware manufacturer's product line in real time and provides the latest list of compatible expansion enclosures when the user makes a selection, solving the problem of missing dynamic compatibility and avoiding lag in recommended information. Compatibility verification is carried out, covering interface verification, resource verification, and topology connection verification, which can verify the global resources in a multi-level expansion architecture, making up for the deficiency of traditional methods that only support single-level verification. When the compatibility verification fails, the error information is determined and the solution strategy is matched, which helps to quickly discover and solve problems in the configuration process, reducing hardware returns, rework, or system downtime caused by configuration errors, thereby reducing after-sales costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] To more clearly illustrate the embodiments of the present application, the following will briefly introduce the drawings required in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0015] Figure 1 It is a flowchart showing a method for configuring server hardware provided by an embodiment of the present application;

[0016] Figure 2 It is a logical diagram showing the compatibility verification provided by an embodiment of the present application;

[0017] Figure 3 It is a structural diagram showing a device for configuring server hardware provided by an embodiment of the present application;

[0018] Figure 4 It is a structural diagram showing an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the protection scope of the present application.

[0020] It should be noted that in the description of this application, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly 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, rather than to describe a specific order or sequence.

[0021] To more clearly illustrate the embodiments of this application, the following will briefly introduce the technical terms required in the embodiments:

[0022] The server host, usually called the Head Unit, is the core control part of the server. It usually includes key components such as a processor, memory, and management interface, and is responsible for controlling and managing the operation of the entire system and coordinating the work of each component.

[0023] The Expansion Enclosure is a device used to expand the functions and capacity of the server. It can be connected to the server host to provide additional storage slots, I / O interfaces, power modules, etc., to increase the storage capacity, processing power, or connectivity of the system. For example, when the storage capacity of the server is insufficient, more hard drives can be installed by adding an expansion enclosure to expand the storage resources; or when more external devices need to be connected, the expansion enclosure can provide additional I / O interfaces to meet the requirements.

[0024] Compatibility parameters include: interface type and protocol, power supply specification, firmware version, bus bandwidth, heat dissipation requirements, logical unit number support, and operating system and driver.

[0025] To enable those skilled in the art of this technology to better understand the solution of this application, the following will further elaborate on this application in conjunction with the accompanying drawings and specific implementation manners.

[0026] In combination with the specific application environment architecture or specific hardware architecture on which the execution of the server hardware configuration method depends, the specific application environment architecture or specific hardware architecture will be described herein.

[0027] The specific application environment architecture includes a graphical interface application environment, a compatibility database management system, a predefined rule library management system, a message queue, and a data transmission environment.

[0028] Graphical interface application environment: Users operate through a graphical interface, which usually means there is a graphical management system. This system may run on a server and provide services through the network. Users can use various terminal devices (such as personal computers, tablets, etc.) to connect to the management system through the network to perform server hardware configuration operations. For example, in the management scenario of a data center, an administrator can access the graphical management system through their computer in a remote office to configure server hardware.

[0029] Compatibility database management system: The pre-established compatibility database requires a corresponding database management system to store and manage data. This database management system may run on one or more servers and is responsible for generating and maintaining compatibility data according to the compatibility rules of the hardware manufacturer's product line. For example, for large hardware manufacturers, there may be a dedicated database server cluster to store and manage a large amount of compatibility information, and the database needs to be updated regularly to reflect the latest hardware compatibility situation.

[0030] Predefined rule library management system: The predefined rule library also requires a management system to maintain and manage error information and its corresponding solution strategies. This system may cooperate with the compatibility database management system to quickly retrieve and provide appropriate solution strategies from the rule library according to different error information. For example, when the compatibility check fails, this management system can quickly locate the corresponding error information and return an effective solution strategy to guide users to solve hardware configuration problems.

[0031] Message queue and data transmission environment: During the configuration process, data transmission and interaction may be involved. For example, when performing a compatibility check, data may need to be obtained from different system components (such as the compatibility database, predefined rule library, etc.), which requires a reliable data transmission mechanism such as a message queue. The message queue can transfer data between different system components to ensure reliable data transmission and asynchronous processing, improving the performance and stability of the system.

[0032] The specific hardware architecture includes the target server host, expansion chassis, and other related hardware devices.

[0033] Target server host: The target server host is the core device for hardware configuration. Its hardware architecture may include a processor, memory, storage devices, network interfaces, etc. Different server hosts may have different hardware specifications and performance parameters, and these factors need to be considered during the configuration process to ensure compatibility with the expansion chassis. For example, some server hosts may only support specific types of interfaces or limited resources, and strict compatibility checks are required when selecting an expansion chassis.

[0034] Expansion Cabinet: The expansion cabinet is used to expand the functions of the server host, which may include a storage expansion cabinet (for increasing the storage capacity of the server), a network expansion cabinet (for increasing network interfaces or improving network performance), etc. The hardware architectures of expansion cabinets also vary. For example, a storage expansion cabinet may contain multiple hard disk trays and controllers, and a network expansion cabinet may contain multiple network interface modules. During the configuration process, the interface type, resource requirements, and topology connection method of the expansion cabinet need to be strictly verified for compatibility with the target server host.

[0035] Other Related Hardware Devices: In addition to the target server host and the expansion cabinet, some other hardware devices may be required to support the entire configuration process. For example, cables used to connect the server host and the expansion cabinet, such as Serial Attached SCSI (SAS) cables, Ethernet cables, etc. The specifications and quality of these cables will also affect the hardware compatibility and performance. In addition, some hardware devices may be required to implement data storage and transmission, such as storage arrays, network switches, etc. The hardware architectures and performances of these devices also need to match the hardware configuration of the entire system.

[0036] Through the above descriptions of the specific application environment architecture and specific hardware architecture, the operating environment and hardware foundation of the server hardware configuration method in practical applications can be better understood, thus ensuring the effective implementation of the method and the accuracy and stability of the hardware configuration.

[0037] Embodiments of the present application provide a server hardware configuration method, which is described in detail in combination with the execution flow of the server hardware configuration method.

[0038] As Figure 1 shown, Figure 1 is a schematic flowchart of a server hardware configuration method provided by an embodiment of the present application. The method includes the following steps S101 to S104:

[0039] S101. In response to the user's selection input of the target server host in the graphical interface, load a list of expansion cabinets compatible with the target server host based on a pre-established compatibility database.

[0040] Among them, the compatibility database is generated according to the compatibility rules of the hardware manufacturer's product line.

[0041] In response to the target server host selected by the user, determine the model (head_id) of the target server host. Exemplarily, head_id = HX5000.

[0042] List of expansion enclosures compatible with the target server host, such as EX-3500 and EX-3200. It can be displayed classified by different expansion enclosure types. It can be storage type, network type, Graphics Processing Unit (GPU) type, etc. The expansion enclosure type can be used as a filtering condition to filter out expansion enclosures that do not match the interface of the target server host or are not firmware-compatible.

[0043] In some embodiments, the pre-established compatibility database can adopt a hybrid architecture of a relational database and a document database. The relational database is used to store structured static parameters, such as MySQL and PostgreSQL. The document database is responsible for managing dynamic documents, such as MongoDB. Thus, it takes into account the structured storage requirements of parameters and the dynamic management requirements of documents.

[0044] Exemplarily, the list of expansion enclosures compatible with the target server host is obtained through the / api / expansions?head_id=HX5000 interface. The following is the pseudo-code. The list of expansion enclosures compatible with the target server host is schematically shown with one expansion enclosure here.

[0045]

[0046] The expansion enclosure model shown in the pseudo-code is EX3500. The type of this expansion enclosure is storage type. The power consumption of this expansion enclosure is 180 watts and it requires a PCIe 5.0 interface to work properly.

[0047] The following will introduce the establishment process of the compatibility database, including the following steps S1011~S1014:

[0048] S1011. Obtain the static parameters of the server host and the expansion enclosure, and establish a static parameter table.

[0049] Static parameters are the inherent physical properties of the server host and the expansion enclosure, and usually do not change with the change of firmware or manufacturer policies. Static parameters include but are not limited to: interface type, size, maximum power supply, weight, power consumption, installation specifications;

[0050] Exemplarily, the static parameters of the server host are shown in Table 1:

[0051] Table 1

[0052]

[0053] The static parameters of the expansion enclosure (Expansions) are shown in Table 2:

[0054] Table 2

[0055]

[0056] S1012. Obtain the dynamic parameters of the server host and the expansion cabinet, and establish a dynamic parameter table.

[0057] Dynamic parameters are parameters that change with firmware updates and vendor policy adjustments. The dynamic parameter table includes, but is not limited to, the firmware compatibility table (Firmware_Compatibility) and the vendor update log (Vendor_Logs);

[0058] The dynamic parameters are shown in Table 3:

[0059] Table 3

[0060]

[0061] S1013. Establish an association relationship between the static parameter table and the firmware compatibility table to generate a list of compatible devices;

[0062] Associate the static parameter table with the firmware compatibility table to generate a list of compatible devices. Optionally, associate the static parameters with the solid-state compatibility table through the server host model and the expansion cabinet model to generate a list of compatible devices. This facilitates the system to quickly query and match compatible server hosts and expansion cabinets.

[0063] S1014. Update the list of compatible devices when the target field in the vendor update log table is updated.

[0064] Specifically, update the list of compatible devices according to the target field affected_model in the vendor update log. Link the vendor log table with the hardware table through the affected_model field to achieve automatic triggering of compatibility rule updates when the vendor releases an update, ensuring the timeliness and accuracy of the database.

[0065] Exemplarily, the vendor releases a new firmware v2.2, stating that the HX5000 server host needs to be upgraded to v2.2 to support the EX3600 expansion cabinet. The system obtains the update log through the API, writes it into the vendor update log table, and modifies the min_firmware field of EX3600 in the firmware compatibility table to v2.2. At this time, an order that has selected EX3600 but the server host firmware is v2.1 will be automatically marked as "firmware upgrade required" to ensure that the user is aware of and can handle the compatibility issue.

[0066] In the above embodiments, by obtaining the static and dynamic parameters of the server host and the expansion chassis, and establishing the corresponding tables and association relationships, it is possible to accurately determine which expansion chassis are compatible with a specific server host. The generation of the compatible device list provides a clear reference for users when selecting an expansion chassis. Users do not need to consult a large number of hardware specification documents and compatibility information by themselves. They only need to view the compatible device list to quickly understand which expansion chassis are suitable for their server host, greatly saving the time and effort of configuring server hardware and improving work efficiency. When the target field in the manufacturer update log table is updated, updating the compatible device list in a timely manner enables the system to always keep track of the latest hardware compatibility. In this way, when the hardware manufacturer releases a new firmware version or updates the hardware, the system can adjust the compatible device list in a timely manner to ensure that users can still select a compatible expansion chassis when using the new hardware version or update, thus ensuring the stability and reliability of the entire server system.

[0067] In some embodiments, before performing step S1014, first obtain the manufacturer's technical documents and firmware information, and then preprocess the manufacturer's technical documents and firmware information, including deduplication and format standardization. Then, detect the preprocessed manufacturer's technical documents and firmware information to determine whether the target field in the manufacturer update log table is updated.

[0068] Optionally, the manufacturer's technical documents and firmware information are retrieved through an Application Programming Interface (API) or a crawler. The following pseudo-code retrieves the compatibility information of the expansion chassis from the server through a compatibility query interface.

[0069]

[0070] The response of the Hypertext Transfer Protocol (HTTP) shown in the following pseudo-code includes: the model of the queried expansion chassis is EX3500, the lowest firmware version supported by this expansion chassis is v2.1, and the last update time of the compatibility information is 2023-10-01.

[0071] Optionally, establish API connections with mainstream hardware manufacturers (such as Dell iDRAC, Huawei FusionDirector, etc.), and pull the latest product specifications and compatibility lists according to a schedule (such as daily) to ensure timely access to official and authoritative data. For manufacturers that do not open APIs, deploy Python crawlers to parse technical documents in PDF / HTML format, use PyPDF2 to parse PDF documents, and the web parsing library (Beautiful Soup, BS4) to scrape web tables to extract compatibility table data, so as to cover the information of more manufacturers. Provide a management interface that allows operation and maintenance personnel to manually enter emergency updates or data of niche manufacturers as a means of data supplementation to ensure the integrity of database information.

[0072] The timed task triggers the manufacturer's API or crawler to obtain the original data, providing materials for database updates. Clean the obtained original data, remove duplicate records, and standardize the parameter format, such as unifying the power unit, interface naming, etc., to improve data quality. During the data update process, if conflicts between new and old data are found (such as inconsistent firmware requirements for the same model), trigger an alarm and have it confirmed manually to ensure the accuracy and reliability of the data. Use the database transaction log (such as MySQL Binlog) to record the change history, supporting rollback to snapshots at any point in time for convenient data recovery and traceability in case of problems.

[0073] When critical parameters (such as the minimum firmware version) are updated, the system automatically sends an email notification to the users who have placed orders to upgrade the system, enabling users to timely understand the compatibility changes of hardware devices and avoid device incompatibility caused by firmware problems.

[0074] In the above embodiments, through the automatic synchronization with the APIs of mainstream hardware manufacturers, the latest product specifications and compatibility lists can be obtained according to a schedule, ensuring that the information in the database is consistent with the latest content released by the manufacturers. The data scraping is triggered by timed tasks, realizing automated operations, reducing manual intervention, and improving the efficiency of data acquisition. The conflict detection mechanism triggers an alarm and has it confirmed manually when conflicts between new and old data are found, preventing incorrect or inconsistent data from entering the database and ensuring data consistency and reliability.

[0075] In some embodiments, before performing step S101, first obtain the server host model input by the user and determine the server host list corresponding to the server host model. Optionally, perform a keyword fuzzy search based on the server host model input by the user (such as HX-5000) to obtain the corresponding server host list. The interface model of the server host (Heads) can be used as a filtering condition for the server host list, such as interface_type=PCIe5.0. By calling the / api / heads interface to obtain the head data and supporting requests with filtering conditions, the data acquisition is more accurate, unnecessary data transmission is reduced, the efficiency of data acquisition is improved, and thus the response speed of the system is enhanced.

[0076] In the graphical interface, display the server host list in the form of a responsive table or card view. The server host list includes multiple server hosts corresponding to the server host model, as well as server host data, including but not limited to: interface type, maximum power consumption, firmware version. The following is the pseudo-code:

[0077]

[0078] The pseudo-code shown here represents obtaining the server host data of the server host with the model HX-5000. The interface type adopted by this server host is PCI Express 5.0, the maximum power consumption of this server host is 500 watts, the lowest firmware version supported by this server host is v2.1, and it is compatible with higher versions. Users can browse or search for the server head model through the graphical interface and view key parameters such as interface type, maximum power consumption, and supported firmware version, providing a convenient operation method for users, enabling users to quickly obtain the required information, and meeting the user's comprehensive understanding needs of the head information.

[0079] It should be noted that a responsive table is a table that can automatically adjust the layout and style according to the browser window size or device screen size. A card view is to display information in the form of cards. Each card usually contains a set of related data or content, such as pictures, titles, descriptions, buttons, etc. Cards can exist independently or be arranged and combined on the page to form a neat and beautiful layout.

[0080] In some embodiments, the recommended server host models are displayed in the graphical interface for users to use. The recommended server host models can be determined according to the historical hardware configuration list. The head models are recommended based on the user's historical orders or popular configurations, providing personalized recommendation services for users. For example, for users who often purchase a specific type of head, the system can recommend models that meet their past needs; for new users, the heads with popular configurations can be recommended, saving the time for users to screen head models and improving the efficiency of users to select heads.

[0081] In some embodiments, the server host data interface ( / api / heads interface) is called to determine the server host list corresponding to the server host model. The system uses Redis to cache the server host data with high-frequency access to reduce the query pressure. Using Redis to cache the head data with high-frequency access reduces the query pressure on the database. For some commonly used head data, such as the parameter information of popular models, there is no need to query the database frequently, and it can be directly obtained from the cache, improving the data reading speed, enhancing the overall performance and stability of the system. Especially in the case of high concurrency, it can effectively reduce the burden on the database and ensure the normal operation of the system.

[0082] S102. In response to the user's configuration operation on the target expansion cabinet in the expansion cabinet list, determine the configuration parameters and perform compatibility verification.

[0083] Among them, the configuration operation includes but is not limited to at least one of customizing the expansion cabinet model, quantity, and topological connection structure. The user selects the required expansion cabinet model and quantity in the compatible expansion cabinet list provided by the system and determines the connection topology to implement the configuration of the target expansion cabinet. For example, select "2 storage expansion cabinets connected in daisy chain and 1 GPU expansion cabinet directly connected". Optionally, according to the user's selection, the resource requirements, including total power consumption, bandwidth occupancy, etc., are displayed in real time to facilitate the user to understand the configuration situation.

[0084] The following is the pseudo code:

[0085]

[0086] The pseudo code here indicates that the user has configured 4 EX3500s for the server host with the model HX5000, and the topological connection result between the devices is the daisy chain structure "daisy_chain". It means that one HX5000 server host cascades 4 EX3500 storage devices through the PCIe5.0 interface.

[0087] In some embodiments, it further includes generating a topology map, which is to visualize the topology connection structure. Specifically, the D3 visualization library (Data-Driven Documents, D3.js) or the ECharts library is integrated to draw the topology connection structure of the target expansion cabinet.

[0088] When performing compatibility verification on the configured target expansion cabinet, such as Figure 2 shown, the compatibility verification includes but is not limited to interface verification, resource verification, and topology connection verification.

[0089] Among them, the interface verification is used to verify whether the physical interface protocol between the server host and the expansion cabinet is compatible, including at least one of protocol version verification, physical specification verification, bandwidth and channel verification, and firmware dependency verification. When the user selects an expansion cabinet in the system, the interface verification module is called in real time at the front end. According to the verification result, the compatibility status of the expansion cabinet and the server host is highlighted in an intuitive way (such as a green tick indicating compatibility and a red warning icon indicating incompatibility), so that the user can timely understand whether the selected configuration is feasible.

[0090] During the interface verification process, first determine the interface parameters of the target server host and the target expansion cabinet, and then perform protocol version verification. The interface parameters include the interface type, etc., and the interface type includes but is not limited to Peripheral Component Interconnect Express (PCIe), SAS, Non-Volatile Memory Express (NVMe), and Universal Serial Bus (USB).

[0091] The protocol version verification is used to check whether the server host interface supports the protocol type and version of the expansion cabinet. To avoid communication failures or unstable communication between devices due to protocol incompatibility, ensure that different devices can be mutually adapted at the communication protocol level, and guarantee the basic connectivity of the system. For example, determine whether a PCIe 5.0 server host is compatible with a PCIe 4.0 expansion cabinet. If it is supported, the protocol version verification passes; if it is not supported, error code INTERFACE_VERSION_MISMATCH is triggered to prompt the interface version mismatch problem.

[0092] Physical specification verification is used to verify whether the size of the server host slot matches that of the expansion cabinet. This prevents the expansion cabinet from being incorrectly connected to the head due to physical form mismatch, ensuring the feasibility of physical connection of the device and avoiding system failures caused by hardware connection problems. For example, an x16 slot can accommodate an x8 device. If this is not met, an error code PHYSICAL_SLOT_INCOMPATIBLE is triggered, indicating that the physical slots are incompatible. Exemplarily, assume that a user attempts to install an expansion cabinet EX3500 with a depth of 440mm into a server host HX5000 that only supports a 400mm deep rack. The verification result indicates that the rack depth is incompatible.

[0093] Bandwidth and channel verification is used to verify whether the total bandwidth requirement of the expansion cabinet exceeds the available bandwidth of the server host interface. This prevents data transmission bottlenecks or data loss caused by the bandwidth requirement of the expansion cabinet exceeding the capacity of the head interface, ensuring the stability and reliability of the system in data transmission. For example, if the expansion cabinet requires 4 PCIe4.0 x4 devices, the total bandwidth requirement is 4 × 4 × 2 GB / s = 32 GB / s, and the bandwidth of the server host PCIe5.0 x16 interface is 64 GB / s. In this case, the verification passes; if it is exceeded, the verification fails.

[0094] Firmware dependency verification is used to compare whether the current firmware version of the server host matches the firmware version of the expansion cabinet. This avoids the inability to support the functions of the expansion cabinet due to too low a firmware version, ensuring compatibility between devices at the functional level and preventing the expansion cabinet from malfunctioning or lacking functions due to firmware problems. For example, if the expansion cabinet requires PCIe4.0 functionality and depends on the server host firmware v2.1+, and the server host firmware version is too low, an error code FIRMWARE_UPGRADE_REQUIRED is triggered, indicating that the server host firmware needs to be upgraded.

[0095] In some embodiments, in response to a user's configuration operation on a target expansion cabinet, the determined configuration parameters include at least one of the protocol version type and version of the target expansion cabinet, the interface size of the target expansion unit, the bandwidth requirement of the target expansion cabinet, and the firmware version of the target expansion cabinet. Interface verification is performed based on these configuration parameters.

[0096] During the process of performing interface verification based on the configuration parameters, it may include at least one of the following: checking whether the interface of the target server host supports the protocol type and version of the target expansion cabinet; verifying whether the slot size of the target server host matches the interface size of the target expansion cabinet; verifying whether the bandwidth requirement of the target expansion cabinet exceeds the available bandwidth of the target server host; verifying whether the current firmware version of the target server host matches the firmware version of the target expansion cabinet. It can be understood that at least one of protocol version verification, physical specification verification, bandwidth and channel verification, and firmware dependency verification is performed based on the configuration parameters.

[0097] In some embodiments, after interface verification is performed according to configuration parameters, an interface verification report is generated. The interface verification report includes passed items and failed items, as follows:

[0098]

[0099] In the above interface verification, device compatibility is ensured by at least one of protocol version verification, physical specification verification, bandwidth and channel verification, and firmware dependency verification. Through comprehensive interface verification, potential compatibility issues are excluded before device connection and use, reducing the probability of system failures due to interface incompatibility, improving the overall stability and reliability of the system, and reducing system maintenance costs and downtime caused by failures.

[0100] Resource verification is used to quantitatively analyze the global resource requirements of the server host and the expansion cabinet configuration, including total computing power consumption, total heat dissipation, and total bandwidth requirements.

[0101] In some embodiments, in response to a user's configuration operation on a target expansion cabinet, the determined configuration parameters include the power consumption of the target expansion cabinet and / or the bandwidth requirement of the target expansion cabinet. Then, resource verification is performed according to the power consumption of the target expansion cabinet and / or the bandwidth requirement of the target expansion cabinet.

[0102] Performing resource verification based on the above embodiments includes: calculating the total power consumption according to the power consumption of the target server host, the power consumption of the target expansion cabinet, and the load rate; and / or, calculating the total bandwidth requirement according to the bandwidth requirement of the target expansion cabinet, the bandwidth of the target server host, and the topology connection coefficient.

[0103] During the process of resource verification, in response to a user's configuration operation on a target expansion cabinet, determine the maximum power supply capacity (max_power_supply) and base power consumption (base_power) of the target server host, as well as the power consumption per unit of the target expansion cabinet (power_consumption), and the load rate.

[0104] Calculate the total power consumption according to the power consumption of the server host, the power consumption of the target expansion cabinet, and the load rate. Optionally, calculate the total power consumption according to the following formula: P total =P head +∑i=1n(P expansioni ×Q i )×L. In the formula, P head represents the base power consumption of the target server host; P expansioni represents the power consumption per unit of the i-th type of target expansion cabinet; Q i is the number of the i-th type of target expansion cabinet; L represents the load rate.

[0105] For example, if the basic power consumption of the server host HX5000 is 500W, the power consumption of a single expansion cabinet EX3500 is 180W, the user selects 4 units, and the load factor is set to 1.0, then the total power consumption is 500+(180×4)=1220W.

[0106] Calculate the total bandwidth requirement based on the server host bandwidth, the bandwidth requirement of the expansion cabinet, and the topology connection method. For example, if the interface bandwidth of the server host is 200Gbps, the bandwidth requirement of a single expansion cabinet EX3500 is 40Gbps, the user selects 4 units, and the topology coefficient is 1.0 (star connection), then the total bandwidth requirement is 40×4 = 160Gbps. Verify whether the total bandwidth requirement is less than or equal to the maximum bandwidth of the server host, 160Gbps ≤ 200Gbps.

[0107] The above embodiments calculate the bandwidth occupancy based on the interface parameters and topology influence, which can ensure that the interface bandwidth meets the total requirements of the expansion cabinet, avoid affecting the system performance due to bandwidth bottlenecks, enable efficient and stable data transmission, and give full play to the performance potential of the hardware.

[0108] In some embodiments, after calculating the total power consumption based on the server host power consumption, the target expansion cabinet power consumption, and the load rate, calculate the total heat dissipation according to the total power consumption and the heat dissipation efficiency coefficient. The power capacity P can be recommended according to the power redundancy rule PSU , and the calculation is as follows: P PSU =P total ×1.2. Exemplarily, P PSU =1,220×1.2 = 1,464W, and a 1,500W power module can be recommended for selection.

[0109] The above embodiments can ensure the stable power supply of the head and the expansion cabinet by accurately calculating the total power consumption and recommending the appropriate power capacity according to the power redundancy rule, avoid hardware failures or system instability caused by insufficient power, and the reserved redundancy also provides a guarantee for system upgrades or sudden high-load situations.

[0110] Optionally, combine the thermal design power (TDP) of the server host and the expansion cabinet, the room temperature input by the user, the rack heat dissipation capacity and other parameters to calculate the total heat dissipation. The total heat dissipation is calculated according to the following formula: Q cooling =P total ×η. In the formula, η is the heat dissipation coefficient, such as 0.85 - 0.95.

[0111] It is possible to compare whether the total heat dissipation is less than or equal to the maximum heat dissipation capacity of a single rack Q rack_max . If the total heat dissipation does not exceed the maximum heat dissipation capacity of a single rack, the verification passes. Exemplarily, assuming η = 0.9 in the air-cooled solution, Q rack_max =1500W. The total heat dissipation Qcooling = 1,220 × 0.9 = 1,098 W, less than or equal to the maximum heat dissipation capacity of a single rack, indicating that the heat dissipation through the rack passes the verification. Otherwise, Q cooling > Q rack_max , and subsequent solutions such as adding fans, liquid cooling modules, etc. will be matched to ensure the feasibility of the configuration in terms of heat dissipation.

[0112] By considering the hardware parameters and environmental parameters to calculate the heat dissipation requirements, the above embodiments can make the heat dissipation system adapt to the hardware configuration, prevent equipment overheating and downtime caused by poor heat dissipation, extend the service life of the hardware, and ensure the stable operation of the system in a suitable temperature environment.

[0113] The above resource verification quantitatively analyzes the configuration of the server head and the expansion cabinet from aspects such as total power consumption, heat dissipation requirements, and bandwidth occupancy to ensure the feasibility of the hardware configuration. The comprehensive evaluation and planning of key resources such as power supply, heat dissipation, and bandwidth help eliminate potential single-point failure hazards, improve the reliability and stability of the entire system, and reduce system failures and downtime caused by insufficient or mismatched hardware resources.

[0114] The topology connection verification is used to verify whether the physical connection method between the server host and the expansion cabinet conforms to the technical specifications. Optionally, it includes parsing the topology configuration, hierarchical verification, calculating the signal attenuation value, and bandwidth allocation verification.

[0115] In some embodiments, in response to a configuration operation for a target expansion cabinet, the topology connection structure between the target server host and the target expansion cabinet is determined, and then the topology connection structure is subjected to topology connection verification according to the verification rules corresponding to the topology connection structure. Different topology connection structures correspond to different verification rules.

[0116] Determining the topology connection structure between the target server host and the target expansion cabinet in response to a configuration operation for the target expansion cabinet is to convert the user-input connection relationship into a graph structure of nodes and edges for subsequent hierarchical verification and analysis, so that the topology connection structure is presented in a form that can be processed by a computer.

[0117] The topology connection structure includes but is not limited to: Daisy Chain, Star topology, Hybrid topology. The Hybrid topology combines the characteristics of the Daisy Chain and the Star topology. For example, first connect the head to the switch through a star structure, and then connect multiple Daisy Chain expansion cabinets through the switch.

[0118] The verification rules for daisy chains include, but are not limited to: verifying whether the maximum number of cascades is exceeded, whether a signal terminator is enabled at the end of the chain structure, and verifying whether the total data transmission requirements of all devices exceed the link capacity. For example, if a maximum of 4 levels is specified, then connecting more than 4 expansion enclosures in series may affect the stability and performance of the entire system. Taking the SAS expansion enclosure as an example, enabling the terminator can effectively avoid signal reflection and ensure the integrity and stability of signal transmission.

[0119] Exemplarily, assume that the user configures to start from the target server host HX5000 and connect three expansion enclosures, namely EX3500-1, EX3500-2, and EX3500-3 in sequence, forming a 3-level cascaded chain structure, where the bandwidth requirement of each expansion enclosure is 40 Gbps. First, perform the maximum cascade number verification. If the specified maximum allowable cascade number is 4 levels and the currently configured cascade number is 3 levels, and 3 is less than or equal to 4, so the maximum cascade number verification passes. Then calculate the total bandwidth requirement of 120 Gbps and compare it with the bandwidth of 256 Gbps of PCIe5.0x16, indicating that the total bandwidth requirement of all devices under the current configuration does not exceed the bandwidth capacity that the link can provide. Further, assume that the signal attenuation per meter of the link is 0.5 dB, the link length for each cascaded expansion enclosure in the current configuration is 1 m, and there are 3 levels of cascades in total, so the total signal attenuation is 3×1 m×0.5 dB / m = 1.5 dB. And the maximum signal attenuation that the system can withstand is 12 dB, and 1.5 dB is less than or equal to 12 dB, indicating that the signal attenuation is within the acceptable range. After verifying the three aspects of the cascade number, total bandwidth requirement, and signal attenuation, all meet the corresponding rules and requirements, and it can be determined that this topology structure is legal.

[0120] The verification rules for star topology include, but are not limited to: verifying whether the number of interfaces provided by the target server host is sufficient, and verifying whether the total bandwidth of the target server host meets the total bandwidth requirements of the target expansion enclosures. If there are 8 expansion enclosures, then the head end needs to have 8 independent interfaces to connect them. If the number of interfaces is insufficient, the connection of all expansion enclosures cannot be achieved, and the system cannot work properly. If the total bandwidth of the head end is limited and the total bandwidth requirements of the expansion enclosures exceed the bearing capacity of the head end, then there will be a data transmission bottleneck, affecting the system performance.

[0121] The verification rules for the hybrid topology include, but are not limited to: hierarchical verification and global resource coordination. For example, checking whether the number of cascaded switches is within the allowable range and whether the bandwidth allocation for each branch is reasonable. Global resource coordination considers the resource conditions such as power consumption, heat dissipation, and bandwidth of the system as a whole to ensure that they are all within the carrying capacity of the system. If the power consumption of the devices in a certain area is too high, it may cause heat dissipation problems, which in turn affect the normal operation of the devices; if the bandwidth allocation is unreasonable, it may cause congestion on some links while the utilization rate of other links is low.

[0122] In some embodiments, assuming that the topology connection structure is a hybrid topology, in the process of performing topology connection verification on the topology connection structure according to the corresponding verification rules of the topology connection structure, first hierarchically verify whether the topology connection structure conforms to the technical specifications; calculate the signal attenuation value according to the cable length and attenuation coefficient of the topology connection structure, and verify whether the signal attenuation value exceeds the corresponding preset attenuation threshold; verify whether the bandwidth requirement of the topology connection structure meets the corresponding bandwidth allocation conditions.

[0123] In the process of hierarchically verifying whether the topology connection structure conforms to the technical specifications, first verify whether the direct connection between the server host and the first-level expansion cabinet is legal, and check whether the interface type, quantity, etc. meet the requirements; then gradually verify the number of cascaded downstream devices and the bandwidth allocation to ensure that the connection at each level in the entire topology connection structure conforms to the technical specifications.

[0124] Further calculate the signal attenuation value according to the formula "attenuation (dB)=∑i=1nLi×k", where Li is the length of the i-th section of the cable and k is the attenuation coefficient per unit length (such as 0.5 dB / m for SAS cables). If the total attenuation exceeds the threshold (such as 12 dB), it is determined that the topology connection structure is illegal because excessive signal attenuation may cause communication failures.

[0125] In the process of verifying whether the bandwidth requirement of the topology connection structure meets the corresponding bandwidth allocation conditions, for the daisy-chain structure, it is necessary to ensure that the total bandwidth requirement does not exceed the single-link bandwidth × multiplexing factor. For example, a PCIe5.0x8 link provides 32 GB / s, and for 4-level multiplexing, the total requirement ≤ 32 GB / s; for the star structure, the exclusive bandwidth of each expansion cabinet should not exceed the corresponding interface capacity to ensure reasonable allocation of bandwidth resources and avoid resource contention and performance bottlenecks.

[0126] Exemplarily, assume that the user configures to connect the target server host HX5000 to a switch, and the EX3500-1 connected through the switch forms a three-level daisy chain structure (i.e., there are three devices connected in series in sequence), while the EX3500-2 is directly connected to the switch. This configuration method combines the characteristics of the daisy chain and star topologies to form a hybrid topology. During the verification process, the maximum number of cascaded levels allowed by the target server host HX5000 is three levels, while the total number of cascaded levels of this hybrid topology is four levels, exceeding the support capacity of the target server host.

[0127] The above topology connection verification can verify whether the connections between the head unit and each level of expansion cabinets meet the requirements of interface types and quantities by parsing the topology configuration and performing hierarchical verification, avoiding device failure to communicate normally or system failures caused by incorrect connections, and ensuring the correctness and stability of the hardware connections. By calculating the signal attenuation of long links, possible signal quality problems can be detected in a timely manner. Verifying the bandwidth allocation for different topologies (daisy chain and star) ensures that the bandwidth requirements of the expansion cabinets are within the allowable range of the link bandwidth, avoiding performance bottlenecks or bandwidth waste caused by insufficient bandwidth, realizing the rational utilization of bandwidth resources, and improving the overall performance and efficiency of the system.

[0128] S103. In the case of failed compatibility verification, determine the error message and match the solution strategy corresponding to the error message from the predefined rule library.

[0129] In each verification step, once an incompatibility is found, the corresponding error message will be triggered. These error messages can clearly indicate the problem, facilitating technicians to quickly locate and solve the problem, enhancing the system's error handling ability and maintainability.

[0130] Among them, the error message includes an error code and an error description. The following is the pseudo-code:

[0131]

[0132] The pseudocode here indicates that the current verification fails as "false". The error code "POWER_OVERLOAD" means power overload. The error description is that the total power consumption of the current system is 1,220 watts, but the maximum power supply capacity of the server host is only 1,000 watts, exceeding by 220 watts. The solution strategies include: adding an additional power supply unit; using a power supply with the model "PSU1500W" whose rated power is 1,500 watts, which is sufficient to meet the current system requirements. In addition to adding a PSU, other possible solution strategies include reducing EX3500 from 4 to 3 (assuming each is 180W, and the total power consumption drops to 1040W); upgrading the server host PSU to a 1250W model; turning off unnecessary devices or using low-power models.

[0133] The predefined rule library includes error codes and their descriptions, as well as corresponding solution strategies. An example is shown in Table 4 as follows:

[0134] Table 4

[0135]

[0136] If problems are found during the interface verification process, assume the user selects the target server host HX4000 (SAS-3, 12Gbps) and configures the target expansion cabinet EX4500 (requiring SAS-4, 24Gbps). During the interface verification process, if it is determined that SAS-3 cannot support SAS-4 devices, the physical specification verification fails, and the error code is "INTERFACE_VERSION_MISMATCH"; then match the corresponding solution strategy: it is recommended to replace it with the server host HX5000 that supports SAS-4, or select the expansion cabinet EX3500 that is compatible with SAS-3.

[0137] Exemplarily, assume the target expansion cabinet EX-2800 that is not compatible with the interface of the server host HX-5000 is selected. The server host HX-5000 only supports PCIe5.0, and the target expansion cabinet EX-2800 only supports PCIe4.0. The determined corresponding solution strategy is to replace it with the expansion cabinet EX-3500, or replace it with the server host HX-4000.

[0138] If problems are found during the resource verification process, exemplarily, assume the user selects the target server host HX7000 (PCIe5.0x16, total bandwidth 400Gbps) and configures 8 target expansion cabinets (single unit power consumption 300W, bandwidth 50Gbps). The calculated total power consumption is 2900w, and the total bandwidth is 400Gbps. To avoid errors, the solution strategies include: recommending a 3480W power supply; suggesting reserving a higher bandwidth margin to cope with peak loads.

[0139] Exemplarily, assume that the user selects the target server host HX6000 (SAS-4, total bandwidth 24 Gbps), configures 12 target expansion cabinets (single cabinet bandwidth 2.5 Gbps), and calculates that the total bandwidth requirement is 30 Gbps, which is greater than the total bandwidth of the target server host, triggering the error code "INSUFFICIENT_BANDWIDTH". The corresponding solution strategies include: recommending reducing to 9 expansion cabinets or upgrading to a server host that supports SAS-5.

[0140] If problems are found during the topology connection verification process, for example, the total number of cascades in the hybrid topology structure is 4 levels, exceeding the maximum allowed cascading number of 3 for the target server host, the solution strategies corresponding to the error information matched from the predefined rule library include: reducing the number of daisy-chain devices formed by EX3500-1 to 2, or selecting a switch that can support 4 levels or more of cascading.

[0141] In some embodiments, if problems are found during the resource verification or topology connection verification process, such as insufficient power supply, interface incompatibility, etc., the system will trigger a conflict detection mechanism. The conflict resolution engine will analyze the root cause of the conflict based on preset rules and real-time data, and provide corresponding solution strategies, such as replacing the high-power power supply, reducing the number of expansion cabinets, replacing the compatible expansion cabinet or server host model, etc. At the same time, the solution strategies will be prioritized, and the solutions with low cost, high timeliness, and good compatibility will be recommended first. The user can make a choice according to the recommendation or make manual adjustments.

[0142] As shown in Table 5, the predefined rule library includes error codes and corresponding multiple solution strategies. When the system detects a hardware configuration conflict, the corresponding solution strategy can be directly called, avoiding the need for technicians to conduct ad hoc troubleshooting and trial-and-error, greatly shortening the problem location and resolution time, and improving the configuration efficiency.

[0143] Table 5

[0144]

[0145] Optionally, set evaluation dimensions and weight formulas to calculate the scores of each solution strategy, so as to determine its priority. The evaluation dimensions involve the total cost (cost) of the solution strategy, the delivery cycle (DeliveryTime) of the replacement hardware, and the long-term stability (Compatibility) of the solution strategy, etc. The total cost of the solution strategy includes the hardware cost and the expected operation and maintenance cost. The hardware cost refers to the cost required to purchase relevant equipment, while the expected operation and maintenance cost covers the costs of equipment maintenance, upgrade, fault repair, etc. during the use process.

[0146] The calculation formula for the priority is as follows: Score = w 1× Cost+ w 2 × Delivery Time + w 3 × Compatibility In the formula, Cost, DeliveryTime, and Compatibility are the evaluation values of the solution in the three dimensions of economy, timeliness, and compatibility respectively. w1, w2, and w3 are the corresponding weight coefficients, which can be dynamically adjusted according to the user's needs. By adjusting the weight coefficients, the priorities of each solution can be evaluated more flexibly according to the preferences and actual needs of different users, so as to select the most suitable solution for the specific situation.

[0147] Exemplarily, the error code "POWER_OVERLOAD" indicates that the current device configuration causes the power load to be too high. The matching solution strategies include: (1) using a power supply module of PSU-1500W; (2) removing one EX3500 expansion cabinet; (3) replacing the existing expansion cabinet with an EX3200. The cost of solution strategy (1) is $300 and the delivery time is 3 days; solution strategy (2) saves $800 in cost but causes a loss of storage capacity; solution strategy (3) requires additional procurement, with a cost of $1200 and a delivery time of 7 days. Based on the priority calculation formula, the priority scores of each solution strategy are calculated respectively, and it is determined that the score of solution strategy (1) is the highest. While solving the power overload problem, the comprehensive factors such as cost and delivery time are relatively better, and it can solve the power overload problem at a relatively low cost in a short time, so it is given priority consideration.

[0148] Also exemplarily, the error code "INTERFACE_MISMATCH" indicates that there is a problem of interface protocol incompatibility in the current device configuration. The matching solution strategies include: (1) selecting an EX3500 expansion cabinet compatible with PCIe5.0; (2) replacing the head with an HX4000 (supporting PCIe4.0); (3) purchasing a PCIe5.0 to 4.0 converter. Among them, the cost of each EX3500 expansion cabinet for solution strategy (1) is $500 and the delivery time is 2 days; solution strategy (2) can save $200 in cost but will limit future upgrade capabilities; solution strategy (3) has a cost of $150 and a delivery time of 5 days. Based on the priority calculation formula, the priority scores of each solution strategy are calculated respectively and the priority ranking is carried out. Strategy (1) has the best score because it performs well in terms of compatibility (directly replacing with an expansion cabinet compatible with PCIe5.0) and has a fast delivery speed. Strategy (3) is the second. Although the cost is lower, due to the problem of introducing delay risks, its priority is lower than that of strategy 1.

[0149] The above embodiments are based on a priority sorting algorithm in three dimensions of economy, timeliness, and compatibility. By dynamically adjusting the weight coefficients, the needs of different user groups are met. Enterprise users can focus on low-cost solutions, and data centers can give priority to high-compatibility solutions to ensure that the output solutions are optimal in different scenarios, reducing after-sales costs and system risks caused by configuration errors.

[0150] S104. When the compatibility check is successful, generate a hardware configuration list corresponding to the target server host.

[0151] The hardware configuration list corresponding to the target server host includes the target server host, the target expansion cabinet, and the topology connection structure, resource requirements, technical documents, etc. Resource requirements include recommended power supplies, cooling solutions, etc. Technical documents include topology diagrams, firmware version information, etc.

[0152] After the compatibility check passes, generate a hardware configuration list including the server host, expansion cabinet, configuration documents, and topology diagram. The list details information such as the models, quantities, power supplies, and cooling solutions of the server host and expansion cabinet, and synchronizes it to the production system. The production system interface will convert the list data into a standardized format and transmit it to the production system through a RESTful Application Programming Interface (RESTful API) or a message queue, etc., triggering pre-configuration tasks such as firmware flashing, hardware assembly, and functional testing on the production line, realizing seamless connection from order to production.

[0153] Exemplarily, assume that the user selects the target server host HX5000 (PCIe5.0x16, firmware v2.2) and the target expansion cabinet (PCIe4.0x8). During the interface check, if it is determined that PCIe5.0 is compatible with PCIe4.0, the protocol version check passes; if it is determined that x16 supports x8 devices, the physical specification check passes; if it is determined that v2.2 ≥ v2.1, the firmware dependency check passes. Then generate a hardware configuration list.

[0154] Exemplarily, assume that the user's configuration starts from the target server host HX5000 and successively connects three expansion cabinets, EX3500-1, EX3500-2, and EX3500-3, and the topology connection check corresponding to the daisy chain passes, meeting the rules and requirements in three aspects: the number of cascades, total bandwidth requirements, and signal attenuation. Then generate a hardware configuration list corresponding to the target server host HX5000, and the equipment can be purchased and deployed according to this configuration.

[0155] In some embodiments, after generating the hardware configuration list, the hardware configuration list is transmitted to the production system to trigger subsequent hardware pre-configuration tasks, thus achieving seamless connection from the list to generation. The hardware pre-configuration tasks include firmware pre-flashing, hardware assembly guidance, automated testing, etc. Moreover, the task execution status fed back by the production system is received and the hardware configuration list is updated accordingly.

[0156] Among them, for firmware pre-flashing, according to the firmware version in the list, the firmware package is downloaded from the image repository and flashed to the head unit and expansion cabinets through the IPMI / iDRAC interface. The instruction is like ipmitool -H <BMC_IP> -U admin -P password firmware update bios / firmware / hx5000_v2.1.bin. The hardware assembly guidance is to push the topology diagram to the production line display screen to guide the workers to install the expansion cabinets and connect the cables in the specified order. The automated testing is to execute the diagnostic script after power-on to verify the interface connectivity, bandwidth rate and heat dissipation performance. The test cases are as follows:

[0157]

[0158] The above test cases are used to verify whether the bandwidth of the PCIe devices in the system meets the PCIe 5.0 standard. If the test fails, it will be automatically retried or the engineer will be notified to intervene and troubleshoot.

[0159] In the process of transmitting the hardware configuration list to the production system, first convert the hardware configuration list into a preset format, such as XML format (XML Schema Definition, Schema). Then publish the hardware configuration list to the message queue, and the production system obtains it asynchronously. A message list such as Kafka is a distributed message queue system that can reliably transmit a large amount of data.

[0160] Exemplarily, assume that the user configures 50 HX5000 heads, and each HX5000 head is connected to 4 EX3500 expansion cabinets, adopting a star topology structure to generate 50 hardware configuration lists. These hardware configuration lists are sent to the Kafka message queue, and then the Kafka message queue pushes this data to the production system. After receiving the list data from the Kafka message queue, the production system parses this data and extracts the information related to production. Then, the production system creates 50 parallel work orders, that is, processes 50 production tasks simultaneously, and distributes these work orders to different production lines for production. In the production line, operations such as firmware flashing of devices (installing and configuring the firmware of devices), hardware assembly (installing each hardware component into the device), and testing (performing various function and performance tests on the device) are carried out through an automated assembly line. And during the entire production process, the status of the devices is transmitted back to the order system in real time, enabling the order system to timely understand the production progress and device status, facilitating monitoring and management by users and relevant personnel.

[0161] In summary, for a server hardware configuration method provided in an embodiment of the present application, through a graphical interface and a pre-established compatibility database, users can quickly obtain a list of expansion cabinets compatible with the target server host without manual searching and filtering, reducing the configuration time and workload and improving the efficiency of hardware configuration. Compatibility verification, including interface verification, resource verification, and topology connection verification, etc., can ensure that the selected hardware matches each other in terms of interface type, quantity, resource requirements, and connection method, etc., avoiding system failures or performance problems caused by hardware incompatibility and ensuring the accuracy and stability of hardware configuration. When the compatibility verification fails, it is possible to match the solution strategy corresponding to the error message from a predefined rule library to help users quickly locate and solve problems, reducing the risk of system failures caused by hardware configuration errors and enhancing the reliability of the entire server system. The use of a graphical interface makes the hardware configuration process more intuitive and convenient, and even non-professional users can easily get started. At the same time, the system automatically performs verification and provides solution strategies, reducing the technical burden on users and enhancing the user experience during the hardware configuration process. This method clarifies a series of processes from when the user selects a server host to generating a hardware configuration list, including loading the compatibility database, determining configuration parameters, verification, and error handling, etc., standardizing and normalizing the hardware configuration process, which is beneficial to improving the consistency and manageability of configuration.

[0162] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a 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.

[0163] An embodiment of the present application further provides a server hardware configuration device, as Figure 3 shown, the device includes:

[0164] A loading module 301, configured to, in response to a user's selection input of a target server host in a graphical interface, load a list of expansion enclosures compatible with the target server host based on a pre-established compatibility database; the compatibility database is generated according to the compatibility rules of the hardware manufacturer's product line;

[0165] A configuration and verification module 302, configured to, in response to a user's configuration operation on a target expansion enclosure in the expansion enclosure list, determine configuration parameters and perform compatibility verification, and the compatibility verification includes at least one of interface verification, resource verification, and topology connection verification;

[0166] A verification result processing module 303, configured to, in the case of a failed compatibility verification, determine an error message, and match a solution strategy corresponding to the error message from a predefined rule library; in the case of a successful compatibility verification, generate a hardware configuration list corresponding to the target server host.

[0167] As an optional implementation manner provided by an embodiment of the present application, the server hardware configuration further includes an interaction module, configured to: in response to a server host model input by a user, determine a list of server hosts corresponding to the server host model; and display the list of server hosts in a graphical interface.

[0168] As an optional implementation manner provided by an embodiment of the present application, the compatibility database includes a list of compatible devices; the server hardware configuration further includes a compatibility database establishment module, configured to: obtain static parameters of the server host and the expansion enclosure, and establish a static parameter table; obtain dynamic parameters of the server host and the expansion enclosure, and establish a dynamic parameter table, where the dynamic parameter table includes a firmware compatibility table and a manufacturer update log table; establish an association relationship between the static parameter table and the firmware compatibility table to generate a list of compatible devices; and update the list of compatible devices when a target field in the manufacturer update log table is updated.

[0169] As an optional implementation manner provided by an embodiment of the present application, the server hardware configuration further includes a compatibility database update module, configured to: obtain manufacturer technical documents and firmware information; preprocess the manufacturer technical documents and firmware information, including deduplication and format standardization; and detect the preprocessed manufacturer technical documents and firmware information to determine whether a target field in the manufacturer update log table is updated.

[0170] As an alternative implementation provided by the embodiments of the present application, the configuration and verification module 302 is specifically configured to: in response to a user's configuration operation on a target expansion cabinet, determine that the configuration parameters include at least one of the following: the protocol type and version of the target expansion cabinet, the interface size of the target expansion cabinet, the bandwidth requirement of the target expansion cabinet, and the firmware version of the target expansion cabinet; perform interface verification according to the configuration parameters.

[0171] As an alternative implementation provided by the embodiments of the present application, the configuration and verification module 302 is specifically configured to perform interface verification according to the configuration parameters, including at least one of the following: checking whether the interface of the target server host supports the protocol type and version of the target expansion cabinet; verifying whether the slot size of the target server host matches the interface size of the target expansion cabinet; verifying whether the bandwidth requirement of the target expansion cabinet exceeds the available bandwidth of the target server host; verifying whether the current firmware version of the target server host matches the firmware version of the target expansion cabinet.

[0172] As an alternative implementation provided by the embodiments of the present application, the configuration and verification module 302 is specifically configured to: in response to a user's configuration operation on a target expansion cabinet, determine that the configuration parameters include the power consumption of the target expansion cabinet and / or the bandwidth requirement of the target expansion cabinet; perform resource verification according to the configuration parameters.

[0173] As an alternative implementation provided by the embodiments of the present application, the configuration and verification module 302 is specifically configured to perform resource verification according to the configuration parameters, including: calculating the total power consumption based on the power consumption of the target server host, the power consumption of the target expansion cabinet, and the load rate; and / or calculating the total bandwidth requirement based on the bandwidth requirement of the target expansion cabinet, the bandwidth of the target server host, and the topology connection coefficient.

[0174] As an alternative implementation provided by the embodiments of the present application, after the configuration and verification module 302 calculates the total power consumption based on the power consumption of the target server host, the power consumption of the target expansion cabinet, and the load rate, it is further configured to: calculate the total heat dissipation based on the total power consumption and the heat dissipation efficiency coefficient.

[0175] As an alternative implementation provided by the embodiments of the present application, the configuration and verification module 302 is specifically configured to: in response to a user's configuration operation on a target expansion cabinet, determine the topology connection structure between the target server host and the target expansion cabinet; perform topology connection verification on the topology connection structure according to the verification rules corresponding to the topology connection structure.

[0176] As an alternative implementation provided by the embodiments of the present application, the configuration and verification module 302 performs topology connection verification on the topology connection structure according to the verification rules corresponding to the topology connection structure, specifically for: verifying layer by layer whether the topology connection structure complies with the technical specifications; calculating the signal attenuation value according to the cable length and attenuation coefficient of the topology connection structure, and verifying whether the signal attenuation value exceeds the corresponding preset attenuation threshold; verifying whether the bandwidth requirement of the topology connection structure meets the corresponding bandwidth allocation condition.

[0177] For the description of the features in the corresponding embodiments of the server hardware configuration device, reference can be made to the relevant descriptions in the corresponding embodiments of the server hardware configuration method, which will not be elaborated here one by one.

[0178] The embodiments of the present application also provide an electronic device, as Figure 4 shown, including a memory 401 and a processor 402. The memory 401 stores a computer program, and the processor 402 is configured to run the computer program to execute the steps in any of the above embodiments of the server hardware configuration method.

[0179] The embodiments of the present application also provide a computer-readable storage medium, in which a computer program is stored. Wherein, the computer program is configured to execute the steps in any of the above embodiments of the server hardware configuration method when running.

[0180] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: USB flash drive, read-only memory (ROM for short), random access memory (RAM for short), mobile hard disk, magnetic disk or optical disc and other various media that can store computer programs.

[0181] The embodiments of the present application also provide a computer program product. The above computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above embodiments of the server hardware configuration method.

[0182] The embodiments of the present application also provide another computer program product, including a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above embodiments of the server hardware configuration method.

[0183] Those skilled in the art may further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods for each specific application to implement the described functions, but such implementation should not be considered as exceeding the scope of this application.

[0184] The above has introduced in detail a server hardware configuration method, device, equipment, storage medium, and product provided by this application. Specific examples are used herein to elaborate on the principles and implementation manners of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principle of this application, several improvements and modifications can be made to this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A server hardware configuration method, characterized in that, Including: In response to a user's selection input of a target server host in a graphical interface, loading a list of expansion enclosures compatible with the target server host based on a pre-established compatibility database; the compatibility database is generated according to the compatibility rules of the hardware manufacturer's product line; In response to a user's configuration operation on a target expansion enclosure in the list of expansion enclosures, determining configuration parameters and performing a compatibility check, the compatibility check includes at least one of an interface check, a resource check, and a topology connection check; the interface check is used to verify whether the physical interface protocols between the server host and the expansion enclosure are compatible, including at least one of a protocol version check, a physical specification check, a bandwidth and channel check, and a firmware dependency check; the resource check is used to quantitatively analyze the global resource requirements of the server host and the expansion enclosure configuration, including the total computing power consumption, the total heat dissipation, and the total bandwidth requirement; the topology connection check is used to verify whether the physical connection method between the server host and the expansion enclosure conforms to the technical specifications, including parsing the topology configuration, hierarchical check, calculating the signal attenuation value, and bandwidth allocation verification; In the case where the compatibility check fails, determining an error message and matching a solution strategy corresponding to the error message from a predefined rule library; In the case where the compatibility check is successful, generating a hardware configuration list corresponding to the target server host and synchronizing it to the production system to trigger a hardware pre-configuration task; The hardware configuration list includes the target server host, the target expansion enclosure, and the topology connection structure, resource requirements, and technical documents.

2. The method according to claim 1, wherein Before the step of, in response to a user's selection input of a target server host in a graphical interface, loading a list of expansion enclosures compatible with the target server host based on a pre-established compatibility database, the method further includes: In response to a server host model input by the user, determining a list of server hosts corresponding to the server host model; Displaying the list of server hosts in the graphical interface.

3. The method according to claim 1, wherein The compatibility database includes a list of compatible devices; the establishment process of the compatibility database includes: Obtaining the static parameters of the server host and the expansion enclosure and establishing a static parameter table; Obtaining the dynamic parameters of the server host and the expansion enclosure and establishing a dynamic parameter table, the dynamic parameter table includes a firmware compatibility table and a manufacturer update log table; Establishing an association relationship between the static parameter table and the firmware compatibility table to generate a list of compatible devices; Updating the list of compatible devices when the target field in the manufacturer update log table is updated.

4. The method according to claim 3, wherein After the step of establishing an association relationship between the static parameter table and the firmware compatibility table to generate a list of compatible devices and before the step of updating the list of compatible devices when the target field in the manufacturer update log table is updated, the method further includes: Obtaining manufacturer technical documents and firmware information; Preprocessing the manufacturer technical documents and the firmware information, including deduplication and format standardization; Detecting the preprocessed manufacturer technical documents and firmware information to determine whether the target field in the manufacturer update log table is updated.

5. The method according to claim 1, wherein In response to a user's configuration operation on a target expansion cabinet in the expansion cabinet list, determine configuration parameters and perform compatibility verification, including: In response to a user's configuration operation on the target expansion cabinet, determine that the configuration parameters include at least one of the following: the protocol type and version of the target expansion cabinet, the interface size of the target expansion cabinet, the bandwidth requirement of the target expansion cabinet, and the firmware version of the target expansion cabinet; Perform the interface verification according to the configuration parameters.

6. The method according to claim 5, wherein The performing the interface verification according to the configuration parameters includes at least one of the following: Check whether the interface of the target server host supports the protocol type and version of the target expansion cabinet; Verify whether the slot size of the target server host matches the interface size of the target expansion cabinet; Verify whether the bandwidth requirement of the target expansion cabinet exceeds the available bandwidth of the target server host; Verify whether the current firmware version of the target server host matches the firmware version of the target expansion cabinet.

7. The method according to claim 1, wherein In response to a user's configuration operation on a target expansion cabinet in the expansion cabinet list, determine configuration parameters and perform compatibility verification, including: In response to a user's configuration operation on the target expansion cabinet, determine that the configuration parameters include the power consumption of the target expansion cabinet and / or the bandwidth requirement of the target expansion cabinet; Perform the resource verification according to the configuration parameters.

8. The method according to claim 7, wherein The performing the resource verification according to the configuration parameters includes: Calculate the total power consumption according to the power consumption of the target server host, the power consumption of the target expansion cabinet, and the load rate; and / or, Calculate the total bandwidth requirement according to the bandwidth requirement of the target expansion cabinet, the bandwidth of the target server host, and the topology connection coefficient.

9. The method according to claim 8, characterized in that, After calculating the total power consumption according to the power consumption of the target server host, the power consumption of the target expansion cabinet, and the load rate, the method further includes: Calculate the total heat dissipation according to the total power consumption and the heat dissipation efficiency coefficient.

10. The method according to claim 1, wherein In response to a user's configuration operation on a target expansion cabinet in the expansion cabinet list, determine configuration parameters and perform compatibility verification, including: In response to a user's configuration operation on the target expansion cabinet, determine the topology connection structure between the target server host and the target expansion cabinet; Perform the topology connection verification on the topology connection structure according to the verification rules corresponding to the topology connection structure.

11. The method according to claim 10, wherein The performing the topology connection verification on the topology connection structure according to the verification rules corresponding to the topology connection structure includes: Hierarchically verify whether the topology connection structure conforms to the technical specifications; Calculate the signal attenuation value according to the cable length and attenuation coefficient of the topology connection structure, and verify whether the signal attenuation value exceeds the corresponding preset attenuation threshold; Verify whether the bandwidth requirement of the topology connection structure meets the corresponding bandwidth allocation conditions.

12. A server hardware configuration device, characterized in that, including: A loading module, configured to, in response to a user's selection input of a target server host in a graphical interface, load a list of expansion cabinets compatible with the target server host based on a pre-established compatibility database; the compatibility database is generated according to the compatibility rules of the hardware manufacturer's product line; A configuration and verification module, which is used to determine configuration parameters and perform compatibility verification in response to a user's configuration operation on a target expansion cabinet in the expansion cabinet list. The compatibility verification includes at least one of interface verification, resource verification, and topology connection verification; the interface verification is used to verify whether the physical interface protocols between the server host and the expansion cabinet are compatible, including at least one of protocol version verification, physical specification verification, bandwidth and channel verification, and firmware dependency verification; the resource verification is used to quantitatively analyze the global resource requirements of the server host and the expansion cabinet configuration, including total computing power consumption, total computing heat dissipation, and total bandwidth requirement; the topology connection verification is used to verify whether the physical connection method between the server host and the expansion cabinet conforms to technical specifications, including parsing topology configuration, hierarchical verification, calculating signal attenuation value, and bandwidth allocation verification. A verification result processing module, which is used to determine error information and match a solution strategy corresponding to the error information from a predefined rule library when the compatibility verification fails. When the compatibility verification is successful, generate a hardware configuration list corresponding to the target server host and synchronize it to the production system to trigger a hardware pre-configuration task; the hardware configuration list includes the target server host, the target expansion cabinet, and the topology connection structure, resource requirements, and technical documents.

13. An electronic device, characterized in that, Comprising: A memory, which is used to store computer programs. A processor, which is used to implement the steps of the server hardware configuration method according to any one of claims 1 to 11 when executing the computer program.

14. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program, when executed by a processor, implements the steps of the server hardware configuration method according to any one of claims 1 to 11.

15. A computer program product, comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the steps of the server hardware configuration method according to any one of claims 1 to 11.

Images