CN114866398A - Network fault diagnosis method and device - Google Patents
Network fault diagnosis method and device Download PDFInfo
- Publication number
- CN114866398A CN114866398A CN202210302940.0A CN202210302940A CN114866398A CN 114866398 A CN114866398 A CN 114866398A CN 202210302940 A CN202210302940 A CN 202210302940A CN 114866398 A CN114866398 A CN 114866398A
- Authority
- CN
- China
- Prior art keywords
- fault diagnosis
- fault
- request message
- option field
- diagnosis request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003745 diagnosis Methods 0.000 title claims abstract description 316
- 238000000034 method Methods 0.000 title claims abstract description 89
- 230000004044 response Effects 0.000 claims abstract description 139
- 230000008569 process Effects 0.000 claims abstract description 29
- 238000012545 processing Methods 0.000 claims abstract description 28
- 238000001514 detection method Methods 0.000 claims description 82
- 238000004043 dyeing Methods 0.000 claims description 10
- 238000012544 monitoring process Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 8
- 238000012423 maintenance Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 3
- 238000004590 computer program Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000012806 monitoring device Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000013102 re-test Methods 0.000 description 1
- 239000000523 sample Substances 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application provides a network fault diagnosis method and a device, wherein the method comprises the following steps: sending a fault diagnosis request message to target network element equipment in the edge cloud so that the target network element equipment processes a target service according to the fault diagnosis request message, updating an option field in the fault diagnosis request message according to a processing result, generating a fault diagnosis response message according to the updated option field, receiving the fault diagnosis response message containing the updated option field sent by the target network element equipment, and determining fault information in the edge cloud according to the updated option field in the fault diagnosis response message. The method and the device can determine specific packet loss information, not only determine packet loss points, and improve the accuracy of fault determination.
Description
Technical Field
The embodiment of the application relates to the technical field of data transmission, in particular to a network fault diagnosis method and device.
Background
With the popularization of the edge cloud application, more and more network element devices are arranged in the edge cloud, and the problem troubleshooting is more and more complicated.
In the prior art, a fault in the edge cloud may be determined through a fault diagnosis request message, and correspondingly, the fault diagnosis request message may be sent to each network element device in the edge cloud, so that the network element device mirrors the identified fault diagnosis request message after identifying the fault diagnosis request message, and then sends the mirrored fault diagnosis request message to an analysis system, so that the analysis system analyzes a specific packet loss point according to all received messages.
However, the analysis system can only determine the packet loss point, and cannot detect a specific packet loss reason, thereby reducing the accuracy of fault determination.
Disclosure of Invention
The embodiment of the application provides a network fault diagnosis method and device, so that the accuracy of fault determination is improved.
In a first aspect, an embodiment of the present application provides a network fault diagnosis method, including:
sending a fault diagnosis request message to target network element equipment in the edge cloud so that the target network element equipment processes a target service according to the fault diagnosis request message, updates an option field in the fault diagnosis request message according to a processing result, and generates a fault diagnosis response message according to the updated option field;
receiving a fault diagnosis response message which is sent by the target network element equipment and contains the updated option fields;
and determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message.
Optionally, if the updated option field includes a fault identifier, determining fault information in the edge cloud according to the updated option field in the fault diagnosis response message includes:
determining a target fault type corresponding to the target fault identification contained in the updated option field according to a pre-stored corresponding relationship between the fault identification and the fault type;
and determining fault information in the edge cloud according to the target fault type, wherein the fault information comprises a fault reason and a fault position.
Optionally, after the sending the fault diagnosis request packet to the target network element device in the edge cloud, the method further includes:
receiving a detection response message sent by the target network element equipment, wherein the detection response message is generated after the target service is processed, and the detection response message contains allowed maximum hop TTL;
correspondingly, the determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message includes:
determining forwarding link information according to TTL contained in the detection response message, wherein the forwarding link information represents the sending sequence of the fault diagnosis request message and the fault diagnosis response message in the edge cloud;
determining a target fault type corresponding to the target fault identification contained in the updated option field according to a pre-stored corresponding relationship between the fault identification and the fault type;
and determining fault information in the edge cloud according to the target fault type and the forwarding link information, wherein the fault information comprises a fault reason and a fault position.
Optionally, the sending the fault diagnosis request message to the target network element device in the edge cloud includes:
generating an initial fault diagnosis request message, and dyeing the option fields in the initial fault diagnosis request message to obtain a fault diagnosis request message;
and sending the fault diagnosis request message to target network element equipment in the edge cloud.
Optionally, the sending the fault diagnosis request message to the target network element device in the edge cloud, so that the target network element device processes the target service according to the fault diagnosis request message, and updates the option field in the fault diagnosis request message according to the processing result, includes:
sending a fault diagnosis request message to a virtual switch in the edge cloud, so that the virtual switch writes a fault identifier into an option field in the fault diagnosis request message according to the actual running state of the virtual switch, and sends the fault diagnosis request message containing the updated option field to a gateway;
after receiving the fault diagnosis request message containing the updated option field, the gateway writes a fault identifier into the updated option field according to the new actual running state of the gateway, and sends the fault diagnosis request message containing the newly updated option field to the virtual switch;
after receiving the fault diagnosis request message, the virtual switch writes the fault identification into the renewed option field according to the actual running state of the virtual switch, and sends the fault diagnosis request message containing the latest option field to the virtual client, so that the virtual client processes the target service according to the fault diagnosis request message, updates the option field in the fault diagnosis request message according to the processing result, and generates a fault diagnosis response message according to the updated option field.
Optionally, the receiving the fault diagnosis response message including the updated option field sent by the target network element device includes:
receiving a fault diagnosis response message sent by the virtual client through the virtual switch, the gateway and the virtual switch in sequence,
when the fault diagnosis response message is sent to the virtual switch, the gateway and the virtual switch, the gateway and the virtual switch update the updated option field in the fault diagnosis response message according to the actual running state.
Optionally, the receiving the fault diagnosis response message including the updated option field sent by the target network element device includes:
receiving a fault diagnosis response message sent by the virtual switch through the gateway and the virtual switch in sequence,
the fault diagnosis response message is generated after the virtual switch receives the fault diagnosis request message, a target virtual client is determined according to a client identifier contained in the fault diagnosis request message, and a target service is processed according to the fault diagnosis request message after the target virtual client is determined to be in a pre-stored monitoring list.
Optionally, before the sending the fault diagnosis request packet to the target network element device in the edge cloud, the method further includes:
receiving at least one network fault prompt sent by monitoring equipment;
and if the number of the network fault prompts exceeds a preset number threshold value or the execution priority of any target network fault prompt is higher than a preset priority, determining a detection task according to each network fault prompt and generating a fault diagnosis request message according to the detection task.
Optionally, before the sending the fault diagnosis request packet to the target network element device in the edge cloud, the method further includes:
and determining a detection task every other preset time, and generating a fault diagnosis request message according to the detection task.
In a second aspect, an embodiment of the present application provides a network fault diagnosis apparatus, including:
the sending module is used for sending a fault diagnosis request message to target network element equipment in the edge cloud so that the target network element equipment processes a target service according to the fault diagnosis request message, updates an option field in the fault diagnosis request message according to a processing result, and generates a fault diagnosis response message according to the updated option field;
a receiving module, configured to receive a fault diagnosis response message that includes the updated option field and is sent by the target network element device;
and the determining module is used for determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message.
The embodiment of the application provides a network fault diagnosis method and a device, after the scheme is adopted, a fault diagnosis request message can be sent to target network element equipment in an edge cloud, so that the target network element equipment can process a target service according to the fault diagnosis request message, update an option field in the fault diagnosis request message according to a processing result, generate a fault diagnosis response message according to the updated option field, return the fault diagnosis response message to a server, the server determines specific faults in the edge cloud according to information in the updated option field contained in the fault diagnosis response message, and can determine specific fault information in a network according to information written in the option field instead of determining packet loss points in a mode of updating the option field in the fault diagnosis request message according to the processing result, the accuracy of fault determination is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic architecture diagram of an application system of a network fault diagnosis method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a network fault diagnosis method according to an embodiment of the present application;
fig. 3 is a schematic diagram illustrating a network fault diagnosis method according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a network fault diagnosis apparatus according to an embodiment of the present application;
fig. 5 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the above-described drawings (if any) are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of including other sequential examples in addition to those illustrated or described. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The edge cloud is a cloud computing platform constructed on an edge infrastructure based on cloud computing and edge computing capabilities, and is a cloud platform with computing, network, storage, security and other capabilities at an edge position. And the edge cloud corresponds to the central cloud, which means that the cloud computing platform is relatively close to the terminal, and therefore the characteristics of being closer to the terminal equipment and having high data transmission efficiency with the terminal equipment are achieved. Therefore, the applications of the edge cloud are also more and more widespread, and the number of network element devices in the edge cloud is also more and more, for example, virtual switches, virtual routers, gateways, etc. may be included, and the problem troubleshooting of the edge cloud is also more and more complicated. In the prior art, a fault in the edge cloud may be determined through a fault diagnosis request message, and correspondingly, the fault diagnosis request message may be sent to each network element device in the edge cloud, so that the network element device mirrors the identified fault diagnosis request message after identifying the fault diagnosis request message, and then sends the mirrored fault diagnosis request message to an analysis system, so that the analysis system analyzes a message packet loss point. However, the analysis system can only determine the packet loss point, and cannot detect information such as specific packet loss reasons, so that the accuracy of fault determination is reduced.
Based on the technical problems, the method and the device can determine specific fault information according to the information in the option field in a mode of updating the option field in the fault diagnosis request message according to the processing result, and are not limited to determining packet loss points any more, so that the technical effect of improving the accuracy of fault determination is achieved.
Fig. 1 is a schematic architecture diagram of an application system of a network fault diagnosis method provided in an embodiment of the present application, and as shown in fig. 1, the application system may include: the server 101 and the target network element device 102 in the edge cloud, the server 101 may interact with the target network element device 102 through another network element device 103 in the edge cloud.
Further, a detection system and an analysis system may be deployed in the server 101, the detection system may send a fault diagnosis request message including an option field to the target network element device 102, the target network element device 102 may process the target service according to the fault diagnosis request message and update the processing result to the option field, then generate a fault diagnosis response message according to the updated option field and send the fault diagnosis response message to the detection system, and the detection system sends the fault diagnosis response message including the updated option field to the analysis system for analysis, thereby determining fault information in the edge cloud.
The target network element device 102 may be a virtual client, the server 101 may be a virtual machine, and the detection system and the analysis system are application programs deployed on the virtual machine.
The technical solution of the present application will be described in detail below with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.
Fig. 2 is a schematic flowchart of a network fault diagnosis method provided in this embodiment, where the method in this embodiment may be executed by the server 101. As shown in fig. 2, the method of this embodiment may include:
s201: and sending the fault diagnosis request message to target network element equipment in the edge cloud so that the target network element equipment processes the target service according to the fault diagnosis request message, updates the processing result to an option field in the fault diagnosis request message, and then generates a fault diagnosis response message according to the updated option field.
In this embodiment, when testing whether a network fault exists in the edge cloud or positioning a specific fault cause in the edge cloud, a fault diagnosis request message including an option field may be generated first, and then the fault diagnosis request message is sent to the target network element device through other network element devices in the edge cloud, so that the target network element device processes the target service according to the fault diagnosis request message, and after the processing is completed, a fault diagnosis response message is generated, and the fault diagnosis response message is sent to the server through other network element devices in the edge cloud. In the process of sending the fault diagnosis request message and the fault diagnosis response message, in order to locate a specific fault cause, an option field may be included in both the fault diagnosis request message and the fault diagnosis response message, and after each network element device receives the fault diagnosis request message or the fault diagnosis response message, the operation state of the network element device and the processing result of the target service are written in the option field, and then the specific fault cause and the fault position may be determined according to the content in the option field.
In addition, the generated fault diagnosis request message may adopt an IP address determined in advance from an IP pool. The IP address may be re-determined once every preset time.
The option field can adopt an expansion field of a standard protocol, so that the transmission requirement can be met, the field content can be set in a user-defined mode, and the option field does not conflict with other dyeing fields. For example, the OPTIONs field may be an OPTIONs extension field in the standard IP protocol.
In summary, the message in the prior art cannot record a specific failure cause, and only the packet loss point can be determined according to all finally received messages, but by writing the running state of the network element device and the processing result of the target service into the option field, the specific failure cause and the specific failure position can be determined subsequently according to the content in the option field, so that the accuracy of determining the failure is improved.
Further, sending a fault diagnosis request message to a target network element device in the edge cloud, so that the target network element device processes a target service according to the fault diagnosis request message, updates an option field in the fault diagnosis request message according to a processing result, and generates a fault diagnosis response message according to the updated option field, which may specifically include:
and sending a fault diagnosis request message to a virtual switch in the edge cloud so that the virtual switch writes a fault identifier into an option field in the fault diagnosis request message according to the actual running state of the virtual switch, and sending the fault diagnosis request message containing the updated option field to a gateway.
And after receiving the fault diagnosis request message containing the updated option field, the gateway writes the fault identification into the updated option field according to the actual running state of the gateway, and sends the fault diagnosis request message containing the newly updated option field to the virtual switch.
After receiving the fault diagnosis request message, the virtual switch writes the fault identification into the newly updated option field according to the new actual running state of the virtual switch, and sends the fault diagnosis request message containing the latest option field to the virtual client, so that the virtual client processes the target service according to the fault diagnosis request message, updates the latest option field in the received fault diagnosis request message, and generates a fault diagnosis response message according to the updated option field.
Specifically, the target network element device may be a virtual client, the edge cloud may include a virtual switch, a gateway, and other devices besides the virtual client, and in the process of sending the fault diagnosis request message to the virtual client, the fault diagnosis request message may be sent to the virtual switch first, and after receiving the fault diagnosis request message, the virtual switch may write the fault identifier into the option field according to its actual operating state. For example, if operating normally, an identifier 0 indicating no fault may be written into the option field; if there is a fault, a fault flag indicating the type of the fault may be written into the option field (for example, fault flag 1 indicates a packet loss fault, fault flag 2 indicates a network fault, etc.).
In addition, after the virtual switch writes the fault type, the fault diagnosis request message containing the updated option field can be sent to the gateway, and after receiving the fault diagnosis request message, the gateway can also write the fault identification into the option field according to the actual running state of the gateway. In addition, the number of the virtual clients is multiple, and the gateway can determine the virtual client to be forwarded from the multiple virtual clients, add the virtual client to the fault diagnosis request message, and then send the fault diagnosis request message containing the latest option field and the virtual client to be forwarded to the virtual switch. After receiving the fault diagnosis request message, the virtual switch writes the fault identification into the newly updated option field according to the new actual running state of the virtual switch, and sends the fault diagnosis request message containing the latest option field to the virtual client, so that the virtual client processes the target service according to the fault diagnosis request message, updates the latest option field in the received fault diagnosis request message, and generates a fault diagnosis response message according to the updated option field.
In summary, by means of updating the option field by each network element device that receives the fault diagnosis request message, the operating state of each network element device, the sending condition of the message, and the like can be determined, and subsequently, specific fault information can be directly determined according to the content in the option field, instead of determining a packet loss point, so that the accuracy and efficiency of determining the network fault are improved.
S202: and receiving a fault diagnosis response message which is sent by the target network element equipment and contains the updated option fields.
In this embodiment, after processing the target service and updating the option field in the fault diagnosis request message, the target network element device may generate a fault diagnosis response message including the updated option field, and send the fault diagnosis response message to the server through each network element device in the edge cloud.
Further, in an implementation manner, receiving a fault diagnosis response message that includes the updated option field and is sent by the target network element device may specifically include:
receiving a fault diagnosis response message sent by the virtual client through the virtual switch, the gateway and the virtual switch in sequence,
when the fault diagnosis response message is sent to the virtual switch, the gateway and the virtual switch, the gateway and the virtual switch update the updated option field in the fault diagnosis response message according to the actual running state.
Specifically, after the virtual switch receives the fault diagnosis response message sent by the virtual client, because the IP address in the original fault diagnosis response message does not correspond to the destination IP of the original service sending message, the virtual switch can send the received fault diagnosis response message sent by the virtual client to the gateway first, and then the received fault diagnosis response message is forwarded back to the virtual switch by the gateway, so that it can be ensured that the IP address in the original fault diagnosis response message corresponds to the destination IP of the original service sending message.
In summary, by means of updating the option field by each network element device that receives the fault diagnosis response message, the operation state of each network element device, the sending condition of the message, and the like can be determined, and then the specific fault reason and the fault position can be directly determined according to the content in the option field, thereby improving the accuracy and efficiency of determining the network fault.
In another implementation manner, receiving the fault diagnosis response message including the updated option field sent by the target network element device may specifically include:
and receiving a fault diagnosis response message sent by the virtual switch sequentially through the gateway and the virtual switch.
The fault diagnosis response message is generated after the virtual switch receives a fault diagnosis request message, a target virtual client is determined according to a client identifier contained in the fault diagnosis request message, and a target service is processed according to the fault diagnosis request message after the target virtual client is determined to be in a pre-stored monitoring list.
Specifically, in the virtual switch, for a packet sent by the virtual client, a triplet table may be generated by using the source IP address, the source port, and the protocol, and used as the client identifier. And starting service monitoring of the virtual client according to the three-tuple table, when detecting that the message accesses the monitored virtual client, the virtual switch can directly replace the virtual client to process corresponding service, the message does not reach the corresponding virtual client, the service message is prevented from directly reaching the client, and the user does not feel the service message, so that the use experience of the user is improved.
S203: and determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message.
In this embodiment, the fault information may include a fault cause and a fault location, and after receiving the fault diagnosis response message, the fault information may obtain a fault identifier from an updated option field included in the fault diagnosis response message, and then may determine a specific fault cause according to the fault identifier, and determine the fault location according to a specific device that generates the fault identifier.
Further, if the updated option field includes a fault identifier, determining fault information in the edge cloud according to the updated option field in the fault diagnosis response message may specifically include:
and determining a target fault type corresponding to the target fault identification contained in the updated option field according to a pre-stored corresponding relation between the fault identification and the fault type.
And determining fault information in the edge cloud according to the target fault type, wherein the fault information can comprise a fault reason and a fault position.
Specifically, the updated option field includes a target fault identifier, different target fault identifiers may correspond to different fault types, and after the target fault identifier is determined, the target fault type corresponding to the target fault identifier may be determined according to a pre-stored corresponding relationship between the fault identifier and the fault type. And determining fault information in the edge cloud according to the target fault type. The failure information includes a failure cause and a failure location. For example, if the target fault type is a packet loss fault, it may be further determined from the updated option field that the network element device a is an updated packet loss fault, that is, the fault cause is a packet loss, the fault location is the network element device a, and it may be determined that the network element device a has a packet loss fault according to the network element device a which updates the packet loss fault and the packet loss fault identifier.
In addition, after sending the fault diagnosis request message to the target network element device in the edge cloud, the method may further include:
and receiving a detection response message sent by the target network element device, wherein the detection response message is generated after the target service is processed, and the detection response message contains TTL (Time To Live, allowed maximum hop count).
Correspondingly, determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message may specifically include:
and determining forwarding link information according to TTL contained in the detection response message, wherein the forwarding link information represents the sending sequence of the fault diagnosis request message and the fault diagnosis response message in the edge cloud.
And determining a target fault type corresponding to the target fault identification contained in the updated option field according to a pre-stored corresponding relation between the fault identification and the fault type.
And determining fault information in the edge cloud according to the target fault type and the forwarding link information, wherein the fault information may include a fault reason and a fault position.
Specifically, after the target network element device receives the fault diagnosis request message sent by the server and completes the processing of the target service according to the fault diagnosis request message, a detection response message may be generated and sent back to the server, so that the server knows the sending condition of the fault diagnosis request message. In addition, when the server sends the fault diagnosis request message to the target network element device through the network element devices such as the virtual switch and the gateway, and the target network element device sends the fault diagnosis response message to the server through the network element devices such as the virtual switch and the gateway, each network element device can send the detection response message to the server.
Furthermore, the detection response message may include TTL, and the value of TTL may be reduced by one when the detection response message passes through a network element device, and through the TTL value, the server may concatenate forwarding conditions of the message to obtain forwarding link information, and a forwarding fault in the message forwarding process may be determined through the forwarding link information. Illustratively, the original forwarding link is from the server to the network element device a, then to the network element device B, then to the network element device C, and finally back to the server through the network element device C. The forwarding link information determined by the TTL value is from the server to the network element device a, then to the network element device C, and finally returns to the server by the network element device C, so that it can be determined that a forwarding failure has occurred, and details of the forwarding failure can also be determined.
In addition, the target fault type can be directly determined according to the target fault identification, namely the forwarding fault can be determined, and then the fault information is determined in a double determination mode by combining the detailed condition of the forwarding fault determined according to the forwarding link information, so that the accuracy of determining the fault information is improved.
In addition, the detection response message may further include an operation state and/or a message receiving condition of the network element device, and when the option field is updated, the option field may be updated according to the operation state and/or the message receiving condition of the network element device included in the detection response message, so that accuracy and efficiency of updating the option field are improved.
In addition, the method may further include:
and if the target fault type is no fault, generating a fault not found and whether to detect again or not.
And responding to the touch operation for confirming the redetection control, and re-executing the steps of sending the fault diagnosis request message to the target network element equipment in the edge cloud and the subsequent steps.
Specifically, if the target fault type is no fault, a situation that the fault is not detected may exist, and therefore, the operation and maintenance personnel can be reminded whether to need to perform retesting in a manner of generating and displaying whether the fault is not found or whether to perform retesting prompting. If the operation and maintenance personnel touch the re-detection control through touch operation, the re-detection is determined to be needed, and the steps of sending the fault diagnosis request message to the target network element equipment in the edge cloud and the subsequent steps can be re-executed. If the operation and maintenance personnel touch the control without re-detection through touch operation, the operation and maintenance personnel are indicated to give up re-detection, and it can be considered that no network fault occurs in the current edge cloud.
The mode of generating the retest prompt is used for the operation and maintenance personnel to select, so that the operation and maintenance personnel can know the detection condition in time, and the application experience of the operation and maintenance personnel is improved.
After the scheme is adopted, the fault diagnosis request message can be sent to the target network element equipment in the edge cloud, so that the target network element equipment can process the target service according to the fault diagnosis request message, the option field in the fault diagnosis request message is updated according to the processing result, the fault diagnosis response message is generated according to the updated option field and is returned to the server, the server determines the fault reason and the fault position in the edge cloud according to the information in the updated option field contained in the fault diagnosis response message, and the specific fault information can be determined according to the information written in the option field, not only the packet loss point is determined by means of updating the option field in the fault diagnosis request message according to the processing result, and the accuracy of fault determination is improved.
Based on the method of fig. 2, the present specification also provides some specific embodiments of the method, which are described below.
In another embodiment, the sending the fault diagnosis request message to the target network element device in the edge cloud may specifically include:
and generating an initial fault diagnosis request message, and dyeing the option fields in the initial fault diagnosis request message to obtain the fault diagnosis request message.
And sending the fault diagnosis request message to target network element equipment in the edge cloud.
In this embodiment, when determining a network fault in the edge cloud by using the fault diagnosis request message, the fault diagnosis request message may be dyed first, so that each network element device in the edge cloud may recognize the fault diagnosis request message and update the option field in the message, and subsequently, the fault cause and the fault type may be determined according to specific information in the updated option field.
In the prior art, when a detection message is dyed, different protocols may apply different dyeing methods, but all the protocols are applied to the existing fields (e.g., TOS field and SEQ field), so that different protocols may dye the same dyed field, and the dyeing modes of the common fields are the same, which causes the risk of field collision, thereby reducing the accuracy of fault determination.
In addition, in the prior art, the method further includes dyeing the service packet, and then forwarding the dyed service packet to each network element, after receiving the service packet, the network element may identify the dyed service packet, and package and send the dyed service packet, the corresponding forwarding information, the packet loss information, and the like to the database. The subsequent analysis system may obtain data from the database and determine fault information in the network based on the obtained data. However, when the service message is dyed, the service message can only be dyed in VXLAN (Virtual Extensible Local Area Network), and since the message in the underlay is a client service message and cannot be modified at will, only the scene of overlay access is supported, and the scene of underlay access is not supported, so that the flexibility of the application of the scene is reduced, and the accuracy of determining the fault is further influenced.
In addition, when the message is dyed, the message of the simulation user is dyed, so that the scenario of overlay access can be supported, the scenario of underlay access can also be supported, and the flexibility of the scenario application is improved.
In another embodiment, before the sending the fault diagnosis request message to the target network element device in the edge cloud, the method further includes:
and receiving at least one network fault prompt sent by the monitoring equipment.
And if the number of the network fault prompts exceeds a preset number threshold value or the execution priority of any target network fault prompt is higher than a preset priority, determining a detection task according to each network fault prompt and generating a fault diagnosis request message according to the detection task.
In this embodiment, the user side may start the monitoring device, and may monitor the network state in real time through the monitoring device, and when the network state is abnormal, generate a network failure prompt and send the network failure prompt to the server. After receiving the network failure prompt, the server may evaluate the urgency of the network failure prompt and determine whether to generate a probe task according to the urgency. Correspondingly, the degree of urgency of the network failure prompts can be evaluated according to the number of the network failure prompts, and the degree of urgency of the network failure prompts can also be evaluated according to the execution priority of the network failure prompts. If the degree of urgency requires maintenance, a detection task may be generated, and a fault diagnosis request message may be generated according to the detection task.
The detection task may include a detection object, a detection time, a detection method, and the like.
In conclusion, by the method, the network fault can be determined in time, and the normal operation of each network element device in the network is ensured.
In addition, in another embodiment, before the sending the fault diagnosis request message to the target network element device in the edge cloud, the method further includes:
and determining a detection task every other preset time, and generating a fault diagnosis request message according to the detection task.
In this embodiment, a preset time duration may be preset, a detection task is determined every other preset time duration, and a fault diagnosis request message is generated according to the detection task. The preset duration can be set according to the actual application scene in a user-defined mode, and the limitation is not performed in detail here.
By the method, the calculation amount of the server can be reduced, faults in the network can be discovered in time, and manpower and material resources are saved.
In addition, when initializing, the IP pool can be detected first, the fixed IP address to be applied is determined, the fixed IP address is issued to the network element equipment such as the virtual switch and the like, and the updating is carried out after the change.
Fig. 3 is a schematic diagram illustrating a principle of a network fault diagnosis method provided in an embodiment of the present application, as shown in fig. 3, in this embodiment, a user of a center cloud may enable a network monitoring function through a monitoring device, and initiate a detection task to a server in an edge cloud when receiving a network fault prompt, and a detection system in the server may generate a fault diagnosis request packet including an OPTION field according to the detection task, where the OPTION field may be an OPTION field in an IP protocol, and send a fault diagnosis request packet 1 including the OPTION field to a virtual switch.
After receiving the fault diagnosis request message 1 forwarded by the detection system, the virtual switch may respond to the detection response message to the detection system (for example, the detection response message may be encapsulated into VXLAN and directly returned to the detection system), and continue to forward the fault diagnosis request message 2 to the gateway. After receiving the fault diagnosis request message 2 forwarded by the virtual switch, the gateway responds to the detection response message to the detection system, and continues to forward the fault diagnosis request message 3 to the virtual switch. After receiving the fault diagnosis request message 3 forwarded by the gateway, the virtual switch may respond to the detection response message to the detection system, and continue to forward the fault diagnosis request message 4 to the virtual client. After receiving the fault diagnosis request message 4 forwarded by the virtual switch, the virtual client may process the target service according to the fault diagnosis request message 4, and after the processing is completed, send a fault diagnosis response message 5 to the virtual switch. After receiving the fault diagnosis response message 5 sent by the virtual client, the virtual switch can respond to the detection response message to the detection system, and continue to forward the fault diagnosis response message 6 to the gateway. After receiving the fault diagnosis response message 6 forwarded by the virtual switch, the gateway can respond to the detection response message to the detection system and continue to forward the fault diagnosis response message 7 to the virtual switch. After receiving the fault diagnosis response message 7 forwarded by the gateway, the virtual switch may respond to the detection response message to the detection system, and continue to forward the fault diagnosis response message 8 to the detection system. In addition, after receiving the fault diagnosis request message or the fault diagnosis response message, each network element device updates the option field included therein and writes the corresponding fault identifier.
In addition, after the detection system collects all messages (namely after all detection response messages and the fault diagnosis response message 8), the messages can be sent to the analysis system, the analysis system can analyze data in the IP-OPTION, the forwarding links are connected in series through TTL in the IP-OPTION to obtain forwarding link information, the fault type can be determined according to fault identification in an OPTION field in the fault diagnosis response message 8, and finally fault information in the edge cloud is determined.
In addition, the determined fault information in the edge cloud can be sent to the display device to be displayed.
In addition, in another embodiment, a network fault diagnosis method is also provided, where the method of this embodiment may be executed by the target network element device 102, and the method may include:
and receiving a fault diagnosis request message, wherein the fault diagnosis request message comprises an option field.
And processing the target service according to the fault diagnosis request message, updating the option field in the received fault diagnosis request message, and generating a fault diagnosis response message according to the updated option field.
And sending a fault diagnosis response message containing the updated option field to the server so that the server determines the fault information in the edge cloud according to the updated option field in the fault diagnosis response message.
After the scheme is adopted, the fault diagnosis request message can be sent to the target network element equipment in the edge cloud, so that the target network element equipment can process the target service according to the fault diagnosis request message and update the option field in the fault diagnosis request message, after the target network element equipment finishes processing the target service, the target network element equipment can generate a fault diagnosis response message containing the updated option field and return the fault diagnosis response message to the server, the server determines the fault information in the edge cloud according to the updated option field in the fault diagnosis response message, the dyeing is performed by adopting the custom expansion field of the standard protocol, the collision with other dyeing protocols can be avoided, the specific packet loss reason can be determined, and the accuracy of fault determination is improved.
Further, if the updated option field includes a fault identifier, the server determines fault information in the edge cloud according to the updated option field in the fault diagnosis response message, including:
and the server determines the target fault type corresponding to the target fault identification contained in the updated option field according to the corresponding relation between the pre-stored fault identification and the fault type.
And determining fault information in the edge cloud according to the target fault type.
In addition, the target network element device may also send a detection response message to the server, where the detection response message includes TTL, and after the target network element device receives the fault diagnosis request message, the target network element device may subtract one from the TTL, generate a detection response message according to the new TTL, and send the detection response message including the new TTL to the server. Wherein, the initial value of TTL may be set to 128.
Based on the same idea, an embodiment of the present specification further provides a device corresponding to the above method, and fig. 4 is a schematic structural diagram of the fault diagnosis device provided in the embodiment of the present application, and as shown in fig. 4, the device may include:
a sending module 401, configured to send a fault diagnosis request message to a target network element device in an edge cloud, so that the target network element device processes a target service according to the fault diagnosis request message, updates an option field in the fault diagnosis request message according to a processing result, and generates a fault diagnosis response message according to the updated option field.
A receiving module 402, configured to receive a fault diagnosis response message that includes the updated option field and is sent by the target network element device.
In this embodiment, the receiving module 402 is further configured to:
and sending a fault diagnosis request message to a virtual switch in the edge cloud so that the virtual switch writes a fault identifier into an option field in the fault diagnosis request message according to the actual running state of the virtual switch, and sending the fault diagnosis request message containing the updated option field to a gateway.
And after receiving the fault diagnosis request message containing the updated option field, the gateway writes the fault identification into the updated option field according to the actual running state of the gateway, and sends the fault diagnosis request message containing the newly updated option field to the virtual switch.
After receiving the fault diagnosis request message, the virtual switch writes the fault identification into the newly updated option field according to the new actual running state of the virtual switch, and sends the fault diagnosis request message containing the latest option field to the virtual client, so that the virtual client processes the target service according to the fault diagnosis request message, updates the option field in the fault diagnosis request message according to the processing result, and generates a fault diagnosis response message according to the updated option field.
Furthermore, in an implementation manner, the receiving module 402 is further configured to:
and receiving a fault diagnosis response message sent by the virtual client through the virtual switch, the gateway and the virtual switch in sequence.
When the fault diagnosis response message is sent to the virtual switch, the gateway and the virtual switch, the gateway and the virtual switch update the updated option field in the fault diagnosis response message according to the actual running state.
In another implementation manner, the receiving module 402 is further configured to:
and receiving a fault diagnosis response message sent by the virtual switch sequentially through the gateway and the virtual switch.
The fault diagnosis response message is generated after the virtual switch receives the fault diagnosis request message, a target virtual client is determined according to a client identifier contained in the fault diagnosis request message, and a target service is processed according to the fault diagnosis request message after the target virtual client is determined to be in a pre-stored monitoring list.
A determining module 403, configured to determine the fault information in the edge cloud according to the updated option field in the fault diagnosis response message.
In this embodiment, the determining module 403 is further configured to:
and determining the target fault type corresponding to the target fault identification contained in the updated option field according to the corresponding relation between the pre-stored fault identification and the fault type.
And determining fault information in the edge cloud according to the target fault type, wherein the fault information comprises a fault reason and a fault position.
In another implementation, the determining module 403 is further configured to:
and receiving a detection response message sent by the target network element equipment, wherein the detection response message is generated after the target service is processed, and the detection response message contains TTL.
And determining forwarding link information according to TTL contained in the detection response message, wherein the forwarding link information represents the sending sequence of the fault diagnosis request message and the fault diagnosis response message in the edge cloud.
And determining the target fault type corresponding to the target fault identification contained in the updated option field according to the corresponding relation between the pre-stored fault identification and the fault type.
And determining fault information in the edge cloud according to the target fault type and the forwarding link information, wherein the fault information comprises a fault reason and a fault position.
Furthermore, in another embodiment, the sending module is further configured to:
and generating an initial fault diagnosis request message, and dyeing the option fields in the initial fault diagnosis request message to obtain the fault diagnosis request message.
And sending the fault diagnosis request message to target network element equipment in the edge cloud.
Furthermore, the determining module 403 is further configured to:
and if the target fault type is no fault, generating a prompt for re-detecting whether no fault is found or not.
And responding to the touch operation for confirming the redetection control, and re-executing the steps of sending the fault diagnosis request message to the target network element equipment in the edge cloud and the subsequent steps.
Furthermore, in another embodiment, the determining module 403 is further configured to:
and receiving at least one network fault prompt sent by the monitoring equipment.
And if the number of the network fault prompts exceeds a preset number threshold value or the execution priority of any target network fault prompt is higher than a preset priority, determining a detection task according to each network fault prompt and generating a fault diagnosis request message according to the detection task.
Furthermore, in another embodiment, the determining module 403 is further configured to:
and determining a detection task every other preset time, and generating a fault diagnosis request message according to the detection task.
The apparatus provided in the embodiment of the present application can implement the method of the embodiment shown in fig. 2, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 5 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application, and as shown in fig. 5, a device 500 according to the embodiment includes: a processor 501, and a memory communicatively coupled to the processor. The processor 501 and the memory 502 are connected by a bus 503.
In a specific implementation, the processor 501 executes the computer executable instructions stored in the memory 502, so that the processor 501 executes the method in the above method embodiment.
For a specific implementation process of the processor 501, reference may be made to the above method embodiments, which implement the similar principle and technical effect, and this embodiment is not described herein again.
In the embodiment shown in fig. 5, it should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose processors, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor, or in a combination of hardware and software modules.
The memory may comprise high speed RAM memory and may also include non-volatile storage NVM, such as at least one disk memory.
The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.
The embodiment of the present application further provides a computer-readable storage medium, where a computer execution instruction is stored in the computer-readable storage medium, and when a processor executes the computer execution instruction, the network fault diagnosis method according to the embodiment of the foregoing method is implemented.
An embodiment of the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the network fault diagnosis method as described above is implemented.
The computer-readable storage medium may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. Readable storage media can be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. Of course, the readable storage medium may also be an integral part of the processor. The processor and the readable storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the readable storage medium may also reside as discrete components in the apparatus.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A method for network fault diagnosis, the method comprising:
sending a fault diagnosis request message to target network element equipment in the edge cloud so that the target network element equipment processes a target service according to the fault diagnosis request message, updates an option field in the fault diagnosis request message according to a processing result, and generates a fault diagnosis response message according to the updated option field;
receiving a fault diagnosis response message which is sent by the target network element equipment and contains the updated option fields;
and determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message.
2. The method according to claim 1, wherein if the updated option field includes a fault identifier, the determining fault information in the edge cloud according to the updated option field in the fault diagnosis response message includes:
determining a target fault type corresponding to the target fault identification contained in the updated option field according to a pre-stored corresponding relationship between the fault identification and the fault type;
and determining fault information in the edge cloud according to the target fault type, wherein the fault information comprises a fault reason and a fault position.
3. The method according to claim 1, wherein after the sending the fault diagnosis request message to the target network element device in the edge cloud, the method further comprises:
receiving a detection response message sent by the target network element equipment, wherein the detection response message is generated after the target service is processed, and the detection response message contains allowed maximum hop TTL;
correspondingly, the determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message includes:
determining forwarding link information according to TTL contained in the detection response message, wherein the forwarding link information represents the sending sequence of the fault diagnosis request message and the fault diagnosis response message in the edge cloud;
determining a target fault type corresponding to the target fault identification contained in the updated option field according to a pre-stored corresponding relationship between the fault identification and the fault type;
and determining fault information in the edge cloud according to the target fault type and the forwarding link information, wherein the fault information comprises a fault reason and a fault position.
4. The method of claim 1, wherein the sending the fault diagnosis request message to the target network element device in the edge cloud comprises:
generating an initial fault diagnosis request message, and dyeing the option fields in the initial fault diagnosis request message to obtain a fault diagnosis request message;
and sending the fault diagnosis request message to target network element equipment in the edge cloud.
5. The method according to any one of claims 1 to 4, wherein the sending a fault diagnosis request message to a target network element device in an edge cloud, so that the target network element device processes a target service according to the fault diagnosis request message, updates an option field in the fault diagnosis request message according to a processing result, and generates a fault diagnosis response message according to the updated option field, includes:
sending a fault diagnosis request message to a virtual switch in the edge cloud, so that the virtual switch writes a fault identifier into an option field in the fault diagnosis request message according to the actual running state of the virtual switch, and sends the fault diagnosis request message containing the updated option field to a gateway;
after receiving the fault diagnosis request message containing the updated option field, the gateway writes the fault identification into the updated option field according to the actual running state of the gateway, and sends the fault diagnosis request message containing the newly updated option field to the virtual switch;
after receiving the fault diagnosis request message, the virtual switch writes the fault identification into the newly updated option field according to the new actual running state of the virtual switch, and sends the fault diagnosis request message containing the latest option field to the virtual client, so that the virtual client processes the target service according to the fault diagnosis request message, updates the option field in the fault diagnosis request message according to the processing result, and generates a fault diagnosis response message according to the updated option field.
6. The method according to claim 5, wherein the receiving the fault diagnosis response message containing the updated option field sent by the target network element device comprises:
receiving a fault diagnosis response message sent by the virtual client through the virtual switch, the gateway and the virtual switch in sequence,
when the fault diagnosis response message is sent to the virtual switch, the gateway and the virtual switch, the gateway and the virtual switch update the updated option field in the fault diagnosis response message according to the actual running state.
7. The method according to claim 5, wherein the receiving the fault diagnosis response message containing the updated option field sent by the target network element device comprises:
receiving a fault diagnosis response message sent by the virtual switch through the gateway and the virtual switch in sequence,
the fault diagnosis response message is generated after the virtual switch receives the fault diagnosis request message, a target virtual client is determined according to a client identifier contained in the fault diagnosis request message, and a target service is processed according to the fault diagnosis request message after the target virtual client is determined to be in a pre-stored monitoring list.
8. The method according to any one of claims 1 to 4, wherein before the sending the fault diagnosis request message to the target network element device in the edge cloud, the method further comprises:
receiving at least one network fault prompt sent by monitoring equipment;
and if the number of the network fault prompts exceeds a preset number threshold value or the execution priority of any target network fault prompt is higher than a preset priority, determining a detection task according to each network fault prompt and generating a fault diagnosis request message according to the detection task.
9. The method according to any one of claims 1 to 4, wherein before the sending the fault diagnosis request message to the target network element device in the edge cloud, the method further comprises:
and determining a detection task every other preset time, and generating a fault diagnosis request message according to the detection task.
10. A network fault diagnosis apparatus, characterized in that the apparatus comprises:
the sending module is used for sending a fault diagnosis request message to target network element equipment in the edge cloud so that the target network element equipment processes a target service according to the fault diagnosis request message, updates an option field in the fault diagnosis request message according to a processing result, and generates a fault diagnosis response message according to the updated option field;
a receiving module, configured to receive a fault diagnosis response message that includes the updated option field and is sent by the target network element device;
and the determining module is used for determining the fault information in the edge cloud according to the updated option field in the fault diagnosis response message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210302940.0A CN114866398B (en) | 2022-03-24 | 2022-03-24 | Network fault diagnosis method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210302940.0A CN114866398B (en) | 2022-03-24 | 2022-03-24 | Network fault diagnosis method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114866398A true CN114866398A (en) | 2022-08-05 |
| CN114866398B CN114866398B (en) | 2024-01-09 |
Family
ID=82629342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210302940.0A Active CN114866398B (en) | 2022-03-24 | 2022-03-24 | Network fault diagnosis method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114866398B (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101141313A (en) * | 2006-09-08 | 2008-03-12 | 中兴通讯股份有限公司 | Method of positioning communication fault location of equipment monitoring system |
| WO2009071030A1 (en) * | 2007-11-30 | 2009-06-11 | Huawei Technologies Co., Ltd. | Method for reporting device information, system and device for obtaining device information |
| CN101605063A (en) * | 2008-06-10 | 2009-12-16 | 鸿富锦精密工业（深圳）有限公司 | Network fault positioning system and method |
| CN105743711A (en) * | 2016-04-13 | 2016-07-06 | 华为技术有限公司 | Fault detection method and device for network path and network equipment |
| US20160248649A1 (en) * | 2013-10-25 | 2016-08-25 | Huawei Device Co., Ltd. | Fault Diagnosis Method, Device, and Fault Diagnosis System |
| CN106464590A (en) * | 2015-11-27 | 2017-02-22 | 华为技术有限公司 | Method and apparatus for obtaining path information |
| US20180123873A1 (en) * | 2015-06-29 | 2018-05-03 | Huawei Technologies Co., Ltd. | Service fault locating method and apparatus |
| WO2018145560A1 (en) * | 2017-02-13 | 2018-08-16 | 中兴通讯股份有限公司 | Method and device for link failure diagnosis |
| CN109032825A (en) * | 2018-06-06 | 2018-12-18 | 阿里巴巴集团控股有限公司 | A kind of fault filling method, device and equipment |
| JP2019103117A (en) * | 2017-11-30 | 2019-06-24 | 日本電気株式会社 | Network management device, method, and program |
| CN112187584A (en) * | 2020-09-30 | 2021-01-05 | 腾讯科技（深圳）有限公司 | Path fault detection method, system, server and storage medium |
| CN113377590A (en) * | 2021-06-09 | 2021-09-10 | 东软睿驰汽车技术（沈阳）有限公司 | Fault diagnosis method and device, vehicle-mounted terminal and medium |
| CN113708995A (en) * | 2021-08-20 | 2021-11-26 | 深圳市风云实业有限公司 | Network fault diagnosis method, system, electronic equipment and storage medium |
| CN113794633A (en) * | 2021-11-17 | 2021-12-14 | 鹏城实验室 | Zero-packet-loss rerouting method and routing system |
| CN114205221A (en) * | 2020-08-26 | 2022-03-18 | 北京华为数字技术有限公司 | Fault query method and device |
-
2022
- 2022-03-24 CN CN202210302940.0A patent/CN114866398B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101141313A (en) * | 2006-09-08 | 2008-03-12 | 中兴通讯股份有限公司 | Method of positioning communication fault location of equipment monitoring system |
| WO2009071030A1 (en) * | 2007-11-30 | 2009-06-11 | Huawei Technologies Co., Ltd. | Method for reporting device information, system and device for obtaining device information |
| CN101605063A (en) * | 2008-06-10 | 2009-12-16 | 鸿富锦精密工业（深圳）有限公司 | Network fault positioning system and method |
| US20160248649A1 (en) * | 2013-10-25 | 2016-08-25 | Huawei Device Co., Ltd. | Fault Diagnosis Method, Device, and Fault Diagnosis System |
| US20180123873A1 (en) * | 2015-06-29 | 2018-05-03 | Huawei Technologies Co., Ltd. | Service fault locating method and apparatus |
| CN106464590A (en) * | 2015-11-27 | 2017-02-22 | 华为技术有限公司 | Method and apparatus for obtaining path information |
| WO2017088190A1 (en) * | 2015-11-27 | 2017-06-01 | 华为技术有限公司 | Method and apparatus for acquiring path information |
| CN105743711A (en) * | 2016-04-13 | 2016-07-06 | 华为技术有限公司 | Fault detection method and device for network path and network equipment |
| WO2018145560A1 (en) * | 2017-02-13 | 2018-08-16 | 中兴通讯股份有限公司 | Method and device for link failure diagnosis |
| JP2019103117A (en) * | 2017-11-30 | 2019-06-24 | 日本電気株式会社 | Network management device, method, and program |
| CN109032825A (en) * | 2018-06-06 | 2018-12-18 | 阿里巴巴集团控股有限公司 | A kind of fault filling method, device and equipment |
| CN114205221A (en) * | 2020-08-26 | 2022-03-18 | 北京华为数字技术有限公司 | Fault query method and device |
| CN112187584A (en) * | 2020-09-30 | 2021-01-05 | 腾讯科技（深圳）有限公司 | Path fault detection method, system, server and storage medium |
| CN113377590A (en) * | 2021-06-09 | 2021-09-10 | 东软睿驰汽车技术（沈阳）有限公司 | Fault diagnosis method and device, vehicle-mounted terminal and medium |
| CN113708995A (en) * | 2021-08-20 | 2021-11-26 | 深圳市风云实业有限公司 | Network fault diagnosis method, system, electronic equipment and storage medium |
| CN113794633A (en) * | 2021-11-17 | 2021-12-14 | 鹏城实验室 | Zero-packet-loss rerouting method and routing system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114866398B (en) | 2024-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111008380B (en) | Method and device for detecting industrial control system bugs and electronic equipment | |
| CN110505248B (en) | Method and system for positioning intranet NAT flow | |
| US10855546B2 (en) | Systems and methods for non-intrusive network performance monitoring | |
| CN109150587B (en) | Maintenance method and device | |
| CN109787865B (en) | Method, system, switch and storage medium for verifying upgrading condition | |
| CN110737565A (en) | data monitoring method, device, electronic equipment and storage medium | |
| CN113179295A (en) | Message processing method and device | |
| CN114866398B (en) | Network fault diagnosis method and device | |
| CN110474821B (en) | Node fault detection method and device | |
| CN112464238A (en) | Vulnerability scanning method and electronic equipment | |
| CN107547308B (en) | Message mirroring method and device, and controller in Software Defined Network (SDN) | |
| CN115665035A (en) | Information processing method and device, first node and storage medium | |
| CN113904972B (en) | Path detection method and device, controller and PE (polyethylene) equipment | |
| CN111131198B (en) | Updating method and device for network security policy configuration | |
| CN109962820B (en) | Detection method and detection platform of cloud platform | |
| CN113986676A (en) | Server health check method and device, electronic equipment and storage medium | |
| CN107919980B (en) | Evaluation method and device for clustered system | |
| CN111190701A (en) | Method and device for detecting data migration integrity of virtualization platform | |
| CN112181802A (en) | Test method and device | |
| CN111193639A (en) | Network quality detection processing method and system | |
| CN111506507A (en) | Business service state detection method and device, electronic equipment and storage medium | |
| CN110209470A (en) | Heartbeat detecting method, system, equipment and the medium of virtual machine | |
| WO2023226601A1 (en) | Anomaly processing method and apparatus for heterogeneous acceleration resource, and storage medium and electronic apparatus | |
| CN114184361B (en) | Method, device and medium for detecting information of switch fan | |
| CN111615124B (en) | Service detection method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |