CN115714712A - Method, computing device and storage medium for network operation and maintenance - Google Patents

Method, computing device and storage medium for network operation and maintenance Download PDF

Info

Publication number
CN115714712A
CN115714712A CN202211326299.0A CN202211326299A CN115714712A CN 115714712 A CN115714712 A CN 115714712A CN 202211326299 A CN202211326299 A CN 202211326299A CN 115714712 A CN115714712 A CN 115714712A
Authority
CN
China
Prior art keywords
access
information
configuration
relation
sub
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211326299.0A
Other languages
Chinese (zh)
Inventor
王永韬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp Shanghai Branch
Original Assignee
China Construction Bank Corp Shanghai Branch
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp Shanghai Branch filed Critical China Construction Bank Corp Shanghai Branch
Priority to CN202211326299.0A priority Critical patent/CN115714712A/en
Publication of CN115714712A publication Critical patent/CN115714712A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Embodiments of the present disclosure relate to a method, computing device, and storage medium for network operations and maintenance. Responding to an operation and maintenance demand instruction retrieved, and acquiring whole network topology information and access relation information; the access relation information comprises access relation information about at least one access relation and at least indicates a starting point and an end point in an access path corresponding to the access relation; generating topology information of each access relation based on the access relation information; one piece of topology information at least indicates an access path corresponding to one access relationship and equipment information of all equipment in the path; acquiring a configuration task corresponding to each access relation based on the topology information of each access relation; executing the configuration tasks corresponding to each access relation in parallel; and acquiring the execution results of all the configuration tasks so as to aggregate the execution results for indicating the configuration state of the network. Therefore, the network configuration efficiency can be improved, and the automatic operation and maintenance requirements under the complex scene with multiple devices can be met.

Description

Method, computing device and storage medium for network operation and maintenance
Technical Field
Embodiments of the present disclosure relate generally to the field of network communication technologies, and in particular, to a method, a computing device, and a storage medium for network operation and maintenance.
Background
The traditional operation and maintenance tool generally operates in a network device oriented manner, and such traditional operation and maintenance method or tool generally configures each network device individually, and can obtain a very good effect when processing devices with simple models such as an access layer switch, or in a scene with a single configuration.
However, with the rapid development of internet application technology, communication technology, and data processing technology, the demand for network access has increased explosively. The increasing access requirements make the operation and maintenance of the data center face a great challenge. In the operation and maintenance scene of the data center, the opening of the network access relationship is an important ring. The opening of one access relationship may involve configuration modifications of multiple devices, while hundreds or thousands of access relationships may be opened for a data center each day. Because a single network device lacks perception of global topology information, under the task of opening access relationships, the operation and maintenance tool facing the device cannot meet the increasingly complex requirements of automation operation and maintenance of the east-west direction (namely, flow among devices in a data center).
In summary, the conventional network operation and maintenance method has the following disadvantages: the requirement of automation operation and maintenance under multiple devices and complex scenes is difficult to meet.
Disclosure of Invention
In order to solve the above problems, the present disclosure provides a method, a computing device, and a storage medium for network operation and maintenance, which can improve network configuration efficiency and meet the requirements of automation operation and maintenance in a multi-device and complex scenario.
According to a first aspect of the present disclosure, there is provided a method for network operation and maintenance, comprising: responding to an operation and maintenance requirement retrieval instruction, acquiring full-network topology information and access relation information, wherein the access relation information comprises access relation information about at least one access relation, and the access relation information at least indicates a starting point and an end point in an access path corresponding to the access relation; generating topology information of each access relation based on the access relation information, wherein the topology information of one access relation at least indicates an access path corresponding to the access relation and equipment information of all equipment in the access path; acquiring a configuration task corresponding to each access relation based on the topological information of each access relation; executing the configuration tasks corresponding to each access relation in parallel; and acquiring execution results of all the configuration tasks so as to aggregate the execution results for indicating the configuration state of the network.
According to a second aspect of the present disclosure, there is provided a computing device comprising: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first aspect of the disclosure.
In a third aspect of the present disclosure, a non-transitory computer readable storage medium is provided having stored thereon computer instructions for causing a computer to perform the method of the first aspect of the present disclosure.
In some embodiments, executing the configuration task corresponding to each access relationship in parallel includes: acquiring a sub-configuration task corresponding to each device in an access path corresponding to each access relation based on the configuration task corresponding to each access relation; and executing all the sub-configuration tasks of any access relation in the at least one access relation in parallel.
In some embodiments, the obtaining the sub-configuration task corresponding to each device in the access path corresponding to each access relationship includes: based on a pre-entered task library and equipment information of the equipment, calling a task template corresponding to the equipment in the access path so as to generate a sub-configuration task corresponding to each equipment in the access path; and the sub-configuration tasks at least comprise an information acquisition task, a configuration backup task and a configuration issuing task.
In some embodiments, obtaining the execution results of all the configuration tasks so as to aggregate the execution results for indicating the configuration state of the network comprises: acquiring an execution result of each sub-configuration task; associating the execution result of each sub-configuration task with the access relation based on the execution result of each sub-configuration task; and aggregating the execution results of all the sub-configuration tasks executed by the same equipment based on the association of the execution result of each sub-configuration task and the access relation so as to indicate the configuration state of the network based on the aggregated execution results.
In some embodiments, the method for network operation and maintenance further comprises: acquiring error codes fed back by equipment corresponding to the sub-configuration tasks with the execution results being failed; associating the error codes fed back by the equipment with the corresponding sub-configuration tasks and aggregating the error codes to an execution result; and in response to detecting the error code of the device, re-executing the sub-configuration task on the device corresponding to the error code according to a preset error processing rule.
In some embodiments, generating topology information for each access relationship based on the access relationship information comprises: determining an access path corresponding to each access relation based on the nodes included in each piece of access relation information; determining all devices related to each access relation based on the access path corresponding to each access relation; and acquiring the equipment information of all the equipment related to each access relation, wherein the equipment information at least comprises the equipment model, the position information, the interface information and the connection information with other equipment of the current equipment.
In some embodiments, determining, based on the node included in each piece of access relationship information, the access path corresponding to each piece of access relationship includes: if it is determined that only one access path exists based on the nodes in one access relationship, determining the only one access path as the access path corresponding to the one access relationship; if at least two access paths exist based on the nodes in one 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 the access path is determined not to exist based on the nodes in one access relation, returning indication information for indicating the path confirmation failure.
In some embodiments, the method for network operation and maintenance further comprises: determining whether the same device needs to execute a plurality of sub-configuration tasks; and in response to determining that the same device needs to execute a plurality of sub-configuration tasks, executing the plurality of sub-configuration tasks of the same device according to a preset execution sequence rule.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The above and other features, advantages and aspects of embodiments of the present disclosure will become more apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings. In the drawings, like or similar reference characters designate like or similar elements.
Fig. 1 shows a schematic diagram of a system for implementing a method for network operation and maintenance according to an embodiment of the invention.
Fig. 2 shows a flow diagram of a method 200 for network operation and maintenance according to an embodiment of the disclosure.
FIG. 3 shows a flow diagram of a method 300 for parallel execution of a sub-configuration task, according to an embodiment of the present disclosure.
FIG. 4 shows a flow diagram of a method 400 for configuring task execution result indication, according to an embodiment of the present disclosure.
FIG. 5 shows a flow diagram of a method 500 for reconfiguration task re-execution according to an embodiment of the present disclosure.
FIG. 6 illustrates a flow diagram of a method 600 for determining access relationship topology information in accordance with an embodiment of the disclosure.
Fig. 7 shows a flow diagram of a method 700 for determining an access path according to an embodiment of the present disclosure.
Fig. 8 shows a schematic diagram of a network configuration concurrency principle according to an embodiment of the present disclosure.
Fig. 9 shows a schematic diagram of network configuration status indication according to an embodiment of the present disclosure.
Fig. 10 shows a block diagram of an electronic device according to an embodiment of the disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of embodiments of the present disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
The term "including" and variations thereof as used herein is intended to be open-ended, i.e., "including but not limited to". The term "or" means "and/or" unless specifically stated otherwise. The term "based on" means "based at least in part on". The terms "one example embodiment" and "one embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment". The terms "first," "second," and the like may refer to different or the same objects. Other explicit and implicit definitions are also possible below.
As described above, in an operation and maintenance scene of a data center, the increasing access requirements may involve the opening of multiple access relationships at the same time, and the opening of each access relationship may involve the configuration modification of multiple devices, a conventional operation and maintenance tool generally operates in a network device-oriented manner, and such a conventional operation and maintenance method or tool generally configures each network device individually, and this configuration manner causes the device to lack the perception of global topology information, so that in the operation and maintenance scene of the data center, the conventional network operation and maintenance method is difficult to meet the configuration requirements of multiple devices and complex scenes. In summary, the conventional network operation and maintenance method has the following disadvantages: the automatic operation and maintenance requirements under multiple devices and complex scenes are difficult to meet.
To at least partially solve one or more of the above problems and other potential problems, an example embodiment of the present disclosure proposes a scheme for network operation and maintenance, in which full-network topology information and access relationship information are obtained in response to a retrieval of an operation and maintenance requirement instruction, where the access relationship information includes access relationship information about at least one access relationship, and the access relationship information indicates at least a start point and an end point in an access path corresponding to the access relationship; generating topology information of each access relation based on the access relation information, wherein the topology information of one access relation at least indicates an access path corresponding to the access relation and equipment information of all equipment in the access path; acquiring a configuration task corresponding to each access relation based on the topological information of each access relation; executing the configuration tasks corresponding to each access relation in parallel; according to the method and the device, the topology information of each access relation can be generated only through the starting point and the end point in the access path corresponding to each access relation according to the access relation of the whole network, so that the configuration tasks corresponding to all the devices on the access path corresponding to the access relation are acquired by taking the access relation as an object and are executed in parallel, and the network configuration efficiency is effectively improved. In addition, the method and the device can also acquire the execution results of all the configuration tasks so as to aggregate the execution results for indicating the configuration state of the network; the centralized display of the execution result of the configuration task is realized, and good guidance is provided for improving the configuration efficiency. Therefore, the network configuration efficiency can be improved, and the automatic operation and maintenance requirements under the complex scene with multiple devices can be met.
Fig. 1 shows a schematic diagram of a system 100 for implementing a method for network operation and maintenance according to an embodiment of the invention. As shown in fig. 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 may perform data interaction via a network 140 (e.g., the internet).
The access relationship information providing device 130 may store, for example, a plurality of types of different 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 relation information providing device 130 may generate digital files, such as data tables, in a specific format related to the access relation information according to a plurality of different types of access relation information data sources stored therein, where the formats of the access relation information data sources are not limited to xls, xlsx, accdb, txt, csv, word, dat, mdf, mdb, db, dbf, wdb, and the like, which may present the digital files of the access relation information and/or may be applied to the access relation information providing device, and the access relation information providing device 130 converts data in the digital files in the above formats into a specific format so as to interface with an access relation information database in the access relation information providing device 130 or interface with the computing device 110; the type of the specific format to be converted can also be determined according to the equipment condition and the use requirement of the actual scene. In addition, the specific data source format can be dynamically adjusted according to the access relation information required by the user. The access relationship information providing device 130 may also provide the access relationship information to the computing device 110.
Regarding the computing device 110, for example, in response to retrieving the operation and maintenance requirement instruction, obtaining the topology information of the whole network and obtaining the access relationship information from the access relationship information providing device 130, where the access relationship information includes access relationship information regarding at least one access relationship, and the access relationship information indicates at least a start point and an end point in an access path corresponding to the access relationship; generating topology information of each access relation based on the access relation information, wherein the topology information of one access relation at least indicates an access path corresponding to the access relation and equipment information of all equipment in the access path; acquiring a configuration task corresponding to each access relation based on the topology information of each access relation; and executing the configuration task corresponding to each access relation in parallel. The computing device 110 may also obtain execution results of all configuration tasks to aggregate the execution results for indicating a configuration status of the network. Computing device 110 may have one or more processing units, including special purpose processing units such as GPUs, FPGAs, ASICs, and the like, as well as general purpose processing units such as CPUs. Additionally, one or more virtual machines may also be running on each computing device 110. In some embodiments, the computing device 110 and the access relationship information providing device 130 may be integrated together or may be provided separately from each other. In some embodiments, computing device 110 includes, for example, 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.
An information acquisition module 112, configured to determine whether an operation and maintenance requirement instruction is retrieved; and if the operation and maintenance requirement instruction is retrieved, acquiring full-network topology information and access relation information, wherein the access relation information comprises access relation information about at least one access relation, and the access relation information at least indicates a starting point and an end point in an access path corresponding to the access relation.
And the topology information generating module 114 is configured to generate topology information of each access relationship based on the access relationship information, where the topology information of one access relationship at least indicates an access path corresponding to the access relationship and device information of all devices in the access path.
And the configuration task obtaining module 116 is configured to obtain a configuration task corresponding to each access relationship based on the topology information of each access relationship.
And the configuration task execution module 118 is used for executing the configuration task corresponding to each access relation in parallel.
And the configuration result analysis module 120 is configured to obtain execution results of all configuration tasks, so as to aggregate the execution results for indicating the configuration state of the network.
Fig. 2 shows a flow diagram of a method 200 for network operation and maintenance according to an embodiment of the disclosure. Fig. 8 shows a schematic diagram of a network configuration concurrency principle. The method 200 is described below in conjunction with fig. 2 and 8. The method 200 may be performed by the computing device 110 as shown in FIG. 1, or may be performed at the electronic device 1000 shown in FIG. 10. It should be understood that method 200 may also include additional steps not shown and/or may omit steps shown, as the scope of the disclosure is not limited in this respect.
In step 202, if the computing device 110 retrieves the operation and maintenance requirement instruction, the full-network topology information and the access relationship information are obtained, where the access relationship information includes access relationship information about at least one access relationship, and the access relationship information at least indicates a start point and an end point in an access path corresponding to the access relationship.
The operation and maintenance requirement instruction at least comprises a timing task instruction which is preset according to the operation and maintenance requirement, an operation and maintenance requirement instruction which is imported by operation and maintenance personnel, and an operation and maintenance requirement instruction which is input by the operation and maintenance personnel in real time; these operation and maintenance requirement instructions can be preset and adjusted according to the information and state of the network and the actual configuration requirements.
Before acquiring the topology information and the access relationship information of the whole network, the computing device 110 may call a configuration file to initialize a topology information data source of the whole network, so as to convert the topology information data of the whole network into a specific structured format, so as to store, read, call, process, etc. the topology information data; meanwhile, the access relation information providing device 130 may also call the configuration file to initialize the access relation information data source, and convert the access relation information data into a specific structured format, so as to facilitate storage, reading, calling, processing, and the like of the access relation information data.
The access relation information may be, for example, access relation information of at least one access relation stored in a form of a data table, and each piece of access relation information may include corresponding access path information (such as nodes in an access path, node device information, and the like), association information with other access relations, and the like; it should be noted that the access relationship information of an access relationship at least needs to include an indication of a start point and an end point in an access path corresponding to the access relationship, so that the computing device 110 may obtain the access path corresponding to the access relationship and information of all nodes in the corresponding access path according to the node information of the access path corresponding to the access relationship.
Regarding the starting point and the end point in the access path, the starting point and the end point are only two nodes that one access path needs to include at least, each node corresponds to one device, and the configuration tasks executed by the network configuration are also directed at the devices of the nodes; in a data center scenario, an access path will typically contain at least 3 nodes, a start point, an end point, and a firewall node.
Regarding the topology information of the whole network, it is necessary to define in advance, for example, each device in the whole network, the relationship between the devices, each transmission medium, and the like. The topology information of the whole network at least comprises topology structure of the whole network, equipment information of all equipment, connection relation between equipment, transmission media, data transmission line information, configuration task screening conditions, execution condition information and the like.
In step 204, the computing device 110 generates topology information of each access relationship based on the access relationship information, where the topology information of one access relationship at least indicates an access path corresponding to the access relationship and device information of all devices in the access path.
The topology information about an access relationship may further include: all transmission media, connection line information, node position information, configuration task screening conditions and execution condition information of each device in the access path corresponding to the access relationship.
The device information may include at least a device model, location information, interface information, and connection information and association relationship with other devices of the current device.
For example, referring to fig. 8, the obtained access relationship information a includes three access relationships, that is, an access relationship a1, an access relationship a2, and an access relationship a3, and generates a topological relationship p1 of the access relationship a1, a topological relationship p2 of the access relationship a2, and a topological relationship p3 of the access relationship a3, respectively; the scheme realizes concurrency based on the access relation so as to realize concurrency configuration based on the access relation on the network equipment.
In step 206, the computing device 110 obtains a configuration task corresponding to each access relationship based on the topology information of each access relationship.
The configuration tasks may be entered in advance according to the conditions and requirements of the devices, the configuration task corresponding to one access relationship at least includes an operation that is required to be executed by each device on the access path corresponding to the access relationship, the executed operations may be customized, and the configuration task that triggers the device to operate may be sent to the devices only by knowing the address information of the corresponding device. The operations to be executed at least include executing some filtering conditions, such as filtering the shortest path among multiple devices, whether the path contains a certain device, determining whether two devices are connected, returning path information connecting two devices, and the like.
At step 208, the computing device 110 performs configuration tasks corresponding to each of the access relationships in parallel.
With respect to obtaining a configuration task corresponding to an access relation, executing a configuration task corresponding to an access relation in parallel, for example, referring to fig. 8, generating a configuration task T corresponding to access relations a1, a2 and a3 based on topological relations p1, p2 and p3 respectively a1 Configure task T a2 Configure task T a3 And executing the configuration tasks T corresponding to the access relations a1-a3 in parallel a1 、T a2 And T a3 (ii) a According to the scheme, the devices on the access path corresponding to each access relation are configured in parallel by taking the access relation as an object for each device related to the operation and maintenance requirements, rather than being configured by taking a single device as a unit, so that the relevance among the devices is greatly improved, the compatibility of the configuration is better, and the configuration efficiency is higher.
At step 210, the computing device 110 obtains execution results of all configuration tasks to aggregate the execution results for indicating the configuration status of the network.
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 successful configuration, failed configuration, current configuration state, and the like.
In the above scheme, for the access relationship information, the topology information of each access relationship can be generated only by the starting point and the ending point in the access path corresponding to each access relationship, and the information of all the node devices on the access path corresponding to each access relationship is acquired, so that network configuration is performed by taking the access relationship as an object, and the network configuration efficiency is effectively improved. In addition, the execution results of all the configuration tasks can be acquired, so that the execution results are aggregated to realize the indication of the configuration state of the network; can provide good guidance for 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, thereby meeting the automatic operation and maintenance requirements under the complex scene with multiple devices.
FIG. 3 shows a flow diagram of a method 300 for parallel execution of a sub-configuration task according to an embodiment of the present disclosure. The method will be described below with reference to fig. 3 and 8. The method 300 may be performed by the computing device 110 as shown in FIG. 1, or may be performed at the electronic device 1000 shown in FIG. 10. It should be understood that method 300 may also include additional steps not shown and/or may omit steps shown, as the scope of the disclosure is not limited in this respect.
In step 302, the computing device 110 obtains a sub-configuration task corresponding to each device in the access path corresponding to each access relationship based on the configuration task corresponding to each access relationship.
Referring to fig. 8, for example, the obtained access relationship information a includes three access relationships, namely, an access relationship a1, an access relationship a2, and an access relationship a3, and the configuration task T is generated according to topology information p1-p3 of the three access relationships a1 Configuration task T a2 Configuration task T a3 (ii) a Wherein, the node devices in the access path corresponding to the access relationship a1 have Z0, Z1, Z2 and Z3, and the sub-configuration tasks of the devices Z0-Z3 with respect to the access relationship a1 are respectively generated according to the access relationship a1, for example, the sub-configuration task T is generated a1-Z0 、T a1-Z1 、T a1-Z2 And T a1-Z3 (ii) a Node devices in an access path corresponding to the access relationship a2 are provided with Z1, Z3 and Z5, and a sub-configuration task of the devices Z1, Z3 and Z5 about the access relationship a2 is respectively generated according to the access relationship a 2; node devices in an access path corresponding to the access relationship a3 are Z0, Z3, Z4, Z5 and Z6, and a sub-configuration task of the devices Z0, Z3, Z4, Z5 and Z6 about the access relationship a3 is respectively generated according to the access relationship a3; it should be noted that the same device may be involved in multiple access relationships, i.e. different accessesThe paths may include the same device, for example, the access paths a1, a2, and a3 all include the node device Z3; thus, there may be multiple sub-configuration tasks for the same device.
At step 304, the computing device 110 performs all sub-configuration tasks of any of the at least one access relationships in parallel.
Referring to fig. 8, for example, in the access relationship information a, the configuration tasks T corresponding to the access relationship a1, the access relationship a2 and the access relationship a3 are executed in parallel a1 Configure task T a2 Configuring task T a3 (ii) a The configuration tasks respectively have a plurality of sub-configuration tasks; for example, all the sub-configuration tasks in the access relationships a1, a2 and a3, i.e. all the sub-configuration tasks of the devices Z0, Z1, Z2, Z3, Z4, Z5 and Z6 are executed in parallel; the method realizes the concurrent generation of the sub-configuration tasks and the concurrent execution of the sub-configuration tasks.
At step 306, the computing device 110 determines whether the same device needs to perform multiple sub-configuration tasks.
For example, referring to fig. 8, the device Z3 relates to three access relationships a1, a2 and a3 at the same time, so that the device Z3 is a node on three access paths corresponding to the access relationships a1, a2 and a3 at the same time, and 3 sub-configuration tasks are generated with respect to the device Z3. When each node device only has 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, during the actual configuration process, the same device may not be able to execute the multiple configuration tasks at the same time, and at this time, it needs to determine whether the same device needs to execute the multiple sub-configuration tasks, and the execution sequence of the multiple sub-configuration tasks of the same device during the actual execution process of the configuration tasks.
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 the predetermined execution order rule.
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.
The predetermined sequence rule may be, for example, that the sub-configuration tasks are executed first according to the time when the same device actually receives the sub-configuration tasks; the priority of execution may also be a1 > a2 > a3 according to the association order among the access relations, for example, the access relations a1, a2 and a3 are in relation to the execution order rule of the same node device task; the sequence rule of processing a plurality of sub-configuration tasks by the same node can be determined in advance according to the operation and maintenance task requirement in an actual scene.
In some embodiments, the computing device 110 may also invoke a task template corresponding to the devices in the access path based on the pre-entered task library and the device information of the devices, so as to generate a sub-configuration task corresponding to each device in the access path; and
the sub-configuration tasks at least comprise an information acquisition task, a configuration backup task and a configuration issuing task.
Regarding the task template, a plurality of nodes may be involved in the access path, and information such as model and manufacturer of each node device may be different, which results in different formats of configuration task files compatible with different node devices; regarding the pre-entered task library, the task library at least comprises information such as a task template, a node type and/or a task parameter corresponding to the node device, and automatic differential configuration of multiple devices can be realized, so that configuration efficiency is improved.
According to the scheme, the concurrence of operation and maintenance required tasks is realized, and the access relation information of each access relation is parallelly acquired according to the access relation information; then based on the topology information of the whole network, taking the access relations as objects, and generating the topology relations of the access relations in parallel according to the access relation information of each access relation; generating configuration tasks corresponding to the access relations in parallel based on the topological relations of the access relations; then, based on the access path node information, all node devices on the access path corresponding to the access relationship are taken as objects, and the sub-configuration tasks of all the node devices in each access relationship are generated in parallel; finally, executing the sub-configuration tasks of any access relation in the at least one access relation in parallel; according to the method for network operation and maintenance, in each link for generating the configuration task based on the access relation information, the access relation and the node equipment in the path corresponding to the access relation are respectively used as objects for carrying out concurrence for many times, so that the efficiency of network configuration is greatly improved, and the relevance among the equipment needing to be configured can be considered, so that the high-efficiency and high-quality network configuration is realized when the network operation and maintenance requirements are met.
Fig. 4 shows a flowchart of a method 400 for configuring task execution result indication according to an embodiment of the present disclosure, fig. 9 shows a schematic diagram of network configuration status indication according to an embodiment of the present disclosure, and the method 400 is explained below with reference to fig. 4, fig. 8, and fig. 9. The method 400 may be performed by the computing device 110 as shown in FIG. 1, or may be performed at the electronic device 1000 shown in FIG. 10. It should be understood that method 400 may also include additional steps not shown and/or may omit steps shown, as the scope of the disclosure is not limited in this respect.
At step 402, the computing device 110 obtains the results of the execution of each of the sub-configuration tasks.
For example, referring to fig. 8 and 9, the execution results of all the sub-configuration tasks of the access relationships a1, a2, and a3 are obtained.
At step 404, the computing device 110 associates each of the sub-configuration task execution results with an access relationship based on the execution results of each of the sub-configuration tasks.
In step 406, the computing device 110 aggregates the execution results of all the sub-configuration tasks executed by the same device based on the association between the execution result of each sub-configuration task and the access relationship, so as to indicate the configuration status of the network based on the aggregated execution results.
For example, referring to fig. 9, in fig. 9, taking the configuration task execution results corresponding to the access relationships a1, a2, and a3 illustrated in fig. 8 as an example, taking the node device as a set, associating the configuration task execution results with the access relationships, showing the execution results of each sub-configuration task, and implementing an indication of the network configuration state; for example, the device Z0, the configuration is successful with respect to the access relation a1, and the configuration is failed with respect to the access relation a 2; it should be noted that fig. 9 only illustrates the execution results of the sub-configuration tasks of the partial node devices corresponding to the access relationships a1, a2, and a3, and only indicates one association manner between the execution results and the access relationships, and in the actual use process, the result association and the configuration state indication may also be performed in other manners, and the execution results of the sub-configuration tasks may also be aggregated in other aggregation manners.
The scheme can associate the execution condition of the configuration task with the equipment for configuration and multiple access relations, and clearly indicate the configuration result of each equipment in each access relation, so that operation and maintenance personnel can know the execution condition of the configuration task, the configuration conditions of each equipment and each access path.
FIG. 5 shows a flow diagram of a method 500 for reconfiguration task re-execution according to an embodiment of the present disclosure. The method 500 may be performed by the computing device 110 as shown in FIG. 1, or may be performed at the electronic device 1000 shown in FIG. 10. It should be understood that method 500 may also include additional steps not shown and/or may omit steps shown, as the scope of the present disclosure is not limited in this respect.
In step 502, the computing device 110 obtains an error code fed back by a device corresponding to the sub-configuration task whose execution result is failure.
At step 504, the computing device 110 associates and aggregates the error codes fed back by the device with the corresponding sub-configuration tasks to the execution results.
Regarding the error code, for example, the error code of the sub-configuration task "access relationship a3 — configuration failure" of the device Z0 with respect to the access relationship 3 in fig. 9 is "xxxZ0a3xxx", and the error code is used to indicate the reason why the configuration of the device Z0 fails.
At step 506, the computing device 110 determines whether an error code of the device is detected. If the computing device 110 does not detect a device error code, proceed to step 502.
At step 508, if the computing device 110 detects an error code for a device, the sub-configuration task is re-executed for the device to which the error code corresponds according to predetermined error handling rules.
Regarding the predetermined error processing rules, various error code processing rules may be pre-entered according to error reasons corresponding to respective error codes, so that the computing device 110 automatically debugs the node device in which an error occurs in response to the error code, or automatically generates a new sub-configuration task according to error code debugging configuration parameters, so as to implement re-execution of the sub-configuration task on the node device with failed configuration.
By the scheme, the error reason of the node equipment with the failure of the sub-configuration task can be acquired, the failed sub-configuration task can be conveniently re-executed after timely debugging, and the configuration efficiency is improved.
FIG. 6 illustrates a flow diagram of a method 600 for determining access relationship topology information in accordance with an embodiment of the disclosure. The method 600 may be performed by the computing device 110 as shown in FIG. 1, or may be performed at the electronic device 1000 shown in FIG. 10. It should be understood that method 600 may also include additional steps not shown and/or may omit steps shown, as the scope of the disclosure is not limited in this respect.
In step 602, the computing device 110 determines an access path corresponding to each access relationship based on the nodes included in each piece of access relationship information.
Regarding the nodes included in each piece of access relationship information, at least the number of the node or the number of the node device is included, so as to obtain the device information of the node device; for example, the access relationship information of the access relationship a1 includes nodes Z0 and Z3, and the access relationship information of the access relationship a3 includes nodes Z0, Z5, and Z6. It should be noted that, usually, at least the start point and the end point of the access path corresponding to the access relationship need to be included to determine one access path, but more nodes may also be included.
At step 604, the computing device 110 determines all devices involved in each access relationship based on the access path corresponding to each access relationship.
After the access path is determined, all nodes of the access path can be obtained, so that after one access path is determined, all devices related to the access relationship corresponding to the access path can be determined; for example, determining the access path "Z0 → Z1 → Z2 → Z3" makes it possible to determine that all the devices involved in the access relationship a1 are four devices "Z0, Z1, Z2 and Z3".
In step 606, the computing device 110 obtains device information of all devices involved in each access relationship, where the device information at least includes a device model, location information, interface information, and connection information with other devices of the current device.
The connection information with other devices at least comprises the connection relation between the devices, the specific connection mode, the connected interface information and the transmission medium information; it should be noted that the connection information with other devices is not limited to devices connected to the entire network, and may be devices connected to an external network.
Regarding the transmission line, when the devices at the edge of the intranet topology need to connect to external devices, an external transmission medium, such as an external line, is usually used; therefore, the scheme provides an extra private line message so as to distinguish an external line from other internal devices and lines when the whole network topology initialization is carried out; therefore, when the configuration task fails and the error reason is the external private line, it is obvious that the internal network operation and maintenance cannot solve the problems, and only an alarm can be given, so that the operation and maintenance personnel can remind the operator of the external network private line to solve the related problems.
For example, the storage of the private line information may be performed in the form of a data table, which may include information such as a private line number, a private line operator, a vlan number, a private line type, a private line bandwidth, a home terminal name, a home terminal private line port address, an opposite terminal name, and an opposite terminal private line port address; the special line number, the special line operator, the vlan number, the special line type and the special line bandwidth are necessary options, titles beginning at a local end and an opposite end are initialized to be a center and a branch class at one end of the special line, the name at one end of the special line and the port address of the special line are necessary items, and information such as a special line interface can be expanded according to actual conditions; the external lines can be screened and judged through the configuration task, such as according to the key field, the line number, whether a conflicting vlan number exists or not, a conflicting IP and the like.
According to the scheme, the complete access path corresponding to each access relation can be determined according to the path nodes included in each piece of access relation information, the equipment information of all node equipment is obtained, and independent management and processing of external circuits are provided, so that operation and maintenance personnel can confirm the reason of configuration failure in time, problems caused by non-internal reasons are eliminated in time, and operation and maintenance efficiency is improved.
Fig. 7 shows a flow diagram of a method 700 for determining an access path according to an embodiment of the present disclosure. The method 700 may be performed by the computing device 110 as shown in FIG. 1, or may be performed at the electronic device 1000 shown in FIG. 10. It should be understood that method 700 may also include additional steps not shown and/or may omit steps shown, as the scope of the present disclosure is not limited in this respect.
At step 702, the computing device 110 is operable to determine the number of access paths that exist based on the nodes in an access relationship.
In step 704, if the computing device 110 determines that only one access path exists based on the nodes in one access relationship, the only one access path is determined as the access path corresponding to the one access relationship.
In step 706, if the computing device 110 determines that at least two access paths exist based on the node in one access relationship, according to a predetermined path determination rule, one access path is determined from the determined at least two access paths as the access path corresponding to the one access relationship.
As for the predetermined path determination rule, a rule about how to determine an access path when at least two access paths exist in one access relationship may be entered in advance according to requirements, for example, a priority rule of a node may be set, and a path with a high node priority in the selected paths is determined as the access path; the priority of the node can be determined or adjusted according to factors such as a network state, an equipment hardware state, a node association relation, an access relation type and the like, and can also be dynamically adjusted according to the execution success rate of the sub-configuration task; the node priority rules may be set in the topology information.
At step 708, if based on a node in an access relationship, the computing device 110 determines that no access path exists and returns indication information indicating that path validation failed.
When it is determined that the access path does not exist, the alarm information may also be returned to prompt the operation and maintenance staff that the access path does not exist and that the access relationship information needs to be adjusted, which may be a problem in the node information provided in the access relationship information, for example, the number of nodes is too small, a key node is missing, and the like, so that no path exists.
By the scheme, the path nodes can be completed according to the incomplete access relation of the path node information in the access relation information, so that the corresponding complete access path is obtained, all the nodes on the access path and the information of the equipment where all the nodes are located are obtained, the access relation information without the access path can be fed back in time, the problem of the access relation of operation and maintenance personnel is prompted, and the operation and maintenance efficiency is improved.
The above scheme may be implemented by some databases and operation and maintenance management tools, for example, by an Access database, a task setting module, a controller and an operation and maintenance tool in combination with fig. 8, and the specific implementation manner may be: initializing the whole network topology information by calling a configuration file such as an InitController function, specifically initializing path information, equipment information, special line information and the like, and returning a Controller object containing the whole network topology information after initialization; storing access relation information through an access object, initializing the access object by calling a load _ access function, wherein the access object can be a class list object, each access object is an access relation, and screening a Controller object of the whole network topology information to respectively generate the whole network topology information corresponding to each access relation when each access relation is initialized; calling a task function to generate a configuration task of each access relation and a sub-configuration task of each device in a corresponding access path according to the full-network topological relation of each access relation through a task configuration task module; when configuration is performed, whether configuration is correct can be determined by whether a data packet output by a front node is consistent with a data packet input by a rear node in the same access path, for example, referring to an access relationship a2 illustrated in fig. 8, nodes Z1, Z3 and Z5 are involved, the access path is "Z1 → Z3 → Z5", a data packet output after passing through the Z1 node is the same as a data packet input to the Z3 node, a data packet output after passing through the Z3 node is the same as a data packet input to the Z5 node, and whether configuration of a certain device in a certain access relationship is successful can be determined by checking similarity of the data packets; the data packet information that will be encountered in the configuration task may be pre-entered into the corresponding access relationship information.
And finally, returning all the configuration task execution results. It should be appreciated that, when the operation and maintenance method provided by the present disclosure is actually executed, the database, the operation and maintenance tool, the plug-in, etc. for deploying the operation and maintenance method 200-700 may be determined according to the actual state of the database in the whole network, the model of the device, the type of the system, etc.
Fig. 10 shows a schematic step diagram of an example electronic device 1000 that may be used to implement embodiments of the present disclosure. For example, the computing device 110 as shown in fig. 1 may 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 computer program instructions loaded from a storage unit 1008 into a Random Access Memory (RAM) 1003. In the random access memory 1003, various programs and data necessary for the operation of the electronic apparatus 1000 can also be stored. The central processing unit 1001, the read only memory 1002, and the random access memory 1003 are connected to each other by a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.
A plurality of 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, and the like; an output unit 1007 such as various types of displays, speakers, and the like; a storage unit 1008 such as a magnetic disk, an optical disk, or the like; and a communication unit 1009 such as a network card, a modem, a wireless communication transceiver, or the like. 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.
The various processes and processes described above, such as methods 200 through 700, may be performed by the central processing unit 1001. For example, in some embodiments, methods 200-700 may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 1008. In some embodiments, some or all of the computer program may be loaded and/or installed onto device 1000 via read only memory 1002 and/or communications 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 to 700 described above may be performed.
The present disclosure relates to methods, apparatuses, systems, electronic devices, computer-readable storage media and/or computer program products. The computer program product may include computer-readable program instructions for performing various aspects of the present disclosure.
The computer-readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would 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 Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be interpreted as a transitory signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or an electrical signal transmitted through an electrical wire.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge computing devices. The network adapter card or network interface in each computing/processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
Computer program instructions for carrying out operations of the present disclosure may be assembler instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source 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 may 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 case of a remote computer, the remote computer may 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 may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the disclosure are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.
Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or step diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or step diagram step or steps. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or step diagram step or steps.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or step diagram step or steps.
The flowcharts and step diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or step diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two successive method steps may in fact be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each step of the step diagrams and/or flowchart illustration, and combinations of steps in the step diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (10)

1. A method for network operations and maintenance, comprising:
responding to an operation and maintenance requirement retrieval instruction, acquiring full-network topology information and access relation information, wherein the access relation information comprises access relation information about at least one access relation, and the access relation information at least indicates a starting point and an end point in an access path corresponding to the access relation;
generating topology information of each access relation based on the access relation information, wherein the topology information of one access relation at least indicates an access path corresponding to the access relation and equipment information of all equipment in the access path;
acquiring a configuration task corresponding to each access relation based on the topological information of each access relation;
executing the configuration tasks corresponding to each access relation in parallel; and
and acquiring the execution results of all the configuration tasks so as to aggregate the execution results for indicating the configuration state of the network.
2. The method of claim 1, wherein executing the configuration task corresponding to each access relationship in parallel comprises:
acquiring a sub-configuration task corresponding to each device in an access path corresponding to each access relation based on the configuration task corresponding to each access relation;
and executing all the sub-configuration tasks of any access relation in the at least one access relation in parallel.
3. The method of claim 2, wherein obtaining the sub-configuration task corresponding to each device in the access path corresponding to each access relationship comprises:
based on a pre-entered task library and equipment information of the equipment, calling a task template corresponding to the equipment in the access path so as to generate a sub-configuration task corresponding to each equipment in the access path; and
the sub-configuration tasks at least comprise an information acquisition task, a configuration backup task and a configuration issuing task.
4. The method of claim 2, wherein obtaining execution results of all configuration tasks to aggregate the execution results for indicating a configuration state of the network comprises:
acquiring an execution result of each sub-configuration task;
associating the execution result of each sub-configuration task with the access relation based on the execution result of each sub-configuration task;
and aggregating the execution results of all the sub-configuration tasks executed by the same equipment based on the association of the execution result of each sub-configuration task and the access relation so as to indicate the configuration state of the network based on the aggregated execution results.
5. The method of claim 4, further comprising:
acquiring error codes fed back by equipment corresponding to the sub-configuration tasks with the execution results being failed;
associating the error codes fed back by the equipment with the corresponding sub-configuration tasks and aggregating the error codes to an execution result; and
and in response to detecting the error code of the equipment, re-executing the sub-configuration task on the equipment corresponding to the error code according to a preset error processing rule.
6. The method of claim 1, wherein generating topology information for each access relationship based on the access relationship information comprises:
determining an access path corresponding to each access relation based on the nodes included in each piece of access relation information;
determining all devices related to each access relation based on the access path corresponding to each access relation; and
and acquiring the equipment information of all the equipment related to each access relation, wherein the equipment information at least comprises the equipment model, the position information, the interface information and the connection information with other equipment of the current equipment.
7. The method of claim 6, wherein determining, based on the node included in each piece of access relationship information, an access path corresponding to each piece of access relationship comprises:
if it is determined that only one access path exists based on the nodes in one access relationship, determining the only one access path as the access path corresponding to the one access relationship;
if at least two access paths exist based on the nodes in one 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 it is determined that no access path exists based on the nodes in one access relationship, returning indication information for indicating path validation failure.
8. The method of claim 2, further comprising:
determining whether the same device needs to execute a plurality of sub-configuration tasks;
and in response to determining that the same device needs to execute a plurality of sub-configuration tasks, executing the plurality of sub-configuration tasks of the same device according to a preset execution sequence rule.
9. A computing device, comprising:
at least one processor; and a memory communicatively coupled to the at least one processor;
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-8.
10. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-8.
CN202211326299.0A 2022-10-27 2022-10-27 Method, computing device and storage medium for network operation and maintenance Pending CN115714712A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211326299.0A CN115714712A (en) 2022-10-27 2022-10-27 Method, computing device and storage medium for network operation and maintenance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211326299.0A CN115714712A (en) 2022-10-27 2022-10-27 Method, computing device and storage medium for network operation and maintenance

