Network equipment configuration method, device, equipment and readable storage medium

Abstract

The invention discloses a network equipment configuration method and device, equipment and a readable storage medium, which are applied to the technical field of network engineering, and comprise the following steps: defining a service type identifier based on a service scene and equipment list information, and classifying configuration commands according to universality, personalization and characterization to obtain a configuration module library; obtaining target physical specification information from an equipment baseline library based on an equipment list template determined based on the service demand, and generating a service network topology based on interconnection information determined based on the target physical specification information; and rendering the target configuration module to obtain a rendered configuration module, generating a target network configuration file based on the rendered configuration module and the service network topology, and performing configuration based on the target network configuration file. According to the invention, the automatic conversion from the service intention to the network equipment configuration is realized, and the configuration file is arranged and generated as required through the visual interaction based on the equipment baseline library and the configuration module library, so that the efficiency and accuracy of the equipment configuration are improved.

Description

Technical Field

[0001] This invention relates to the field of network engineering technology, and in particular to a network device configuration method, apparatus, device, and readable storage medium. Background Technology

[0002] Currently, network device configuration mainly relies on network engineers manually writing command-line configurations. This manual approach is inefficient and prone to errors. Especially in heterogeneous network environments, the configuration syntax of devices from different vendors (such as Cisco, Huawei, H3C, etc.) varies significantly. Engineers need to have multi-vendor technical skills and write configuration code separately for each device, resulting in a large workload, high repetition, and difficulty in ensuring configuration consistency and accuracy.

[0003] It is evident that improving the accuracy and efficiency of configuration is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a network device configuration method, apparatus, device and readable storage medium, which solves the technical problems of low accuracy and efficiency in configuration in the prior art.

[0005] To address the aforementioned technical problems, this invention provides a network device configuration method, comprising:

[0006] Predefine the physical specifications of heterogeneous network devices, and classify the physical specifications of the heterogeneous network devices based on business scenario requirements to obtain a device baseline library;

[0007] Based on business scenarios and equipment list information, define business type identifiers, and classify and modularize configuration commands according to generality, personalization and specialization, based on equipment roles, to obtain a configuration module library;

[0008] Based on the equipment list template determined by business requirements, target physical specification information is obtained from the equipment baseline library, and the business network topology is generated based on the interconnection information determined by the target physical specification information.

[0009] Based on the service type identifier determined by the device list template, the target configuration module in the configuration module library is determined, and the target configuration module is rendered to obtain the rendered configuration module. Based on the rendered configuration module and the service network topology, a target network configuration file is generated, and the target network configuration file is configured.

[0010] Optionally, business type identifiers are defined based on business scenarios and device inventory information. Configuration commands are then categorized and modularized according to their generality, personalization, and specialization, using device roles as the dimension, resulting in a configuration module library, including:

[0011] The configuration commands are decomposed according to their functions to form independent configuration modules;

[0012] Assign each configuration module with encoding that includes business semantics;

[0013] The configuration module and its encoding, as well as the predefined configuration identifiers within the module, are stored; wherein the configuration identifiers are used to be replaced by actual business parameters during configuration generation to achieve rendering parameter injection.

[0014] Optional, predefined physical specification information for heterogeneous network devices, including:

[0015] The physical specifications of the predefined heterogeneous network devices include the manufacturer, model, port type, and number of ports.

[0016] Optionally, business type identifiers are defined based on business scenarios and device inventory information. Configuration commands are then categorized and modularized according to their generality, personalization, and specialization, using device roles as the dimension, resulting in a configuration module library, including:

[0017] Based on the standardization of configuration order, the modularization of configuration options, and the objectification of configuration parameters, the configuration commands are classified according to their generality, personalization, and characteristics.

[0018] The standardized configuration order follows the basic logic of network configuration and is divided into element-level configuration, global-level configuration, and extended-level configuration.

[0019] The configuration options are modularized based on the generality of business scenarios and are divided into general configuration, personalized configuration and feature-specific configuration.

[0020] The configuration parameters are objectified and divided into pre-allocated parameters and variable parameters based on the business scenario.

[0021] Optionally, based on the equipment list template determined by business requirements, target physical specification information is obtained from the equipment baseline library, and based on the interconnection information determined by the target physical specification information, a business network topology is generated, including:

[0022] The device list template is parsed using a one-center, three-view visualization orchestration component to obtain a visual interactive orchestration of device objects and device baselines; wherein, the one center is the configuration visualization orchestration center, and the three views are the device baseline view, configuration module view, and configuration code view in the device baseline library;

[0023] Interconnection is achieved through visual orchestration of the device objects and device baselines, resulting in interconnection information, and the service network topology is generated based on the interconnection information.

[0024] Optionally, based on the service type identifier determined by the device list template, a target configuration module in the configuration module library is determined, and the target configuration module is rendered to obtain a rendered configuration module. A target network configuration file is then generated based on the rendered configuration module and the service network topology. Configuration is performed based on the target network configuration file, including:

[0025] The target network configuration file generates a unique identifier based on the device manufacturer, service type identifier code, and device address.

[0026] Optionally, based on the service type identifier determined by the device list template, a target configuration module in the configuration module library is determined, and the target configuration module is rendered to obtain a rendered configuration module. A target network configuration file is then generated based on the rendered configuration module and the service network topology. Configuration is performed based on the target network configuration file, including:

[0027] Based on the rendered configuration modules and the business network topology, the target network configuration file is generated by serialization and orchestration using preset construction rules; wherein, the preset construction rules are based on the network configuration logic of the equipment manufacturer and define the association relationship and generation order between each configuration module.

[0028] The present invention also provides a network device configuration apparatus, comprising:

[0029] The device baseline library construction module is used to predefine the physical specification information of heterogeneous network devices, classify the physical specification information of the heterogeneous network devices based on business scenario requirements, and obtain the device baseline library.

[0030] The configuration module library is built by defining business type identifiers based on business scenarios and device list information, and classifying and modularizing configuration commands according to generality, personalization and feature-based coding based on device roles to obtain the configuration module library.

[0031] The visualization module is used to obtain target physical specification information from the equipment baseline library based on the equipment list template determined by business requirements, and generate a business network topology based on the interconnection information determined by the target physical specification information.

[0032] The network device configuration module is used to determine the target configuration module in the configuration module library based on the service type identifier determined by the device list template, render the target configuration module to obtain the rendered configuration module, generate a target network configuration file based on the rendered configuration module and the service network topology, and configure based on the target network configuration file.

[0033] The present invention also provides a network device configuration device, comprising:

[0034] Memory, used to store computer programs;

[0035] A processor for executing the computer program to implement the steps of the network device configuration method described above.

[0036] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described network device configuration method.

[0037] The present invention also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the above-described network configuration method.

[0038] As can be seen, this invention predefines the physical specifications of heterogeneous network devices, classifies these specifications based on business scenario requirements, and obtains a device baseline library. It defines business type identifiers based on business scenarios and device list information, and classifies and modularizes configuration commands according to generality, personalization, and specialization, using device roles as the dimension, resulting in a configuration module library. Based on the device list template determined by business requirements, it retrieves target physical specification information from the device baseline library and generates a business network topology based on the interconnection information determined by the target physical specification information. Based on the business type identifier determined by the device list template, it identifies the target configuration module in the configuration module library, renders the target configuration module, and generates a target network configuration file based on the rendered configuration module and the business network topology. Configuration is then performed based on the target network configuration file. Compared to current manual configuration writing, this invention provides orchestratable configuration modular construction and generation dump capabilities, achieving end-to-end automated conversion from business intent to device configuration. Through visual interaction, it enables on-demand customization, orchestration, and expansion to adapt to different business scenarios, thereby improving configuration efficiency and accuracy.

[0039] In addition, the present invention also provides a network device configuration apparatus, device, and readable storage medium, which also have the above-mentioned beneficial effects. Attached Figure Description

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

[0041] Figure 1A flowchart illustrating a network device configuration method provided in an embodiment of the present invention;

[0042] Figure 2 This is a schematic diagram of a device baseline library arrangement provided in an embodiment of the present invention;

[0043] Figure 3 A schematic diagram illustrating the construction of a configuration module according to an embodiment of the present invention;

[0044] Figure 4 This is a schematic diagram illustrating the visualization, parsing, orchestration, configuration, and generation process provided in an embodiment of the present invention.

[0045] Figure 5 This is a schematic diagram of a network device configuration apparatus provided in an embodiment of the present invention;

[0046] Figure 6 This is a schematic diagram of the structure of a network device configuration device provided in an embodiment of the present invention. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0048] The purpose of this invention is to provide a modular configuration construction and generation method based on a B / S (browser-server) architecture, which can be independently orchestrated and easily extended. It realizes a complete automated generation process from business intent to device configuration file, organically integrating multiple discrete steps (parsing-visualization-module matching-parameter injection-file generation) into a smooth automated pipeline. It is suitable for standardized new data center construction, equipment expansion, and network transformation. While improving efficiency, it also serves as a repository of organizational configuration module libraries and business practice scenarios.

[0049] The main features are: after predefining the orchestration device baseline library and configuration module library, the business intent is formatted into preset basic business configuration fields and parameters through a visual parsing and orchestration method. After modular deconstructing and encoding the network device hardware and business configuration logic, the backend service component obtains the configuration module group / configuration module through the business type identifier encoding, and initializes the parsing request in combination with the configuration parameters. The configuration module is injected and integrated with the configuration identifier. Finally, after being uniquely named according to the business type identifier encoding + device address + suffix, it is automatically dumped to the cloud and exported or distributed for use as needed. This invention targets specialized business scenarios in the field of network engineering, providing orchestratable configuration modular construction and dump generation capabilities. It achieves end-to-end automated conversion from business intent to device configuration, forming a unified configuration abstraction layer by deconstructing the configuration generation logic of heterogeneous network devices. Furthermore, it offers excellent visual interaction capabilities, allowing users to customize, orchestrate, and extend configurations as needed to adapt to different business scenarios. A modular and scalable systematic configuration module library is formed, enabling the modular storage of configuration commands after summarizing, classifying, and encoding them according to generality, personalization, and specificity. It allows for the dynamic matching, combination, and rendering of different configuration modules through "business type identifiers" and "deployment configuration identifiers," and the automated injection of parameters. Finally, it automatically completes the automated configuration processing and file generation dump based on the basic parameter module library of business intent and the backend business configuration construction module. To achieve the above objectives, the technical solution of this invention mainly consists of: device baseline library orchestration, configuration module library construction, visual parsing orchestration, and configuration construction, generation, and dumping.

[0050] Please refer to Figure 1 , Figure 1 A flowchart illustrating a network device configuration method provided in an embodiment of the present invention. The method may include:

[0051] S101, predefine the physical specifications of heterogeneous network devices, classify the physical specifications of heterogeneous network devices based on business scenario requirements, and obtain the device baseline library.

[0052] Each step in this embodiment can be executed by a designated electronic device, which can be a server, portable terminal, or other form. This embodiment predefines the manufacturers, models, port types, and port quantities of various potentially involved heterogeneous network devices based on actual business scenario requirements and device physical specifications. These are then batch-stored in a database, and a standardized API interface is provided for external use. This provides standard, programmable physical device baseline data for visual interaction. For ease of understanding, please refer to [link / reference]. Figure 2 , Figure 2This diagram illustrates a device baseline library arrangement according to an embodiment of the present invention. As shown, the collected physical specification information undergoes "CRUD operations" (add, delete, modify, query). This step does not involve direct storage; instead, the data is cleaned, parsed, transformed, and standardized for mapping. Following this, a data format check is performed. The system compares the processed data with predefined data models and business rules to verify its completeness and compliance (e.g., whether the manufacturer and model are on the supported list, and whether the number of ports is reasonable).

[0053] S102 defines business type identifiers based on business scenarios and equipment list information, and classifies and modularizes configuration commands according to generality, personalization and specialization based on equipment roles to obtain a configuration module library.

[0054] This embodiment encodes business type identifiers based on business scenarios and their corresponding equipment list information (equipment manufacturers, quantities, and models). For example: A - Business Scenario: Classic Deployment Solution - A1 / VXLAN (Virtual Extended LAN) Deployment Solution - B1; A1 / B1 is the deployment solution type identifier for this business scenario; 2 - Equipment Role: Internet Access Switch - 2A / Service Switch - 2B / Computing Power Access Switch - 2C; 3 - Deployment Method: Single Machine - 3A / Redundant Primary - 3M / Redundant Backup - 3S; 4 - Equipment Manufacturer: AA - 4A / BB - 4B / CC - 4C; 5 - Equipment Model: CE6880-4A-301 / S6800-4B-301, etc., and so on, ultimately forming... The combined A1-2A-3M-4C-501 can be resolved to VXLAN deployment scenario / solution - Internet access switch - redundant deployment main device - AA-CE6880), where the definition here focuses on the overall service deployment scenario / solution. It should be further noted that, based on any of the above embodiments, the predefined physical specification information of the heterogeneous network devices may include: the predefined physical specification information of the heterogeneous network devices includes the manufacturer, model, port type, and number of ports. It can be understood that the device baseline library is the physical layer device information, and the configuration module is the configuration command. The configuration code is used to name the configuration module. This embodiment provides specific physical specification information, improving the accuracy of determining the physical specification information.

[0055] It should be further explained that, based on any of the above embodiments, the above-described business type identifier defined based on business scenarios, and the classification and modular coding of configuration commands according to generality, personalization, and specialization based on device roles, to obtain a configuration module library, may include:

[0056] S1021, decompose the configuration commands according to their functions to form independent configuration modules;

[0057] S1022, assign each configuration module with encoding containing business semantics;

[0058] S1023, the configuration module, its code, and predefined configuration identifiers within the module are stored; wherein, the configuration identifiers are used to be replaced by actual business parameters during configuration generation to achieve rendering parameter injection. In this embodiment, a configuration module can be generated based on a configuration command. This configuration module has a corresponding code and configuration identifier, so that during subsequent rendering, the corresponding configuration command can be directly obtained based on the code, and rendering can be performed based on the configuration identifier.

[0059] It should be further explained that, based on any of the above embodiments, the above-described business type identifier definition based on business scenarios, and the classification and modular coding of configuration commands according to generality, personalization, and specialization based on device roles to obtain a configuration module library, may include: classifying configuration commands according to generality, personalization, and specialization based on configuration order standardization, configuration option modularization, and configuration parameter objectification; configuration order standardization follows the basic logic of network configuration and is divided into element-level configuration, global-level configuration, and extended-level configuration; configuration option modularization is based on the generality of business scenarios and is divided into general configuration, personalized configuration, and specialization configuration; configuration parameter objectification is based on the needs of business scenarios and is divided into pre-allocated parameters and variable parameters. For ease of understanding, please refer to [reference needed]. Figure 3 , Figure 3This is a schematic diagram illustrating the construction of a configuration module according to an embodiment of the present invention. Based on device roles, and according to predefined device roles (e.g., service switch / computing access switch / internet access switch, etc., the preset roles need to be coupled with the input after the visual interactive orchestration), configuration commands are defined, summarized, and classified according to generality / personalization / characteristics. The classification rules are preset based on aspects such as standardized configuration order, modularized configuration options, and object-oriented configuration parameters. (1) The configuration order is standardized and classified according to the basic configuration order logic of the network configuration. It is divided into ① element level - corresponding to basic configuration element objects: such as VLAN (Virtual Local Area Network) / VSI (Virtual Switch Instance), LOOPBACK (Loopback Interface) interface, ACL configuration (Access Control List Configuration), VRF (Virtual Router Forwarding Instance) instance, etc.; ② global level - corresponding to global function or protocol enablement support: such as DHCP (Dynamic Host Configuration Protocol), LLDP (Link Layer Discovery Protocol), STP (Spanning Tree Protocol), VXLAN (Virtual Extended Local Area Network), EVPN (Ethernet Virtual Private Network), etc.; ③ extension level - based on the element level, the configuration is extended or associated to ensure the fullness and necessity of the configuration: such as VLAN IF (Virtual Local Area Network Interface), PBR (Policy Routing), VPN (Virtual Private Network) binding and other configuration options are modularized. (2) The configuration options are modularized, following common knowledge in business scenarios / solutions and network configuration scenarios, and are subdivided into ① general configurations, which are common to both VXLAN and classic network deployment scenarios, such as sysname, ntp, snmp, ssh, etc.; ② personalized configurations, which are involved in both VXLAN and classic network deployment scenarios but have different configurations, such as VLAN / VNI (Virtual Network Identifier), VLANIF (Layer 3 Virtual Interface) / VBD (Virtual Bridge Domain Interface), etc.; ③ characteristic configurations, which are only involved in VXLAN deployments, such as enabling VXLAN / EVPN (Ethernet Virtual Private Network) and other deployment scenarios.(3) If the configuration parameters are objectified, then based on the business scenario or deployment configuration needs, it provides orchestration capabilities, which are divided into ① pre-allocated parameters, some global or fixed-plan local configuration parameters, which are fixedly pre-allocated or orchestrated on demand; ② variable parameters, which are parameters that need to be modified according to the business scenario. By defining the configuration module corresponding configuration identifier, they are used for subsequent configuration building and generation. The configuration is organized and arranged according to the actual configuration commands of the vendor. If personalized and characteristic configurations are involved, the configuration identifiers need to be preset in the configuration module and finally encoded and stored (e.g., X101: X is identified as category - general configuration, X1 - global baseline configuration module group, X101 - basic function configuration module, configuration identifier - not involved; Y301: Y is identified as category personalized configuration, Y3 - network IP address configuration module group, Y302 - switch). The system includes interconnected VLAN configuration modules, configuration identifiers (VLANs, etc.), forming configuration modules and configuration module groups. Each configuration module, based on the configuration logic of the adapted vendor's network equipment and combined with different business scenarios, presets device roles, redundancy roles, interconnection methods, interconnection types, priorities, configuration blocks, configuration identifiers, etc. This method abstracts the complexity of network configuration, making it manageable and reusable. It also allows for personalized customization and orchestration of specific configuration modules based on actual business scenario requirements and scenarios. Finally, based on the inductive classification and modular coding construction logic, a configuration module library is formed with the vendor as the dimension. It supports horizontal expansion at the vendor level and vertical iteration at the configuration module group / configuration module granularity. It provides standardized API interfaces and provides standard, orchestratable, and reusable configuration baseline data when providing visual interaction.

[0060] S103: Based on the equipment list template determined by business requirements, obtain the target physical specification information from the equipment baseline library, and generate the business network topology based on the interconnection information determined by the target physical specification information.

[0061] This embodiment, when configuring network devices, can determine the required device list template for visual parsing and orchestration. The device list template in this embodiment is a list of devices that need to be configured. Using "device model" as an index, it matches against a device baseline library, extracting all standardized physical and logical attributes of that model. This embodiment can, based on a visual baseline orchestration built from the device baseline library and configuration module library, parse the device list template and present device views and parameter information based on device roles (allowing users to perform drag-and-drop interconnection and parameter adjustments, presenting a visual topology canvas of devices, and enabling one-click generation / storage of configurations based on business intent, etc.).

[0062] It should be further explained that, based on any of the above embodiments, the above-mentioned method of obtaining target physical specification information from the device baseline library based on the device list template, and generating a service network topology based on the interconnection information determined by the target physical specification information, may include:

[0063] S1031, using a one-center, three-view visualization orchestration component, the device list template is parsed to obtain the visual interactive orchestration of device objects and device baselines; where the one center is the configuration visualization orchestration center, and the three views are the device baseline view, configuration module view, and configuration code view in the device baseline library;

[0064] S1032, based on the visual orchestration of device objects and device baselines, interconnection is achieved, interconnection information is obtained, and network topology is generated based on the interconnection information.

[0065] This implementation utilizes a one-center, three-view architecture to provide a simple and easy-to-use visual parsing and intelligent orchestration exchange capability for device lists. The three views—device baseline view, configuration module view, and configuration coding view—form three data baselines, providing data baselines for device, configuration, and coding-related functions, and integrating visual baseline orchestration functionality. The central hub is the intelligent configuration orchestration center, which, based on the baseline data formed by the three views, serves as the core component of the intelligent orchestration architecture. Southbound, it uses the standard POST API interface (data submission interface) of the three views to form a stable and flexible data warehouse baseline. The backend connects to a B / S architecture intelligent configuration orchestration server component. Finally, through a visual dashboard interface, users are provided with import, export, and parsing of the business network device list module (using a preset device list template and form fields, users can export and fill in the form by selecting options from the dropdown menu, then import the list through the visual interface; after automatic parsing, the device view and device parameter information are presented based on device roles). Users can also perform drag-and-drop interconnection and parameter adjustment (based on the visual interactive orchestration of device objects and device baselines). This system enables the creation of physical device connections through drag-and-drop functionality for business intents, as well as the planning and orchestration of interconnection options and parameters between device objects, thereby achieving dynamic configuration of field parameters for business intents, and formatting processing. It also allows for the visualization of device topology canvases (by parsing devices and performing drag-and-drop interconnection and interactive orchestration, a concrete business network topology based on user business intents is formed), and one-click generation / storage of configurations based on business intents (through a pre-defined API interface, a backend intelligent orchestration component sends a POST request to the configuration file, which, based on the network device basic configuration rules of various vendors, completes the request processing and result response for the autonomous orchestration, construction, generation, and dumping of configurations).

[0066] S104: Based on the service type identifier determined by the device list template, determine the target configuration module in the configuration module library, render the target configuration module to obtain the rendered configuration module, generate the target network configuration file based on the rendered configuration module and the service network topology, and configure based on the target network configuration file.

