Server hardware configuration method and device, equipment, storage medium and product

Abstract

The invention discloses a server hardware configuration method and device, equipment, a storage medium and a product, and relates to the technical field of server hardware configuration and intelligent supply chain management.The server hardware configuration method comprises the steps that after a target server host is selected on a graphical interface, a database is established based on a hardware manufacturer compatibility rule, a compatible extension cabinet list is automatically loaded, and the target server host is configured; manual matching is avoided, the dependence on technical documents and artificial experience is reduced, the configuration efficiency is remarkably improved, and the error rate is reduced. Meanwhile, interface, resource and topological connection verification is carried out in the configuration process, global resource verification can be carried out on the multi-level extension architecture, and the defect of traditional single-level verification is overcome. If verification fails, error information is automatically determined, a predefined solution strategy is matched, and the configuration problem is quickly positioned and processed, so that hardware return, reworking and system downtime are effectively reduced, and the after-sales cost is reduced.

Description

Technical Field

[0001] This application relates to the technical fields of server hardware configuration and intelligent supply chain management, and particularly relates 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 compatibility between components such as the server host and 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 the server host 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, consuming a large amount of time, but also extremely prone to errors. At the same time, hardware manufacturers frequently update their product lines, but the recommended information lags severely, making it difficult to meet actual needs. In the face of 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 outages caused by configuration errors are common. According to statistics, approximately 15% of server orders require secondary processing 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 existing in the 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 failed compatibility verification, determining error information and matching a solution strategy corresponding to the error information from a predefined rule library; in the case of successful compatibility verification, generating a hardware configuration list corresponding to the target server host.

[0006] The present application also provides a server hardware configuration device, 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 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; 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; A verification result processing module, configured to, in the case of failed compatibility verification, determine error information and match a solution strategy corresponding to the error information from a predefined rule library; in the case of successful compatibility verification, generate a hardware configuration list corresponding to the target server host.

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

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

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

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

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

[0012] Figure 1 It is a flowchart of a server hardware configuration method provided by an embodiment of this application; Figure 2 It is a logical diagram of compatibility verification provided by an embodiment of this application; Figure 3 It is a structural diagram of a server hardware configuration device provided by an embodiment of this application; Figure 4 It is a structural diagram of an electronic device provided by an embodiment of this application. DETAILED DESCRIPTION OF THE EMBODIMENTS

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

[0014] It should be noted that in the description of this application, the terms "include", "comprise" or any other variants 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 also includes 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.

[0015] To more clearly illustrate the embodiments of this application, the following will briefly introduce the technical terms required in the embodiments: 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.

[0016] 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 disks 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.

[0017] The compatibility parameters include: interface type and protocol, power supply specifications, firmware version, bus bandwidth, heat dissipation requirements, logical unit number support, and operating system and driver.

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

[0019] 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 here.

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

[0021] Graphical interface application environment: Users operate through a graphical interface, which usually means there is a graphical management system that may run on a server and provide services through a 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.

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

[0023] 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 verification 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.

[0024] Message queue and data transmission environment: During the configuration process, data transmission and interaction may be involved. For example, when performing compatibility verification, 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.

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

[0026] 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 verification is required when selecting an expansion chassis.

[0027] Expansion Cabinet: The expansion cabinet is used to expand the functions of the server host and 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 bays 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 compatibility-checked with the target server host.

[0028] 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 for connecting 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 performance of these devices also need to match the hardware configuration of the entire system.

[0029] 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, thereby ensuring the effective implementation of the method and the accuracy and stability of the hardware configuration.

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

[0031] 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: 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.

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

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

[0034] List of expansion enclosures compatible with the target server host, such as EX-3500 and EX-3200. It can be displayed classified by different types of expansion enclosures. It can be storage type, network type, Graphics Processing Unit (GPU) type, etc. The type of expansion enclosure 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.

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

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

[0037]

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

[0039] The following will introduce the establishment process of the compatibility database, including the following steps S1011~S1014: S1011. Obtain the static parameters of the server host and the expansion enclosure, and establish a static parameter table.

[0040] 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; Exemplarily, the static parameters of the server host are shown in Table 1: Table 1

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

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

