Network fault locating method, network device and storage medium

Abstract

The embodiment of the application provides a network fault positioning method, network equipment and a storage medium, the method comprises the following steps: configuring a link layer discovery protocol in an IP network element and an optical network element, characterizing an adjacency relationship between devices by a simple graph, and constructing a simple graph adjacency matrix of cross-layer association; defining a fault range and a fault device based on an alarm of the simple graph adjacency matrix of cross-layer association, and obtaining association information; and determining a fault position based on the association information. Through the method, not only can the effective interaction of mutual network information and state information between an IP network layer and an optical network layer control plane which lack a cooperation mechanism due to independent operation be solved, but also the positioning problem of an alarm storm of the IP network layer caused by an optical network layer fault can be effectively solved.

Description

Technical Field

[0001] This application relates to the field of network fault location technology, and in particular to a network fault location method, network device and storage medium. Background Technology

[0002] In existing technologies, network diagnostics primarily relies on passively monitoring network devices to capture network fault information. The fault management system receives device alarm CDRs (Call Records) transmitted from network devices via northbound interfaces using network layer protocols such as SNMP. Based on pre-defined rules, the CDRs are parsed, and alarms are standardized and output according to key fields, transforming them into real-time network device alarms for the system. However, existing methods have the following problems: 1) The IP network layer is carried on top of the optical network layer. Network faults, besides being caused by hardware issues, may also be due to problems in the optical network layer; and when the optical network layer experiences a fault, it may manifest as multiple faults in the IP network layer. The IP network layer and optical network layer control planes operate independently and lack a coordination mechanism, preventing effective exchange of network and status information, let alone topology and resource information. 2) In large networks, the end-to-end transmission of IP traffic involves numerous specialties and resources. Furthermore, alarm information is generated after the original data transmitted by the device is standardized, without deduplication or correlation, which leads to a large number of alarms being triggered by a single fault. When a large number of equipment failures occur, it increases the difficulty for maintenance personnel to identify useful information and reduces the efficiency of fault handling and maintenance. Summary of the Invention

[0003] This application provides a network fault location method, network device, and storage medium. This method can at least solve the problem that the IP network layer and the optical network layer control plane cannot effectively exchange network information and status information, let alone communicate topology and resource information, because they operate independently and lack a coordination mechanism.

[0004] In a first aspect, embodiments of this application provide a network fault location method. The method includes: configuring a link layer discovery protocol on IP network elements and optical network elements to represent the adjacency relationships between devices using a simple graph, and constructing a cross-layer associated simple graph adjacency matrix; defining the fault range and faulty devices based on alarms from the cross-layer associated simple graph adjacency matrix, and obtaining association information; and determining the fault location based on the association information. This method not only solves the problem of the IP network layer and optical network layer control planes being unable to effectively exchange network information and status information due to their independent operation and lack of coordination mechanisms, but also effectively solves the problem of locating alarm storms in the IP network layer caused by optical network layer faults.

[0005] Furthermore, the simple graph adjacency matrix is ​​symmetrically distributed with the diagonal as the axis.

[0006] Furthermore, the step of configuring a link layer discovery protocol on IP network elements and optical network elements to represent the adjacency relationships between devices using a simple graph and constructing a cross-layer associated simple graph adjacency matrix includes: configuring a link layer discovery protocol on the IP network elements and the optical network elements; collecting management information from the joint network element side database through a simple network management protocol to obtain device adjacency information between joint network elements; and constructing a two-dimensional array to store the adjacency relationships of vertex elements based on the vertex set of network element devices in the joint network, and determining that the simple graph adjacency matrix construction is complete when the elements of the two-dimensional array are set to a set value.

[0007] Furthermore, the alarm based on the cross-layer associative simple graph adjacency matrix, which defines the fault scope and faulty devices and obtains association information, includes: dividing standardized network management alarms into device-level alarms and link-level alarms; performing alarm deduplication and key alarm extraction based on local devices, peer devices, and interconnecting links; mapping the cleaned alarms to the cross-layer associative simple graph adjacency matrix, with device alarms mapped to row elements of the associative simple graph adjacency matrix and link alarms mapped to individual elements of the associative simple graph adjacency matrix; setting simple graph adjacency matrix elements with the alarm association relationship to a first set value, and setting simple graph adjacency matrix elements without the association relationship to a second set value, thereby constructing a cross-layer associative alarm adjacency matrix; and based on the cross-layer associative alarm adjacency matrix, defining the fault scope and faulty devices through a set algorithm and obtaining association information.

[0008] Furthermore, the association information includes: after defining the fault range and faulty devices through the set algorithm, the association information of the relevant vertex devices is extracted from the adjacency matrix of the cross-layer association simple graph for each fault.

[0009] Furthermore, determining the fault location based on the associated information includes: locating the fault based on the associated information, combined with the interface identifiers stored in the Joint Network Element Management Information Database collected by the Simple Network Management Protocol, the asset management system board information, and the important alarm information of the equipment itself.

[0010] Secondly, embodiments of this application also provide an electronic device, the device comprising: a processor and a memory, the memory being used to store at least one instruction, the instruction being loaded and executed by the processor to implement the network fault location method as provided in the first aspect.

[0011] Thirdly, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the network fault location method as provided in the first aspect.

[0012] Fourthly, embodiments of this application also provide a computer program product, including a computer program or instructions, characterized in that, when the computer program or instructions are executed by a processor, they implement the network fault location method provided in the first aspect.

[0013] Through the above technical solutions, the construction of a cross-layer association simple graph adjacency matrix for optical network collaboration can effectively characterize the connection relationship between IP network devices and optical network devices. Based on this, a cross-layer topology can be constructed to intuitively show the carrying relationship between optical network layer and IP network layer devices. The mapping of optical network layer alarms and IP network layer alarms to the cross-layer association simple graph adjacency matrix can effectively solve the problems of alarm storms and the inability to associate cross-professional alarms. The cross-layer association simple graph adjacency matrix network fault location method realizes the association and collaboration between IP network and optical network layer, improving the accuracy and real-time performance of fault location. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 The diagram illustrates cross-layer routing via manual negotiation and cross-layer routing based on the ASON architecture in related technologies.

[0016] Figure 2 This is a schematic diagram of a cross-layer association simple graph adjacency matrix fault location system provided in one embodiment of this application;

[0017] Figure 3 This is a schematic flowchart of a network fault location method provided in one embodiment of this application;

[0018] Figure 4 This is a schematic diagram of a cross-layer association simple graph adjacency matrix fault location system provided in one embodiment of this application;

[0019] Figure 5 This is a schematic diagram illustrating the construction of a cross-layer association simple graph adjacency matrix and an alarm association adjacency matrix, provided in one embodiment of this application. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] The IP network layer runs on top of the optical network layer, and the IP layer needs to request resources and connections from the optical network layer. The relationship between IP data streams and optical network layer resources can be viewed as an end-to-end IP stream service running on an end-to-end transmission channel of the optical network layer. Currently, the mainstream management approach is to manage the IP network layer and the optical network layer separately.

[0022] Figure 1 This diagram illustrates cross-layer routing using manual negotiation and cross-layer routing based on the ASON architecture in related technologies. (Refer to...) Figure 1 As shown, some operators currently primarily use ODUk (Optical Data Unit) as the transmission channel for the optical network layer, manually negotiating cross-layer resource and traffic mapping. IP network maintenance personnel communicate with optical network layer maintenance personnel to construct optical network layer channels based on IP network layer routing requirements. The network layer IP flow is encapsulated into ODUk at the source node of the optical network layer, and the ODUk is further multiplexed into OCh (Optical Channel). Depending on the functions supported by the optical network node, OCh is further multiplexed into OMS (Optical Multiplex Section) and transmitted via optical fiber to the next optical network layer node. After the optical network signal reaches the optical network layer destination node, it is demultiplexed step-by-step to restore it to ODUk, and then restored to IP flow via the tributary board.

[0023] Reference Figure 1As shown, another group of operators uses ASON based on GMPLS as the intelligent architecture in their optical networks, employing the GMPLS protocol for intelligent control of the optical network layer. When IP network layer services need to be transmitted through the optical network layer channel, an end-to-end connection request is sent to the GMPLS control plane via the UNI (User Network Interface). Connections across control domains are established through the E-NNI (Extro Network Node Interface). In application, the ASON network uses the GMPLS protocol in the control plane to automate signaling and routing calculations in the transport network, thereby establishing and tearing down calls / connections. However, as an extension of the IP network protocol MPLS at the optical network layer, GMPLS can only manage the optical network layer, necessitating the existence of two independently operating control logics.

[0024] In current network diagnostics, the primary approach is passive monitoring of network devices (monitoring their own operational metrics) to capture fault information. The fault management system receives device alarm CDRs (Call Records) transmitted via northbound interfaces through network layer protocols such as SNMP. It then parses these CDRs based on pre-defined rules and standardizes the output according to key fields, transforming them into real-time network device alarms. Batch annotation and line-by-line presentation are the main functions of the fault management system. Significant network faults can cause the alarm monitoring window to display a flood of alarms. Fault localization currently relies solely on manually exporting and analyzing alarms.

[0025] Based on the above-mentioned implementation scheme proposed in the prior art, the following disadvantages exist:

[0026] 1. The problem of coordination between the IP network layer and the optical network layer

[0027] The IP network layer runs on top of the optical network layer. Network failures, besides being caused by hardware issues, can also be due to problems in the optical network layer. Conversely, when the optical network layer experiences a failure, it may manifest as multiple failures in the IP network layer. Regardless of whether manual negotiation or an ASON-based architecture is used, the IP network layer and the optical network layer control planes operate independently and lack a coordination mechanism, preventing effective exchange of network and status information, let alone topology and resource information.

[0028] 2. Alarm storms prevent effective fault location.

[0029] In large networks, the end-to-end transmission of IP traffic involves numerous specialties and resources. Furthermore, alarm information is generated after the original data transmitted by the devices has been standardized, without deduplication or correlation. This can lead to a single fault triggering a large number of alarms. When a large number of devices fail, it further increases the difficulty for maintenance personnel to identify useful information, reducing the efficiency of fault handling and maintenance.

[0030] To overcome the above-mentioned technical problems, embodiments of this application provide a network fault location method. Figure 2 This is a schematic diagram of a cross-layer association simple graph adjacency matrix fault location system provided in one embodiment of this application, as shown below. Figure 2 As shown, alarm dimensionality reduction mapping is performed on the adjacency matrix of the cross-layer association simple graph, and alarm range and faulty equipment are defined by clustering. Finally, the root cause of the fault is located based on multiple information such as the device alarms in the defined fault area.

[0031] Figure 3 This is a schematic flowchart of a network fault location method provided in one embodiment of this application, as shown below. Figure 3 As shown, the method includes the following steps:

[0032] Step 301: Deploy the Link Layer Discovery Protocol (LLDP) simultaneously in IP network layer and optical network layer devices, introduce a simple graph to represent the adjacency relationship between devices, and construct a simple graph adjacency matrix for cross-layer association.

[0033] Figure 4 This is a schematic diagram of a cross-layer association simple graph adjacency matrix fault location system provided in one embodiment of this application. For example, as shown... Figure 4 As shown, a graph G is constructed using a metropolitan area network (MAN) of a certain city as an example. The IP network from BRAS to PA in the CMNet MAN of this city is carried on the optical network ring of the first and second planes of the city and county. N devices are used as the vertex set V (Nth order) of graph G, and the links between devices are used as the edge set E of graph G. If edge α = {Vi, Vj} ∈ E, (i, j = 0, 1, ..., N), then the two devices Vi and Vj connected by α are adjacent. A one-dimensional array is used to store all vertex data of graph G. The two-dimensional array constructed using all vertices as rows and column headers to store the relationships (edges) between vertices is called the adjacency matrix. When there are no multiple edges in the adjacency relationships between vertices, the resulting graph G is a simple graph, denoted as Gi. S When the adjacency relationships between vertices have multiple edges, the resulting graph G is a multigraph, denoted as Gi. M Since the graph G formed by the network does not have vertex self-connections (cycles), in a simple graph G... S and multigraph G MA general graph cannot be constructed based on this. To enable devices from different manufacturers to exchange system / configuration information in the network, LLDP is chosen as the standard information exchange protocol to implement the link layer discovery method. LLDP organizes local device information into different TLVs (Type / Length / Value) and encapsulates them into Link Layer Discovery Protocol Data Units (LLDPDUs) and publishes them to directly connected neighbors. After receiving the information, the directly connected neighbors save it in the form of a standard MIB (Management Information Base) for querying and judging link status.

[0034] In one implementation, step 301 can be achieved through the following specific steps:

[0035] Step 301a: Configure LLDP for IP and optical networks.

[0036] Specifically, by jointly configuring LLDP for IP network and optical network elements, the mutual publication and collection of data such as device information, interconnection relationships, and interface identifiers of the cross-layer joint network composed of IP network and optical network can be realized, and these data information can be temporarily stored inside the joint network elements in the form of MIB.

[0037] Step 301b: The cross-layer integrated network management system collects the Management Information Base (MIB) on the federated network element side through Simple Network Management Protocol (SNMP) to obtain device adjacency information between federated network elements.

[0038] Step 301c: Construct a two-dimensional array to store the adjacency relationships of vertex elements based on the vertex set of network element devices in the joint network, and determine that the simple graph adjacency matrix construction is complete when the elements of the two-dimensional array are set to the set values.

[0039] Among them, the vertex set V of N network element devices in the joint network S (Nth order), with vertex set V S The elements Vi and Vj (i,j=0,1,…N) are used as the head of the row and column of the two-dimensional array, respectively, to construct a two-dimensional array to store the adjacency relationship of vertex elements. When Vi and Vj have an adjacency relationship, the element of the two-dimensional array is set to 1. Then the N-order simple graph adjacency matrix of N network elements in the joint network is completed.

[0040] An N-order simple graph adjacency matrix has its elements symmetrically distributed along its diagonal axis, such as... Figure 4 As shown, a total of N*(N-1) / 2 storage units are needed for data storage, which can efficiently index graph elements.

[0041] Step 302: Based on the alarms from the cross-layer association simple graph adjacency matrix, define the fault range and faulty devices, and obtain the association information.

[0042] Since the IP network layer and the optical network layer are operated and maintained independently, their control planes cannot effectively exchange network information and status, thus lacking a coordination mechanism. Therefore, by using relevant alarms from the IP network management alarm management system and the optical network alarm management system, a cross-layer correlation alarm adjacency matrix is ​​constructed by dimensionality reduction and association with a simple cross-layer correlation graph. Step 302 can then be achieved through the following specific steps:

[0043] Step 302a: Divide the standardized network management alarms into device-level alarms and link-level alarms, and perform cleaning work such as alarm deduplication and key alarm extraction based on the local device, peer device and interconnection link.

[0044] Step 302b: Map the cleaned alarms to the cross-layer association simple graph adjacency matrix. Device alarms are mapped to row elements of the association simple graph adjacency matrix; link alarms are mapped to individual elements of the association simple graph adjacency matrix.

[0045] Step 302c: Set the simple graph adjacency matrix elements with alarm associations to the first set value (e.g., the first set value is 1), and set the simple graph adjacency matrix elements without associations to the second set value (e.g., the second set value is 0), thereby constructing a cross-layer associated alarm adjacency matrix.

[0046] Step 302d: As Figure 5 As shown, based on the cross-layer associated alarm adjacency matrix, algorithms such as graph community clustering, K-means clustering, or fast greedy modularity maximization clustering are used to define the fault range and faulty devices and obtain associated information. Specifically, for each fault, the associated information of relevant vertex elements (devices) can be extracted from the cross-layer associated simple graph adjacency matrix.

[0047] Step 303: Determine the location of the fault based on the associated information.

[0048] After the scope of faulty devices obtained by clustering is defined, relevant vertex element (device) association information is extracted from the adjacency matrix of the cross-layer association simple graph for each fault. The fault location is then performed by combining the interface identifier stored in the device MIB collected by SNMP, the asset management system board information, and the device's own important alarm information.

[0049] The network fault location method provided in this application can effectively characterize the connection relationship between IP network devices and optical network devices by constructing a cross-layer association simple graph adjacency matrix for optical network collaboration. Based on this, a cross-layer topology can be constructed to intuitively show the carrying relationship between optical network layer and IP network layer devices. The mapping of optical network layer alarms and IP network layer alarms to the cross-layer association simple graph adjacency matrix can effectively solve the problems of alarm storms and the inability to associate cross-professional alarms. The cross-layer association simple graph adjacency matrix network fault location method realizes the association and collaboration between IP network and optical network layer, improving the accuracy and real-time performance of fault location.

[0050] This application also provides an electronic device that may include a processor and a memory, wherein the memory is used to store at least one instruction, which is loaded and executed by the processor to implement the network fault location method provided in any embodiment of this application.

[0051] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the network fault location method provided in any embodiment of this application.

[0052] This application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the network fault location method provided in any embodiment of this application.

[0053] It should be noted that the terminals involved in the embodiments of this application may include, but are not limited to, personal computers (PCs), personal digital assistants (PDAs), wireless handheld devices, tablet computers, mobile phones, MP3 players, MP4 players, etc.

[0054] It is understood that the application may be a native application installed on the terminal, or it may be a web application of a browser on the terminal. This application embodiment does not limit this.

[0055] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0056] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0057] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0058] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0059] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0060] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0061] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for locating network faults, characterized in that, The method includes: Configure link layer discovery protocols in IP network elements and optical network elements to represent the adjacency relationships between devices using a simple graph, and construct a simple graph adjacency matrix that links across layers; Alarms based on a cross-layer association simple graph adjacency matrix are used to define the fault range and faulty devices, and obtain association information; and The location of the fault is determined based on the associated information; The step of configuring a link layer discovery protocol in IP network elements and optical network elements, representing the adjacency relationships between devices with a simple graph, and constructing a simple graph adjacency matrix for cross-layer association includes: Configure link layer discovery protocols for the IP network elements and the optical network elements; collect management information databases on the joint network element side through simple network management protocol to obtain device adjacency information between joint network elements; and construct a two-dimensional array to store the adjacency relationships of vertex elements based on the vertex set of network element devices in the joint network, and determine that the simple graph adjacency matrix construction is complete when the elements of the two-dimensional array are set to a set value. The alarm based on the cross-layer association simple graph adjacency matrix defines the fault range and faulty devices, and obtains association information including: Standardized network management alarm outputs are divided into device-level alarms and link-level alarms. Alarm deduplication and key alarm extraction are performed based on local devices, peer devices, and interconnecting links. The cleaned alarms are mapped to a cross-layer associative simple graph adjacency matrix. Device alarms are mapped to row elements of the associative simple graph adjacency matrix, and link alarms are mapped to individual elements of the associative simple graph adjacency matrix. Elements of the simple graph adjacency matrix with alarm associations are set to a first set value, and elements without such associations are set to a second set value, thereby constructing a cross-layer associative alarm adjacency matrix. Based on the cross-layer associative alarm adjacency matrix, an algorithm is used to define the fault range and faulty devices, and association information is obtained. Determining the fault location based on the associated information includes: Based on the aforementioned associated information, fault location is performed by combining the interface identifiers, asset management system board information, and important alarm information of the equipment itself stored in the Joint Network Element Side Management Information Database collected by the Simple Network Management Protocol.

2. The method according to claim 1, characterized in that, The simple graph adjacency matrix is ​​symmetrically distributed with the diagonal as the axis.

3. The method according to claim 1, characterized in that, The associated information includes: after defining the fault range and faulty devices through a set algorithm, the associated information of relevant vertex devices is extracted from the adjacency matrix of the cross-layer association simple graph for each fault.

4. An electronic device, characterized in that, The device includes: A processor and a memory, the memory being used to store at least one instruction, which, when loaded and executed by the processor, implements the network fault location method as described in any one of claims 1-3.

5. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the network fault location method as described in any one of claims 1-3.

6. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the processor, they implement the network fault location method as described in any one of claims 1-3.

Images