State determination method, computer equipment and storage medium

Abstract

The invention relates to a state determination method, computer equipment and a storage medium, which are used for solving the problem that the state of equipment in a ZTP process is difficult to determine. The method comprises the following steps: acquiring monitoring information of a target deployment progress in a zero configuration deployment task execution process corresponding to network element equipment; determining state information of the target deployment progress according to the monitoring information; the state information is used for indicating the execution condition of the target deployment progress.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technologies, and in particular, to a method for determining a state, a computer device, and a storage medium. Background Art

[0002] Currently, through the zero touch provisioning (ZTP) technology, the initial configuration of a large number of devices can be efficiently implemented.

[0003] However, most of the process of initial configuration of devices using the ZTP technology is performed on the device side, and it is difficult for the management side to determine the state of the device during the ZTP process, resulting in the inability to timely maintain the device and handle faults, etc. Summary of the Invention

[0004] Embodiments of the present application provide a method for determining a state, a computer device, and a storage medium, which are used to solve the problem of difficultly determining the state of a device during the ZTP process.

[0005] On the one hand, a method for determining a state is provided, including:

[0006] Obtaining monitoring information of a target deployment progress during the execution of a zero touch deployment task corresponding to a network element device;

[0007] Determining state information of the target deployment progress according to the monitoring information; the state information is used to indicate the execution situation of the target deployment progress.

[0008] On the other hand, a state determination device is provided, including: an obtaining module and a processing module;

[0009] The obtaining module is used to obtain monitoring information of a target deployment progress during the execution of a zero touch deployment task corresponding to a network element device;

[0010] The processing module is used to determine state information of the target deployment progress according to the monitoring information; the state information is used to indicate the execution situation of the target deployment progress.

[0011] On yet another hand, a computer device is provided, including: a memory and a processor; the memory and the processor are coupled; the memory is used to store instructions executable by the processor; when the processor executes the instructions, the method for determining a state described in any of the above embodiments is implemented.

[0012] On yet another hand, a computer-readable storage medium is provided, on which computer instructions are stored. When the computer instructions run on a computer, the computer implements the method for determining a state described in any of the above embodiments.

[0013] In another aspect, a computer program product is provided, which includes computer program instructions that, when executed by a processor, implement the state determination method described in any of the above embodiments.

[0014] In an embodiment of the present application, a computer device may obtain monitoring information on the target deployment progress during the execution of the zero-configuration deployment task corresponding to the network element device. Wherein, the target deployment progress may be the progress currently being executed by the zero-configuration deployment task. That is, the computer device may monitor the information on the progress executed by the network element device during the ZTP process, so as to determine the current progress of the network element device during the deployment process, and whether there are any abnormalities at the current progress. Furthermore, the computer device may determine the status information of the target deployment progress, that is, the execution situation of the target deployment progress, based on the monitoring information, thereby perceiving the status of the network element device during the deployment process.

[0015] Based on this, the present application can determine the execution situation of the network element device at the target deployment progress by monitoring the execution progress of the zero-configuration deployment task of the network element device, and realize the perception of the status of the network element device during the deployment process. Therefore, the present application can be used to solve the problem of difficulty in determining the status of a device during the ZTP process. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the present application, the following will briefly introduce the drawings required to be used in some embodiments of the present application. Obviously, the drawings described below are only the drawings of some embodiments of the present application, and those of ordinary skill in the art can also obtain other drawings based on these drawings.

[0017] Figure 1 A schematic structural diagram of a networking system provided in some embodiments of the present application;

[0018] Figure 2 A schematic structural diagram of a state determination system provided in some embodiments of the present application;

[0019] Figure 3 A schematic structural diagram of another state determination system provided in some embodiments of the present application;

[0020] Figure 4 A schematic flowchart of a state determination method provided in some embodiments of the present application;

[0021] Figure 5 A schematic structural diagram of a log file information provided in some embodiments of the present application;

[0022] Figure 6 A schematic diagram of a task management interface provided in some embodiments of the present application;

[0023] Figure 7 A schematic flowchart of another method for determining a state provided by some embodiments of the present application;

[0024] Figure 8 A schematic flowchart of another method for determining a state provided by some embodiments of the present application;

[0025] Figure 9 A schematic structural diagram of a state determination device provided by some embodiments of the present application;

[0026] Figure 10 A schematic structural diagram of a computer device provided by some embodiments of the present application. Detailed implementation manners

[0027] Next, the technical solutions in the present application will be clearly and completely described in conjunction with the accompanying drawings in the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0028] It should be noted that in the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0029] Hereinafter, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include one or more of such features.

[0030] In the description of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. The "and / or" herein is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, "at least one" means one or more, and "a plurality" means two or more.

[0031] Newly built data centers often have a large number of connected switches. Manually configuring these devices at deployment time is prone to configuration errors, which are difficult to pinpoint, leading to delays in data center service rollouts. When expanding data centers, manual configuration can also impact existing services due to improper configuration.

[0032] To avoid the aforementioned issues associated with manual large-scale deployment, ZTP technology can be used, eliminating the need for on-site personnel to debug device software. With ZTP, after powering on, the device can function as a Dynamic Host Configuration Protocol (DHCP) client, exchanging DHCP messages with a DHCP server to obtain a temporary address during the ZTP process.

[0033] Furthermore, the device can obtain resource files such as configuration files and software packages from the file server based on the obtained temporary address, and complete automatic startup configuration after restarting and loading the configuration file, thereby realizing batch and automatic distribution of device programs and device startup files to switches, optimizing the device startup configuration process, accelerating the speed of service launch, improving the efficiency of device deployment, daily maintenance and troubleshooting, and reducing labor costs.

[0034] However, when using ZTP technology for device deployment, most of the process is performed on the device side, and staff cannot perceive the status of the device during deployment in real time. If errors occur during deployment, staff generally need to check the device log to locate the cause.

[0035] In order to solve the problem of difficulty in determining the status of a device during the ZTP process, an embodiment of the present application proposes a status determination method, in which a computer device can obtain monitoring information of the target deployment progress during the execution of a zero-configuration deployment task corresponding to a network element device. The target deployment progress can be the progress currently being executed by the zero-configuration deployment task. That is, the computer device can monitor the information of the progress executed by the network element device during the ZTP process, so as to determine the current progress of the network element device during the deployment process, and whether there are any abnormalities in the current progress. Furthermore, the computer device can determine the status information of the target deployment progress, that is, the execution status of the target deployment progress, based on the monitoring information, thereby perceiving the status of the network element device during the deployment process.

[0036] Based on this, this application can monitor the progress of the zero-touch deployment task of the network element device to determine the execution status of the network element device at the target deployment progress, thereby realizing the perception of the status of the network element device during the deployment process. Therefore, this application can be used to solve the problem of difficulty in determining the status of the device during the ZTP process.

[0037] In some embodiments of the present application, the status determination method can be applied to a computer device in a status determination system. The status determination system provided in the embodiments of the present application will be described below.

[0038] In some embodiments of the present application, the status determination system can be built based on a networking system that applies the ZTP technology. As Figure 1 shown, it is a schematic structural diagram of a networking system 100 provided in an embodiment of the present application. The networking system 100 may include network element devices, a DHCP relay, a DHCP server, a DNS server, an intermediate file server, a version file server, a zero-deployment microservice, and a network management device controlled by a user.

[0039] Figure 1 The DHCP server in can be used to allocate information such as a temporary management Internet Protocol (IP) address, a default gateway, a Domain Name System (DNS) server address, and an intermediate file server address to the network element devices. The DHCP server can also send the allocated device address information, that is, the temporary management IP address allocated to the network element devices, to the zero-deployment microservice.

[0040] The DHCP relay can forward the DHCP packets exchanged between the network element devices in different network segments and the DHCP server.

[0041] The intermediate file server can be used to save the intermediate files required by the network element devices during the ZTP process. The intermediate files can include information such as the version file server address and version files. The type of the intermediate file can be in the initialization (INI) file format. The intermediate file server can be a File Transfer Protocol (FTP) server or a Secure File Transfer Protocol (SFTP) server.

[0042] The version file server can be used to store the version files required by the network element devices, such as system software, configuration files, and patch files. The version file server can be deployed on the same file server as the intermediate file server, or it can be an FTP server or an SFTP server.

[0043] The DNS server can be used to provide the mapping relationship between domain names and IP addresses. The network element devices can resolve the domain names of the intermediate file server or the version file server into IP addresses through the DNS server, so as to obtain the required files from the intermediate file server or the version file server.

[0044] Users can control the network management device to configure intermediate files and configuration files in the intermediate file server through zero-deployment microservices, and configure version files in the version file server, etc.

[0045] The zero-deployment microservice can be used to send zero-configuration deployment tasks to network element devices and monitor the execution status of zero-configuration deployment tasks at each execution progress. The zero-deployment microservice can include a task management module, a device attribute configuration module, a status monitoring module, a network element management module, etc., and can be deployed in the network management device.

[0046] Among them, the task management module can manage the ZTP execution process of network element devices in a task manner. For example, the task management module can create multiple ZTP tasks corresponding one-to-one with multiple network element devices to manage the progress of each network element device in the ZTP process through one ZTP task. For example, the progress such as address request and address selection during the temporary address allocation process, and the progress such as downloading configuration files and loading configuration files during the zero-deployment process.

[0047] The status monitoring module can be used to monitor the information of each progress of network element devices during the ZTP process. For example, the information of DHCP packets during the temporary address allocation process, and the log information such as the network element device downloading configuration files and loading configuration files during the zero-deployment process.

[0048] The device attribute configuration module can be used to configure the device attribute information of each network element device. The device attribute information can be used to create an offline network element corresponding to the network element device, and can include device type information, simple network management protocol (SNMP) attribute information, telecommunications network protocol (Telnet) attribute information, secure shell (SSH) attribute information, etc.

[0049] The network element management module can be used to create an offline network element corresponding to the network element device based on the device attribute information of the network element device, and automatically establish a connection with the network element device after the zero-deployment process of the network element device is completed, so as to realize automatic management of the network element device.

[0050] As Figure 2 shown, it is a schematic diagram of a status determination system 200 provided by an embodiment of the present application. Figure 2 The status determination system 200 in

[0051] can include a computer device 10 and multiple network element devices 20.

[0052] Combined with Figure 1 the networking system shown Figure 2 the computer device 10 in it can be a network management device, and can be configured with DHCP services, file services, zero-deployment microservices, etc.

[0053] The DHCP service can be used to implement the functions of the DHCP server in the above Figure 1 and can report the interaction information during the process of allocating temporary addresses to the status monitoring module of the zero-deployment microservice through the message middleware. The file service can be used to implement the functions implemented by the intermediate file server and the version file server in the above Figure 1 Based on this, the computer device 10 can be used to provide ZTP services to the network element device 20 and support the initial configuration of the network element device 20. Moreover, the computer device 10 can also monitor the status of each progress of the network element device 20 during the deployment process.

[0054] For example, the computer device 10 can manage the ZTP tasks of the network element device 20 through the task management module and monitor the information of each progress in the ZTP tasks of the network element device 20 through the status monitoring module. Furthermore, the computer device 10 can determine the execution status of each progress of the network element device 20 during the ZTP process based on the monitored information, and update the execution status of the ZTP tasks of the network element device 20 in each progress, so as to support the perception of the deployment process of the network element device 20 by updating the ZTP tasks.

[0055] For another example, the computer device 10 can configure the device attribute information of the network element device 20 through the device attribute configuration module and create an offline network element corresponding to the network element device 20 through the network element management module to support the automatic management of the network element device 20.

[0056] In a possible way, the computer device 10 can also be configured with a display module, or be connected to a front-end display device, and can display the execution status of the ZTP tasks of the network element device 20 in real time, so as to facilitate the staff to understand the status of each progress of the gateway device 20 during the deployment process.

[0057] Figure 2 The network element device 20 in it can be an electronic device for providing computing resources and / or storage resources, etc. For example, an access switch in a data center, etc. In the case of a new deployment, the network element device 20 can achieve the initial configuration by interacting with the computer device 10.