[0067] In this embodiment, a target service type identifier related to the service requirements in the device manifest template is determined. Based on this identifier, the corresponding target configuration module is obtained, and then the target configuration module is rendered based on the input parameters (user-defined rendering parameters). This embodiment primarily utilizes a dynamic configuration module overlay and elastic parameter injection method based on service type identifiers to achieve rendering. It associates logical configurations with specific physical ports based on port information provided by the device baseline library, assembles each configuration module in the correct order according to the business logic defined by the service type identifier, and resolves dependencies between modules. This embodiment can also parse the configuration module code based on the service type identifier to obtain the corresponding configuration module group / module, extract the configuration command block and configuration identifier corresponding to the configuration module code, and finally, based on the initialized device manifest parameters and network configuration basic logic, perform parameter injection to complete the configuration block rendering process.

[0068] It should be further explained that, based on any of the above embodiments, the target configuration module in the configuration module library is determined by the service type identifier based on the device list template, and the target configuration module is rendered to obtain the rendered configuration module. A target network configuration file is then generated based on the rendered configuration module and the service network topology. Configuration based on the target network configuration file can include: generating a uniquely identified target network configuration file based on the device manufacturer, service type identifier encoding, and device address. This embodiment can generate a corresponding suffix configuration file based on the manufacturer and service template encoding, and the device management address, ensuring file uniqueness and identifiability (the device service type and related information can be identified through secondary decoding based on encoding rules). Finally, it is automatically uploaded to the cloud for subsequent service deployment.

