Method, computing device, and storage medium for network operations

Abstract

Embodiments of the present disclosure relate to a method, a computing device and a storage medium for network operation and maintenance. The method comprises, in response to retrieving an operation and maintenance requirement instruction, obtaining full network topology information and access relationship information; the access relationship information comprises access relationship information about at least one access relationship and at least indicates a start point and an end point in an access path corresponding to the access relationship; based on the access relationship information, generating topology information of each access relationship; one piece of topology information at least indicates an access path corresponding to one access relationship and device information of all devices in the path; based on the topology information of each access relationship, obtaining a configuration task corresponding to each access relationship; executing the configuration task corresponding to each access relationship in parallel; obtaining execution results of all configuration tasks, so as to aggregate the execution results to indicate a configuration state of the network. Thus, the present disclosure can improve network configuration efficiency and meet the requirement of automatic operation and maintenance in a multi-device and complex scenario.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure generally relate to the field of network communication technology, and more particularly to a method for network operation and maintenance, a computing device and a storage medium. BACKGROUND

[0002] Traditional operation and maintenance tools usually run in a network device-oriented manner. Such traditional operation and maintenance methods or tools usually configure each network device separately. They can achieve very good results in handling simple devices such as access layer switches or in configuring a single scenario.

[0003] However, with the rapid development of Internet application technology, communication technology and data processing technology, network access demand is growing explosively. The growing access demand poses a huge challenge to the operation and maintenance of data centers. In the operation and maintenance scenario of data centers, the opening of network access relationship is very important. The opening of an access relationship may involve configuration modification of multiple devices, and for data centers, hundreds of access relationships may be opened every day. Due to the lack of global topology information perception of a single network device, in the opening task of access relationship, the device-oriented operation and maintenance tool cannot meet the needs of complex east-west (i.e. traffic between devices in the data center) device automation operation and maintenance.

[0004] In summary, the traditional network operation and maintenance method has the following disadvantages: it is difficult to meet the automation operation and maintenance needs in the multi-device and complex scenario. SUMMARY

[0005] To solve the above problems, the present disclosure provides a method for network operation and maintenance, a computing device and a storage medium, which can improve network configuration efficiency and meet the automation operation and maintenance needs in the multi-device and complex scenario.

[0006] According to a first aspect of the present disclosure, a method for network operation and maintenance is provided, comprising: in response to retrieving an operation and maintenance requirement instruction, acquiring global topology information and access relationship information, the access relationship information comprising access relationship information about at least one access relationship, the access relationship information at least indicating a starting point and an ending point in an access path corresponding to the access relationship; based on the access relationship information, generating topology information of each access relationship, the topology information of one access relationship at least indicating the access path corresponding to the one access relationship and device information of all devices in the access path; based on the topology information of each access relationship, acquiring a configuration task corresponding to each access relationship; executing the configuration task corresponding to each access relationship in parallel; and acquiring an execution result of all configuration tasks, so as to aggregate the execution result to indicate a configuration state of the network.

[0007] According to a second aspect of the present disclosure, a computing device is provided, comprising: at least one processor; and a memory communicatively connected with the at least one processor; the memory storing instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method of the first aspect of the present disclosure.

[0008] In a third aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to cause a computer to perform the method of the first aspect of the present disclosure.

[0009] In some embodiments, performing the configuration task corresponding to each access relationship in parallel comprises: based on the configuration task corresponding to each access relationship, obtaining a sub-configuration task corresponding to each device in the access path corresponding to each access relationship; and performing all sub-configuration tasks of any access relationship in the at least one access relationship in parallel.

[0010] In some embodiments, obtaining the sub-configuration task corresponding to each device in the access path corresponding to each access relationship comprises: based on the pre-recorded task library and the device information of the device, calling a task template corresponding to the device in the access path to generate the sub-configuration task corresponding to each device in the access path; and the sub-configuration task at least comprises an information collection task, a configuration backup task and a configuration delivery task.

[0011] In some embodiments, obtaining the execution result of all configuration tasks to aggregate the execution result to indicate the configuration state of the network comprises: obtaining the execution result of each sub-configuration task; based on the execution result of each sub-configuration task, associating each sub-configuration task execution result with the access relationship; based on the association of each sub-configuration task execution result with the access relationship, aggregating the execution results of all sub-configuration tasks performed by the same device to indicate the configuration state of the network based on the aggregated execution result.

[0012] In some embodiments, the method for network operation further comprises: obtaining an error code fed back by the device corresponding to the sub-configuration task with a failed execution result; associating the error code fed back by the device with the corresponding sub-configuration task and aggregating to the execution result; and in response to detecting the error code of the device, re-executing the sub-configuration task of the device corresponding to the error code according to a predetermined error handling rule.

[0013] In some embodiments, the generating, based on the access relationship information, the topology information of each access relationship comprises: determining an access path corresponding to each access relationship based on the nodes included in each access relationship information; determining all devices involved in each access relationship based on the access path corresponding to each access relationship; and obtaining device information of all devices involved in each access relationship, the device information at least including a device model, location information, interface information, and connection information with other devices of the current device.

[0014] In some embodiments, the determining, based on the nodes included in each access relationship information, the access path corresponding to each access relationship comprises: if there is only one access path based on the nodes in an access relationship, determining the only one access path as the access path corresponding to the access relationship; if there are at least two access paths based on the nodes in an access relationship, determining one access path from the at least two determined access paths as the access path corresponding to the access relationship according to a predetermined path determination rule; and if there is no access path based on the nodes in an access relationship, returning indication information indicating a path confirmation failure.

[0015] In some embodiments, the method for network operation further comprises: determining whether a same device needs to perform multiple sub-configuration tasks; and in response to determining that the same device needs to perform multiple sub-configuration tasks, performing the multiple sub-configuration tasks of the same device according to a predetermined execution order rule.

[0016] It should be understood that the content described in this section is not intended to identify key or important features of the embodiments of the disclosure, nor is it used to limit the scope of the disclosure. Other features of the disclosure will become apparent through the following description. BRIEF DESCRIPTION OF DRAWINGS

[0017] The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by describing in detail the following embodiments with reference to the attached drawings. In the drawings, the same or similar reference numerals refer to the same or similar elements.

[0018] Figure 1 A schematic diagram of a system for implementing the method for network operation according to an embodiment of the present disclosure is shown.

[0019] Figure 2 A flowchart of the method 200 for network operation according to an embodiment of the present disclosure is shown.

[0020] Figure 3 A flowchart of the method 300 for parallel execution of sub-configuration tasks according to an embodiment of the present disclosure is shown.

[0021] Figure 4 A flowchart of a method 400 for configuring task execution result indication according to embodiments of the present disclosure is shown.

[0022] Figure 5 A flowchart of a method 500 for sub-configuration task re-execution according to embodiments of the present disclosure is shown.

[0023] Figure 6 A flowchart of a method 600 for determining access relationship topology information according to embodiments of the present disclosure is shown.

[0024] Figure 7 A flowchart of a method 700 for determining an access path according to embodiments of the present disclosure is shown.

[0025] Figure 8 A schematic diagram of network configuration concurrency principles according to embodiments of the present disclosure is shown.

[0026] Figure 9 A schematic diagram of network configuration state indication according to embodiments of the present disclosure is shown.

[0027] Figure 10 A block diagram of an electronic device according to embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0028] Exemplary embodiments of the present disclosure are described herein with reference to the accompanying drawings, which are used to help understand various details of the present disclosure. It should be noted that various specific details are set forth in the following description in order to provide a thorough understanding of the present disclosure. Thus, it can be apparent to those skilled in the art that the present disclosure can be practiced without such specific details. In other instances, well-known structures and functions are not described in detail in order to avoid obscuring the present disclosure.

[0029] As used herein, the terms "comprises," "comprising," "includes," "including," "has," "having," "contains," "containing," or variations thereof, are intended to mean a non-exclusive inclusion. Unless specifically set forth herein, the terms "or" and "and" are used in their inclusive sense (and not in their exclusive sense). The term "based on" is used in the sense of "based, at least in part, on." The terms "one example embodiment" and "an example embodiment" are utilized throughout the specification to mean that a particular feature, structure, or characteristic has been described in one or more embodiments, and is included, but is not necessarily included, in all embodiments. The term "another embodiment" is used throughout the specification to mean that a particular feature, structure, or characteristic has been described in one or more embodiments, and is included, but is not necessarily included, in all embodiments. The terms "first," "second," and the like are used to describe various objects throughout the specification, and are not necessarily used to denote numbering of the objects. Other definitions can be found throughout the specification.

[0030] As described previously, the growing access demand makes the opening of multiple access relationships involved in the operation and maintenance scene of the data center, and the opening of each access relationship may involve the configuration modification of multiple devices. The traditional operation and maintenance tool usually runs in a network device-oriented manner. The traditional operation and maintenance method or tool usually configures each network device separately. This configuration mode causes the device to lack the perception of global topology information, and thus the traditional network operation and maintenance method is difficult to meet the configuration requirements of multiple devices and complex scenarios in the data center operation and maintenance scene. In summary, the deficiency of the traditional network operation and maintenance method is that it is difficult to meet the automated operation and maintenance requirements in multiple device and complex scenarios.

[0031] To at least partially solve one or more of the above problems and other potential problems, example embodiments of the present disclosure propose a scheme for network operation and maintenance. In the scheme of the present disclosure, by responding to the retrieval of operation and maintenance requirement instructions, the global network topology information and access relationship information are obtained, the access relationship information includes access relationship information about at least one access relationship, and the access relationship information at least indicates the start point and the end point in the access path corresponding to the access relationship; based on the access relationship information, the topology information of each access relationship is generated, the topology information of one access relationship at least indicates the access path corresponding to the access relationship and the device information of all devices in the access path; based on the topology information of each access relationship, the configuration task corresponding to each access relationship is obtained; and the configuration task corresponding to each access relationship is executed in parallel. The present disclosure can generate the topology information of each access relationship according to the access relationship of the global network, only through the start point and the end point in the access path corresponding to each access relationship, so as to realize the acquisition and parallel execution of the configuration task corresponding to all devices on the access path corresponding to the access relationship with the access relationship as the object, effectively improving the network configuration efficiency. In addition, the present disclosure can also obtain the execution result of all configuration tasks, so as to aggregate the execution result for indicating the configuration state of the network; realize the centralized display of the configuration task execution result, and provide good guidance for improving the configuration efficiency. Therefore, the present disclosure can improve the network configuration efficiency, thereby meeting the automated operation and maintenance requirements in multiple device and complex scenarios.

[0032] Figure 1 A schematic diagram of a system 100 for implementing the method for network operation and maintenance according to the embodiments of the present disclosure is shown. As shown in Figure 1 The system 100 includes a computing device 110 and an access relationship information providing device 130 and a network 140. The computing device 110 and the access relationship information providing device 130 can interact data through the network 140 (for example, the Internet).

[0033] The access relationship information providing device 130, for example, can store a plurality of different types of access relationship information data, such as access path information corresponding to an access relationship, device information on an access path corresponding to an access relationship, topology information corresponding to an access relationship, and the like; and the access relationship information providing device 130 can generate a digital file in a specific format, such as a data table, about access relationship information according to a plurality of different types of access relationship information data sources stored therein, the format of which is not limited to xls, xlsx, accdb, txt, csv, word, dat, mdf, mdb, db, dbf, wdb, and the like, and the digital file can present access relationship information and / or can be applied to the access relationship information providing device 130, and the access relationship information providing device 130 converts data in the above format digital file into a specific format so as to interface with an access relationship information database in the access relationship information providing device 130 or with the computing device 110; and the type of the specific format to be converted can also be determined according to the device conditions and use requirements of the actual scene. In addition, the specific data source format can be dynamically adjusted according to the access relationship information required by the user. The access relationship information providing device 130 can also provide access relationship information to the computing device 110.

[0034] As for the computing device 110, for example, it is configured to, in response to retrieving an operation and maintenance requirement instruction, acquire network topology information and acquire access relationship information from the access relationship information providing device 130, the access relationship information including access relationship information about at least one access relationship, the access relationship information at least indicating a start point and an end point in an access path corresponding to the access relationship; based on the access relationship information, generating topology information of each access relationship, the topology information of one access relationship at least indicating an access path corresponding to the one access relationship and device information of all devices in the access path; based on the topology information of each access relationship, acquiring a configuration task corresponding to each access relationship; and executing the configuration task corresponding to each access relationship in parallel. The computing device 110 can also acquire execution results of all configuration tasks so as to aggregate the execution results for indicating a configuration state of the network. The computing device 110 can have one or more processing units, including special-purpose processing units such as GPU, FPGA, and ASIC, and general-purpose processing units such as CPU. In addition, one or more virtual machines can also be running on each computing device 110. In some embodiments, the computing device 110 and the access relationship information providing device 130 can be integrated together or can be separately arranged from each other. In some embodiments, the computing device 110, for example, includes an information acquisition module 112, a topology information generation module 114, a configuration task acquisition module 116, a configuration task execution module 118, and a configuration result analysis module 120.

[0035] Regarding the information acquisition module 112, it is used to confirm whether an operation and maintenance requirement instruction has been retrieved; if an operation and maintenance requirement instruction has been retrieved, the entire network topology information and access relationship information are obtained. The access relationship information includes access relationship information about at least one access relationship, and the access relationship information at least indicates the start and end points in the access path corresponding to the access relationship.

[0036] Regarding the topology information generation module 114, it is used to generate topology information for each access relationship based on the access relationship information. The topology information of an access relationship at least indicates the access path corresponding to the access relationship and the device information of all devices in the access path.

[0037] Regarding the configuration task acquisition module 116, it is used to acquire the configuration task corresponding to each access relationship based on the topology information of each access relationship.

[0038] Regarding the configuration task execution module 118, it is used to execute the configuration task corresponding to each access relationship in parallel.

[0039] Regarding the configuration result analysis module 120, it is used to obtain the execution results of all configuration tasks so as to aggregate the execution results to indicate the configuration status of the network.

[0040] Figure 2 A flowchart of a method 200 for network operation and maintenance according to an embodiment of the present disclosure is shown. Figure 8 A schematic diagram illustrating the principles of network configuration concurrency is shown below. Figure 2 and Figure 8 Method 200 will be described below. Method 200 can be derived from, for example... Figure 1 The computing device 110 shown can be used for execution, and can also be used in Figure 10 The method is performed at the illustrated electronic device 1000. It should be understood that method 200 may also include additional steps not shown and / or the steps shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0041] In step 202, if the computing device 110 retrieves the operation and maintenance requirement instruction, it obtains the network topology information and access relationship information. The access relationship information includes access relationship information about at least one access relationship, and the access relationship information at least indicates the start and end points in the access path corresponding to the access relationship.

[0042] Regarding operation and maintenance requirement instructions, they include at least pre-set scheduled task instructions based on operation and maintenance requirements, operation and maintenance requirement instructions imported by operation and maintenance personnel, and operation and maintenance requirement instructions entered by operation and maintenance personnel in real time; these operation and maintenance requirement instructions can be pre-set and adjusted according to network information and status, as well as actual configuration requirements.

[0043] Before obtaining the whole network topology information and the access relationship information, the computing device 110 can call the configuration file to initialize the whole network topology information data source, so as to convert the whole network topology information data into a specific structured format, so as to facilitate the storage, reading, calling and processing of the topology information data; at the same time, the access relationship information providing device 130 can also call the configuration file to initialize the access relationship information data source, and convert the access relationship information data into a specific structured format, so as to facilitate the storage, reading, calling and processing of the access relationship information data.

[0044] As for the access relationship information, for example, the access relationship information of at least one access relationship can be stored in the form of a data table, and for each piece of access relationship information, the corresponding access path information (such as the nodes in the access path, the node device information, etc.), the association information with other access relationships, etc. can be included; it should be noted that the access relationship information of an access relationship needs to at least include the starting point and the ending point in the access path corresponding to the access relationship, so that the computing device 110 can obtain the access path corresponding to the access relationship according to the node information of the access path corresponding to the access relationship, and the information of all nodes in the corresponding access path.

