Source: https://patents.google.com/patent/US10374936B2/en
Timestamp: 2019-10-17 21:10:21
Document Index: 380038781

Matched Legal Cases: ['Application No. 16204540', 'Application No. 16204540', 'Application No. 16204540', 'Application No. 16204540', 'Application No. 16204540', 'Application No. 16204540', 'art-06']

US10374936B2 - Reducing false alarms when using network keep-alive messages - Google Patents
Reducing false alarms when using network keep-alive messages Download PDF
US10374936B2
US10374936B2 US14/984,926 US201514984926A US10374936B2 US 10374936 B2 US10374936 B2 US 10374936B2 US 201514984926 A US201514984926 A US 201514984926A US 10374936 B2 US10374936 B2 US 10374936B2
US14/984,926
US20170195209A1 (en
Sairam Neelam
2015-12-30 Application filed by Juniper Networks Inc filed Critical Juniper Networks Inc
2015-12-30 Priority to US14/984,926 priority Critical patent/US10374936B2/en
2015-12-30 Assigned to JUNIPER NETWORKS, INC. reassignment JUNIPER NETWORKS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NEELAM, SAIRAM, SINGH, PRASHANT
2017-07-06 Publication of US20170195209A1 publication Critical patent/US20170195209A1/en
2019-08-06 Publication of US10374936B2 publication Critical patent/US10374936B2/en
241000713154 Toscana virus Species 0 abstract 1
Techniques are described to reduce false alarms in network devices utilizing keepalive messaging schemes. In order to potentially avoid false alarms, a transmitting network device adjusts quality of service QOS/TOS settings in keep-alive probe packets that are sent later in a current detection interval such that the keep-alive probe packets have escalating priorities. In addition, for keep-alive probe packets that are sent later in the current detection interval, the network device may also insert host-level preferential indicator within each of the packets to request preferential treatment at both itself and the peer network device.
This disclosure relates generally to computer networks, and more specifically, to periodic communications, such as communications used for liveliness detection, between devices in a computer network.
Applications executing within a network environment frequently utilize “keep alive” messaging schemes to monitor operational status of other applications within the network. For example, applications executing on network devices within network environment send periodic packets to each to confirm connectivity and to indicate operational status of each device. These periodic packets are sometimes referred to as “keepalives” or “hellos.” For example, a first application executing on one network device may send periodic packets to a peer application executing on another network device every 50 milliseconds (ms) to indicate that the first application is still operational. Likewise, the application may detect reception of corresponding periodic packets from the peer application within the same period of time (e.g., 50 ms). When a threshold number of packets have not been received in the allotted time frame, the application determines that a session failure event has occurred, such as failure of the network device on which the peer application is executing, failure of a link or node connecting the two network devices or failure of the application itself. In response to the failure, the network device on which the peer application is executing may take certain actions, such as redirecting communications to a different peer application.
As one example, routers may exchange periodic packets by establishing a session provided by the bidirectional forwarding detection (BFD) protocol. In accordance with BFD, a first router periodically sends BFD packets at a negotiated transmission time interval and detects a session failure event when the router does not receive a BFD packet from a second router within session detection time interval. For instance, a router may negotiate to receive BFD packets every 50 ms from a peer router and may independently utilize a detection multiplier of three (3) times that interval, i.e., 150 ms in this example, for detecting failure. If the receiving router does not receive a BFD packet from the peer router within the 150 ms session detection time interval, the receiving router detects a connectivity failure with respect to the second router. Consequently, the receiving router may update its routing information to route traffic around the second router. Further details of the BFD protocol may be found in the proposed standard for BFD, by D. Katz and D. Ward (Juniper Networks, June 2010, ISSN: 2070-1721), the entire content of which is incorporated herein by reference.
In general, techniques of this disclosure are directed to reducing false alarms in network devices utilizing keep-alive messaging schemes. As described herein, in order to potentially avoid false alarms, a transmitting network device may adjust quality of service (QOS)/type of service (TOS) settings in keep-alive probe packets for a communication session that are sent later in a detection interval for the communication session such that the keep-alive probe packets have escalating priorities. That is, when transmitting keep-alive probe packets for a given communication session, the network device monitors whether a response communication (e.g., keep-alive response packets or asynchronous keep-alive probe packets) has been received from the peer device within the current detection interval and sets the QOS/TOS settings within headers of the keep-alive probe packets accordingly. As such, keep-alive probe packets sent by network device at a time later in the detection interval receive increased QOS/TOS priority and, therefore, receive preferential treatment by intermediate network elements.
In addition, for keep-alive probe packets that are sent later in the detection interval, the network device may also insert host-level preferential indicator within each of the packets to request preferential treatment at both itself and the peer network device. For example, the host-level preferential indicator may indicate that the corresponding keep-alive probe packet is the last to be sent prior to expiration of the detection interval. Hardware/software of the network devices that handle packet transmissions, such as operating system (kernel) software including network stack software, interface drivers, network interface hardware, such as a network interface card (NIC), provide preferential treatment when servicing the transmission or reception of keep-alive probe packets and response packets.
Moreover, the peer network device may generate response communications so as to inherit the QOS/TOS settings and any host-level preferential indicator of the most recently received keep-alive probe packet.
In one example, a method includes maintaining, with a network device, a keep-alive transmit timer and a keep-alive detection timer associated with a communication session with a peer network device within a network. The keep-alive transmit timer defines a transmit time interval for transmitting keep-alive probe packets for the communication session and the keep-alive detection timer defines a current detection interval within which a response communication (e.g., keep-alive response messages or asynchronous keep-alive probe messages) from the peer network device must be received to avoid a failure event for the communication session. The method further includes responsive to expiration of the keep-alive transit timer during the current detection interval, outputting, by the network device, a first keep-alive probe packet associated with the communication session with the peer network device, wherein the keep-alive probe packet includes quality of service (QoS) settings that controls forwarding priority of the keep-alive probe packet by packet-switching devices within the network, and wherein the QoS settings have a value indicating a first priority level. The method further includes, responsive to a second expiration of the keep-alive transit timer associated during the current detection interval, determining whether a communication has been received from the peer network device since output of the first keep-alive probe packet and, when the communication has not been received, outputting a second keep-alive probe packet associated with the communication session, wherein the second keep-alive probe packet includes QoS settings having a value indicating a second priority level increased from the first priority level.
In another example, a method includes receiving, by a network device, a keep-alive probe packet associated with a communication session with a peer network device within a network, wherein the keep-alive probe packet includes quality of service (QoS) settings that controls forwarding priority of the keep-alive probe packet by packet-switching devices within the network. The method further includes constructing, with the network device, a keep-alive response packet, copying the QoS settings of the keep-alive probe packet to QoS settings within the keep-alive response packet, and outputting the keep-alive response packet from the network device to the peer network device.
In another example, a network device includes a memory, programmable processor(s), a network interface, and a control unit. The control unit is configured to perform the operations described herein.
In another example, a computer-readable storage medium is encoded with instructions. The instructions cause one or more programmable processors of a network device to perform the operations described herein.
FIG. 2 is a block diagram illustrating another example network system implementing the techniques described herein.
FIG. 3 is a block diagram illustrating an exemplary network device in accordance with the disclosure herein.
FIG. 4 is a block diagram illustrating an exemplary router in accordance with the disclosure herein.
FIG. 5 is a flowchart illustrating example processes by which network devices participating in keep-alive messaging schemes operate in accordance with one or more aspects of this disclosure.
FIG. 1 is a block diagram illustrating an example network system 10 in which techniques described herein may be implemented. In this example, network system 10 includes network devices 12A, 12B (“network devices 12”), which operate and interact with one another in accordance with the techniques described herein. Network devices 12 are communicatively coupled to one another, either directly, or indirectly, via one or more intermediate network elements (“E”) interconnected by physical links 18. Network elements 16 may, for example, be routers, switches, gateways, firewalls and the like. Links 18 represent any physical medium, such as a copper wire, a coaxial cable, any of a host of different fiber optic lines, a wireless connection, and various combinations thereof.
In general, network devices 12 execute applications that periodically send status messages (e.g., send “periodic packets” or “keep-alive packets”) to one another in order to indicate monitor operational and connectivity status of each other. That is, by sending periodic inquiries and detecting receipt of similar periodic inquiries, network devices 12 detect any failures, either as a result of failure of one or more of network devices 12, network elements 16 or of links 18 between them. Upon detecting such a failure, the detecting network device 12 takes certain actions, such as redirecting communications to a different peer application. Network devices 12 may be end-user computers, desktops, laptops, mobile devices, servers, virtual machines or networking infrastructure, such as routers, switches, gateways, firewalls, or other network-enabled devices.
In the example of FIG. 1, an application executing on network device 12A establishes a communication session 15, such as a Transmission Control Protocol (TCP) session, with network 12B and transmits keep-alive probe packets 14A to network device 12B over the communication session. When transmitted, keep-alive probe packets 14A are first processed by transmit hardware/software on network device 12A (e.g., kernel software including network stack software, interface drivers and network interface hardware), processed by hardware/software of intermediate network elements 16 (e.g., packet forwarding ASICs, switch fabrics, packet queues of the network elements) when transporting the packets, and ultimately processed by receive hardware/software of network device 12B.
In response, network device 12B transmits keep-alive response packets 14B on communication session 15. That is, upon receiving a keep-alive probe packet 14A, network device 12B constructs a respective keep-alive response packet 14B and outputs the response packet to network device 12A over the communication session. Keep-alive response packet 14B are, therefore, processed by transmit hardware/software on network device 12B when transmitting the packet, processed by hardware/software of network elements 16 (e.g., packet forwarding ASICs, switch fabrics, packet queues) when transporting the packets and ultimately processed by receive hardware/software of network device 12A.
In operation, network device 12A implements a transmission (or “transmit”) timer that controls transmission of keep-alive probe packets 14A over the communication session. That is, the transmit timer measures intervals for network device 12A to transmit a keep-alive probe packet 14A over the communication session, and triggers transmission of the packet upon reaching the negotiated interval.
Network device 12A implements a detection timer to monitor receipt of keep-alive response packets 14B. The detection timer measures intervals between received keep-alive probe packets 14B over the communication session. Using the detection timer, network device 12A determines the operational status of network device 12B, i.e., whether network device 12A is operational and in communication. For instance, if network device 12A does not receive a keep-alive response packet 14B within the session detection time, the network device determines that a network event has occurred that is preventing communication, such as a failure of an intermediate link 18 or network element 16 or failure of hardware and/or software of network device 12B. In many instances, network device 12A sets the detection timer to a multiple (e.g., an integer multiple) of the negotiated transmit interval, such as a value of 3*Transmit_Interval. For example, if the transmit interval is being used by network device 12A is 50 ms, network device 12A may determine a failure has occurred if no keep-alive response packet 14B is received in 150 ms, i.e., three (3) transmit intervals.
In some situations, the detection timer of network device 12A may expire even though network device 12B has not failed and communication connectivity still exists between the devices. For example, network congestion, i.e., heavy traffic loads leading to length packet queues, within intermediate network elements 16 may cause communication delays that exceed the detection interval maintained by network device 12A. During this period, network device 12A will typically have sent multiple keep-alive probe packets 14A, one for each respective transmit interval. Each of the successive keep-alive probe packets 14A sent by network device 12A during the detection interval traverses intermediate elements 16 and links 18 and may be subject to the same congestion and network delays, thereby giving rise to a network event upon expiration of the detection interval at network device 12B.
As described herein, in order to potentially avoid false alarms, network device 12A may adjust quality of service (QOS)/type of service (TOS) settings in keep-alive probe packets 14A that are sent later in the detection interval so as to have escalating priorities. That is, when transmitting keep-alive probe packets 14A, network device 12A monitors whether keep-alive response packets 14B have been received and sets the QOS/TOS settings within the header of the keep-alive probe packets 14A accordingly. For example, network device 12A may utilize an increased QOS/TOS setting in an outbound keep-alive probe packet 14A when an expected keep-alive response packet 14B has not been received within a current detection interval. Moreover, network device 12A may utilize a further increased QOS/TOS setting when transmitting subsequent keep-alive probe packets 14A when a keep-alive response packet 14B still has not been received within the detection interval. As such, keep-alive probe packets 14A sent by network device 12A at a time later in the detection interval of network device 12B receive increased QOS/TOS priority and, therefore, receive preferential treatment by intermediate network elements 16 and by queuing and processing operations of network devices 12A, 12B.
In addition, for keep-alive probe packets 14A that are sent later in the detection interval, network device 12A may insert host-level preferential indicator within each of the packets to request preferential treatment by network devices 12A, 12B. For example, network device 12A may include the host-level preferential indicator within the final keep-alive probe packet 14A to be transmitted before expiration of the detection interval of network device 12B. Keep-alive probe packets 14A containing the host-level preferential indicator are serviced with a higher priority by both the transmission hardware/software of network device 12A and the receive hardware/software of network device 12B. Example hardware/software of network devices 12A, 12B that typically handle packet transmissions include operating system (kernel) software including network stack software, interface drivers, network interface hardware, such as a network interface card (NIC). The hardware/software on network devices 12A, 12B may service the transmission or reception of keep-alive probe packets 14A having the host-level preferential indicator on an interrupt-driven basis rather than a thread polling scheme that would otherwise be used for keep-alive probe packets 14A that do not include the preferential indicator. As another example, hardware/software of network devices 12A, 12B may maintain separate transmit and receive queues for keep-alive probe packets 14A that contain the preferential indicator, thereby bypassing queues used for packets that do not contain the host-level preferential indicator.
In this way, the techniques described herein may help ensure timely delivery of keep-alive probe packets 14A when expiration of the detection interval maintained by network device 12A is approaching, thereby increasing the likelihood of the keep-alive probe packets reaching network device 12B and avoiding false alarms due to network congestion within network elements 16 or network devices 12A, 12B themselves.
Moreover, in some example implementations, network device 12B generates keep-alive response packets 14B so as to inherit the QOS/TOS settings and any host-level preferential indicator of the most recently received keep-alive probe packet 14A. That is, when constructing keep-alive response packets 14B, network device 12B may set the QOS/TOS settings within the packet header to be the same as the QOS/TOS settings within the packet header of the most-recently received keep-alive probe packet 14A. Moreover, network device 12B may also set the host-level preferential indicator within keep-alive response packets 14B to be the same as the host-level preferential indicator of the most-recently received keep-alive probe packet 14A. As such, in the event a keep-alive probe packet 14A is received having escalated priority and host-level preferential indicator, thereby receiving priorities processing and avoiding network congestion within intermediate network elements 16 and/or network devices 12A, the keep-alive response packet 14B sent in response thereto will automatically have the same escalated priorities and host-level preferential indicator. Thus, in this example implementation, the keep-alive response packet 14B will similarly have an increased likelihood of avoiding network congestion within intermediate network elements 16 and/or network devices 12A so as to be received and processed by network device 12A within the expected time frame. In other words, receipt of a keep-alive probe packet 14A having escalated priority and host-level preferential indicator provides an indication to network device 12B that network device 12A is operational but is not receiving keep-alive response packets 14B and, therefore, network device 12A has escalated the priorities and host-level preferential indicator in an effort to avoid false alarm triggering of a failure of the keep-alive messaging scheme. As such, network device 12B mirrors the priorities and host-level preferential indicator into keep-alive response packets 14B when generating the keep-alive response packets to further assist avoidance of triggering false alarms.
In one example implementation, applications executing on network devices 12A, 12B may configure the Differentiated Services Field (DS Field) in the IPv4 and IPv6 headers of the keep-alive probe packets 14A and keep-alive response packets 14B to set desired QOS/TOS priories for packets. Further example details of the differentiated services field in IP are described in RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, December 1998, the entire contents of which are incorporated herein by reference.
Moreover, when utilizing TCP/IP-based communication sessions, the applications of network devices 12A, 12B may utilize one or more of the Reserved bits or the “Urgent” (URG) bit of the TCP header to carry the host-level preferential indicator. As another example implementation, when utilizing BFD communication sessions, network devices 12A, 12B may utilize one or more of the Diagnostic (DIAG) bit of the BFD header to carry the host-level preferential indicator. As another example, applications may utilize the Options field within the IP header to carry the host-level preferential indicatory.
FIG. 2 is a block diagram illustrating another example in which network devices 12A, 12B exchange keep-alive packets with one another. In the example described above with respect to FIG. 1, network device 12A, 12B are implementing an acknowledgement-based communication scheme in which network device 12A transmits keep-alive probe packets 14A and network device 12B responds with a response communication, e.g., keep-alive response packets 14B. In the example implementation of FIG. 2, network devices 12A, 12B each output a so-called “heart beat” of keep-alive probe packets over one or more communication sessions 15A, 15B. That is, in this example, network device 12A transmits keep-alive probe packets 14A at a certain transmit interval while network device 12B similarly outputs keep-alive probe packets 14B at a certain transmit interval. As described above, each network device 12A, 12B monitors whether keep-alive probe packets have been received from the other device within a current detection interval, and when generating and transmitting its respective keep-alive probe packets, sets the QOS/TOS settings within the header of the keep-alive probe packet accordingly. For example, network device 12A may utilize an increased QOS/TOS setting when a keep-alive probe packet 14B has not been received within a detection interval maintained by network device 12A. Similarly, network device 12B may utilize an increased QOS/TOS setting for keep-alive probe packet 14B when a keep-alive probe packet 14A has not been received within a current detection interval maintained by network device 12B. In addition, network devices 12A, 12B may insert host-level preferential indicator when transmitting for keep-alive probe packets 14A, 14B, respectively, to request preferential treatment by network devices 12A, 12B.
As described, keep-alive probe packets 14A, 14B having increase QOS/TOS priority receive preferential treatment by intermediate network elements 16, and such packets having host-level preferential indicator are further prioritized and efficiently processed by network devices 12A, 12B. In this way, the techniques described herein may help ensure timely delivery of keep-alive probe packets 14A, 14B so as to avoid false alarms due to network congestion within network elements 16 or network devices 12A, 12B themselves.
Moreover, in some examples, both network devices 12A, 12B generates keep-alive probe packets 14A, 14B so as to inherit the QOS/TOS settings and any host-level preferential indicator of the keep-alive probe packet most recently received from the other network device. That is, upon receiving an incoming keep-alive probe packet having increased QOS/TOS settings and host-level preferential indicator, the receiving one of the network devices 12 copies the settings in the next keep-alive probe packet that it transmits. For example, receipt of a keep-alive probe packet 14A having escalated priority and host-level preferential indicator provides an indication to the receiving network device 12B that network device 12A is operational but is not receiving keep-alive probe packets 14B from network device 12B and that, in response, network device 12A has escalated the priorities and host-level preferential indicator in an effort to avoid false alarm triggering of a failure of the keep-alive messaging scheme. As such, network device 12B mirrors the priorities and host-level preferential indicator into keep-alive probe packets 14B when generating the keep-alive probe packets to further assist avoidance of triggering false alarms.
The techniques described above with respect to FIGS. 1 and 2, may be applied to a variety of network protocols that utilizes periodic messages for indicating operational and connectivity status to a peer device. One exemplary protocol is referred to as the bidirectional forwarding detection (BFD) protocol, which is commonly used between two network devices in order for each router to closely monitor the state (e.g., health) of the other device. For example, network devices 12 may establish a BFD session for sending and responding to status inquiries in the form of Hello packets, either asynchronously or when needed (e.g., as in the BFD Demand Mode). In either case, the BFD protocol provides a very short interval of time between which network devices 12 must transmit periodic messages, and thus may facilitate the quicker detection of failures by network devices 12 that are in an active BFD session. Further example details of the BFD protocol are described in D. Katz, D. Ward, Bidirectional Forwarding Detection, June 2010, the entire contents being incorporated herein by reference.
FIG. 3 is a block diagram illustrating an example network device 100 that provides an operating environment for one or more applications 103A-103M (“applications 103”). For example, network device 100 may represent any of network devices 12A, 12B of FIGS. 1, 2.
In this example, network device 100 includes a network interface 101 to send and receive network packets. In addition, network device 100 includes a microprocessor 110 executing operating system 106 to provide an execution environment for one or more applications 103 that communicate with other network devices over a packet-based network. In general, applications 103 represent any component of a network device that utilizes keep-alive messages to communicate with other network device. As discussed herein, in example implementations, network device may be an endpoint network device, e.g., a user computing device, backend server or virtual machine executing in the “cloud.” Example user-related applications include email applications, video conferencing applications, peer computing applications, and the like. As additional examples, network device 100 may provide network operations, such as a router, switch, firewall, Intrusion detection system, network cache, DNS server. Example applications 103 include routing protocols, device management applications, such as BFD, SNMP or NETCONF, or the like.
In the example of FIG. 3, operating system 106 executing within network device 100 implements kernel-level processes for handling data at various layers of the open systems interconnection (OSI) networking model (shown as protocol stack 114). Operating system 106 provides an API by which applications 103 creates sockets 112 and establishes, for example, TCP/IP-based communication sessions for sending and receiving routing messages for each socket. Details of the OSI model are described in ISO 7498, 2nd Information technology—Open Systems Interconnection—Basic Reference Model: The Basic Model, (1994), incorporated herein by reference. Further details of TCP are described in RFC 793, TRANSMISSION CONTROL PROTOCOL, Internet Engineering Task Force (IETF), September 1981, the entire contents of which are incorporated herein by reference.
Sockets 112 are logical constructs having data structures and state data maintained by operating system 106 and may be viewed as acting as interfaces between applications 103 and protocol stack 114. For instance, sockets 112 may include one or more data structures that define data relating to one or communication sessions, such as a file descriptor of a socket, a thread identifier of the socket, an active/backup state of the socket, and a pointer to a TCP socket within protocol stack 114. Sockets are used herein as one common mechanism for establishing communication sessions between devices and the techniques described herein may be applied to any other type of communication session that utilizes which session maintenance messages.
In the example, TCP implementation of protocol stack 114 includes a keep alive manager 116 that provides keep-alive functionality for each socket 112 instantiated by applications 103. For example, for each socket, keep alive manager 116 creates timers 122, such as a transmit timer and a detection timer, for triggering transmission of keep alive probe messages and keep alive response messages, respectively, for the corresponding socket, i.e., for each communication session established by applications 103. Keep-alive transmit controller (“TX”) 118 and keep-alive receive controller (“RCV”) 120 operate responsive to transmit and detection timers 122, respectively, in accordance with the techniques described herein.
For example, keep-alive receive controller 120 produces message 124 to inform keep-alive transmit controller 118 when a keep-alive response message is received for a given communication session. When constructing and transmitting keep-alive probe packets 14A, keep-alive transmit controller 118 sets the QOS/TOS settings within the header of the packets based on when a most-recent keep-alive response packets 14B was received within a current detection interval. For example, keep-alive transmit controller 118 may utilize an increased QOS/TOS setting when constructing a current keep-alive probe packet 14A if a keep-alive response packet 14B has not been received since transmission of the prior keep-alive probe packet 14A within the current detection interval. Moreover, keep-alive transmit controller 118 may utilize a further increased QOS/TOS setting when transmitting subsequent keep-alive probe packets 14A in the event a keep-alive response packet 14B still has not been received at a time later in that same detection interval. As such, keep-alive probe packets 14A sent by keep-alive transmit controller 118 at a time later in the detection interval for the respective socket 112 receive increased QOS/TOS priority and, therefore, receive preferential treatment by intermediate network elements. In addition, for keep-alive probe packets 14A that are sent later in the detection interval, keep-alive transmit controller 118 may insert host-level preferential indicator within each of the packets to request preferential treatment by endpoint network devices. In this way, the techniques described herein may help ensure timely delivery of keep-alive probe packets 14A when expiration of the detection interval is approaching, thereby avoiding false alarms due to network congestion within network elements 16 or network devices 12A, 12B themselves.
As one example, keep-alive transmit controller 118 may operate generally as shown in Table 1. In this example, keep-alive receive controller 120 is configured with a detection interval of five (5) times the transmit interval and, in the event keep-alive response packets 14B are not received from a peer network device, constructs keep-alive probe packets throughout the detection interval as shown in Table 1.
TABLE 1 KEEP ALIVE HOST-LEVEL PROBE PACKET PRIORITY PREFERENTIAL SEQUENCE # BITS INDICATOR 1 LOW NO 2 LOW NO 3 MED NO 4 MED YES 5 HIGH YES
In this example, keep-alive transmit controller 118 constructs the first and second keep-alive probe packets 14A within a current detection interval for the communication session as a conventional keep-alive probe packet 14A, i.e., without any TOS/QOS settings and without requesting any host-level preferential indicator. In the event a keep-alive response packet 14B has not been received by the time keep-alive transmit controller 118 is to transmit the third keep-alive probe packet 14A within the same detection interval, keep-alive transmit controller 118 constructs the third keep alive probe packet 14A within the detection interval to have increased priority bits, e.g., set to a MEDIUM priority level, but does not at this time include a host-level preferential indicator within the keep-alive probe packet. In the event a keep-alive response packet 14B has still not been received by keep-alive receive controller 120 when time keep-alive transmit controller 118 is triggered to transmit the fourth keep-alive probe packet 14A within the same detection interval, the keep-alive transmit controller 118 constructs the fourth keep alive probe packet 14A to have increased priority bits, e.g., set to a MEDIUM priority level as well as having a host-level preferential indicator. Finally, in this example, if a keep-alive response packet 14B has not been received by keep-alive receive controller 120 when keep-alive transmit controller 118 is triggered to transmit the fifth keep-alive probe packet 14A, the keep-alive transmit controller constructs the fifth keep alive probe packet 14A within the detection interval to have increased priority bits of HIGH priority level and to include a host-level preferential indicator.
In addition, keep-alive transmit controller 118 and keep-alive receive controller 120 of network device 100 operate to respond to keep-alive messages from other device for a given communication session. For example, keep-alive receive controller 120 may receive inbound keep alive probe message 14A′. Responsive to those inbound keep-alive probe message 14A′, keep-alive receive controller 120 outputs message 126 directing transmit controller 118 to construct and output a keep-alive response message 14B′. When generating message 126, keep alive receive controller 120 includes and priority settings (e.g., QOS/TOS bits) and any host-level preferential indicator that were present within inbound keep-alive probe message 14A′, thereby communicating this information to keep alive transmit controller 118. In response, keep alive transmit controller 118 generates keep-alive response packets 14B′ so as to inherit the QOS/TOS settings and any host-level preferential indicator of the most recently received keep-alive probe packet 14A′. That is, when constructing keep-alive response packets 14B′, keep alive transmit controller 118 set the QOS/TOS settings and host-level preferential indicator within the packet header to be the same as (i.e., copies) the QOS/TOS settings and host-level preferential indicator within the packet header of the most-recently received keep-alive probe packet 14A′, as specified by message 126. As such, in the event a keep-alive probe packet 14A′ is received having escalated priority and host-level preferential indicator, thereby receiving priorities processing and avoiding network congestion within intermediate network elements and/or host network devices, the keep-alive response packets 14B′ sent in response thereto will automatically have the same escalated priorities and host-level preferential indicator.
FIG. 4 is a block diagram illustrating an exemplary router 230 in accordance with the disclosure herein. Router 230 is one example implementation of any of network devices 12 illustrated in FIGS. 1-3. While router 230 illustrates one possible router implementation to perform the techniques described herein, it will be appreciated that various other implementations are possible in accordance with this disclosure.
In this example, router 230 includes a control unit 231 that comprises a routing engine 232 and a forwarding engine 234. In addition, router 230 includes a set of interface cards (IFCs) 250A-250N (collectively, “IFCs 250”) for communicating packets via inbound links 252A-252N (collectively, “inbound links 252”) and outbound links 254A-254N (collectively, “outbound links 254”).
Routing engine 232 primarily provides an operating environment for control plane protocols, such as those included in protocols 240. For example, one or more routing protocols (“RPs”) 247 that maintain routing information 236 to reflect the current topology of a network and other network entities to which it is connected. In particular, each RP 247 updates routing information 236 to accurately reflect the topology of the network and other entities. Example routing protocols include Multi-Protocol Border Gateway Protocol (mpBGP), the Intermediate System to Intermediate System (ISIS) routing protocol, the Open Shortest Path First (OSPF) routing protocol and the like.
Routing engine 232 generates and programs forwarding engine 234 with forwarding information 238 that associates network destinations with specific next hops and corresponding interface ports of IFCs 250 in accordance with routing information 236. Routing engine 232 may generate forwarding information 238 in the form of a radix tree having leaf nodes that represent destinations within the network.
Based on forwarding information 238, forwarding engine 234 forwards packets received from inbound links 252 to outbound links 254 that correspond to next hops associated with destinations of the packets. U.S. Pat. No. 7,184,437 provides details on an exemplary embodiment of a router that utilizes a radix tree for route resolution, the contents of which is incorporated herein by reference in its entirety.
In one example, forwarding engine 234 is a rich and dynamic shared forwarding plane, optionally distributed over a multi-chassis router. Moreover, forwarding plane 234 may be provided by dedicated forwarding integrated circuits normally associated with high-end routing components of a network router. Further details of one example embodiment of router 230 can be found in U.S. Provisional Patent Application 61/054,692, filed May 20, 2008, entitled “STREAMLINED PACKET FORWARDING USING DYNAMIC FILTERS FOR ROUTING AND SECURITY IN A SHARED FORWARDING PLANE,” which is incorporated herein by reference.
Moreover, as shown in FIG. 4, protocols 240 include BFD module 239 that is enhanced in accordance with the techniques described herein. For example, BFD module 239, in conjunction with other components of router 230, is configured to avoid potential false alarms as described herein. BFD module 239 of routing engine 232 may program BFD module 239′ in forwarding engine 234 or similar logic (not shown) in any of IFCs 50 that utilize BFD protocol-based logic to monitor incoming BFD packets and report a failed connection with another router to routing engine 239. BFD module 239 may, for example, program BFD module 239′ with configuration information that specifies TOS/QOS settings and host-level preferential indicator that escalate for keep-alive probe packets sent later within a detection interval of the acknowledging device, such as the example shown in Table 1. The configuration information may be received from an administrator, e.g., by a device management session, or from the peer network device during session negotiation.
BFD module 239′ implements BFD protocol-based functionalities, such as transmitting and monitoring for periodic BFD packets received by forwarding engine 234, thereby conserving resources that would otherwise be expended by routing engine 232. In case of a detected connectivity failure, BFD module 239′ is configured to transmit a failure notification, or other similar indication, to BFD module 239 of routing engine 232. In response to receiving the failure notification from BFD module 239′ of forwarding engine 234, BFD module 239 causes RP 247 to update the network topology currently stored to routing information 236, to reflect the failed link(s) represented by the BFD failure.
As shown in FIG. 4, forwarding engine 234 includes keep-alive manager 216, which is communicatively coupled to BFD module 239′. While shown separately from BFD module 239′ for purposes of clarity, in various examples, keep-alive manager 216 may be included in BFD 239′, or may be implemented in other components of router 230.
In general, keep-alive manager 216 operates as described herein, such as with respect to keep alive manager 116, to reduce avoidance of triggering false alarms with respect to BFD protocol implemented by BFD module 239′. That is, keep-alive manager 216 provides keep-alive functionality for each BFD session instantiated by BFD module 239′. For example, for each communication session, keep alive manager 216 instantiates a transmit timer and a detection timer, for triggering transmission of BFD keep alive messages and, if required, BFD keep alive response messages, respectively, for the corresponding BFD session. Although not shown in FIG. 4, keep-alive manager 216 may include a keep-alive transmit controller and a keep-alive receive controller that operate responsive to internal timers as described with respect to keep-alive TX controller 118 and keep-alive RCV controller 120 in accordance with the techniques described herein. As such, keep-alive manager 216 may generate BFD keep-alive packets at a time later in the detection interval for the respective BFD session to include increased QOS/TOS priority and, therefore, receive preferential treatment by intermediate network elements. In addition, for BFD keep-alive packets that are sent later in the detection interval, keep-alive manager 216 may insert host-level preferential indicator within each of the packets to request preferential treatment by endpoint network devices. In this way, the techniques described herein may help ensure timely delivery of BFD keep-alive packets when expiration of the detection interval is approaching, thereby avoiding false alarms due to network congestion. Moreover, when constructing BFD keep-alive packets, keep alive manager 216 may set the QOS/TOS settings and host-level preferential indicator within the packet header to be the same as the QOS/TOS settings and host-level preferential indicator within the packet header of the most-recently received BFD keep-alive packet. As such, in the event a BFD keep-alive probe packet is received having escalated priority and host-level preferential indicator, thereby receiving priorities processing and avoiding network congestion within intermediate network elements and/or host network devices, the BFD keep-alive packets sent in response thereto will automatically have the same escalated priorities and host-level preferential indicator.
The architecture of router 230 illustrated in FIG. 4 is shown for exemplary purposes only. In other implementations, router 230 may be configured in a variety of ways. In one example, control unit 231 and its corresponding functionality may be distributed within IFCs 250. Control unit 231 may be implemented solely in software, or hardware, or may be implemented as a combination of software, hardware, or firmware. For example, control unit 231 may include one or more processors which execute software instructions. In that case, the various software modules of control unit 231, such as protocols 240, may comprise executable instructions stored on a computer-readable medium, such as one or more of computer memory, computer readable-storage devices (e.g., hard disks and/or solid-state disks), or non-transitory computer-readable media.
FIG. 5 is a flowchart illustrating example processes by which network devices participating in keep-alive messaging schemes operate in accordance with one or more aspects of this disclosure. In the example of FIG. 5, the techniques are described with respect to a first network device and a second (peer) network device. The network devices of FIG. 5 may, for example, represent any of network devices 12A, 12B of FIGS. 1-2, network device 100 of FIG. 3 or network router 200 of FIG. 4.
Initially, the first network device receives configuration information (300) and establishes a communication session, such as a BFD session, with the peer network device (301). For instance, the first network device may receive configuration information that specifies TOS/QOS settings and host-level preferential indicator that escalate for keep-alive probe packets sent later within a detection interval of the acknowledging device, such as the example shown in Table 1. The configuration information may be received from an administrator, e.g., by a device management session, or from the peer network device.
Upon establishing the network session with the peer network device, the first network device initiates a transmit timer for the session (302) and, responsive to expiration of the transmit timer, constructs and outputs keep-alive probe packets (304). As described herein, in order to potentially avoid false alarms, the transmitting network device adjusts quality of service (QOS)/type of service (TOS) settings and any host-level preferential indicators in the keep-alive probe packets that are sent later in the detection interval so as to have escalating priorities. That is, when constructing a given keep-alive probe packet, the network device determines whether a communication (e.g., a keep-alive response packet or a keep-alive probe packet) has been received from the peer network device since the last keep-alive probe packet transmitted by the network device. When a communication has not been received the network device constructs and outputs the keep-alive probe packet and sets the QoS settings based on the configuration data so as to have increased priority. Moreover, when the communication from the peer network device has not been received, the network device sets the host-level preferential indicator of the keep-alive probe packet to have a value indicating that preferential treatment is requested.
The peer network device constructs a response communication (306). As one example, the peer network device may construct a keep-alive response packet in response to receiving the keep-alive probe packet. As another example, the peer network device may construct its own keep-alive probe packet upon expiration of a respective transmit timer. In any event, the peer network device copies the QoS settings and any host-level preferential indicator of the first keep-alive probe packet to QoS settings and host-level preferential indicator of the response communication (308). Once constructed, the peer network device outputs the response communication to the first network device (310). The peer network device may output the response communication on the same network session on which the keep-alive probe packet was received. For example, the peer network device may construct and output the response communication as a keep-alive response packet and output the keep-alive response packet on the same communication session. Alternatively, the peer network device may output the response communication to the first network device on a different communication session. For example, the peer network device may construct the response communication as a keep-alive probe packet (e.g., asynchronous BFD probe packet) and output the keep-alive probe packet on a separate communications session different from the communication session on which the keep-alive probe packet was received from the first network device.
maintaining, with a network device, a keep-alive transmit timer and a keep-alive detection timer associated with a communication session with a peer network device within a network, wherein the keep-alive transmit timer defines a transmit time interval for transmitting keep-alive probe packets for the communication session and the keep-alive detection timer defines a current detection interval within which a response communication from the peer network device must be received to avoid a failure event for the communication session;
responsive to expiration of the keep-alive transit timer during the current detection interval, outputting, by the network device, a first keep-alive probe packet associated with the communication session with the peer network device, wherein the first keep-alive probe packet includes quality of service (QoS) settings that control forwarding priority of the keep-alive probe packet by packet-switching devices within the network, and wherein the QoS settings have a value indicating a first priority level; and responsive to a second expiration of the keep-alive transit timer associated with the current detection interval, determining, by the network device, whether a communication has been received from the peer network device since output of the first keep-alive probe packet and, when the communication has not been received, outputting a second keep-alive probe packet associated with the communication session, wherein the second keep-alive probe packet includes QoS settings having a value indicating a second priority level increased from the first priority level.
wherein the first keep-alive probe packet and the second keep-alive probe packet each includes a host-level preferential indicator separate from the QoS settings that specifies preferential treatment for the first keep-alive probe packet by packet processing software or hardware on the network device when outputting the first keep-alive probe packet and by packet processing software or hardware on the peer network device when receiving the first keep-alive probe packet,
wherein the network device sets the host-level preferential indicator of the first keep-alive probe packet to have a first value indicating that preferential treatment is not requested, and
wherein, when the communication from the peer network device has not been received, the network device sets the host-level preferential indicator of the second keep-alive probe packet to have a second value indicating that preferential treatment is requested.
3. The method of claim 2, wherein the host-level preferential indicator comprise one of: a flag set within a reserved Transmission Control Protocol (TCP) bit, a flag set within an unused bidirectional forwarding detection (BFD) protocol diagnostic bit, or an unused Internet Protocol (IP) options bit.
4. The method of claim 1, wherein the communication from the peer network device comprises a keep-alive response packet sent by the peer network device to the network device on the communication session.
5. The method of claim 1, wherein the communication from the peer network device comprises a keep-alive probe packet sent by the peer network device to the network device on a second communication session.
wherein the communication session comprises a bidirectional forwarding detection (BFD) protocol session between the network device and the peer network device,
wherein the first keep-alive probe packet and the second keep-alive probe packets output by the network device comprises BFD keep-alive probe packets, and
wherein the communication from the peer network device comprises a BFD keep-alive probe packet sent by the peer network device to the network device on a second communication session.
further comprising: receiving, by the peer network device, the first keep-alive probe packet;
constructing, with the peer network device, a keep-alive response packet, wherein constructing the keep-alive response packet includes copying the QoS settings of the first keep-alive probe packet to QoS settings within the keep-alive response packet; and
outputting the keep-alive response packet from the peer device to the network device.
8. The method of claim of claim 7,
wherein the first keep-alive probe packet includes a host-level preferential indicator that specifies preferential treatment for the first keep-alive probe packet by packet processing software or hardware on the network device when outputting the first keep-alive probe packet and by packet processing software or hardware on the peer network device when receiving the first keep-alive probe packet, and
wherein constructing the keep-alive response packet with the peer network device includes copying the host-level preferential indicator of the first keep-alive probe packet received from the network device to a host-level preferential indicator within the keep-alive response packet.
receiving, by a network device, a keep-alive probe packet associated with a communication session with a peer network device within a network, wherein the keep-alive probe packet includes quality of service (QoS) settings that controls forwarding priority of the keep-alive probe packet by packet-switching devices within the network;
constructing, with the network device, a keep-alive response packet, wherein constructing the keep-alive response packet includes copying the QoS settings of the keep-alive probe packet to QoS settings within the keep-alive response packet; and outputting the keep-alive response packet from the network device to the peer network device;
wherein the keep-alive probe packet includes a host-level preferential indicator that specifies preferential treatment for the keep-alive probe packet by packet processing software or hardware on the network device when receiving the keep-alive probe packet and by packet processing software or hardware on the peer network device when transmitting the keep-alive probe packet, and
wherein constructing the keep-alive response packet with the network device includes copying the host-level preferential indicator of the keep-alive probe packet received from the network device to a host-level preferential indicator within the keep-alive response packet.
one or more programmable processors coupled to a memory storing instructions and at least one network interface; and
wherein, when executing the instructions, the processor is configured to:
maintain a keep-alive transmit timer and a keep-alive detection timer associated with a communication session with a peer network device within a network, wherein keep-alive transmit timer defines a transmit time interval for transmitting keep-alive probe packets for the communication session and the keep-alive detection timer defines a current detection interval within which a response communication from the peer network device must be received to avoid a failure event for the communication session;
responsive to expiration of the keep-alive transit timer during the current detection interval, output a first keep-alive probe packet associated with the communication session with the peer network device, wherein the first keep-alive probe packet includes quality of service (QoS) settings that control forwarding priority of the keep-alive probe packet by packet-switching devices within the network, and wherein the QoS settings have a value indicating a first priority level; responsive to a second expiration of the keep-alive transit timer associated with the current detection interval, determine whether a communication has been received from the peer network device since output of the first keep-alive probe packet and, when the communication has not been received, output a second keep-alive probe packet associated with the communication session, wherein the second keep-alive probe packet includes QoS settings having a value indicating a second priority level increased from the first priority level.
12. The network device of claim 11, wherein the host-level preferential indicator comprise one of: a flag set within a reserved Transmission Control Protocol (TCP) bit, a flag set within an unused bidirectional forwarding detection (BFD) protocol diagnostic bit, or an unused Internet Protocol (IP) options bit.
13. The network device of claim 10, wherein the communication from the peer network device comprises a keep-alive response packet sent by the peer network device to the network device on the communication session.
14. The network device of claim 10, wherein the communication from the peer network device comprises a keep-alive probe packet sent by the peer network device to the network device on a second communication session.
15. The network device of claim 10,
wherein, when executing the instructions, the processor is configured to: receive, by a network device, a keep-alive probe packet associated with a communication session with a peer network device within a network, wherein the keep-alive probe packet includes quality of service (QoS) settings that controls forwarding priority of the keep-alive probe packet by packet-switching devices within the network;
construct, with the network device, a keep-alive response packet, wherein constructing the keep-alive response packet includes copying the QoS settings of the keep-alive probe packet to QoS settings within the keep-alive response packet; and
output the keep-alive response packet from the network device to the peer network device;
US14/984,926 2015-12-30 2015-12-30 Reducing false alarms when using network keep-alive messages Active 2037-01-19 US10374936B2 (en)
US14/984,926 US10374936B2 (en) 2015-12-30 2015-12-30 Reducing false alarms when using network keep-alive messages
EP16204540.5A EP3188450B1 (en) 2015-12-30 2016-12-15 Reducing false alarms when using network keep-alive messages
CN201611246118.8A CN107070689A (en) 2015-12-30 2016-12-29 Reducing false alarms when using network keep-alive messages
US20170195209A1 US20170195209A1 (en) 2017-07-06
US10374936B2 true US10374936B2 (en) 2019-08-06
ID=57758414
US14/984,926 Active 2037-01-19 US10374936B2 (en) 2015-12-30 2015-12-30 Reducing false alarms when using network keep-alive messages
US (1) US10374936B2 (en)
EP (1) EP3188450B1 (en)
CN (1) CN107070689A (en)
US10404548B2 (en) * 2016-08-29 2019-09-03 Cisco Technology, Inc. Control of network nodes in computer network systems
US10404612B2 (en) * 2016-12-01 2019-09-03 Nicira, Inc. Prioritizing flows in software defined networks
US20180278459A1 (en) * 2017-03-27 2018-09-27 Cisco Technology, Inc. Sharding Of Network Resources In A Network Policy Platform
EP1816801A1 (en) 2006-02-03 2007-08-08 BRITISH TELECOMMUNICATIONS public limited company Method of operating a network
US7336615B1 (en) 2001-06-25 2008-02-26 Juniper Networks, Inc. Detecting data plane livelines in connections such as label-switched paths
US7760652B2 (en) 2002-04-16 2010-07-20 Enterasys Networks, Inc. Methods and apparatus for improved failure recovery of intermediate systems
US7813267B2 (en) 2006-08-29 2010-10-12 Cisco Technology, Inc. Method and system for providing control plane resiliency with undisrupted forwarding in a data network
US20130086144A1 (en) 2011-09-30 2013-04-04 Alcatel-Lucent Canada Inc. Adaptive period network session reservation
US20150063117A1 (en) * 2013-09-05 2015-03-05 Avaya Inc. Tunnel Keep-alive Timeout Mechanism Based On Quality of Service (QoS) Value of Received Keep-alive Messages
US9455894B1 (en) 2013-09-27 2016-09-27 Juniper Networks, Inc. Selective fast re-route using forwarding plane liveliness detection protocols
CN103297461B (en) * 2012-02-28 2016-05-25 中国移动通信集团公司 Nat length setting method, and a session client and the server keep-alive
2015-12-30 US US14/984,926 patent/US10374936B2/en active Active
2016-12-15 EP EP16204540.5A patent/EP3188450B1/en active Active
2016-12-29 CN CN201611246118.8A patent/CN107070689A/en active Search and Examination
"ActiveXperts Ping backgrounds (PING is part of the ActiveSocket Toolkit)," ActiveSocket Network Communication Toolkit 2.4, Activexperts, retrieved from www.activexperts.com/activsocket/toolkits/ping.html, Nov. 10, 2005, 3 pp.
"Configure an Unnumbered Interface," retrieved from www.juniper.net/tech,nubs/software/junos/junos56/index.html, Nov. 7, 2005, 1 p.
"Configure the loopback Interface," retrieved from www.juniper.net/techpubs/soft-ware/iunos/junos56/index.html, Nov. 7, 2005, 2 pp.
"ICMP (Internet Control Message Protocol)," Data Network Resource, www.rhyshaden.com/icmn.html, last printed Nov. 10, 2005, 4 pp.
"Traceroute," Webopedia, retrieved from www.webopedia.com/TERM/t/traceroute.html, Aug. 26, 2004, 1 p.
"Using the IP unnumbered configuration FAQ," APNIC, retrieved from www.apnic.net/info/faq/ip_unnumb.html, Jul. 1, 2005, 2 pp.
Atlas, "ICMP Extensions for Unnumbered Interfaces," Internet Draft, draft-atlas-icmp-unnumbered-01, Feb. 2006, 8 pp.
Boney, "Cisco IOS in a Nutshell, 2nd Edition", O'Reilly Media, Inc., Aug. 2005, 16 pp.
Chapter 1: BFD Configuration Commands, Command Manual-BFD-GR, H3C S361 O&S551 0 Series Ethernet Switches, Version: 20081229-C-1.01, Release 5303, 2006-2008, 13 pp.
Chapter 1: BFD Configuration Commands, Command Manual—BFD-GR, H3C S361 O&S551 0 Series Ethernet Switches, Version: 20081229-C-1.01, Release 5303, 2006-2008, 13 pp.
Examination Report from counterpart European Application No. 16204540.5, dated Feb. 8, 2018, 9 pp.
Examination Report from counterpart European Application No. 16204540.5, dated Oct. 29, 2018, 5 pp.
Extended Search Report from counterpart European Application No. 16204540.5, dated Apr. 21, 2017, 5 pp.
Fairhurst, "Internet Control Message protocol," Internet Control Protocol, (ICMP), retrieved from www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.html, Sep. 6, 2006, 3 pp.
Harmon, "32-Bit Bus Master Ethernet Interface for the 68030 (Using the Macintosh SE/30)," National Semiconductor Corporation, Apr. 1993, 10 pp.
Hegde et al., Multipoint BFD for MPLS, Network Working Group, Internet-Draft, draft- chandra-hedge-mpoint-bfd-for-mpls-00.txt, Mar. 5, 2012, 12 pp.
Kattz et al., "BFD for Multipoint Networks", Network Working Group, Internet Draft, draft-ietf-bfd-multipoint-00.txt, Oct. 18, 2011, 29 pp.
Kattz et al., "Biderectional Forwarding Detection (BFD) for Multihop Paths," Internet Engineering Task Force (IETF), RFC 5883, Jun. 2010, 6 pp.
Katz et al., "Bidirectional Forwarding Detection (BFD)," Internet Engineering Task Force (IETF), RFC 5880, Jun. 2010, 49 pp.
Katz et al., "Generic Application of Bidirectional Forwarding Detection (BFD)," Internet Engineering Task Force (IETF), RFC 5882, Jun. 2010, 17 pp.
Katz et al.,"Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)," Internet Engineering Task Force (IETF), RFC 5881, Jun. 2010, 7 pp.
Kessler et al., RFC 2151, "A Primer on Internet and TCP/IP Tools and Utilities," Chapter 3.4: Traceroute, Nov. 9, 2005, pp. 9-11.
Kolon, "BFD spots router forwarding failures," Network World, retrieved from www.networkworld.com/news/tech/2005/030705techupdate.html, Mar. 7, 2005, 3 pp.
Kompella et al., "Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures," Network Working Group, RFC 4379, Feb. 2006, 50 pp.
Mukhi et al., "Internet Control Message Protocol ICMP," retrieved from www.vijaymukhi.com/vmis/icmp, Sep. 6, 2006, 5 pp.
Mukhi et al., "Internet Control Message Protocol ICMP," www.vijaymukhi.com/vmis/icmp, last printed Sep. 6, 2006, 5pp.
Nadeau et al., "Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)," Internet Engineering Task Force (IETF), RFC 5885, Jun. 2010, 14 pp.
Nichols, et al., "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers," Network Working Group, RFC 2474, Dec. 1998, 19 pp.
Ramakrishnan et al.,"The Addition of Explicit Congestion Notification (ECN) to IP", RFC 3168, Network Working Group, Sep. 2001, 63 pp.
Response to Examination Report dated Feb. 8, 2018, from counterpart European Application No. 16204540.5, filed Jun. 5, 2018, 23 pp.
Response to Examination Report dated Oct. 29, 2018, from counterpart European Application No. 16204540.5, filed Feb. 26, 2019 10 pp. (Year: 2018). *
Response to Extended Search Report dated Apr. 21, 2017, from counterpart European Application No. 16204540.5, filed Jan. 4, 2018, 1 pp.
Sangli et al., "Graceful Restart Mechanism for BGP," Network Working Group, Internet Draft, draft-ietf-idr-restart-06.txt, Jul. 2003, 10 pp.
Saxena et al., Detecting Data-Plane Failures in Point-to-Multipoint Mpls-Extensions to LSP Ping, Internet Engineering Task Force (IETF), RFC 6425, Nov. 2011, 28 pp.
Saxena et al., Detecting Data-Plane Failures in Point-to-Multipoint Mpls—Extensions to LSP Ping, Internet Engineering Task Force (IETF), RFC 6425, Nov. 2011, 28 pp.
Sun Hai-Feng, "Advanced TCP Port Scan and it's Response," O.L. Automation 2005, vol. 24, No. 4, China Academic Electronic Publishing House, Apr. 24, 2005, 2 pp. (English translation provided for abstract only).
Troutman, "DP83916EB-AT: High Performance AT Compatible Bus Master Ethernet Adapter Card," National Semiconductor Corporation, Nov. 1992, 34 pp.
U.S. Appl. No. 15/018,669, by Juniper Networks, Inc. (Inventors: Addepalli et al.), filed Feb. 8, 2016.
U.S. Appl. No. 15/198,756, by Juniper Networks, Inc. (Inventors: Seth et al.), filed Jun. 30, 2016.
Zvon, RFC 2072, [Router Renumbering Guide]-Router Identifiers, Chapter 8.3, Unnumbered Interfaces, Nov. 7, 2005, 2 pp.
Zvon, RFC 2072, [Router Renumbering Guide]—Router Identifiers, Chapter 8.3, Unnumbered Interfaces, Nov. 7, 2005, 2 pp.
CN107070689A (en) 2017-08-18
EP3188450A1 (en) 2017-07-05
US20170195209A1 (en) 2017-07-06
EP3188450B1 (en) 2019-09-18
US10284447B2 (en) 2019-05-07 Using liveness of protocols and/or interfaces to make routing decisions
JP5992602B2 (en) 2016-09-14 System and method for using label distribution protocol (LDP) in IPv6 networks
US7940678B2 (en) 2011-05-10 Method for triggering failure detection in bidirectional forwarding detection
EP2093944B1 (en) 2016-03-30 A method, a system and a router for implementing communication between the ip devices
EP2924932A1 (en) 2015-09-30 Link keepalive method, controller and switch
EP2595350B1 (en) 2018-10-17 GMPLS based OAM provisioning
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SINGH, PRASHANT;NEELAM, SAIRAM;SIGNING DATES FROM 20151221 TO 20151222;REEL/FRAME:037386/0815