[0069] It should be further explained that, based on any of the above embodiments, the target configuration module in the configuration module library is determined by the service type identifier based on the device manifest template, and the target configuration module is rendered to obtain the rendered configuration module. A target network configuration file is then generated based on the rendered configuration module and the service network topology. Configuration based on the target network configuration file can include: generating the target network configuration file by serializing and orchestrating it using preset construction rules based on the rendered configuration module and the service network topology; wherein, the preset construction rules are based on the network configuration logic of the device manufacturer and define the relationships and generation order between each configuration module. This embodiment can complete the serialization and orchestration of service configuration content through preset construction rules.Understandably, this step primarily relies on the dynamic configuration module overlay and elastic parameter injection method based on identifiers. It dynamically matches, combines, and renders different configuration modules using "business type identifiers" and "deployment configuration identifiers," and automatically injects parameters (this is implemented by the backend server component, which provides corresponding functional APIs (interfaces) to listen for corresponding HTTP (Hypertext Transfer Protocol) requests. Upon receiving the configuration generation request body, it routes to the corresponding function (calling the corresponding program for data formatting). First, it formats and cleans the input parameters to obtain the data required for configuration generation, and formats and preprocesses the device information to be generated. Then, it centrally collects key parameters for all device business scenarios: device role, name, IP address, manufacturer, template encoding, and subsequent rendering, construction, and file generation / dumping of user configuration module groups / configuration modules. After formatting the manifest information, it performs multi-threaded concurrent generation processing, matching the corresponding processor based on the manufacturer and device role, creating a processor instance and executing it. The processor instance first initializes the device's global parameters, device interconnection parameters, and configuration file parameters, and then processes predefined parameters that only require individual configuration. The system generates a general-purpose global configuration module that is processed only once. This module includes settings such as device naming, management method and corresponding address, basic function configuration, and enabling / disabling SNMP (Simple Network Management Protocol) / LLDP (Link Layer Discovery Protocol) / DHCP (Dynamic Host Configuration Protocol) services. Next, it processes interconnection-related modules, generating configurations based on edge interconnection data between devices, such as VLAN (Virtual Local Area Network) / interface / aggregation / MLAG (Multi-Chassis Link Aggregation) / routing, etc. After parsing the preset configuration module encoding based on the service type identifier, it obtains the corresponding configuration module group / module and extracts the configuration command block and configuration identifier corresponding to the configuration module encoding. Finally, based on the initialized device list parameters and network configuration basic logic, it performs parameter injection to complete the configuration block rendering process. After all rendering is complete, it serializes and orchestrates the service configuration content according to preset construction rules, and generates corresponding suffix configuration files based on the vendor and service template encoding and device management IP naming, ensuring file uniqueness and identifiability (the encoding rules allow for secondary decoding to identify device service types and related information). Finally, it automatically uploads the files to the cloud for subsequent service deployment. Please refer to the documentation for easier understanding. Figure 4 , Figure 4This invention provides a visual parsing, orchestration, and configuration generation diagram. First, a device list template is downloaded; this is a standardized spreadsheet file. Users fill in the device list to be configured in the template according to their actual network device service requirements and then upload it back to the system. Upon receiving the device list, the system enters the device baseline view stage. This can be understood as automatically matching and generating a standard configuration baseline or view for each device based on a built-in device model knowledge base. Simultaneously, it processes the connection relationships between devices, generating device interconnection information and clarifying the logical connections between the ports of each device. The system verifies the format of the device list, the legality of the device models, and the rationality of the connection logic to ensure the accuracy of the input data, laying a reliable foundation for subsequent configuration generation. After successful verification, the process enters the final stage. Users or the system can trigger the one-click configuration generation function. The system combines information such as device baselines and interconnection relationships to automatically generate complete and directly usable detailed configuration text for each device in the list. Finally, these generated standard configurations are securely saved to cloud storage.

[0070] Specifically, it can include:

[0071] First, users obtain the configuration template through the intelligent orchestration center. After successful acquisition, they proceed to the second step.

[0072] Second, edit the template form. Click to select the deployment plan, device type, role, manufacturer, and model. Then, plan the device name, management address and mask, deployment method, and other information as needed, and save the template. Proceed to the third step.

[0073] Third, after importing the device list by clicking the upload template button and selecting the template file, check the topology canvas to confirm that the devices and information are displayed correctly. Then proceed to step four. Otherwise, try to re-import or report the problem to maintenance personnel for handling.

[0074] Fourth, click "Add Device Interconnection," select the network device in the visual topology, select and connect the physical lines of the topology as needed, and after completing the expected interconnection link connection for the business intent, proceed to step five.

[0075] 5. After the initial connection, the line color is gray. Click on the corresponding gray lines in sequence to enter the line card parameter configuration view. Arrange the preset local and peer interconnection types (heartbeat, interconnection, uplink, downlink, detection, out-of-band interface, etc.), interconnection methods (single line, static, dynamic), aggregation group number, interconnection-related VLANs, IPs, masks, interfaces, virtual MACs, etc., and routing-related routing types (static, dynamic), process IDs, Area IDs, COST values, etc., and then click submit. After success, the line will turn green, and you can then complete the arrangement of other lines and the improvement of line parameters in sequence. After the line parameters are improved, proceed to step six; otherwise, report the fault.

[0076] 6. Click "Save Topology". After the business topology data has been successfully saved, proceed to step 7; otherwise, execute step 5 to confirm whether the data is incomplete or duplicated.

[0077] 7. Click "Generate Configuration with One Click". A message indicating that the configuration generation is complete will appear, meaning that the current business network topology configuration has been generated. Check if a uniquely named configuration file exists in the default cloud storage path. If it does, proceed to step 8. Otherwise, modify the parameters according to the error message and click "Generate" again or report the error.

[0078] 8. Click Export Data to verify whether the configuration meets expectations. If it does, you can import it into the device for use. Alternatively, you can adjust the device line parameters or the corresponding configuration block in the configuration module view as needed, and then repeat steps 5-7 for custom editing and adaptation.

[0079] 9. Complete the generation and dumping of modular configurations.

[0080] This invention provides a network device configuration method, which may include: S101, predefining physical specification information of heterogeneous network devices, classifying the physical specification information of heterogeneous network devices based on business scenario requirements, and obtaining a device baseline library; S102, defining business type identifiers based on business scenarios, and classifying and modularizing configuration commands according to generality, personalization, and characteristic based on device roles, and obtaining a configuration module library; S103, obtaining target physical specification information from the device baseline library based on a device manifest template, and generating a business network topology based on the interconnection information determined by the target physical specification information; S104, determining the target configuration module in the configuration module library based on the business type identifier determined by the device manifest template, rendering the target configuration module, obtaining a rendered configuration module, generating a target network configuration file based on the rendered configuration module and the business network topology, and configuring based on the target network configuration file. Compared with the current manual configuration writing, this invention provides orchestrable configuration modular construction and generation dump capabilities, realizing end-to-end automated conversion from business intent to device configuration, and enabling on-demand customization, orchestration, and expansion through visual interaction to adapt to different business scenarios, thereby improving configuration efficiency. This invention primarily innovates in configuration module library construction, visual parsing and orchestration, and configuration generation. The configuration module library construction abstracts the complexity of network configuration by summarizing, classifying, and modularizing configuration commands according to their generality, personalization, and specialization, making them manageable and reusable – an innovation at the software architecture and data organization level. Visual parsing and orchestration, based on a business scenario-based device list parsing and visual interaction method, transforms the tedious device list into a visual dashboard, allowing users to drag and drop interconnections and parameter adjustments – an innovation at the human-computer interaction level, improving the efficiency and accuracy of configuration generation. Configuration generation utilizes a dynamic configuration module overlay and elastic parameter injection method based on identifiers. It dynamically matches, combines, and renders different configuration modules using "business type identifier fields" and "deployment configuration identifiers," and automatically injects parameters – an innovation at the data processing and generation level, resolving the contradiction between template flexibility and rigidity. The entire solution, from business intent to complete automated generation of device configuration files, as a complete system and method, organically integrates multiple discrete steps (parsing-visualization-template matching-parameter injection-file generation) into a smooth automated pipeline – a systemic innovation.

[0081] The network device configuration apparatus provided in the embodiments of the present invention will be described below. The network device configuration apparatus described below and the network device configuration method described above can be referred to in correspondence.

[0082] Please refer to the details. Figure 5 , Figure 5A schematic diagram of a network device configuration apparatus provided in an embodiment of the present invention may include:

[0083] The device baseline library construction module 100 is used to predefine the physical specification information of heterogeneous network devices, classify the physical specification information of the heterogeneous network devices based on business scenario requirements, and obtain the device baseline library.

[0084] The configuration module library is built by module 200, which is used to define business type identifiers based on business scenarios and equipment list information, and classify and modularize configuration commands according to generality, personalization and feature-based coding based on equipment roles, so as to obtain the configuration module library.

[0085] The visualization module 300 is used to obtain target physical specification information from the equipment baseline library based on the equipment list template determined by business requirements, and generate a business network topology based on the interconnection information determined by the target physical specification information.

[0086] The network device configuration module 400 is used to determine the target configuration module in the configuration module library based on the service type identifier determined by the device list template, render the target configuration module, generate a target network configuration file based on the rendered configuration module and the service network topology, and configure the target network configuration file.

[0087] Furthermore, based on any of the above embodiments, the configuration module library construction module 200 may include:

[0088] The decomposition unit is used to decompose the configuration commands according to their functions, forming independent configuration modules;

[0089] Encoding unit, used to assign encoding containing business semantics to each configuration module;

[0090] The storage unit is used to store the configuration module and its encoding, as well as the predefined configuration identifiers within the module; wherein the configuration identifiers are used to be replaced by actual business parameters during configuration generation to achieve rendering parameter injection.

[0091] Furthermore, based on any of the above embodiments, the device baseline library construction module 100 may include:

[0092] The device baseline library constructs a ternary structure, which is used to define the physical specifications of heterogeneous network devices, including the manufacturer, model, port type, and number of ports.

[0093] Furthermore, based on any of the above embodiments, the configuration module library construction module 200 may include:

[0094] The classification unit is used to categorize the configuration commands according to their generality, personalization, and specialization based on the standardization of configuration order, the modularization of configuration options, and the objectification of configuration parameters. The standardization of configuration order follows the basic logic of network configuration and is divided into element-level configuration, global-level configuration, and extended-level configuration. The modularization of configuration options is based on the generality of business scenarios and is divided into general configuration, personalized configuration, and specialization configuration. The objectification of configuration parameters is based on the needs of business scenarios and is divided into pre-allocated parameters and variable parameters.

[0095] Furthermore, based on any of the above embodiments, the visualization module 300 may include:

[0096] The orchestration unit is used to parse the device list template using a one-center, three-view visualization orchestration component to obtain a visual interactive orchestration of device objects and device baselines; wherein, the one center is the configuration visualization orchestration center, and the three views are the device baseline view, configuration module view, and configuration code view in the device baseline library;

[0097] The interconnection unit is used to achieve interconnection based on the visual orchestration of the device object and the device baseline, obtain interconnection information, and generate the service network topology based on the interconnection information.

[0098] Furthermore, based on any of the above embodiments, the network device configuration module 400 may include:

[0099] The identifier generation unit is used to generate a unique identifier for the target network configuration file based on the device manufacturer, service type identifier code, and device address.

[0100] Furthermore, based on any of the above embodiments, the network device configuration module 400 may include:

[0101] The target network configuration file generation unit is used to generate the target network configuration file by serialization and arrangement based on the rendered configuration modules and the service network topology using preset construction rules; wherein, the preset construction rules are based on the network configuration logic of the equipment manufacturer and define the association relationship and generation order between each configuration module.

[0102] It should be noted that the order of the modules and units in the above-mentioned network device configuration device can be changed without affecting the logic.

[0103] This invention provides a network device configuration apparatus, which may include: a device baseline library construction module 100, used to predefine physical specification information of heterogeneous network devices, classify the physical specification information of the heterogeneous network devices based on business scenario requirements, and obtain a device baseline library; a configuration module library construction module 200, used to define business type identifiers based on business scenarios and device list information, and classify and modularize configuration commands according to generality, personalization, and characteristic based on device roles, and obtain a configuration module library; a visualization module 300, used to obtain target physical specification information from the device baseline library based on the device list template determined by business requirements, and generate a business network topology based on the interconnection information determined by the target physical specification information; and a network device configuration module 400, used to determine the target configuration module in the configuration module library based on the business type identifier determined by the device list template, render the target configuration module to obtain a rendered configuration module, generate a target network configuration file based on the rendered configuration module and the business network topology, and configure based on the target network configuration file. Compared to the current manual configuration writing, this invention provides the ability to build and generate dumps of programmable configuration modules, realizing end-to-end automated conversion from business intent to device configuration. Through visual interaction, it can be customized, orchestrated, and extended as needed to adapt to different business scenarios, thereby improving configuration efficiency.

[0104] The following describes a network device configuration device provided by an embodiment of the present invention. The network device configuration device described below can be referred to in correspondence with the network device configuration method described above.

[0105] Please refer to Figure 6 , Figure 6 A schematic diagram of a network device configuration device provided in an embodiment of the present invention may include:

[0106] Memory 10 is used to store computer programs;

[0107] Processor 20 is used to execute computer programs to implement the network device configuration method described above.

[0108] The memory 10, processor 20, and communication interface 30 all communicate with each other through the communication bus 40.

[0109] In this embodiment of the invention, the memory 10 is used to store one or more programs. The programs may include program code, which includes computer operation instructions. In this embodiment of the invention, the memory 10 may store programs for implementing the following functions:

[0110] Predefine the physical specifications of heterogeneous network devices, classify the physical specifications of heterogeneous network devices based on business scenario requirements, and obtain a device baseline library;

[0111] Based on business scenarios, define business type identifiers, and classify and modularize configuration commands according to generality, personalization and feature-based coding, using device roles as the dimension, to obtain a configuration module library;

[0112] Based on the equipment list template, target physical specification information is obtained from the equipment baseline library, and the service network topology is generated based on the interconnection information determined by the target physical specification information.

[0113] The target configuration module in the configuration module library is determined based on the service type identifier determined by the device list template. The target configuration module is then rendered to obtain the rendered configuration module. Based on the rendered configuration module and the service network topology, a target network configuration file is generated, and configuration is performed based on the target network configuration file.

[0114] In one possible implementation, the memory 10 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and applications required for at least one function; and the data storage area may store data created during use.

[0115] Furthermore, memory 10 may include read-only memory and random access memory, providing instructions and data to the processor. A portion of the memory may also include NVRAM. The memory stores operating systems and operating instructions, executable modules, or data structures, or subsets thereof, or extended sets thereof, wherein the operating instructions may include various operating instructions for implementing various operations. The operating system may include various system programs for implementing various basic tasks and handling hardware-based tasks.

[0116] Processor 20 can be a central processing unit (CPU), an application-specific integrated circuit, a digital signal processor, a field-programmable gate array, or other programmable logic device. Processor 20 can be a microprocessor or any conventional processor. Processor 20 can call programs stored in memory 10.

[0117] The communication interface 30 can be an interface for the communication module, used to connect with other devices or systems.

[0118] Of course, it should be noted that, Figure 6 The structure shown does not constitute a limitation on the network device configuration device in the embodiments of the present invention. In practical applications, the network device configuration device may include more than Figure 6 More or fewer components as shown, or combinations of certain components.

[0119] The computer-readable storage medium provided in the embodiments of the present invention is described below. The computer-readable storage medium described below can be referred to in correspondence with the network device configuration method described above.

[0120] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the network device configuration method described above.

[0121] The computer-readable storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0122] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0123] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0124] Finally, it should be noted that in this document, relationships such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0125] The foregoing has provided a detailed description of a network device configuration method, apparatus, device, and readable storage medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A network device configuration method, characterized in that, include: Predefine the physical specifications of heterogeneous network devices, and classify the physical specifications of the heterogeneous network devices based on business scenario requirements to obtain a device baseline library; Based on business scenarios and equipment list information, define business type identifiers, and classify and modularize configuration commands according to generality, personalization and specialization, based on equipment roles, to obtain a configuration module library; Based on the equipment list template determined by business requirements, target physical specification information is obtained from the equipment baseline library, and the business network topology is generated based on the interconnection information determined by the target physical specification information. Based on the service type identifier determined by the device list template, the target configuration module in the configuration module library is determined, and the target configuration module is rendered to obtain the rendered configuration module. Based on the rendered configuration module and the service network topology, a target network configuration file is generated, and the target network configuration file is configured.

2. The network device configuration method according to claim 1, characterized in that, Based on business scenarios and equipment inventory information, business type identifiers are defined. Configuration commands are then categorized and modularized according to their generality, personalization, and specialization, using equipment roles as the dimension, resulting in a configuration module library, including: The configuration commands are decomposed according to their functions to form independent configuration modules; Assign each configuration module with encoding that includes business semantics; The configuration module and its encoding, as well as the predefined configuration identifiers within the module, are stored; wherein the configuration identifiers are used to be replaced by actual business parameters during configuration generation to achieve rendering parameter injection.

3. The network device configuration method according to claim 1, characterized in that, Predefined physical specifications of heterogeneous network devices, including: The physical specifications of the predefined heterogeneous network devices include the manufacturer, model, port type, and number of ports.

4. The network device configuration method according to any one of claims 1 to 3, characterized in that, Based on business scenarios and equipment inventory information, business type identifiers are defined. Configuration commands are then categorized and modularized according to their generality, personalization, and specialization, using equipment roles as the dimension, resulting in a configuration module library, including: Based on the standardization of configuration order, the modularization of configuration options, and the objectification of configuration parameters, the configuration commands are classified according to their generality, personalization, and characteristics. The standardized configuration order follows the basic logic of network configuration and is divided into element-level configuration, global-level configuration, and extended-level configuration. The configuration options are modularized based on the generality of business scenarios and are divided into general configuration, personalized configuration and feature-specific configuration. The configuration parameters are objectified and divided into pre-allocated parameters and variable parameters based on the business scenario.

5. The network device configuration method according to claim 1, characterized in that, Based on the equipment list template determined by business requirements, target physical specification information is obtained from the equipment baseline library, and based on the interconnection information determined by the target physical specification information, a business network topology is generated, including: The device list template is parsed using a one-center, three-view visualization orchestration component to obtain a visual interactive orchestration of device objects and device baselines; wherein, the one center is the configuration visualization orchestration center, and the three views are the device baseline view, configuration module view, and configuration code view in the device baseline library; Interconnection is achieved through visual orchestration of the device objects and device baselines, resulting in interconnection information, and the service network topology is generated based on the interconnection information.

6. The network device configuration method according to claim 1, characterized in that, Based on the service type identifier determined by the device list template, the target configuration module in the configuration module library is determined, and the target configuration module is rendered to obtain the rendered configuration module. A target network configuration file is then generated based on the rendered configuration module and the service network topology. Configuration is performed based on the target network configuration file, including: The target network configuration file generates a unique identifier based on the device manufacturer, service type identifier code, and device address.

7. The network device configuration method according to claim 1, characterized in that, Based on the service type identifier determined by the device list template, the target configuration module in the configuration module library is determined, and the target configuration module is rendered to obtain the rendered configuration module. A target network configuration file is then generated based on the rendered configuration module and the service network topology. Configuration is performed based on the target network configuration file, including: Based on the rendered configuration modules and the business network topology, the target network configuration file is generated by serialization and orchestration using preset construction rules; wherein, the preset construction rules are based on the network configuration logic of the equipment manufacturer and define the association relationship and generation order between each configuration module.

8. A network device configuration apparatus, characterized in that, include: The device baseline library construction module is used to predefine the physical specification information of heterogeneous network devices, classify the physical specification information of the heterogeneous network devices based on business scenario requirements, and obtain the device baseline library. The configuration module library is built by defining business type identifiers based on business scenarios and device list information, and classifying and modularizing configuration commands according to generality, personalization and feature-based coding based on device roles to obtain the configuration module library. The visualization module is used to obtain target physical specification information from the equipment baseline library based on the equipment list template determined by business requirements, and generate a business network topology based on the interconnection information determined by the target physical specification information. The network device configuration module is used to determine the target configuration module in the configuration module library based on the service type identifier determined by the device list template, render the target configuration module to obtain the rendered configuration module, generate a target network configuration file based on the rendered configuration module and the service network topology, and configure based on the target network configuration file.

9. A network device configuration device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the network device configuration method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the network device configuration method as described in any one of claims 1 to 7.

Images