[0045] As for the starting point and the ending point in the access path, the starting point and the ending point are only two nodes that an access path needs to include at least, each node corresponds to a device, and the configuration task performed by the network configuration also targets the device of each node; in the data center scenario, the access path usually contains at least three nodes, the starting point, the ending point and the firewall node.

[0046] As for the whole network topology information, it needs to be defined in advance, such as defining each device in the whole network, the relationship between the devices and each transmission medium, etc. The whole network topology information at least includes the topology structure of the whole network, the device information of all devices, the connection relationship between the devices, the transmission medium, the data transmission line information and the configuration task screening condition, the execution condition information, etc.

[0047] In step 204, the computing device 110 generates the topology information of each access relationship based on the access relationship information, and the topology information of an access relationship at least indicates the access path corresponding to the access relationship and the device information of all devices in the access path.

[0048] As for the topology information of an access relationship, it can also include all transmission media, connection line information, node position information in the access path corresponding to the access relationship, and configuration task screening condition, execution condition information of each device, etc.

[0049] The device information can at least include the device model of the current device, location information, interface information, and connection information and association relationship with other devices.

[0050] The topology information of each access relationship is generated based on the access relationship information, for example, refer to Figure 8 The access relationship information a includes three access relationships a1, a2 and a3, and the topology relationship p1 of the access relationship a1, the topology relationship p2 of the access relationship a2 and the topology relationship p3 of the access relationship a3 are generated respectively. The above scheme realizes concurrent configuration based on access relationship, so as to realize concurrent configuration of network devices based on access relationship.

[0051] In step 206, the computing device 110 obtains the configuration task corresponding to each access relationship based on the topology information of each access relationship.

[0052] The configuration task can be pre-recorded according to the situation and demand of each device. The configuration task corresponding to an access relationship at least includes the operation that each device on the access path corresponding to the access relationship needs to perform. The operation can be customized, and the address information of the corresponding device can be sent to the trigger device to perform the operation. The operation to be performed at least includes performing some filtering conditions, such as filtering the shortest path of multiple devices, whether the path contains a certain device, judging whether two devices are connected, returning the path information of the connected two devices, etc.

[0053] In step 208, the computing device 110 executes the configuration task corresponding to each access relationship in parallel.

[0054] The configuration task corresponding to an access relationship is obtained, and the configuration task corresponding to an access relationship is executed in parallel, for example, refer to Figure 8 The configuration tasks T a1 , T a2 and T a3 corresponding to the access relationships a1, a2 and a3 are generated based on the topology relationships p1, p2 and p3 respectively; the configuration tasks T a1 , T a2 and T a3 corresponding to the access relationships a1-a3 are executed in parallel; the above scheme realizes parallel configuration of the devices on the access path corresponding to each access relationship based on the access relationship of the operation and maintenance demand, instead of separate configuration based on a single device, which greatly improves the association between devices, makes the configuration more compatible, and improves the configuration efficiency.

[0055] At step 210, the computing device 110 obtains the execution results of all configuration tasks, so as to aggregate the execution results for indicating the configuration state of the network.

[0056] Regarding the execution result, the execution result of the configuration task corresponding to one access relationship includes the configuration state of the device of each node on the access path corresponding to the one access relationship, such as configuration success, configuration failure, current configuration state, etc.

[0057] In the above scheme, for the access relationship information, the topology information of each access relationship can be generated only by the start point and the end point in the access path corresponding to each access relationship, and the information of all node devices on the access path corresponding to each access relationship can be obtained, so as to realize the network configuration taking the access relationship as the object, and effectively improve the network configuration efficiency. In addition, the execution results of all configuration tasks can be obtained, so as to aggregate the execution results to realize the indication of the configuration state of the network, and provide good guidance for the operation and maintenance personnel. Therefore, the method 200 for network operation and maintenance provided by the embodiment of the present disclosure can improve the network configuration efficiency, so as to meet the automatic operation and maintenance demand in the multi-device and complex scene.

[0058] Figure 3 A flowchart of a method 300 for parallel execution of sub-configuration tasks according to an embodiment of the present disclosure is shown. The following will be described in combination with Figure 3 and Figure 8 The method will be described. The method 300 can be executed by the computing device 110 as shown in Figure 1 , or can be executed at the electronic device 1000 as shown in Figure 10 . It should be understood that the method 300 can also include additional steps not shown and / or can omit the steps shown, and the scope of the present disclosure is not limited in this respect.

[0059] At step 302, the computing device 110 obtains, based on the configuration task corresponding to each access relationship, the sub-configuration task corresponding to each device in the access path corresponding to each access relationship.

[0060] Regarding the sub-configuration task, please refer to Figure 8 , for example, the access relationship information a obtained includes three access relationships a1, a2, and a3, and the configuration task T a1 , the configuration task T a2 , and the configuration task T a3 are respectively generated according to the topology information p1-p3 of the three access relationships; wherein the node devices in the access path corresponding to the access relationship a1 are Z0, Z1, Z2, and Z3, and the sub-configuration tasks of the devices Z0-Z3 about the access relationship a1 are generated, for example, the sub-configuration task Ta1-Z0 , T a1-Z1 , T a1-Z2 , and T a1-Z3 ; the node devices in the access path corresponding to the access relationship a2 are Z1, Z3, and Z5, and the sub-configuration tasks of the devices Z1, Z3, and Z5 with respect to the access relationship a2 are generated according to the access relationship a2; the node devices in the access path corresponding to the access relationship a3 are Z0, Z3, Z4, Z5, and Z6, and the sub-configuration tasks of the devices Z0, Z3, Z4, Z5, and Z6 with respect to the access relationship a3 are generated according to the access relationship a3; it should be noted that the same device can be involved in multiple access relationships, that is, the same device can be included in different access paths, such as the node device Z3 included in the access paths a1, a2, and a3; therefore, there can be multiple sub-configuration tasks for the same device.