[0058] Optionally, the computer device 10 and the network element device 20 can be terminals, can also be servers, or can be other types of devices with the above functions. Figure 2Shown in the figure is an example of the device form of the computer device 10 and the network element device 20, which does not limit it.

[0059] When the computer device 10 and the network element device 20 are servers, the server can be a single server, or can also be a server cluster composed of multiple servers. In some implementation manners, the server cluster can also be a distributed cluster. The present application does not limit the form of the server.

[0060] Alternatively, when the computer device 10 and the network element device 20 are terminals, the terminal can be a personal computer such as a desktop computer, a tablet computer, and a laptop computer, or can also be a remote terminal, a user terminal (terminal equipment, TE), and a mobile device, etc. The present application does not limit the form of the terminal. The device for implementing the functions of the terminal can be the terminal or can also be a device capable of supporting the terminal to implement the functions, such as a chip system. The device can be installed in the terminal or used in matching with the terminal. In the embodiments of the present application, the chip system can be composed of chips or can also include chips and other discrete devices.

[0061] It should be noted that Figure 2 The shown state determination system 200 is only an example, which does not limit the system architecture applicable to the state determination method provided by the embodiments of the present application. For example, the state determination system 200 can include more computer devices 10. Another example is that the state determination system 200 can include fewer network element devices 20.

[0062] Combined with Figure 2 the shown state determination system 200, as Figure 3 shown, is a schematic structural diagram of a state determination system 300 provided by the embodiments of the present application. The computer device 10 can include modules such as a network management user interface (user interface, UI), network element management, status monitoring, device attribute configuration, task management, DHCP service, and file service.

[0063] Staff can create a configuration template for device attribute information in the device attribute configuration module and create a zero-configuration deployment task for the network element device 20 in the task management module through the network management UI module of the computer device 10. And the zero-configuration deployment task of the network element device 20 can be bound to the device attribute information of the network element device 20.

[0064] The file service module can be used to store intermediate files, configuration files, version files, etc., and provide intermediate files, configuration files, and version files to the network element device 20. The file service module can be built into the computer device 10 or can also be a file server connected to the computer device 10, and this is not limited.

[0065] The network element device 20 may report the status log file during the zero-deployment process to the file service module. The file service module may be used to record the status log file reported by the network element device 20.

[0066] The status monitoring module may monitor the file service module to obtain the status log file of the network element device 20 during the zero-deployment process, so as to determine the status information of the network element device 20 during the zero-deployment process. Moreover, the status monitoring module may monitor the middleware messages reported by the DHCP service module to obtain the interaction information between the network element device 20 and the DHCP service module during the temporary address allocation process, so as to determine the status information of the network element device 20 during the temporary address allocation process. Furthermore, the status monitoring module may send the status information to the network management UI, so that the network management UI can display the status information of the network element device 20 to the staff.

[0067] In a possible way, the message middleware used in the embodiments of the present application to support the status monitoring module to monitor the DHCP service module may be Kafka, Rabbit Message Queue (MQ), RocketMQ, ActiveMQ, ZeroMQ, MetaMQ, ETCD, etc., which is not limited thereto.

[0068] Regarding other modules in the computer device 10, reference may be made to Figure 1 and Figure 2 for the description, which will not be elaborated herein.

[0069] Hereinafter, in combination with Figure 2 or Figure 3 the status determination system shown, the status determination method provided by the embodiments of the present application will be described. Figure 4 It is a schematic flowchart of a status determination method provided by an embodiment of the present application. Figure 4 The method shown can be applied to Figure 2 or Figure 3 the computer device in the status determination system shown. As Figure 4 shown, the status determination method may include: S401-S402.

[0070] S401. The computer device obtains the monitoring information of the target deployment progress during the execution of the zero-configuration deployment task corresponding to the network element device.

[0071] Among them, the target deployment progress may be any one of the deployment progress during the temporary address allocation process, or may also be any one of the deployment progress during the zero-deployment of the network element device.

[0072] In a possible way, the process of allocating a temporary address can be that the network element device interacts with the DHCP server to obtain the temporary address during the ZTP process. Moreover, the DHCP server can be a functional module deployed inside the computer device, and can report the interaction information between the target deployment progress and the network element device to the status monitoring module configured on the computer device through middleware messages or other means. Furthermore, the computer device can obtain the monitoring information of the target deployment progress of the network element device during the process of allocating the temporary address through the configured status monitoring module. For example, the DHCP server can report the middleware message to a specified middleware topic (Topic). The status monitoring module can monitor the specified middleware topic to obtain the middleware message.

[0073] In this case, the target deployment progress can be the progress during the process of allocating the temporary address. The monitoring information can be the middleware message monitored by the status monitoring module. The middleware message can include at least one of the interaction message type, the address information of the network element device, and the first indication information.

[0074] The interaction message type is used to indicate the type of the interaction message corresponding to the target deployment progress, that is, the type of the interaction message between the network element device and the DHCP server. For example, the interaction message type can be the type of requesting a temporary address, the type of providing a temporary address, the type of selecting a temporary address, or the type of confirming a temporary address, etc. The message of the type of requesting a temporary address can be a DHCP discovery message (DHCP DISCOVER). The message of the type of providing a temporary address can be a DHCP offer message (DHCP OFFER). The message of the type of selecting a temporary address can be a DHCP request message (DHCP REQUEST). The message of the type of confirming a temporary address can be a DHCP acknowledge message (DHCP acknowledge character, DHCP ACK). Through the type of this interaction message, it can be determined whether the target deployment progress is the progress of requesting a temporary address, the progress of providing a temporary address, the progress of selecting a temporary address, or the progress of confirming a temporary address.

[0075] The address information of the network element device can be carried in each type of interaction message to facilitate determining the network element device to which the current progress information reported by the middleware message belongs. For example, the address information of the network element device can be the media access control (MAC) address of the network element device.

[0076] The first indication information can be used to indicate that there is an exception in the process of parsing the interaction message. That is, when there is an exception in the process of parsing any type of the above interaction messages, while the DHCP server reports the interaction message type and the address information of the network element device through the middleware message, the first indication information can also be carried in the middleware message, so that the status monitoring module can determine the exception in the execution process.

[0077] In a possible way, the zero-deployment process can be a process in which the network element device downloads resource files such as intermediate files, configuration files, and version files, and completes the deployment. This process can include multiple processes. For example, processes such as downloading intermediate files, parsing intermediate files, downloading configuration files, downloading version files, device restart, loading version files, and loading configuration files.

[0078] When the network element device executes any one of the processes in the zero-deployment process, it can record the status log file during execution, and can send the recorded status log file to the log server. And the log server can be a functional module deployed in a computer device. That is, the network element device can send the status log file during the zero-deployment process to the log service module of the computer device. Furthermore, the computer device can monitor the log service module through the configured status monitoring module to obtain the monitoring information of the target deployment progress of the network element device during the zero-deployment process.

[0079] In this case, the target deployment progress can be the progress during the zero-deployment process. The monitoring information can be the log file information monitored by the status monitoring module from the log service module, and the log file information is the status log file of the process corresponding to the target deployment progress.

[0080] S402. The computer device determines the status information of the target deployment progress according to the monitoring information.

[0081] Among them, the status information can be used to indicate the execution situation of the target deployment progress. For example, execution exception, normal execution, or medium execution situation.

[0082] In a possible way, when the monitoring information is a middleware message, the computer device can determine the progress corresponding to the interaction message type as the target deployment progress, and determine whether there is an execution exception in the target deployment progress according to whether the middleware message includes the first indication information.

[0083] Or, when the monitoring information is log file information, the computer device can determine the process corresponding to the log file information as the target deployment progress, and determine the status information of the target deployment progress according to the status information in the log file information.

[0084] Based on the description of S401 - S402 above, it can be known that the computer device can obtain the monitoring information of the target deployment progress during the execution of the zero - configuration deployment task corresponding to the network element device. Among them, the target deployment progress can be the progress currently being executed by the zero - configuration deployment task. That is, the computer device can monitor the progress information of the network element device during the ZTP process to facilitate determining the current progress of the network element device during the deployment process and whether there are any abnormalities at the current progress. Furthermore, the computer device can determine the status information of the target deployment progress, that is, the execution situation of the target deployment progress, based on the monitoring information, so as to perceive the status of the network element device during the deployment process.

[0085] Based on this, the present application can determine the execution situation of the network element device at the target deployment progress by monitoring the execution progress of the zero - configuration deployment task of the network element device, and realize the perception of the status of the network element device during the deployment process. Therefore, the present application can be used to solve the problem of difficulty in determining the status of the device during the ZTP process.

[0086] In one embodiment, if the monitoring information is a middleware message, when the computer device executes S402 above, that is, when the computer device determines the status information of the target deployment progress according to the monitoring information, an optional implementation manner provided by the embodiment of the present application includes: S501 - S502.

[0087] S501. When the middleware message does not include the first indication information, the computer device determines that the status information of the target deployment progress is normal execution.

[0088] In a possible way, a specific field can be defined in the middleware message, and different values of the specific field are used to indicate whether the first indication information exists. For example, the specific field can be the errorInfo field. When the value of this field is 0, it can be used to indicate that the first indication information does not exist, that is, there is no parsing exception. When the value of this field is 1, it can be used to indicate that the first indication information exists, that is, there is a parsing exception. Furthermore, when the specific field is 0, the computer device determines that the middleware message does not include the first indication information, so as to determine that the status information of the target deployment progress is normal execution.

[0089] In a possible way, the first indication information can also be specifically described in the message body of the middleware message, which can be used to indicate the specific abnormal position when parsing the interaction message, so as to facilitate the staff to understand the specific reason for the exception. In this case, if the computer device does not recognize the first indication information after parsing the middleware message, it can determine that the status information of the target deployment progress is normal execution.

[0090] S502. When the middleware message includes the first indication information, the computer device determines that the status information of the target deployment progress is abnormal execution.

[0091] In a possible way, when a specific field in the middleware message is 1, it can indicate that there is an exception in parsing the message. Then the computer device can determine that the status information of the target deployment progress is an execution exception.

[0092] In a possible way, if the computer device identifies the first indication information after parsing the middleware message, it can determine that the status information of the target deployment progress is an execution exception. Subsequently, the computer device can report the first indication information to the front end for display, so that the staff can understand the specific reason for the exception.

[0093] In another embodiment, if the monitoring information is log file information, when the computer device executes S402 above, that is, when the computer device determines the status information of the target deployment progress according to the monitoring information, the embodiment of the present application provides another optional implementation manner, including: S601.

[0094] S601. The computer device determines the execution status of the process of zero-deploying the network element device according to the log file information, and determines the execution status as the status information of the target deployment progress.

[0095] In a possible way, the status log file reported by the network element device may include the currently executed process and the execution status of the currently executed process. The currently executed process may be downloading an intermediate file, parsing an intermediate file, downloading a configuration file, downloading a version file, device restart, loading a version file, or loading a configuration file, etc. The computer device can parse the log file information, determine the currently executed process as the target deployment progress, and determine the execution status of the currently executed process as the status information of the target deployment progress.

[0096] In a possible way, the execution status of the process may be an execution start status, an execution in-progress status, an execution success status, or an execution exception status, etc.

[0097] In a possible way, the computer device can monitor the change of the status log file in the file service module in real time through the status monitoring module. When the status log file changes, the computer device can parse all status log files with the module name ZTP through the status monitoring module, and perceive the execution status of the zero-deployment process at the current progress through specific fields such as Parse, Download, and Load, so as to push the status information to the front end for display in real time.

[0098] In a possible example, such as Figure 5As shown in the figure, it is a schematic structural diagram of log file information provided by an embodiment of the present application. For a network element device with the address information of "Address 1", the execution status of each progress can be determined by identifying fields such as the parsing file, download file, and loading file in the status log files at different times such as time 1, time 2, and time 3 during the zero-deployment process.

