A method and apparatus for failure localization of an intermediate system to intermediate system protocol failure

Abstract

The application discloses a fault positioning method and device for intermediate system to intermediate system protocol failure, wherein the method comprises the following steps: S01, loading network alarm data, including device port Down alarm and IS-IS Down alarm; S02, checking whether the IS-IS state is recovered; S03, Ping measuring neighbor IP, whether reachable; S04, checking whether the opposite ARP is learned; S05, checking whether the configuration area IDs at both ends are consistent; S06, checking whether the LEVEL levels at both ends are consistent; S07, checking whether the interface network types at both ends are the same; and S08, logging in to the opposite device, which is the neighbor device of the device receiving the IS-IS Down alarm, and Ping measuring the interconnection IP, whether reachable. The application discloses a fault positioning method and device for intermediate system to intermediate system protocol failure, through alarm collection and analysis, protocol state collection and analysis, and testing initiated according to the fault network element, the fault positioning of the IS-IS Down is realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and in particular to a method and device for fault positioning of an intermediate system to intermediate system protocol failure. BACKGROUND

[0002] IS-IS (Intermediate System to Intermediate System) protocol is a routing protocol widely used in IP networks, which belongs to IGP (Interior Gateway Protocol). When the IS-IS protocol has a Down failure, it will cause network communication interruption, affecting the stability and efficiency of data transmission.

[0003] Because it is a protocol-level failure, fault positioning is complex, and the following problems exist:

[0004] Dynamic: Routing protocols are dynamic, and routing information in the network is constantly updated as the network state changes. This means that the fault may be temporary or persistent, and the manifestation of the fault may change over time;

[0005] Protocol complexity: Routing protocols are complex, containing multiple parameters and state variables. Understanding how these parameters interact and how they affect routing is crucial for fault positioning;

[0006] Dependency: Routing protocol failures are associated with network layer problems, increasing the complexity of fault diagnosis, and analysis across multiple network layers.

[0007] Maintenance personnel need to spend a long time manually judging the location of the fault, causing the problem to be stuck for a long time, which has a negative impact on customers.

[0008] Currently, maintenance personnel need to use various protocols and commands to analyze the fault based on professional knowledge, spend a long time manually judging the cause of the IS-IS Down failure, which is time-consuming and laborious, and the fault handling timeliness is low. On the one hand, it requires deep professional knowledge and rich experience; on the other hand, even with experience, there may be omissions in the actual operation of routing fault positioning, and maintenance personnel are under great pressure. SUMMARY

[0009] To solve the problems existing in the prior art, the present application provides a method and device for fault positioning of an intermediate system to intermediate system protocol failure, which realizes fault positioning of IS-IS Down by collecting and analyzing alarms, collecting and analyzing protocol states, and initiating tests for faulty network elements.

[0010] To achieve the above object, the application adopts the following technical scheme:

[0011] In an embodiment of the application, a fault locating method for IS-IS protocol failure is provided, which comprises the following steps:

[0012] S01, loading network alarm data, including: focusing on device port Down alarm and IS-IS Down alarm;

[0013] Further, the S01 comprises:

[0014] S011, when a device network element appears port Down alarm and continuously appears IS-IS Down alarm, it can be judged that the IS-IS protocol Down is caused by device port Down;

[0015] Further, the number of continuously appearing IS-IS Down alarm in the S011 is not less than 3.

[0016] S012, logging in the device receiving IS-IS Down alarm, and entering S02.

[0017] S02, checking whether the IS-IS state is recovered;

[0018] Further, the S02 comprises:

[0019] S021, executing the command "system-view" to enter the system view, executing the command "display IS-IS peer" to check the state of IS-IS neighbor, and executing the command "display IS-IS interface" to check the IS-IS state on the interface where the IS-IS Down fault is located;

[0020] Further, the system view in the S021 is a specific mode entered by a user through a command line interface (CLI), which is used for configuring and managing system-level parameters of a device network element, and the system view has the function of accessing the global configuration of the device network element.

[0021] S022, when the IS-IS state is UP, checking whether the IS-IS connection has self-healed and the fault has been recovered, and ending the flow;

[0022] S023, when the IS-IS state is not recovered, entering S03.

[0023] S03, pinging the neighbor IP to check whether it is reachable;

[0024] Further, the S03 comprises:

[0025] S031, execute the command "ping x.x.x.x [neighbor IP]", return "!" to indicate Ping reachable; return "...." to indicate Ping unreachable;

[0026] S032, Ping unreachable, prompt IS-IS interruption, peer address unreachable, locate the fault cause, and the process ends;

[0027] S033, Ping reachable, prompt IS-IS peer ping reachable, enter S04.

[0028] S04, check whether the peer ARP is learned;

[0029] Further, the S04 comprises:

[0030] S041, execute the command "dis arp interface eth", and the "D" in the echoed information indicates that the learning is successful, and other echoed information indicates that the learning is failed;

[0031] S042, if the learning is successful, the peer ARP is learned, and enter S05;

[0032] S043, if the learning is failed, the peer ARP is not learned, prompt ARP learning failed, locate the fault cause, and the process ends.

[0033] S05, check whether the region IDs of two ends are consistent;

[0034] Further, the S05 comprises:

[0035] S051, execute the commands "display cur conf IS-IS" on the local device and the peer device respectively, and check whether the IS-IS configuration region IDs of the local device and the peer device are consistent;

[0036] S052, if the IS-IS region IDs are consistent, the check is passed, and enter S06;

[0037] S053, if the IS-IS configuration region IDs of the local device and the peer device are inconsistent, locate the fault cause, and the process ends.

[0038] S06, check whether the LEVEL levels of two ends are consistent;

[0039] Further, the S06 comprises:

[0040] S061, execute the commands "display IS-IS interface GigabitEthernet0 / 0 / 0 [interconnection interface]" on the local device and the peer device respectively, and check whether the IS-IS configuration level of the local device and the peer device are consistent;

[0041] S062, if the level of the two ends is the same, then pass, and enter S07;

[0042] S063, if the level of the two ends is inconsistent, then locate the fault cause, and the process ends;

[0043] S07, check whether the network types of the interfaces of the two ends are the same;

[0044] Further, the S07 comprises:

[0045] S071, respectively execute the command “display cur interface Eth-Trunk x | include IS-IS” on the local device and the peer device, and check whether the network types of the IS-IS interfaces of the local device and the peer device are the same;

[0046] S072, if the network types of the interfaces of the two ends are the same, then check pass, and enter S08;

[0047] S073, if the network types of the interfaces of the two ends are inconsistent, then locate the fault cause, and the process ends.

[0048] S08, log in the peer device, which is the neighbor device of the device receiving the IS-IS Down alarm, and ping the interconnected IP to check whether it is reachable.

[0049] Further, the S08 comprises:

[0050] S081, execute the command “ping x.x.x.x [local device IP]”, and return “!” to indicate that it is reachable, and return “....” to indicate that it is unreachable;

[0051] S082, if the ping is unreachable, then prompt IS-IS interruption, the peer ping address of the local device is unreachable, locate the fault cause, and the process ends;

[0052] S083, if the ping is reachable, then transfer to manual processing.

[0053] In an embodiment of the present application, a fault locating device for intermediate system to intermediate system protocol failure is also provided, which comprises:

[0054] a network alarm data loading module, which loads network alarm data including device port Down alarm and IS-IS Down alarm;

[0055] an IS-IS state checking module, which checks whether the IS-IS state is recovered;

[0056] Ping test module, Ping neighbor IP, whether reachable;

[0057] Learned peer ARP module, check whether the peer ARP is learned;

[0058] ID consistency module, check whether the area ID of the two ends is consistent;

[0059] LEVEL consistency module, check whether the LEVEL level of the two ends is consistent;

[0060] Network type module, check whether the network types of the two ends are the same;

[0061] Peer Ping test module, log in to the peer device, which is the neighbor device of the device receiving the IS-IS Down alarm, Ping the interconnection IP, and whether it is reachable.

[0062] In an embodiment of the present application, a computer device is also provided, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the aforementioned intermediate system to intermediate system protocol failure positioning method when executing the computer program.

[0063] In an embodiment of the present application, a computer readable storage medium is also provided, which stores a computer program for implementing the intermediate system to intermediate system protocol failure positioning method.

[0064] Advantages:

[0065] The intermediate system to intermediate system protocol failure positioning method and device provided by the present application have the advantages that the expert ability is attached, the IS-IS Down fault diagnosis is automatically performed in combination with alarm information, network protocols and test commands, the check result data is processed in real time to ensure the timeliness, the IS-IS Down fault is processed and analyzed in a flow, the network operation and maintenance personnel are helped to quickly locate the business fault, and the work pressure is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0066] Figure 1 is a flowchart of the intermediate system to intermediate system protocol failure positioning method in the present application;

[0067] Figure 2 is a structural schematic diagram of the intermediate system to intermediate system protocol failure positioning device in the present application;

[0068] Figure 3 is a structural schematic diagram of the computer device in an embodiment of the present application. DETAILED DESCRIPTION

[0069] The principles and spirits of the present application will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are given only to enable those skilled in the art to better understand and implement the present application, and are not intended to limit the scope of the present application in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0070] It is known to those skilled in the art that the embodiments of the present application can be implemented as a system, a device, an apparatus, a method or a computer program product. Therefore, the present disclosure can be embodied in the form of an entirely hardware, an entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0071] According to the embodiments of the present application, a fault locating method and device for intermediate system to intermediate system protocol failure are provided. The method comprises collecting and analyzing alarms, collecting and analyzing protocol states, and initiating a test for a faulty network element, thereby realizing fault locating for IS-IS Down.

[0072] The principles and spirits of the present application will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are given only to enable those skilled in the art to better understand and implement the present application, and are not intended to limit the scope of the present application in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0073] As shown in Figure 1 A fault locating method for intermediate system to intermediate system protocol failure according to the present application, the method comprises:

[0074] S01, loading network alarm data, including: focusing on device port Down alarm and IS-IS Down alarm;

[0075] The S01 comprises:

[0076] S011, when a device network element appears a port Down alarm and continuously appears an IS-IS Down alarm, it can be judged that the IS-IS protocol Down is caused by the device port Down;

[0077] The number of times of continuously appearing the IS-IS Down alarm in the S011 is not less than 3.

[0078] S012, logging in the device receiving the IS-IS Down alarm, and entering S02.

[0079] S02, checking whether the IS-IS state is recovered;

[0080] The S02 comprises:

[0081] S021, execute the command "system-view" to enter the system view, execute the command "display IS-IS peer" to check the status of IS-IS neighbor, execute the command "display IS-IS interface" to check the IS-IS status on the interface where the IS-IS Down fault is located;

[0082] The system view in S021 is a specific mode entered by a user through a command line interface (CLI), which is used to configure and manage system-level parameters of a device network element, and the system view has the function of accessing global configuration of the device network element.

[0083] S022, if the IS-IS status is UP, check whether the IS-IS connection has self-healed and the fault has been recovered, and the process ends;

[0084] S023, if the IS-IS status is not recovered, enter S03.

[0085] S03, ping the neighbor IP to check whether it is reachable;

[0086] The S03 includes:

[0087] S031, execute the command "ping x.x.x.x [neighbor IP]" to return "!" indicating that the ping is reachable, and return "...." indicating that the ping is not reachable;

[0088] S032, if the ping is not reachable, prompt that the IS-IS is interrupted and the opposite address is not reachable, locate the fault reason, and the process ends;

[0089] S033, if the ping is reachable, prompt that the IS-IS peer ping is reachable, and enter S04.

[0090] S04, check whether the opposite ARP is learned;

[0091] The S04 includes:

[0092] S041, execute the command "dis arp interface eth" to return "D" in the echoed information, which means that the learning is successful, and other echoed information means that the learning is failed;

[0093] S042, if the learning is successful, the opposite ARP is learned, and enter S05;

[0094] S043, if the learning is failed, the opposite ARP is not learned, prompt that the ARP learning is failed, locate the fault reason, and the process ends.

[0095] S05, check whether the configuration area IDs of two ends are consistent;

[0096] The S05 comprises:

[0097] S051, respectively executing the command "display cur conf IS-IS" on the local device and the peer device to check whether the IS-IS configuration area IDs of the local device and the peer device are consistent;

[0098] S052, if the IS-IS area IDs are consistent, the check is passed, and the process goes to S06;

[0099] S053, if the IS-IS configuration area IDs of the local device and the peer device are inconsistent, the fault reason is located, and the process ends.

[0100] S06, checking whether the LEVELs of the two ends are consistent;

[0101] The S06 comprises:

[0102] S061, respectively executing the command "display IS-IS interface GigabitEthernet0 / 0 / 0 [interconnection interface]" on the local device and the peer device to check whether the level levels of the local device and the peer device are consistent;

[0103] S062, if the level levels of the two ends are the same, the check is passed, and the process goes to S07;

[0104] S063, if the LEVEL levels of the two ends are inconsistent, the fault reason is located, and the process ends.

[0105] S07, checking whether the network types of the interfaces of the two ends are the same;

[0106] The S07 comprises:

[0107] S071, respectively executing the command "display cur interface Eth-Trunk x | include IS-IS" on the local device and the peer device to check whether the IS-IS interface network types of the local device and the peer device are the same;

[0108] S072, if the IS-IS network types of the interfaces of the two ends are the same, the check is passed, and the process goes to S08;

[0109] S073, if the IS-IS network types of the interfaces of the two ends are inconsistent, the fault reason is located, and the process ends.

[0110] In the IS-IS protocol, the network types usually include the following:

[0111] point-to-point: point-to-point network, usually used for serial link.

[0112] broadcast: broadcast network, usually used in Ethernet environment.

[0113] non-broadcast: non-broadcast multiple access network, such as some types of frame relay network.

[0114] S08, log in the opposite end device, which is the neighbor device receiving IS-IS Down alarm device, ping the interconnection IP, whether it is reachable.

[0115] The S08 comprises:

[0116] S081, execute the command "ping x.x.x.x [the IP of the local device]", return "!" to indicate that it is reachable, and return "...." to indicate that it is not reachable;

[0117] S082, ping the unreachable, prompt IS-IS interruption, the opposite end ping the local end address is not reachable, locate the fault cause, and the process ends;

[0118] S083, ping the reachable, and transfer to manual processing.

[0119] It should be noted that although the operations of the method of the present application are described in a specific order in the above embodiments and drawings, this does not require or imply that the operations must be performed in this specific order, or that all of the shown operations must be performed to achieve the desired result. Additionally or alternatively, some steps can be omitted, a plurality of steps can be combined into one step, and / or one step can be divided into a plurality of steps.

[0120] In order to more clearly explain the above-mentioned fault locating method for intermediate system to intermediate system protocol failure, the following specific embodiments will be described, however, it should be noted that the embodiments are only for better illustrating the present application, and do not constitute an improper limitation on the present application.

[0121] S01, load network alarm data, including: focus on device port Down alarm, IS-IS Down alarm;

[0122] The S01 comprises:

[0123] S011, when the device network element appears port Down alarm and continuous IS-IS Down alarm, it can be judged that it is caused by device port Down and IS-IS protocol Down;

[0124] The number of continuous IS-IS Down alarms in the S011 is not less than 3.

[0125] S012, log in the device receiving IS-IS Down alarm, enter S02.

[0126] S02, check whether IS-IS state is recovered;

[0127] The S02 comprises:

[0128] S021, execute command "system-view" to enter system view, execute command "display IS-IS peer" to check the state of IS-IS neighbor, execute command "display IS-IS interface" to check the IS-IS state on the interface where IS-IS Down fault is located;

[0129] The system view in the S021 is a specific mode entered by a user through a command line interface (CLI), used for configuring and managing system-level parameters of the device network element, and the system view has the function of accessing global configuration of the device network element.

[0130] S022, if the IS-IS state is UP, check whether IS-IS connection has self-healed and the fault has been recovered, and the process ends;

[0131] S023, if the IS-IS state is not recovered, enter S03.

[0132] S03, ping the neighbor IP to check whether it is reachable;

[0133] The S03 comprises:

[0134] S031, execute command "ping x.x.x.x [neighbor IP]" to return "!" indicating that ping measurement is reachable, and return "...." indicating that ping measurement is not reachable;

[0135] S032, if ping measurement is not reachable, prompt IS-IS interruption, and the address of the opposite end is not reachable, locate the fault cause, and the process ends;

[0136] S033, if ping measurement is reachable, prompt IS-IS peer ping is reachable, and enter S04.

[0137] S04, check whether the opposite end ARP is learned;

[0138] The S04 comprises:

[0139] S041, execute command "dis arp interface eth", and if "D" is in the echoed information, it means that learning is successful, and other echoed information means that learning fails;

[0140] S042, if the learning is successful, the peer ARP is learned, and the process goes to S05;

[0141] S043, if the learning is unsuccessful, the peer ARP is not learned, the ARP learning failure is prompted, the failure cause is located, and the process ends.

[0142] S05, whether the area IDs of the two ends are consistent is checked;

[0143] The S05 includes:

[0144] S051, the command "display cur conf IS-IS" is executed on the local device and the peer device respectively, and whether the IS-IS area IDs of the local device and the peer device are consistent is checked;

[0145] S052, if the IS-IS area IDs are consistent, the check is passed, and the process goes to S06;

[0146] S053, if the IS-IS area IDs of the local device and the peer device are inconsistent, the failure cause is located, and the process ends.

[0147] Example:

[0148] display cur conf IS-IS

[0149] IS-IS interface GigabitEthernet0 / 0 / 0

[0150] IS-IS state UP

[0151] IS-IS area 49.0001

[0152] In this example, the IS-IS area 49.0001 indicates that the interface belongs to the IS-IS area 49.0001.

[0153] S06, whether the LEVEL levels of the two ends are consistent is checked;

[0154] The S06 includes:

[0155] S061, the command "display IS-IS interface GigabitEthernet0 / 0 / 0 [interconnected interface]" is executed on the local device and the peer device respectively, and whether the IS-IS configuration level of the local device and the peer device is consistent is checked;

[0156] S062, if the level levels of the two ends are the same, the check is passed, and the process goes to S07;

[0157] S063, The LEVEL levels at both ends are inconsistent. The cause of the fault has been located, and the process ends.

[0158] For example: if one end is level 1 and the other end is level 2, it will not pass.

[0159] Example:

[0160] display IS-IS interface GigabitEthernet0 / 0 / 0

[0161] IS-IS interface GigabitEthernet0 / 0 / 0

[0162] IS-IS state UP

[0163] IS-IS circuit-type level-2-only

[0164] IS-IS priority 0

[0165] IS-IS hello interval 9 seconds

[0166] IS-IS hello multiplier 3

[0167] IS-IS cost 100 metric-style wide

[0168] In this example, IS-IS circuit-type level-2-only indicates that the interface is configured for Level-2 only. If level-1-2 is displayed, it means that the interface supports both Level-1 and Level-2.

[0169] S07. Check if the network types of the interfaces at both ends are the same;

[0170] S07 includes:

[0171] S071. Execute the command "display cur interface Eth-Trunk x | include IS-IS" on both the local and remote devices to check whether the network types of the IS-IS interfaces on the local and remote devices are the same.

[0172] S072 If the IS-IS network types of the two-end interfaces are the same, the check passes and proceeds to S08;

[0173] S073, Inconsistent IS-IS network types at both ends of the interface interconnection. The cause of the fault has been identified, and the process ends.

[0174] In IS-IS protocol, network types are usually as follows:

[0175] point-to-point: point-to-point network, usually used for serial links.

[0176] broadcast: broadcast network, usually used in Ethernet environment.

[0177] non-broadcast: non-broadcast multiple access network, such as some types of frame relay network.

[0178] Example:

[0179] display cur interface Eth-Trunk x | include IS-IS

[0180] IS-IS interface GigabitEthernet0 / 0 / 0

[0181] IS-IS network-type point-to-point

[0182] In this example, IS-IS network-type point-to-point, indicating that the IS-IS network type of the interface is configured as point-to-point.

[0183] S08, log in to the opposite device, which is the neighbor device receiving the IS-IS Down alarm device, Ping the interconnection IP, and check whether it is reachable.

[0184] The S08 includes:

[0185] S081, execute the command "ping x.x.x.x [local device IP]", return "!" to indicate reachability, and return "...." to indicate unreachability;

[0186] S082, Ping is not reachable, prompt IS-IS interruption, opposite Ping local address is not reachable, locate the cause of the failure, and the process ends;

[0187] S083, Ping is reachable, and transfer to manual processing.

[0188] Based on the same inventive concept, the present application further proposes a fault locating device for IS-IS protocol failure. The implementation of the device can refer to the implementation of the above method, and the repeated parts will not be described herein. The term "module" used below can be a combination of software and / or hardware that realizes the predetermined function. Although the device described in the following embodiments is preferably realized in software, the implementation of hardware or a combination of software and hardware is also possible and is conceived.

[0189] Figure 2 Fig. 1 is a structural schematic diagram of the fault locating device for IS-IS protocol failure according to the present application. As shown in Fig. 1, the device comprises: Figure 2

[0190] a network alarm data loading module 110 for loading network alarm data including device port Down alarm and IS-IS Down alarm;

[0191] an IS-IS state checking module 120 for checking whether the IS-IS state is recovered;

[0192] a Ping measurement module 130 for Ping measurement of neighbor IP and whether it is reachable;

[0193] a learning-to-destination ARP module 140 for checking whether learning to the destination ARP;

[0194] an ID consistency module 150 for checking whether the area ID configured on both ends is consistent;

[0195] a LEVEL consistency module 160 for checking whether the LEVEL level on both ends is consistent;

[0196] a network type module 170 for checking whether the interface network type on both ends is the same;

[0197] a destination Ping measurement module 180 for logging in the destination device, which is the neighbor device of the device receiving the IS-IS Down alarm, and Ping measurement of interconnection IP and whether it is reachable.

[0198] It should be noted that although several modules of the fault locating device for IS-IS protocol failure are mentioned in the above detailed description, such division is only exemplary and not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules described above can be embodied in one module. Conversely, the features and functions of one module described above can be further divided into modules embodied by multiple modules.

[0199] Based on the foregoing inventive concept, as Figure 3 ​As shown, the present application also proposes a computer device 200, comprising a memory 210, a processor 220, and a computer program 230 stored in the memory 210 and executable on the processor 220, wherein the processor 220 implements the aforementioned fault locating method for IS-IS Down when executing the computer program 230.

[0200] Based on the aforementioned inventive concept, the present application also proposes a computer readable storage medium, which stores a computer program for executing the aforementioned fault locating method for IS-IS Down.

[0201] The present application is a fault locating method and device for IS-IS Down, which is attached with expert capabilities, automatically diagnoses the fault of IS-IS Down in combination with alarm information, network protocols, and test commands, analyzes and processes the inspection result data in real time to ensure its timeliness; the present application processes and analyzes the fault of IS-IS Down in a flow, helps network operation and maintenance personnel quickly locate the business fault, and reduces their work pressure; the fault locating process of the present application is standardized and automated, reduces the possibility of human error and omission, improves the accuracy of fault diagnosis, and improves the efficiency of fault location.

[0202] Although the spirit and principles of the present application have been described with reference to several specific embodiments, it should be understood that the present application is not limited to the disclosed specific embodiments, and the division of aspects does not mean that the features in these aspects cannot be combined for the benefit, but is only for the convenience of expression. The present application is intended to cover various modifications and equivalent arrangements included in the spirit and scope of the appended claims.

[0203] Various embodiments of the systems and techniques described above can be realized in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a complex programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0204] Program code for carrying out methods of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the program code, when executed by the processor or controller, produces the functions / operations specified in the flowcharts and / or block diagrams. The program code can be executed entirely on a machine, partially on a machine, partially on a machine as a standalone software package, or entirely on a remote machine or server.

[0205] In the context of the present disclosure, a machine-readable medium can be a tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0206] To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0207] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0208] The computer system can include clients and servers. This relationship can be. The servers are typically remote from the clients with the interactions between them occurring over a communication network. The relationship between client and server is one of client-server. The server can be a cloud server, a server of a distributed system, or a server incorporating a blockchain.

[0209] It should be understood that the various forms of flow shown above can be re-ordered, added to, or deleted from without departing from the scope of the present disclosure. For example, the steps recited in the present disclosure can be executed in parallel, executed in series, or executed in different orders, as long as the desired results of the technical solutions of the present disclosure are achieved, and the present disclosure is not limited herein.

[0210] The above detailed description does not constitute a limitation on the protection scope of the present disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent replacements, and improvements within the spirit and principles of the present disclosure should be included in the protection scope of the present disclosure.

[0211] The skilled in the art should understand that various modifications or changes made on the basis of the technical solutions of the present disclosure without creative labor are still within the protection scope of the present disclosure.

Claims

1. A fault location method for intermediate system-to-intermediate system protocol failure, characterized in that, The method includes: S01. Load network alarm data including: device port down alarm, IS-IS down alarm, wherein the IS-IS down alarm indicates that the intermediate system to intermediate system protocol has failed; S02. Check if the IS-IS status has been restored; S03. Ping the neighbor's IP address to check if it is reachable; S031. Execute the command "ping xxxx[neighbor IP]". A return "!" indicates that the ping is reachable; a return "..." indicates that the ping is unreachable. S032, Ping test unreachable, prompting IS-IS interruption, peer address unreachable, fault cause located, process ends; S033, Ping test shows reachable, prompting IS-IS peer ping is reachable, proceed to S04; S04. Check if the peer's ARP has been learned; S041. Execute the command "dis arp interface eth". If the output message contains "D", the learning was successful. Other output messages indicate that the learning failed. S042. If learning is successful, the peer's ARP will be learned, and proceed to S05. S043. If learning fails, the peer's ARP will not be learned, and an ARP learning failure message will be displayed. After locating the cause of the fault, the process ends. S05. Check if the configuration area IDs at both ends are consistent; S051. Execute the command "display cur conf IS-IS" on both the local and remote devices to check whether the IS-IS configuration zone IDs on the local and remote devices are consistent. If S052 and IS-IS area IDs match, the check passes and proceeds to S06. S053. The IS-IS configuration area IDs of the local end and the remote end are inconsistent. The cause of the fault has been located and the process ends. S06. Check if the LEVEL levels at both ends are consistent; S061. Execute the command "display IS-IS interface GigabitEthernet0 / 0 / 0 [interconnection interface]" on both the local and remote devices to check whether the IS-IS configuration levels on the local and remote devices are consistent. S062 If the levels at both ends are the same, then proceed to S07; S063, The LEVEL levels at both ends are inconsistent. The cause of the fault has been located, and the process ends. S07. Check if the network types of the interfaces at both ends are the same; S071. Execute the command "display cur interface Eth-Trunk x| include IS-IS" on both the local and remote devices to check if the network types of the IS-IS interfaces on the local and remote devices are the same. S072 If the IS-IS network types of the two-end interfaces are the same, the check passes and proceeds to S08; S073, Inconsistent IS-IS network types at both ends of the interface; the cause of the fault has been identified, and the process ends. S08. Log in to the peer device, which is a neighboring device of the device that received the IS-IS Down alarm. Ping the interconnected IP to see if it is reachable. S081. Execute the command "ping xxxx[local device IP]". A return "!" indicates reachability, and a return "..." indicates unreachability. S082, Ping test unreachable, prompting IS-IS interruption, peer ping local address unreachable, fault cause located, process ends; S083, Ping test results are reachable, proceed to manual processing.

2. The fault location method for intermediate system-to-intermediate system protocol failure according to claim 1, characterized in that, S01 includes: S011. When a device network element experiences a port down alarm and continuously experiences IS-IS down alarms, the IS-IS protocol down is caused by the device port down. S012. Log in to the device that received the IS-IS Down alarm and proceed to S02.

3. The fault location method for intermediate system-to-intermediate system protocol failure according to claim 2, characterized in that, The number of consecutive IS-IS Down alarms in S011 is no less than 3.

4. The fault location method for intermediate system-to-intermediate system protocol failure according to claim 1, characterized in that, The S02 includes: S021. Execute the command "system-view" to enter the system view, execute the command "display IS-IS peer" to view the status of the IS-IS peer; execute the command "display IS-IS interface" to view the IS-IS status on the interface where the IS-IS Down fault occurs; S022. If the IS-IS status is UP, then the IS-IS connection has self-healed during the inspection, the fault has been recovered, and the process ends. S023, IS-IS status not restored, proceed to S03.

5. The fault location method for intermediate system-to-intermediate system protocol failure according to claim 4, characterized in that, The system view in S021 is a specific mode that users enter through the command-line interface, used to configure and manage system-level parameters of device network elements. The system view has the function of accessing the global configuration of device network elements.

6. A fault location device for intermediate system-to-intermediate system protocol failure, characterized in that, The device includes: The network alarm data loading module loads network alarm data including: device port down alarm and IS-IS down alarm, wherein the IS-IS down alarm indicates that the intermediate system to intermediate system protocol has failed. The IS-IS status check module checks whether the IS-IS status has been restored. The ping test module checks if a neighbor's IP address is reachable, including: Executing the command "ping xxxx[neighbor IP]" will return "!" if the ping is reachable, and "...." if the ping is not reachable. Ping test unreachable, indicating IS-IS interruption, peer address unreachable, fault cause located, process ends; Ping test is successful, indicating IS-IS peer ping is successful, and the system enters the peer ARP module for learning. Upon learning the peer's ARP module, check if the peer's ARP has been learned, including: Executing the command "dis arp interface eth" will result in a "D" in the output message, indicating successful learning. Other output messages indicate learning failure. If the learning is successful, the peer's ARP will be learned, and the system will enter the LEVEL consistency module; If learning fails, the peer's ARP will not be learned, and an ARP learning failure message will be displayed. Once the cause of the fault is located, the process will end. The LEVEL consistency module checks whether the LEVEL levels at both ends are consistent, including: Execute the command "display cur conf IS-IS" on both the local and remote devices to check if the IS-IS configuration zone IDs on the local and remote devices are consistent. If the IS-IS area IDs match, the check passes and proceeds to the ID consistency module. The IS-IS configuration area IDs of the local and remote ends are inconsistent. The cause of the fault has been located and the process ends. The ID consistency module checks whether the IDs of the configuration areas at both ends are consistent, including: Execute the command "display IS-IS interface GigabitEthernet0 / 0 / 0 [interconnection interface]" on both the local and remote devices to check whether the IS-IS configuration levels on the local and remote devices are consistent. If the levels at both ends are the same, then proceed to the network type module; The LEVEL levels at both ends are inconsistent, the cause of the fault has been located, and the process ends. The network type module checks whether the network types of the interfaces at both ends are the same, including: Execute the command "display cur interface Eth-Trunk x |include IS-IS" on both the local and remote devices to check if the IS-IS interface network types on the local and remote devices are the same. If the IS-IS network types of the two-end interfaces are the same, the check passes and the device proceeds to the Ping test module on the other end. The IS-IS network types of the two-end interfaces are inconsistent; the cause of the fault has been located, and the process ends. The peer ping test module logs into the peer device, which is a neighboring device of the device that received the IS-IS Down alarm. It pings the interconnecting IP address to check its reachability, including: Executing the command "ping xxxx[local device IP]" will return "!" indicating that the device is reachable, and "...." indicating that it is not reachable. Ping test unreachable, indicating IS-IS interruption, peer ping to local address unreachable, fault cause located, process ends; Ping test successful; transfer to manual processing.

7. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that performs the method according to any one of claims 1-5.

Images