Fault root cause location method and device

Abstract

The present application discloses a method and device for locating the root cause of a fault, which belongs to the field of operation and maintenance technology. The method is applied to a management node that manages a service cluster, and the service cluster includes multiple service nodes, and the service nodes are used to implement user services. The method includes: obtaining the networking information of multiple service nodes; when a service cluster fails, obtaining the link status of the links between the multiple service nodes; performing convergence analysis based on the link status and networking information to determine the root cause of the fault. The present application can quickly locate the root cause of the fault, and improves the efficiency of locating the root cause of the fault.

Description

Technical Field

[0001] The present application relates to the field of operation and maintenance technology, and in particular to a method and device for locating the root cause of a fault. Background Art

[0002] A service cluster is used to implement user services and provide services to users. A service cluster includes multiple service nodes. In addition, the scale of a service cluster is usually large, and different service nodes may span multiple service nodes. In the current network operation and maintenance process, if a device in a link fails, it will take a lot of time and manpower to locate the root cause of the failure. In addition, if it takes too long to locate the root cause of the failure, it may also cause more damage to customers.

[0003] Currently, when a link between service nodes fails, the management node will issue an alarm message and indicate the source service node and destination service node in the link in the alarm message. The operation and maintenance personnel will then check the network devices connected to the source service node and the destination service node one by one to determine the root cause of the failure.

[0004] However, the efficiency of locating the root cause of the fault in this method is very low. Summary of the invention

[0005] The present application provides a method and device for locating the root cause of a fault. The present application improves the efficiency of locating the root cause of a fault and reduces the probability of the fault affecting the service. The technical solution provided by the present application is as follows:

[0006] In the first aspect, the present application provides a method for locating the root cause of a fault. The method is applied to a management node that manages a service cluster, where the service cluster includes multiple service nodes, and the service nodes are used to implement user services. The method includes: obtaining networking information of multiple service nodes; when a service cluster fails, obtaining the link status of links between multiple service nodes; performing convergence analysis based on the link status and networking information to determine the root cause of the fault.

[0007] In the fault root cause location method provided in the present application, by performing convergent analysis based on link status and networking information, the fault root cause can be automatically located on a global scale, the fault root cause can be quickly located, the efficiency of locating the fault root cause is improved, and the probability of the fault affecting the service is reduced.

[0008] In one implementation, multiple service nodes access the network through access network devices located at the access layer. Based on the link status and networking information, convergence analysis is performed to determine the root cause of the fault, including: when the link status of the link between the target service node and other service nodes cannot be obtained, or the link status indication from other service nodes is disconnected from the target service node, the target service node is determined as the candidate root cause of the fault; based on the networking information, the first access network device connected to the target service node and the first service node connected to the first access network device are obtained, and the first service node is a service node other than the target service node connected to the first access network device; when the link status indicates that the first service node includes a normal node, the target service node is determined to be the root cause of the fault.

[0009] Furthermore, the access network device accesses the network through an aggregation network device located at the aggregation layer. Then, based on the link status and networking information, aggregation analysis is performed to determine the root cause of the fault, and further includes: when the link status indicates that the first service nodes are all candidate root causes of the fault, based on the networking information, obtaining the first aggregation network device connected to the first access network device and the second service nodes connected to other access network devices connected to the first aggregation network device, the second service nodes being service nodes other than the target service nodes connected to the first aggregation network device; when the link status indicates that the second service nodes include normal nodes, determining that the first access network device is the root cause of the fault.

[0010] Furthermore, the converged network device accesses the network through the core network device located at the core layer. Then, based on the link status and networking information, the converged analysis is performed to determine the root cause of the fault, and further includes: when the link status indicates that the second service nodes are all candidate root causes of the fault, based on the networking information, obtaining the first core network device connected to the first converged network device, and the third service node connected to other converged network devices connected to the first core network device, the third service node being the service node other than the target service node connected to the first core network device; when the link status indicates that the third service node includes a normal node, determining that the first converged network device is the root cause of the fault.

[0011] Otherwise, performing convergence analysis based on the link status and networking information to determine the root cause of the fault also includes: when the link status indicates that all third service nodes are candidate root causes of the fault, determining the first core network device as the root cause of the fault.

[0012] Optionally, the service node may detect the link status of the link between the service nodes connected thereto and send the link status to the management node. The link status of the links between multiple service nodes is obtained, including: receiving the link status of the link between the service node and other service nodes provided by each service node.

[0013] In one implementation, before the management node obtains the link status of the links between multiple service nodes, the management node may also first select a representative service node in the service cluster, so that the service nodes in the service cluster obtain the link status of the links between themselves and each representative service node. The method may also include: the management node determines multiple service nodes to be tested among multiple service nodes, and provides information of multiple service nodes to be tested to each service node, so that each service node obtains the link status of the link between the service node and each service node to be tested. Accordingly, the management node receives the link status of the link between the service node and other service nodes provided by each service node, including: the management node receives the link status of the link between the service node and each service node to be tested provided by each service node.

[0014] By selecting the service node to be tested in the service cluster through the management node, the service node in the service cluster obtains the link status of the link between itself and each service node to be tested. In this way, the service node does not need to obtain the link status of the link between the service node and each other service node in the service cluster, which can reduce the consumption caused by obtaining the link status, reduce the probability of network storms in the service cluster, and reduce the impact of obtaining the link status on the performance of the service cluster. This effect is particularly obvious when the service cluster is large.

[0015] Optionally, the overall network range of all service nodes to be tested in the service cluster can cover the network range of the service cluster. The network range is the transmission range that can be reached through the network. In this way, the overall network range of all service nodes to be tested covers all cabinets and all network segments of the network used by the service cluster, which can ensure the comprehensiveness of the link information obtained and ensure the accurate location of the root cause of the fault.

[0016] In one implementation, the link status is reflected by one or more of the following: the connectivity status and transmission delay of the link. The connectivity status of the link is used to indicate whether the link is connected or disconnected. When the connectivity status of the link indicates that the link is disconnected, the service nodes cannot use the link to transmit data. The transmission delay can reflect the status of the link. When the transmission delay is too large (such as exceeding the expected transmission delay threshold), it is possible that the link is disconnected, or it is possible that the link is connected but the status is poor. At this time, if the service node uses the link to transmit data, the service timeliness of the service node cannot be met, and it will also cause the service cluster to fail. Therefore, the link status can be reflected through the transmission delay of the link.

[0017] In the second aspect, the present application provides a device for locating the root cause of a fault. The device is applied to a management node that manages a service cluster, and the service cluster includes multiple service nodes, and the service nodes are used to implement user services. The device includes: an acquisition module, which is used to obtain the networking information of multiple service nodes; the acquisition module is also used to obtain the link status of the links between the multiple service nodes when a service cluster fails; a processing module is used to perform convergence analysis based on the link status and networking information to determine the root cause of the fault.

[0018] Optionally, multiple service nodes access the network through an access network device located at the access layer. The processing module is specifically used to: determine the target service node as a candidate fault root cause when the link status of the link between the target service node and other service nodes cannot be obtained, or the link status indication from other service nodes is disconnected from the target service node; based on the networking information, obtain the first access network device connected to the target service node, and the first service node connected to the first access network device, the first service node is a service node other than the target service node connected to the first access network device; when the link status indicates that the first service node includes a normal node, determine the target service node as the fault root cause.

[0019] Optionally, the access network device accesses the network through an aggregation network device located at the aggregation layer. The processing module is specifically used to: when the link status indicates that the first service nodes are all candidate root causes of the fault, based on the networking information, obtain the first aggregation network device connected to the first access network device, and the second service nodes connected to other access network devices connected to the first aggregation network device, where the second service nodes are service nodes other than the target service nodes connected to the first aggregation network device; when the link status indicates that the second service nodes include normal nodes, determine that the first access network device is the root cause of the fault.

[0020] Optionally, the converged network device accesses the network through a core network device located at the core layer. The processing module is specifically used to: when the link status indicates that the second service nodes are all candidate root causes of the fault, based on the networking information, obtain the first core network device connected to the first converged network device, and the third service node connected to other converged network devices connected to the first core network device, the third service node being the service node other than the target service node connected to the first core network device; when the link status indicates that the third service node includes a normal node, determine that the first converged network device is the root cause of the fault.

[0021] Alternatively, when the link status indicates that all third service nodes are candidate root causes of the fault, the first core network device is determined to be the root cause of the fault.

[0022] Optionally, the acquisition module is specifically used to: receive the link status of the link between each service node and other service nodes provided by each service node.

[0023] Optionally, the acquisition module is specifically used to: determine multiple service nodes to be tested among multiple service nodes; provide information of multiple service nodes to be tested to each service node, so that each service node obtains the link status of the link between the service node and each service node to be tested; receive the link status of the link between the service node and each service node to be tested provided by each service node.

[0024] Optionally, the network ranges of the multiple service nodes to be tested cover the network range of the service cluster.

[0025] Optionally, the link status is reflected by one or more of the following: connectivity status and transmission delay of the link.

[0026] In a third aspect, the present application provides a computing device including a memory and a processor, wherein the memory stores program instructions, and the processor runs the program instructions to execute the method provided in the first aspect of the present application and any possible implementation thereof.

[0027] In a fourth aspect, the present application provides a computer cluster comprising at least one computing device, each computing device comprising a processor and a memory, the processor of at least one computing device being used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the method provided in the first aspect of the present application and any possible implementation thereof.

[0028] In a fifth aspect, the present application provides a computer-readable storage medium, which is a non-volatile computer-readable storage medium, and the computer-readable storage medium includes program instructions. When the program instructions are executed on a computing device, the computing device executes the method provided in the first aspect of the present application and any possible implementation thereof.

[0029] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method provided in the first aspect of the present application and any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 It is a schematic diagram of an implementation environment involved in a fault root cause location method provided in an embodiment of the present application;

[0031] Figure 2 It is a schematic diagram of an implementation environment involved in another fault root cause location method provided in an embodiment of the present application;

[0032] Figure 3 This is a process diagram of a method for locating the root cause of a fault provided by an embodiment of the present application;

[0033] Figure 4 It is a schematic diagram of an implementation environment involved in another fault root cause location method provided in an embodiment of the present application;

[0034] Figure 5 is a flow chart of another fault root cause location method provided by an embodiment of the present application;

[0035] Figure 6 This is a flowchart provided by an embodiment of the present application in which a management node performs convergence analysis based on link status and networking information to determine the root cause of a fault;

[0036] Figure 7 It is a visual schematic diagram of a management node performing convergence analysis based on link status and networking information provided by an embodiment of the present application;

[0037] Figure 8 It is a visual schematic diagram of another management node performing convergence analysis based on link status and networking information provided by an embodiment of the present application;

[0038] Fig. 9 It is a visual schematic diagram of another management node performing convergence analysis based on link status and networking information provided by an embodiment of the present application;

[0039] Fig.10 It is a visual schematic diagram of another management node performing convergence analysis based on link status and networking information provided by an embodiment of the present application;

[0040] Fig.11 is a schematic diagram of a fault root cause locating device provided in an embodiment of the present application;

[0041] Fig.12 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0042] Fig.13 It is a structural diagram of a computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0044] To facilitate understanding, the technology and background involved in the embodiments of the present application are first explained below.

[0045] The service cluster is used to implement the user's business and provide services to the user. The service cluster includes multiple service nodes. The service cluster can be deployed in a distributed manner. For example, the service cluster can be a distributed storage cluster. The distributed storage cluster is used to provide distributed storage services. The distributed storage service is provided by one or more storage pools, each of which is composed of one or more storage servers. The storage pool abstracts the hard disks on these storage servers into a unified storage space for users to use. Usually, a distributed storage cluster has a management platform, which is used to manage the distributed storage cluster. A client is installed on each storage server, which communicates with the management platform through the client. In addition, in an embodiment of the present application, the service cluster can be a cloud service cluster.

[0046] The scale of a service cluster is usually large, and different service nodes may span multiple service nodes. During the operation and maintenance process, if a device in the link of the service cluster fails, it will take a lot of time and manpower to locate the root cause of the failure. Moreover, if it takes too long to locate the root cause of the failure, it may also cause more damage to customers.

[0047] At present, when a link between service nodes fails, the management node will issue an alarm message and indicate the source service node and the destination service node in the link in the alarm message. Then the operation and maintenance personnel will check the network devices connected to the source service node and the destination service node one by one to determine the root cause of the failure. For example, according to the network topology of the service cluster, according to the Internet protocol (IP) addresses of the source service node and the destination service node, check the switches and other devices connected to the source server and the destination server to determine the root cause of the failure. Among them, the network topology refers to the specific physical (i.e. real) or logical (i.e. virtual) network arrangement between the members that constitute the network.

[0048] However, the efficiency of locating the root cause of the fault in this method is very low.

[0049] The embodiment of the present application provides a method for locating the root cause of a fault. The method can be applied to a management node that manages a service cluster. The service cluster includes multiple service nodes. The service node is used to implement user services. The method includes: obtaining networking information of multiple service nodes; when a service cluster fails, obtaining the link status of the links between the multiple service nodes; performing convergence analysis based on the link status and networking information to determine the root cause of the fault.

[0050] In the fault root cause location method, by performing convergence analysis based on link status and networking information, the fault root cause can be automatically located on a global scale, the fault root cause can be quickly located, the efficiency of locating the fault root cause is improved, and the probability of the fault affecting the service is reduced.

[0051] Figure 1 FIG. 1 is a schematic diagram of an implementation environment involved in a method for locating the root cause of a fault provided in an embodiment of the present application. Figure 1 As shown, the implementation environment includes: a management node 10 and a service cluster. The service cluster includes multiple service nodes 20. The service node 20 is used to implement user services. The management node 10 is used to locate the root cause of the fault in the service cluster using the fault root cause location method provided in the embodiment of the present application. For example, the management node 10 is used to obtain the networking information of the service node 20, and, when a fault occurs in the service cluster, obtain the link status of the links between the multiple service nodes 20, and perform convergence analysis based on the link status and networking information to determine the root cause of the fault.

[0052] The management node 10 can establish a communication connection with the service node 20 in the service cluster. For example, the management node 10 and the service node 20 can establish a communication connection through a network. Optionally, the network can be a local area network, the Internet, or other networks, which is not limited in the embodiments of the present application.

[0053] Optionally, the management node 10 may be a computing device with computing functions. In one embodiment, the management node 10 may be a server. The server may be a single server, or a server cluster consisting of a plurality of servers, or a cloud computing service center. A large number of basic resources owned by a cloud service provider are deployed in the cloud computing service center. For example, computing resources, storage resources, and network resources are deployed in the cloud computing service center. The cloud computing service center may utilize the large number of basic resources to implement the method for locating the root cause of a fault provided in the embodiment of the present application.

[0054] When the service node 20 is implemented by a cloud computing service center, the function implemented by the fault root cause location method provided in the embodiment of the present application can be abstracted by the cloud service provider into a fault root cause location cloud service on the cloud platform, and the cloud platform can use the resources in the cloud computing center to provide the fault root cause location cloud service to users. After the user purchases the fault root cause location cloud service on the cloud platform, the fault root cause location cloud service can be used to locate the fault root cause for the user's service cluster.

[0055] Alternatively, when the service node 20 is implemented by a cloud computing service center, the function implemented by the fault root cause location method provided in the embodiment of the present application can also be provided as an additional service of other cloud services. For example, when the service cluster is a distributed storage cluster, and the distributed storage cluster is used to provide storage cloud services, the fault root cause location cloud service provided in the embodiment of the present application can be provided as an additional service of the storage cloud service, that is, the fault root cause location method is used to locate the root cause of the storage cloud service to ensure the service quality of the storage cloud service and improve the user experience.

[0056] Optionally, the cloud platform can be a cloud platform of a central cloud, a cloud platform of an edge cloud, or a cloud platform including a central cloud and an edge cloud, which is not specifically limited in the embodiments of the present application. Moreover, in the implementation environment provided in the embodiments of the present application, the service node 20 can also be implemented through other resource platforms other than the cloud platform, which is not specifically limited in the embodiments of the present application. At this time, the service node 20 can be implemented through resources in other resource platforms and provide relevant services to users.

[0057] In the embodiments of the present application, Figure 2 As shown, the management node 10 may belong to a service cluster, that is, the service cluster includes the management node 10. At this time, the management node 10 can not only locate the root cause of the fault in the service cluster, but also manage the service nodes 20 in the service cluster. For example, the management node 10 is used to schedule tasks for the service nodes 20. The management node 10 records the relevant information of all service nodes 20 in the service cluster.

[0058] Or, if Figure 1 As shown, the management node 10 may not belong to the service cluster, that is, the service cluster does not include the management node 10. In one implementation, the management node 10 may be an operation and maintenance platform independent of the service cluster. For example, the operation and maintenance platform can perform operation and maintenance management for the entire data center, and the service cluster can be deployed in an availability zone (AZ) of the data center. At this time, the management node 10 can also locate the root cause of other clusters or systems. For example, when the function implemented by the fault root cause location method provided in the embodiment of the present application is provided as an additional service of other cloud services, since the cloud platform can provide a variety of cloud services, the fault root cause location method can be used to locate the root cause of all cloud services provided by the cloud platform.

[0059] Optionally, when performing convergence analysis based on link status and networking information to determine the root cause of the fault, the management node 10 may also visualize the process. Figure 3As shown, after the management node 10 obtains the networking information of multiple service nodes 20 and the link status of the links between the multiple service nodes 20, when performing convergence analysis, the convergence analysis process can be displayed in real time on the display interface of the management node 10 for the user to view.

[0060] In addition, the service nodes 20 in the service cluster are usually connected through a network. When a service cluster fails, it may be that the service node 20 fails or the link between the service nodes 20 fails. Figure 4 As shown, the implementation scenario may also include: an access switch 30, an aggregation switch 40 and a core switch 50. It should be noted that: Figure 4 This is only an example of the connection between the service nodes 20. The connection method between the service nodes 20 may change according to the application requirements of different scenarios, and the embodiments of the present application do not limit this. And the way to achieve connection between the service nodes 20 may also change according to the application scenario. For example, the network equipment between the service nodes 20 may not only include switches, but also routers or optical network terminals (optical network termination, ONT, also known as optical modem), etc. For another example, the access switch 30 can be transformed into other types of access network devices located at the access layer, the aggregation switch 40 can be transformed into other types of aggregation network devices located at the aggregation layer, and the core switch 50 can be transformed into other types of core network devices located at the core layer.

[0061] It should be understood that the above content is an exemplary description of the application scenario of the fault root cause locating method provided in the embodiment of the present application, and does not constitute a limitation on the application scenario of the fault root cause locating method. A person of ordinary skill in the art can know that as business needs change, its application scenario can be adjusted according to application needs, and the embodiment of the present application does not list them one by one.

[0062] The following is an explanation of the fault root cause location method provided in the embodiment of the present application. Figure 5 As shown, the fault root cause location method includes the following steps:

[0063] Step 501: The management node obtains networking information of multiple service nodes.

[0064] The networking information of the service node is used to indicate the networking state and networking mode of the service node. In an implementable manner, the networking information of the service node can be represented by the network topology of the service node.

[0065] Step 502: When a service cluster fails, the management node obtains the link status of links between multiple service nodes.

[0066] The link status of the link between the service nodes will affect the data transmission process between the service nodes. When the link is normal, data can be transmitted normally between the service nodes. When the link is abnormal, the data transmission process between the service nodes will be affected. In one implementation, the link status is reflected by one or more of the following: the connectivity status and transmission delay of the link. The connectivity status of the link is used to indicate whether the link is connected or disconnected. When the connectivity status of the link indicates that the link is disconnected, the service nodes cannot use the link to transmit data. The transmission delay can reflect the status of the link. When the transmission delay is too large (such as exceeding the expected transmission delay threshold), it is possible that the link is disconnected, or it is possible that the link is connected but the status is poor. At this time, if the service node uses the link to transmit data, the service timeliness of the service node cannot be met, and the service cluster will also fail. Therefore, the link status can be reflected by the transmission delay of the link. Among them, when the service node has multiple ports, the link status of the link between the service nodes is the link status of the link between the ports currently used by the service node. For example, when the service node has a primary port and a backup port and the service node currently uses the primary port to implement a service, the link state of the link between the service nodes is the link state of the link between the primary ports of the service nodes.

[0067] Optionally, the management node obtains the link status of the links between the multiple service nodes, including: receiving the link status of the links between the service node and other service nodes provided by each service node. The service node can detect the link status of the links between the service nodes connected to it, and send the link status to the management node. For example, the service node can detect the link status of the links between it and other service nodes through a ping command. Alternatively, the service node can also detect the link status of the links between it and other service nodes through other methods, which is not specifically limited in the embodiments of the present application.

[0068] In one implementation, before the management node obtains the link status of the link between multiple service nodes, the management node may also select a representative service node in the service cluster so that the service nodes in the service cluster obtain the link status of the link between themselves and each representative service node. Then the method may also include: the management node determines multiple service nodes to be tested among multiple service nodes, and provides information of multiple service nodes to be tested to each service node, so that each service node obtains the link status of the link between the service node and each service node to be tested. Correspondingly, the management node receives the link status of the link between the service node and other service nodes provided by each service node, including: the management node receives the link status of the link between the service node and each service node to be tested provided by each service node. Among them, in addition to providing the information of multiple service nodes to be tested to the service node, the management node may also send an instruction to the service node, which instructs the service node to obtain the link status of the link between the service node and each service node to be tested. Alternatively, the management node may not send the instruction to the service node, and the instruction may be implemented in other ways. For example, the management node and the service node may pre-agree that when the management node provides the service node with information of the service node to be tested, the service node needs to obtain the link status of the link between the service node and each service node to be tested, and send the obtained link status to the management node.

[0069] In addition, there are multiple implementation methods for the service node to provide the management node with the link status of the link between the service node and each service node to be tested. For example, after the service node obtains the link status of the link between the service node and each service node to be tested, the link status can be output to the log, and the management node can obtain the link status from the log. Alternatively, the implementation scenario of the fault root cause location method provided in the embodiment of the present application may also include a collection node, which is used to obtain the link status from the log and provide the link status to the management node. In addition, after obtaining the information for indicating the link status, the management node can also perform operations such as data cleaning (such as format conversion) on the information so that the management node can parse the information.

[0070] Optionally, the overall network range of all service nodes to be tested in the service cluster can cover the network range of the service cluster. The network range is the transmission range that can be reached through the network. In this way, the overall network range of all service nodes to be tested covers all cabinets and all network segments of the network used by the service cluster, which can ensure the comprehensiveness of the link information obtained and ensure the accurate location of the root cause of the fault.

[0071] When the service cluster is large in scale, if each service node obtains the link status for each other service node in the service cluster, this will cause a network storm in the service cluster and affect the performance of the service cluster. The management node selects the service node to be tested in the service cluster, so that the service node in the service cluster obtains the link status of the link between itself and each service node to be tested. In this way, there is no need for the service node to obtain the link status of the link between the service node and each other service node in the service cluster, which can reduce the consumption caused by obtaining the link status, reduce the probability of network storms in the service cluster, and reduce the impact of obtaining the link status on the performance of the service cluster. This effect is particularly obvious when the service cluster is large in scale.

[0072] Step 503: The management node performs convergence analysis based on the link status and networking information to determine the root cause of the fault.

[0073] In the network, service nodes in the service cluster access the network through access network devices located in the access layer, access network devices access the network through convergence network devices located in the convergence layer, and convergence network devices access the network through core network devices located in the core layer. When determining the root cause of the fault, a convergence analysis can be performed on the network devices that provide network connections for the service nodes. In one implementation, Figure 6 As shown in the figure, based on the link status and networking information, the convergence analysis is performed to determine the root cause of the fault, which may include:

[0074] Step 5031: When the link status of the link between the target service node and other service nodes cannot be obtained, or the link status from other service nodes indicates a disconnection with the target service node, the management node determines the target service node as a candidate fault root cause.

[0075] Failure to obtain the link status of the link between the target service node and other service nodes means that the management node has not received information indicating the link status of the link between the target service node and other service nodes. This may be because the target service node is disconnected from the network, or the target service node cannot collect link information between it and other service nodes. In either case, it indicates that the target service node cannot perform network transmission. However, the target service node cannot perform network transmission because there is a problem with the target service node itself, or there may be a problem with the network connected to the target service node. At this time, the target service node can be marked as a candidate root cause of the fault to further determine whether the target service node is the root cause of the fault.

[0076] Step 5032: The management node obtains the first access network device connected to the target service node and the first service node connected to the first access network device based on the networking information. The first service node is a service node other than the target service node connected to the first access network device.

[0077] After determining that the target service node is a candidate root cause of the fault, the state of the network device that provides the network to the target service node can be used for judgment to further determine whether the target service node is the root cause of the fault. Since the service nodes in the service cluster all access the network through access network devices located at the access layer, it is possible to first determine whether the target service node is the root cause of the fault based on the link state of the service node connected to the first access network device connected to the target service node. Prior to this, the first access network device connected to the target service node and the first service node connected to the first access network device can be obtained. In one implementation method, the first access network device connected to the target service node and the first service node connected to the first access network device can be determined based on the networking information of the service nodes in the service cluster.

[0078] Step 5033: When the link status indicates that the first service node includes a normal node, the management node determines that the target service node is the root cause of the fault.

[0079] After determining the first access network device connected to the target service node and the first service node connected to the first access network device, the link status of all the first service nodes connected to the first access network device can be obtained, and whether the link of the first service node is normal can be determined based on the link status of each first service node. When the link of the first service node is normal, it means that the first service node can transmit data through the link, and the first service node is a normal node. In addition, if the first access network device is the root cause of the fault, all the first service nodes connected to the first access network device cannot work normally. Therefore, when the link status indicates that there is a normal node among all the first service nodes connected to the first access network device, it can be determined that the first access network device is in a normal state, and then it can be determined that there is a problem with the target service node itself, that is, the target service node is determined to be the root cause of the fault. At this time, the fault occurring in the service cluster can be called a service node fault.

[0080] Optionally, when performing convergence analysis based on link status and networking information to determine the root cause of the fault, the management node can also visualize the process. In one implementation, the management node can visualize at the cluster granularity. For example, Figure 7 As shown, in step 5033, the current candidate fault root cause is the target service node, then the management node can display at least the target service node and the access network device ( Figure 7 , representing the access switch 30), and all first service nodes connected through the access network device. Figure 7 The black filled dots are service nodes that are determined as candidate root causes of faults, and the white filled dots are service nodes that are not determined as candidate root causes of faults. Figure 7 It can be known that if there is a normal node among all the first service nodes connected to the first access network device, then it can be determined that the target service node is the root cause of the fault.

[0081] Step 5034: When the link status indicates that the first service nodes are all candidate root causes of the fault, the management node obtains, based on the networking information, the first aggregation network device connected to the first access network device and the second service nodes connected to other access network devices connected to the first aggregation network device, where the second service nodes are service nodes other than the target service node connected to the first aggregation network device.

[0082] Since the probability of all service nodes connected to the same access network device failing at the same time is low, when the link status indicates that all first service nodes connected to the first access network device are candidate root causes of the failure, it can be determined that the first access network device or the network device providing the network to the first access network device has failed. The management node can then obtain the first aggregation network device connected to the first access network device and the second service nodes connected to other access network devices connected to the first aggregation network device based on the networking information, so as to determine the root cause of the failure based on them.

[0083] Step 5035: When the link status indicates that the second service node includes a normal node, the management node determines that the first access network device is the root cause of the fault.

[0084] After determining the first aggregation network device connected to the first access network device, and all the second service nodes connected to the first aggregation network device, the link status of all the second service nodes connected to the first aggregation network device can be obtained, and whether the link of the second service node is normal can be determined based on the link status of each second service node. When the link of the second service node is normal, it means that the second service node can transmit data through the link, and the second service node is a normal node. And, if the first aggregation network device is the root cause of the fault, all the second service nodes connected to the first aggregation network device cannot work normally. Therefore, when the link status indicates that there is a normal node among all the second service nodes connected to the first aggregation network device, it can be determined that the first aggregation network device is in a normal state, and then it can be determined that there is a problem with the first access network device itself, that is, the first access network device is determined to be the root cause of the fault. At this time, the fault occurring in the service cluster can be called an access network device fault.

[0085] like Figure 8 As shown, in step 5035, the current candidate fault root is the first access network device ( Figure 830), the management node can display at least the first access network device, the service node connected to the first access network device, the first aggregation network device, and the service node connected to the first aggregation network device according to the topology diagram. Figure 8 The aggregation switch 40 is connected to all the second service nodes. Figure 8 The black filled dots are service nodes that are determined as candidate root causes of faults, and the white filled dots are service nodes that are not determined as candidate root causes of faults. Figure 8 It can be known that if there is a normal node among all the second service nodes connected to the first aggregation network device, it can be determined that the first access network device is the root cause of the fault.

[0086] Step 5036: When the link status indicates that the second service nodes are all candidate root causes of the fault, the management node obtains the first core network device connected to the first aggregation network device, and the third service node connected to other aggregation network devices connected to the first core network device based on the networking information. The third service node is a service node other than the target service node connected to the first core network device.

[0087] Since the probability of all service nodes connected to the same converged network device failing at the same time is low, when the link status indicates that all second service nodes connected to the first converged network device are candidate root causes of the failure, it can be determined that the first converged network device or the network device providing the network to the first converged network device has failed. The management node can then obtain the first core network device connected to the first converged network device and the third service nodes connected to other converged network devices connected to the first core network device based on the networking information, so as to determine the root cause of the failure based on them.

[0088] Step 5037: When the link status indicates that the third service node includes a normal node, the management node determines that the first aggregation network device is the root cause of the fault.

[0089] After determining the first core network device connected to the first aggregation network device, and all the third service nodes connected to the first core network device, the link status of all the third service nodes connected to the first core network device can be obtained, and whether the link of the third service node is normal can be determined according to the link status of each third service node. When the link of the third service node is normal, it means that the third service node can transmit data through the link, and the third service node is a normal node. In addition, if the first core network device is the root cause of the fault, all the third service nodes connected to the first core network device cannot work normally. Therefore, when the link status indicates that there is a normal node among all the third service nodes connected to the first core network device, it can be determined that the first core network device is in a normal state, and then it is determined that the first aggregation network device itself has a problem, that is, the first aggregation network device is determined to be the root cause of the fault. At this time, the fault in the service cluster can be called an aggregation network device fault.

[0090] like Fig. 9 As shown, in step 5037, the current candidate fault root is the first aggregation network device ( Fig. 9 The management node can display at least the first aggregation network device and the access network device ( Fig. 9 , access switch 30), service node, first core network device ( Fig. 9 , wherein the core switch 50 is a core switch, and all third service nodes connected through the first core network device. Fig. 9 The black filled dots are service nodes that are determined as candidate root causes of faults, and the white filled dots are service nodes that are not determined as candidate root causes of faults. Fig. 9 It can be known that if there is a normal node among all the third service nodes connected to the first core network device, it can be determined that the first aggregation network device is the root cause of the fault.

[0091] Step 5038: When the link status indicates that all third service nodes are candidate root causes of the fault, the management node determines that the first core network device is the root cause of the fault.

[0092] Since the probability of all service nodes connected to the same core network device failing at the same time is low, when the link status indicates that all third service nodes connected to the first core network device are candidate root causes of the failure, it can be determined that the first core network device has failed, that is, the first core network device is determined to be the root cause of the failure. At this time, the failure of the service cluster can be called a core network device failure. Among them, the impact of service node failure, access network device failure, aggregation network device failure and core network device failure increases in turn.

[0093] It should be noted that the above steps 5031 to 5038 are examples of the implementation process of determining the root cause of the fault by performing convergence analysis based on the link status and networking information, and are not used to limit its implementation method. Under different application requirements, its implementation method can be appropriately changed. For example, after determining that a device in a network layer is a candidate root cause of the fault, other service nodes connected to the upper-level network device connected to the candidate root cause of the fault can be obtained. Then, a first specified number of other service nodes and a second specified number of other service nodes are selected from all other service nodes in a normal state, and a third specified number of service nodes are selected from the service nodes of the candidate root cause of the fault, and then the first specified number of other service nodes are used as destination nodes, and the second specified number of other service nodes and the third specified number of service nodes are used as source nodes, and then the link state between each destination node and each source node is determined, and whether the candidate root cause of the fault is the root cause of the fault is determined according to the logic of the above steps 5031 to 5038. By selecting a specified number of service nodes and other service nodes and determining the root cause of the fault according to the link status between the selected service nodes and other service nodes, the number of convergence analysis processes required can be reduced, further improving the efficiency of locating the root cause of the fault.

[0094] Among them, when the candidate fault root cause is a service node, the service node of the candidate fault root cause is the service node. When the candidate fault root cause is a network device that provides a network to the service node, the service node of the candidate fault root cause is a service node connected to the network device. The hierarchy of the service node and the network device that provides the network for it increases in sequence according to the increase of the logical distance to the service node. For example, for the service node, access network device, aggregation network device and core network device, since the logical distances of the service node, access network device, aggregation network device and core network device to the service node increase in sequence, the hierarchy of the service node, access network device, aggregation network device and core network device increases in sequence.

[0095] For example, Fig.10 As shown, assuming that the aggregation network device ( Fig.10 The aggregation switch 40 in the figure is a candidate fault root cause, and the core network device ( Fig.10 Then, a first specified number of ( Fig.10 1) other service nodes and a second specified number ( Fig.10 1) other service nodes, and select a third specified number ( Fig.102) service nodes, and then the first specified number of other service nodes are used as destination nodes, and the second specified number of other service nodes and the third specified number of service nodes are used as source nodes, and then the link state between each destination node and each source node is determined ( Fig.10 Y on the dotted arrow indicates that the link status is normal, and N indicates that the link status is abnormal), and according to the logic of the above steps 5031 to 5038, it is determined whether the aggregation network device is the root cause of the fault.

[0096] To summarize, in the fault root cause location method provided in the embodiment of the present application, by performing convergent analysis based on link status and networking information, the fault root cause can be automatically located on a global scale, the fault root cause can be quickly located, the efficiency of locating the fault root cause is improved, and the probability of the fault affecting the service is reduced.

[0097] It should be noted that the sequence of steps of the fault root cause location method provided in the embodiment of the present application can be appropriately adjusted, and the steps can be increased or decreased accordingly according to the situation. Any technician familiar with the technical field can easily think of a change within the technical scope disclosed in this application, which should be included in the protection scope of this application, so it will not be repeated.

[0098] The above describes the fault root cause location method of the embodiment of the present application. Corresponding to the above method, the embodiment of the present application also provides a fault root cause location device. Fig.11 Schematic diagram of a fault root cause location device provided in an embodiment of the present application. Fig.11 As shown in the following multiple modules, the Fig.11 The fault root cause location device shown can perform the above Figure 5 All or part of the operations shown. It should be understood that the device may include more additional modules than the modules shown or omit some of the modules shown, and the embodiments of the present application are not limited to this. The fault root cause location device is applied to a management node that manages a service cluster, and the service cluster includes multiple service nodes, which are used to implement user services. Fig.11 As shown, the fault root cause locating device 110 includes:

[0099] The acquisition module 1101 is used to acquire the networking information of multiple service nodes.

[0100] The acquisition module 1101 is further configured to acquire the link status of links between multiple service nodes when a service cluster fails.

[0101] The processing module 1102 is used to perform convergence analysis based on the link status and networking information to determine the root cause of the fault.

[0102] Optionally, multiple service nodes access the network through an access network device located at the access layer. The processing module 1102 is specifically used to: determine the target service node as a candidate fault root cause when the link status of the link between the target service node and other service nodes cannot be obtained, or the link status from other service nodes indicates that the link is disconnected from the target service node; based on the networking information, obtain the first access network device connected to the target service node, and the first service node connected to the first access network device, the first service node is a service node other than the target service node connected to the first access network device; when the link status indicates that the first service node includes a normal node, determine the target service node as the fault root cause.

[0103] Optionally, the access network device accesses the network through an aggregation network device located at the aggregation layer. The processing module 1102 is specifically used to: when the link status indicates that the first service nodes are all candidate root causes of the fault, based on the networking information, obtain the first aggregation network device connected to the first access network device, and the second service nodes connected to other access network devices connected to the first aggregation network device, where the second service nodes are service nodes other than the target service nodes connected to the first aggregation network device; when the link status indicates that the second service nodes include normal nodes, determine that the first access network device is the root cause of the fault.

[0104] Optionally, the converged network device accesses the network through a core network device located at the core layer. The processing module 1102 is specifically used to: when the link status indicates that the second service nodes are all candidate root causes of the fault, based on the networking information, obtain the first core network device connected to the first converged network device, and the third service node connected to other converged network devices connected to the first core network device, the third service node being the service node other than the target service node connected to the first core network device; when the link status indicates that the third service node includes a normal node, determine that the first converged network device is the root cause of the fault.

[0105] Alternatively, when the link status indicates that all third service nodes are candidate root causes of the fault, the first core network device is determined to be the root cause of the fault.

[0106] Optionally, the acquisition module 1101 is specifically configured to: receive the link status of the link between each service node and other service nodes provided by each service node.

[0107] Optionally, the acquisition module 1101 is specifically used to: determine multiple service nodes to be tested among multiple service nodes; provide information of multiple service nodes to be tested to each service node, so that each service node obtains the link status of the link between the service node and each service node to be tested; and receive the link status of the link between the service node and each service node to be tested provided by each service node.

[0108] Optionally, the network ranges of the multiple service nodes to be tested cover the network range of the service cluster.

[0109] Optionally, the link status is reflected by one or more of the following: connectivity status and transmission delay of the link.

[0110] To sum up, in the fault root cause locating device provided in the embodiment of the present application, by performing convergent analysis based on link status and networking information, the fault root cause can be automatically located on a global scale, the fault root cause can be quickly located, the efficiency of locating the fault root cause is improved, and the probability of the fault affecting the service is reduced.

[0111] Among them, both the acquisition module 1101 and the processing module 1102 can be implemented by software or by hardware. Exemplarily, the implementation of the acquisition module 1101 is described below by taking the acquisition module 1101 as an example. Similarly, the implementation of the processing module 1102 can refer to the implementation of the acquisition module 1101.

[0112] As an example of a software functional unit, the acquisition module 1101 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the acquisition module 1101 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region (region) or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including a data center or multiple data centers with similar geographical locations. Among them, usually a region may include multiple AZs.

[0113] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

[0114] As an example of a hardware functional unit, the acquisition module 1101 may include at least one computing device, such as a server, etc. Alternatively, the acquisition module 1101 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0115] The multiple computing devices included in the acquisition module 1101 can be distributed in the same region or in different regions. The multiple computing devices included in the acquisition module 1101 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the acquisition module 1101 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0116] It should be noted that, in other embodiments, any one of the acquisition module 1101 and the processing module 1102 can be used to execute any step in the fault root cause location method. The steps that the acquisition module 1101 and the processing module 1102 are responsible for implementing can be specified as needed, and the acquisition module 1101 and the processing module 1102 respectively implement different steps in the fault root cause location method to achieve all the functions of the fault root cause location device.

[0117] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding contents in the aforementioned method embodiments and will not be repeated here.

[0118] The embodiment of the present application provides a computing device, which is used to implement part or all of the functions of the fault root cause location method provided in the embodiment of the present application. Fig.12 Schematic diagram of a computing device provided in an embodiment of the present application. Fig.12As shown, the computing device 1200 includes a processor 1201, a memory 1202, a communication interface 1203 and a bus 1204. The processor 1201, the memory 1202 and the communication interface 1203 are connected to each other through the bus 1204.

[0119] Processor 1201 may include a general processor and / or a dedicated hardware chip. A general processor may include: a central processing unit (CPU), a microprocessor or a graphics processing unit (GPU). The CPU is, for example, a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A dedicated hardware chip is a hardware module for high-performance processing. A dedicated hardware chip includes at least one of a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or a network processor (NP). Processor 1201 may also be an integrated circuit chip having signal processing capabilities. In the implementation process, some or all of the functions of the fault root cause location method of the present application may be completed by the hardware integrated logic circuit in the processor 1201 or instructions in the form of software.

[0120] The memory 1202 is used to store computer programs, and the computer programs include an operating system 1202a and executable codes (i.e., program instructions) 1202b. The memory 1202 is, for example, a read-only memory or other types of static storage devices that can store static information and instructions, or a random access memory or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory, a read-only optical disc or other optical disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a blue-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired executable code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. For example, the memory 1202 is used to store an outbound port queue, etc. The memory 1202 is, for example, independent and connected to the processor 1201 via a bus 1204. Or the memory 1202 and the processor 1201 are integrated together. The memory 1202 can store executable code. When the executable code stored in the memory 1202 is executed by the processor 1201, the processor 1201 is used to perform part or all of the functions of the fault root cause location method provided in the embodiment of the present application. For the implementation of the processor 1201 to execute the process, please refer to the relevant description in the aforementioned embodiment. The memory 1202 may also include software modules and data required for other running processes such as the operating system.

[0121] The communication interface 1203 uses a transceiver module such as, but not limited to, a transceiver to achieve communication with other devices or communication networks. For example, the communication interface 1203 can be any one or any combination of the following devices: a network interface (such as an Ethernet interface), a wireless network card, and other devices with network access functions.

[0122] The bus 1204 is any type of communication bus for interconnecting the internal devices of the computing device (e.g., the memory 1202, the processor 1201, and the communication interface 1203). For example, a system bus. The embodiment of the present application takes the interconnection of the above-mentioned devices inside the computing device through the bus 1204 as an example. Optionally, the above-mentioned devices inside the computing device 1200 can also be connected to each other in communication with each other using other connection methods other than the bus 1204. For example, the above-mentioned devices inside the computing device 1200 are interconnected through an internal logical interface.

[0123] It should be noted that the above-mentioned multiple devices can be respectively arranged on independent chips, or at least partially or completely arranged on the same chip. Whether to independently arrange each device on different chips or to integrate and arrange it on one or more chips often depends on the needs of product design. The embodiments of the present application do not limit the specific implementation form of the above-mentioned devices. The descriptions of the processes corresponding to the above-mentioned figures have different focuses. For the parts not described in detail in a certain process, please refer to the relevant descriptions of other processes.

[0124] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product providing a program development platform includes one or more computer instructions, and when these computer program instructions are loaded and executed on a computing device, all or part of the functions of the fault root cause location method provided in the embodiments of the present application are implemented.

[0125] Furthermore, computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium stores computer program instructions that provide a program development platform.

[0126] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0127] Optionally, the structure of at least one computing device included in the computing device cluster can be found in Figure 1 The computing device 1200 is shown. The memory 1202 in one or more computing devices 1200 in the computing device cluster may store the same instructions for executing the fault root cause location method.

[0128] In some possible implementations, the memory 1202 of one or more computing devices 1200 in the computing device cluster may also store partial instructions for executing the fault root cause location method. In other words, the combination of one or more computing devices 1200 may jointly execute instructions for executing the fault root cause location method.

[0129] It should be noted that the memory 1202 in different computing devices 1200 in the computing device cluster can store different instructions, which are respectively used to execute part of the functions of the fault root cause location device. That is, the instructions stored in the memory 1202 in different computing devices 1200 can implement the functions of one or more modules among the acquisition module, the determination module and the grouping module.

[0130] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig.13 A possible implementation is shown. Fig.13 As shown, two computing devices 1300A and 1300B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, computing devices 1300A and 1300B include a bus 1302, a processor 1304, a memory 1306, and a communication interface 1308. The memory 1306 in the computing device 1300A stores instructions for executing the functions of the processing module. At the same time, the memory 1306 in the computing device 1300B stores instructions for executing the functions of the acquisition module.

[0131] It should be understood that Fig.13 The function of the computing device 1300A shown in the figure can also be completed by multiple computing devices 1300. Similarly, the function of the computing device 1300B can also be completed by multiple computing devices 1300. And the deployment mode of the module for implementing the fault root cause location method in the computing device can also be adjusted according to the application requirements.

[0132] An embodiment of the present application also provides a computer-readable storage medium, which is a non-volatile computer-readable storage medium. The computer-readable storage medium includes program instructions. When the program instructions are executed on a computing device, the computing device implements the fault root cause locating method provided in the embodiment of the present application.

[0133] The embodiment of the present application also provides a computer program product including instructions. When the computer program product is executed on a computer, the computer implements the fault root cause locating method provided by the embodiment of the present application.

[0134] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0135] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the networking information and link status involved in this application are all obtained with full authorization.

[0136] In the embodiments of the present application, the terms "first", "second" and "third" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance. The term "at least one" means one or more, and the term "plurality" means two or more, unless otherwise expressly defined.

[0137] The term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0138] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the concept and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for locating the root cause of a fault, characterized in that: The method is applied to a management node that manages a service cluster, the service cluster includes multiple service nodes, and the service nodes are used to implement user services. The method includes: Acquire networking information of the multiple service nodes; When a failure occurs in the service cluster, obtaining link status of links between the multiple service nodes; Perform convergence analysis based on the link status and the networking information to determine the root cause of the fault; The multiple service nodes all access the network through an access network device located at an access layer, and the convergence analysis based on the link status and the networking information to determine the root cause of the fault includes: When the link status of the link between the target service node and other service nodes cannot be obtained, or the link status from other service nodes indicates that the link is disconnected from the target service node, determining the target service node as a candidate fault root cause; Based on the networking information, acquiring a first access network device connected to the target service node and a first service node connected to the first access network device, wherein the first service node is a service node other than the target service node connected to the first access network device; When the link status indicates that the first service node includes a normal node, the target service node is determined to be the root cause of the fault.

2. The method according to claim 1, characterized in that The access network device accesses the network through an aggregation network device located at the aggregation layer, and the aggregation analysis is performed based on the link status and the networking information to determine the root cause of the fault, further comprising: When the link status indicates that the first service nodes are all candidate fault root causes, based on the networking information, obtaining a first aggregation network device connected to the first access network device and a second service node connected to other access network devices connected to the first aggregation network device, the second service node being a service node other than the target service node connected to the first aggregation network device; When the link status indicates that the second service node includes a normal node, it is determined that the first access network device is the root cause of the fault.

3. The method according to claim 2, characterized in that The converged network device accesses the network through a core network device located at the core layer, and the converged analysis is performed based on the link status and the networking information to determine the root cause of the fault, further comprising: When the link status indicates that the second service nodes are all candidate fault root causes, based on the networking information, obtaining a first core network device connected to the first aggregation network device, and a third service node connected to other aggregation network devices connected to the first core network device, wherein the third service node is a service node other than the target service node connected to the first core network device; When the link status indicates that the third service node includes a normal node, it is determined that the first aggregation network device is a root cause of the fault.

4. The method according to claim 3, characterized in that The performing convergence analysis based on the link status and the networking information to determine the root cause of the fault also includes: When the link status indicates that all of the third service nodes are candidate root causes of the fault, the first core network device is determined to be the root cause of the fault.

5. The method according to any one of claims 1 to 4, characterized in that: The obtaining the link status of the links between the multiple service nodes includes: A link status of a link between each service node and other service nodes is received.

6. The method according to claim 5, characterized in that Before acquiring the link status of the links between the multiple service nodes, the method further includes: Determining a plurality of service nodes to be tested among the plurality of service nodes; Providing information of the plurality of service nodes to be tested to each service node, so that each service node obtains a link status of a link between the service node and each service node to be tested; The receiving, provided by each service node, the link status of the link between the service node and other service nodes includes: A link status of a link between the service node and each service node to be tested is received, provided by each service node.

7. The method according to claim 6, characterized in that The network ranges of the multiple service nodes to be tested cover the network range of the service cluster.

8. The method according to claim 1, characterized in that The link status is reflected by one or more of the following: connectivity status and transmission delay of the link.

9. A fault root cause location device, characterized in that: The device is applied to a management node that manages a service cluster, the service cluster includes multiple service nodes, the service nodes are used to implement user services, and the device includes: An acquisition module, used to acquire the networking information of the multiple service nodes; The acquisition module is further configured to acquire the link status of the links between the multiple service nodes when a failure occurs in the service cluster; A processing module, configured to perform convergence analysis based on the link status and the networking information to determine a root cause of the fault; The multiple service nodes all access the network through access network devices located at the access layer, and the processing module is specifically used to: When the link status of the link between the target service node and other service nodes cannot be obtained, or the link status from other service nodes indicates that the link is disconnected from the target service node, determining the target service node as a candidate fault root cause; Based on the networking information, acquiring a first access network device connected to the target service node and a first service node connected to the first access network device, wherein the first service node is a service node other than the target service node connected to the first access network device; When the link status indicates that the first service node includes a normal node, the target service node is determined to be the root cause of the fault.

10. The device according to claim 9, characterized in that The access network device accesses the network through a convergence network device located at the convergence layer, and the processing module is specifically used to: When the link status indicates that the first service nodes are all candidate fault root causes, based on the networking information, obtaining a first aggregation network device connected to the first access network device and a second service node connected to other access network devices connected to the first aggregation network device, the second service node being a service node other than the target service node connected to the first aggregation network device; When the link status indicates that the second service node includes a normal node, it is determined that the first access network device is the root cause of the fault.

11. The device according to claim 10, characterized in that The converged network device accesses the network through a core network device located at the core layer, and the processing module is specifically used to: When the link status indicates that the second service nodes are all candidate fault root causes, based on the networking information, obtaining a first core network device connected to the first aggregation network device, and a third service node connected to other aggregation network devices connected to the first core network device, wherein the third service node is a service node other than the target service node connected to the first core network device; When the link status indicates that the third service node includes a normal node, it is determined that the first aggregation network device is a root cause of the fault.

12. The device according to claim 11, characterized in that The processing module is specifically used for: When the link status indicates that all of the third service nodes are candidate root causes of the fault, the first core network device is determined to be the root cause of the fault.

13. The device according to any one of claims 9 to 12, characterized in that: The acquisition module is specifically used for: A link status of a link between each service node and other service nodes is received.

14. The device according to claim 13, characterized in that The acquisition module is specifically used for: Determining a plurality of service nodes to be tested among the plurality of service nodes; Providing information of the plurality of service nodes to be tested to each service node, so that each service node obtains a link status of a link between the service node and each service node to be tested; A link status of a link between the service node and each service node to be tested is received, provided by each service node.

15. The device according to claim 14, characterized in that The network ranges of the multiple service nodes to be tested cover the network range of the service cluster.

16. The device according to claim 9, characterized in that The link status is reflected by one or more of the following: connectivity status and transmission delay of the link.

17. A computing device cluster, characterized in that: The method comprises at least one computing device, each computing device comprises a processor and a memory, and the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 8.

18. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 8.

19. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 8.

Images