[0099] In a possible way, the format of the status log file can be JavaScript object notation (JSON), another markup language (YAML ain't markup language, YAML), and extensible markup language (XML), etc.

[0100] In one embodiment, during the execution of the zero-configuration deployment task corresponding to the network element device, the status determination method provided by the embodiment of the present application further includes: S701.

[0101] S701. The computer device listens to the log file information of the network element device during the zero-deployment process in response to the completion of the process of allocating a temporary address.

[0102] In a possible way, when the type of the interaction message in the middleware message monitored by the computer device through the status monitoring module is the type of confirming the temporary address, that is, when the interaction message is a DHCP ACK, it can indicate that the DHCP server has completed the allocation of the temporary address of the network element device, and the device zero-deployment process can start. In this case, the computer device can poll and listen to the log file information of the network element device during the zero-deployment process through the configured status monitoring module.

[0103] In one embodiment, after the above S402, that is, after the computer device determines the status information of the target deployment progress according to the monitoring information, the status determination method provided by the embodiment of the present application further includes: S801 - S802.

[0104] S801. The computer device updates the task progress of the zero-configuration deployment task according to the status information of the target deployment progress.

[0105] In a possible way, the computer device can match the zero-configuration deployment task corresponding to the network element device according to the address information of the network element device in the middleware message or the address information of the network element device in the log file information. If the zero-configuration deployment task corresponding to the network element device is matched, the computer device can update the target deployment progress to the current task progress of the zero-configuration deployment task, and update the status information of the target deployment progress to the status of the current task progress. If the zero-configuration deployment task corresponding to the network element device is not matched, the computer device can discard the monitored information.

[0106] The computer device S802 displays the task progress of the updated zero-configuration deployment task.

[0107] In a possible way, to facilitate the staff to understand the status of the network device during the deployment process, the computer device can push the task progress of the updated zero-configuration deployment task to the front-end display module through the configured status monitoring module, and display the task progress of the updated zero-configuration deployment task through the front-end display module.

[0108] In a possible way, the computer device can report the status information of the target deployment progress to the front-end display module through the configured status monitoring module to display the task progress of the zero-configuration deployment task. For example, efficient information synchronization can be achieved between the status monitoring module and the front-end display module through message push frameworks such as CometD, Server-Sent, and WebSocket.

[0109] In a possible example, as Figure 6 shown, it is a schematic diagram of a task management interface provided by an embodiment of the present application. In the zero-configuration deployment management interface, function buttons such as task management, device attribute configuration, and file library can be provided. The task management module can be used to support management operations such as refreshing, creating, deleting, importing, and exporting the zero-configuration deployment tasks of network element devices, and display the task progress of the zero-configuration deployment tasks corresponding to the address information of the network element devices. The device attribute configuration module can be used to configure the device attribute information of the network element devices. The file library module can be used to configure intermediate files, configuration files, version files, etc.

[0110] For example, the task progress of the zero-configuration deployment task corresponding to Address 1 may be that the version file download fails, and the task progress of the zero-configuration deployment task corresponding to Address 2 may be the ACK status, that is, the temporary address confirmation status. For the zero-configuration deployment task corresponding to Address 1, the specific task process can be viewed by clicking on the status bar.

[0111] For example, the task process of the zero-configuration deployment task corresponding to Address 1 can be to start obtaining the intermediate file at 2023-07-18T20:14:26:968+00:00 (i.e., the download intermediate file process is in the execution start state), be downloading the intermediate file at 2023-07-18T20:14:26:970+00:00 (i.e., the download intermediate file process is in the execution state), successfully download the intermediate file at 2023-07-18T20:14:27:860+00:00 (i.e., the download intermediate file process is in the execution success state), successfully parse the intermediate file at 2023-07-18T20:14:27:861+00:00, start downloading the configuration file at 2023-07-18T20:14:27:861+00:00, be downloading the configuration file at 2023-07-18T20:14:27:861+00:00, successfully download the configuration file at 2023-07-18T20:14:28:125+00:00, start downloading the version file at 2023-07-18T20:14:28:143+00:00, be downloading the version file at 2023-07-18T20:14:28:143+00:00, and fail to download the version file at 2023-07-18T20:14:28:190+00:00 (i.e., the download version file process is in the execution exception state).

[0112] Based on the descriptions in S801 - S802, it can be known that this application can display the status of the network element device in the ZTP process in real time through the computer device, and can support the staff to understand the deployment progress of the network element device in real time. When the network element device has an exception during any deployment progress, the abnormal location can be intuitively perceived, and the exception can be repaired in time, which can significantly save the operation and maintenance cost.

[0113] In one embodiment, before the above S401, that is, before the computer device obtains the monitoring information of the target deployment progress during the execution of the zero-configuration deployment task corresponding to the network element device, the status determination method provided by the embodiments of this application further includes: S901.

[0114] S901: The computer device configures the zero-configuration deployment task corresponding to the address information of the network element device, and establishes the corresponding relationship between the zero-configuration deployment task and the device attribute information of the network element device.

[0115] In a possible way, the ZTP process of each network element device can be effectively managed by corresponding one network element device to one zero-configuration deployment task. For example, the zero-configuration deployment tasks corresponding to the MAC addresses of each network element device can be pre-configured through a task management module, and the device attribute information of each network element device can be pre-configured through a device attribute configuration module. Furthermore, the correspondence between the zero-configuration deployment task of the network element device and the device attribute information of the network element device can be created and stored in a database.

[0116] Among them, the device attribute information may include at least one of device type information, SNMP parameters, and remote login parameters. The remote login parameters may be attribute information such as account passwords based on Telnet or SSH.

[0117] In one embodiment, the state determination method provided by the embodiments of the present application further includes: S1001.

[0118] S1001. The computer device, in response to the completion of the execution of the zero-configuration deployment task, creates an offline network element according to the device attribute information.

[0119] Among them, the offline network element can be used to manage the network element device. For example, the computer device can send tasks to be executed to the network element device, change the configuration of the network element device, or control the startup and shutdown of the network element device, etc. through the offline network element.

[0120] In a possible way, when the computer device monitors through the configured state monitoring module that the network element device has completed the process of loading the configuration file, the configured network element management module can create an offline network element corresponding to the network element device according to the device attribute information of the network element device.

[0121] After the computer device creates an offline network element corresponding to the network element device, it can establish a connection with the network element device through the SNMP automatic discovery function, thereby realizing the automatic management of the network element device. Based on this, the present application can avoid the problem that manual management of the device by staff is required after the device deployment is completed, improve the device management efficiency, and reduce the operation and maintenance cost.

[0122] Based on this, the present application can automatically create an offline network element of the network element device after the network element device completes the zero-deployment process, realizing the automatic management of the network element device. When facing a large number of network element devices that need to be managed (such as thousands of them), the present application can configure the attribute template once in the device attribute configuration module to realize the attribute configuration of multiple network element devices with the same device attribute information, and can avoid the problem that manual operations need to be repeated in the network topology interface to create offline network elements in the traditional way, saving the cost of manual configuration management and improving the management efficiency.

[0123] In one embodiment, such as Figure 7As shown, during the process of allocating a temporary address, it is a schematic flowchart of a status determination method provided for an embodiment of this application. This status determination method may include: S1101 - S1107.

[0124] S1101. The computer device monitors a middleware message.

[0125] Among them, the middleware message may include the address information of the network element device and the type of interaction message. In the case where there is an abnormality in parsing the message, the middleware message may further include first indication information.

[0126] S1102. The computer device determines whether there is a zero - configuration deployment task that matches the address information.

[0127] S1103. When the computer device determines that there is no zero - configuration deployment task that matches the address information, it discards the middleware message.

[0128] In a possible way, if the computer device discards the middleware message, the current judgment logic ends.

[0129] S1104. When the computer device determines that there is a zero - configuration deployment task that matches the address information, it updates the task progress of the zero - configuration deployment task.

[0130] S1105. The computer device reports the status information to the task management page.

[0131] In a possible way, the computer device can report the status information of the target deployment progress to the task management page through a configured status monitoring module to display the task progress of the zero - configuration deployment task. For example, the status monitoring module and the task management page can achieve efficient information synchronization through message push frameworks such as CometD, Server - Sent, and WebSocket.

[0132] S1106. The computer device determines whether it is an acknowledgement type.

[0133] In a possible way, when the computer device determines that there is a zero - configuration deployment task that matches the address information, it can also determine whether the interaction message type in the middleware message is an acknowledgement type for acknowledging the temporary address.

[0134] S1107. When the computer device determines that the interaction message type is an acknowledgement type, it monitors the status log file in the file service.

[0135] In a possible way, when the computer device determines that the interaction message type is an acknowledgement type, it can poll and monitor the status log file in the file service to determine the progress information of the network element device during the zero - deployment process.

[0136] In a possible way, if the computer device determines that the type of the interaction message is not the confirmation type, the current judgment logic ends.

[0137] In one embodiment, as Figure 8 shown, in the zero-deployment process, it is a schematic flowchart of a status determination method provided by an embodiment of the present application. The status determination method may include: S1201 - S1208.

[0138] S1201. The computer device receives the status log file sent by the network element device.

[0139] S1202. The computer device records the status log file through the file service module.

[0140] S1203. The computer device monitors whether the status log file has changed.

[0141] S1204. The computer device parses the log file information and updates the task progress.

[0142] In a possible way, when the computer device monitors that the status log file has changed, it can parse the changed log file information to determine the status information of the target deployment progress and update the task progress of the zero-configuration deployment task corresponding to the network element device.

[0143] S1205. The computer device reports the status information to the task management page.

[0144] S1206. The computer device determines whether the zero-configuration deployment task has been completed.

[0145] S1207. The computer device creates an offline network element and automatically establishes a connection.

[0146] In a possible way, when the computer device determines that the zero-deployment process is completed, it can create an offline network element according to the device attribute information of the network element device and automatically establish a connection to achieve automatic management of the network element device. So far, the zero-configuration deployment task of the network element device ends.

[0147] S1208. The computer device continues to monitor.

[0148] In a possible way, when the status log file has not changed or it is determined that the zero-deployment process is not completed, the computer device continues to monitor whether the status log file in the file service module has changed.

[0149] Combined with Figure 7 and Figure 8As described above, the present application can monitor the status of each deployment progress of network element devices during the ZTP process and support automatic management of network element devices. Moreover, the present application can display the status of each deployment progress of network element devices during the ZTP process in real time through the task management page, and can intuitively understand the exception information and perform exception handling in a timely manner when any deployment progress is executed abnormally. Therefore, when using the ZTP technology to perform initial configuration on a large number of devices, the present application can further improve the deployment efficiency and reduce the manual operation and maintenance cost.

[0150] In a possible embodiment, based on the status determination method provided in some of the above embodiments of the present application, when using the ZTP technology to perform initial configuration on zero-configuration network element devices, the embodiments of the present application provide an optional implementation manner, including: S1301-S1312.

[0151] S1301. The computer device configures the device attribute information of the network element device through the device attribute configuration module and stores the device attribute information of the network element device in the database.

[0152] S1302. The computer device creates a zero-configuration deployment task corresponding to the address information of the network element device through the task management module, establishes a correspondence between the zero-configuration deployment task and the device attribute information of the network element device, stores the zero-configuration deployment task in the database, and uploads the intermediate files, configuration files, and version files required for the zero-deployment process to the file service module.

[0153] S1303. The computer device subscribes to the middleware topic reported by the DHCP service module through the status monitoring module.

[0154] S1304. The computer device receives the DHCP discovery message sent by the network element device through the DHCP service module.

[0155] In a possible way, after the network element device is powered on with empty configuration, it can broadcast a DHCP discovery message through the DHCP client to find the DHCP server. The DHCP service module configured by the computer device can act as the DHCP server to receive the DHCP discovery message broadcast by the network element device.

[0156] S1305. The computer device reports a middleware message to the middleware topic through the DHCP service module.

[0157] In a possible way, the middleware message may include at least one of an interaction message type, the address information of the network element device, and a first indication information.

[0158] S1306. The computer device monitors the middleware message reported by the DHCP service module through the status monitoring module.

[0159] In a possible way, the computer device can parse the middleware message and match the address information of the network element device in the middleware message in the database. If a corresponding zero-configuration deployment task is matched, the computer device can update the status information of the deployment progress during the temporary address allocation process of the zero-configuration deployment task and push the updated status information to the task management page. If no corresponding zero-configuration deployment task is matched, the computer device can discard this middleware message.

[0160] S1307. The computer device allocates a temporary address for the network element device through the DHCP service module and sends a DHCP offer message to the network element device.

[0161] In a possible way, the temporary address can be a temporary management IP address in the address pool.

[0162] In a possible way, after the computer device executes S1307, while executing S1308, or before executing S1308, or after executing S1308, it can also repeatedly execute S1305 and S1306.

[0163] S1308. The computer device sends a DHCP acknowledgment message to the network element device in response to the DHCP request message sent by the network element device.

[0164] In a possible way, after the network element device receives the DHCP offer message through the DHCP client, it can send a DHCP request message to the computer device.

[0165] After the computer device receives the DHCP request message sent by the network element device, it can match whether there is a corresponding lease record according to the address information of the network element device carried in the DHCP request message. If there is a corresponding lease record, the computer device can send a DHCP acknowledgment message containing the temporary address and other settings to the network element device and repeatedly execute S1305 and S1306.

[0166] S1309. When the interaction message type in the middleware message parsed by the status monitoring module is ACK, the computer device monitors the log file information of the network element device during the zero-deployment process.

[0167] In a possible way, if the interaction message type in the middleware message parsed by the status monitoring module is ACK, it can indicate that the DHCP service module has completed the temporary address allocation process and the network element device starts the zero-deployment process. In this case, the computer device can start polling and monitoring the log file information in the file service module through the status monitoring module.

[0168] S1310. The computer device receives the status log file sent by the network element device through the file service module.

[0169] In a possible way, based on the assigned temporary address, the network element device can start the device zero-deployment process, and can record the status log file in real time during a series of key processes such as downloading intermediate files, parsing intermediate files, downloading configuration files, downloading version files, restarting, loading version files, and loading configuration files, and send the status log file to the file service module of the computer device.

[0170] S1311. The computer device parses the status log file during the zero-deployment process through the status monitoring module, updates the status information of the deployment progress of the zero-configuration deployment task during the zero-deployment process, and pushes the updated status information to the task management page for real-time display.

[0171] S1312. In response to the completion of the execution of the zero-configuration deployment task, the computer device creates an offline network element according to the device attribute information of the network element device corresponding to the zero-configuration deployment task.

[0172] In a possible way, when the computer device parses through the status monitoring module that the process of loading the configuration file is completed during the zero-deployment process, it can create an offline network element according to the device attribute information of the network element device corresponding to the zero-configuration deployment task through the network element management module, and establish a connection with the network element device through the SNMP automatic discovery function after successfully creating the offline network element, so as to realize the automatic management of the network element device.

[0173] It can be understood that in order to implement the above functions, the computer device in the status determination system includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combined with the algorithm steps of each example described in the embodiments of the present application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0174] The embodiments of the present application can divide the functional modules of the main gateway in the status determination system according to the above method embodiments. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above integrated module can be implemented in the form of hardware or software. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation. The following takes the division of each functional module corresponding to each function as an example for description.

