Equipment off-management fault analysis method and system, electronic equipment and storage medium

Abstract

The invention relates to an equipment off-management fault analysis method and system, electronic equipment and a storage medium, and the analysis method comprises the steps: scanning the routing information of equipment in a management region, and constructing a network topology according to the routing information; according to the routing state of each device, determining an abnormal device which is abnormal; and according to the number of the abnormal devices, determining the device out-of-management state, and based on the device out-of-management state, determining the device out-of-management fault position through the position information of the abnormal devices in the network topology. According to the scheme, intelligent diagnosis is carried out on the fault, the equipment off-pipe state is determined according to the number of the abnormal equipment, then the equipment off-pipe fault is positioned according to the position of the abnormal equipment in the network topology based on the equipment off-pipe state, and the purpose of fast troubleshooting is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of network operation and maintenance, and in particular to a method and system for analyzing equipment out-of-control failures, an electronic device, and a storage medium. Background Art

[0002] As operators' network topologies and services become more complex and diversified, the complexity of technology grows exponentially, and network operation and maintenance becomes increasingly complicated and difficult. Operation and maintenance personnel must face a large amount of alarm information generated by various devices, analyze the possible causes of failures, and perform manual troubleshooting, which is time-consuming and labor-intensive, and has low troubleshooting efficiency.

[0003] The existing network management systems and technical means can no longer provide sufficient support for operation and maintenance personnel, resulting in many faults not being discovered and resolved in a timely manner. Faults continue to spread and escalate until they affect the business and customer experience, especially equipment out-of-control failures, which can lead to regional network failures in severe cases. Summary of the invention

[0004] To solve the above problems, the present invention provides a device disconnection fault analysis method, system, electronic device and storage medium. This solution locates the device disconnection fault based on the device disconnection state and the position of the abnormal device in the network topology, so as to achieve the purpose of rapid troubleshooting.

[0005] In order to solve the above technical problems, the present invention provides a method for analyzing equipment disconnection failure in a first aspect, the method comprising:

[0006] Scanning routing information of devices within the management area and building a network topology based on the routing information;

[0007] According to the routing status of each of the devices, determining an abnormal device where an abnormality occurs;

[0008] The device out-of-control state is determined according to the number of the abnormal devices, and based on the device out-of-control state, the device out-of-control fault location is determined through the location information of the abnormal device in the network topology.

[0009] According to a preferred embodiment of the present invention, determining the device disconnection state according to the number of abnormal devices, and determining the device disconnection fault location based on the device disconnection state through the location information of the abnormal device in the network topology includes:

[0010] When the number of abnormal devices is greater than a first preset number, the device out-of-control state is a large-volume device out-of-control state, and the number of abnormal devices belonging to the first-station device in the network topology is determined according to the location information; the first-station device includes: a device directly connected to the data center network;

[0011] If the number of abnormal devices belonging to the first station device is greater than the second preset number, the fault location is determined to be the data center network;

[0012] If the number of abnormal devices belonging to the first station device is not greater than the second preset number, the device disconnection fault location is determined according to the routing information of each abnormal device.

[0013] According to a preferred embodiment of the present invention, if the number of abnormal devices belonging to the first station device is not greater than the second preset number, determining the device disconnection fault location according to the routing information of each abnormal device includes:

[0014] If the number of abnormal devices belonging to the first station device is not greater than the second preset number and is not equal to 0, determine whether each abnormal device has passed through the abnormal device belonging to the first station device according to the routing information of each abnormal device; if so, determine that the abnormal device belonging to the first station device has a disconnection fault;

[0015] If the number of abnormal devices belonging to the first station device is equal to 0, obtaining the first routing information of the abnormal device before the abnormality and the second routing information after the abnormality;

[0016] The fault location of the abnormal device is determined in the network topology according to the first routing information and the second routing information.

[0017] According to a preferred embodiment of the present invention, determining the device disconnection state according to the number of abnormal devices, and determining the device disconnection fault location based on the device disconnection state through the location information of the abnormal device in the network topology includes:

[0018] When the number of abnormal devices is not greater than a first preset number, obtaining current routing information of each abnormal device;

[0019] Determine the node IP of the last hop device that survives in the routing path according to the current routing information;

[0020] When the node IP belongs to a device in the management area, directly log in to the last hop device, and determine the device with the out-of-management failure according to the routing status of the neighbor routing of the last hop device;

[0021] When the node IP does not belong to the equipment in the management area, it is determined that the fault location is the data center network.

[0022] According to a preferred embodiment of the present invention, before determining the device disconnection status according to the number of abnormal devices, and determining the device disconnection fault location based on the device disconnection status through the location information of the abnormal device in the network topology, the analysis method further includes:

[0023] Acquire the alarm data of each abnormal device, analyze the alarm data, and determine whether the alarm data is a flash alarm;

[0024] When the alarm data is a flash alarm, the corresponding abnormal equipment does not have a disconnection failure.

[0025] According to a preferred embodiment of the present invention, the analysis method further comprises:

[0026] Acquire the device status and connectivity relationship of each of the devices in real time;

[0027] When the device state or connectivity relationship of any of the devices changes, the device whose device state or connectivity relationship changes is used as the first update device, and the device associated with the first update device is used as the second update device;

[0028] The routing information of the first updating device and the second updating device is obtained by scanning, and the network topology is updated.

[0029] According to a preferred embodiment of the present invention, the step of using the device associated with the first updating device as the second updating device includes:

[0030] The device communicating with the first update device is obtained in the network topology as a second update device.

[0031] In order to solve the above technical problems, the second aspect of the present invention provides an equipment disconnection fault analysis system, the analysis system comprising:

[0032] A network topology building module, used to scan the routing information of devices in the management area and build a network topology based on the routing information;

[0033] An abnormal device analysis module, used to determine an abnormal device having an abnormality according to the routing status of each of the devices;

[0034] The device disconnection analysis module is used to determine the device disconnection status according to the number of abnormal devices, and based on the device disconnection status, determine the device disconnection fault location through the location information of the abnormal device in the network topology.

[0035] In order to solve the above technical problem, the third aspect of the present invention provides an electronic device, comprising:

[0036] Processor; and

[0037] A memory storing computer executable instructions, wherein when the computer executable instructions are executed, the processor executes the method described in any one of the above embodiments.

[0038] In order to solve the above technical problems, the fourth aspect of the present invention proposes a computer storage medium, wherein the computer storage medium stores one or more programs, and when the one or more programs are executed by a processor, the method described in any one of the above embodiments is implemented.

[0039] Compared with the prior art, the present invention has the following advantages: the present invention obtains the routing information of each device in the management area to construct a corresponding topological network, and then determines the abnormal device according to the routing status of the device, determines the device off-management status by the number of abnormal devices, and based on the device off-management status, determines the device off-management fault location by the position information of the abnormal device in the network topology, which can achieve the purpose of quickly determining and identifying the device off-management fault and intelligently diagnosing the fault, determines the device off-management status by the number of abnormal devices, and then locates the device off-management fault based on the device off-management status by the position of the abnormal device in the network topology, thereby achieving the purpose of rapid troubleshooting.

[0040] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or be understood by implementing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0042] Figure 1 A first flow chart of a method for analyzing a device disconnection failure according to an embodiment of the present disclosure is shown;

[0043] Figure 2 A schematic diagram of a carrier network topology according to an embodiment of the present disclosure is shown;

[0044] Figure 3 A schematic diagram of the operator network topology after removing device B according to an embodiment of the present disclosure is shown;

[0045] Figure 4 A second flow chart of a method for analyzing a device disconnection failure according to an embodiment of the present disclosure is shown;

[0046] Figure 5 A schematic diagram of a network topology of an operator with DCN decoupled from management according to an embodiment of the present disclosure is shown;

[0047] Figure 6 A schematic diagram of an operator network topology when an abnormality occurs in a first station device according to an embodiment of the present disclosure is shown;

[0048] Figure 7 A schematic diagram of a process of determining a device disconnection fault location according to routing information of each abnormal device according to an embodiment of the present disclosure is shown;

[0049] Figure 8 A third flow chart of a method for analyzing a device disconnection failure according to an embodiment of the present disclosure is shown;

[0050] Fig. 9 A schematic diagram of the operator network topology when devices E and F are abnormal according to an embodiment of the present disclosure is shown;

[0051] Fig.10 A block diagram of a device disconnection fault analysis system according to an embodiment of the present disclosure is shown;

[0052] Fig.11 A schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0054] The same reference numerals in the drawings represent the same or similar elements, components or parts, and thus the repeated description of the same or similar elements, components or parts may be omitted below. It should also be understood that although the first, second, third and other attributives representing the numbers may be used herein to describe various devices, elements, components or parts, these devices, elements, components or parts should not be limited by these attributives. In other words, these attributives are only used to distinguish one from another. For example, the first device may also be called the second device, but it does not deviate from the essential technical solution of the present invention. In addition, the terms "and / or" and "and / or" refer to all combinations including any one or more of the listed items.

[0055] See also Figure 1 , Figure 1 This is a flow chart of a method for analyzing a device disconnection failure provided by the present invention. Figure 1 As shown, the method includes:

[0056] S11. Scan the routing information of the devices in the management area, and build a network topology based on the routing information.

[0057] In this embodiment, if Figure 2 As shown, the operator network topology includes the network management system, DCN network and various devices in the management area. DCN network: Data Center Network refers to the network architecture used to connect and manage various devices in the data center. Its main components include core switches, access switches, edge routers, firewalls and security devices, load balancers, etc. In the present invention, it generally refers to the network connecting the network management system and the devices in the management area.

[0058] In this embodiment, routing information refers to information stored in a router or network device that is used to guide the path and direction of data packets transmitted in the network. Network topology refers to the physical layout of various devices interconnected by transmission media. It refers to the specific physical (real) or logical (virtual) arrangement between members that constitute the network.

[0059] In this embodiment, the routing information of devices in the entire management area can be scanned by using the tracert command. After the routing information in each management area is obtained, the network topology of each device is constructed according to the communication relationship of the devices in the routing information.

[0060] In this embodiment, in the network topology, adding or removing a device or changing the fiber connection will cause the routing of the devices associated with it to change. Figure 3 As shown in the figure, after removing device B, the routes of devices G and H will change accordingly. The routing information of devices is not static, but it will not change frequently, so it is necessary to update the routing information of devices regularly. The specific implementation is to subscribe to the changes of devices and fiber connections in the network management system. When a device or fiber connection changes, find the devices associated with it, re-scan the routes of these devices, and obtain new routing information.

[0061] Specifically, the device status and connectivity relationship of each device are obtained in real time; when the device status or connectivity relationship of any device changes, the device whose device status or connectivity relationship has changed is used as the first update device, and the device associated with the first update device is used as the second update device; the routing information of the first update device and the second update device is obtained by scanning, and the network topology is updated. In this embodiment, the device status can be the device status of use, deactivation, removal, addition, change of use purpose, etc., and the connectivity relationship can be a connectivity relationship through IO line connection, bus connection, communication connection and other connection methods. When the status or connectivity relationship of a device changes, this solution uses the changed device and the device that has a connection relationship with the changed device as the update device, vertex scans the routing information of the updated device, so as to update the network topology, complete the update of the network topology more quickly and accurately, and avoid the waste of resources caused by global scanning.

[0062] S12. According to the routing status of each device, determine the abnormal device where the abnormality occurs.

[0063] In this embodiment, the routing status involves multiple aspects, including the physical status of the routing, the network connection status, the software running status, etc. If there is a problem with the physical status and connection status of the device routing, it is impossible to communicate directly with other devices. At this time, it can be determined that the device is abnormal. If there is a problem with the software running status of the device routing, it will generally cause abnormal data transmission or slow data transmission speed. At this time, it can also be determined that the device is abnormal.

[0064] In this embodiment, the network management system can periodically check whether the routes of the devices in the management area are reachable. Once it is found that one or some devices have abnormal communication, an alarm of abnormal device communication is reported.

[0065] S13. Determine the device disconnection status according to the number of abnormal devices, and based on the device disconnection status, determine the device disconnection fault location through the location information of the abnormal device in the network topology.

[0066] In this embodiment, under normal circumstances, most devices are in normal working condition. Once a large number of abnormal devices appear, it can be determined that the actual abnormal situation is more serious. At the same time, the level or level of the abnormal devices is higher. For example, the core switches, access switches, edge routers, firewalls and security devices or load balancers in the data center network are abnormal. At this time, it is necessary to quickly locate the abnormality to solve the network problem.

[0067] In this embodiment, before determining that an abnormal device has a disconnection failure, the alarm data of each abnormal device is obtained, the alarm data is analyzed, and it is determined whether the alarm data is a flash-off alarm; when the alarm data is a flash-off alarm, the corresponding abnormal device has not had a disconnection failure. A flash-off alarm refers to when the interval between the generation time and the clearing time of an alarm is less than a certain value (called the flash-off threshold), the alarm is called a flash-off alarm. In layman's terms, flash-off alarms refer to those alarms that last for a very short time. This type of alarm is usually caused by unstable network links, device interface failures, or other transient problems. Since the flash-off alarm indicates that the device has restored connectivity, at this point, it is no longer analyzed whether the device has a disconnection failure.

[0068] In this embodiment, the device disconnection status is first determined by the number of abnormal devices. The abnormal number standard can be set. Whether a large number of devices are disconnected can be determined by the abnormal number standard and the number of abnormal devices. In this way, a method for determining the location of the device disconnection can be selected to achieve rapid fault location. For example, the device disconnection status can be determined based on the minimum value of the number of abnormal devices when a large number of devices are disconnected in historical data as the abnormal number standard. The number of abnormal devices when a large number of devices are disconnected in historical data can be averaged as the abnormal number standard. The number of nodes can also be determined from the routing information of the longest routing path from the DCN network to each device in the management area, and the number of nodes can be used as the abnormal number standard.

[0069] In this embodiment, after determining the device off-management state, a fault location method corresponding to the device off-management state is selected based on the device off-management state, and the device off-management fault location is determined through the location information of each abnormal device in the network topology; for example, when a large number of devices are off-management, the probability that there is a problem with the routing state of each device is very small, so at this time, it should be that an abnormality has occurred in a device that is connected to multiple devices at the same time, and the fault can be quickly located through the corresponding fault location method.

[0070] In this embodiment, this scheme acquires the routing information of each device in the management area to construct a corresponding topological network, and then determines the abnormal device according to the routing status of the device, determines the device off-management status by the number of abnormal devices, and based on the device off-management status, determines the device off-management fault location by the location information of the abnormal device in the network topology, so as to quickly identify the device off-management fault and perform intelligent diagnosis on the fault, determine the device off-management status by the number of abnormal devices, and then locate the device off-management fault based on the device off-management status by the location of the abnormal device in the network topology, so as to achieve the purpose of rapid troubleshooting.

[0071] See also Figure 4 , Figure 4The second is a flow chart of a method for analyzing a device disconnection failure provided by the present invention. Figure 4 As shown, step S13 method includes:

[0072] S21. When the number of abnormal devices is greater than a first preset number, the device unmanagement state is a large-scale device unmanagement state, and the number of abnormal devices belonging to the first-station devices in the network topology is determined according to the location information; the first-station devices include: devices directly connected to the data center network.

[0073] In this embodiment, the first preset number is the abnormal number standard in the above embodiment, and this solution will not be repeated here.

[0074] In this embodiment, by setting the first preset number, it is determined according to the established standard whether a large number of devices are in the disconnected state, so that different analysis methods can be selected to quickly locate the fault and improve the efficiency of fault handling.

[0075] S22: If the number of abnormal devices belonging to the first station device is greater than a second preset number, it is determined that the fault location is the data center network.

[0076] S23: If the number of abnormal devices belonging to the first station device is not greater than a second preset number, determine the device disconnection fault location according to the routing information of each abnormal device.

[0077] In this embodiment, when there are many abnormal situations in the first-station equipment, and the probability of abnormal situations in the first-station equipment at the same time is low, it can be explained from the side that the data center network is abnormal at this time. Prioritizing the inspection of the data center network connected to the first-station equipment can greatly improve the efficiency of fault processing. Specifically, for example, the second preset number is 2, and the number of first-station equipment included in the disconnected equipment is checked. If the number of disconnected first-station equipment is greater than 2 (based on the first-line troubleshooting experience, it is usually caused by DCN network abnormalities), it is considered to be caused by DCN disconnection. Figure 5 shown.