[0061] In step 304, the computing device 110 executes all the sub-configuration tasks of any one of the at least one access relationship in parallel.

[0062] For the parallel execution of all the sub-configuration tasks of any one access relationship, please refer to Figure 8 , for example, in the above access relationship information a, the configuration tasks T a1 , T a2 , and T a3 corresponding to the access relationships a1, a2, and a3 are executed in parallel; and these configuration tasks have multiple sub-configuration tasks, respectively; for example, all the sub-configuration tasks in the access relationships a1, a2, and a3 are executed in parallel, that is, all the sub-configuration tasks of the devices Z0, Z1, Z2, Z3, Z4, Z5, and Z6 are executed in parallel; the above method realizes the concurrent generation of sub-configuration tasks and the concurrent execution of sub-configuration tasks.

[0063] In step 306, the computing device 110 determines whether the same device needs to execute multiple sub-configuration tasks.

[0064] For example, please refer to Figure 8 , the device Z3 is involved in the access relationships a1, a2, and a3, and therefore the device Z3 is a node on the three access paths corresponding to the access relationships a1, a2, and a3, and three sub-configuration tasks are generated for the device Z3. When each node device has only one sub-configuration task, all the sub-configuration tasks can be executed in parallel in the actual execution process; however, when the same node device has multiple sub-configuration tasks, the same device can not be able to perform multiple configuration tasks simultaneously in the actual configuration process, and therefore it is necessary to determine whether the same device needs to execute multiple sub-configuration tasks and the execution order of the multiple sub-configuration tasks of the same device in the actual execution process of the configuration tasks.

[0065] At step 308, if the computing device 110 determines that the same device needs to perform multiple sub-configuration tasks, the multiple sub-configuration tasks of the same device are performed according to a predetermined execution order rule.

[0066] At step 310, if the computing device 110 determines that the same device does not need to perform multiple sub-configuration tasks, the sub-configuration tasks are performed in parallel.

[0067] As for the predetermined order rule, for example, it can be first-come-first-served according to the time when the same device actually receives the sub-configuration task, or it can be according to the associated order between the access relations, for example, the execution order rule of the access relations a1, a2 and a3 with respect to the same node device task is a1>a2>a3, or it can be determined according to the operation and maintenance task demand in the actual scene.

[0068] In some embodiments, the computing device 110 can also call the task template corresponding to the device in the access path based on the pre-entered task library and the device information of the device, so as to generate the sub-configuration task corresponding to each device in the access path; and

[0069] The sub-configuration task at least includes an information collection task, a configuration backup task and a configuration delivery task.

[0070] As for the task template, multiple nodes in the access path can be involved, and the model, manufacturer and other information of each node device can be different, which leads to different compatible configuration task file formats of different node devices; as for the pre-entered task library, the task library at least includes the template of the task, the type of the node and / or the task parameters corresponding to the node device, and can realize automatic differential configuration of multiple devices, thereby improving the configuration efficiency.

[0071] The above scheme realizes the concurrency of operation and maintenance demand tasks. First, according to the access relationship information, access relationship information of each access relationship is acquired in parallel. Then, based on the whole network topology information, the topology relationship of each access relationship is generated in parallel according to the access relationship information of each access relationship, taking the access relationship as the object. Based on the topology relationship of each access relationship, the configuration task corresponding to each access relationship is generated in parallel. Then, based on the access path node information, all node devices on the access path corresponding to the access relationship are taken as the object, and the sub-configuration task of all node devices in each access relationship is generated in parallel. Finally, the sub-configuration task of any access relationship in at least one access relationship is executed in parallel. The above method for network operation and maintenance performs multiple concurrent operations in each link of the configuration task generation based on the access relationship information, taking the access relationship and the node device in the path corresponding to the access relationship as the object, which greatly improves the efficiency of network configuration, and can consider the correlation between the devices that need to be configured, so that efficient and high-quality network configuration is realized when dealing with network operation and maintenance demands.

[0072] Figure 4 A flowchart of a method 400 for configuration task execution result indication according to an embodiment of the present disclosure is shown, Figure 9 A schematic diagram of network configuration state indication according to an embodiment of the present disclosure is shown, and the method 400 will be described below in combination with Figure 4 、 Figure 8 and Figure 9 The method 400 can be executed by the computing device 110 as shown in Figure 1 , or can be executed at the electronic device 1000 as shown in Figure 10 . It should be understood that the method 400 can also include additional steps not shown and / or can omit the steps shown, and the scope of the present disclosure is not limited in this respect.

[0073] In step 402, the computing device 110 acquires the execution result of each sub-configuration task.

[0074] For example, referring to Figure 8 and Figure 9 , the execution results of all sub-configuration tasks of the access relationships a1, a2 and a3 are acquired.

[0075] In step 404, the computing device 110 associates each sub-configuration task execution result with the access relationship based on the execution result of each sub-configuration task.

