WO2009018787A1

WO2009018787A1 - A method and apparatus for verifying network configuration information

Info

Publication number: WO2009018787A1
Application number: PCT/CN2008/071947
Authority: WO
Inventors: Dan Li; Hao Long; Jianhua Gao; Jixiong Dong
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-09
Filing date: 2008-08-11
Publication date: 2009-02-12
Also published as: CN101364890A; CN101364890B

Abstract

A method and apparatus for verifying network configuration information, include that: a signaling message such as GMPLS (Generalized Multiprotocol Label Switching) is transmitted between network nodes, and the signaling message carries the network configuration information; The network nodes verify the network configuration information. By using the invention, the network configuration information can be verified effectively, the burden of network managers can be lightened and carrying out the network service and function normally can be ensured.

Description

Method and apparatus for verifying network configuration information

[I] Technical field

[2] The present invention relates to the field of network communications, and in particular, to a method and apparatus for verifying network configuration information.

[3] Background of the invention

[4] There are a large number of configuration information in the current carrier network, such as OAM (operation, administration and maintenance) configuration, protection configuration, address configuration, etc. These configuration information is necessary for the normal operation of the network. Many of these configuration information are manually configured through the network management, which is prone to some configuration errors.

[5] Usually, a certain function mechanism cannot detect its own configuration error. For example, the OAM configuration error cannot be located and detected by the OAM mechanism itself, because the OAM mechanism itself cannot operate normally after an OAM configuration error occurs. Therefore, verifying the correctness of the configuration information in the network is an urgent problem to be solved.

[6] A method for verifying the correctness of configuration information in the prior art is: In Ethernet, LLDP (L Ink Layer Discovery)

Protocol, link layer discovery protocol) discovers the configuration information around itself, and feeds the configuration information back to the network management system to verify the correctness of the configuration information through the network management.

[7] In the process of implementing the present invention, the inventors have found that the above-described prior art method of verifying the correctness of configuration information has at least the following disadvantages:

[8] 1, can only detect some mismatched configuration information of adjacent nodes;

[9] 2. The network management system needs to process a large amount of configuration information, which increases the burden on the network management.

[10] Summary of the invention

[I I] It is an object of the present invention to provide a method and apparatus for verifying network configuration information so that configuration information in the network can be effectively verified.

[12] The object of the present invention is achieved by the following technical solutions:

[13] A method of verifying network configuration information, including:

[14] transmitting a signaling message in the network, where the signaling message carries network configuration information; [15] verifying the network configuration of the node to be verified passing through the signaling message according to the network configuration information.

[16] A device for verifying network configuration information, the device is disposed in a network node, and the device specifically includes

[17] configuring a message transmission module, configured to transmit signaling messages between network nodes, and carry network configuration information in the signaling messages;

[18] The configuration information verification module is configured to obtain network configuration information carried in the signaling message, and verify the network configuration information.

[19] It can be seen from the technical solution provided by the present invention that the present invention transmits the signaling message between the network nodes, and carries the network configuration information in the signaling message, and the network node configures the network. The information is verified. Therefore, the configuration information on the network can be effectively verified, the burden of the network management can be reduced, and the network services and functions can be normally carried out.

[20] BRIEF DESCRIPTION OF THE DRAWINGS

1 and 2 are schematic diagrams showing an implementation principle of Embodiment 1 of the present invention;

[22] FIG. 3 is a schematic diagram showing an implementation principle of verifying OAM configuration information by using a PATH/RESV message in Embodiment 1 of the present invention;

4 is a schematic diagram of an implementation principle of Embodiment 2 according to the present invention;

[24] FIG. 5 illustrates the use of a NOTIFY message to verify OAM in Embodiment 2 of the present invention.

Schematic diagram of the implementation principle of the MEG configuration information;

6 and FIG. 7 are schematic diagrams showing an implementation principle of Embodiment 3 according to the present invention;

[26] FIG. 8 is a schematic diagram showing the implementation principle of verifying OAM configuration information by using a PATH/RESV message in Embodiment 3 of the present invention;

9 is a schematic structural diagram of Embodiment 1 of an apparatus for verifying network configuration information according to the present invention;

FIG. 10 is a schematic structural diagram of Embodiment 2 of an apparatus for verifying network configuration information according to the present invention.

[29] Mode for carrying out the invention

[30] Embodiments of the present invention provide a method and apparatus for verifying network configuration information.

[31] The embodiment of the present invention transmits a signaling message between network nodes, and carries network configuration information in the signaling message, where the network node verifies the network configuration information. The above signaling message can be GM PLS (Generalized Multiprotocol Label

Switching, General Multi-Protocol Label Switching) Messages, the following uses GMPLS messages as an example to illustrate embodiments of the present invention.

[32] GMPLS is made up of MPLS (Multiprotocol Label

Switching, Multi-Protocol Label Switching) evolved from the Internet Engineering Task Force (IETF), a general-purpose multi-protocol label switching technology for optical layer control. In order to achieve IP and WDM (wavelength division

Seamless integration of multiplex, wavelength division multiplexing, GMPLS extends MPLS labels so that tags can be used to tag legacy packets as well as TDM (Time Division)

Multiplexing, 吋 multiplexing) 吋 gap, wavelength, wavelength group, fiber, etc.

[33] The embodiment of the present invention utilizes the GMPLS protocol to verify network configuration information. In the embodiment of the present invention, the PATH (Reservation) message and the NOTIFY (Notification) message in the GMPLS protocol are extended, and the Attribution_Verify_Object attribute verification object is set in the PATH message, the RESV message or the NOTIFY message, and the Attribution_Query_Object (attribute) Query object) or Attribution_An swer_Object (property response object).

[34] The PATH message, RESV message or NOTIFY message of the above Attribution_Verify_Object, Attribution_Query_Object or Attribution_Answer_Object is transmitted between nodes, through the above Attribution_Verify_Object, Attribution_Query_Object or Attribution-

Answer_Object to carry the network information, the above Attribution_Verify_Object, Attribution. Query_Obj ect or Attribution—

Answer—Object can contain information such as attribute type, attribute name, and attribute value. By comparing the above Attr ibution_Verify_Object, Attribution_Query_Object or Attribution— Answer

- The configuration information in the Object is consistent with the correct configuration information to verify the network configuration information.

[35] The embodiment of the present invention provides three specific application embodiments of the method according to the embodiment of the present invention.

[36] In the first embodiment of the present invention, the PATH/RESV message is used for configuration verification. The schematic diagram of the implementation principle of Embodiment 1 is as shown in FIG. 1 and FIG. 2. When it is necessary to verify whether some public attributes are correctly configured, in PATH/RES The corresponding Attribution_Verify_Object is added to the V message, and the Attribution_Verify_Object contains the attribute name and the correct attribute configuration. The node is processing the above PATH/RESV message, according to Attributi Whether _{0n _Verify_Obj} _eC t attribute name included in the comparison with the corresponding configuration of the present node is correctly configured consistent

If they are inconsistent, a configuration error alarm is generated. The subsequent optional step may be to change the corresponding configuration to the correct configuration. If they are consistent, the configuration of this node is correct.

[37] The schematic diagram of the implementation principle of verifying OAM configuration information by using the PATH/RESV message in Embodiment 1 of the present invention is as shown in FIG. 3, and the specific processing procedure includes the following steps:

[38] Step 1. The source node A sends a PATH message, and the PATH message carries an Attribution_Verify_0 bject. The Attribution_Verify_Object may include the following content:

[39] (1)

Attribute.Code (Attribute Type Code), the attribute type information indicates that OAM attribute verification is to be performed;

(2)

OAM_Attribution_Value (OAM attribute value), including maintenance point attribute, MEG (Maintenance Entity Group) ID (ID), MEG

Information such as Level (Maintenance Entity Group Level), which includes MEP (MEG End Point Maintenance Entity Group Endpoint) and MIP (MEG Intermediate Point Maintenance Entity Group Intermediate Point).

[41] Step 2. The PATH message is based on the ERO (Explicit Route Object) carried in it.

Explicit routing object) hop-by-hop forwarding. After receiving the PATH message, the passing nodes (A, B, C, and D) obtain the Attribution_Verify_Object contained in the PATH message and save the correct OAM carried in the Attribution_Verify_Object. Configuration information.

[42] Step 3. After receiving the above PATH message, the sink node D returns the RESV message in the opposite direction because the sink node D is the last one of the ERO objects.

Step 4: Each node forwards hop by hop according to the ER0 carried in the RESV message, and the passed nodes (D, C, B, and A) trigger the verification process after receiving the RESV message, according to the previously saved correct OAM configuration information and itself. The OAM configuration is compared. After comparison, the following options are available:

If the configuration is incorrect, a configuration error alarm indicator is generated directly to the NMS; or

If the configuration is not correct, an error indication is carried return RESV message to the source node A (specific method may add a new Attributi ₀ n_Verify_R _eS ult_Obj _eC t attribute object, the verification result carried in this attribute object), by the source node A feedback to the network management or configuration signaling by the source node for reconfiguration. [46] Specifically, taking FIG. 3 as an example, if A and D are located at the MEG Level of 4, MEG

The ID is A_D_Connection_EVPL, and the PATH message sent by the source node A carries Attribution—

Verify.Object, which includes the correct configuration information, specifically:

[47] Attribution—Verify—Object:

[48] Attribute—Code =

OAM (that is, the type code assigned to the OAM attribute), indicating that the 0AM attribute is to be verified; [49] The maintenance point attribute = 1, that is, each node that passes through is configured as a maintenance point, and each point must be a MEP or Ml

P;

[50] MEG ID = "A_D_Connection_EVPL";

[51] MEG Level = 4o

[52] The PATH message is forwarded hop by hop along the nodes A, B, C, and D according to the explicit route. After processing the PATH message, the nodes A, B, C, and D record the Attribution_Verify_Object.

[53] For endpoint D, determine the authentication required for the 0AM configuration based on the Attribution_Verify_Object in the previously stored PATH message. According to the ER0 object, it is judged that the node is the connected endpoint, and the verification check OA M attribute 吋, according to the Attribution_Verify_Object value, each node on the connection is required to be a maintenance point. If the local node is the connected endpoint, check whether the local node is configured as a MEP, and the MEG level configured for the MEP is 4, and the configured MEG ID is "A_D_Connection_EVPL".

[54] If the configuration of the configuration is incorrect, the endpoint D generates alarm information to the NMS; or, if the configuration is correct, the information is carried in the Attribution_Verify_Result_Object attribute object. Specifically, a sub-object may be added to the Attribution_Verify_Result_Object, including the IP address of the node D on the control plane and the configuration verification result information.

[55] After the above endpoint D completes the above processing, according to the ER0 object or the RSVP_H0P object, the next node, node C, is passed the RESV message.

[56] After receiving the RESV message sent by the node D, the node C determines that the OAM configuration needs to be verified according to the Attribution_Verify_Object in the previously stored PATH message.

[57] The above node C verifies that the 0AM attribute is checked, and according to the Attribution_Verify_Object value, each node on the connection is required to be a maintenance point. If the local node is the intermediate point of the connection, check whether the local node is configured as a MIP, and the MEG level of the MIP configuration is 4. [58] If the above node C detects a configuration error, it generates an alarm message to the network management; or, the configuration information is carried in the Attribution_Verify_Result_Object attribute object. Specifically, a sub-object may be added to the Attri bution_Verify_Result_Object, including the IP address of the node C on the control plane and the configuration verification result information.

[59] After the above node C completes the above processing, according to the ERO object or the RSVP_HOP object, the next node, that is, the node B, transmits the RESV message.

[60] Node B is handled in a similar way to Node C.

[61] After receiving the RESV message, Node A determines that the OAM configuration needs to be verified according to the Attribution_Verif y.Object in the previously stored PATH message.

[62] The above node A verification checks the OAM attribute 吋, and according to the Attribution_Verify_Object value, each node on the connection is required to be a maintenance point. If the local node is the connected endpoint, check whether the local node is configured as a MEP, and the MEG level configured for the MEP is 4, and the configured MEG is configured.

The ID is "A_D_Connection_EVPL,,.

[63] If the above node A detects a configuration error, it generates an alarm message to the network management; or, if the configuration is correct, the information is carried in the Attribution_Verify_Result_Object attribute object. Specifically, a sub-object may be added to the Attribution_Verify_Result_Object, including the IP address of the node D on the control plane and the configuration verification result information.

[64] When the above node A completes the above processing, according to the ERO object, since this node is the final node. in case

The RESV contains the Attribution_Verify_Result_Object, and the verification result carried in it is fed back to the network management.

In the first embodiment of the present invention, configuration verification may be performed when the PATH message is received. In FIG. 3, the source node A initiates a configuration verification message, and carries the Attribution_Verify in the PATH message. Object (same as in embodiment 1), which includes the correct 0AM configuration information. The PATH message is forwarded hop by hop according to the E R0 object. After the received node (A, B, C, D) receives the PATH message, it performs the verification operation (same as in the first embodiment). If the configuration error is found, the node directly Report to the network management.

The embodiment 2 of the present invention uses the NOTIFY message to verify the configuration information of a certain node. The schematic diagram of the implementation principle of the embodiment 2 of the present invention is shown in FIG. 4 . When it is necessary to verify whether a node attribute is configured correctly, add the corresponding Attribution_Verify_Object in the NOT TIFY message, the Attribution_Verify_Object Contains the property name and the correct property configuration. In the above-described processing node NOTIFY message inch, according to the attribute name Attributio n_Verify_Obj _eC t included in the comparison itself is consistent with the corresponding configuration configured correctly, and if not, an alarm is generated configuration error, the appropriate follow-up can be configured to the correct configuration. If they are consistent, the node is configured correctly.

[67] In the second embodiment of the present invention, the NOTIFY message is used to verify 0AM.

The schematic diagram of the implementation principle of the MEG configuration information is shown in Figure 5. The specific processing process includes the following steps:

[68] Step 1. The source node A sends a NOTIFY message, and the NOTIFY message carries an Attribution_Veri fy_Object, and the Attribution_Verify_Object includes the following contents:

[69] (1) Attribute type, the attribute type information indicates that OAM attribute verification is to be performed;

[70] (2) OAM_Attribution_Value (OAM attribute value), including MEG Level, MEG

IDs PEER MEP ID List (Public Maintenance Entity Endpoint Identification List) and other information.

[71] For a specific example, refer to Embodiment 1.

[72] Step 2. After receiving the NOTIFY message, the sink node D obtains the Attribution_Verify_Object included in the above NOTIFY message. The OAM configuration verification is performed according to the OAM_Attr ibution_Value carried in the Attribution_Verify_Object, and it is checked whether the MEG Levels MEG ID and the PEER MEP ID are configured on the host node D.

List and other information. If yes, it is determined that the corresponding configuration of the host node D is correct, or that the configuration is correct in the ACK message replied to the source node A; otherwise, the corresponding configuration error of the node D of the host node is determined, and a configuration error alarm is generated or A configuration error is indicated in the ACK (ACKnowledgment Acknowledgement) message replied to the source node A. The corresponding configuration of the host node D can be changed to the correct configuration.

[73] Step 3: After receiving the ACK message, the source node A generates an indication information, such as a correct indication or a configuration error indication, if the information is correct according to the configuration in the ACK message.

[74] The third embodiment of the present invention uses the PATH/RESV message to perform configuration verification. The schematic diagram of the implementation principle of the third embodiment is as shown in FIG. 6 and FIG. 7. When it is required to verify that some OAM attributes are correctly configured, in the PATH message. Add the corresponding Attribution_Query_Object, the Attribution- Query

—Object contains the name of the property that needs to be queried. In the above-described processing node inch PATH message based on the attribute name included in Attributio n_Query_Obj _eC t need to query, add an attribute value corresponding to the RESV message The RESV message is returned to the initiating node of the PATH message, and the initiating node of the PATH message compares the collected attribute values of other nodes with the pre-configured correct attribute values to determine whether the configuration of the other nodes is correct.

[75] The schematic diagram of the implementation principle of verifying the OAM configuration information by using the PATH/RESV message in Embodiment 3 is as shown in FIG. 8. The specific processing procedure includes the following steps:

[76] Step 1. The source node A sends a PATH message, and the PATH message carries Attribution_Query.