[0078] If only one first-station device is disconnected, check the historical routing information to see whether the routes of the disconnected devices all pass through this first-station device. If so, it means that the disconnection of the first-station device caused a large number of devices to be disconnected. Figure 6 Specifically, Figure 7 As shown, step S23 includes the following steps:

[0079] S31. If the number of abnormal devices belonging to the first station device is not greater than the second preset number and is not equal to 0, determine whether each abnormal device has passed through the abnormal device belonging to the first station device according to the routing information of each abnormal device; if so, determine that the abnormal device belonging to the first station device has a disconnection failure.

[0080] S32: If the number of abnormal devices belonging to the first station device is equal to 0, obtain the first routing information of the abnormal device before the abnormality and the second routing information after the abnormality.

[0081] S33. Determine a fault location of the abnormal device in the network topology according to the first routing information and the second routing information.

[0082] In this embodiment, when an abnormality occurs in a non-first-station device, any faulty device will cause the device connected to the faulty device and the subsequently connected devices to become disconnected. At this time, two faulty devices are randomly selected for route scanning, and the scanning results are compared with the historical routing information of the two devices to obtain the specific location of the fault and present the diagnosis results to the user. For example, the routing information before the device failure is [ip1, ip2, ip3, ip4...], and the routing scanning result after the failure is: [ip1, ip2]. Please check the network status between ip2 and ip3.

[0083] See also Figure 8 , Figure 8 The third is a flow chart of a method for analyzing a device disconnection failure provided by the present invention. Figure 8 As shown, step S13 method includes:

[0084] S41. When the number of abnormal devices is not greater than a first preset number, obtain current routing information of each abnormal device.

[0085] In this embodiment, the first preset number is the abnormal number standard in the above embodiment, and this solution will not be repeated here.

[0086] S42: Determine the node IP of the last hop device that survives in the routing path according to the current routing information.

[0087] In this embodiment, the surviving last-hop device is the last device in the routing path that can still communicate normally. The node IP refers to the IP address of the node server. In a distributed system, the node IP is the IP address of the node server used to connect to the network, provide data transmission and processing services, and is the unique identifier of the node server.

[0088] S43. When the node IP belongs to a device in the management area, directly log in to the last hop device, and determine the device with the out-of-management failure according to the routing status of the neighbor routing of the last hop device.

[0089] S44. When the node IP does not belong to a device in the management area, it is determined that the fault location is the data center network.

[0090] In this embodiment, the unique identification of the device is used to determine whether the faulty device is within the management area. This can locate the device and allow staff to determine the location of devices that are still working properly.

[0091] In this embodiment, if Fig. 9 As shown in the figure, the route scan is used to scan the unmanaged devices E and F, and the last surviving node IP is found in the scan results. Then, it is determined whether the IP is a device in the management area or a DCN network device. If it is a device in the management area, the last hop device is directly logged in to check whether the neighbor routing of the device is normal, find the abnormal device and present it to the user as a diagnostic result. If the IP does not belong to a device in the management area, it means that the DCN network is abnormal, and the DCN network fault is reported, and the IP is presented to the user as a diagnostic result. Fig. 9 In the network topology shown, the last hop device is device D, and the neighbor node of device D is device C. At this time, both devices D and C are normal, which means that devices E and F are both out-of-control failures. If device D is abnormal and device C is normal, it means that device D is out-of-control failure.

[0092] See also Fig.10 , Fig.10 This is a block diagram of a device disconnection fault analysis system provided by the present invention, such as Fig.10 As shown, the analysis system includes: a network topology construction module 11, an abnormal device analysis module 12 and a device out-of-control analysis module 13.

[0093] In this embodiment, the network topology building module 11 is used to scan the routing information of the devices in the management area and build the network topology according to the routing information.

[0094] In this embodiment, the abnormal device analysis module 12 is used to determine the abnormal device where the abnormality occurs according to the routing status of each device.

[0095] In this embodiment, the device disconnection analysis module 13 is used to determine the device disconnection status according to the number of abnormal devices, and based on the device disconnection status, determine the device disconnection fault location through the location information of the abnormal device in the network topology.

[0096] In this embodiment, the device off-management analysis module 13 is specifically used to determine the number of abnormal devices belonging to the first-station device in the network topology according to the location information when the number of abnormal devices is greater than a first preset number, the device off-management state is a large-scale device off-management state; the first-station device includes: a device directly connected to the data center network; if the number of abnormal devices belonging to the first-station device is greater than a second preset number, the fault location is determined to be the data center network; if the number of abnormal devices belonging to the first-station device is not greater than the second preset number, the device off-management fault location is determined according to the routing information of each abnormal device.

[0097] In this embodiment, the device disconnection analysis module 13 is specifically used to determine whether each abnormal device has passed through the abnormal device belonging to the first station device according to the routing information of each abnormal device if the number of abnormal devices belonging to the first station device is not greater than the second preset number and is not equal to 0; if so, it is determined that the abnormal device belonging to the first station device has a disconnection fault; if the number of abnormal devices belonging to the first station device is equal to 0, obtain the first routing information of the abnormal device before the abnormality and the second routing information after the abnormality; determine the fault location of the abnormal device in the network topology according to the first routing information and the second routing information.

[0098] In this embodiment, the device off-management analysis module 13 is specifically used to obtain the current routing information of each abnormal device when the number of abnormal devices is not greater than the first preset number, which is a non-bulk device off-management state; determine the node IP of the last hop device that survives in the routing path according to the current routing information; when the node IP belongs to a device within the management area, directly log in to the last hop device, and determine the device that has an off-management fault based on the routing status of the neighbor routing of the last hop device; when the node IP does not belong to a device within the management area, determine that the fault location is the data center network.

[0099] In this embodiment, the equipment disconnection analysis module 13 is also used to obtain the alarm data of each abnormal equipment, analyze the alarm data, and determine whether the alarm data is a flash alarm; when the alarm data is a flash alarm, the corresponding abnormal equipment has not experienced a disconnection fault.

[0100] In this embodiment, the network topology construction module 11 is also used to obtain the device status and connectivity relationship of each device in real time; when the device status or connectivity relationship of any device changes, the device whose device status or connectivity relationship changes is used as the first update device, and the device associated with the first update device is used as the second update device; the routing information of the first update device and the second update device is scanned and the network topology is updated.

[0101] In this embodiment, the network topology building module 11 is specifically configured to obtain a device in the network topology that communicates with the first update device as the second update device.

[0102] like Fig.11 As shown, an embodiment of the present invention provides an electronic device, including a processor 1110, a communication interface 1120, a memory 1130 and a communication bus 1140, wherein the processor 1110, the communication interface 1120, and the memory 1130 communicate with each other through the communication bus 1140;

[0103] Memory 1130, used for storing computer programs;

[0104] The processor 1110 is used to implement any of the above analysis methods when executing the program stored in the memory 1130.

[0105] In the electronic device provided by the embodiment of the present invention, the processor 1110 scans the routing information of the devices in the management area by executing the program stored in the memory 1130, and builds a network topology based on the routing information; determines the abnormal devices among the devices according to the routing status of each device; determines the device off-management status according to the number of abnormal devices, and based on the device off-management status, determines the device off-management fault location through the location information of the abnormal device in the network topology.

[0106] The communication bus 1140 mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus 1140 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0107] The communication interface 1120 is used for communication between the above electronic device and other devices.

[0108] The memory 1130 may include a random access memory 1130 (RAM), or may include a non-volatile memory 1130 (non-volatile memory), such as at least one disk memory 1130. Optionally, the memory 1130 may also be at least one storage device located away from the processor 1110.

[0109] The above-mentioned processor 1110 can be a general-purpose processor 1110, including a central processing unit 1110 (CPU), a network processor 1110 (NP), etc.; it can also be a digital signal processor 1110 (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0110] An embodiment of the present invention provides a computer-readable storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors 1110 to implement the analysis method of any of the above embodiments.

[0111] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk SolidStateDisk (SSD)), etc.