[0076] In step 406, the computing device 110 aggregates the execution results of all sub-configuration tasks performed by the same device based on the association of each sub-configuration task execution result with the access relationship, so as to indicate the configuration state of the network based on the aggregated execution result.

[0077] For each sub-configuration task execution result and access relationship, and aggregation of all sub-configuration task execution results performed by the same device, for example, refer to Figure 9 In Figure 9 , the above Figure 8 The configuration task execution results corresponding to the access relationships a1, a2 and a3 shown in the above Figure 9 , taking the node device as a set, the configuration task execution results are associated with the access relationships, the execution results of each sub-configuration task are displayed, and the indication of the network configuration state is realized; for example, device Z0, regarding access relationship a1 - configuration success, regarding access relationship a2 - configuration failure; it should be noted that In

[0078] , only the sub-configuration task execution results of part of the node devices corresponding to the access relationships a1, a2 and a3 are shown, and only one execution result and access relationship association method is indicated. In actual use, other methods can be used for result association and configuration state indication, and other aggregation methods can be used to aggregate the execution results of sub-configuration tasks.

[0079] Figure 5 A flowchart of a method 500 for sub-configuration task re-execution according to an embodiment of the present disclosure is shown. The method 500 can be performed by a computing device 110 as shown in Figure 1 , or can be performed at an electronic device 1000 as shown in Figure 10 . It should be understood that the method 500 can also include additional steps not shown and / or the steps shown can be omitted, and the scope of the present disclosure is not limited in this regard.

[0080] In step 502, the computing device 110 obtains an error code fed back by a device corresponding to a sub-configuration task with a failed execution result.

[0081] In step 504, the computing device 110 associates the error code fed back by the device with the corresponding sub-configuration task and aggregates it to the execution result.

[0082] For example, in Figure 9 , the sub-configuration task of device Z0 regarding access relationship 3 is "access relationship a3 - configuration failure", and its error code is "xxxZ0a3xxx", which is used to indicate the reason for the configuration failure of device Z0.

[0083] In step 506, computing device 110 determines whether a device error code has been detected. If computing device 110 does not detect a device error code, it proceeds to step 502.

[0084] In step 508, if the computing device 110 detects an error code of the device, it re-executes the sub-configuration task for the device corresponding to the error code according to the predetermined error handling rules.

[0085] Regarding the pre-defined error handling rules, various error code handling rules can be pre-entered according to the error reasons corresponding to each error code, so that the computing device 110 can automatically debug the node device that has an error in response to the error code, or automatically generate a new sub-configuration task according to the error code debugging configuration parameters, so as to re-execute the sub-configuration task for the node device that has failed to configure.

[0086] The above solution enables the identification of error reasons in node devices where sub-configuration tasks fail, facilitating timely debugging and re-execution of failed sub-configuration tasks, thereby improving configuration efficiency.

[0087] Figure 6 A flowchart of a method 600 for determining access relationship topology information according to an embodiment of the present disclosure is shown. Method 600 may be derived from, for example... Figure 1 The computing device 110 shown can be used for execution, and can also be used in Figure 10 The method is performed at the illustrated electronic device 1000. It should be understood that method 600 may also include additional steps not shown and / or the steps shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0088] In step 602, the computing device 110 determines the access path corresponding to each access relationship based on the nodes included in each access relationship information.

[0089] For each access relationship, the nodes included must at least have their node IDs or device IDs to facilitate obtaining device information. For example, access relationship a1 includes nodes Z0 and Z3, while access relationship a3 includes nodes Z0, Z5, and Z6. It's important to note that typically, at least the start and end points of the access path corresponding to the access relationship must be included to determine an access path; however, more nodes can also be included.

[0090] In step 604, computing device 110 determines all devices involved in each access relationship based on the access path corresponding to each access relationship.

[0091] After determining the access path, all nodes of the access path can be obtained, so that after determining one access path, all devices involved in the access relationship corresponding to the one access path can be determined; for example, after determining the access path "Z0→Z1→Z2→Z3", it can be determined that all devices involved in the access relationship a1 are the four devices "Z0, Z1, Z2 and Z3".

[0092] In step 606, the computing device 110 obtains device information of all devices involved in each access relationship, and the device information at least includes device model, location information, interface information and connection information with other devices of the current device.

[0093] As to the connection information with other devices, at least includes the connection relationship between devices, specific connection mode, connection interface information and transmission medium information; it should be noted that the connection information with other devices here is not limited to connecting devices in the whole network, but also can be connecting devices to external network.

[0094] As to the transmission line, when the device at the edge of the internal network topology needs to connect external devices, external transmission medium such as external line is usually used; for this, the present scheme provides an additional dedicated line information, so as to distinguish the external line from other internal devices and lines when initializing the topology of the whole network; thus, when the configuration task fails, if the error reason is the external dedicated line, the internal network operation and maintenance obviously cannot solve these problems, and can only alarm and prompt to remind the operator of the external network dedicated line to solve the related problems.

[0095] For example, the storage of the dedicated line information can be in the form of a data table, which can include dedicated line number, dedicated line operator, vlan number, dedicated line type, dedicated line bandwidth, local end name, local end dedicated line port, local end dedicated line port address, opposite end name, opposite end dedicated line port address and other information; among them, the dedicated line number, dedicated line operator, vlan number, dedicated line type and dedicated line bandwidth are mandatory, the titles starting with "local end" and "opposite end" are initialized as a center and a branch of the dedicated line one end class, and the dedicated line one end name and dedicated line port address are mandatory, and the dedicated line interface and other information can be expanded according to actual situation; the external line can be screened and judged through the configuration task, such as judging whether there is a conflict vlan number according to the key field, line number, judging conflict IP and the like.

[0096] The above scheme can determine the complete access path corresponding to each access relationship according to the path nodes included in each access relationship information, obtain the device information of all node devices, and provide separate management and processing of external lines, so as to enable the operation and maintenance personnel to confirm the reason for the configuration failure in time, exclude the problems caused by non-internal reasons in time, and improve the operation and maintenance efficiency.

[0097] Figure 7 A flowchart of a method 700 for determining an access path according to an embodiment of the present disclosure is shown. The method 700 can be performed by the computing device 110 as shown, or can also be performed at the electronic device 1000 as shown. It should be understood that the method 700 can also include additional steps not shown and / or can omit steps shown, and the scope of the present disclosure is not limited in this respect. Figure 1 Figure 10 The method 700 can be performed by the computing device 110 as shown, or can also be performed at the electronic device 1000 as shown. It should be understood that the method 700 can also include additional steps not shown and / or can omit steps shown, and the scope of the present disclosure is not limited in this respect.

[0098] At step 702, the computing device 110 is configured to determine the number of access paths that exist based on the nodes in an access relationship.

[0099] At step 704, if the computing device 110 determines that there is only one access path based on the nodes in an access relationship, the only one access path is determined as the access path corresponding to the access relationship.

[0100] At step 706, if the computing device 110 determines that there are at least two access paths based on the nodes in an access relationship, one access path is determined from the at least two access paths that exist as the access path corresponding to the access relationship according to a predetermined path determination rule.

[0101] Regarding the predetermined path determination rule, the rule for how to determine the access path when there are at least two access paths for an access relationship can be pre-entered according to requirements, for example, a node priority rule can be set, and a path with high node priority in the path is selected as the access path; the node priority can be determined or adjusted according to factors such as network state, device hardware state, node association relationship, access relationship type, etc., or the node priority can be dynamically adjusted according to the execution success rate of a sub-configuration task; the above node priority rules can all be set in the topology information.

[0102] At step 708, if the computing device 110 determines that there is no access path based on the nodes in an access relationship, an indication information indicating that the path confirmation fails is returned.

[0103] Regarding when it is determined that there is no access path, alarm information can also be returned to prompt the operation and maintenance personnel that there is no access path, and the access relationship information needs to be adjusted. This situation can be caused by problems in the node information provided in the access relationship information, such as too few numbers, missing key nodes, etc., resulting in no path.

[0104] ​Through the above scheme, the path node of the access relationship with incomplete path node information in the access relationship information can be completed, so as to obtain the corresponding complete access path, all nodes on the access path, and the information of the devices where the nodes are located. In addition, for the access relationship information without an access path, the problem of the access relationship can be fed back in time to prompt the operation and maintenance personnel, thereby improving the operation and maintenance efficiency.

[0105] The above scheme can be implemented by some databases and operation and maintenance management tools in combination with Figure 8 , for example, by means of an Access database, a task configuration module, a controller, and an operation and maintenance tool. The specific implementation manner can be: initializing the whole network topology information by calling a configuration file such as an InitController function, specifically, initializing path information, device information, and private line information, and returning a Controller object containing the whole network topology information after initialization; storing the access relationship information by means of an access object, initializing the access object by calling a load_access function, the access object can be a list object, each access object is an access relationship, and the Controller object of the whole network topology information is filtered to generate the whole network topology information corresponding to each access relationship when each access relationship is initialized; generating the configuration task of each access relationship and the sub-configuration task of each device in the corresponding access path by calling a task function according to the whole network topology relationship of each access relationship by means of a task configuration module; and determining whether the configuration is correct by checking whether the data packet output by the front node and the data packet input by the rear node in the same access path are consistent when the configuration is performed, for example, referring to the access relationship a2 shown in Figure 8 , which involves nodes Z1, Z3, and Z5, and the access path thereof is “Z1→Z3→Z5”. The data packet output after passing through the Z1 node is the same as the data packet input by the Z3 node, and the data packet output after passing through the Z3 node is the same as the data packet input by the Z5 node. Whether the configuration of a certain device in a certain access relationship is successful can be confirmed by checking the similarity of the data packets. The data packet information that can be encountered in the configuration task can be pre-recorded in the corresponding access relationship information.

[0106] Finally, the execution results of all the configuration tasks are returned. It should be known that, when actually implementing the operation and maintenance method provided by the present disclosure, the database, operation and maintenance tool, plug-in, and the like used for deploying the operation and maintenance method 200-700 can be determined according to the actual whole network database state, device model, system type, and the like.

[0107] Figure 10A schematic block diagram of an example electronic device 1000 that can be used to implement embodiments of the present disclosure is shown. For example, the computing device 110 can be implemented by the electronic device 1000 as shown. Figure 1 The computing device 110 shown can be implemented by the electronic device 1000. As shown, the electronic device 1000 includes a central processing unit (CPU) 1001 that can perform various appropriate actions and processes according to computer program instructions stored in a read-only memory (ROM) 1002 or loaded into a random access memory (RAM) 1003 from a storage unit 1008. Various programs and data required by the electronic device 1000 to operate can also be stored in the random access memory 1003. The central processing unit 1001, the read-only memory 1002, and the random access memory 1003 are connected to each other through a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0108] Various components in the electronic device 1000 are connected to the input / output interface 1005, including an input unit 1006, such as a keyboard, a mouse, a microphone, etc.; an output unit 1007, such as various types of displays, speakers, etc.; a storage unit 1008, such as a magnetic disk, a magneto-optical disk, etc.; and a communication unit 1009, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 1009 allows the device 1000 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.

[0109] The various processes and procedures described above, such as the methods 200-700, can be performed by the central processing unit 1001. For example, in some embodiments, the methods 200-700 can be implemented as a computer software program that is tangibly embodied in a machine-readable medium, such as the storage unit 1008. In some embodiments, portions or all of the computer program can be loaded and / or installed onto the device 1000 via the read-only memory 1002 and / or the communication unit 1009. When the computer program is loaded into the random access memory 1003 and executed by the central processing unit 1001, one or more actions of the methods 200-700 described above can be performed.

[0110] The present disclosure relates to methods, apparatus, systems, electronic devices, computer readable storage media, and / or computer program products. The computer program product can include computer readable program instructions for executing various aspects of the present disclosure.

[0111] Computer readable storage media can be tangible storage media which can retain and store instructions for use by an instruction execution device. Computer readable storage media can be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer readable storage media include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

[0112] Computer readable program instructions described herein can be downloaded to respective computing / processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network can comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing / processing device.

[0113] Computer readable program instructions for carrying out operations of the present disclosure can be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate array (FPGA), or programmable logic array (PLA) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.

[0114] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0115] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0116] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0117] The flow and step diagrams in the drawings show architectural, functional and operational architectures of possible implementations of systems, methods and computer program products according to the various embodiments of the present disclosure. In this regard, each block in the flow and step diagrams can represent a module, a segment, or a portion of instructions which comprise one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may

[0118] Embodiments of the present disclosure have been described above, and the description is intended to be illustrative of the various embodiments of the disclosure and not exhaustive. Numerous modifications and adaptations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The scope of the disclosure is defined by the appended claims and equivalents thereof. The choice of words in the description is intended to best explain the principles of the embodiments of the present disclosure, the practical application of the embodiments of the present disclosure, or the improvement over the technology in the art, or to enable others skilled in the art to understand the embodiments of the present disclosure disclosed herein.

Claims

1. A method for network operation and maintenance, comprising: In response to a retrieved operation and maintenance request command, the system obtains network topology information and access relationship information. The access relationship information includes access relationship information about at least one access relationship, and the access relationship information at least indicates the start and end points of the access path corresponding to the access relationship. Based on the access relationship information, topology information for each access relationship is generated. The topology information for each access relationship at least indicates the access path corresponding to the access relationship and the device information of all devices in the access path. Based on the topology information of each access relationship, obtain the configuration task corresponding to each access relationship; Parallel execution of configuration tasks corresponding to each access relationship includes: parallel execution of all sub-configuration tasks of any one of the at least one access relationship; in response to determining that multiple sub-configuration tasks need to be executed for the same device, executing multiple sub-configuration tasks for the same device according to a predetermined execution order rule; and Obtain the execution results of all configuration tasks so that the results can be aggregated to indicate the configuration status of the network.

2. The method according to claim 1, wherein executing the configuration task corresponding to each access relationship in parallel includes: Based on the configuration task corresponding to each access relationship, obtain the sub-configuration task corresponding to each device in the access path corresponding to each access relationship.

3. The method according to claim 2, wherein obtaining the sub-configuration task corresponding to each device in the access path corresponding to each access relationship includes: Based on the pre-entered task library and device information, the task template corresponding to the device in the access path is called to generate a sub-configuration task for each device in the access path. as well as The sub-configuration tasks include at least an information collection task, a configuration backup task, and a configuration distribution task.

4. The method of claim 2, wherein obtaining the execution results of all configuration tasks to aggregate the execution results for indicating the network configuration status includes: Obtain the execution result of each sub-configuration task; Based on the execution result of each sub-configuration task, associate the execution result of each sub-configuration task with the access relationship; Based on the association between the execution result of each sub-configuration task and the access relationship, the execution results of all sub-configuration tasks executed on the same device are aggregated so as to indicate the network configuration status based on the aggregated execution results.

5. The method according to claim 4, further comprising: Get the error code returned by the device corresponding to the sub-configuration task that failed to execute; Associate the error codes reported by the device with the corresponding sub-configuration tasks and aggregate them into the execution result; as well as In response to the detection of a device error code, the sub-configuration task is re-executed for the device corresponding to the error code according to the predefined error handling rules.

6. The method according to claim 1, wherein generating topology information for each access relationship based on the access relationship information comprises: Based on the nodes included in each access relationship information, determine the access path corresponding to each access relationship; Based on the access path corresponding to each access relationship, determine all devices involved in each access relationship; as well as Obtain device information for all devices involved in each access relationship. The device information includes at least the device model, location information, interface information, and connection information with other devices of the current device.

7. The method according to claim 6, wherein determining the access path corresponding to each access relationship based on the nodes included in each access relationship information includes: If it is determined that there is only one access path based on the nodes in an access relationship, then the only existing access path is determined as the access path corresponding to the access relationship. If at least two access paths are determined based on nodes in an access relationship, then according to a predetermined path determination rule, one access path is determined from the at least two existing access paths as the access path corresponding to the access relationship. as well as If it is determined that no access path exists based on a node in an access relationship, an indication message is returned to indicate that the path confirmation failed.

8. A computing device, comprising: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

9. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method of any one of claims 1-7.

Images