Publications (1)

Publication Number Publication Date
CN115714712A true CN115714712A (en) 2023-02-24

Family

ID=85231449

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211326299.0A Pending CN115714712A (en) 2022-10-27 2022-10-27 Method, computing device and storage medium for network operation and maintenance

Country Status (1)

Country Link
CN (1) CN115714712A (en)

Similar Documents

Publication Publication Date Title
US9442822B2 (en) Providing a visual representation of a sub-set of a visual program
US8913729B2 (en) Automated provisioning
CN109936479B (en) Control plane fault diagnosis system based on differential detection and implementation method thereof
US20150066572A1 (en) Identity and access management
US20130014127A1 (en) System and method for automatically generating computer code for message flows
CN109189758B (en) Operation and maintenance flow design method, device and equipment, operation method, device and host
WO2006117831A1 (en) Network design processing device and method, and program therefor
CN108845940A (en) A kind of enterprise information system automated function test method and system
CN107341096A (en) The generation method and device of journal file, computer equipment and storage medium
CN109726066B (en) Method and apparatus for identifying problem components in a storage system
CN109039788A (en) Port configuration method, device and the storage medium of the network equipment
CN113285906A (en) Security policy configuration method, device, equipment and storage medium
CN113347060B (en) Method, device and system for detecting power network fault based on process automation
US20180123900A1 (en) Scenario driven, technology agnostic network simulation
US20180123899A1 (en) Technology agnostic network simulation
CN112311574A (en) Method, device and equipment for checking network topology connection
US11330053B1 (en) Making eventual consistency cache updates deterministic
CN116455869A (en) Method and system for efficiently configuring public network domain name based on Kubernetes
US11960385B2 (en) Automatic generation of integrated test procedures using system test procedures
CN111726255A (en) Processing method and device for network change
CN115714712A (en) Method, computing device and storage medium for network operation and maintenance
CN110855456B (en) Network change method and equipment
US20220308911A1 (en) System and method for a distributed workflow system
US11632266B2 (en) Device setting control device, network system, device setting method, and program
CN102843269A (en) Method and system of analog microcode business processing flow

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination