CN112751728A - Link health state monitoring method and device - Google Patents

Link health state monitoring method and device Download PDF

Info

Publication number
CN112751728A
CN112751728A CN202011593812.3A CN202011593812A CN112751728A CN 112751728 A CN112751728 A CN 112751728A CN 202011593812 A CN202011593812 A CN 202011593812A CN 112751728 A CN112751728 A CN 112751728A
Authority
CN
China
Prior art keywords
message
physical link
monitoring
abnormal
link
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.)
Pending
Application number
CN202011593812.3A
Other languages
Chinese (zh)
Inventor
姜吉祥
孙艳杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou DPTech Technologies Co Ltd
Original Assignee
Hangzhou DPTech Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hangzhou DPTech Technologies Co Ltd filed Critical Hangzhou DPTech Technologies Co Ltd
Priority to CN202011593812.3A priority Critical patent/CN112751728A/en
Publication of CN112751728A publication Critical patent/CN112751728A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/50Testing arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • H04L47/125Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering

Abstract

The application provides a method and a device for monitoring link health status, the method is applied to a load balancing device, the load balancing device is used for realizing load sharing of flow for a plurality of physical links, and the method can include the following steps: acquiring messages flowing through each physical link; when determining that an abnormal message exists on any physical link, sending a monitoring message through the any physical link to monitor the health state of the any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility. By the technical scheme, the health state of the physical link can be determined more timely, the accuracy of monitoring the health state of the link is improved, and unnecessary resource waste is reduced.

Description

Link health state monitoring method and device
Technical Field
The present application relates to the field of network communication technologies, and in particular, to a method and an apparatus for monitoring a link health status.
Background
In order to provide better network service, a plurality of physical links can be reasonably applied by using load balancing equipment to carry out load sharing on traffic. In the process of load sharing, the load balancing device needs to monitor the health status of each physical link to ensure that traffic is scheduled to the physical link in a healthy state.
In the related art, load balancing equipment periodically sends monitoring messages to a physical link to be monitored according to a fixed time interval, if a reply message aiming at the monitoring messages can be received within a preset time, the physical link is determined to be in a healthy state, and if the reply message aiming at the monitoring messages cannot be received within the preset time, the physical link is determined to be in a fault state. Because the period for sending the monitoring message is fixed, the load balancing device cannot monitor the health state of the physical link at the time point in the period interval for sending the monitoring message, the monitoring timeliness is low, and for the physical link with a stable health state, if the physical link is monitored in a short period, the resource waste is caused.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for monitoring a link health status, so as to obtain a physical link health status in time.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of the present application, a method for monitoring a link health state is provided, which is applied to a load balancing device, where the load balancing device is configured to implement load sharing of traffic for multiple physical links, and the method includes:
acquiring messages flowing through each physical link;
when determining that an abnormal message exists on any physical link, sending a monitoring message through the any physical link to monitor the health state of the any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility.
According to a second aspect of the present application, a link health status monitoring apparatus is provided, which is applied to a load balancing device, where the load balancing device is configured to implement load sharing of traffic for multiple physical links, and includes:
an obtaining unit, configured to obtain a packet flowing through each physical link;
the monitoring unit is used for sending a monitoring message through any physical link to monitor the health state of any physical link when the abnormal message is determined to exist on any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility.
According to a third aspect of the present application, there is provided an electronic device comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method as described in the embodiments of the first aspect above by executing the executable instructions.
According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method as described in the embodiments of the first aspect above.
According to the technical scheme, the messages flowing through the physical links are counted, when the abnormal messages are detected on one physical link and the physical link is judged to be abnormal, the physical link is subjected to health monitoring, the health state of the physical link can be determined more timely, the accuracy of monitoring the health state of the link is improved, and unnecessary resource waste is reduced.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a flow chart illustrating a method of monitoring link health status according to an exemplary embodiment of the present application;
FIG. 2 is a schematic diagram of a network architecture of a link health status monitoring system to which an embodiment of the present application is applied;
FIG. 3 is a detailed flow chart illustrating a method of monitoring link health status according to an exemplary embodiment of the present application;
FIG. 4 is a schematic diagram illustrating a link health status monitoring electronics according to an exemplary embodiment of the present application;
fig. 5 is a block diagram illustrating a link health status monitoring apparatus according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Next, examples of the present application will be described in detail.
Fig. 1 is a flowchart illustrating a method for monitoring a link health status according to an exemplary embodiment of the present application. As shown in fig. 1, the method is applied to a load balancing device, where the load balancing device is configured to implement load sharing of traffic for multiple physical links, and may include the following steps:
step 102: and acquiring messages flowing through each physical link.
The load balancing device receives the flow and distributes the flow to different physical links through a certain scheduling algorithm, thereby realizing the load sharing of the flow. The load balancing device needs to monitor the health status of each physical link to ensure that traffic is scheduled to the physical link with a healthy status, so that an available link with a higher priority can be selected according to a corresponding scheduling algorithm in the traffic scheduling process to realize traffic forwarding.
In an embodiment, the load balancing device obtains messages flowing through each physical link, counts the messages of each physical link according to the protocol type and/or the destination address of the obtained messages, and classifies the messages flowing through each physical link and having the same protocol type and/or the same destination address. By counting the acquired messages, the protocol type and/or the destination address distribution condition of the messages on the link can be acquired more intuitively, and unnecessary repeated monitoring on the link is reduced when abnormal messages of the same protocol type and/or the same destination address are acquired subsequently.
Step 104: when determining that an abnormal message exists on any physical link, sending a monitoring message through the any physical link to monitor the health state of the any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility.
In the link health status monitoring method of the related art, the monitoring target, the monitoring protocol, the monitoring message content and the sending time interval of the monitoring message are all configured in advance manually. The load balancing equipment sends a monitoring message, and if a reply message aiming at the monitoring message is received within a preset time length, the physical link is determined to be in a healthy state; and if the reply message aiming at the monitoring message is not received within the preset time length, determining that the physical link is in a fault state.
In an embodiment, an exception packet is predefined, where the exception packet is a packet that may flow through a physical link when the physical link has an exception. For example, when the TCP protocol connection fails, the TCP reset packet flows through the physical link, so the TCP reset packet can be predefined as an abnormal packet; when the destination address of the UDP packet sent by the load balancing device is unreachable, the ICMP unreachable packet may flow through the physical link, so the ICMP unreachable packet may be predefined as an abnormal packet. In fact, all messages that may flow through the physical link when the physical link is in a failure state may be applied to this, and this is not limited in this application. By analyzing the message flowing through the link and determining whether to perform health monitoring on the physical link according to whether an abnormal message exists on the physical link, the load balancing equipment can timely perform health state monitoring on the physical link when detecting that the abnormal message exists on the physical link and accordingly judging that the physical link is possibly abnormal, real-time monitoring on the health state of the physical link is achieved to a certain extent, and the physical link is not subjected to health monitoring when the abnormal message is not monitored, namely the physical link is not abnormal, so that unnecessary resource waste can be reduced.
In an embodiment, the load balancing device counts the common characteristics of the abnormal messages; and generating a monitoring message matched with the common characteristic so as to monitor the health state of any physical link. Wherein the common features include: the protocol type and/or the destination address of the message. The generating of the monitoring message matched with the common characteristic includes: when the common characteristic of the abnormal message is a protocol type, generating a monitoring message which has the same protocol type as the abnormal message; and when the common characteristic of the abnormal message is a destination address, generating a monitoring message with the same destination address as the abnormal message. For example, when the abnormal message flowing through the physical link is counted and obtained as a TCP reset message, a monitoring message is generated as a TCP connection request message; and when the abnormal message flowing through the physical link is counted as the ICMP destination unreachable message, generating a playback request message of which the monitoring message is the same as the destination address of the ICMP destination unreachable message. The method is different from the monitoring messages which are manually configured in advance in the prior art, and the monitoring messages which are matched with the common characteristics of the abnormal messages are automatically generated by counting the common characteristics of the abnormal messages, so that the monitoring messages sent by the load balancing equipment are more flexible and have higher pertinence, all protocol types and destination addresses of the flow passing through the link can be covered, and the health states of the physical link aiming at all protocol types and destination addresses can be reflected.
In one embodiment, load data of any one of the physical links is acquired; and determining the sending frequency and the sending quantity of the monitoring messages according to the load data, so that the load data when any physical link sends the monitoring messages does not exceed the preset load data. For example, if the load data of the physical link is less than 30%, the sending number and sending frequency of the monitoring messages can be properly increased; if the load data of the physical link is greater than 80%, the sending number and the sending frequency of the monitoring messages can be properly reduced. By counting the load condition of the physical link, the sending frequency and the sending quantity of the monitoring messages can be adjusted and controlled in time, the load pressure of the physical link is prevented from being overlarge, the monitoring efficiency of the physical link is improved, and the influence on the normal flow forwarding work of the physical link can be reduced.
In an embodiment, a physical link is provided with a fixed bandwidth, the traffic of any physical link is counted, and the load data of any physical link is determined according to the traffic and the bandwidth. For example, if the physical link is configured with a fixed bandwidth of 80Mbps, the flow rate flowing through the link per second may be up to 10MByte/s, and the current flow rate of the physical link is 2MByte/s, which can be calculated to obtain that the load data of the physical link is 20%. In fact, all methods for obtaining load data can be applied to this, and the present application is not limited to this. Load data of the physical link is calculated by counting the flow of the physical link, so that the sending frequency and the sending quantity of monitoring messages can be adjusted conveniently and timely, and more sufficient data support can be provided for subsequent flow scheduling.
According to the technical scheme, the physical link health state monitoring method and the physical link health state monitoring system have the advantages that the messages flowing through the physical link are analyzed, the physical link health state is monitored when the abnormal messages are determined, the physical link health state monitoring can have higher timeliness and reduce resource waste, the specific content of the monitored messages can be flexibly changed according to the abnormal messages, the physical link health state can be monitored in a more targeted mode, and the monitoring accuracy is improved.
Fig. 2 is a schematic diagram of a network architecture of a link health status monitoring system to which an embodiment of the present invention is applied. As shown in fig. 2, the link health monitoring system may include a client 21, a load balancing device 22, and a server cluster 23. The server cluster 23 includes a plurality of servers, such as the server 23a, the server 23b, and the server 23c shown in fig. 2, but the number of servers included in the server cluster 23 is not limited in the present application. The load balancing device 22 performs health monitoring on each physical link between itself and each server in the server cluster 23 to determine whether each physical link is in a healthy state. The client 21 sends the traffic to the load balancing device 22, and the load balancing device 23 selects a healthy link to send the traffic to each server in the server cluster 23, so as to implement load sharing of the traffic. It should be noted that the network architecture illustrated in fig. 2 is only an illustration of the simplest network architecture for implementing the present application, and the practical application may be expanded according to the actual situation.
In the technical solution of the present application, the health status of each physical link between the load balancing device 22 and each server in the server cluster 23 can be obtained in time by improving the health status monitoring process of each physical link, which is described in detail below with reference to fig. 3. Fig. 3 is a detailed flowchart illustrating a method for monitoring a link health status according to an exemplary embodiment of the present application. As shown in fig. 3, the process of the load balancing device 22 performing health status monitoring on the physical link between the load balancing device and the server cluster 23 includes the following steps:
step 301, the load balancing device 22 obtains messages flowing through each physical link between itself and the server cluster 23.
In this embodiment, the traffic received by the load balancing device 22 and sent by the client 21 is forwarded to each server in the server cluster 23 through a plurality of physical links, so as to implement load sharing of the traffic. There are physical links between the load balancing device 22 and each server in the server cluster 23, and traffic can be sent to each server through each physical link. And acquiring messages flowing through each physical link.
Step 302, when the load balancing device 22 determines that an abnormal packet exists on any physical link, the common characteristics of the abnormal packet are counted.
In this embodiment, the load balancing device 22 defines an abnormal packet for indicating that there is an abnormal possibility in the physical link in advance, and can determine whether there is an abnormal packet in each physical link by analyzing the acquired packet flowing through each physical link.
For example, it is analyzed that abnormal messages, such as a TCP re-request message identified as [ TCP dup ack ], a TCP Fast Retransmission message identified as [ TCP Fast Retransmission ], and a TCP timeout Retransmission message identified as [ TCP Retransmission ], exist on the physical link between the load balancing device 22 and the server 23a, and the protocol types of the abnormal messages are TCP protocols.
Step 303, the load balancing device 22 generates a monitoring message matched with the common characteristic.
In this embodiment, the load balancing device 22 generates a monitoring packet matching the common characteristic of the abnormal packet according to the common characteristic of the abnormal packet obtained by statistics.
According to the above example, the protocol types of the abnormal messages on the physical link between the load balancing device 22 and the server 23a are both TCP protocols, and the load balancing device 22 generates a TCP connection request message whose protocol type is also TCP protocol and whose flag bit is [ SYN ] sequence number Seq is 0 as a monitoring message.
And step 304, counting the flow of any physical link, and determining the load data of any physical link according to the flow and the bandwidth.
In this embodiment, the physical link has a fixed bandwidth, for example, the fixed bandwidth configured for the physical link is 80Mbps, the flow rate flowing through the link per second may be up to 10MByte/s, the current flow rate of the physical link is obtained by statistics as 2MByte/s, and it can be calculated that the load data of the physical link between the load balancing device 22 and the server 23a is 20%.
In step 305, the load balancing device 22 determines the sending frequency and the sending number of the monitoring packets according to the load data, so that the load data when the monitoring packets are sent by any physical link does not exceed the preset load data.
In this embodiment, a standard sending frequency is configured in advance to send the monitoring messages every 10s, the load data of the physical link between the load balancing device 22 and the server 23a is 20%, the load is small, the sending number and the sending frequency of the monitoring messages can be appropriately increased, and the load balancing device 22 automatically sets the sending frequency to send the monitoring messages every 8 s.
Step 306, the load balancing device 22 sends the monitoring packet.
In this embodiment, the load balancing apparatus 22 sends a TCP connection request packet with a flag bit of [ SYN ] sequence number Seq equal to 0 every 8s to flow through the physical link between itself and the server 23 a.
Step 307, determining the health status of the physical link according to the reply message condition received by the load balancing device 22.
In this embodiment, after receiving the monitoring message, the server 23a returns, as a reply message, an acknowledgement message with a flag bit of [ SYN, ACK ] and a sequence number of Seq ═ 0 and an acknowledgement number of ACK ═ x +1 to the load balancing device 22, where the acknowledgement message may indicate that the server 23a confirms that the sequence number of the TCP connection request message sent by the load balancing device 22 is valid, and the server 23a can normally receive the data sent by the load balancing device 22 and agree to create a new connection. If the load balancing device 22 receives a reply message for the TCP connection request within a preset time, it determines that the physical link is in a healthy state; if the load balancing device 22 does not receive the reply message for the TCP connection request within the preset time, it determines that the physical link is in a failure state.
Corresponding to the method embodiments, the present specification also provides an embodiment of an apparatus.
Fig. 4 is a schematic structural diagram of an electronic device for monitoring a link health status according to an exemplary embodiment of the present application. Referring to fig. 4, at the hardware level, the electronic device includes a processor 402, an internal bus 404, a network interface 406, a memory 408, and a non-volatile memory 410, but may also include hardware required for other services. The processor 402 reads the corresponding computer program from the non-volatile memory 410 into the memory 408 and runs it, forming a means for solving the problem of untimely monitoring at a logical level. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Fig. 5 is a block diagram illustrating a link health status monitoring apparatus according to an exemplary embodiment of the present application. Referring to fig. 5, the apparatus comprises an acquisition unit 502 and a monitoring 504, wherein:
the obtaining unit 502 is configured to obtain messages flowing through each physical link.
The monitoring unit 504 is configured to, when it is determined that an abnormal packet exists on any physical link, send a monitoring packet through the any physical link to monitor a health state of the any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility.
Optionally, the apparatus further comprises:
a statistic unit 506 configured to count common features of the abnormal packets;
a generating unit 508, configured to generate a monitoring packet matched to the common characteristic, so as to perform health status monitoring on any physical link.
Optionally, the common characteristic includes a protocol type and/or a destination address of the packet.
Optionally, the generating the monitoring packet matched with the common feature includes: when the common characteristic of the abnormal message is a protocol type, generating a monitoring message which has the same protocol type as the abnormal message; and when the common characteristic of the abnormal message is a destination address, generating a monitoring message with the same destination address as the abnormal message.
Optionally, when the common feature of the abnormal packet is a protocol type, generating a monitoring packet having the same protocol type as the abnormal packet includes: when the abnormal message is a reset message of a TCP protocol, generating a TCP connection request message as the monitoring message; when the common characteristic of the abnormal message is a destination address, generating a monitoring message having the same destination address as the abnormal message, including: and when the abnormal message is an ICMP (Internet control protocol) destination unreachable message corresponding to a specific destination address, generating a display back request message aiming at the specific destination address as the monitoring message.
Optionally, the apparatus further comprises:
a calculating unit 510 configured to obtain load data of the any physical link;
a determining unit 512, configured to determine, according to the load data, a sending frequency and a sending number of the monitoring packets, so that the load data when the monitoring packets are sent by any physical link does not exceed preset load data.
Optionally, the determining the sending frequency and the sending number of the monitoring packets according to the load data includes: counting the flow of any physical link; and determining the load data of any physical link according to the flow and the bandwidth.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium, e.g. a memory, comprising instructions executable by a processor of a link health monitoring device to implement a method as described in any of the above embodiments, such as the method may comprise:
acquiring messages flowing through each physical link; when determining that an abnormal message exists on any physical link, sending a monitoring message through the any physical link to monitor the health state of the any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility.
The non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc., which is not limited in this application.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (10)

1. A method for monitoring link health status is applied to a load balancing device, and the load balancing device is used for realizing load sharing of traffic for a plurality of physical links, and the method comprises the following steps:
acquiring messages flowing through each physical link;
when determining that an abnormal message exists on any physical link, sending a monitoring message through the any physical link to monitor the health state of the any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility.
2. The method of claim 1, further comprising:
counting the common characteristics of the abnormal messages;
and generating a monitoring message matched with the common characteristic so as to monitor the health state of any physical link.
3. The method of claim 2, wherein the common features comprise:
the protocol type and/or the destination address of the message.
4. The method of claim 3, wherein the generating the monitoring message matching the common characteristic comprises:
when the common characteristic of the abnormal message is a protocol type, generating a monitoring message which has the same protocol type as the abnormal message;
and when the common characteristic of the abnormal message is a destination address, generating a monitoring message with the same destination address as the abnormal message.
5. The method of claim 4,
when the common characteristic of the abnormal message is a protocol type, generating a monitoring message having the same protocol type as the abnormal message, including: when the abnormal message is a reset message of a TCP protocol, generating a TCP connection request message as the monitoring message;
when the common feature of the abnormal message is a destination address, generating a monitoring message having the same destination address as the abnormal message, including: and when the abnormal message is an ICMP (Internet control protocol) destination unreachable message corresponding to a specific destination address, generating a display back request message aiming at the specific destination address as the monitoring message.
6. The method of claim 1, further comprising:
acquiring load data of any physical link;
and determining the sending frequency and the sending quantity of the monitoring messages according to the load data, so that the load data when any physical link sends the monitoring messages does not exceed the preset load data.
7. The method of claim 6, wherein any physical link is configured with a fixed bandwidth; the acquiring load data of any physical link includes:
counting the flow of any physical link;
and determining the load data of any physical link according to the flow and the bandwidth.
8. A monitoring device for link health status is characterized in that a load balancing device is applied, and the load balancing device is used for realizing load sharing of traffic for a plurality of physical links, and the device comprises:
an obtaining unit, configured to obtain a packet flowing through each physical link;
the monitoring unit is used for sending a monitoring message through any physical link to monitor the health state of any physical link when the abnormal message is determined to exist on any physical link; the abnormal message is a predefined message used for indicating that the physical link has abnormal possibility.
9. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 1-7 by executing the executable instructions.
10. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method according to any one of claims 1-7.
CN202011593812.3A 2020-12-29 2020-12-29 Link health state monitoring method and device Pending CN112751728A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011593812.3A CN112751728A (en) 2020-12-29 2020-12-29 Link health state monitoring method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011593812.3A CN112751728A (en) 2020-12-29 2020-12-29 Link health state monitoring method and device

Publications (1)

Publication Number Publication Date
CN112751728A true CN112751728A (en) 2021-05-04

Family

ID=75646892

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011593812.3A Pending CN112751728A (en) 2020-12-29 2020-12-29 Link health state monitoring method and device

Country Status (1)

Country Link
CN (1) CN112751728A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629822A (en) * 2022-04-18 2022-06-14 北京小米移动软件有限公司 Link detection method and device, electronic equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101640620A (en) * 2009-09-01 2010-02-03 杭州华三通信技术有限公司 Method and device for health detection for equalized equipment
CN101808043A (en) * 2010-03-12 2010-08-18 成都市华为赛门铁克科技有限公司 Method and device for detecting service message forwarding state of TRUNK members
CN102299831A (en) * 2011-09-27 2011-12-28 杭州华三通信技术有限公司 Method for detecting invalidation of group members of internal server and network address translation (NAT) equipment
US20190394263A1 (en) * 2017-07-03 2019-12-26 Pure Storage, Inc. Stateful connection resets

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101640620A (en) * 2009-09-01 2010-02-03 杭州华三通信技术有限公司 Method and device for health detection for equalized equipment
CN101808043A (en) * 2010-03-12 2010-08-18 成都市华为赛门铁克科技有限公司 Method and device for detecting service message forwarding state of TRUNK members
CN102299831A (en) * 2011-09-27 2011-12-28 杭州华三通信技术有限公司 Method for detecting invalidation of group members of internal server and network address translation (NAT) equipment
US20190394263A1 (en) * 2017-07-03 2019-12-26 Pure Storage, Inc. Stateful connection resets

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629822A (en) * 2022-04-18 2022-06-14 北京小米移动软件有限公司 Link detection method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
CN113315682B (en) Method, system and device for generating information transmission performance warning
KR100870166B1 (en) Load distributing apparatus, load distributing method, and load distributing program
CN106612284B (en) Streaming data transmission method and device
CN110908872B (en) Method and system for detecting server state
US6633230B2 (en) Apparatus and method for providing improved stress thresholds in network management systems
WO2021093465A1 (en) Method, device, and system for transmitting packet and receiving packet for performing oam
CN112636979B (en) Cluster alarm method and related device
CN108322401A (en) The control method and device of network transmission congestion
US10498626B2 (en) Method, traffic monitor (TM), request router (RR) and system for monitoring a content delivery network (CDN)
CN111314236A (en) Message forwarding method and device
CN112671813B (en) Server determination method, device, equipment and storage medium
JP2010538551A (en) Method and system for automatically confirming connectivity status of an IP link on an IP network
CN112866338B (en) Server state detection method and device
CN112751728A (en) Link health state monitoring method and device
US10567262B1 (en) Dynamic server device monitoring
CN112866394B (en) Load balancing method, device, system, computer equipment and storage medium
CN110808917B (en) Multilink aggregation data retransmission method and transmitting equipment
CN108781215B (en) Network service implementation method, service controller and communication system
CN110891077A (en) CDN node detection method and device
CN106817268B (en) DDOS attack detection method and system
EP3158685B1 (en) Identification of candidate problem network entities
JP4915345B2 (en) Test equipment measurement system
JP6928241B2 (en) Traffic analyzers, traffic analysis methods, traffic analysis programs, and communication systems
CN110740078A (en) Agent monitoring method for servers and related product
CN114826741B (en) Attack monitoring system and attack monitoring method

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
RJ01 Rejection of invention patent application after publication

Application publication date: 20210504

RJ01 Rejection of invention patent application after publication