[0043] 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 and the Vendor_Logs table; The dynamic parameters are shown in Table 3: Table 3

[0044] S1013. Establish an association relationship between the static parameter table and the firmware compatibility table to generate a list of compatible devices; 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.

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

[0046] Specifically, update the list of compatible devices according to the affected_model field in the vendor update log. Link the vendor log table with the hardware table through the affected_model field to automatically trigger the update of compatibility rules when the vendor releases an update, ensuring the timeliness and accuracy of the database.

[0047] Exemplarily, when the vendor releases a new firmware v2.2, it is stated 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 whose 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.

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

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

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

[0051]

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

[0053] 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 capture web tables and 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.

[0054] Timed tasks trigger the manufacturer's API or crawlers to obtain raw data, providing materials for database updates. Clean the obtained raw data, remove duplicate records, and standardize the parameter format, such as unifying power units, 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 a database transaction log (such as MySQL Binlog) to record the change history, supporting rollback to a snapshot at any point in time for convenient data recovery and traceability in case of problems.

[0055] When key 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.

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

[0057] 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 according to 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.

[0058] Display the server host list in the form of a responsive table or card view in the graphical interface. 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:

[0059] 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 can 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.

[0060] 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. The card view displays information in the form of cards. Each card usually contains a set of related data or content, such as pictures, titles, descriptions, buttons, etc. The cards can exist independently or be arranged and combined on the page to form a neat and beautiful layout.

[0061] In some embodiments, display the recommended server host model in the graphical interface for users to use. The recommended server host model can be determined according to the historical hardware configuration list. Recommend the head model based on the user's historical orders or popular configurations, providing a personalized recommendation service 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, it can recommend heads with popular configurations, saving the user's time for screening head models and improving the efficiency of the user's selection of heads.

[0062] 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 frequently accessed server host data to reduce the query pressure. Using Redis to cache the frequently accessed head data 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, which improves the data reading speed, enhances 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.

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

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

[0065] The following is the pseudo code:

[0066] 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 a daisy chain structure "daisy_chain". It means that one HX5000 server host cascades 4 EX3500 storage devices through the PCIe5.0 interface.

[0067] In some embodiments, it also includes generating a topology diagram, which is a visual processing of the topological connection structure. Specifically, the D3 visualization library (Data-Driven Documents, D3.js) or the ECharts library is integrated to draw the topological connection structure of the target expansion cabinet.

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

[0069] Among them, 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. When a user selects an expansion cabinet in the system, the front end calls the interface verification module in real time. According to the verification results, the compatibility status of the expansion cabinet and the server host is highlighted in an intuitive way (for example, a green tick indicates compatibility, and a red warning icon indicates incompatibility), so that the user can timely understand whether the selected configuration is feasible.

[0070] 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. Interface parameters include interface types, etc., and interface types include, but are not limited to, Peripheral Component Interconnect Express (PCIe), SAS, Non - Volatile Memory Express (NVMe), and Universal Serial Bus (USB).

[0071] Protocol version verification is used to check whether the server host interface supports the protocol type and version of the expansion cabinet. It avoids the inability to communicate or unstable communication between devices due to protocol incompatibility, ensures that different devices can adapt to each other at the communication protocol level, and guarantees the basic connectivity of the system. For example, determine whether a server host with PCIe 5.0 is compatible with an expansion cabinet with PCIe 4.0. 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.

[0072] Physical specification verification is used to verify whether the server host slot size matches the expansion cabinet. It prevents the expansion cabinet from being incorrectly connected to the head due to mismatched physical forms, ensures the feasibility of physical connection of the device, and avoids system failures caused by hardware connection problems. For example, an x16 slot can accommodate an x8 device. If it does not meet the requirement, error code PHYSICAL_SLOT_INCOMPATIBLE is triggered, indicating physical slot incompatibility. 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.

[0073] 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 transfer 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 transfer. For example, if the expansion cabinet requires 4 PCIe4.0 x4 devices, the total bandwidth requirement is 4 x 4 x 2 GB / s = 32 GB / s, and the server host PCIe5.0 x16 interface bandwidth is 64 GB / s, the verification passes in this case; if it exceeds, the verification fails.

[0074] 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, ensures the compatibility between devices at the functional level, and prevents the expansion cabinet from malfunctioning or lacking functions due to firmware problems. For example, if the expansion cabinet requires PCIe4.0 functions and depends on the server host firmware v2.1+, if the server host firmware version is too low, the error code FIRMWARE_UPGRADE_REQUIRED is triggered, indicating that the server host firmware needs to be upgraded.

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

[0076] During the process of 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.

[0077] In some embodiments, after interface verification based on the configuration parameters, an interface verification report is generated. The interface verification report includes passed items and failed items, as follows:

[0078] In the above interface verification, device compatibility is ensured through 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.

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

[0080] 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 based on the power consumption of the target expansion cabinet and / or the bandwidth requirement of the target expansion cabinet.

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

[0082] During the resource verification process, 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 (power_consumption) of the target expansion cabinet, and the load rate.

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

[0084] For example, if the base power consumption of the server host HX5000 is 500W, the power consumption per unit of the 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.

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

[0086] The above embodiments calculate the bandwidth occupancy based on interface parameters and topology impacts, which can ensure that the interface bandwidth meets the total requirements of the expansion chassis, avoid affecting system performance due to bandwidth bottlenecks, enable efficient and stable data transmission, and fully exert the performance potential of the hardware.

[0087] In some embodiments, after calculating the total power consumption based on the server host power consumption, the target expansion chassis 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 is calculated according to the following formula: P PSU =P total ×1.2. Exemplarily, P PSU =1,220×1.2 = 1,464 W, and a 1,500 W power module can be recommended for selection.

[0088] The above embodiments can ensure stable power supply for the head and the expansion chassis by accurately calculating the total power consumption and recommending an 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.

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

[0090] 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, assume that η = 0.9 in the air-cooled solution and Q rack_max =1500 W. The total heat dissipation Q cooling =1,220×0.9 = 1,098 W, which is less than or equal to the maximum heat dissipation capacity of a single rack, indicating that the rack heat dissipation verification passes. Otherwise, Q cooling >Q rack_max, subsequent solution strategies such as adding fans, liquid cooling modules, etc. will be matched to ensure the feasibility of the configuration in terms of heat dissipation.

[0091] By considering 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 crashing due to poor heat dissipation, extend the service life of the hardware, and ensure the stable operation of the system in a suitable temperature environment.

[0092] The above resource verification quantitatively analyzes the configuration of the server head and expansion cabinets 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 risks, improve the reliability and stability of the entire system, and reduce system failures and downtime caused by insufficient or mismatched hardware resources.

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

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

[0095] 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 connection relationship input by the user 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.

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

[0097] The verification rules for the Daisy Chain 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 it is stipulated that there are at most 4 levels, then connecting more than 4 expansion cabinets in series may affect the stability and performance of the entire system. Taking the SAS expansion cabinet as an example, enabling the Terminator can effectively avoid signal reflection and ensure the integrity and stability of signal transmission.

[0098] For example, assume that the user configuration starts from the target server host HX5000, and connects the three expansion cabinets EX3500-1, EX3500-2 and EX3500-3 in sequence, forming a three-level cascade chain structure, in which the bandwidth requirement of each expansion cabinet is 40Gbps. First, the maximum cascade number check is performed. If the maximum allowed cascade number is 4, and the current configured cascade number is 3, 3 is less than or equal to 4, so the maximum cascade number check passes. Then the total bandwidth requirement of 120Gbps is calculated and compared with the bandwidth of 256Gbps 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, assuming that each meter of link will produce 0.5dB of signal attenuation, the link length of each cascaded expansion cabinet in the current configuration is 1m, and there are 3 levels of cascade, so the total signal attenuation is 3×1m×0.5dB / m=1.5dB. The maximum signal attenuation that the system can withstand is 12dB, and 1.5dB is less than or equal to 12dB, indicating that the signal attenuation is within the acceptable range. After checking the number of cascades, total bandwidth requirements, and signal attenuation, all of them meet the corresponding rules and requirements, and it can be determined that the topology is legal.

