A method and device for queue control based on network element equipment configuration

Abstract

The present invention discloses a method and device based on queue control of network element device configuration, wherein the method comprises: adding a serial configuration lock to all network element devices; creating a configuration delivery task queue, and setting the serial configuration lock of the network element device corresponding to each delivery task to Y, and storing the corresponding lock identifier Y in Redis; and delivering serial configuration to the network element device whose configuration protocol is CLI or SNMP and whose lock identifier is Y. In the process of batch configuration delivery, the method and device add the ability to lock the network element device, form a control flow of a batch configuration delivery queue, and realize the control of the number of session connections of the network element device, thereby improving the success rate of batch configuration delivery of the network element device and reducing the workload of the operation and maintenance personnel.

Description

Technical Field

[0001] The present invention relates to the field of configuration data sending of network element equipment, and in particular to a method and device for controlling queues based on configuration sending of network element equipment. Background Art

[0002] In the operator field, the staff of the network operation and maintenance department need to issue various commands to the network element equipment every day to realize functions such as service activation, fault handling, performance collection, topology collection, alarm collection and security protection. The number of network element equipment of operators is large. For example, the number of PON (Passive Optical Network) equipment in a province can reach millions.

[0003] Some of these commands need to be uniformly configured for all network element devices, such as QoS (Quality of Service) configuration, ACL (Access Control List) configuration, bandwidth rate template configuration, network management server IP (Internet Protocol) address configuration and SNMP (Simple Network Management Protocol) configuration, etc. Therefore, it is necessary to uniformly issue command sets to a large number of network element devices to save the workload of operation and maintenance personnel.

[0004] However, if some network elements fail to be delivered during the batch delivery process, after the batch delivery is completed, it is necessary to screen the reasons for the failure and sort out the list of failed network elements, and then re-deliver the failed network elements. This is one of the maintenance bottlenecks that bothers operation and maintenance personnel. The most common reason for delivery failure is the session (session limit) number limit of the network element device itself.

[0005] When a management user logs in to a network element device to perform an operation, a session connection will be generated on the network element device. In order to protect the normal operation of its own session connection function, the network element device will implement corresponding limiting protection mechanisms on the total number of sessions and the number of new sessions per second, especially limiting the number of session connections for a single IP address.

[0006] On the network element device, you can configure the session limit accordingly:

[0007] ip connection limit ADDR-NAME total limit-num per_second limit-num.

[0008] On the network element device, you can display the statistics of the number of session connections:

[0009] display ip connection statistics[ipaddr].

[0010] The protection mechanism of the above-mentioned network element equipment for session connections will often lead to failure of batch delivery, because the batch delivery operation is issued through the network management software system, and the network management software system may also be performing other operations on the network element equipment or maintaining multiple session connections at the same time, so the failure to establish the session connection occurs, resulting in failure of batch delivery.

[0011] The problem of configuration data delivery failure that occurs during the unified delivery of configuration data to a large number of network element devices cannot be solved by blindly increasing the limit on the number of session connections of the network element devices. This method can only treat the symptoms but not the root cause, and there are certain security risks. Summary of the invention

[0012] In order to solve the problem of configuration data delivery failure in the process of unified delivery of configuration data for large quantities of network element devices, the present invention provides a method and device based on the control of network element device configuration delivery queue. In the process of batch configuration delivery, the ability to lock the network element devices is newly added to form a control flow of a batch configuration delivery queue, and the number of session connections of the network element devices is controlled, thereby improving the success rate of batch configuration delivery of network element devices and reducing the workload of operation and maintenance personnel.

[0013] To achieve the above object, the present invention adopts the following technical solutions:

[0014] In one embodiment of the present invention, a method for queue control based on network element device configuration is proposed, the method comprising:

[0015] Add serial configuration locks to all network element devices;

[0016] Create a configuration delivery task queue, set the serial configuration lock of each network element device corresponding to each delivery task to Y, and store the corresponding lock flag in Redis as Y;

[0017] Deliver serial configuration to network element devices whose configuration protocol is CLI or SNMP and whose lock flag is Y.

[0018] Furthermore, the serial configuration is issued to the network element device whose configuration protocol is CLI or SNMP and whose lock identifier is Y, including:

[0019] When the configuration is issued, it is determined whether the network element device with the configuration protocol of CLI or SNMP is locked;

[0020] If the lock status is Y, it will enter the task queue. If there are tasks in the task queue, the corresponding lock flag will be checked every second.

[0021] If the lock flag is N, the task is issued, and the corresponding lock flag stored in Redis for the issued task is updated to Y. At the same time, after waiting for the execution of the issued task, the lock flag corresponding to the task is updated to N.

[0022] Furthermore, if the execution of the task issued times out or fails, the lock flag corresponding to the task is updated to N.

[0023] Furthermore, in the network element device management module of the network management software system, a serial configuration lock is added to all network element devices by default.

[0024] In one embodiment of the present invention, a device for issuing queue control based on network element device configuration is also proposed, and the device includes:

[0025] The network element device management module is used to add a serial configuration lock to all network element devices by default;

[0026] The configuration delivery task creation module is used to create a configuration delivery task queue, and set the serial configuration lock of the network element device corresponding to each delivery task to Y, and store the corresponding lock identifier in Redis as Y;

[0027] The serial configuration delivery module is used to deliver serial configuration to network element devices whose configuration protocol is CLI or SNMP and whose lock flag is Y.

[0028] Furthermore, the serial configuration sending module is specifically used for:

[0029] When the configuration is issued, it is determined whether the network element device with the configuration protocol of CLI or SNMP is locked;

[0030] If the lock status is Y, it will enter the task queue. If there are tasks in the task queue, the corresponding lock flag will be checked every second.

[0031] If the lock flag is N, the task is issued, and the corresponding lock flag stored in Redis for the issued task is updated to Y. At the same time, after waiting for the execution of the issued task, the lock flag corresponding to the task is updated to N.

[0032] Furthermore, if the execution of the task issued times out or fails, the lock flag corresponding to the task is updated to N.

[0033] In one embodiment of the present invention, a computer device is also proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the aforementioned queue control based on the configuration of the network element device is implemented.

[0034] In one embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program for executing queue control based on network element device configuration.

[0035] Beneficial effects:

[0036] The present invention realizes serial configuration operation on the same network element device through the network element device configuration sending locking technology, thereby avoiding failure phenomenon occurring in the process of uniformly sending configuration data of a large number of network element devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 It is a flow chart of a method for queue control based on network element device configuration in the present invention;

[0038] Figure 2 It is a schematic diagram of the structure of a device for issuing queue control based on network element device configuration in the present invention;

[0039] Figure 3 It is a schematic diagram of the computer device structure of the present invention. DETAILED DESCRIPTION

[0040] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0041] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a device, apparatus, equipment, method or computer program product. Therefore, the present disclosure may be implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0042] According to an implementation manner of the present invention, a method and device based on network element device configuration delivery queue control are proposed. In the process of batch configuration delivery, a new capability of locking the network element device is added to form a control flow of a batch configuration delivery queue, thereby realizing control over the number of session connections of the network element device, thereby improving the success rate of batch configuration delivery of the network element device and reducing the workload of operation and maintenance personnel.

[0043] The principle and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.

[0044] Figure 1 This is a flow chart of the method for queue control based on network element device configuration in the present invention. Figure 1 As shown, the method includes:

[0045] 1. In the network element device management module of the network management software system, a serial configuration lock is added to all network element devices by default;

[0046] 2. Create a configuration delivery task queue, and set the serial configuration lock of each network element device corresponding to each delivery task to Y. At the same time, store the corresponding lock flag (a parameter used to record variables, with only two values) as Y in Redis (Redis is an in-memory key-value database, usually called a data structure server);

[0047] 3. After logging in to the network element device, when the northbound interface calls the API (Application Programming Interface) to issue configuration, for network element devices whose configuration protocol is CLI (command-line interface) or SNMP (Simple Network Management Protocol) and whose lock mark is Y, serial configuration is issued by default;

[0048] Determine whether the network element device with CLI or SNMP configuration protocol is locked;

[0049] If the lock status is Y (Y stands for locked), the task queue is entered. If there are tasks queued in the task queue, the corresponding lock flag is checked every second.

[0050] If the lock flag is N (N stands for unlocked), the task is issued, and the corresponding lock flag stored in Redis for the issued task is updated to Y;

[0051] If the previous delivery task is not completed, other delivery tasks for this network element device need to wait in line until the delivery task is completed, and the lock flag corresponding to the task is updated to N to ensure that the configuration delivery tasks are executed serially, and the network element device will not report an error due to the parallel execution of multiple delivery tasks;

[0052] If the execution of the dispatched task times out or fails, the lock flag corresponding to the dispatched task is updated to N.

[0053] It should be noted that, although the operations of the method of the present invention are described in a specific order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0054] In order to explain the above-mentioned queue control based on network element device configuration more clearly, a specific embodiment is used for illustration below. However, it is worth noting that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation on the present invention.

[0055] Example:

[0056] 1. Locking and unlocking operations

[0057] Locking operation instructions issued by CLI:

[0058] alter table cm_ccf_device add cli_lock char(1)default'Y';

[0059] Unlock command issued by CLI:

[0060] alter table cm_ccf_device add cli_lock char(1)default'N';

[0061] Locking operation instructions sent by SNMP:

[0062] alter table cm_ccf_device add snmp_lock char(1)default'Y';

[0063] Unlocking instructions sent by SNMP:

[0064] alter table cm_ccf_device add snmp_lock char(1)default'N'.

[0065] 2. When calling the API to issue configuration, if the corresponding configuration protocol = CLI, follow the steps below:

[0066] Step 1: If a process calls the configuration delivery service / rpc / ccf / querydevbycondition, first go to Redis to obtain the lock status corresponding to the network element device. The input parameter is the current network element device identifier devid, and the corresponding return parameter cliLock (the lock identifier delivered by CLI mode). If cliLock = N, jump to step 3;

[0067] step2: If cliLock = Y, then sleep for 1 second and re-execute step1;

[0068] Step 3: According to the locking status of the network element device, N is set to execute the configuration operation normally;

[0069] Step 4: After the delivery is completed, set cliLock = N (release the locked state).

[0070] 3. When calling the API to issue configuration, if the corresponding configuration protocol = SNMP, follow the steps below:

[0071] Step 1: If a process calls the configuration delivery service / rpc / ccf / querydevbycondition, first go to Redis to obtain the lock status corresponding to the network element device. The input parameter is the current network element device ID devid, and the corresponding return parameter snmpLock (lock ID delivered by SNMP). If snmpLock = N, jump to step 3;

[0072] Step 2: If snmpLock = Y, then sleep for 1 second and re-execute step 1;

[0073] Step 3: According to the locking status of the network element device, N is set to execute the configuration operation normally;

[0074] Step 4: After the delivery is completed, set snmpLock = N (release the lock state).

[0075] 4. Method for determining protocol type

[0076] Virtual instruction: corresponds to cfgType in the virtual instruction information;

[0077] Virtual instruction set: according to the current virtual instruction set code / manage / composer / queryServSceneList (input parameter code = virtual instruction set code, corresponding to the part of the virtual instruction set code " / " in the API list), then according to the returned virtual instruction set identifier resId, call / manage / capconfig / queryCapConfigByResId (input parameter resId), get the returned serviceUrl, use the last segment in serviceUrl to match the last segment of the read dictionary value data protocol action, and get the protocol type used by the virtual instruction set;

[0078] The dictionary value corresponds to module=ccf, group_code=cm_biz_templetdef, dict_code=cfgItemUrl, where dict_value corresponds to the protocol type, and dict_text corresponds to the protocol action.

[0079] 5. The output parameters are as shown in Table 1:

[0080] Table 1

[0081]

[0082]

[0083] 6. Abnormal situation handling

[0084] When the configuration task execution times out or fails, the lock flag of the task is updated to N to release the lock state.

[0085] 7. Determine whether the locking function sent by the network element device is successfully enabled

[0086] Create multiple APIs for the same network element device;

[0087] At the same time, these APIs are released;

[0088] Observe whether the network element devices are executed serially.

[0089] Based on the same inventive concept, the present invention also proposes a device for queue control based on network element device configuration. The implementation of the device can refer to the implementation of the above method, and the repeated parts will not be repeated. The term "module" used below can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0090] Figure 2 Schematic diagram of the structure of the apparatus for queue control based on the configuration of network element equipment in the present invention. Figure 2 As shown, the device comprises:

[0091] The network element device management module 101 is used to add a serial configuration lock to all network element devices by default;

[0092] The configuration delivery task creation module 102 is used to create a configuration delivery task queue, and set the serial configuration lock of the network element device corresponding to each delivery task to Y, and store the corresponding lock identifier Y in Redis;

[0093] The serial configuration delivery module 103 is used to deliver serial configuration to the network element device whose configuration protocol is CLI or SNMP and whose lock identifier is Y; the details are as follows:

[0094] When the configuration is issued, it is determined whether the network element device with the configuration protocol of CLI or SNMP is locked;

[0095] If the lock status is Y, it will enter the task queue. If there are tasks in the task queue, the corresponding lock flag will be checked every second.

[0096] If the lock flag is N, issue the task and update the corresponding lock flag stored in Redis to Y. After the task is executed, update the lock flag corresponding to the task to N.

[0097] If the task execution times out or fails, the lock flag corresponding to the task is updated to N.

[0098] It should be noted that although several modules of the apparatus for issuing queue control based on network element device configuration are mentioned in the above detailed description, this division is only exemplary and not mandatory. In fact, according to an embodiment of the present invention, the features and functions of two or more modules described above can be concretized in one module. Conversely, the features and functions of one module described above can be further divided into multiple modules for concretization.

[0099] Based on the above invention concept, Figure 3 As shown, the present invention also proposes a computer device 200, including a memory 210, a processor 220, and a computer program 230 stored in the memory 210 and executable on the processor 220, and when the processor 220 executes the computer program 230, the aforementioned queue control based on the network element device configuration is implemented.

[0100] Based on the aforementioned inventive concept, the present invention further proposes a computer-readable storage medium, which stores a computer program for executing the aforementioned queue control based on network element device configuration.

[0101] The method and device for queue control based on network element device configuration delivery proposed in the present invention realize serial configuration operation on the same network element device through network element device configuration delivery locking technology.

[0102] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements contained in the spirit and scope of the attached claims.

[0103] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.

Claims

1. A method for queue control based on network element device configuration, characterized in that: The method includes: Add serial configuration locks to all network element devices; Create a configuration delivery task queue, set the serial configuration lock of each network element device corresponding to each delivery task to Y, and store the corresponding lock flag in Redis as Y; Deliver serial configuration to NE devices whose configuration protocol is CLI or SNMP and whose lock flag is N, including: When the configuration is issued, it is determined whether the network element device with the configuration protocol of CLI or SNMP is locked; If the lock status is Y, it will enter the task queue. If there are tasks in the task queue, the corresponding lock flag will be checked every second. If the lock flag is N, issue the task and update the corresponding lock flag stored in Redis to Y. After the task is executed, update the lock flag corresponding to the task to N. If the task execution times out or fails, the lock flag corresponding to the task is updated to N.

2. The method for queue control based on network element device configuration according to claim 1, characterized in that: In the network element device management module of the network management software system, a serial configuration lock is added to all network element devices by default.

3. A device for issuing queue control based on network element device configuration, characterized in that: The device includes: The network element device management module is used to add a serial configuration lock to all network element devices by default; The configuration delivery task creation module is used to create a configuration delivery task queue, and set the serial configuration lock of the network element device corresponding to each delivery task to Y, and store the corresponding lock identifier in Redis as Y; The serial configuration delivery module is used to deliver serial configuration to network element devices whose configuration protocol is CLI or SNMP and whose lock flag is N, including: When the configuration is issued, it is determined whether the network element device with the configuration protocol of CLI or SNMP is locked; If the lock status is Y, it will enter the task queue. If there are tasks in the task queue, the corresponding lock flag will be checked every second. If the lock flag is N, issue the task and update the corresponding lock flag stored in Redis to Y. After the task is executed, update the lock flag corresponding to the task to N. If the task execution times out or fails, the lock flag corresponding to the task is updated to N.

4. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 2 is implemented.

5. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 2.

Images