[0112] Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A method for analyzing equipment disconnection failure, characterized in that: The analysis method comprises: Scanning routing information of devices within the management area and building a network topology based on the routing information; According to the routing status of each of the devices, determining an abnormal device where an abnormality occurs; The device out-of-control state is determined according to the number of the abnormal devices, and based on the device out-of-control state, the device out-of-control fault location is determined through the location information of the abnormal device in the network topology.

2. The analysis method according to claim 1, characterized in that The determining of the device disconnection state according to the number of abnormal devices, and determining the device disconnection fault location based on the device disconnection state and through the location information of the abnormal device in the network topology, includes: When the number of abnormal devices is greater than a first preset number, the device out-of-control state is a large-volume device out-of-control state, and the number of abnormal devices belonging to the first-station device in the network topology is determined according to the location information; the first-station device includes: a device directly connected to the data center network; If the number of abnormal devices belonging to the first station device is greater than the second preset number, the fault location is determined to be the data center network; If the number of abnormal devices belonging to the first station device is not greater than the second preset number, the device disconnection fault location is determined according to the routing information of each abnormal device.

3. The analysis method according to claim 2, characterized in that If the number of abnormal devices belonging to the first station device is not greater than the second preset number, determining the device disconnection fault location according to the routing information of each abnormal device includes: If the number of abnormal devices belonging to the first station device is not greater than the second preset number and is not equal to 0, determine whether each abnormal device has passed through the abnormal device belonging to the first station device according to the routing information of each abnormal device; if so, determine that the abnormal device belonging to the first station device has a disconnection fault; If the number of abnormal devices belonging to the first station device is equal to 0, obtaining the first routing information of the abnormal device before the abnormality and the second routing information after the abnormality; The fault location of the abnormal device is determined in the network topology according to the first routing information and the second routing information.

4. The analysis method according to claim 2, characterized in that The determining of the device disconnection state according to the number of abnormal devices, and determining the device disconnection fault location based on the device disconnection state and through the location information of the abnormal device in the network topology, includes: When the number of abnormal devices is not greater than the first preset number, it is a non-bulk device out-of-control state, and the current routing information of each abnormal device is obtained; Determine the node IP of the last hop device that survives in the routing path according to the current routing information; When the node IP belongs to a device in the management area, directly log in to the last hop device, and determine the device with the out-of-management failure according to the routing status of the neighbor routing of the last hop device; When the node IP does not belong to the equipment in the management area, it is determined that the fault location is the data center network.

5. The analysis method according to claim 1, characterized in that Before determining the device disconnection status according to the number of abnormal devices, and determining the device disconnection fault location based on the device disconnection status by using the location information of the abnormal device in the network topology, the analysis method further includes: Acquire the alarm data of each abnormal device, analyze the alarm data, and determine whether the alarm data is a flash alarm; When the alarm data is a flash alarm, the corresponding abnormal equipment does not have a disconnection failure.

6. The analysis method according to any one of claims 1 to 5, characterized in that: The analysis method further comprises: Acquire the device status and connectivity relationship of each of the devices in real time; When the device state or connectivity relationship of any of the devices changes, the device whose device state or connectivity relationship changes is used as a first update device, and the device associated with the first update device is used as a second update device; The routing information of the first updating device and the second updating device is obtained by scanning, and the network topology is updated.

7. The analysis method according to claim 6, characterized in that The step of using the device associated with the first update device as the second update device includes: The device communicating with the first update device is obtained in the network topology as a second update device.

8. A device disconnection fault analysis system, characterized in that: The analysis system comprises: A network topology building module, used to scan the routing information of devices in the management area and build a network topology based on the routing information; An abnormal device analysis module, used to determine an abnormal device having an abnormality according to the routing status of each of the devices; The device disconnection analysis module is used to determine the device disconnection status according to the number of abnormal devices, and based on the device disconnection status, determine the device disconnection fault location through the location information of the abnormal device in the network topology.

9. An electronic device, characterized in that: include: processor; as well as A memory storing computer executable instructions which, when executed, cause the processor to perform the method according to any one of claims 1-7.

10. A computer storage medium, characterized in that: in, The computer storage medium stores one or more programs, and when the one or more programs are executed by a processor, the method of any one of claims 1 to 7 is implemented.

Images