[0099] The star-shaped verification rules 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 cabinet. If there are 8 expansion cabinets, then the head needs to have 8 independent interfaces to connect them. If the number of interfaces is insufficient, it is impossible to connect all expansion cabinets, and the system will not work properly. If the total bandwidth of the head is limited, and the total bandwidth requirements of the expansion cabinets exceed the carrying capacity of the head, then a data transmission bottleneck will occur, affecting system performance.

[0100] Verification rules for hybrid topologies include, but are not limited to, hierarchical verification and global resource coordination. For example, check whether the number of cascades of switches is within the allowed range, and whether the bandwidth allocation of each branch is reasonable. Global resource coordination considers the system's power consumption, heat dissipation, bandwidth and other resources as a whole to ensure that they are within the system's carrying capacity. If the power consumption of equipment in a certain area is too high, it may cause heat dissipation problems, which in turn affects the normal operation of the equipment; if the bandwidth allocation is unreasonable, it may cause congestion on some links while other links are underutilized.

[0101] In some embodiments, assuming that the topology connection structure is a hybrid topology, during the process of performing topology connection verification on the topology connection structure according to the verification rules corresponding to the topology connection structure, first, verify layer by layer whether the topology connection structure complies with the technical specifications; calculate the signal attenuation value based on 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.

[0102] During the process of verifying layer by layer whether the topology connection structure complies with 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 verify the cascade number and bandwidth allocation of the downstream devices level by level to ensure that the connection of each level in the entire topology connection structure complies with the technical specifications.

[0103] Further, calculate the signal attenuation value according to the formula "attenuation (dB)=∑i=1nLi×k", where Li is the cable length of the i-th segment 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.

[0104] During 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 coefficient. 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.