[0175] When each functional module is divided according to each function in the form of software, Figure 9 FIG. shows a schematic structural diagram of a status determination device 400. The status determination device 400 can be applied to Figure 2 or Figure 3 in the computer device within the status determination system, and can be used to execute the status determination method executed by the computer device in the above method embodiments. As Figure 9 shown, the status determination device 400 may include: an acquisition module 1401 and a processing module 1402.

[0176] The acquisition module 1401 is configured to acquire monitoring information of the target deployment progress during the execution of the zero-configuration deployment task corresponding to the network element device;

[0177] The processing module 1402 is configured to determine the status information of the target deployment progress according to the monitoring information; the status information is used to indicate the execution situation of the target deployment progress.

[0178] In a possible embodiment, the target deployment progress includes any one of the deployment progress during the process of allocating a temporary address and the deployment progress during the process of zero-deploying the network element device.

[0179] In a possible embodiment, when the target deployment progress is the progress during the process of allocating a temporary address, the monitoring information is a middleware message, and the middleware message includes at least one of an interaction message type, the address information of the network element device, and a first indication information. The interaction message type is used to indicate the type of the interaction message corresponding to the target deployment progress, and the first indication information is used to indicate that an exception exists in the process of parsing the interaction message.

[0180] In a possible embodiment, the processing module 1402 is specifically configured to: when the middleware message does not include the first indication information, determine that the status information of the target deployment progress is normal execution; when the middleware message includes the first indication information, determine that the status information of the target deployment progress is abnormal execution.

[0181] In a possible embodiment, the interaction message type includes any one of a type of requesting a temporary address, a type of providing a temporary address, a type of selecting a temporary address, and a type of confirming a temporary address.

[0182] In a possible embodiment, when the target deployment progress is the progress during the zero-deployment process, the monitoring information is log file information, and the log file information is the status log file of the process corresponding to the target deployment progress.

[0183] In a possible embodiment, the process includes at least one of downloading an intermediate file, parsing the intermediate file, downloading a configuration file, downloading a version file, device restart, loading the version file, and loading the configuration file.

[0184] In a possible embodiment, the processing module 1402 is specifically configured to: determine the execution status of the process when zero-deploying the network element device according to the log file information, and determine the execution status as the status information of the target deployment progress; wherein, the execution status includes any one of the execution start status, the execution in-progress status, the execution success status, and the execution exception status.

[0185] In a possible embodiment, the obtaining module 1401 is further configured to: in response to the completion of the process of allocating a temporary address, monitor the log file information of the network element device during the zero-deployment process.

[0186] In a possible embodiment, the apparatus further includes: a display module 1403;

[0187] The processing module 1402 is further configured to update the task progress of the zero-configuration deployment task according to the status information of the target deployment progress.

[0188] The display module 1403 is configured to display the updated task progress of the zero-configuration deployment task.

[0189] In a possible embodiment, the apparatus further includes: a configuration module 1404;

[0190] The configuration module 1404 is configured to configure a zero-configuration deployment task corresponding to the address information of the network element device, and establish a corresponding relationship between the zero-configuration deployment task and the device attribute information of the network element device; the device attribute information includes at least one of device type information, Simple Network Management Protocol (SNMP) parameters, and remote login parameters.

[0191] In a possible embodiment, the configuration module 1404 is further configured to, in response to the completion of the execution of the zero-configuration deployment task, create an offline network element according to the device attribute information; the offline network element is used to manage the network element device.

[0192] In the case of implementing the functions of the above integrated modules in the form of hardware, another possible structure of the computer device involved in the embodiments of the present application is provided. As Figure 10 shown, the computer device 500 may include: a processor 1502, a bus 1504. Optionally, the computer device 500 may further include a memory 1501; optionally, the computer device 500 may further include a communication interface 1503.

[0193] For example, some or all of the functions of the obtaining module 1401, the processing module 1402, and other modules included in the status determination device 400 described above can also be implemented by the processor 1502. Figure 9

[0194] ​The processor 1502 can be a device that implements or executes various exemplary logical blocks, modules, and circuits described in connection with the embodiments of the present application. The processor 1502 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the embodiments of the present application. The processor 1502 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0195] The communication interface 1503 is used to connect to other devices through a communication network. The communication network can be an Ethernet, a radio access network, a wireless local area network (WLAN), etc.

[0196] The memory 1501 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium, or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0197] As a possible implementation, the memory 1501 can exist independently of the processor 1502. The memory 1501 can be connected to the processor 1502 through a bus 1504 for storing instructions or program code. When the processor 1502 calls and executes the instructions or program code stored in the memory 1501, the state determination method provided by the embodiments of the present application can be implemented.

[0198] In another possible implementation, the memory 1501 can also be integrated with the processor 1502.

[0199] The bus 1504 can be an extended industry standard architecture (EISA) bus, etc. The bus 1504 can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 10 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0200] Some embodiments of the present application provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium), in which computer program instructions are stored. When the computer program instructions run on a computer, the computer is caused to execute the state determination method described in any one of the above embodiments.

[0201] Exemplarily, the above computer-readable storage medium may include, but is not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes, etc.), optical discs (e.g., Compact Disks (CDs), Digital Versatile Disks (DVDs), etc.), smart cards, and flash memory devices (e.g., Erasable Programmable Read-Only Memories (EPROMs), cards, sticks, or key drives, etc.).

[0202] The various computer-readable storage media described in the present application may represent one or more devices and / or other machine-readable storage media for storing information.

[0203] The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media that can store, contain, and / or carry instructions and / or data.

[0204] The embodiments of the present application provide a computer program product containing instructions. When the computer program product runs on a computer, the computer is caused to execute the state determination method described in any one of the above embodiments.

[0205] As described above, the above are only the specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A status determination method, comprising: Obtaining monitoring information of a target deployment progress during the execution of a zero-configuration deployment task corresponding to a network element device; Determining status information of the target deployment progress according to the monitoring information; The status information is used to indicate the execution situation of the target deployment progress.

2. The method according to claim 1, characterized in that, The target deployment progress includes any one of each deployment progress during the process of allocating a temporary address and each deployment progress during the process of zero-deploying the network element device.

3. The method according to claim 2, wherein When the target deployment progress is the progress during the process of allocating a temporary address, the monitoring information is middleware message, and the middleware message includes at least one of an interaction message type, address information of the network element device, and a first indication information. The interaction message type is used to indicate the type of the interaction message corresponding to the target deployment progress, and the first indication information is used to indicate that there is an abnormality in the process of parsing the interaction message.

4. The method according to claim 3, characterized in that, The determining the status information of the target deployment progress according to the monitoring information includes: When the middleware message does not include the first indication information, determining that the status information of the target deployment progress is normal execution; When the middleware message includes the first indication information, determining that the status information of the target deployment progress is abnormal execution.

5. The method according to claim 3, characterized in that The interaction message type includes any one of a type of requesting a temporary address, a type of providing a temporary address, a type of selecting a temporary address, and a type of confirming a temporary address.

6. The method according to claim 2, wherein When the target deployment progress is the progress during the zero-deployment process, the monitoring information is log file information, and the log file information is a status log file of a process corresponding to the target deployment progress.

7. The method according to claim 6, wherein The process includes at least one of downloading an intermediate file, parsing the intermediate file, downloading a configuration file, downloading a version file, device restart, loading the version file, and loading the configuration file.

8. The method according to claim 6, characterized in that The determining the status information of the target deployment progress according to the monitoring information includes: Determining the execution status of the process when zero-deploying the network element device according to the log file information, and determining the execution status as the status information of the target deployment progress; wherein, the execution status includes any one of an execution start status, an execution in-progress status, an execution success status, and an execution abnormal status.

9. The method according to claim 2, wherein It further includes: In response to the completion of the process of allocating a temporary address, monitoring the log file information of the network element device during the zero-deployment process.

10. The method according to claim 1, wherein After the determining the status information of the target deployment progress according to the monitoring information, it further includes: Updating the task progress of the zero-configuration deployment task according to the status information of the target deployment progress; Displaying the updated task progress of the zero-configuration deployment task.

11. The method according to claim 1, wherein Before the obtaining the monitoring information of the target deployment progress during the execution of the zero-configuration deployment task corresponding to the network element device, the method further includes: Configure the zero-configuration deployment task corresponding to the address information of the network element device, and establish a corresponding relationship between the zero-configuration deployment task and the device attribute information of the network element device; the device attribute information includes at least one of device type information, Simple Network Management Protocol (SNMP) parameters, and remote login parameters.

12. The method according to claim 11, wherein The method further includes: In response to the completion of the execution of the zero-configuration deployment task, create an offline network element according to the device attribute information; the offline network element is used to manage the network element device.

13. A computer device, characterized in that, It includes: A memory and a processor; The memory and the processor are coupled; The memory is used to store instructions executable by the processor; When the processor executes the instructions, it executes the method according to any one of claims 1-12.

14. A computer-readable storage medium, characterized in that, Computer instructions are stored on the computer-readable storage medium, and when the computer instructions run on a computer, the computer is caused to execute the method according to any one of claims 1-12.

Images