Visual network equipment management method, device and processing system
By introducing container management technology into network device management, providing visual configuration interface and real-time configuration management, the inefficiency and compatibility problems under traditional management methods are solved, and efficient and unified management of network equipment of large enterprises is achieved.
Patent Information
- Application Number
- CN202411234553.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-04
- Publication Date
- 2024-12-13
AI Technical Summary
Traditional network equipment management methods are difficult to achieve efficient and unified management in large enterprises, resulting in inefficient configuration management and serious compatibility problems, which cannot meet the needs of rapid development of the Internet.
By combining container management technology, it provides a visual network device management method, including determining the target device in the network architecture, creating system image files, deploying it on the container management platform, displaying the visual configuration interface to the user, receiving and applying user configuration data, and realizing real-time Configuration management.
It significantly improves the convenience and compatibility of network equipment management, meets the high-quality configuration management needs of large-scale network equipment, and reduces operating costs and abnormal configuration risks.
Smart Images
Figure CN119135535A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network technology, and in particular to a visual network equipment management method, device and processing system. Background Art
[0002] With the development of the Internet, higher requirements are placed on network security. Among them, efficient management of network devices in the network architecture is an important part.
[0003] In this context, the traditional inefficient offline management mode of network equipment by equipment administrators can no longer meet the rapid development of the Internet. Especially in medium and large enterprises, how to efficiently and uniformly manage the network equipment of subordinate units or departments has become a major problem in actual situations. Summary of the invention
[0004] The present application provides a visual network device management method, apparatus and processing system for realizing a network device management mechanism with convenient system operation and significantly improved compatibility issues by combining container management technology, thereby meeting the high-quality configuration management requirements for large quantities of network devices.
[0005] In a first aspect, the present application provides a visual network device management method, the method comprising:
[0006] In the network architecture, determine the target network devices to be included in the visual network device management scope;
[0007] Create a system image file for the target network device;
[0008] Deploy the system image file on the preset container management platform;
[0009] The container management platform displays the corresponding visual configuration interface of the system image file during operation to the user end;
[0010] Receive network device configuration data entered by the user end for the visual configuration interface through the container management platform;
[0011] Configure network device configuration data for the local target network device and respond to the configuration management of the user end.
[0012] In conjunction with the first aspect of the present application, in a first possible implementation manner of the first aspect of the present application, determining a target network device to be included in the management scope of the visualized network device includes:
[0013] Determine the network equipment systems that are included in the visual network equipment management scope;
[0014] Based on the system source code of the network device system, deploy the network device system on the target network device;
[0015] Create a system image file for the target network device, including:
[0016] Based on the system source code of the network device system, create the system image file of the target network device.
[0017] In combination with the first aspect of the present application, in a second possible implementation manner of the first aspect of the present application, the method further includes:
[0018] Based on the Websocket link configured between the container management platform and the target network device, the container management platform receives the system information sent by the target network device.
[0019] Configure the real-time mapping relationship between the system image file and the target network device through system information.
[0020] In combination with the first aspect of the present application, in a third possible implementation manner of the first aspect of the present application, configuring network device configuration data for a local target network device includes:
[0021] Based on the RESTful API standard format, the network device configuration data is sent to the local target network device, so that the local target network device configures the network device configuration data.
[0022] In combination with the first aspect of the present application, in a fourth possible implementation manner of the first aspect of the present application, configuring network device configuration data for a local target network device includes:
[0023] The network device configuration data is configured for the local target network device and the first network device having the same system version as the target network device.
[0024] In combination with the first aspect of the present application, in a fifth possible implementation manner of the first aspect of the present application, configuring network device configuration data for a local target network device includes:
[0025] The network device configuration data is configured for the local target network device and the second network device specified by the network device configuration data.
[0026] In combination with the first aspect of the present application, in a sixth possible implementation manner of the first aspect of the present application, configuring network device configuration data for a local target network device includes:
[0027] The network device configuration data is configured for the local target network device and the third network device that is pre-configured with the target network device. The association relationship is used to indicate that all the network devices with the configured relationship are configured together when receiving the network device configuration data to be processed.
[0028] In a second aspect, the present application provides a visual network device management device, the device comprising:
[0029] A determination unit, used to determine, in the network architecture, a target network device to be included in the management scope of the visualized network device;
[0030] A production unit, used for producing a system image file of a target network device;
[0031] A deployment unit is used to deploy system image files on a preset container management platform;
[0032] A display unit is used to display the corresponding visual configuration interface of the system image file during operation to the user end through the container management platform;
[0033] A receiving unit, used to receive network device configuration data entered by a user terminal for a visual configuration interface through a container management platform;
[0034] The configuration unit is used to configure the network device configuration data for the local target network device and respond to the configuration management of the user end.
[0035] In conjunction with the second aspect of the present application, in a first possible implementation manner of the second aspect of the present application, the determining unit is specifically configured to:
[0036] Determine the network equipment systems that are included in the visual network equipment management scope;
[0037] Based on the system source code of the network device system, deploy the network device system on the target network device;
[0038] Production unit, specifically used for:
[0039] Based on the system source code of the network device system, create the system image file of the target network device.
[0040] In conjunction with the second aspect of the present application, in a second possible implementation manner of the second aspect of the present application, the configuration unit is further configured to:
[0041] Based on the Websocket link configured between the container management platform and the target network device, the container management platform receives the system information sent by the target network device.
[0042] Configure the real-time mapping relationship between the system image file and the target network device through system information.
[0043] In combination with the second aspect of the present application, in a third possible implementation manner of the second aspect of the present application, the configuration unit is specifically configured to:
[0044] Based on the RESTful API standard format, the network device configuration data is sent to the local target network device, so that the local target network device configures the network device configuration data.
[0045] In combination with the second aspect of the present application, in a fourth possible implementation manner of the second aspect of the present application, the configuration unit is specifically configured to:
[0046] The network device configuration data is configured for the local target network device and the first network device having the same system version as the target network device.
[0047] In combination with the second aspect of the present application, in a fifth possible implementation manner of the second aspect of the present application, the configuration unit is specifically configured to:
[0048] The network device configuration data is configured for the local target network device and the second network device specified by the network device configuration data.
[0049] In combination with the second aspect of the present application, in a sixth possible implementation manner of the second aspect of the present application, the configuration unit is specifically configured to:
[0050] The network device configuration data is configured for the local target network device and the third network device that is pre-configured with the target network device. The association relationship is used to indicate that all the network devices with the configured relationship are configured together when receiving the network device configuration data to be processed.
[0051] In a third aspect, the present application provides a processing system including a processor and a memory, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the method provided in the first aspect of the present application or any possible implementation method of the first aspect of the present application is executed.
[0052] In a fourth aspect, the present application provides a computer-readable storage medium, which stores multiple instructions, and the instructions are suitable for a processor to load to execute the method provided by the first aspect of the present application or any possible implementation of the first aspect of the present application.
[0053] From the above content, it can be concluded that the present application has the following beneficial effects:
[0054] In response to the needs of network device configuration management, this application, in the network architecture, determines the target network devices to be included in the scope of visual network device management, creates a system image file for the target network device, and deploys the system image file on a preset container management platform. Then, the corresponding visual configuration interface of the system image file during operation is displayed to the user end, and the network device configuration data entered by the user end for the visual configuration interface is received. At this time, the network device configuration data is configured for the local target network device, and the configuration management of the user end is responded to. In this processing process, by combining container management technology, a network device management mechanism with convenient system operation and significantly improved compatibility issues is realized, which can meet the high-quality configuration management needs for large quantities of network devices. BRIEF DESCRIPTION OF THE DRAWINGS
[0055] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0056] Figure 1 A flowchart of a visual network device management method of the present application;
[0057] Figure 2 A schematic diagram of a scenario for an application example of this application;
[0058] Figure 3 A structural diagram of a visual network device management device of the present application;
[0059] Figure 4 A structural diagram of the application processing system. DETAILED DESCRIPTION
[0060] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0061] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than that illustrated or described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or modules is not necessarily limited to those steps or modules clearly listed, but may include other steps or modules that are not clearly listed or inherent to these processes, methods, products or devices. The naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time / logical sequence indicated by the naming or numbering. The process steps that have been named or numbered can change the execution order according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved.
[0062] The division of modules in this application is a logical division. There may be other division methods when it is implemented in actual applications. For example, multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection between modules can be electrical or other similar forms, which are not limited in this application. In addition, the modules or submodules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in multiple circuit modules, and some or all of the modules may be selected according to actual needs to achieve the purpose of the present application.
[0063] Before introducing the visualized network device management method provided by the present application, the background content involved in the present application is first introduced.
[0064] The visual network device management method, apparatus, and computer-readable storage medium provided in the present application can be applied to a processing system to implement a network device management mechanism with convenient system operation and significantly improved compatibility issues by combining container management technology, thereby meeting the high-quality configuration management requirements for large quantities of network devices.
[0065] The visualization network device management method mentioned in the present application may be executed by a visualization network device management device, or a processing system integrating the visualization network device management device. The processing system may be understood to be a device node in the network architecture that is specifically responsible for the visualization network device management work involved in the present application, or a device node in the network architecture that is also responsible for the visualization network device management work involved in the present application on the basis of the original work. In addition, the processing system may directly include at least one of the network device, container management platform and user terminal involved in the solution of the present application. Therefore, it can be seen that the specific device structure and specific device deployment form of the processing system are relatively flexible, and the present application does not make specific limitations, among which:
[0066] The visual network equipment management device can be implemented in hardware or software;
[0067] The network device may specifically be a firewall, a gateway, an intrusion prevention system (IPS), an intrusion detection system (IDS), and other different types of device nodes that are responsible for the responsibilities of network devices in the network architecture;
[0068] The container management platform can be specifically installed on the original device nodes or newly deployed device nodes in the network architecture, which can be implemented through container management services such as Docker. For the container management platform, in this application scheme, it is not important what type of existing container management service is used. The focus is on the new work responsibilities / logic planned for it by this application scheme. Of course, it is also possible to use improved or even self-developed container management services;
[0069] The user end can be different types of devices such as a server, a physical host or a user equipment (UE), among which the UE can specifically be a terminal device such as a smart phone, a tablet computer, a laptop computer, a desktop computer or a personal digital assistant (PDA). It can be seen here that the specific device of the user end is relatively flexible, and the key point is that it can realize the visualization operations involved in the solution of the present application. In other words, any device that can realize the visualization operations involved in the present application on the user side can be used as a user end.
[0070] Next, we will introduce the visual network device management method provided by this application.
[0071] First, see Figure 1 , Figure 1A flow chart of a visualized network device management method of the present application is shown. The visualized network device management method provided by the present application may specifically include the following steps S101 to S106:
[0072] Step S101, in the network architecture, determining a target network device to be included in the management scope of the visualized network device;
[0073] It is easy to understand that during the implementation of the solution, it involves the determination and processing of the network device that is currently to be visually managed. This network device is one of the many network devices that need to be managed in the network architecture. For the sake of convenience, it can be recorded as the target network device.
[0074] It can be understood that the network devices included in the visualization network device management scope can itself be equivalent to the determination and processing of the target network devices, that is, whichever network device is currently included in the visualization network device management scope can be identified as the target network device for processing according to the present application scheme, or, the target network device to be processed currently can be determined among the network devices included in the visualization network device management scope. Both situations are possible and can be configured according to actual needs.
[0075] Among them, the determination of the target network device is usually carried out along with the initiation of the accompanying processing task. It can be either manually operated or autonomously determined by the system according to a preset determination strategy. For example, the network device that is newly added to the network architecture / newly online can be determined as the target network device. For example, the network device that is detected to have frequent update / maintenance needs can be determined as the target network device.
[0076] It is understandable that in the network architecture, the network equipment itself has configuration requirements (specifically corresponding to the configuration requirements for the deployment of new equipment and the update and maintenance of existing equipment). Therefore, how to determine or select the network equipment that needs to be configured can itself be considered to be within the scope of the prior art. Of course, it is not ruled out that in actual situations, a more novel target network equipment determination mechanism may be involved, which corresponds to some more detailed or special application requirements in actual situations.
[0077] Step S102, creating a system image file of the target network device;
[0078] It can be understood that the present application involves the application of a container management platform, and considers deploying the target network device to be configured and managed in a container on the container management platform for operation for subsequent configuration management.
[0079] In this regard, a system image file of the target network device, which is the processing target, can be created for deployment on the container management platform side.
[0080] Step S103, deploying the system image file on a preset container management platform;
[0081] It can be understood that after the system image file of the target network device is obtained, it can be deployed on the container management platform.
[0082] Among them, it should be noted that the processing object for executing the production process of the system image file of the target network device can be the target network device itself, other devices, or the container management platform. This can be adjusted according to the actual situation. If it is done by a device other than the container management platform, it is obviously necessary to involve the transmission process of the system image file.
[0083] As an example, the present application can specifically use the Docker product to build the container management platform involved in the present application. For the Docker product, the corresponding system image file can be referred to as the Docker image. The Docker image is a read-only template for creating a Docker container, which contains all the content required to run the application, including code, runtime environment, libraries, environment variables, and configuration files.
[0084] A Docker container is a running instance of an image that contains an application and all its dependencies to isolate the application and its environment, ensuring that it runs consistently in any environment.
[0085] Regarding the production and processing of Docker images, it is understandable that each network device has its own system version, which is compiled from the source code of the network device and has very complete functions, including interface display, traffic forwarding, traffic auditing and many other functions.
[0086] The Docker service can run multiple containers at the same time. A Docker service can support multiple system versions of network devices. It compiles and provides corresponding Docker images according to the required or existing system versions and runs them. The system with the same interface as the network device after running is called a container.
[0087] Step S104, displaying the corresponding visual configuration interface of the system image file during operation to the user terminal;
[0088] The system image file of the target network device is deployed on the container management platform. The operation status of the system image file can replace the operation status of the target network device itself in the configuration management of the target network device, and provide a corresponding visual configuration interface for the user to process the corresponding configuration data required for configuration management through visual operations.
[0089] In this regard, the container management platform needs to display the corresponding visual configuration interface of the system image file during operation to the user end.
[0090] It can be understood here that the container management platform itself has human-computer interaction functions so that users or staff can manage the deployed related application services (the system image file of the target network device is one of the application service methods). In this way, the container management platform can send the relevant data required to display the visual configuration interface through the pre-registered / configured user terminal that has a corresponding relationship with the target network device, so as to achieve the effect of displaying the visual configuration interface to the user terminal.
[0091] Among them, the visual configuration interface is easy to understand. Its interface content includes the relevant items that can be configured for the target network device and the currently entered configuration content. It also provides an operation entrance for users to enter configuration data. For example, it may involve interface elements such as selection buttons, input boxes, or voice input buttons. In this way, users can conveniently enter the corresponding device configuration data based on the content presented on the visual configuration interface.
[0092] The display of the visual configuration interface to the user end can be completed by the container management platform itself or by the device part outside the container management platform.
[0093] Step S105, receiving network device configuration data entered by the user terminal for the visual configuration interface;
[0094] In this way, after the visual configuration interface is displayed to the user, the user can provide feedback. In this way, the displayer of the visual configuration interface (the container management platform itself or the device part outside) can receive the network device configuration data entered by the user for the visual configuration interface.
[0095] Step S106, configuring the network device configuration data for the local target network device, and responding to the configuration management of the user end.
[0096] After receiving the network device configuration data required for the configuration management of the target network device, deployment can be performed to achieve the effect of updating the configuration.
[0097] It should be noted that the configuration processing based on the network device configuration data is specifically carried out on the local target network device, rather than on the container on the container management platform. In other words, the system image file (the image of the target network device) running through the container will not be configured based on the network device configuration data.
[0098] It can be seen that this application is not concerned with the conventional container management application mechanism of conveniently running the target network device on the container management platform to provide corresponding functional services. The application of the container management platform in this application focuses on providing a convenient visual configuration interface through the container management platform.
[0099] If the container management platform is not used and the corresponding visual configuration interface is provided directly based on the local target network device, this processing method may cause configuration compatibility problems due to inconsistent network device versions. This will obviously likely cause additional operating costs (including manual operating costs) and may also cause abnormal configuration situations, which is not conducive to the configuration management of large quantities of network devices involved in the enterprise.
[0100] Under the scheme setting of the present application, a visual configuration interface is provided through a container management platform. For the user side, it can be guaranteed that what the user sees is a configuration interface that is exactly the same as or highly adapted to the target network device, and there will be no compatibility issues caused by version mismatches, thereby avoiding additional operating costs and abnormal configuration situations like the prior art, and helping to promote the configuration management of large quantities of network devices involved in the enterprise to be carried out conveniently and efficiently.
[0101] While or after configuring the network device configuration data for the local target network device, you can either shut down / stop the deployment / operation of the system image file on the container management platform, or you can allow the container management platform to continue to allow the originally deployed system image file without updating the system image file, and provide the same visual configuration interface as the original one for the user to initiate a new configuration management process, or you can create a new system image file and update it to the container management platform based on the configuration update status of the target network device.
[0102] from Figure 1It can be seen from the illustrated embodiments that, in response to the network device configuration management requirements, the present application, in the network architecture, after determining the target network device to be included in the visual network device management scope, creates a system image file for the target network device, and deploys the system image file on a preset container management platform. The corresponding visual configuration interface of the system image file during operation is then displayed to the user terminal, and the network device configuration data entered by the user terminal for the visual configuration interface is received. At this time, the network device configuration data is configured for the local target network device, and the configuration management of the user terminal is responded to. In this processing process, by combining the container management technology, a network device management mechanism with convenient system operation and significantly improved compatibility issues is implemented, which can meet the high-quality configuration management requirements for large quantities of network devices.
[0103] Continue to the above Figure 1 Each step of the illustrated embodiment and possible embodiments thereof in practical application are explained in detail.
[0104] As an exemplary embodiment, the process of determining the target network device to be included in the management scope of the visualized network device in the previous step S101 may specifically include:
[0105] Determine the network equipment systems that are included in the visual network equipment management scope;
[0106] Based on the system source code of the network device system, the network device system is deployed on the target network device.
[0107] It can be seen that in the embodiment here, the determination process of the target network device is equivalent to executing the deployment process of a new network device this time, and is specifically carried out based on the system source code of the corresponding network device system.
[0108] In this case, step S102 of making a system image file of the target network device may include:
[0109] Based on the system source code of the network device system, create the system image file of the target network device.
[0110] It can be seen that the processing of the system image file corresponds to the deployment of the target network device above, and can also be carried out based on the system source code of its network device system.
[0111] Furthermore, as mentioned above, the container management technology introduced in the present application is not to deploy the target network device on the container management platform side to conveniently provide the application services that the target network device can provide as in the prior art, but to conveniently provide a highly compatible visual configuration interface through the container management platform, so as to conveniently and accurately obtain the network device configuration data. In this regard, the present application can also simplify the system image file, thereby further reducing the operating cost and improving the operating efficiency.
[0112] Specifically, the present application can only extract the configuration layer of the target network device (the configuration content involved in the visual configuration), and the compilation result can be controlled by the compilation macro. Based on the system source code, a streamlined network device system with only configuration functions can be compiled, and deployed and run in the service environment of the container management platform.
[0113] At the same time, in actual situations, this setting is obviously more conducive to the application of the present application solution to the visual configuration processing of large quantities of network devices.
[0114] Furthermore, in order to continue to enhance the effect of the above-mentioned solution, it is understandable that the configuration content can be further simplified to obtain a more streamlined system image file, and the scope can be further narrowed from all the configuration content that can be involved originally, so that the content processing is more streamlined and the operating cost is lower. At the same time, it also helps users on the user side to enter network device configuration data more concisely and clearly.
[0115] For example, the system image file can be configured according to a given / specified local configuration range; for another example, the system image file can be configured according to the corresponding local configuration range determined according to user permissions; for another example, the configuration requirements of the user side can be predicted based on at least one influencing factor such as the system situation of the target network device, current application requirements, and user configuration habits, so as to determine the corresponding local configuration range and configure the system image file. Obviously, these operations can achieve a more refined configuration content adjustment effect at the detail level, which can effectively reduce the system operating cost and promote higher processing efficiency and processing accuracy.
[0116] In addition, as an exemplary embodiment, the present application may specifically adopt a Websocket link between the target network device and the container management platform.
[0117] Among them, Websocket is a protocol for full-duplex communication on a single TCP connection. It can be used for security verification and as a management channel to ensure the security of configuration and network devices. The network device initiates the connection and establishes a Websocket link with the container management platform (server). This is the basis for configuring the client (network device) on the container management platform side.
[0118] First, the network device registers with the container management platform and sends verification information. If the verification passes, the Uniform Resource Locator (URL) of the Websocket link will be returned. When the network device successfully establishes a link with the container management platform using the URL, the container management platform can manage the device. After the link is successful, the network device needs to send its own system information (including important information such as the system version) to bind the system image file to the network device.
[0119] In this case, the present application method may also include:
[0120] Based on the Websocket link configured between the container management platform and the target network device, the container management platform receives the system information sent by the target network device.
[0121] Configure the real-time mapping relationship between the system image file and the target network device through system information.
[0122] As for the data format between the container management platform and the target network device, this application also provides a specific implementation solution.
[0123] As an exemplary embodiment, the RESTful API standard format can be used to transmit data between the two. The RESTful API standard format can be understood as an architecture style of an application programming interface (API) that uses HTTP requests to access or use data. It can be parsed using an XML interpreter and is more versatile.
[0124] In this case, step S106 configures the network device configuration data for the local target network device, which may include:
[0125] Based on the RESTful API standard format, the network device configuration data is sent to the local target network device, so that the local target network device configures the network device configuration data.
[0126] Next, we will use a set of application examples of the container management platform to provide a more vivid understanding of the above solutions.
[0127] For the container management platform side (which itself can be considered as the server or under the control of the server), when it manages (including deployment and operation) the system image files of many network devices, all network devices with the same system version can be managed in a unified manner. Of course, if there are different system versions, a small number of devices with the same version can be managed in a unified manner in the form of subdivided groups.
[0128] 1. Assume that there are 500 network devices with system version A, 100 with version B, and 10 with version C;
[0129] 2. Each device successfully establishes a Websocket link on the container management platform and successfully reports its own system version information;
[0130] 3. Create group A-1 on the container management platform, including 100 devices of version A;
[0131] 4. Associate group A-1 with version A container on the container management platform. Open version A container, operate the container, and perform configuration addition, deletion, modification, and query. Note that the operations here are all operations on containers, but the interface is exactly the same as or highly adapted to the local network device. After each configuration data submission, the network device configuration data in the Restful API format will be generated and then sent to the associated network device through the Websocket channel. When the network is good, the configuration action will take effect in real time, greatly improving efficiency.
[0132] 5. For different versions, you can set different groups and then associate the corresponding containers, so the B and C systems can be operated similarly. For the system type D to be deployed, you only need to deploy the compiled D system image on the container management platform side in advance.
[0133] 6. After receiving the data, the network device parses it through the XML parser and finally takes effect.
[0134] Specifically, you can also combine Figure 2 A scenario diagram of an application example of the present application is shown for a more vivid understanding.
[0135] In addition, from the above application examples, it can be seen that each network device configuration work can be initiated not only for a local target network device, but also for multiple network devices including the target network device, so as to achieve batch network device configuration management effect and further improve convenience and configuration efficiency.
[0136] In this regard, as exemplary embodiments, the present application provides three different batch configuration schemes to correspond to specific application requirements in different actual situations.
[0137] 1. Configuring network device configuration data for the local target network device may include:
[0138] The network device configuration data is configured for the local target network device and the first network device having the same system version as the target network device.
[0139] It can be seen that for network devices with the same system version, when configuration management is initiated for a target network device therein, configuration synchronization can be conveniently performed between these network devices.
[0140] 2. Configuring network device configuration data for the local target network device may also include:
[0141] The network device configuration data is configured for the local target network device and the second network device specified by the network device configuration data.
[0142] It can be seen that for network devices of different system versions, the same configuration synchronization operation may be adopted in some cases, or for network devices of the same version, the same configuration synchronization operation may not be adopted in some cases.
[0143] In this regard, when initiating configuration management for a target network device, the network devices that need to be synchronized with the configuration can be specified to conveniently synchronize the configurations between these network devices.
[0144] 3. Configuring network device configuration data for the local target network device may also include:
[0145] The network device configuration data is configured for the local target network device and the third network device that is pre-configured with the target network device. The association relationship is used to indicate that all the network devices with the configured relationship are configured together when receiving the network device configuration data to be processed.
[0146] It can be seen that for network devices of different system versions, the same configuration synchronization operation may be adopted in some cases, or for network devices of the same version, the same configuration synchronization operation may not be adopted in some cases.
[0147] In this regard, when initiating configuration management for a target network device, configuration synchronization can be conveniently performed between these network devices according to the pre-configured association relationship (network devices with an association relationship perform configuration synchronization operations when configuration management is initiated on a certain network device).
[0148] It can be seen that the above three implementation schemes provide three configuration synchronization schemes to provide three configuration synchronization application scenarios that are not passed, making the application scheme more specific and having better application value in practical applications.
[0149] The above is an introduction to the visualized network device management method provided by the present application. To facilitate better implementation of the visualized network device management method provided by the present application, the present application also provides a visualized network device management apparatus from the perspective of functional modules.
[0150] See also Figure 3 , Figure 3 This is a structural diagram of a visual network device management device of the present application. In the present application, the visual network device management device 300 may specifically include the following structure:
[0151] A determination unit 301 is used to determine, in the network architecture, a target network device to be included in the management scope of the visualized network device;
[0152] A production unit 302, used to produce a system image file of a target network device;
[0153] A deployment unit 303 is used to deploy a system image file on a preset container management platform;
[0154] A display unit 304 is used to display a corresponding visual configuration interface of the system image file during operation to the user terminal through the container management platform;
[0155] The receiving unit 305 is used to receive the network device configuration data entered by the user terminal for the visual configuration interface through the container management platform;
[0156] The configuration unit 306 is used to configure the network device configuration data for the local target network device and respond to the configuration management of the user end.
[0157] In an exemplary embodiment, the determining unit 301 is specifically configured to:
[0158] Determine the network equipment systems that are included in the visual network equipment management scope;
[0159] Based on the system source code of the network device system, deploy the network device system on the target network device;
[0160] The production unit 302 is specifically used for:
[0161] Based on the system source code of the network device system, create the system image file of the target network device.
[0162] In another exemplary embodiment, the configuration unit 306 is further configured to:
[0163] Based on the Websocket link configured between the container management platform and the target network device, the container management platform receives the system information sent by the target network device.
[0164] Configure the real-time mapping relationship between the system image file and the target network device through system information.
[0165] In another exemplary embodiment, the configuration unit 306 is specifically configured to:
[0166] Based on the RESTful API standard format, the network device configuration data is sent to the local target network device, so that the local target network device configures the network device configuration data.
[0167] In another exemplary embodiment, the configuration unit 306 is specifically configured to:
[0168] The network device configuration data is configured for the local target network device and the first network device having the same system version as the target network device.
[0169] In another exemplary embodiment, the configuration unit 306 is specifically configured to:
[0170] The network device configuration data is configured for the local target network device and the second network device specified by the network device configuration data.
[0171] In another exemplary embodiment, the configuration unit 306 is specifically configured to:
[0172] The network device configuration data is configured for the local target network device and the third network device that is pre-configured with the target network device. The association relationship is used to indicate that all the network devices with the configured relationship are configured together when receiving the network device configuration data to be processed.
[0173] This application also provides a processing system from the perspective of hardware structure. Regardless of its specific device composition structure, it is regarded as a hardware device. Figure 4 , Figure 4 401, a computer program stored in the memory 402, and an input / output device 403. The processor 401 is used to execute the computer program stored in the memory 402. Figure 1 The steps of the visual network device management method in the corresponding embodiment; or, the processor 401 is used to execute the computer program stored in the memory 402 to implement the following Figure 3 Corresponding to the functions of each unit in the embodiment, the memory 402 is used to store the processor 401 executing the above Figure 1The computer program required by the visual network device management method in the corresponding embodiment.
[0174] Exemplarily, the computer program may be divided into one or more modules / units, one or more modules / units are stored in the memory 402, and executed by the processor 401 to complete the present application. One or more modules / units may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the computer device.
[0175] The processing system may include, but is not limited to, the processor 401, the memory 402, and the input / output device 403. Those skilled in the art will appreciate that the illustration is merely an example of the processing system and does not constitute a limitation on the processing system, and may include more or fewer components than shown in the illustration, or a combination of certain components, or different components. For example, the processing system may also include a network access device, a bus, etc., and the processor 401, the memory 402, the input / output device 403, etc. are connected via the bus.
[0176] The processor 401 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the processing system, and uses various interfaces and lines to connect various parts of the entire device.
[0177] The memory 402 can be used to store computer programs and / or modules. The processor 401 implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory 402 and calling the data stored in the memory 402. The memory 402 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created according to the use of the processing system, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.
[0178] When the processor 401 is used to execute the computer program stored in the memory 402, the following functions can be implemented:
[0179] In the network architecture, determine the target network devices to be included in the visual network device management scope;
[0180] Create a system image file for the target network device;
[0181] Deploy the system image file on the preset container management platform;
[0182] Display the corresponding visual configuration interface of the system image file during operation to the user end;
[0183] Receive network device configuration data entered by the user end for the visual configuration interface;
[0184] Configure network device configuration data for the local target network device and respond to the configuration management of the user end.
[0185] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described visual network device management device, processing system and its corresponding units can refer to the following. Figure 1 The description of the visual network device management method in the corresponding embodiment will not be repeated here in detail.
[0186] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0187] To this end, the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the present application as follows: Figure 1 For the steps of the visual network device management method in the corresponding embodiment, the specific operations can be referred to as follows Figure 1 The description of the visual network device management method in the corresponding embodiment will not be repeated here.
[0188] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0189] Due to the instructions stored in the computer-readable storage medium, the present application can be executed. Figure 1 The steps of the visual network device management method in the corresponding embodiment, therefore, the present application can be implemented as follows Figure 1 The beneficial effects that can be achieved by the visual network device management method in the corresponding embodiment are detailed in the previous description and will not be repeated here.
[0190] The above is a detailed introduction to the visual network device management method, device, processing system and computer-readable storage medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A visual network device management method, characterized in that: The method comprises: In the network architecture, determine the target network devices to be included in the visual network device management scope; Creating a system image file of the target network device; Deploy the system image file on a preset container management platform; Displaying the corresponding visual configuration interface of the system image file during operation to the user terminal through the container management platform; Receiving, through the container management platform, network device configuration data entered by the user terminal for the visual configuration interface; The network device configuration data is configured for the local target network device in response to the configuration management of the user end.
2. The method according to claim 1, characterized in that: The target network devices to be included in the management scope of the visualized network devices include: Determine the network device systems included in the visual network device management scope; Deploying the network device system on the target network device based on the system source code of the network device system; The step of making the system image file of the target network device comprises: Based on the system source code of the network device system, the system image file of the target network device is produced.
3. The method according to claim 1, characterized in that The method further comprises: Based on the Websocket link configured between the container management platform and the target network device, the container management platform receives the system information sent by the target network device, A real-time mapping relationship between the system image file and the target network device is configured through the system information.
4. The method according to claim 1, characterized in that: The configuring the network device configuration data for the local target network device includes: Based on the Restful API standard format, the network device configuration data is sent to the local target network device, so that the local target network device configures the network device configuration data.
5. The method according to claim 1, characterized in that The configuring the network device configuration data for the local target network device includes: The network device configuration data is configured for the local target network device and a first network device having the same system version as the target network device.
6. The method according to claim 1, characterized in that The configuring the network device configuration data for the local target network device includes: The network device configuration data is configured for the local target network device and the second network device specified by the network device configuration data.
7. The method according to claim 1, characterized in that The configuring the network device configuration data for the local target network device includes: The network device configuration data is configured for the local target network device and for a third network device that is pre-configured with the target network device. The association relationship is used to indicate that all network devices with the configured relationship are to be configured together when receiving the network device configuration data to be processed.
8. A visual network device management device, characterized in that: The device comprises: A determination unit, used to determine, in the network architecture, a target network device to be included in the management scope of the visualized network device; A production unit, used for producing a system image file of the target network device; A deployment unit, used to deploy the system image file on a preset container management platform; A display unit, used to display the corresponding visual configuration interface of the system image file during operation to the user terminal through the container management platform; A receiving unit, configured to receive, through the container management platform, network device configuration data entered by the user terminal for the visual configuration interface; The configuration unit is used to configure the network device configuration data for the local target network device and respond to the configuration management of the user end.
9. A processing system, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program, and the processor executes the method according to any one of claims 1 to 7 when calling the computer program in the memory.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the method according to any one of claims 1 to 7.