Cloud network, cloud network fault determination method and device, equipment, medium and product

Abstract

The embodiment of the invention discloses a cloud network, a cloud network fault determination method, a cloud network fault determination device, equipment, a medium and a product, and relates to the technical field of computers, the method comprises the following steps: obtaining at least one abnormal detection data, the abnormal detection data being detection data containing an abnormal detection result in a detection data set, the detection data set comprises detection data of all target communication links between each network element and each adjacent network element in the network topological graph, and the detection data comprises a detection result and an associated network element identifier; and determining a fault analysis result of the current cloud network according to the associated network element identifier in the at least one abnormal detection data. By adopting the technical scheme of the embodiment of the invention, the determination speed of the cloud network fault analysis result can be improved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computer technology, and in particular, to a cloud network, a cloud network fault determination method, an apparatus, a device, a medium, and a product. Background Art

[0002] Currently, real-time traffic monitoring of cloud networks is usually performed based on a cloud network monitoring platform. When abnormal traffic at a certain node is detected, the specific cause of the abnormal traffic is manually analyzed.

[0003] However, in the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0004] The method of combining traffic monitoring with manual analysis of traffic anomalies cannot quickly identify the cause of cloud network failures. Summary of the invention

[0005] Embodiments of the present invention provide a cloud network, a cloud network fault determination method, an apparatus, a device, a medium, and a product to increase the speed of determining cloud network fault analysis results.

[0006] In a first aspect, an embodiment of the present invention provides a cloud network fault determination method, the method comprising:

[0007] Acquire at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in a detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes the detection result and an associated network element identifier;

[0008] A fault analysis result of the current cloud network is determined according to the associated network element identifier in the at least one abnormality detection data.

[0009] In a second aspect, an embodiment of the present invention further provides a cloud network fault determination device, the device comprising:

[0010] A data acquisition module, configured to acquire at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in a detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes the detection results and associated network element identifiers;

[0011] The result determination module is used to determine the fault analysis result of the current cloud network according to the associated network element identifier in the at least one abnormal detection data.

[0012] In a third aspect, an embodiment of the present invention provides an electronic device, the electronic device comprising:

[0013] one or more processors;

[0014] A memory for storing one or more programs;

[0015] When the one or more programs are executed by the one or more processors, the one or more processors implement the cloud network fault determination method provided by any embodiment of the present invention.

[0016] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a cloud network fault determination method as provided in any embodiment of the present invention.

[0017] In a fifth aspect, an embodiment of the present invention further provides a computer product, wherein the computer program product includes a computer program, and when the computer program is executed by a processor, the cloud network fault determination method described in any embodiment is implemented.

[0018] The embodiments of the above invention have the following advantages or beneficial effects:

[0019] Since the detection data set includes the detection data of each network element and all target communication links in the network topology diagram, the detection data set includes the detection data of all target communication links in the network topology diagram, and is comprehensive network communication quality data; since the detection data includes the detection results and the associated network element identifiers, it is possible to determine whether the detection data set includes at least one abnormal detection data based on the relationship between the detection results in each detection data and the abnormal result conditions. When the detection data set includes at least one abnormal detection data, the fault analysis result of the current cloud network can be determined based on the associated network element identifier in the at least one abnormal detection data, thereby achieving the technical effect of indiscriminate detection of all target communication links and rapid and automatic locking of abnormal communication links. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a schematic diagram of the structure of a cloud network provided by an embodiment of the present invention;

[0021] Figure 2 is a schematic diagram of a network element link relationship provided by an embodiment of the present invention;

[0022] Figure 3 is another structural diagram of a cloud network provided by an embodiment of the present invention;

[0023] Figure 4 is a flow chart of a cloud network fault determination method provided by an embodiment of the present invention;

[0024] Figure 5 is another flow chart of the cloud network fault determination method provided by an embodiment of the present invention;

[0025] Figure 6 is a schematic diagram of the structure of a cloud network fault determination device provided by an embodiment of the present invention;

[0026] Figure 7 It is another structural diagram of a cloud network fault determination device provided by an embodiment of the present invention;

[0027] Figure 8 It is another structural diagram of a cloud network fault determination device provided by an embodiment of the present invention;

[0028] Fig. 9 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0030] Figure 1 A schematic diagram of a cloud network structure provided by an embodiment of the present invention (only one network element is shown). The cloud network can promptly detect abnormal network elements and abnormal communication links within abnormal network elements. Figure 1 As shown, the cloud network includes: a first monitoring server, multiple network elements, a role monitoring agent, a screening device and a data processing device arranged in each of the network elements; the first monitoring server stores a network topology map; the role monitoring agent is used to obtain the network topology map, obtain the detection data of all target communication links between the network element and the adjacent network elements according to the network topology map, and transmit the detection data to the screening device, the detection data including the detection result and the associated network element identifier; the screening device is used to use the detection data that meets the abnormal result condition as abnormal detection data, and send the abnormal detection data to the data processing device; the data processing device is used to receive at least one abnormal detection data sent by the screening device, and determine the fault analysis result of the current cloud network according to the associated network element identifier in the at least one abnormal detection data.

[0031] The technical solution provided by the embodiment of the present invention is comprehensive network communication quality data because the detection data set includes the detection data of each network element and all target communication links in the network topology diagram. Since the detection data includes the detection data of all target communication links in the network topology diagram, the detection data set is comprehensive network communication quality data. Since the detection data includes the detection result and the associated network element identifier, it is possible to determine whether the detection data set includes at least one abnormal detection data based on the relationship between the detection result in each detection data and the abnormal result condition. In the case that the detection data set includes at least one abnormal detection data, the fault analysis result of the current cloud network can be determined based on the associated network element identifier in the at least one abnormal detection data, thereby achieving the technical effect of indiscriminate detection of all target communication links and rapid and automatic locking of abnormal communication links.

[0032] In one embodiment, the target communication link is a communication link that is currently in an activated state, or in other words, a communication link that is currently in a working state.

[0033] In one embodiment, the target communication link is a communication link corresponding to the target communication protocol. In a detection cycle, one or more communication protocols can be set as the target communication protocol. In this way, all target communication links between a network element and its adjacent network elements include communication links corresponding to one or more target communication protocols.

[0034] The monitoring database is used to store cloud network quality control related data, such as network topology diagrams, fault analysis results, etc.

[0035] A network topology diagram, also known as a topology diagram, is a diagram used to sort out the structure of network node devices and communication media. It can intuitively display the relationship between network elements in a cloud network, such as link relationships. A network element is an element in a cloud network, the smallest unit that can be monitored and managed, such as a virtual router, distributed router, virtual server, etc.

[0036] An adjacent network element can be understood as a neighboring network element, which refers to a network element that is adjacent and has a communication link.

[0037] Each network element in the network topology diagram is connected to at least one adjacent network element, and each network element will become an adjacent network element of at least one other network element.

[0038] Exemplarily, the first network element has two adjacent network elements, namely the second network element and the third network element; the second network element has three adjacent network elements, namely the first network element, the third network element and the fourth network element. When the first network element is the target network element, the second network element is its adjacent network element; when the second network element is the target network element, the first network element is its adjacent network element.

[0039] In one embodiment, different detection packets are set for different communication protocols, and the detection data corresponding to different detection packets are also different. For example, there is a Ping packet (Packet Internet Groper) for IP (internet Protocol) and a heartbeat packet for TCP (Transmission Control Protocol). The detection data corresponding to the Ping packet include: the identification of the network element sending the detection packet, the identification of the network element to which the detection packet flows, the type of network element to which the detection packet flows, the time required for the detection packet to be sent and received, the number of packets sent, and the recorded packet sending time of the detection packet sending network element when the detection packet is sent. The detection data corresponding to the heartbeat packet include: the identification of the network element to which the detection packet flows, the heartbeat index identification, the timestamp, the detection packet return value, and the detection consumption time corresponding to the current heartbeat packet. Regarding the detection packet return value, "0" indicates that the detection is successful, and "1" indicates that the detection fails.

[0040] Abnormal detection data refers to detection data including abnormal detection results. Abnormal detection results are abnormal detection results. In this embodiment, detection results that meet the abnormal result conditions are used as abnormal detection results.

[0041] The abnormal result conditions for different detection tasks are different. For example, for TCP-based communication scenarios, the abnormal result condition is the detection failure mark; for IP-based communication scenarios, the abnormal result condition is that the detection time is greater than or equal to the set duration, which can be set to 3 seconds, 5 seconds, etc.

[0042] The associated network element identifier may be the network element identifier of the network element to which the detection packet flows, or the network element identifier of the network element from which the detection packet sends and the network element identifier of the network element to which the detection packet flows.

[0043] In one embodiment, each of the network elements is provided with at least one role monitoring agent, and each of the at least one role monitoring agent corresponds to a different predetermined communication protocol; the role monitoring agent is configured to send a detection packet to an adjacent network element of the network element based on the network topology map and the corresponding predetermined communication protocol, receive response data corresponding to the detection packet, and use the response data as detection data of the corresponding target communication link between the network element and the adjacent network element.

[0044] Specifically, a role monitoring agent corresponds to a predetermined communication protocol, so Figure 1 The N role monitoring agents in the system correspond to a predetermined communication protocol respectively. For example, the IP monitoring agent corresponds to the IP communication protocol, and the app (Application) monitoring agent corresponds to the TCP communication protocol.

[0045] In one detection cycle, one detection data corresponds to one communication link. It should be noted that if network element A and network element B can communicate based on the first communication protocol, then for the first communication protocol, there are two communication links between network element A and network element B, namely, the first communication link from network element A to network element B, and the second communication link from network element B to network element A.

[0046] Exemplarily, the first network element is configured to communicate with the second network element based on the first communication protocol and the second communication protocol, and to communicate with the third network element based on the first communication protocol and the third communication protocol. At this time, the first network element is provided with a first role monitoring agent for the first communication protocol, a second role monitoring agent for the second communication protocol, and a third role monitoring agent for the third communication protocol. The first role monitoring agent is configured to send a first detection packet to the first network element, and receive the response data of the first network element to the first detection packet, and use the response data as the first detection data of the corresponding target communication link under the first network element; send a first detection packet to the second network element, and receive the response data fed back by the second network element to the first detection packet, and use the response data as the first detection data of the corresponding target communication link under the second network element. The second role monitoring agent is configured to send a second detection packet to the first network element, and receive the response data of the first network element to the second detection packet, and use the response data as the second detection data of the corresponding target communication link under the first network element. The third role monitoring agent is configured to send a third detection packet to the second network element, receive response data from the second network element to the third detection packet, and use the response data as third detection data of the corresponding target communication link under the second network element.

[0047] For example, Figure 2 As shown, if the target network element is a virtual router, the adjacent network elements of the virtual router include a distributed router and at least one virtual server. An IP monitoring agent and an app monitoring agent are set in the target network element. The IP monitoring agent is configured to send a Ping packet to the distributed router and each virtual server. The app monitoring agent is configured to send a heartbeat packet, such as a hello heartbeat packet, to the distributed router and each virtual server.

[0048] In one embodiment, after the role monitoring agent obtains the network topology map, it determines at least one adjacent network element of the network element and all addresses between the network element and the at least one adjacent network element from the network topology map, and uses all addresses between the network element and the at least one adjacent network element as an address combination. Based on the address combination, the detection data of all target communication links between the network element and each adjacent network element is obtained, and the detection data is sent to the role monitoring device, which forwards the detection data to the screening device. By connecting the role monitoring agent and the screening device through the role monitoring device, the stability of the work of the screening device and the role monitoring agent can be improved.

[0049] In the above embodiment, detection data of a target communication link based on one or more communication protocols in a cloud network is obtained by at least one role monitoring agent disposed in each network element.

[0050] In one embodiment, the screening device may be optionally a distributed message subscription system; the distributed message subscription system is configured to perform screening operations on the received detection data based on the abnormal result conditions corresponding to each communication protocol, and when the abnormal detection data is screened out, send the abnormal detection data to the data processing device. Exemplarily, the abnormal result condition of the TCP communication protocol is a detection failure flag; the abnormal result condition of the IP communication protocol is that the detection time is greater than or equal to 5 seconds. The data processing device preferably stores each abnormal detection data in the corresponding abnormal detection data combination based on the detection data identifier in the abnormal detection data, thereby obtaining the abnormal communication data combination corresponding to each communication protocol in the current detection cycle,

[0051] It can be understood that since the detection data includes the associated network element identifier, and any abnormal detection data corresponds to an abnormal communication link. Therefore, the abnormal communication link and the network element where the abnormal communication link is located can be locked according to the associated network element identifier in the abnormal detection data. Therefore, the fault analysis result includes the abnormal network element identifier and the abnormal communication link in the network element corresponding to the abnormal network element identifier. The fault analysis result allows the user to directly and quickly lock the cause of the fault.

[0052] In one embodiment, Figure 3 As shown, the cloud network also includes a monitoring database; the data processing device is also used to synchronize the fault analysis results to the monitoring database, and the monitoring database is used to update the network topology map according to the fault analysis results, and send the updated network topology map directly or indirectly to the first monitoring server, for example, to identify abnormal network elements and abnormal communication links in the abnormal network elements from the network topology map. The timeliness of updating the network topology map in the monitoring database is improved. Of course, the first monitoring server can also be configured to automatically pull the latest network topology map from the monitoring database under set circumstances.

[0053] In one embodiment, Figure 3As shown, the cloud network also includes a log controller; the data processing device is also used to send the fault analysis result to the log controller; the log controller is used to display the fault analysis result, and reorganize the current cloud network based on the fault analysis result to obtain an updated cloud network. This embodiment realizes that the log controller automatically reorganizes the current cloud network based on the non-faulty network elements in the current cloud network, so that the reorganized cloud network provides services to users; or the log controller automatically reorganizes the current cloud network based on the non-faulty network elements and backup network elements in the current cloud network, and the reorganized cloud network provides services to users, so that the cloud network has self-healing capabilities and can provide network services 24 hours a day, significantly improving operation and maintenance efficiency, reducing operation and maintenance failures, and reducing operation and maintenance costs.

[0054] In one embodiment, after detecting the cloud network reorganization, the log controller determines the network topology of the reorganized cloud network and synchronizes the network topology to the monitoring database in real time, so that the monitoring database can obtain the latest network topology in time.

[0055] In one embodiment, the data processor sends the fault analysis result to the log controller; the log controller determines the communication protocol corresponding to each abnormal communication link according to the coding information of each abnormal communication link, and displays the fault analysis result, and in the fault analysis result, the sub-fault analysis results under different communication protocols correspond to different identification information, such as corresponding to different color identifications. Optionally, the log controller displays the fault analysis result in the form of a network topology diagram, and in the network topology image, different colors are used to identify abnormal information in different sub-fault analysis results, such as abnormal network element identification and abnormal communication line.

[0056] Since the cloud network includes multiple servers, the multiple servers are divided into multiple server clusters. In order to improve the data access speed, in one embodiment, each server cluster is configured with a slave monitoring database, and the slave monitoring database is set to synchronize data with the monitoring database at regular intervals. In this way, after the network topology map in the monitoring database is updated, it will be synchronized to the slave monitoring database in a timely manner. After the network topology map in the slave monitoring database is updated, it will be automatically pushed to the second monitoring server, and the second monitoring server will obtain it and store it in a specified location, such as Redis (cache server) (see Figure 3 ). The first monitoring server sends the network topology map stored in the specified location to the role monitoring agent in each network element in the cluster. In some cases, for example, after a network element fails and restarts, the role monitoring agent set in each network element will automatically obtain the network topology map from the first monitoring server.

[0057] On the basis of the above embodiment, a role monitoring device is provided for each role monitoring agent. After detecting the detection data, the role monitoring agent provided in each network element sends the detection data to the corresponding role monitoring device, so that the role monitoring device sends the detection data to the data screening device. The role monitoring device and the role monitoring agent belong to the same role, or the two correspond to the same communication protocol. The use of the role monitoring device can improve the stability of the role monitoring agent and the data screening device, thereby improving the stability of the operation of the entire cloud network.

[0058] Figure 4 This is a flow chart of a cloud network fault determination method provided by an embodiment of the present invention. This embodiment is applicable to the case of automatically determining the fault analysis result of a cloud network. The method can be executed by a cloud network fault determination device in a data processing device, and the device can be implemented by software and / or hardware. Figure 4 As shown, the method specifically comprises the following steps:

[0059] S110. Obtain at least one abnormality detection data, where the abnormality detection data is detection data in a detection data set that contains abnormality detection results. The detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes detection results and associated network element identifiers.

[0060] In one embodiment, the target communication link is a communication link that is currently in an activated state, or in other words, a communication link that is currently in a working state.

[0061] In one embodiment, the target communication link is a communication link corresponding to the target communication protocol. In a detection cycle, one or more communication protocols can be set as the target communication protocol. In this way, all target communication links between a network element and its adjacent network elements include communication links corresponding to one or more target communication protocols.

[0062] A network topology diagram, also known as a topology diagram, is a diagram used to sort out the structure of network node devices and communication media, and can intuitively show the relationship between network elements in the network. A network element is an element or device in a cloud network, and is the smallest unit that can be monitored and managed in network management.

[0063] The associated network element identifier may be the network element identifier of the network element to which the detection packet flows, or the network element identifier of the network element from which the detection packet sends and the network element identifier of the network element to which the detection packet flows.

[0064] An adjacent network element can be understood as a neighboring network element, which refers to a network element that is adjacent and has a communication connection.

[0065] Each network element in the network topology diagram is connected to at least one adjacent network element, and each network element will become an adjacent network element of at least one other network element.

[0066] Exemplarily, the first network element has two adjacent network elements, namely the second network element and the third network element; the second network element has three adjacent matrices, namely the first network element, the third network element and the fourth network element. When the first network element is the target network element, the second network element is its adjacent network element; when the second network element is the target network element, the first network element is its adjacent network element.

[0067] Abnormal detection data refers to detection data including abnormal detection results. Abnormal detection results are abnormal detection results. In this embodiment, detection results that meet the abnormal result conditions are used as abnormal detection results.

[0068] The detection result may be a detection success mark, a detection failure mark or a detection time consumption.

[0069] The abnormal result conditions for different detection tasks are different. For example, for IP protocol communication scenarios, the abnormal result condition is the detection failure mark; for TCP protocol communication scenarios, the abnormal result condition is that the detection time is greater than or equal to the set time, which can be set to 3 seconds, 5 seconds, etc.

[0070] In one embodiment, the network element is provided with one or more role monitoring agents, and each of the multiple role monitoring agents corresponds to a different predetermined communication protocol; the role monitoring agent is configured to send a detection packet to an adjacent network element of the network element based on the network topology diagram and the corresponding predetermined communication protocol, receive response data corresponding to the detection packet, and use the response data as detection data of the corresponding target communication link between the network element and the adjacent network element; and send the detection data to a data screening device. The screening device filters out abnormal detection data from the received detection data based on the abnormal result condition, and sends the abnormal detection data to a data processing device.

[0071] Based on the above embodiment, the role monitoring agent sends the detection data to the role monitoring device, and the role monitoring device forwards the detection data to the data screening device. The data screening device performs a screening operation on the received detection data, and when abnormal detection data is detected, the abnormal detection data is sent to the data processing device. Among them, the screening device can be optionally a distributed message subscription system.

[0072] This step aims to obtain bidirectional detection data between two adjacent network elements with a target communication link in the network topology diagram. For example, for a first network element and a second network element with a target communication link, it is necessary to obtain detection data fed back by the second network element to a detection packet sent by the first network element, and detection data fed back by the first network element to a detection packet sent by the second network element.

[0073] S120. Determine a fault analysis result of the current cloud network according to an associated network element identifier in the at least one abnormality detection data.

[0074] Take the communication scenario based on IP communication protocol as an example. The detection data includes the identification of the network element sending the detection packet and the identification of the network element receiving the detection packet. If a network element has multiple adjacent network elements, then the network element will also be an adjacent network element of at least one other network element.

[0075] It can be understood that, since the detection data includes the associated network element identifier, and any abnormal detection data corresponds to an abnormal communication link. Therefore, the abnormal communication link and the network element where the abnormal communication link is located can be locked according to the associated network element identifier in the abnormal detection data. Therefore, the fault analysis result in this embodiment includes the abnormal network element identifier and the abnormal communication link in the network element corresponding to the abnormal network element identifier.

[0076] On the basis of the above-mentioned embodiment, after the fault analysis result of the current cloud network is determined, the fault analysis result is synchronized to the monitoring database in real time, so that the monitoring database updates the network topology map according to the fault analysis result of the cloud network. The monitoring database is used to store the operation monitoring data of the cloud network. Synchronizing the fault analysis result to the monitoring database in real time can significantly improve the timeliness of updating the fault analysis result and the network topology map in the monitoring database.

[0077] On the basis of the above-mentioned embodiment, after the fault analysis result is determined, the fault analysis result is sent to the log controller, so that the log controller displays the fault analysis result, and reorganizes the current cloud network based on the fault analysis result to obtain a reorganized cloud network. Specifically, the log controller displays the fault analysis result, which can facilitate users to obtain the latest operation status of the current cloud network in a timely manner; the log controller automatically reorganizes a new cloud network based on the non-abnormal network elements in the current cloud network, and uses the new cloud network to provide services to users; or the log controller automatically reorganizes a new cloud network based on the non-abnormal network elements and backup network elements in the current cloud network, and then uses the new cloud network to provide services to users, so that the cloud network has self-healing capabilities and can provide network services 24 hours a day.

[0078] The technical solution provided by the embodiment of the present invention is comprehensive network communication quality data because the detection data set includes the detection data of each network element and all target communication links in the network topology diagram. Since the detection data includes the detection data of all target communication links in the network topology diagram, the detection data set is comprehensive network communication quality data. Since the detection data includes the detection result and the associated network element identifier, it is possible to determine whether the detection data set includes at least one abnormal detection data based on the relationship between the detection result in each detection data and the abnormal result condition. In the case that the detection data set includes at least one abnormal detection data, the fault analysis result of the current cloud network can be determined based on the associated network element identifier in the at least one abnormal detection data, thereby achieving the technical effect of indiscriminate detection of all target communication links and rapid and automatic locking of abnormal communication links.

[0079] Figure 5 Another flow chart of the cloud network fault determination method provided by the embodiment of the present invention. Based on the above embodiment, the embodiment of the present invention refines the processing steps of abnormal detection data. Figure 5 As shown, the method includes:

[0080] S210. Obtain at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in a detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes detection results and associated network element identifiers.

[0081] In a cloud network environment, adjacent network elements can be configured to communicate based on multiple communication links, and different communication links correspond to different communication protocols. In this case, if the cloud network is to be operated normally, it is necessary to ensure that each communication link between adjacent network elements is normal. To this end, in this embodiment, each network element is provided with one or more role monitoring agents, and each of the multiple role monitoring agents corresponds to a different predetermined communication protocol; the role monitoring agent is configured to send a detection packet to the adjacent network element of the network element based on the network topology diagram and the corresponding predetermined communication protocol, receive response data corresponding to the detection packet, and use the response data as the detection data of the corresponding target communication link between the network element and the adjacent network element. This embodiment can obtain the detection data of all target communication links under at least one communication protocol in the cloud network through different role monitoring agents, thereby improving the accuracy of the detection data.

[0082] In one embodiment, each role monitoring agent is configured to periodically send detection packets based on a predetermined communication protocol, thereby achieving the technical effect of periodically detecting the communication status of the corresponding communication link.

[0083] S2201. Divide the at least one abnormality detection data into at least one abnormality detection data combination, where different abnormality detection data combinations in the at least one abnormality detection data combination correspond to different communication protocols.

[0084] In one embodiment, the screening device performs a screening operation on the received detection data based on the abnormal result conditions corresponding to each communication protocol, and sends the abnormal detection data to the data processing device when the abnormal detection data is screened out; the data processing device stores each abnormal data in the corresponding abnormal detection data combination based on the detection data identifier in each abnormal detection data. The data processing device in this embodiment can directly obtain the required abnormal detection data without additional data processing, which greatly reduces the data processing amount of the data processing device and improves the speed of determining the fault analysis result.

[0085] On the basis of the above-mentioned embodiment, the role monitoring agent may also send the detection data to the role monitoring agent corresponding to the same communication protocol, and then the role monitoring agent sends the received communication data to the data screening device.

[0086] The data screening device may be a distributed message subscription system, which can quickly and accurately complete the screening operation of abnormal detection data under different communication protocols and reduce the data processing pressure of the data processing device.

[0087] In one embodiment, a data processing device receives detection data from each role monitoring agent, and obtains a detection data combination corresponding to each communication protocol. It is determined whether each detection data combination includes abnormal detection data, and if so, it is stored in the corresponding abnormal detection data combination, thereby obtaining at least one abnormal detection data combination, wherein the union of all detection data combinations is a detection data set. This embodiment can significantly simplify the structure of the cloud network.

[0088] S2202: Determine a sub-fault analysis result under a corresponding communication protocol according to an associated network element identifier in each abnormal detection data in each abnormal detection data combination.

[0089] Since different abnormal detection data combinations correspond to different communication protocols, each abnormal detection data combination includes all abnormal detection data under the corresponding communication protocol, so the sub-fault analysis result under the corresponding communication protocol can be determined according to the associated network element identifier in each abnormal detection data in each abnormal detection data combination. It can be understood that the sub-fault analysis result includes all abnormal communication links of the current cloud network with respect to the corresponding communication protocol.

[0090] S2203. Determine the fault analysis result of the current cloud network according to all sub-fault analysis results.

[0091] All sub-fault analysis results of the current detection cycle are aggregated together to obtain the fault analysis result of the current cloud network, which includes all abnormal communication links in the current cloud network.

[0092] In the embodiment of the present invention, sub-fault analysis results under different communication protocols are first determined respectively, and then the sub-fault analysis results under all communication protocols are integrated to obtain the fault analysis result of the current cloud network, thereby achieving the technical effect of first determining the local fault analysis result and then determining the global fault analysis result based on all the local fault analysis results, and effectively ensuring the accuracy and comprehensiveness of the fault analysis result.

[0093] The following is an embodiment of a cloud network fault determination device provided in an embodiment of the present invention. The device and the cloud network fault determination method described in the above embodiment belong to the same inventive concept. For details not described in detail in the embodiment of the cloud network fault determination device, please refer to the contents of the above embodiments.

[0094] Figure 6 A schematic diagram of the structure of a cloud network fault determination device provided by an embodiment of the present invention. Figure 6 As shown, the device comprises:

[0095] The data acquisition module 410 is used to acquire at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in the detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes the detection result and the associated network element identifier;

[0096] The result determination module 420 is used to determine the fault analysis result of the current cloud network according to the associated network element identifier in the at least one abnormal detection data.

[0097] In one embodiment, the result determination module is specifically used to:

[0098] Dividing the at least one abnormality detection data into at least one abnormality detection data combination, wherein different abnormality detection data combinations in the at least one abnormality detection data combination correspond to different communication protocols;

[0099] Determine a sub-fault analysis result under a corresponding communication protocol according to the associated network element identifier in each of the abnormal detection data in each of the abnormal detection data combinations;

[0100] The fault analysis result of the current cloud network is determined based on all sub-fault analysis results.

[0101] In one embodiment, each of the network elements is provided with one or more role monitoring agents, and each of the multiple role monitoring agents corresponds to a different predetermined communication protocol;

[0102] The role monitoring agent is configured to send a detection packet to the adjacent network element of the network element based on the network topology map and the corresponding predetermined communication protocol, receive response data corresponding to the detection packet, and use the response data as the detection data of the corresponding target communication link between the network element and the adjacent network element.

[0103] In one embodiment, Figure 7 As shown, the device further includes a decision module 430, which is used to:

[0104] The fault analysis result is sent to a log controller so that the log controller displays the fault analysis result, and the current cloud network is reorganized based on the fault analysis result to obtain a reorganized cloud network.

[0105] In one embodiment, Figure 8 As shown, the device further includes a synchronization module 440, and the synchronization module 440 is used to:

[0106] The fault analysis result is synchronized to a monitoring database in real time, so that the monitoring database updates the network topology map according to the cloud network fault analysis result.

[0107] In one embodiment, the fault analysis result includes an abnormal network element identifier and an abnormal communication link in the network element corresponding to the abnormal network element identifier.

[0108] The technical solution provided by the embodiment of the present invention is comprehensive network communication quality data because the detection data set includes the detection data of each network element and all target communication links in the network topology diagram. Since the detection data includes the detection data of all target communication links in the network topology diagram, the detection data set is comprehensive network communication quality data. Since the detection data includes the detection result and the associated network element identifier, it is possible to determine whether the detection data set includes at least one abnormal detection data based on the relationship between the detection result in each detection data and the abnormal result condition. In the case that the detection data set includes at least one abnormal detection data, the fault analysis result of the current cloud network can be determined based on the associated network element identifier in the at least one abnormal detection data, thereby achieving the technical effect of indiscriminate detection of all target communication links and rapid locking of abnormal communication links.

[0109] The cloud network fault determination device provided in the embodiment of the present invention can execute the cloud network fault determination method provided in the embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the cloud network fault determination method.

[0110] Fig. 9 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Fig. 9 A block diagram of an exemplary server 12 suitable for use in implementing embodiments of the present invention is shown. Fig. 9 The server 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0111] like Fig. 9 As shown, the server 12 is in the form of a general purpose computing device. The components of the server 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).

[0112] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0113] The server 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the server 12, including volatile and non-volatile media, removable and non-removable media.

[0114] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The server 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Fig. 9 not shown, usually called a "hard drive"). Although Fig. 9 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0115] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0116] The server 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), may communicate with one or more devices that enable a user to interact with the server 12, and / or may communicate with any device that enables the server 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input / output (I / O) interface 22. In addition, the server 12 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 20. As shown, the network adapter 20 communicates with other modules of the server 12 via a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the server 12, including, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0117] The processing unit 16 executes various functional applications and data processing by running the program stored in the system memory 28, for example, implementing the steps of the cloud network fault determination method provided in the embodiment of the present invention, the method comprising:

[0118] Acquire at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in a detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes the detection result and an associated network element identifier;

[0119] A fault analysis result of the current cloud network is determined according to the associated network element identifier in the at least one abnormality detection data.

[0120] Of course, those skilled in the art can understand that the processor can also implement the technical solution of the cloud network fault determination method provided by any embodiment of the present invention.

[0121] This embodiment provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the steps of the cloud network fault determination method provided in the foregoing embodiment of the present invention are implemented. The method includes:

[0122] Acquire at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in a detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes the detection result and an associated network element identifier;

[0123] A fault analysis result of the current cloud network is determined according to the associated network element identifier in the at least one abnormal detection data.

[0124] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0125] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0126] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0127] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0128] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented by a program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0129] An embodiment of the present invention also provides a computer program product, including a computer program, which, when executed by a processor, implements a cloud network fault determination method as provided in any embodiment of the present application.

[0130] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0131] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A cloud network fault determination method, characterized in that: The method comprises: Acquire at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in a detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes the detection result and an associated network element identifier; A fault analysis result of the current cloud network is determined according to the associated network element identifier in the at least one abnormal detection data.

2. The method according to claim 1, characterized in that The determining, according to the associated network element identifier in the at least one abnormal detection data, a fault analysis result of the current cloud network includes: Dividing the at least one abnormality detection data into at least one abnormality detection data combination, wherein different abnormality detection data combinations in the at least one abnormality detection data combination correspond to different communication protocols; Determine a sub-fault analysis result under a corresponding communication protocol according to the associated network element identifier in each of the abnormal detection data in each of the abnormal detection data combinations; The fault analysis result of the current cloud network is determined based on all sub-fault analysis results.

3. The method according to claim 1, characterized in that Each of the network elements is provided with one or more role monitoring agents, and each of the multiple role monitoring agents corresponds to a different predetermined communication protocol; The role monitoring agent is configured to send a detection packet to the adjacent network element of the network element based on the network topology map and the corresponding predetermined communication protocol, receive response data corresponding to the detection packet, and use the response data as the detection data of the corresponding target communication link between the network element and the adjacent network element.

4. The method according to claim 1, characterized in that After determining the cloud network fault analysis result, the method further includes: The fault analysis result is sent to a log controller so that the log controller displays the fault analysis result, and the current cloud network is reorganized based on the fault analysis result to obtain a reorganized cloud network.

5. The method according to claim 1, characterized in that After determining the fault analysis result of the current cloud network, the method further includes: The fault analysis result is synchronized to a monitoring database in real time, so that the monitoring database updates the network topology map according to the cloud network fault analysis result.

6. The method according to claim 1, characterized in that The fault analysis result includes an abnormal network element identifier and an abnormal communication link in a network element corresponding to the abnormal network element identifier.

7. A cloud network fault determination device, characterized in that: include: A data acquisition module, configured to acquire at least one abnormality detection data, wherein the abnormality detection data is detection data containing abnormality detection results in a detection data set, wherein the detection data set includes detection data of all target communication links between each network element and each adjacent network element in the network topology diagram, and the detection data includes detection results and associated network element identifiers; The result determination module is used to determine the fault analysis result of the current cloud network according to the associated network element identifier in the at least one abnormal detection data.

8. A cloud network, characterized in that: include: A first monitoring server, a plurality of network elements, a role monitoring agent, a screening device and a data processing device arranged in each of the network elements; The first monitoring server stores a network topology map; The role monitoring agent is used to obtain the network topology map, obtain detection data of all target communication links between the network element where it is located and the adjacent network elements according to the network topology map, and transmit the detection data to the screening device, wherein the detection data includes the detection result and the associated network element identifier; The screening device is used to use the detection data that meets the abnormal result condition as abnormal detection data, and send the abnormal detection data to the data processing device; The data processing device is used to receive at least one abnormality detection data sent by the screening device, and determine the fault analysis result of the current cloud network according to the associated network element identifier in the at least one abnormality detection data.

9. The cloud network according to claim 8, characterized in that: Each of the network elements is provided with one or more role monitoring agents, and each of the multiple role monitoring agents corresponds to a different predetermined communication protocol; The role monitoring agent is configured to send a detection packet to the adjacent network element of the network element based on the network topology map and the corresponding predetermined communication protocol, receive response data corresponding to the detection packet, and use the response data as the detection data of the corresponding target communication link between the network element and the adjacent network element.

10. The cloud network according to claim 8, characterized in that: The screening device is a distributed message subscription system; The distributed message subscription system is configured to perform a screening operation on the received detection data based on the abnormal result conditions corresponding to each communication protocol, and when the abnormal detection data is screened out, send the abnormal detection data to the data processing device.

11. The cloud network according to claim 8, characterized in that: Also includes monitoring database; The data processing device is also used to synchronize the fault analysis results to the monitoring database; The monitoring database is used to update the network topology map according to the fault analysis result, and send the updated network topology map directly or indirectly to the first monitoring server.

12. The cloud network according to claim 8, characterized in that: Also includes a log controller; The data processing device is also used to send the fault analysis result to the log controller; The log controller is used to display the fault analysis result, and reorganize the current cloud network based on the fault analysis result to obtain a reorganized cloud network.

13. The cloud network according to claim 8, characterized in that: The fault analysis result includes an abnormal network element identifier and an abnormal communication link in a network element corresponding to the abnormal network element identifier.

14. An electronic device, characterized in that: The electronic device comprises: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the cloud network fault determination method as described in any one of claims 1-6.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the cloud network fault determination method as described in any one of claims 1-6 is implemented.

16. A computer program product, characterized in that The computer program product comprises a computer program, which, when executed by a processor, implements the cloud network fault determination method according to any one of claims 1-6.

Images