[0105] Exemplarily, assume that the user configures the target server host HX5000 to be connected to the switch, and the EX3500-1 connected through the switch forms a 3-level daisy-chain structure (that is, there are 3 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 structure. During the verification process, the maximum allowed cascade number of the target server host HX5000 is 3 levels, while the total cascade number of this hybrid topology structure is 4 levels, exceeding the support capacity of the target server host.

[0106] The above topological connection check verifies the connection between the head unit and each level of expansion cabinets by parsing the topological configuration and performing hierarchical checks, which can verify whether the connection meets the requirements of interface types and quantities, avoid abnormal communication or system failures caused by incorrect connections, and ensure the correctness and stability of the hardware connection. By calculating the signal attenuation of long links, potential signal quality problems can be detected in a timely manner. Bandwidth allocation verification for different topological structures (daisy chain and star) is carried out to ensure 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, achieving reasonable utilization of bandwidth resources, and improving the overall performance and efficiency of the system.

[0107] S103. In the case of compatibility check failure, determine the error message and match the corresponding solution strategy for the error message from the predefined rule library.

[0108] In each check 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.

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

[0110] The pseudo-code here indicates that the current verification fails as "false". The error code "POWER_OVERLOAD" means power overload, and 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 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.

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

[0112] If problems are found during the interface verification process, assume that the user selects the target server host HX4000 (SAS-3, 12Gbps) and configures the target expansion chassis 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 with the error code "INTERFACE_VERSION_MISMATCH"; then, the corresponding solution strategy is matched: it is recommended to replace it with the server host HX5000 that supports SAS-4, or select the expansion chassis EX3500 that is compatible with SAS-3.

[0113] Exemplarily, assume that the target expansion chassis 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 chassis EX-2800 only supports PCIe4.0. The determined corresponding solution strategy is to replace it with the expansion chassis EX-3500, or replace it with the server host HX-4000.

[0114] If problems are found during the resource verification process, exemplarily, assume that the user selects the target server host HX7000 (PCIe5.0x16, total bandwidth 400Gbps) and configures 8 target expansion chassis (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; it is recommended to reserve a higher bandwidth margin to cope with peak loads.

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

[0116] 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 number of cascades allowed by the target server host, which is 3. The solution strategies for matching the error information 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 cascades.

[0117] In some embodiments, if problems are found during resource verification or topology connection verification, 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 solutions, such as replacing the high-power power supply, reducing the number of expansion enclosures, replacing the compatible expansion enclosure or server host model, etc. At the same time, the solutions will be prioritized, and solutions with low cost, high timeliness, and good compatibility will be recommended first. Users can make selections according to the recommendations or make manual adjustments.

[0118] As shown in Table 5, the predefined rule library includes error codes and corresponding multiple solutions. When the system detects a hardware configuration conflict, the corresponding solution can be directly called, avoiding technicians' temporary troubleshooting and trial-and-error, greatly shortening the problem location and resolution time, and improving the configuration efficiency.

[0119] Table 5

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

[0121] 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, and 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 priority of each solution can be more flexibly evaluated according to different users' preferences and actual needs, so as to select the most suitable solution for the specific situation.

[0122] Exemplarily, the error code "POWER_OVERLOAD" indicates that the current device configuration causes an excessive power load. The matching solution strategies include: (1) using a PSU-1500W power module; (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 results in 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.

[0123] 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 it with an expansion cabinet compatible with PCIe5.0) and has a fast delivery speed. Strategy (3) is the second. Although the cost is low, due to the problem of introducing delay risks, its priority is lower than that of strategy 1.

[0124] The above embodiments are based on the priority ranking 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 solution is the optimal solution in different scenarios, reducing the after-sales cost and system risks caused by configuration errors.

[0125] S104. In the case of successful compatibility verification, generate a hardware configuration list corresponding to the target server host.

[0126] 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. The resource requirements include recommended power supplies, cooling solutions, etc. The technical documents include topology diagrams, firmware version information, etc.

[0127] After the compatibility check passes, a hardware configuration list including the server host, expansion cabinet, configuration documents, and topology diagram is generated. The list details information such as the models, quantities, power supplies, and cooling solutions of the server host and expansion cabinet, and is synchronized to the production system. The production system interface converts the list data into a standardized format and transmits it to the production system through a RESTful Application Programming Interface (RESTful API) or 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.

[0128] Exemplarily, assume 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 a hardware configuration list is generated.

[0129] Exemplarily, assume the user configures starting from the target server host HX5000, connecting three expansion cabinets EX3500-1, EX3500-2, and EX3500-3 in sequence, and the topology connection check corresponding to the daisy chain passes, meeting the rules and requirements in terms of the number of cascades, total bandwidth requirements, and signal attenuation. Then a hardware configuration list corresponding to the target server host HX5000 is generated, and equipment procurement and deployment can be carried out according to this configuration.

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

[0131] Among them, firmware pre-flashing is to download the firmware package from the image repository according to the firmware version in the list and flash it to the head unit and expansion chassis 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 guide is to push the topology diagram to the production line display screen to guide the workers to install the expansion chassis and connect the cables in the specified order. The automated test 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:

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

[0133] During the process of transmitting the hardware configuration list to the production system, the hardware configuration list is first converted into a preset format, such as XML format (XML Schema Definition, Schema). Then the hardware configuration list is published to the message queue, and the production system retrieves it asynchronously. Message queues such as Kafka are distributed message queue systems that can reliably transmit large amounts of data.

[0134] Exemplarily, assume that the user configures 50 HX5000 head units, and each HX5000 head unit is connected to 4 EX3500 expansion chassis, adopting a star topology structure, generating 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 production-related information. 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 (installing and configuring the firmware of the device), hardware assembly (installing each hardware component into the device), and testing (performing various functional and performance tests on the device) are carried out through an automated production line. And during the entire production process, the status of the device will be 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.

[0135] In summary, for the server hardware configuration method provided by the embodiments of the present application, through the graphical interface and the pre-established compatibility database, users can quickly obtain the 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, topology connection verification, etc., can ensure that the selected hardware matches each other in terms of interface type, quantity, resource requirements, and connection method, 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 the 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 the 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 improving the user experience during the hardware configuration process. This method defines a series of processes from the user's selection of the server host to the generation of the hardware configuration list, including the loading of the compatibility database, determination of configuration parameters, verification, and error handling, etc., standardizing and standardizing the hardware configuration process and facilitating the improvement of configuration consistency and manageability.

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

[0137] The embodiments of the present application also provide a server hardware configuration device, as Figure 3 shown, the device includes: A loading module 301, configured to, in response to a user's selection input of a target server host in the graphical interface, load a list of expansion cabinets compatible with the target server host based on the 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 302, configured to, 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, where the compatibility verification includes at least one of interface verification, resource verification, and topology connection verification; 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 the predefined rule library; in the case of a successful compatibility verification, generate a hardware configuration list corresponding to the target server host.

[0138] As an alternative implementation provided by the embodiments of the present application, the server hardware configuration further includes an interaction module, which is configured to: determine a server host list corresponding to the server host model in response to the server host model input by the user; and display the server host list in the graphical interface.

[0139] As an alternative implementation provided by the embodiments of the present application, the compatibility database includes a list of compatible devices; the server hardware configuration further includes a compatibility database establishment module, which is configured to: obtain the static parameters of the server host and the expansion cabinet, and establish a static parameter table; obtain the dynamic parameters of the server host and the expansion cabinet, 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 the target field in the manufacturer update log table is updated.

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

[0141] As an alternative implementation provided by the embodiments of the present application, the configuration and verification module 302 is specifically configured to: determine that the configuration parameters include at least one of the following in response to the user's configuration operation on the target expansion cabinet: 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; and perform interface verification according to the configuration parameters.

[0142] 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; and verifying whether the current firmware version of the target server host matches the firmware version of the target expansion cabinet.

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

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

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

[0146] 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 the target expansion cabinet, determine the topology connection structure between the target server host and the target expansion cabinet; and perform topology connection verification on the topology connection structure according to the verification rules corresponding to the topology connection structure.

[0147] As an alternative implementation provided by the embodiments of the present application, when 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, it is specifically configured to: verify layer by layer whether the topology connection structure complies with technical specifications; calculate the signal attenuation value based on 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.

[0148] For the description of the features in the corresponding embodiments of the server hardware configuration device, reference may 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.

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

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

[0151] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: various media such as USB flash drives, read-only memory (ROM for short), random access memory (RAM for short), external hard drives, magnetic disks, or optical discs that can store computer programs.

[0152] 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 server hardware configuration method embodiments.

[0153] 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 server hardware configuration method embodiments.

[0154] Those skilled in the art can 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 the two. 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. Skilled professionals can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0155] The above has introduced in detail a server hardware configuration method, device, equipment, storage medium, and product provided by the present application. Specific examples are used herein to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present 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 compatibility verification, the compatibility verification includes at least one of interface verification, resource verification, and topology connection verification; In the case where the compatibility verification 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 verification is successful, generating a hardware configuration list corresponding to the target server host.

2. The method according to claim 1, wherein Before the step of loading a list of expansion enclosures compatible with the target server host based on a pre-established compatibility database in response to a user's selection input of a target server host in a graphical interface, the method further includes: In response to a server host model input by a 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, characterized in that The compatibility database includes a list of compatible devices; the establishment process of the compatibility database includes: Obtaining static parameters of a server host and an expansion enclosure, and establishing a static parameter table; Obtaining 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 a target field in the manufacturer update log table is updated.

4. The method according to claim 3, wherein After establishing an association relationship between the static parameter table and the firmware compatibility table to generate a list of compatible devices, and before updating the list of compatible devices when a 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 a target field in the manufacturer update log table is updated.

5. The method according to claim 1, characterized in that In response to a user's configuration operation on a target expansion enclosure in the list of expansion enclosures, determining configuration parameters and performing compatibility verification, including: In response to a user's configuration operation on the target expansion enclosure, determining that the configuration parameters include at least one of the following: the protocol type and version of the target expansion enclosure, the interface size of the target expansion enclosure, the bandwidth requirement of the target expansion enclosure, and the firmware version of the target expansion enclosure; Performing 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: Checking whether the interface of the target server host supports the protocol type and version of the target expansion enclosure; Verifying whether the slot size of the target server host matches the interface size of the target expansion enclosure; 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, characterized in that, 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: Verify layer by layer whether the topology connection structure complies with 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, Includes: 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, configured to, 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, and the compatibility verification includes at least one of interface verification, resource verification, and topology connection verification; 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.

13. An electronic device, characterized in that, Includes: A memory, configured to store a computer program; A processor, configured 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 when the computer program is executed by a processor, the steps of the server hardware configuration method according to any one of claims 1 to 11 are implemented.

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

Images