CN112165395B - Network management configuration data conversion method and system - Google Patents
Network management configuration data conversion method and system Download PDFInfo
- Publication number
- CN112165395B CN112165395B CN202010953965.8A CN202010953965A CN112165395B CN 112165395 B CN112165395 B CN 112165395B CN 202010953965 A CN202010953965 A CN 202010953965A CN 112165395 B CN112165395 B CN 112165395B
- Authority
- CN
- China
- Prior art keywords
- data
- network management
- configuration data
- network
- management system
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A network management configuration data conversion method and system relates to the technical field of network element equipment management, and is suitable for version upgrading of network management configuration data of an old version of network management system, wherein the network management configuration data comprises basic configuration data and service data; the network management configuration data conversion method comprises the following steps: carrying out one-to-one format conversion on the basic configuration data to obtain first data with a format meeting the requirements of the network management system of the new version; generating a network element layer data model by the service data, generating a sub-network layer data model by the network element layer data model, and importing the custom data into the sub-network layer data model to obtain second data with a format meeting the requirements of a new version of network management system; and the first data and the second data form network management configuration data of a new version of network management system. The invention reversely creates and generates the network management configuration data of the network management system of a new version on the basis of the data consistency of the new and the old network management equipment layers, and improves the creation speed by more than ten times compared with the existing forward creation flow.
Description
Technical Field
The present invention relates to the technical field of network element device management, and in particular, to a method and a system for converting network management configuration data.
Background
With the continuous development of telecommunication networks, packet Transport Network (PTN) devices are used in large scale in the process of constructing a metropolitan area Network, different types of PTN devices need to be managed on a Network manager, an old Network manager system cannot cope with a rapidly-developed device application scenario, a new Network manager system must be developed, a unified data model is used, various types of devices are managed, and better use experience is provided for users.
The number of network elements managed by the old network management system is above 1W, and the number of services is about 20W. In the switching process of the new network management system and the old network management system, the traditional forward simulation creation process has a plurality of problems which cannot be solved: the time for completing the whole creation of the service is too long (20W service needs one week or more for completing the creation), and the creation work is not allowed to be performed in such a time under the field upgrading condition of the engineering network management; the creation process of the new network management is inconsistent with the creation process of the old network management, so that the resource allocation is difficult to be consistent with the original data, and the inconsistent data can cause service interruption; the network management configuration data of the network management system comprises basic configuration data and service data, and in the process of creating a new network management, the basic configuration data and the service data of an old network management system have different format conversion difficulties, so that the network management configuration data of the old network management system cannot be directly packaged and updated to obtain the network management configuration data of the new network management system; even if the creation can be completed, the workload of subsequent data checking is large, the data of each issuing device needs to be carefully checked, and the data checking work cannot be completed only by manpower.
In order to effectively solve the above problems, it is necessary to provide a new data conversion method, which can quickly calculate the service data of the sub-network layer on the basis of ensuring the data accuracy of the issuing device, so as to improve the perception and usability of the client.
Disclosure of Invention
Aiming at the problems in the prior art, the invention discloses a method and a system for converting network management configuration data, which adopt a data reverse conversion method to quickly generate network management configuration data of a network management system with a new version on the basis of consistent data of equipment layers of a new network management system and an old network management system.
The invention provides a network management configuration data conversion method, which is suitable for upgrading the version of network management configuration data of an old version of network management system, wherein the network management configuration data comprises basic configuration data and service data; the network management configuration data conversion method comprises the following steps:
carrying out one-to-one format conversion on the basic configuration data to obtain first data with a format meeting the requirements of the network management system of the new version;
generating a network element layer data model by the service data, generating a sub-network layer data model by the network element layer data model, and importing the custom data into the sub-network layer data model to obtain second data with a format meeting the requirements of a new version of the network management system;
and the first data and the second data form network management configuration data of a network management system with a new version.
On the basis of the technical scheme, the basic configuration data comprises safety data, topology data, alarm data, performance data, frame data, slot disk data and network element data.
On the basis of the above technical solution, the service data includes subnet configuration data.
On the basis of the above technical solution, the method for converting network management configuration data further includes:
before the version of the network management configuration data of the network management system of the old version is upgraded, the consistency of the network management configuration data of the network management system of the old version is checked before conversion.
On the basis of the technical scheme, the consistency check before conversion comprises the following specific steps:
and issuing subnet configuration data contained in the network management configuration data of the network management system of the old version to generate device layer data, comparing the generated device layer data with the device layer data stored in the device layer of the network management system of the old version, and correcting the network management configuration data of the network management system of the old version according to a comparison result until the generated device layer data is consistent with the device layer data stored in the device layer.
On the basis of the above technical solution, the method for converting network management configuration data further includes:
and after the network management configuration data of the network management system with the new version is generated, the consistency check is carried out on the converted network management configuration data of the network management system with the new version after conversion.
On the basis of the technical scheme, the consistency check after conversion comprises the following specific steps:
and issuing subnet configuration data contained in the network management configuration data of the new version of the network management system to generate device layer data, comparing the generated device layer data with the device layer data stored in the device layer of the old version of the network management system, judging whether the network management configuration data of the new version of the network management system is correct according to a comparison result, and obtaining a judgment result.
On the basis of the technical scheme, the custom data comprises sub-network layer service user custom data and network element layer consistency configuration data.
On the basis of the technical scheme, the configuration data is converted into first data in a one-to-one format by operating a basic configuration conversion tool;
generating a network element layer data model from the service data by operating a network element layer configuration conversion tool;
and generating a sub-network layer data model from the network element layer data model by operating a sub-network splicing back-calculation tool.
The invention also provides a network management configuration data conversion system, which comprises:
the first conversion module is used for performing one-to-one format conversion on the basic configuration data to obtain first data with a format meeting the requirements of the network management system of the new version;
the second conversion module is used for generating a network element layer data model according to the service data and generating a sub-network layer data model according to the network element layer data model, and the format of the sub-network layer data model conforms to the requirements of a new version of network management system;
the subnet business generating module is connected with the second conversion module and used for importing the custom data into the subnet layer data model to obtain second data;
and the configuration generation module is connected with the first conversion module and the subnet service generation module and is used for generating new version network management configuration data of the network management system according to the first data and the second data.
The invention has the beneficial effects that: a new thought is provided for the processing of the super-large-scale data volume of the PTN network management system, a reverse generation method different from the traditional forward creation process is provided for the configuration data conversion process in the switching process of a new network management system and an old network management system, on the basis of the consistency of the data of the new network management equipment layer and the old network management equipment layer, a unified network element layer data model is generated by converting the network management configuration data of the old network management system containing various different equipment layer data, the unified sub-network layer data model is generated by the network element layer data model, the network management configuration data of the new network management system is further generated, and compared with the existing forward creation process, the creation speed is increased by more than ten times.
Drawings
Fig. 1 is a flowchart of a network management configuration data conversion method in the embodiment of the present invention.
FIG. 2 is a base configuration conversion sequence diagram for running a base configuration conversion tool.
Fig. 3 is a sequence diagram of a network element layer data model generated by operating a network element layer configuration conversion tool.
Fig. 4 is a flow chart of back calculation of data splicing of subnet Tunnel layer.
Fig. 5 is a flowchart of inverse calculation for splicing subnet L2VPN data.
Fig. 6 is a flowchart of inverse calculation for splicing subnet L3VPN data.
Fig. 7 is a schematic diagram of functional modules of a network management configuration data conversion system in the embodiment of the present invention.
Detailed Description
In the following embodiments, the technical features may be combined with each other without conflict.
The following description of the embodiments of the invention is provided in connection with the accompanying drawings:
the basic principle of the conversion is that the data of the equipment which is issued by the interaction of a new (UNM 2000) network management system and an old (OTNM 2000) network management system and the equipment, namely the data of the equipment layer is a piece of data, and on the basis of the consistency of the data of the new and old network management equipment layers, the invention relates to the format conversion of the new and old sets of network management basic configuration data, the model conversion of the data of a network element layer and the back calculation splicing process of the data of a sub-network layer. Which comprises the following steps:
the network management configuration data of the old version of network management system comprises basic configuration data, service data and custom data. And performing one-to-one format conversion on the configuration data to obtain first data, wherein the one-to-one format conversion is that the data content is unchanged, and the data format conversion meets the requirements of a network management system of a new version. And generating a network element layer data model by the service data, generating a sub-network layer data model by the network element layer data model, and importing the custom data into the sub-network layer data model to obtain second data, namely sub-network layer service data. And the first data and the second data form network management configuration data of a network management system with a new version.
The invention adopts a reverse generation method different from the traditional forward creation process, and compared with the existing forward creation process, the creation speed is improved by more than ten times.
First embodiment
Referring to fig. 1, the method for converting network management configuration data in this embodiment includes the steps of:
and S2, respectively storing the network management configuration data and the user-defined data of the network management system of the old version into a first file and a second file, wherein the first file comprises basic configuration data and service data. The first file is a binary stream file of various issuing equipment, wherein the basic configuration data comprises security data, topology data, alarm data, performance data, frame data, slot disk data and network element data, the service data comprises subnet configuration data, and the first file is a custom type file, such as a CFG file. The subnet layer data contained in the custom data is subnet layer service user custom data (including service grade, service classification, client name and the like which are input by a user and stored in a network manager but not sent out equipment) of various non-sent equipment layers, the network element layer data contained in the custom data is resource state data which ensures consistency among different network elements and accelerates the calculation process of the network manager, and the second file is an XML script. During specific operation, version upgrading can be directly carried out based on the network management configuration data and the user-defined data without being stored as a first file and a second file.
An XML script can be simply defined as subnet key + custom content (resource data, etc.), as follows: tunnel keyword: ingressId + EngressId + TunnelId + LspId. PW keyword: srcNeId (source network element id) + SinkNeId ((sink network element id) + InPwLabel + OutPwLabel. L2VPN keyword: PW keyword set. L3VPN keyword: vrfName).
And S3, performing one-to-one format conversion on the basic configuration data to obtain first data with a format meeting the requirements of the network management system of the new version. The basic configuration data is data which is not changed in the running and upgrading processes of the new and old versions of the network management system, and when the new and old network management systems are updated, the data only needs to be updated and then directly imported into the database of the new version of the network management system. Specifically, the basic configuration conversion tool is operated to modify the format of the basic configuration data so that the basic configuration data meets the requirements of the network management system of the new version, and then the basic configuration data is imported into the database of the network management system of the new version.
And S4, generating a network element layer data model from the service data, and generating a sub-network layer data model from the network element layer data model, wherein the format of the sub-network layer data model conforms to the requirements of a new version of network management system. Specifically, a network element layer data model is generated from service data by operating a network element layer configuration conversion tool.
And S5, generating a sub-network layer data model by the network element layer data model. Specifically, a subnet layer data model is generated from the network element layer data model through a subnet splicing back calculation tool. The sub-network layer model mainly comprises basic business models such as Tunnel, PW, L2VPN, L3VPN and the like.
And S6, importing the custom data into the data model of the sub-network layer to obtain second data with a format meeting the requirements of the network management system of the new version. And the consistency of the sub-network layer service data and the network element layer service data of the new network management system is ensured.
And S7, the first data and the second data form network management configuration data of a new version of network management system.
In this embodiment, a basic configuration file in the CFG file is directly converted into a one-to-one format to generate a part of new network management configuration data, that is, first data, service data in the CFG file sequentially generates a network element layer data model and a subnet layer data model, and then an XML script is introduced into the subnet layer data model to generate another part of new network management configuration data, that is, second data, where the final network management configuration data of the new version of network management system includes the first data and the second data.
On the basis of the consistency of the data of the new network management equipment layer and the old network management equipment layer, the format conversion is carried out by the basic configuration data of the network management system of the old version to generate first data; the method comprises the steps that a unified network element layer data model is generated by converting service data of an old version of network management system containing various different device layer data, the network element layer data model generates a unified sub-network layer data model, and further, custom data is imported to generate network management configuration data of a new version of network management system.
Second embodiment
Referring to fig. 1, the method for converting network management configuration data in this embodiment further includes the following steps:
s1, consistency check before conversion is carried out on network management configuration data of the network management system of the old version. Specifically, the subnet configuration data contained in the network management configuration data of the old version of the network management system is issued to generate device layer data, the generated device layer data is compared with the device layer data stored in the device layer of the old version of the network management system, and the network management configuration data of the old version of the network management system is corrected according to the comparison result until the generated device layer data is consistent with the device layer data stored in the device layer.
In this embodiment, in the long-time operation process of the network manager, different data issuing entries may cause the subnet configuration data in the network management configuration data of the network management system of the old version to be inconsistent with the actually issued device data, the basis of the configuration conversion is the actually issued device data, and the data seen by the user is the subnet configuration data, so it is necessary to ensure that the old network management subnet configuration data is consistent with the actually issued device data before the conversion.
Generating device layer data by issuing subnet configuration data in the network management configuration data of the old version of the network management system, comparing the generated device layer data with the device layer data stored in the device layer of the old version of the network management system, for example, comparing whether the values of the two fields are consistent or not by human eyes, and modifying the network management configuration data of the old version of the network management system and/or the device layer data stored in the device layer if the values are inconsistent until the device layer data generated by the subnet configuration data in the network management configuration data of the old version of the network management system is consistent with the device layer data stored in the device layer, and at the moment, completing consistency check before conversion.
The consistency check before the conversion can ensure the integrity and consistency of main resource data in network management configuration data in the operation and upgrading processes of the network management systems of the new and old versions, and ensure the data consistency in the operation process of the network management.
Third embodiment
Referring to fig. 1, the method for converting network management configuration data in this embodiment further includes the following steps:
and S8, performing consistency check after conversion on the network management configuration data of the new version of the network management system. Specifically, the subnet configuration data contained in the network management configuration data of the network management system of the new version is issued to generate device layer data, the generated device layer data is compared with the device layer data stored in the device layer of the network management system of the old version, and whether the network management configuration data of the network management system of the new version is correct or not is judged according to the comparison result, and the judgment result is obtained.
In this embodiment, after the network management configuration data of the new version of the network management system is generated, the correctness of the network management configuration data needs to be checked, the checking method is to verify through the device layer data stored in the device layer of the old version of the network management system, if the device layer data generated by the subnet configuration data contained in the network management configuration data of the new version of the network management system is issued is consistent with the device layer data stored in the device layer of the old version of the network management system, the network management configuration data of the new version of the network management system is correct, otherwise, the problem is solved, and the network management configuration data of the new version of the network management system needs to be corrected.
Fourth embodiment
Referring to fig. 2, in step S3 of the method for converting network management configuration data, a basic configuration conversion tool is operated, and first data is obtained through one-to-one format conversion of basic configuration data. The internal logic of the basic configuration conversion tool is subdivided according to levels, and from the data processing perspective, the basic configuration conversion tool is divided into a conversion controller (or called conversion control logic framework), an unl file processing module, a preprocessing module and a conversion module.
A conversion controller: and the system is responsible for overall conversion flow control and controls the sequential work of other modules in the basic configuration conversion tool.
The unl file processing module: and the system is responsible for processing the unl file (namely the basic configuration data) and generating an intermediate file so that the data format of the intermediate file conforms to the specification.
A preprocessing module: and processing the data of the intermediate file to make the intermediate file meet the data requirement of a specific execution conversion module.
A conversion module: and finishing the final conversion processing to generate a part of new network management configuration data (namely the first data).
Referring to fig. 3, in step S4 of the method for converting network management configuration data, a network element layer data model is generated from service data by operating a network element layer configuration conversion tool. Specifically, a network element layer data model is generated through a network element layer configuration conversion tool, wherein service data comprise single-disk configuration data and network element configuration data, and the single-disk configuration data and the network element configuration data need to be converted independently to generate network element layer data meeting the format requirements of a new network management system. The internal logic of the network element layer configuration conversion tool is subdivided according to the hierarchy, and from the data processing perspective, the network element layer data configuration conversion tool is divided into a network element layer data synchronization manager, a network element back-calculation device, a single-disk back-calculation device and a service converter.
Network element layer data sync manager (NeDataSyncMgr): the method is a factory class and mainly used for instantiating a specific network element back calculation object and controlling the overall flow of data synchronization.
Network element back-calculator (cnerrvcalc): and a specific single-disk back calculator is created to control the data synchronization process.
Single disk back calculator (CBoardRvsCalc): and creating a specific service converter and controlling a specific service conversion process.
Service converter (cbusiconverter): the specific service conversion implementation logic executes the data synchronization calculation of the specific configuration block to generate another part of new network management configuration data (i.e. the second data).
Fifth embodiment
In step S6 of the method for converting network management configuration data, a subnet layer data model is generated from a network element layer data model through a subnet splicing back-calculation tool, and the subnet layer data model mainly includes basic service models such as Tunnel, PW, L2VPN, L3VPN, and the like.
In step S5, referring to fig. 4, a flowchart of inverse computation of data concatenation of the subnet Tunnel layer includes the following steps:
step a1, starting tunnel synchronization;
step a2, acquiring all tunnel data of the current network element;
step a3, traversing each tunnel data, and judging whether the traversal is finished:
if the judgment result is yes, the traversal is finished;
if the judgment result is negative, the node type is obtained, and the node type is judged:
if the node type is a source node, searching a tunnel path (output port PortKey: m _ stOut) along the forward direction of the output port, and turning to the step a4;
if the node type is an intermediate node, searching the channel path (output port PortKey: m _ stOut) along the output port in the forward direction, searching the channel path (input port PortKey: m _ stln) along the input port in the reverse direction, and turning to the step a4;
if the node type is a host node, a tunnel path (port Key of the input port: m _ stln) is searched reversely along the input port, and the step a4 is switched;
step a4, constructing a tunnel route, and judging whether the tunnel route is complete:
if the judgment result is negative, turning to the step a3;
if the judgment result is yes, continuously judging whether the tunnel route is unidirectional:
if yes, turning to the step a5;
if the judgment result is negative, turning to the step a8;
step a5, searching a client layer according to the service id (CTunnel: m _ iSeviceid) of the tunnel of the source node, and judging whether the tunnel of the node has the client layer:
if the judgment result is yes, searching the opposite-end tunnel according to the client layer, inquiring opposite-end tunnel data, and turning to the step a6;
if the judgment result is negative, turning to the step a7;
step a6, searching a reverse tunnel path by taking the tunnel of the node as a starting point, and judging whether the tunnel route is complete:
if yes, turning to the step a7;
if the judgment result is negative, turning to the step a3;
step a7, determining the one-way or two-way of the tunnel according to the existence of the reverse tunnel;
step a8, obtaining all tunnel protection groups (CASSPProtectgroup: m _ vCTWork) according to the tunnel service id (CTunel: m _ iSeviceid) of the source node, and judging whether the tunnel protection groups exist:
if yes, searching for a protection tunnel service id according to a protection object id (CASSPProtectgroup: m _ vctProted) of the Aps protection group, and turning to a step a9;
if the judgment result is negative, turning to the step a10;
step a9, searching the tunnel protection path by the id (CTunnel: m _ iSeviceid) of the tunnel protection path, and judging whether the tunnel route is complete:
if the judgment result is yes, determining a protection path route;
if the judgment result is negative, turning to the step a3;
step a10, generating a complete VpPath parameter list (including oam/bfd) for creating and using;
step a11, creating a subnet service object VpPath (if protection exists, creating a protection group, protecting the path object VpPath, setting a monitoring type, etc.); the creation of a data model of the sub-network layer is completed in the step;
step a12, updating the network element service object (CTunnel, the service id of the CASSPProtectGroup, the service id of the CPw service layer tunnel, if it is bidirectional, the network element layer forward and backward unidirectional tunnels need to be merged into a bidirectional tunnel).
In conclusion, the data splicing back-calculation flow steps of the sub-network Tunnel layer are that the algorithm is repeated for each network element, and the node data which is successfully spliced or failed to be spliced is not accessed any more. When searching for the network element layer Tunnel node in the forward direction, the next hop is found out by matching the output port and the outgoing label of the node, and the previous hop is found out by matching the input port and the incoming label in the reverse search. When a unidirectional (forward or reverse) Tunnel is searched, finding out a reverse Tunnel through a customer layer PW or L3VPN of the Tunnel, and then creating a bidirectional Tunnel; if a Tunnel is added to the protection group, the Tunnel of the protection path needs to be searched. The fault detection type (OAM/BFD) of the Tunnel is determined by judging an OAM object ID and a BFD object ID associated with the Tunnel of the original node. Generating a complete subnet service object, wherein the VpPath parameter comprises Tunnel routing information, protection information, a monitoring type and the like; if there is a protected group, the protected group is created before the subnet object VpPath is created. After the creation of the subnet object is completed, the network element layer protection group object ID (including the associated work and protection Tunnel), the Tunnel object ID, and the Tunnel object ID associated with the Pseudo Wire (PW) in the client layer need to be updated.
In the step S5, referring to fig. 5, the inverse calculation flow chart of the subnet L2VPN data splicing includes the following steps:
step b1, acquiring all v pws/v pls of the current network element;
b2, traversing each piece of v pws/v pls;
b3, traversing each vc, and judging whether the traversal is finished:
if the judgment result is yes, the traversal is finished;
if the judgment result is negative, turning to the step b4;
b4, searching a network element (CPw: m _ iVcld) of the opposite end through pw;
b5, finding out the v pws/v pls of the same pw of the opposite terminal network element;
step b6, recording the information of the nodes of the v pws/v pls, and judging whether other vc exists:
if the judgment result is yes, turning to the step b3;
if the judgment result is negative, turning to the step b7;
b7, generating a complete l2vpn service parameter table (CL 2 vpn);
step b8, creating a pw subnet object;
b9, updating the pw service object of the network element layer;
step b10, creating an l2vpn subnet object; the creation of a data model of the sub-network layer is completed in the step;
and b11, updating the v pws/v pls service object of each pe node of the network element layer.
In conclusion, the step of the sub-network L2VPN data splicing back calculation process is to determine ELine, ETree and ELan networking types according to the number of VPLS and the PW of VPWS working/protection; when a PW has a protection group, the protection group is required to be created before the PW is created, and a working object and a protection object are associated; and when the VPWS or VPLS of the network element layer is updated, the ID of the new PW service object of the service layer needs to be updated synchronously.
In the step S5, referring to fig. 6, the inverse calculation flow chart of the subnet L3VPN data splicing includes the following steps:
step c1, putting an L3vpn needing to be back-calculated into a list to be back-calculated;
step c2, circularly obtaining an L3vpn list;
step c3, searching all L3vpnTunnel related to the network element layer L3 cpn;
step c4, circularly obtaining each L3vpnTunnel;
step c5, searching PeerNe (m _ iPeerlp of the local end L3 vpnTunnel) according to the selected L3vpnTunnel;
step c6, searching an opposite terminal L3vpn (m _ iPeerLabel of the local terminal network element L3vpnTunnel = = m _ ilnLabel of the opposite terminal network element L3 vpn) through an opposite terminal label of the local terminal L3vpnTunnel;
step c7, judging whether an opposite end L3vpn is found:
if the judgment result is yes, turning to the step c8;
if the judgment result is negative, the discrete L3vpn service is used, and the operation is ended;
step c8, judging whether the PeerL3vpn node is already calculated:
if the judgment result is yes, turning to the step c10;
if the judgment result is negative, turning to the step c9;
step c9, adding the L3vpn node into a list needing to be calculated;
step c10, judging whether the node L3vpnTunnel is already calculated:
if yes, go to step c11;
if the judgment result is negative, turning to the step c4;
step c11, judging whether all L3vpn nodes are calculated:
if yes, go to step c12;
if the judgment result is negative, turning to the step c2;
step c12, judging whether the service layer Tunnel is back-calculated successfully:
if yes, go to step c14;
if the judgment result is negative, turning to the step c13;
step c13, searching all service tunnels;
c14, splicing the subnet data to create a subnet object; the creation of a data model of the sub-network layer is completed in the step;
and step c15, refreshing the network element data.
In summary, the step of the back calculation flow for splicing the subnet L3VPN data is to traverse all L3 vpnthannel data of the current network element layer L3 VPN. And searching an opposite terminal L3VPN (the opposite terminal Label of the local terminal L3vpnTunnel is the same as the opposite terminal L3VPN object incoming Label) through an opposite terminal network element and an opposite terminal Label of the L3vpnTunnel data. And step S507 and S508 of re-operation are performed to search each Tunnel peer L3VPN node of each L3VPN node. Repeating steps S507, S508 and S509 for the searched new L3VPN node until no new L3VPN node is found any more and recording the service layer tunnels of all nodes. And traversing the network element configuration data of the service layer Tunnel, and searching the Tunnel until all tunnels are back-calculated successfully. And generating a subnet L3VPN object according to all searched network element layer L3 VPNs.
In this embodiment, the hierarchical search synchronously forms a network element layer data model, and the network element layer data models are spliced to form an end-to-end sub-network layer data model. The method can ignore the difference of the data structure expression modes of the network management systems of different versions, and form the network management configuration data of the network management system of a new version based on the same device layer data. In the whole data conversion process, the data of each network element is independent and unrelated, and can be simultaneously carried out in a concurrent mode, so that the conversion time is greatly shortened, and the efficiency is improved.
Sixth embodiment
Referring to fig. 7, the network management configuration data conversion system in this embodiment includes:
and the first conversion module 1 is used for performing one-to-one format conversion on the basic configuration data to obtain first data of which the format meets the requirement of the network management system of the new version.
And the second conversion module 2 is used for generating a network element layer data model according to the service data and generating a sub-network layer data model according to the network element layer data model, wherein the format of the sub-network layer data model conforms to the requirements of a new version of network management system.
And the subnet business generating module 3 is connected with the second converting module 2 and is used for importing the custom data into the subnet layer data model to obtain second data.
And the configuration generation module 4 is connected with the first conversion module 1 and the subnet service generation module 3, and is used for generating network management configuration data of a new version of network management system according to the first data and the second data.
The network management configuration data conversion system adopts a reverse generation method different from the traditional forward creation process, and compared with the existing forward creation process, the creation speed is improved by more than ten times.
While the specification concludes with claims defining exemplary embodiments of particular structures for practicing the invention, it is believed that other modifications will be made in the spirit of the invention. While the invention has been described in connection with what is presently considered to be the preferred embodiment, it is not intended to be limited to the disclosed embodiment.
Various alterations and modifications will no doubt become apparent to those skilled in the art after reading the specification. It is therefore intended that the appended claims be interpreted as covering all alterations and modifications as fall within the true spirit and scope of the invention. Any and all equivalent ranges and contents within the scope of the claims should be considered to be within the intent and scope of the present invention.
Claims (7)
1. A network management configuration data conversion method is suitable for version upgrading of network management configuration data of an old version of network management system, wherein the network management configuration data comprises basic configuration data and service data; the method for converting the network management configuration data is characterized by comprising the following steps:
carrying out one-to-one format conversion on the basic configuration data to obtain first data with a format meeting the requirements of the network management system of the new version;
generating a network element layer data model by the service data, generating a sub-network layer data model by the network element layer data model, and importing the custom data into the sub-network layer data model to obtain second data with a format meeting the requirements of a new version of network management system;
the first data and the second data form network management configuration data of a new version of network management system;
the service data comprises subnet configuration data; before upgrading the version of the network management configuration data of the network management system of the old version, carrying out consistency check before conversion on the network management configuration data of the network management system of the old version; the consistency check before conversion comprises the following specific steps:
and issuing subnet configuration data contained in the network management configuration data of the network management system of the old version to generate device layer data, comparing the generated device layer data with the device layer data stored in the device layer of the network management system of the old version, and correcting the network management configuration data of the network management system of the old version according to a comparison result until the generated device layer data is consistent with the device layer data stored in the device layer.
2. The network management configuration data conversion method according to claim 1, wherein the basic configuration data includes security data, topology data, alarm data, performance data, frame data, slot disk data, and network element data.
3. The method for converting webmaster configuration data according to claim 1, wherein the method for converting webmaster configuration data further comprises:
and after the network management configuration data of the network management system with the new version is generated, the consistency check is carried out on the converted network management configuration data of the network management system with the new version after conversion.
4. The network management configuration data conversion method according to claim 3, characterized in that the steps of consistency check after conversion are as follows:
and issuing subnet configuration data contained in the network management configuration data of the new version of the network management system to generate device layer data, comparing the generated device layer data with the device layer data stored in the device layer of the old version of the network management system, judging whether the network management configuration data of the new version of the network management system is correct according to a comparison result, and obtaining a judgment result.
5. The network management configuration data conversion method according to claim 1, characterized in that the customization data includes sub-network layer service user customization data and network element layer consistency configuration data.
6. The network management configuration data conversion method according to claim 1, characterized in that the configuration data is subjected to one-to-one format conversion by operating a basic configuration conversion tool to obtain first data;
generating a network element layer data model from the service data by operating a network element layer configuration conversion tool;
and generating a sub-network layer data model from the network element layer data model by operating a sub-network splicing back calculation tool.
7. A network management configuration data conversion system, comprising:
the first conversion module is used for performing one-to-one format conversion on the basic configuration data to obtain first data with a format meeting the requirements of the network management system of the new version;
the second conversion module is used for generating a network element layer data model according to the service data and generating a sub-network layer data model according to the network element layer data model, and the format of the sub-network layer data model conforms to the requirements of a new version of network management system; the service data comprises subnet configuration data; before upgrading the version of the network management configuration data of the network management system of the old version, carrying out consistency check before conversion on the network management configuration data of the network management system of the old version; the consistency check before conversion comprises the following specific steps:
issuing subnet configuration data contained in the network management configuration data of the old version of the network management system to generate equipment layer data, comparing the generated equipment layer data with the equipment layer data stored in the equipment layer of the old version of the network management system, and correcting the network management configuration data of the old version of the network management system according to a comparison result until the generated equipment layer data is consistent with the equipment layer data stored in the equipment layer;
the subnet business generating module is connected with the second conversion module and used for importing the custom data into the subnet layer data model to obtain second data;
and the configuration generation module is connected with the first conversion module and the subnet service generation module and is used for generating new version network management configuration data of the network management system according to the first data and the second data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010953965.8A CN112165395B (en) | 2020-09-11 | 2020-09-11 | Network management configuration data conversion method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010953965.8A CN112165395B (en) | 2020-09-11 | 2020-09-11 | Network management configuration data conversion method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112165395A CN112165395A (en) | 2021-01-01 |
| CN112165395B true CN112165395B (en) | 2023-04-18 |
Family
ID=73858946
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010953965.8A Active CN112165395B (en) | 2020-09-11 | 2020-09-11 | Network management configuration data conversion method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112165395B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859348A (en) * | 2006-02-20 | 2006-11-08 | 华为技术有限公司 | Service capacity coordinating system, calling system and method |
| CN105573830A (en) * | 2014-10-09 | 2016-05-11 | ***股份有限公司 | Virtual machine migration method |
| CN110348201A (en) * | 2019-05-22 | 2019-10-18 | 中国科学院信息工程研究所 | A kind of configuration method and device of device security policy |
| CN110609906A (en) * | 2019-09-16 | 2019-12-24 | 金色熊猫有限公司 | Knowledge graph construction method and device, storage medium and electronic terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10142180B2 (en) * | 2014-11-26 | 2018-11-27 | Edgewater Networks, Inc. | Method and system for providing unified configuration information to disparate system software components |
-
2020
- 2020-09-11 CN CN202010953965.8A patent/CN112165395B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859348A (en) * | 2006-02-20 | 2006-11-08 | 华为技术有限公司 | Service capacity coordinating system, calling system and method |
| CN105573830A (en) * | 2014-10-09 | 2016-05-11 | ***股份有限公司 | Virtual machine migration method |
| CN110348201A (en) * | 2019-05-22 | 2019-10-18 | 中国科学院信息工程研究所 | A kind of configuration method and device of device security policy |
| CN110609906A (en) * | 2019-09-16 | 2019-12-24 | 金色熊猫有限公司 | Knowledge graph construction method and device, storage medium and electronic terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112165395A (en) | 2021-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112787841B (en) | Fault root cause positioning method and device and computer storage medium | |
| US7484004B2 (en) | Analyzing an access control list for a router to identify a subsumption relation between elements in the list | |
| CN107370673B (en) | Method, controller and system for establishing forwarding path in network | |
| US20140092726A1 (en) | Method for mapping a network topology request to a physical network and communication system | |
| GB2433675A (en) | Routing and communications circuit design using high and low level network models | |
| Chen et al. | A review of automated formal verification of ad hoc routing protocols for wireless sensor networks | |
| CN113453260B (en) | Method for realizing random selection and guarantee of 5G transmission sub-slices based on dynamic scheduling algorithm | |
| US9674081B1 (en) | Efficient mapping of table pipelines for software-defined networking (SDN) data plane | |
| EP3637690B1 (en) | Service configuration-driven flow table method and device | |
| CN107645402A (en) | A kind of route management method and device | |
| Lamali et al. | Algorithmic and complexity aspects of path computation in multi-layer networks | |
| Beckett et al. | Katra: Realtime verification for multilayer networks | |
| CN115225493A (en) | Wiraguard-based configuration generation method and equipment for networking nodes | |
| CN112165395B (en) | Network management configuration data conversion method and system | |
| Genda et al. | Multi-stage network recovery considering traffic demand after a large-scale failure | |
| CN112087321B (en) | TAPI layered topology design method, medium, device and service creation method | |
| CN113872784B (en) | Network configuration verification method and device | |
| CN104917623A (en) | Method and device for realizing SDN network communication management | |
| CN107888282B (en) | Circuit whole-course route calculation method of optical transmission network | |
| CN114070746A (en) | Circuit series connection method and system for multi-type transmission network | |
| CN108667508B (en) | Shared link risk group generation method and device | |
| US20030046378A1 (en) | Apparatus and method for existing network configuration | |
| WO2016070551A1 (en) | Route computing method and device | |
| Schneider et al. | Taming the transient while reconfiguring BGP | |
| JP7294450B2 (en) | Apparatus, method and program for generating network topology |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |