CN113114493A - Network element configuration constraint checking method and system - Google Patents
Network element configuration constraint checking method and system Download PDFInfo
- Publication number
- CN113114493A CN113114493A CN202110359999.9A CN202110359999A CN113114493A CN 113114493 A CN113114493 A CN 113114493A CN 202110359999 A CN202110359999 A CN 202110359999A CN 113114493 A CN113114493 A CN 113114493A
- Authority
- CN
- China
- Prior art keywords
- constraint
- network element
- check
- element configuration
- checking
- 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.)
- Granted
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
-
- 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
Abstract
The invention discloses a network element configuration constraint checking method and a system, wherein the method comprises the following steps: loading a constraint check manager and constraint rule checkers, wherein different network element types correspond to different constraint check managers, and each constraint check manager respectively registers a plurality of constraint rule checkers for different network element configuration types according to functional requirements; after receiving the change message of the network element configuration, determining the type of the change message, and obtaining the type of the network element and the type of the network element configuration by analyzing the network element configuration data; searching a corresponding constraint check manager according to the network element type, and acquiring a related constraint rule checker set from the corresponding constraint check manager according to the network element configuration type; and each constraint rule checker performs corresponding constraint check according to the corresponding constraint type and the change message type and reports the constraint check result to the client. The consistency, the validity and the correctness of the network element configuration data can be effectively ensured by the constraint checking method.
Description
Technical Field
The present invention belongs to the technical field of network device management, and more particularly, to a network element configuration constraint checking method and system.
Background
The consistency, validity and correctness of the network element configuration data are important indexes of the network equipment management system, and also form constraint requirements on the configuration data. Firstly, in the network device management system, the service and the configuration need to perform validity check on the relevant data of the network element configuration during the creation or modification process, such as whether a data field is not empty, whether the data field is in a value range, whether the upper limit requirement of the device is exceeded, whether a uniqueness principle is violated, and the like, otherwise, the service creation failure or the configuration activation abnormality and the like are caused, and the function use of the network device is affected. Secondly, some network management operations in the network equipment management system have precedence requirements and cannot be reversed; for example, there is a certain correlation between the service and the configuration data, and it is necessary to check whether the service is carried when deleting or modifying the configuration, otherwise, the configuration cannot be modified at will, so as to avoid affecting the smoothness of the service, and therefore, it is necessary to perform constraint check on the sequence of the network management operation. Thirdly, the network equipment management system needs to support reconstruction constraints, that is, the inventory configuration can be reconstructed in a constraint relation when the engineering is upgraded or the network element business model is changed, so as to ensure the data consistency and correctness of the whole system. In addition, for some illegal or improper operations of the user, the prompt information of the current system is often not clear enough or lacks necessary prompts, which affects the user experience and quickly troubleshoots the problems.
In view of this, it is desirable to provide an efficient constraint checking method and system, which can implement constraint checking on validity of network element configuration data and sequence of network management operations, and can reconstruct constraints when a project is upgraded or a network element service model is changed, thereby ensuring consistency, validity and correctness of network element configuration data. In addition, the prompt information of the checking result needs to be constrained to be clear and accurate so as to improve the efficiency of network management operation of the user, improve the user experience and conveniently investigate the cause of the problem.
Disclosure of Invention
The invention provides a network element configuration constraint checking method and a network element configuration constraint checking system aiming at the defects or the improvement requirements in the prior art, and aims to effectively realize the constraint checking of the legality of network element configuration data and the sequence of network management operation and perform reconstruction constraint if necessary, thereby solving the technical problem that the traditional scheme is difficult to ensure the consistency, the legality and the correctness of the network element configuration data.
To achieve the above object, according to an aspect of the present invention, there is provided a network element configuration constraint checking method, including:
loading a constraint checking manager and a constraint rule checker; the different network element types correspond to different constraint check managers, and each constraint check manager respectively registers a plurality of constraint rule checkers for different network element configuration types according to functional requirements;
after receiving the change message of the network element configuration, determining the type of the change message, and obtaining the type of the network element and the type of the network element configuration by analyzing the network element configuration data;
searching a corresponding constraint check manager according to the network element type, and acquiring a related constraint rule checker set from the corresponding constraint check manager according to the network element configuration type;
and each constraint rule checker in the constraint rule checker set carries out corresponding constraint check according to the corresponding constraint type and the change message type, and reports the constraint check result to the client.
Preferably, before the loading constraint check manager and constraint rule checker, the method further comprises:
defining different constraint types according to functional requirements and abstracting, wherein the constraint types comprise one or more of value range constraint, uniqueness constraint, main foreign key constraint and specification constraint; wherein:
the value range constraint is used for carrying out constraint check on the validity of the current network element configuration data;
constraint relation data corresponding to the uniqueness constraint are stored in a database and used for carrying out constraint check on the uniqueness of the network element configuration, and the corresponding constraint relation data are stored in a Key-Value format;
the constraint relation data corresponding to the main foreign Key constraint is stored in a database and used for carrying out constraint check on the sequence of network management operation, and the corresponding constraint relation data is stored in a Key-Value format;
the constraint relation data corresponding to the specification constraint is stored in a database and is used for carrying out constraint check on the network element configuration specification; and the corresponding constraint relation data is stored in a Key-Value format.
Preferably, before the loading constraint check manager and constraint rule checker, the method further comprises:
setting a rule definition script and a constraint error code script; the rule definition script is used for a user to self-define and set an upper limit value of specification constraint, whether to shield the check of a certain constraint rule checker and whether to start a reconstruction constraint function, and the constraint error code script is used for defining a constraint check error code information template.
Preferably, for each constraint rule checker in the constraint rule checker set, the performing corresponding constraint check according to the corresponding constraint type and the change message type specifically includes:
if the constraint type corresponding to the constraint rule checker is value domain constraint, executing a corresponding constraint checking method according to the change message type configured by the network element, and obtaining a corresponding constraint checking result; wherein the change message type comprises one or more of addition, deletion, modification, activation and deactivation;
if the constraint type corresponding to the constraint rule checker is a non-value range constraint, calculating constraint Key information according to network element configuration data, and searching corresponding constraint relation data from a database according to the constraint Key information; and then, executing a corresponding constraint checking method according to the change message type configured by the network element and the searched constraint relation data, and obtaining a corresponding constraint checking result.
Preferably, for value domain constraints, in the process of executing the corresponding constraint checking method according to the type of the change message configured by the network element, the method further includes:
if the constraint check has conflict, using the network element configuration data as a parameter to format a constraint check error code information template, and storing the formatted error code information as a constraint check result; wherein the constrained check error code information template is defined by a constrained error code script.
Preferably, for the non-value range constraint, in the process of executing the corresponding constraint checking method according to the change message type configured by the network element and the found constraint relationship data, the method further includes:
if the constraint check has conflict, using the network element configuration data as a parameter to format a constraint check error code information template, and storing the formatted error code information as a constraint check result; if the constraint check does not have conflict, updating the corresponding constraint relation data and storing the constraint relation data in the database; wherein the constrained check error code information template is defined by a constrained error code script.
Preferably, when a new configuration is introduced into the network device management system or the network element service model is updated, the reconstruction constraint is performed, specifically: and clearing the current constraint relation data in the database, executing constraint check on the current network element configuration again, generating new constraint relation data and storing the new constraint relation data in the database.
Preferably, the clearing of the current constraint relationship data in the database, performing constraint check on the current network element configuration again, generating new constraint relationship data, and storing the new constraint relationship data in the database specifically includes:
for each network element, searching a network element configuration type set of a registered constraint rule checker from a corresponding constraint check manager according to the network element type, and clearing constraint relation data corresponding to the network element from the database;
acquiring each network element configuration item of the network element according to the network element configuration type set, and sequentially executing a constraint checking method for changing the message type into increased configuration on each network element configuration item by using a constraint rule checker registered by the network element;
for the constraint rule checker with the constraint type of non-value range constraint, updating corresponding constraint relation data after executing a constraint checking method, and storing the new constraint relation data into the database;
if constraint checking conflict exists in the constraint checking process, generating a constraint conflict abstract and storing the constraint conflict abstract in the database.
According to another aspect of the present invention, there is provided a network element configuration constraint checking system, comprising a constraint checking framework, a memory and a processor; wherein the constraint checking framework comprises a constraint checking interface, a constraint checking manager, a constraint rule checker and a database;
the constraint checking interface is used for receiving a change message of network element configuration and triggering constraint checking;
the constraint check managers are provided with one or more constraint check managers which respectively correspond to different network element types, and each constraint check manager respectively registers a plurality of different constraint rule checkers for different network element configuration types according to functional requirements;
the constraint rule checker is used for executing a corresponding constraint checking method according to the corresponding constraint type and the change message type and reporting the obtained constraint checking result to the client;
the database is used for storing constraint relation data and is used by the constraint rule checker;
the memory is used for storing instructions executable by the processor, and the instructions are used for obtaining network element types and network element configuration types by analyzing network element configuration data after being executed by the processor, searching corresponding constraint check managers according to the network element types, and acquiring relevant constraint rule checker sets from the corresponding constraint check managers according to the network element configuration types.
Preferably, the constraint checking framework further comprises a constraint script repository and a script parser;
the constraint script warehouse is used for storing a rule definition script and a constraint error code script;
the script parser is used for parsing the rule definition script and the constraint error code script stored in the constraint script warehouse and used by the constraint checking manager;
the rule definition script is used for a user to self-define and set an upper limit value of specification constraint, whether to shield the check of a certain constraint rule checker and whether to start a reconstruction constraint function; the constraint error code script is used for defining a constraint check error code information template.
Generally, compared with the prior art, the technical scheme of the invention has the following beneficial effects: in the network element configuration constraint checking method and system provided by the invention, different network element types correspond to different constraint checking managers, and each constraint checking manager respectively registers a plurality of constraint rule checkers for different network element configuration types according to functional requirements; when a user executes change operation on certain network element configuration, the corresponding constraint check manager can be triggered to be searched according to the network element type, and then a constraint rule checker set is obtained from the corresponding constraint check manager according to the network element configuration type, each constraint rule checker in the set can execute constraint check according to the corresponding constraint type and change message type, and the result is reported to the client. The consistency, the validity and the correctness of the network element configuration data can be effectively ensured by the constraint checking method.
Drawings
Fig. 1 is a schematic structural diagram of a network element configuration constraint checking framework according to an embodiment of the present invention;
FIG. 2 is a flow diagram of a method for constraint checking framing provided by an embodiment of the present invention;
FIG. 3 is a diagram illustrating a design example of a ruledefine script according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating an example of an error code information script according to an embodiment of the present invention;
fig. 5 is a flowchart of a method for checking network element configuration constraints according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating that each network element executes a reconstruction constraint according to an embodiment of the present invention;
fig. 7 is a complete flowchart of checking constraint of network element configuration according to an embodiment of the present invention;
fig. 8 is a complete flowchart of a network element configuration reconstruction constraint according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
Example 1
In order to solve the technical problem that the consistency, the validity and the correctness of the network element configuration data are difficult to ensure in the traditional scheme, the invention provides a network element configuration constraint checking method which is used for carrying out constraint checking on various network element configurations. In order to better implement the constraint check on the network element configuration, the constraint check may be framed to form a constraint check frame as shown in fig. 1, and then the constraint check frame may be subsequently used to execute the constraint check method.
Referring to fig. 2, in the embodiment of the present invention, the process of constraint checking framing is specifically as follows:
There are many types of network element configurations, such as a loopback interface configuration, an ethernet interface configuration, a VPWS (Virtual Private line Service) configuration, an LSP (Label Switching Path) configuration, and so on. A network element configuration can correspond to a plurality of constraint rule inspectors, different constraint rule inspectors respectively inherit abstractions according to requirements, constraint inspection methods such as addition, deletion, modification, activation and deactivation can be realized, and each constraint rule inspector is provided with a unique constraint rule ID. Wherein:
1) the value range constraint is used for carrying out constraint check on the validity of the current network element configuration data, including whether the current network element configuration data is not empty, whether the current network element configuration data is in a value range, whether modification is allowed and the like; for example, the service name cannot be null, MPLS (Multi-Protocol Label Switching) enabling cannot be modified when L2VPN (Layer2 Virtual Private Network, i.e. two-Layer Virtual Private Network) service is carried over ethernet, and the like.
2) The uniqueness constraint in turn comprises a global uniqueness constraint and an intra-network element uniqueness constraint.
The global uniqueness constraint means that the configuration data is unique in the whole network equipment management system; for example, the IP addresses of loopback ports and ethernet ports cannot be repeated in the whole network device management system.
The uniqueness constraint in the network element means that the configuration data is unique in the whole network element; for example, the names of MA (Maintenance Association), MD (Maintenance Domain) cannot be repeated within the same network element, but are allowed to be repeated in different network elements.
And the constraint relation data corresponding to the uniqueness constraint is stored in a database for subsequent constraint check on the uniqueness of the network element configuration. The constraint relationship data corresponding to the unique constraint is stored in a database in a Key-Value format, and specifically may be as follows:
key is a constraint type, a constraint rule ID and a constraint field value;
value is a keyword of the network element configuration data;
the constraint field value and the keywords of the network element configuration data can be defined according to the functional requirements.
3) The primary foreign key constraints, in turn, include primary key constraints and foreign key constraints. The primary key constraint and the foreign key constraint are relative concepts, and indicate that one configuration data refers to another configuration data; for example, a DS (DiffServ, i.e., differentiated services) template may be configured with a DS domain, at this time, a primary key needs to be newly created for the DS domain, an external key needs to be created for the DS template, and the constraint relationship data is stored in the database for performing constraint check on the subsequent sequence of network management operations. For example, when a DS template data is configured with a DS domain data, if the user deletes the DS domain data, the network device management system pops up to indicate that the DS domain is referenced, and does not allow deletion.
In summary, the constraint relationship data corresponding to the primary foreign key constraint is also stored in the database, and is used for performing constraint check on the sequence of network management operations in the following. The constraint relation data corresponding to the main foreign Key constraint is stored in a database in a Key-Value format, and specifically may be as follows:
key is a constraint type, a constraint rule ID and a constraint field value;
value is a keyword of the network element configuration data;
the constraint field value and the keywords of the network element configuration data can be defined according to the functional requirements.
4) The specification constraint refers to a capability constraint for the network device that indicates whether a certain type of configuration data has reached an upper limit supported by the network device. When the configuration data is added or deleted, the total number of the current type of configuration is dynamically calculated, and the constraint relation data is stored in a database for subsequent specification constraint check. For example, a VPWS service of a certain PTN (Packet Transport Network) device cannot exceed 320, and when a user creates a VPWS service and reaches an upper limit, the Network device management system pops up a prompt.
In summary, the constraint relation data corresponding to the specification constraint is also stored in the database, and is used for performing constraint check on the network element configuration specification. The constraint relation data corresponding to the specification constraint is stored in a database in a Key-Value format, and specifically the following data are stored in the database:
key is a constraint type, a constraint rule ID and a constraint field value;
value is current number;
wherein, the constraint field value can be defined according to the function requirement.
1) the rule definition script is also called ruledefine script, that is, the rule definition is scripted. Specific functional features of the rule definition script include, but are not limited to, the following: 1. the user can self-define and set the upper limit value of the specification constraint; 2. setting a check whether to mask a certain constraint rule checker; 3. and setting the on-off state whether to start the reconstruction constraint function. Specifically, for a constraint rule checker of a specification constraint type, a user can customize an upper limit value of the specification constraint through the script; for all constraint rule checkers, a user can customize whether to shield the check of a certain constraint rule checker through the script; through the script, the user can also decide whether to start the reconstruction constraint function. Wherein, the concrete expression form of the rule definition script includes but is not limited to the form shown in fig. 3.
2) The constraint error code script is used for defining a constraint check error code information template, namely the constraint check error code information is scripted. Specific functional features of the constraint error code script include, but are not limited to, the following: 1. defining the type of the constraint error code; 2. defining a Chinese and English formatting template for restricting error code prompt information; 3. a parameter list is defined that will be entered as a parameter for the constrained error code information formatting template. The formatting template of the error code prompt message is defined through the script, so that the prompt message received by the interface is clearer and is convenient to expand. The specific expression form of the constraint error code script includes, but is not limited to, the form shown in fig. 4.
Based on the 4 constraint types defined in step 101 and the rule definition script and constraint error code script set in step 102, a constraint checking framework can be created, which is a separate module and supports plug-in loading. As shown in FIG. 1, the constraint checking framework includes a constraint checking interface, a constraint checking manager, a constraint rule checker, a database, a constraint script repository, and a script parser. The method comprises the following specific steps:
the constraint checking framework provides a unified constraint checking interface, i.e. the constraint checking interface. The constraint checking interface is connected with the client, and when a user performs change operations such as addition, deletion, modification, activation, deactivation and the like of the network element configuration at the client, the constraint checking interface can receive change messages of the network element configuration so as to trigger constraint checking.
The constraint checking manager may be configured to set one or more devices respectively corresponding to different network element types. For example, an OTN (Optical Transport Network) Network element, a PTN Network element, and an SDH (Synchronous Digital Hierarchy) Network element correspond to the OTN constraint check manager, the PTN constraint check manager, and the SDH constraint check manager, respectively.
Each constraint check manager can respectively register a plurality of different constraint rule checkers for different network element configuration types according to functional requirements through a corresponding constraint check manager registration interface, namely, one network element configuration can correspond to a plurality of constraint rule checkers. Each constraint rule checker has a unique constraint rule ID, corresponds to a constraint type, and supports 5 constraint checking methods of adding, deleting, modifying, activating and deactivating, namely, CheckAdd, CheckDel, CheckDeploy, CheckModify and CheckUnDeploy.
The constraint rule checker can execute a corresponding constraint checking method according to the corresponding constraint type (namely, value range constraint, uniqueness constraint, main foreign key constraint and specification constraint) and the change message type (namely, addition, deletion, modification, activation and deactivation), and report the obtained constraint checking result to the client.
The database is used for storing constraint relation data corresponding to the uniqueness constraint, the main foreign key constraint and the specification constraint, and can be called and used by the constraint rule checker.
The constraint script repository is used for storing set rule definition scripts (namely ruledefine scripts) and constraint error code scripts. The script analyzer can analyze the script stored in the constraint script warehouse, and the analyzed script can be used by the constraint checking manager.
Based on the constraint checking framework, when a user executes change operations such as addition, deletion, modification, activation, deactivation and the like of certain network element configuration at a client, a constraint rule checker set corresponding to the network element configuration and registered can be triggered to be searched, each constraint rule checker in the set executes a corresponding constraint checking method in sequence, and a constraint checking result is reported to the client to complete constraint checking. The specific constraint checking process may refer to embodiment 3, which is not described herein.
Example 2
Based on the constraint checking framework created in the above embodiment 1, the embodiment of the present invention further provides a system for checking network element configuration constraints, which can be used to execute a method for checking network element configuration constraints in the subsequent embodiment 3. The concrete structure is as follows:
the network element configuration constraint checking system comprises a constraint checking framework, a memory and a processor.
The constraint checking framework is an independent module as shown in fig. 1, supports plug-in loading, and mainly comprises a constraint checking interface, a constraint checking manager, a constraint rule checker, a database, a constraint script repository and a script parser. Wherein:
the constraint checking interface is used for receiving the change message of the network element configuration and further triggering constraint checking. With reference to fig. 1, when a user performs operations of adding, deleting, modifying, activating, and deactivating network element configuration at a client, the constraint checking interface may receive a change message of the network element configuration.
The constraint checking manager is provided with one or more devices which respectively correspond to different network element types; for example, when the network element types are an OTN network element, a PTN network element, and an SDH network element, the network element types respectively correspond to an OTN constraint check manager, a PTN constraint check manager, and an SDH constraint check manager. Each constraint check manager registers a plurality of different constraint rule checkers for different network element configuration types respectively according to functional requirements, and each constraint rule checker has a unique constraint rule ID.
And the constraint rule checker is used for executing a corresponding constraint checking method according to the corresponding constraint type and the change message type and reporting the obtained constraint checking result to the client.
The database is used for storing constraint relation data corresponding to the uniqueness constraint, the main foreign key constraint and the specification constraint, and can be called and used by the constraint rule checker.
The constraint script repository is used for storing rule definition scripts and constraint error code scripts.
The script parser is used for parsing the rule definition script and the constraint error code script stored in the constraint script warehouse and used by the constraint checking manager.
The rule definition script is used for a user to self-define and set an upper limit value of specification constraint, whether to shield the check of a certain constraint rule checker, whether to start a reconstruction constraint function and the like; the constraint error code script is used for defining a constraint check error code information template.
The memory is used for storing instructions executable by the processor, and the instructions are used for obtaining network element types and network element configuration types by analyzing network element configuration data after being executed by the processor, searching corresponding constraint check managers according to the network element types, and acquiring relevant constraint rule checker sets from the corresponding constraint check managers according to the network element configuration types, so that each constraint rule checker in the sets respectively executes a corresponding constraint check method, and reports a constraint check result to the client.
The processor is connected with the constraint checking interface of the constraint checking framework, and when a user performs addition, deletion, modification, activation and deactivation operations of certain network element configuration at a client, the constraint checking interface receives a change message of the network element configuration and triggers the processor to perform a series of analysis processing operations so as to obtain a constraint rule checker set related to the network element configuration.
Further, the processor and the memory may be connected by a bus or other means. The memory, which is a non-volatile computer-readable storage medium of the network element configuration constraint checking method, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The processor executes various functional applications and data processing of the network element configuration constraint checking system by executing non-volatile software programs, instructions and modules stored in the memory.
The memory may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Those of ordinary skill in the art will appreciate that all or part of the steps of the various methods of the embodiments may be implemented by associated hardware as instructed by a program, which may be stored on a computer-readable storage medium, which may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
In the system for checking network element configuration constraints provided in the embodiment of the present invention, different network element types correspond to different constraint checking managers, and each constraint checking manager registers a plurality of constraint rule checkers for different network element configuration types according to functional requirements; when a user executes change operation on a certain network element configuration, a constraint rule checker set corresponding to the network element configuration can be triggered and obtained, each constraint rule checker in the set executes constraint check, and the result is reported to a client. The consistency, the validity and the correctness of the network element configuration data can be effectively ensured by the constraint checking method; and the startup of the constraint rule checker, the upper limit value of the custom specification constraint and the error code formatting information are managed in a scripted manner, so that the maintenance is convenient and the expansion is flexible.
Example 3
Based on the system for checking network element configuration constraint provided in embodiment 2, an embodiment of the present invention further provides a method for checking network element configuration constraint, which specifically includes, as shown in fig. 5:
As can be seen from fig. 1 and embodiments 1 and 2, the network element configuration constraint checking system includes a plurality of constraint checking managers and a plurality of constraint rule checkers, where all constraint checking managers and all constraint rule checkers need to be loaded for subsequent use.
With reference to embodiments 1 and 2, it can be seen that the change message type mainly refers to addition, deletion, modification, activation, and deactivation, and the network element type mainly includes an OTN network element, a PTN network element, an SDH network element, and the like; the network element configuration types are divided according to device functions, such as loopback interface configuration, ethernet interface configuration, VPWS configuration, LSP configuration, and the like. When a user performs certain operations of adding, deleting, modifying, activating and deactivating network element configuration at a client, the constraint check interface receives a change message of the network element configuration, and the processor obtains a network element type and a network element configuration type by analyzing network element configuration data.
The processor searches corresponding constraint rule management according to the network element type; for example, when the network element type is an OTN network element, the OTN constraint check manager is correspondingly searched, when the network element type is a PTN network element, the PTN constraint check manager is correspondingly searched, and when the network element type is an SDH network element, the SDH constraint check manager is correspondingly searched.
And after the processor finds out the corresponding constraint rule management, the processor continues to acquire a relevant constraint rule checker set from the corresponding constraint check manager according to the network element configuration type.
And 204, each constraint rule checker in the constraint rule checker set performs corresponding constraint check according to the corresponding constraint type and the change message type, and reports the constraint check result to the client.
And sequentially taking out the constraint rule checker from the constraint rule checker set, and carrying out corresponding constraint check according to the constraint type and the change message type corresponding to the current constraint rule checker. Wherein:
1) and if the constraint type corresponding to the constraint rule checker is value domain constraint, directly executing a corresponding constraint checking method according to the change message type configured by the network element, and obtaining a corresponding constraint checking result. Specifically, if the constraint check has conflict, the constraint check error code information template is formatted by using the network element configuration data as a parameter, and the formatted error code information is saved as the constraint check result. The error code information contains details of specific reasons for restricting the checking error, so that prompt information received by an interface can be clearer, the efficiency of network management operation of a user is improved, the user experience is improved, and the problem reasons are conveniently checked.
2) If the constraint type corresponding to the constraint rule checker is a non-value-range constraint (namely, a uniqueness constraint, a main foreign Key constraint or a specification constraint), calculating constraint Key information according to network element configuration data, and searching corresponding constraint relation data from a database according to the constraint Key information; and then, executing a corresponding constraint checking method according to the change message type configured by the network element and the searched constraint relation data, and obtaining a corresponding constraint checking result.
Specially, if the constraint check has conflict, using the network element configuration data as a parameter to format a constraint check error code information template, and storing the formatted error code information as a constraint check result, wherein the error code information contains details of specific reasons of the constraint check error; and if the constraint check does not have conflict, updating the corresponding constraint relation data and storing the constraint relation data in the database.
As can be seen from the above, the value range constraint is different from the processing logic of the non-value range constraint, and the value range constraint only needs to check the content of the current network element configuration, while the non-value range constraint relates to the checking of the historical data and needs to perform logic processing by means of the constraint relation data stored in the database.
Furthermore, when a new configuration is introduced into the network device management system or the network element service model is updated, reconstruction constraint can be performed in an incremental constraint check mode, that is, current constraint relation data in the database is cleared, constraint check is performed on the network element configuration in the current system again, and new constraint relation data are generated and stored in the database; meanwhile, the network element configuration which violates the existing constraint checking rule in the constraint checking process can be used for generating a constraint conflict abstract for a user to view.
When the reconstruction constraint is performed, reconstruction constraints need to be sequentially performed on all network elements, and for each network element, the reconstruction process may refer to fig. 6, which is as follows:
Taking the current network element as an OTN network element as an example, the processor obtains each network element configuration item of the OTN network element from the corresponding network element configuration type set, and searches for a constraint rule checker corresponding to each network element configuration item. Because the constraint check is executed again, the constraint rule checker can execute the increased constraint check method for the corresponding network element configuration item according to the searched corresponding relation.
Considering that the value domain constraint is different from the processing logic of the non-value domain constraint, the value domain constraint only needs to check the content configured by the current network element, while the non-value domain constraint relates to the checking of the historical data and needs to perform the logic processing by virtue of the constraint relation data stored in the database, so that after the constraint check is performed again, the constraint relation data needs to be updated according to the constraint check result for the non-value domain constraint, and the value domain constraint does not need to be processed. And if constraint checking conflict exists in the constraint checking process, generating a constraint conflict abstract and storing the constraint conflict abstract in the database so as to facilitate subsequent viewing by a user.
In the method for checking constraint of network element configuration provided in the embodiment of the present invention, when a user performs a change operation on a certain network element configuration, a set of constraint rule checkers registered corresponding to the network element configuration may be triggered to be obtained, each constraint rule checker in the set performs constraint checking, and a result is reported to a client. The consistency, the validity and the correctness of the network element configuration data can be effectively ensured by the constraint checking method; the starting of the constraint rule checker, the upper limit value of the custom specification constraint and the error code formatting information are managed in a scripted mode, so that the maintenance is convenient, and the expansion is flexible; meanwhile, the characteristic of constraint can be rebuilt, so that the constraint check can be carried out in an incremental mode, and the engineering upgrade is more convenient.
Example 4
On the basis of the above embodiment 3, the embodiment of the present invention further describes in detail a complete flow of the network element configuration constraint checking method, and specifically includes the following steps, with reference to fig. 7:
The network element configuration constraint checking system comprises a plurality of constraint checking managers and a plurality of constraint rule checkers, equipment of different network element types corresponds to different constraint checking managers, each constraint checking manager respectively registers the plurality of constraint rule checkers for different network element configuration types according to functional requirements, and all the constraint checking managers and all the constraint rule checkers need to be loaded.
Step 402, receiving a change message configured by a network element, and determining a type of the change message. Wherein the change message type includes addition, deletion, modification, activation, deactivation and the like.
And step 404, searching corresponding constraint rule management according to the network element type. For example, when the network element type is an OTN network element, the OTN constraint check manager is correspondingly searched, and when the network element type is a PTN network element, the PTN constraint check manager is correspondingly searched.
At step 406, a constraint rule checker is fetched from the set of constraint rule checkers.
In step 411, the constraint checking results of all constraint rule checkers are returned to the client. And the whole constraint checking flow is executed.
In step 412, the constraint rule checker calculates constraint Key information according to the network element configuration data.
As can be seen from embodiment 1, the constraint Key information is constraint type + constraint rule ID + constraint field value. The constraint field values of the different constraint rule checkers may be defined according to functional requirements, e.g. the constraint field value of the loopback interface IP global uniqueness constraint is the IP address.
And step 413, the constraint rule checker searches corresponding constraint relation data from the database according to the constraint Key information.
In connection with embodiment 1, the storage format of the uniqueness constraint and the primary foreign key constraint in the database is as follows:
key is a constraint type, a constraint rule ID and a constraint field value;
value is a keyword of the network element configuration data;
the storage format of the specification constraint in the database is as follows:
key is a constraint type, a constraint rule ID and a constraint field value;
value is current number;
therefore, the corresponding constraint relation data can be found from the database by the constraint Key information.
And 414, executing a corresponding constraint checking method by the constraint rule checker according to the change message type configured by the network element and the searched constraint relation data, and obtaining a corresponding constraint checking result.
If the constraint check does not have conflict, the corresponding constraint relation data is updated and stored in the database, because the non-value range constraint relates to the check of the historical data and needs to be logically processed by the constraint relation data stored in the database.
And then jumps to step 410 until all constraint rule checkers in the set of constraint rule checkers have processed.
Example 5
On the basis of the foregoing embodiment 4, in the embodiment of the present invention, taking as an example that the MPLS enable of a single-disk ethernet configuration of a certain PTN device is modified from a client to be off, and the IP is set to be 10.26.2.89, that is, the network element type is a PTN network element, the network element configuration type is an ethernet configuration, and the change message type is modified, then the whole network element configuration constraint checking process is specifically as follows:
1) all constraint checking managers and constraint rule checkers are loaded.
2) The constraint checking interface receives a modification message of the ethernet configuration.
3) And analyzing the Ethernet port configuration data to obtain the PTN network element as the network element type, wherein the network element configuration type is Ethernet port configuration.
4) And finding the PTN constraint check manager according to the PTN network element type.
5) And acquiring all related constraint rule inspectors from the PTN constraint inspection manager according to the Ethernet configuration type. Assume that the PTN constraint check manager is found to register two constraint rule checkers for the ethernet configuration: the method comprises an Ethernet port configuration value domain constraint checker and an Ethernet port IP global unique constraint checker, wherein corresponding constraint types are value domain constraint and uniqueness constraint respectively.
6) And executing a modification constraint checking method of the Ethernet configuration value domain constraint checker, and if the L2VPN service is loaded on the current Ethernet in the constraint checking process, returning the existence of conflict by the constraint checking method, and generating error information that the current Ethernet loads the L2VPN service and the MPLS enabling is not allowed to be modified.
7) And executing the modification constraint checking method of the Ethernet port IP global unique constraint checker, calculating constraint Key information as 01100110.26.2.89 according to the Ethernet port configuration data, and searching whether associated constraint relation data exists in a database according to the constraint Key information. And if no conflict is found in the constraint checking process, updating constraint relation data and storing the constraint relation data in the database.
8) And after the two constraint rule checkers are processed, returning a final constraint check result that the current Ethernet port bears the L2VPN service but the MPLS enable is not allowed to be modified to the client. So far the whole constraint checking flow ends.
Example 6
On the basis of the above embodiment 3, the embodiment of the present invention further describes in detail a complete flow of network element configuration reconstruction constraints, and in combination with fig. 8, specifically includes the following steps:
And 505, clearing all constraint relation data corresponding to the network element from the database.
And 507, traversing the constraint rule checker registered by the network element in sequence, and executing a constraint checking method for changing the message type to increase the configuration on each network element configuration item by using the constraint rule checker.
In step 509, if a constraint checking conflict exists in the constraint checking process, a constraint conflict summary is generated and stored in the database for the user to view subsequently.
By the method provided by the embodiment of the invention, when new configuration is introduced into the network equipment management system or the network element service model is updated, reconstruction constraint can be performed in an incremental constraint check mode, so that the constraint check can be performed in an incremental mode, and the engineering upgrade is more convenient.
It will be understood by those skilled in the art that the foregoing is only a preferred embodiment of the present invention, and is not intended to limit the invention, and that any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A network element configuration constraint checking method is characterized by comprising the following steps:
loading a constraint checking manager and a constraint rule checker; the different network element types correspond to different constraint check managers, and each constraint check manager respectively registers a plurality of constraint rule checkers for different network element configuration types according to functional requirements;
after receiving the change message of the network element configuration, determining the type of the change message, and obtaining the type of the network element and the type of the network element configuration by analyzing the network element configuration data;
searching a corresponding constraint check manager according to the network element type, and acquiring a related constraint rule checker set from the corresponding constraint check manager according to the network element configuration type;
and each constraint rule checker in the constraint rule checker set carries out corresponding constraint check according to the corresponding constraint type and the change message type, and reports the constraint check result to the client.
2. The network element configuration constraint checking method of claim 1, wherein prior to said loading constraint check manager and constraint rule checker, said method further comprises:
defining different constraint types according to functional requirements and abstracting, wherein the constraint types comprise one or more of value range constraint, uniqueness constraint, main foreign key constraint and specification constraint; wherein:
the value range constraint is used for carrying out constraint check on the validity of the current network element configuration data;
constraint relation data corresponding to the uniqueness constraint are stored in a database and used for carrying out constraint check on the uniqueness of the network element configuration, and the corresponding constraint relation data are stored in a Key-Value format;
the constraint relation data corresponding to the main foreign Key constraint is stored in a database and used for carrying out constraint check on the sequence of network management operation, and the corresponding constraint relation data is stored in a Key-Value format;
the constraint relation data corresponding to the specification constraint is stored in a database and is used for carrying out constraint check on the network element configuration specification; and the corresponding constraint relation data is stored in a Key-Value format.
3. The network element configuration constraint checking method of claim 1, wherein prior to said loading constraint check manager and constraint rule checker, said method further comprises:
setting a rule definition script and a constraint error code script; the rule definition script is used for a user to self-define and set an upper limit value of specification constraint, whether to shield the check of a certain constraint rule checker and whether to start a reconstruction constraint function, and the constraint error code script is used for defining a constraint check error code information template.
4. The network element configuration constraint checking method of claim 2, wherein, for each constraint rule checker in the set of constraint rule checkers, the corresponding constraint check is performed according to the corresponding constraint type and the change message type, specifically:
if the constraint type corresponding to the constraint rule checker is value domain constraint, executing a corresponding constraint checking method according to the change message type configured by the network element, and obtaining a corresponding constraint checking result; wherein the change message type comprises one or more of addition, deletion, modification, activation and deactivation;
if the constraint type corresponding to the constraint rule checker is a non-value range constraint, calculating constraint Key information according to network element configuration data, and searching corresponding constraint relation data from a database according to the constraint Key information; and then, executing a corresponding constraint checking method according to the change message type configured by the network element and the searched constraint relation data, and obtaining a corresponding constraint checking result.
5. The network element configuration constraint checking method of claim 4, wherein for a value domain constraint, in the process of executing the corresponding constraint checking method according to the type of the change message of the network element configuration, the method further comprises:
if the constraint check has conflict, using the network element configuration data as a parameter to format a constraint check error code information template, and storing the formatted error code information as a constraint check result; wherein the constrained check error code information template is defined by a constrained error code script.
6. The network element configuration constraint checking method according to claim 4, wherein for non-value range constraints, in the process of executing the corresponding constraint checking method according to the change message type of the network element configuration and the found constraint relation data, the method further comprises:
if the constraint check has conflict, using the network element configuration data as a parameter to format a constraint check error code information template, and storing the formatted error code information as a constraint check result; if the constraint check does not have conflict, updating the corresponding constraint relation data and storing the constraint relation data in the database; wherein the constrained check error code information template is defined by a constrained error code script.
7. The method for checking network element configuration constraints according to claim 2, wherein when a new configuration is introduced into the network device management system or the network element service model is updated, the reconstruction constraints are specifically: and clearing the current constraint relation data in the database, executing constraint check on the current network element configuration again, generating new constraint relation data and storing the new constraint relation data in the database.
8. The method for checking constraint of network element configuration according to claim 7, wherein said clearing the current constraint relationship data in the database, performing a constraint check on the current network element configuration again, and generating new constraint relationship data to store in the database specifically comprises:
for each network element, searching a network element configuration type set of a registered constraint rule checker from a corresponding constraint check manager according to the network element type, and clearing constraint relation data corresponding to the network element from the database;
acquiring each network element configuration item of the network element according to the network element configuration type set, and sequentially executing a constraint checking method for changing the message type into increased configuration on each network element configuration item by using a constraint rule checker registered by the network element;
for the constraint rule checker with the constraint type of non-value range constraint, updating corresponding constraint relation data after executing a constraint checking method, and storing the new constraint relation data into the database;
if constraint checking conflict exists in the constraint checking process, generating a constraint conflict abstract and storing the constraint conflict abstract in the database.
9. A network element configuration constraint checking system comprising a constraint checking framework, a memory and a processor; wherein the constraint checking framework comprises a constraint checking interface, a constraint checking manager, a constraint rule checker and a database;
the constraint checking interface is used for receiving a change message of network element configuration and triggering constraint checking;
the constraint check managers are provided with one or more constraint check managers which respectively correspond to different network element types, and each constraint check manager respectively registers a plurality of different constraint rule checkers for different network element configuration types according to functional requirements;
the constraint rule checker is used for executing a corresponding constraint checking method according to the corresponding constraint type and the change message type and reporting the obtained constraint checking result to the client;
the database is used for storing constraint relation data and is used by the constraint rule checker;
the memory is used for storing instructions executable by the processor, and the instructions are used for obtaining network element types and network element configuration types by analyzing network element configuration data after being executed by the processor, searching corresponding constraint check managers according to the network element types, and acquiring relevant constraint rule checker sets from the corresponding constraint check managers according to the network element configuration types.
10. The network element configuration constraint checking system of claim 9, wherein the constraint checking framework further comprises a constraint script repository and a script parser;
the constraint script warehouse is used for storing a rule definition script and a constraint error code script;
the script parser is used for parsing the rule definition script and the constraint error code script stored in the constraint script warehouse and used by the constraint checking manager;
the rule definition script is used for a user to self-define and set an upper limit value of specification constraint, whether to shield the check of a certain constraint rule checker and whether to start a reconstruction constraint function; the constraint error code script is used for defining a constraint check error code information template.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110359999.9A CN113114493B (en) | 2021-04-02 | 2021-04-02 | Network element configuration constraint checking method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110359999.9A CN113114493B (en) | 2021-04-02 | 2021-04-02 | Network element configuration constraint checking method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113114493A true CN113114493A (en) | 2021-07-13 |
| CN113114493B CN113114493B (en) | 2023-03-24 |
Family
ID=76713758
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110359999.9A Active CN113114493B (en) | 2021-04-02 | 2021-04-02 | Network element configuration constraint checking method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113114493B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6393473B1 (en) * | 1998-12-18 | 2002-05-21 | Cisco Technology, Inc. | Representing and verifying network management policies using collective constraints |
| CN1960290A (en) * | 2006-09-18 | 2007-05-09 | 华为技术有限公司 | Reuse method and system of configuration rules in communication network |
| CN101013966A (en) * | 2007-02-09 | 2007-08-08 | 华为技术有限公司 | Configuration rule detecting method and device |
| US7477600B1 (en) * | 2002-02-12 | 2009-01-13 | Cisco Technology, Inc. | Method and apparatus for configuring network elements to support real time applications based on meta-templates |
| CN102088364A (en) * | 2009-12-04 | 2011-06-08 | 中兴通讯股份有限公司 | Method and device for managing network element parameters |
| CN102246550A (en) * | 2011-05-27 | 2011-11-16 | 华为技术有限公司 | Method for verifying business rule of NE configuration and verifying system |
| CN102412996A (en) * | 2011-11-24 | 2012-04-11 | 烽火通信科技股份有限公司 | Method for carrying out rapid checking and verification on service information based on XML (extensive makeup language) NE (network element) dynamic script information |
| CN105701129A (en) * | 2014-11-28 | 2016-06-22 | 中兴通讯股份有限公司 | Inspection method and device of legality of data configured by webmaster |
-
2021
- 2021-04-02 CN CN202110359999.9A patent/CN113114493B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6393473B1 (en) * | 1998-12-18 | 2002-05-21 | Cisco Technology, Inc. | Representing and verifying network management policies using collective constraints |
| US7477600B1 (en) * | 2002-02-12 | 2009-01-13 | Cisco Technology, Inc. | Method and apparatus for configuring network elements to support real time applications based on meta-templates |
| CN1960290A (en) * | 2006-09-18 | 2007-05-09 | 华为技术有限公司 | Reuse method and system of configuration rules in communication network |
| CN101013966A (en) * | 2007-02-09 | 2007-08-08 | 华为技术有限公司 | Configuration rule detecting method and device |
| CN102088364A (en) * | 2009-12-04 | 2011-06-08 | 中兴通讯股份有限公司 | Method and device for managing network element parameters |
| CN102246550A (en) * | 2011-05-27 | 2011-11-16 | 华为技术有限公司 | Method for verifying business rule of NE configuration and verifying system |
| WO2011144109A2 (en) * | 2011-05-27 | 2011-11-24 | 华为技术有限公司 | Method for checking service rules of network element configuration and checking system |
| CN102412996A (en) * | 2011-11-24 | 2012-04-11 | 烽火通信科技股份有限公司 | Method for carrying out rapid checking and verification on service information based on XML (extensive makeup language) NE (network element) dynamic script information |
| CN105701129A (en) * | 2014-11-28 | 2016-06-22 | 中兴通讯股份有限公司 | Inspection method and device of legality of data configured by webmaster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113114493B (en) | 2023-03-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9787558B2 (en) | Identifying configuration inconsistency in edge-based software defined networks (SDN) | |
| US9672137B1 (en) | Shadow test replay service | |
| US8914320B2 (en) | Graph generation method for graph-based search | |
| CN108829584B (en) | Service logic interface mock test method and system | |
| WO2017008578A1 (en) | Data check method and device in network function virtualization framework | |
| US9565243B2 (en) | System and method for managing event tracking | |
| US20110113019A1 (en) | Concurrent Database Access by Production and Prototype Applications | |
| US10083070B2 (en) | Log file reduction according to problem-space network topology | |
| US11768759B2 (en) | Method and system for automated testing of web service APIs | |
| US8224933B2 (en) | Method and apparatus for case-based service composition | |
| CN110955604A (en) | Information display method, device, server and storage medium | |
| JP2006025434A (en) | System and method for high capacity fault correlation | |
| CN113114493B (en) | Network element configuration constraint checking method and system | |
| US11301242B2 (en) | Feature-based reporting of software versions | |
| US9374437B2 (en) | Schema validation proxy | |
| WO2019001321A1 (en) | Yang model extension verification method, device, and computer readable storage medium | |
| CN112395339B (en) | Intersystem data admission verification method, device, computer equipment and storage medium | |
| Zichao et al. | Ethernet topology discovery for virtual local area networks with incomplete information | |
| US11036624B2 (en) | Self healing software utilizing regression test fingerprints | |
| Xu et al. | SDN state inconsistency verification in openstack | |
| CN116097226A (en) | Apparatus and method for injecting faults into a distributed system | |
| CN112714017B (en) | Configuration issuing method and device | |
| CN114528266B (en) | Method, system, device and storage medium for realizing database and cache consistency | |
| US11811804B1 (en) | System and method for detecting process anomalies in a distributed computation system utilizing containers | |
| US20240134967A1 (en) | Systems and methods for contextual alert enrichment in computing infrastructure and remediation thereof |
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 |