_Object, the Attribution-Query-Object contains the following:

[77] (1)

Attribute type, this attribute type information indicates that OAM attribute verification is to be performed. This attribute type information can be represented by the OAM_Configuration_Query sub-object.

[78] (2)

The name of the attribute to be verified. The attribute name to be verified can be specified by the above OAM_Configurati ₀ n_Qu _er y sub-object. Of course, the domain may not be included, which means that all OAM configurations related to the current LSP (Label Switched Path) are returned.

[79] Step 2: The PATH message is forwarded hop by hop according to the explicit routing object ERO carried in the PATH message. After receiving the PATH message, the passing nodes (A, B, C, and D) obtain the Attribution contained in the PATH message. Query

.Object, and save the corresponding query request information. In the third embodiment of the present invention, it is a request for querying the OAM attribute.

[80] Step 3. After receiving the above PATH message, the sink node D returns the RESV message in the opposite direction because it is the last one in the ERO object.

[81] Step 4: Each node forwards the hop by hop according to the explicit routing object ERO carried by the RESV message, and the passed nodes (D, C, B, and A) trigger the query process after receiving the RESV message, according to the previous The saved query request information checks itself with the LSP to which the PATH belongs (by the LSP in the Session_Attributi on in the PATH message)

The ID indicates the attribute configuration and adds the query result to the RESV message. Specifically, it can be in RES

Add a force in the V message Attribution— Answer—Object, through the Attribution— Answer

The .Object contains the OAM_Attribution_Value sub-object to carry the queryed configuration property information and section. Point ID.

[82] The final node A of the RESV obtains the OAM configuration of all the nodes on the LSP, and compares with the correct configuration. If an incorrect configuration is found, the alarm information is generated to the network management system, or a new configuration signaling is directly initiated. Reconfigure the OAM attribute of the node on the LSP.

Specifically, for the present embodiment, the examples described in FIGS. 6 and 7 are used.

[84] The Attribution_Query_Object carried in the PATH message initiated by node A can contain:

[85] Attribute type code Attribution_Type = OAM (ie the corresponding OAM attribute type code).

[86] After processing the PATH message, nodes A, B, C, and D record the Attribution_Query_Object;

[87] After receiving the above PATH message, node D returns a RESV message to node A.

[88] The node D queries the local OAM configuration according to the previously stored OAM query request. When it finds that it is the MEP point of the LSP to be queried, the MEG level, the MEP ID, the Peer MEP ID, and the CC Interval configured on the MEP are configured. The configuration information and the node D are encapsulated into an OAM_Attribution_Value sub-object along with the IP address of the control plane, and the OAM_Attribution_Valu e sub-object is included in the Attribution of the RES V message.

After _Object, the RESV message is forwarded to node C.

[89] After receiving the RESV message, the node C queries the OAM configuration of the local node according to the previously stored OAM query request. When it finds that it is the MIP point of the LSP being queried, the MEG is configured on the MIP.

After Level and configuration information such as the IP address of the node C encapsulated together into a control plane OAM_Attributi _0n _ Value sub-object, the child object is contained in OAM_Attribution_Value Attribution _ Answer _Object RES V message, forwards the RESV message to node B.

[90] Node B is handled similarly to Node C.

[91] Node A is treated similarly to Node D, but since Node A is the final node of the RESV message. Node A will also collect OAM configuration information (by Attribution— Answer

a series of OAM_Attribution_Value sub-objects carried by _Object) Compare with the correct configuration information

Or send the collected OAM configuration information to the configuration server for comparison. If an inconsistency is found, alert the network administrator or directly initiate a new configuration command to correct the misconfiguration.

[92] It is worth noting that the OAM configuration verification method mentioned in the above several embodiments is also applicable to Ethernet C. FM (Connectivity Fault)

Configuration verification for Management, Connection Fault Management), OAM and CFM are different names for similar functions in different standards organizations. When applied to CFM configuration checksum, MEG ID corresponds to MD

Name (Maintenance Domain Name) with A name (Maintenance

Association Name, maintenance group name), MEG level corresponds to MD Level (Maintenance

Domain

Level, maintenance domain level). Further correspondences are not described here, and those skilled in the art will be more clear about this.

The device for verifying network configuration information according to the embodiment of the present invention is disposed in a network node. The schematic structural diagram of Embodiment 1 of the device is as shown in FIG. 9, and includes the following modules:

[94] a configuration information receiving module, configured to receive a signaling message carrying an attribute name and a correct attribute configuration corresponding to the attribute name, where the signaling message includes a GMPLS message, and the like;

[95] a configuration information verification module, configured to acquire configuration information corresponding to the attribute name on the network node, compare the configuration information with the correct configuration information, and if the comparison result is consistent, determine the The configuration information corresponding to the attribute name on the network node is correct; otherwise, the configuration information corresponding to the attribute name on the network node is determined to be incorrect.

[96] A schematic structural diagram of Embodiment 2 of an apparatus for verifying network configuration information according to an embodiment of the present invention is shown in FIG. 10, and includes the following modules:

[97] a configuration information sending module, configured to construct a signaling message carrying an attribute name and a correct attribute configuration corresponding to the attribute name, and sending the signaling message;

[98] a configuration information receiving module, configured to receive a signaling message carrying configuration information corresponding to the attribute name on another network node and identification information of other network nodes;

[99] a configuration information verification module, configured to compare configuration information corresponding to the attribute name on the other network node with correct configuration information according to the identifier information of the other network node, and if the comparison result is consistent, And determining that the configuration information corresponding to the attribute name on the other network node is correct; otherwise, determining that the configuration information corresponding to the attribute name on the other network node is incorrect.

[100] In summary, the embodiment of the present invention can verify the correctness of various configuration attributes of nodes in the network, so as to ensure that the service or management function can operate normally in the network. This check is especially suitable for a connection The configuration verification of the common attributes of the nodes on the node, of course, also applies to the configuration attribute verification of a series or a single node.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary hardware platform, and of course, all can be implemented by hardware, but in many cases, the former It is a better implementation. Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, or the like. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

The above description is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any change that can be easily conceived by those skilled in the art within the technical scope disclosed by the present invention is not limited thereto. Or, the replacement should be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Claim

[1] A method for verifying network configuration information, comprising:

The signaling message is transmitted in the network, and the network message configuration information is carried in the signaling message; and the network configuration of the node to be verified passing through the signaling message is verified according to the network configuration information.

[2] The method according to claim 1, wherein the signaling message comprises a general multi-protocol label switching GMPLS message.

[3] The method according to claim 1, wherein the node to be verified passing through the signaling message is specifically: flowing through the same connection in the process of transmitting the signaling message The node to be verified.

[4] The method according to claim 2, wherein the method specifically includes:

The source node sends a path PAT H message carrying the attribute name and the correct attribute configuration corresponding to the attribute name to the sink node, and the sink node returns the attribute name and the attribute to the source node through the intermediate node. a reserved RESV message corresponding to the correct attribute configuration; the to-be-verified node flowing through the reserved RESV message obtains the configuration information corresponding to the attribute name on the self, and the configuration information is correct The configuration information is compared. If the comparison result is consistent, it is determined that the configuration information corresponding to the attribute name on the self is correct; otherwise, the configuration information corresponding to the attribute name on the self is determined to be incorrect.

[5] The method according to claim 2, wherein the method specifically includes:

The source node sends a notification NOTI FY message carrying the attribute name and the correct attribute configuration corresponding to the attribute name;

After receiving the NOTIFY message, the other node obtains the configuration information corresponding to the attribute name on the self, and compares the configuration information with the correct configuration information. If the comparison result is consistent, determining that the other node is The configuration information corresponding to the attribute name is correct; otherwise, it is determined that the configuration information corresponding to the attribute name on the other node is incorrect.

[6] The method according to claim 2, wherein the method specifically includes:

The source node sends a PATH message carrying the attribute name to the sink node, and the sink node returns an RESV message carrying the attribute name to the source node through the intermediate node; The to-be-verified node that flows through the RESV message obtains configuration information corresponding to the attribute name on the RESV message, adds the configuration information and its own identification information to the RESV message, and sends the RESV message to The source node;

After receiving the RESV message, the source end node compares the configuration information corresponding to the attribute name on the node to be verified with the correct configuration information according to the identifier information of the node to be verified, if the comparison result is If the configuration information is correct, the configuration information corresponding to the attribute name on the node to be verified is determined to be correct; otherwise, the configuration information corresponding to the attribute name on the node to be verified is determined to be incorrect.

[7] The method according to claim 2, wherein the method further comprises:

The source node sends a PATH message carrying the attribute name to the sink node, and the sink node returns an RESV message carrying the attribute name to the source node through the intermediate node; the RESV message flows through the process. The to-be-verified node obtains the configuration information corresponding to the attribute name on the self, and adds the configuration information and its own identification information to the RESV message, and sends the RESV message to the source end node;

After receiving the RESV message, the source end node sends the RESV message to the configuration server, where the configuration server corresponds to the attribute name on the node to be verified according to the identifier information of the node to be verified. The configuration information is compared with the correct configuration information. If the comparison result is consistent, determining that the configuration information corresponding to the attribute name on the node to be verified is correct; otherwise, determining the attribute name on the node to be verified. The corresponding configuration information is incorrect.

[8] The method according to claim 2, wherein the method specifically includes:

The source node sends a path PAT H message carrying the attribute name and the correct attribute configuration corresponding to the attribute name;

The to-be-verified node that flows through the PATH message obtains the configuration information corresponding to the attribute name on the PATH message, and compares the configuration information with the correct configuration information. If the comparison result is consistent, it is determined that the node is determined to be the same. The configuration information corresponding to the attribute name is correct; otherwise, the configuration information corresponding to the attribute name on the self is determined to be incorrect.

[9] The method according to any one of claims 1 to 7, wherein the configuration information comprises

: Run, manage, and maintain OAM configuration information.

[10] The method according to claim 9, wherein the OAM configuration information comprises: at least one of a maintenance point attribute, a maintenance entity group MEG identifier, and an MEG level.

[11] The method according to claim 4 or 5 or 8, wherein the method further comprises:

After determining that the configuration information corresponding to the attribute name on the node is incorrect, the node reports the configuration error information to the network management.

Or,

After determining that the configuration information corresponding to the attribute name on the node is incorrect, the node sends the configuration error information to the source node by using the signaling, and the source node sends the configuration information to the network management, or the source. The node generates configuration signaling to reconfigure the node.

[12] A device for verifying network configuration information, wherein the device is disposed in a network node, and the device specifically includes:

Configuring a message transmission module, configured to transmit a signaling message between the network nodes, where the signaling message carries network configuration information;

The configuration information verification module is configured to obtain network configuration information carried in the signaling message, and verify the network configuration information.

[13] The apparatus for verifying network configuration information according to claim 12, wherein:

The configuration message transmission module includes:

a configuration information receiving module, configured to receive a signaling message carrying an attribute name and a correct attribute configuration corresponding to the attribute name;

The configuration information verification module includes:

a first configuration information verification module, configured to acquire configuration information corresponding to the attribute name on the network node, compare the configuration information with the correct configuration information, and if the comparison result is consistent, determine the network The configuration information corresponding to the attribute name on the node is correct; otherwise, determining that the configuration information corresponding to the attribute name on the network node is incorrect.

[14] The apparatus for verifying network configuration information according to claim 12, wherein:

The configuration message transmission module includes:

a configuration information sending module, configured to construct a signaling message carrying an attribute name and a correct attribute configuration corresponding to the attribute name, and sending the signaling message; a configuration information receiving module, configured to receive a signaling message carrying configuration information corresponding to the attribute name on another network node and identification information of other network nodes;

The configuration information verification module includes:

a second configuration information verification module, configured to compare configuration information corresponding to the attribute name on the other network node with correct configuration information according to the identifier information of the other network node, and if the comparison result is consistent, Determining that the configuration information corresponding to the attribute name on the other network node is correct; otherwise, determining that the configuration information corresponding to the attribute name on the other network node is incorrect.

A computer readable storage medium comprising computer program code, the computer program code being embodied by a computer processor, wherein triggering the computer processor to perform the step comprises transmitting a signaling message in a network, the signaling The message carries network configuration information. According to the network configuration information, the network configuration of the node to be verified passing through the signaling message is verified.