Fault diagnosis method, electronic device and storage medium

Abstract

The present application belongs to the technical field of communications. Disclosed are a fault diagnosis method, an electronic device and a storage medium. The method comprises: separately performing connectivity detection, configuration information detection and performance analysis on a path to be tested; during the process of performing the configuration information detection on said path and in response to a connectivity detection result obtained by performing the connectivity detection on said path, performing the configuration information detection on an object, the status of which is abnormal as indicated by the connectivity detection result, among a current test object of said path undergoing the configuration information detection and a next object to be tested; and on the basis of the connectivity detection result, the configuration information detection result and a performance analysis result, obtaining a fault diagnosis result of said path, the fault diagnosis result comprising information of the abnormal object.

Description

Fault diagnosis method, electronic device and storage medium

[0001] Cross-reference to related applications

[0002] The present application claims priority to the Chinese patent application No. 202410474195.7, filed on April 19, 2024, and entitled "Fault diagnosis method, electronic device and storage medium", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] Embodiments of the present application relate to the field of communication technology, in particular to a fault diagnosis method, an electronic device and a storage medium. BACKGROUND

[0004] In a field environment, a large number of alarms may be reported in a short period of time due to device failure or other abnormal reasons. Due to the too fast frequency of alarm reporting, the network management system cannot normally provide other operation and maintenance functions in addition to alarm processing, so as to affect the availability of the network management system and fall into paralysis, which is an alarm storm.

[0005] The fault diagnosis method in the related technical solution adopts a multi-fault diagnosis process, as shown in FIG. 1. Although multiple faults are input for diagnosis together, each fault is actually executed by a separate fault diagnosis process. The results and processes of each fault diagnosis are mutually shielded, without information exchange and learning reference, and the diagnosis efficiency is low. SUMMARY

[0006] Embodiments of the present application provide a fault diagnosis method, an electronic device and a storage medium.

[0007] In a first aspect, a fault diagnosis method is provided. The method comprises: performing connectivity detection, configuration information detection and performance analysis on a to-be-detected path respectively; in the process of performing configuration information detection on the to-be-detected path, in response to a connectivity detection result obtained by performing connectivity detection on the to-be-detected path, performing the configuration information detection on an object with state abnormality indicated by the connectivity detection result between a current detection object and a next to-be-detected object of the to-be-detected path on which the configuration information detection is performed; and obtaining a fault diagnosis result of the to-be-detected path based on the connectivity detection result, a result obtained by the configuration information detection and a result obtained by the performance analysis, wherein the fault diagnosis result comprises information of the abnormal object.

[0008] In a second aspect, an electronic device is provided. The electronic device comprises a processor and a memory. The memory stores programs or instructions executable on the processor. When the programs or instructions are executed by the processor, the steps of the fault diagnosis method described above are implemented.

[0009] In a third aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions, and the program or instructions are executed by a processor to implement the steps of the fault diagnosis method.

[0010] In a fourth aspect, a computer program product is provided, and the computer program product stores a program or instructions, and the program or instructions are executed by a processor to implement the steps of the fault diagnosis method. BRIEF DESCRIPTION OF DRAWINGS

[0011] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0012] FIG. 1 shows a schematic diagram of an existing fault diagnosis method according to an example embodiment of the present application;

[0013] FIG. 2 shows a flowchart of a fault diagnosis method according to an example embodiment of the present application;

[0014] FIG. 3 shows a schematic diagram of a fault diagnosis method according to an example embodiment of the present application;

[0015] FIG. 4 shows a schematic diagram of a fault diagnosis function module according to an example embodiment of the present application;

[0016] FIG. 5 shows a network diagram of an A area according to an example embodiment of the present application;

[0017] FIG. 6 is a structural block diagram of an electronic device according to an example embodiment;

[0018] FIG. 7 shows a structural block diagram of another electronic device according to an example embodiment of the present application. DETAILED DESCRIPTION

[0019] The example embodiments will be described in detail herein with reference to the drawings. When the following description refers to accompanying drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The following example embodiments described are not representative of all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0020] A fault diagnosis method according to an example embodiment of the present application will be described in detail below with reference to the drawings and specific examples and application scenarios.

[0021] FIG. 2 shows a fault diagnosis method provided by an example embodiment of the present application. The method 200 can be executed by an electronic device, in other words, the method can be executed by software or hardware installed in the electronic device, which can be a terminal device such as a mobile phone. As shown in FIG. 2, the method mainly includes the following steps.

[0022] S201: performing connectivity detection, configuration information detection and performance analysis on the to-be-detected path respectively.

[0023] In the embodiment of the present application, the connectivity detection, configuration information detection and performance analysis on the to-be-detected path can be performed synchronously, that is, the connectivity detection, configuration information detection and performance analysis on the to-be-detected path are performed in parallel.

[0024] In an optional implementation, in order to diagnose the fault as soon as possible, the to-be-detected path most likely to have a fault can be determined according to the input multi-fault information. Therefore, in the optional implementation, before the connectivity detection on the to-be-detected path, the method can further include the following steps 1 to 3.

[0025] Step 1: obtaining at least one common path based on the input multi-fault information.

[0026] In actual application, the input multi-fault information can be summarized to obtain at least one common path (which can be referred to as common path for short), and in the embodiment of the present application, the information of the common path, i.e., common path information, can also be obtained. The common path information can include links, network elements, single boards, ports, etc., which are not limited.

[0027] Step 2: obtaining the priority of each common path.

[0028] For example, the priority of each common path can be obtained according to a pre-setting.

[0029] Step 3: determining the common path with the highest priority as the to-be-detected path.

[0030] In the above optional implementation of the embodiment of the present application, the common path with the highest priority can be determined as the to-be-detected path. In related technologies, one path of each link gives one diagnosis result, and in the embodiment of the present application, one to-be-detected path is determined and the following fault diagnosis is performed to obtain one diagnosis result, thereby improving the efficiency of diagnosis and saving time.

[0031] In an optional implementation, the obtaining of the priority of each of the public paths comprises the following steps: step 1, counting the usage times of each of the public paths; step 2, obtaining a coefficient weight of each of the public paths based on the service transmitted on each of the public paths; and step 3, obtaining the priority of each of the public paths based on the usage times and the coefficient weight of each of the public paths.

[0032] In the optional implementation of the foregoing embodiment of the present application, the usage times of each of the public paths can be counted according to the input multi-failure information, and the coefficient weight of each of the public paths can be obtained based on the service transmitted on each of the public paths. The coefficient weight of each of the public paths is related to the number of passes according to the public path and the importance coefficient of the public path. Generally, the weight value can be allocated when the service is opened, which can be understood as a preset weight value. Finally, the priority of each of the public paths is obtained based on the usage times and the coefficient weight of each of the public paths. In the implementation, the higher the weight value of the path, the higher the priority. In this implementation, the priority of each of the public paths is determined according to the usage times and the service transmitted on the public path, so that the highest priority can be set for the public path with the highest usage times and the highest service level, and then it can be determined as soon as possible whether the public path with the highest usage times and the highest service level is likely to fail, so as to restore the public path with the highest usage times and the highest service level as soon as possible and reduce the impact of the failure on the communication service.

[0033] In the optional implementation of the embodiment of the present application, the connectivity detection of the to-be-detected path can comprise at least one of the following.

[0034] (1) checking whether the three-layer routing information of the to-be-detected path is reachable, for example, checking whether the three-layer routing information of each network element on the to-be-detected path is reachable.

[0035] (2) checking the address resolution protocol (ARP) learning status of the next hop in the path, for example, checking the ARP learning status of the next hop of each network element on the to-be-detected path.

[0036] (3) monitoring the state of the out port of each network element on the to-be-detected path.

[0037] (4) performing bidirectional forwarding detection (BFD) on the static route of each network element on the to-be-detected path.

[0038] In an optional implementation of the embodiments of the present application, the configuration information detection on the to-be-detected path can include at least one of the following.

[0039] (1) Detection of whether a Virtual Routing Forwarding (VRF) ingress / egress label matches; for example, the VRF ingress / egress label matching of each object in the to-be-detected path can be detected.

[0040] (2) Consistency detection of a Virtual Local Area Network Range (VLAN-RANGE); for example, the VLAN-RANGE consistency of each object in the to-be-detected path can be detected.

[0041] (3) Consistency detection of an Address Resolution Protocol (ARP); for example, the ARP consistency of each object in the to-be-detected path can be detected.

[0042] In an optional implementation of the embodiments of the present application, the performance analysis on the to-be-detected path can include at least one of the following.

[0043] (1) Service forwarding time efficiency analysis; for example, the service forwarding time efficiency of each object on the to-be-detected path can be analyzed, for example, the time required for each network element on the to-be-detected path to receive service data and forward the service data can be analyzed.

[0044] (2) Service forwarding traffic performance analysis; for example, the service forwarding traffic performance of each object on the to-be-detected path can be analyzed. For example, the traffic required for each network element on the to-be-detected path to receive service data and forward the service data can be analyzed.

[0045] It should be noted that, although the above examples illustrate specific operations that the connectivity detection, the configuration information detection, and the performance analysis can include, the present application is not limited thereto, and in actual applications, the connectivity detection, the configuration information detection, and the performance analysis can also include other specific operations.

[0046] S202: In the process of the configuration information detection on the to-be-detected path, in response to a connectivity detection result obtained by the connectivity detection on the to-be-detected path, the configuration information detection is performed on an object indicated by the connectivity detection result as having a state abnormality between a current detection object and a next to-be-detected object of the to-be-detected path on which the configuration information detection is performed.

[0047] In the embodiment of the present application, in the process of configuration information detection on the to-be-detected path, the configuration information detection can be performed on the state abnormal object indicated by the connectivity detection result in response to the connectivity detection result obtained by performing connectivity detection on the to-be-detected path, between the current detection object and the next to-be-detected object of the to-be-detected path subjected to configuration information detection. That is, the result after connectivity detection of the to-be-detected path is pushed to configuration checking at the same time, and the configuration checking can focus on checking the links and network elements in the connectivity detection result during the checking process. In the embodiment of the present application, the three detections of connectivity detection, configuration information detection and performance analysis are parallel, and the interaction is reflected in that the connectivity detection can measure the link problem range section, that is, the position of the key section where the communication problem occurs on the link or network element, and the configuration checking can perform configuration checking in combination with the result of the connectivity detection, to focus on checking the configuration of the problem section (it can be understood that the configuration checking pre-checks the problem section corresponding to the connectivity detection result), and other sections are also checked later, but the key section is prioritized for checking.

[0048] In an optional implementation, the object includes at least one of a link, a network element, a single board and a port. In the embodiment of the present application, the object includes at least one of a link, a network element, a single board and a port, which is not specifically limited in the embodiment of the present application.

[0049] In an optional implementation of the embodiment of the present application, the performance analysis on the to-be-detected path can include: in the process of performance analysis on the to-be-detected path, in response to a connectivity detection result obtained by performing connectivity detection on the to-be-detected path, performing the performance analysis on an object in a state abnormality indicated by the connectivity detection result, between a current detection object and a next to-be-detected object of the to-be-detected path subjected to performance analysis.

[0050] In the above optional implementation of the embodiment of the present application, in the process of performance analysis on the to-be-detected path, in response to a connectivity detection result obtained by performing connectivity detection on the to-be-detected path, the performance analysis is preferentially performed on an object in a state abnormality indicated by the connectivity detection result. The performance analysis can include analyzing the service forwarding time efficiency of the object in the state abnormality, and analyzing the service forwarding traffic performance of the object in the state abnormality, so that the efficiency of the performance analysis can be improved, and the object with a fault can be analyzed as soon as possible.

[0051] S203: obtaining a fault diagnosis result of the to-be-detected path based on the connectivity detection result, the result obtained by the configuration information detection and the result obtained by the performance analysis.

[0052] The fault diagnosis result includes information of an abnormal object. The fault diagnosis result can include an identifier of the abnormal object and error information of the abnormal object. For example, the fault diagnosis result can include error information of a link, a network element, a single board, or a port.

[0053] By the technical solution provided in the embodiments of the present application, the configuration information detection can respond to the connectivity detection result obtained by the connectivity detection, and preferentially detect an object with a state abnormality indicated by the connectivity detection result, so that the fault diagnosis result of the to-be-detected path can be obtained as soon as possible, and the diagnosis efficiency is improved. Not only time is saved, but also the operation and maintenance personnel can quickly resolve the alarm storm, and customer complaints are reduced.

[0054] In an optional implementation of the embodiments of the present application, the result obtained by the configuration information detection based on the connectivity detection result, the result obtained by the configuration information detection, and the result obtained by the performance analysis can include the following steps: step 1, performing abnormality summarization based on the connectivity detection result, the result obtained by the configuration information detection, and the result obtained by the performance analysis; and step 2, obtaining the fault diagnosis result based on the abnormality information obtained by the summarization.

[0055] In the above implementation of the embodiments of the present application, the abnormality summarization can be performed based on the connectivity detection result, the result obtained by the configuration information detection, and the result obtained by the performance analysis, and then a fault diagnosis result can be obtained based on the abnormality information obtained by the summarization, so that the connectivity detection result, the result obtained by the configuration information detection, and the result obtained by the performance analysis can be combined to obtain a comprehensive fault diagnosis result, and the accuracy of fault diagnosis is improved.

[0056] In an optional implementation, the fault diagnosis result further includes a fault cause; and the obtaining of the fault diagnosis result based on the abnormality information obtained by the summarization can include searching a diagnosis file library based on the abnormality information obtained by the summarization to obtain the fault cause.

[0057] In the above optional implementation of the embodiments of the present application, the fault cause can be obtained by searching the diagnosis file library based on the abnormality information obtained by the summarization, and then the cause can be traced, which is helpful for the operation and maintenance personnel to resolve the alarm storm and reduce customer complaints.

[0058] The diagnosis file library can be a file library set in advance, and the file library can record various abnormality information and fault causes corresponding to the various abnormality information.

[0059] In an implementation, after the fault diagnosis result is obtained based on the abnormality information obtained by the summarization, the method can further include the following steps.

[0060] Step 1, based on the fault diagnosis result, obtaining a fault solution, for example, the diagnosis file library can record various abnormal information corresponding to the fault solution, and the corresponding fault solution can be obtained by querying the diagnosis file library.

[0061] Step 2, based on the fault solution, updating the configuration of the to-be-detected path.

[0062] Based on the above optional implementation, after the fault diagnosis result is diagnosed, the fault solution is obtained, and the configuration of the to-be-detected path is updated according to the fault solution, so as to restore the normal communication of the to-be-detected path.

[0063] FIG. 3 shows a flowchart of a fault diagnosis method provided by an embodiment of the application. As shown in FIG. 3, the method mainly includes the following steps.

[0064] S301, multiple fault information input.

[0065] S302, based on the input multiple fault information, quickly initiating detection.

[0066] S303, all fault information is summarized and then analyzed.

[0067] Through this step, the link with the most problems (the most alarms) can be obtained, wherein a link includes multiple paths / circuits corresponding to services, and the weight calculation of the circuit information gives priority.

[0068] S304, confirming the link of the to-be-detected path, the network element board, and the port of the first priority.

[0069] S305, performing connectivity detection on the to-be-detected path to obtain link state problems and network element problems; wherein the connectivity detection result is pushed to the configuration check at the same time.

[0070] S306, performing configuration information check on the to-be-detected path; wherein the configuration check focuses on checking the links and network elements in the connectivity detection result in the checking process, so that the configuration problems of the network elements, boards and links can be obtained.

[0071] S307, performing performance analysis on the to-be-detected path to obtain abnormal performance problems.

[0072] S308, analyzing and diagnosing the link state problems and network element problems obtained by the connectivity detection, the configuration problems of the network elements, boards and links obtained by the configuration information check, and the abnormal performance problems obtained by the performance analysis, reading the diagnosis file library, referring to the content of the file library, and giving multiple fault root causes.

[0073] By the technical solution, the configuration check can be performed in combination with the result of the connectivity detection to focus on checking the configuration of the problem section, so that the efficiency of diagnosis can be improved, and by aggregating the results of the three detections to obtain the fault diagnosis result, the accuracy of fault diagnosis can also be improved.

[0074] Fig. 4 shows a structure diagram of a fault diagnosis apparatus provided by an embodiment of the present application. As shown in Fig. 4, the fault diagnosis apparatus 400 can include the following modules.

[0075] A common path analysis module 401 is configured to aggregate the input multi-fault information, extract common path information (the common path information includes links, network elements, single boards, and ports), count the number of uses, and then add a service coefficient weight. After sorting, a first priority detection object (i.e., a path to be detected) is given. A detection module 402 is configured to perform connectivity detection, configuration check, and performance analysis on the path to be detected.

[0076] The connectivity detection can include whether the three-layer routing information is reachable, whether the ARP learning status of the next hop is checked, whether the out-port state is monitored, whether the static route BFD is checked, and the like.

[0077] The configuration check can include matching detection of VRF in-out labels, VLAN-RANGE range consistency detection, ARP consistency check, and the like.

[0078] The performance analysis can include service forwarding time efficiency, service forwarding flow performance, and the like.

[0079] A diagnosis module 403 is configured to search a diagnosis file library according to the problems given by the detection module, and give a fault root cause.

[0080] The following takes an example of 2000 alarm storms in the A area as an example to illustrate the fault diagnosis method provided by the embodiment of the present application. Fig. 5 is a schematic diagram of the network of the area.

[0081] 1. Common path analysis module

[0082] The system can automatically identify 2000 alarms in the area and import them in batches by one key. Some alarm information in the 2000 alarm storms can also be input manually.

[0083] After the information is aggregated, the common path information (the common path information includes links, network elements, single boards, and ports) is extracted, and the number of uses is counted to obtain that the MPE-1 to SPE-1 link is used 1900 times, wherein the service from the 6180H-UEP1 to MPE1 is sent to the global data laboratory, and the service weight is 10. The service from the 6180H-UEP4 to MPE-1 is sent to the B area, and the service weight is 3.

[0084] The first priority incoming diagnostic system is calculated to be the link, network element, board and port of the 6180H-UEP1 to MPE1 service.

[0085] 2, detection module

[0086] Connectivity detection: received incoming object 6180H-UEP1 to MPE-1 from the public diameter analysis module, start to check whether the three-layer routing information is reachable, the next hop ARP learning condition check, the out port state monitoring, static route BFD check and so on. Found that SPE-1 out port state monitoring of MPE-1 is abnormal.

[0087] Configuration check: focus on the configuration information check of the link, network element, board and port of SPE-1 to MPE-1 service, including VRF in and out label matching, VLAN-RANGE range consistency, ARP consistency check and so on. Through the check, it is found that the VLAN-RANGE range of SPE-1 to MPE-1 is inconsistent.

[0088] Performance analysis: the performance analysis of the link, network element, board and port of 6180H-UEP1 to MPE-1 service found that the SPE-1 network element VLAN1-100 range service forwarding traffic performance sustained warning bit.

[0089] 3, diagnosis module

[0090] The diagnosis module performs comprehensive analysis according to the three problems given by the detection module.

[0091] 1, SEP-1 out port state of MPE-1 is abnormal.

[0092] 2, the VLAN-RANGE range of SPE-1 to MPE-1 is inconsistent. The range of MPE-1 is 1-249, and the range of SPE-1 is 100-249.

[0093] 3, the VLAN1-100 range service forwarding traffic performance sustained warning bit of SPE-1.

[0094] According to the diagnosis result given by the detection module, the VLAN-RANGE range of SPE-1 and MPE-1 is inconsistent. Search the diagnosis file library, the range configuration of 6700 device is 1-249.

[0095] Give the diagnosis result, the fault root cause SPE-1 configuration parameter VLAN-RANGE range needs to be modified to VLAN1-249.

[0096] In the related art, a fault is simply queried from a file library to obtain a diagnosis result. Disadvantages of this process are slow analysis, inaccurate analysis results, and only file library comparison. If there is no matching content in the file library, no diagnosis result is obtained. Moreover, the root cause cannot be distinguished, and the root cause cannot be analyzed at the first time. Therefore, a large amount of time is wasted by an operation and maintenance personnel to troubleshoot. By using the above technical solution, multi-fault summary path information is weighted and assigned a priority, and diagnosis is summarized to focus on the root cause of the problem at the first time and find the target. In addition, the detection modules share information with each other, give a conclusion after combined analysis, the fault diagnosis result has logical judgment ability, and is more accurate.

[0097] Optionally, as shown in FIG. 6, the embodiment of the present application further provides an electronic device 600, including a processor 601 and a memory 602, the memory 602 stores programs or instructions that can run on the processor 601, the programs or instructions are executed by the processor 601 to realize each step of the above fault diagnosis method, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0098] It should be noted that the electronic device in the embodiment of the present application includes the mobile electronic device and the non-mobile electronic device described above.

[0099] FIG. 7 shows a structural block diagram of another electronic device 700 according to an example embodiment of the present application. The electronic device 700 can be implemented as a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart watch, a television, and the like. The electronic device 700 can also be referred to as a user equipment, a portable terminal, a laptop terminal, a desktop terminal, and other names.

[0100] Generally, the electronic device 700 includes a processor 701 and a memory 702.

[0101] The processor 701 can include one or more processing cores, such as a 4-core processor, a 10-core processor, etc. The processor 701 can be implemented in at least one of a hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), a PLA (Programmable Logic Array). The processor 701 can also include a main processor and a coprocessor, the main processor being a processor for processing data in an awake state, also known as a CPU (Central Processing Unit), and the coprocessor being a low-power processor for processing data in a standby state. In some embodiments, the processor 701 can be integrated with a GPU (Graphics Processing Unit) for rendering and drawing content required to be displayed by the display screen. In some embodiments, the processor 701 can further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

[0102] The memory 702 can include one or more computer-readable storage media that can be non-transitory. The memory 702 can also include a high-speed random access memory, and a nonvolatile memory such as one or more disk storage devices, flash storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 702 is used to store at least one instruction for being executed by the processor 701 to implement all or part of the steps in the alternative path selection method shown in the method embodiments of the present application.

[0103] In some embodiments, the electronic device 700 can also optionally include a peripheral device interface 703 and at least one peripheral device. The processor 701, the memory 702, and the peripheral device interface 703 can be connected through a bus or a signal line. Each peripheral device can be connected to the peripheral device interface 703 through a bus, a signal line, or a circuit board. Specifically, the peripheral device includes at least one of a radio frequency circuit 704, a display screen 705, a camera assembly 706, an audio circuit 707, and a power supply 708.

[0104] In some embodiments, the electronic device 700 further includes one or more sensors 709. The one or more sensors 709 include, but are not limited to, an acceleration sensor 710, a gyroscope sensor 711, a pressure sensor 712, an optical sensor 713, and a proximity sensor 714.

[0105] Those skilled in the art can understand that the structure shown in FIG. 7 does not constitute a limitation on the electronic device 700, and can include more or fewer components than illustrated, or combine certain components, or have a different arrangement of components.

[0106] In an example embodiment, a computer readable storage medium is also provided, in which at least one computer program is stored, the computer program is loaded and executed by a processor to implement all or part of the steps of the above fault diagnosis method. For example, the computer readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0107] The embodiments of the present application further provide a chip, which comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running programs or instructions to implement various processes of the above fault diagnosis method and achieve the same technical effects. To avoid repetition, details are not described here.

[0108] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system-level chip, a system chip, a chip system, or a system-on-chip chip, etc.

[0109] In an example embodiment, a computer program product is also provided, which comprises at least one computer program, the computer program is loaded and executed by a processor to implement all or part of the steps of the above fault diagnosis method shown in FIG. 2.

[0110] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the application being indicated by the following claims. The specification and examples do not restrict the application.

[0111] It should be understood that the present application is not limited to the precise construction that has been described above and shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is limited only by the appended claims.

Claims

1. A fault diagnosis method, comprising: performing connectivity detection, configuration information detection and performance analysis on a to-be-detected path respectively; in the process of performing configuration information detection on the to-be-detected path, in response to a connectivity detection result obtained by performing connectivity detection on the to-be-detected path, performing the configuration information detection on an object indicated by the connectivity detection result as being in a state of abnormality between a current detection object and a next to-be-detected object of the to-be-detected path on which the configuration information detection is performed; obtaining a fault diagnosis result of the to-be-detected path based on the connectivity detection result, a result obtained by performing the configuration information detection and a result obtained by performing the performance analysis, wherein the fault diagnosis result comprises information of the abnormal object.

2. The method of claim 1, wherein, Before the connectivity detection on the to-be-detected path, the method further comprises: obtaining at least one common path based on inputted multi-fault information; obtaining a priority of each common path; determining a common path with the highest priority as the to-be-detected path.

3. The method of claim 2, wherein, The obtaining of the priority of each common path comprises: counting a usage frequency of each common path; obtaining a coefficient weight of each common path based on a service transmitted on each common path; obtaining the priority of each common path based on the usage frequency and the coefficient weight of each common path.

4. The method of claim 1, wherein, The performance analysis on the to-be-detected path comprises: in the process of performing performance analysis on the to-be-detected path, in response to a connectivity detection result obtained by performing connectivity detection on the to-be-detected path, performing the performance analysis on an object indicated by the connectivity detection result as being in a state of abnormality between a current detection object and a next to-be-detected object of the to-be-detected path on which the performance analysis is performed.

5. The method according to any one of claims 1 to 4, wherein, The obtaining of the fault diagnosis result of the to-be-detected path based on the connectivity detection result, the result obtained by performing the configuration information detection and the result obtained by performing the performance analysis comprises: performing abnormality summarization based on the connectivity detection result, the result obtained by performing the configuration information detection and the result obtained by performing the performance analysis; obtaining the fault diagnosis result based on the abnormality information obtained by the summarization.

6. The method of claim 5, wherein, The fault diagnosis result further comprises a fault cause, and the obtaining of the fault diagnosis result based on the abnormality information obtained by the summarization comprises: searching a diagnosis file library based on the abnormality information obtained by the summarization to obtain the fault cause.

7. The method according to any one of claims 1 to 4, wherein, The object comprises at least one of a link, a network element, a single board and a port. 8.An electronic device, comprising a processor and a memory, wherein the memory stores a program or instructions executable on the processor, and the program or instructions are executed by the processor to implement steps of the fault diagnosis method according to any one of claims 1 to 7. 9.A readable storage medium, wherein the readable storage medium stores a program or instructions, and the program or instructions are executed by a processor to implement steps of the fault diagnosis method according to any one of claims 1 to 7.

10. A computer program product having stored thereon a program or instructions which, when executed by a processor, implement the steps of the fault diagnostic method according to any one of claims 1 to 7.

Images