Juniper Networks, Inc.

Jimmy Jose

Reji Thomas

Sairam Neelam

Amit Arora

Sandip Kumar Ghosh

Harmeet Singh

Samson P Ninan

Vivek R

Raveendra Torvi

Ashish Kumar

Srihari Ramachandra Sangli

Pranavadatta D N

Vivek Ramesh

Vasudevan Navaneetha Krishnan

Satish Dattatri

Vinod Arumugham Chettiar

Srikanth Venakta Gandiboyina

A network device may detect an error associated with a packet based on error information being generated from processing the packet at a layer of a network stack. The network device may determine, based on detecting the error, metadata associated with the packet. The network device may generate telemetry data to include the metadata. The network device may provide the telemetry data to a network analyzer for policy enforcement.

Collection of error packet information for network policy enforcement

A method and network device for detecting a TCP socket failure is described. A network device may be configured to detect a failure of a link between a first node and a second node, determine one or more transmission control protocol (TCP) sockets of a plurality of TCP sockets on the first node that are communicating over the link between the first node and the second node, write information to a TCP stack for the determined one or more TCP sockets, the information indicating that the determined one or more TCP sockets have an error, and remediate the determined one or more TCP sockets in response to the information.

Propagating node failure errors to TCP sockets

A network device in a network may determine a tentative network address for a network interface of the network device and may determine whether the tentative network address is duplicative of any one of the network addresses in the network. If the tentative network address is duplicative of a network address assigned to another network interface in the network, the network device may store an indication of the other network interface. In response to receiving an indication that a new network address is assigned to the other network interface, the network device may re-determine whether the tentative network address is duplicative of any one of the network addresses in the network. If the network device determines that the tentative network address is not duplicative of any one of the plurality of network addresses in the network, the network device may assign the tentative network address to the network interface.

Automatic recovery from duplicate network addresses

A disclosed method may include (1) identifying a memory buffer that is allocated to a packet on a computing device, (2) identifying one or more characteristics of the memory buffer allocated to the packet on the computing device, (3) determining, based at least in part on the characteristics of the memory buffer, that the memory buffer allocated to the packet has leaked, and then in response to determining that the memory buffer has leaked, (4) performing at least one action to remedy the leak of the memory buffer. Various other apparatuses, systems, and methods are also disclosed.

Apparatus, system, and method for detecting and remedying memory buffer leaks in network devices

In general, this disclosure describes a network device that checks consistency between routing objects in a routing information base (RIB), a forwarding information base (FIB), and packet forwarding engine (PFE) forwarding tables. A method includes generating a marker that causes a routing protocol daemon, a control plane kernel, and PFEs of a network device to calculate zonal checksums for a plurality of zones using consistency values for each routing object within a RIB, a FIB, and corresponding forwarding tables respectively. The method includes performing a consistency check on the RIB, the FIB, and the forwarding tables to determine whether the routing objects in each of the RIB, the FIB, and the forwarding tables are consistent with each other. The method includes, when the RIB, the FIB, and the forwarding tables are not consistent, performing an action related to at least one of RIB, the FIB, or the forwarding tables.

Route consistency checker for network devices

A network device may determine a control plane session type associated with a control plane session. The control plane session may be associated with the network device. The network device may determine whether the control plane session type is associated with a forwarding information base (FIB) cache on the network device. The network device may obtain, based on determining that the control plane session type is associated with the FIB cache, forwarding information associated with the control plane session. The forwarding information may be stored in a FIB, associated with the FIB cache, on the network device. The network device may store the forwarding information in the FIB cache and process the control plane session using the forwarding information stored in the FIB cache.

Forwarding information base caching

The disclosed computer-implemented method may include (1) creating, at a proxy node within an IP network, a proxy group that includes a plurality of network nodes within a subnet of the IP network that are represented by a pseudo MAC address, (2) receiving a neighbor solicitation from a network node included in the proxy group, (3) identifying, within the neighbor solicitation, a link-layer address of the network node that sent the neighbor solicitation, (4) modifying the neighbor solicitation by replacing the link-layer address of the network node with the pseudo MAC address of the proxy group, and then (5) forwarding the modified neighbor solicitation to another network node included in the proxy group to facilitate completion of an NDP process in which the other network node responds to the modified neighbor solicitation with a neighbor advertisement proxied by the proxy node. Various other methods, systems, and apparatuses are also disclosed.

Method, system, and apparatus for proxying intra-subnet traffic across multiple interfaces within networks

In general, techniques provide a mapping of host devices to different virtual router identifiers used to identify the source MAC address used for forwarding packets to the participating host devices. For example, a method may include receiving an Address Resolution Protocol (ARP) request for a first Internet protocol (IP) address from a host device, the first IP address comprising a virtual IP address of the virtual router. The method may also include determining a virtual router redundancy protocol (VRRP) virtual router identifier (VRID) associated with the first IP address. The method may further include generating a mapping between the host device and the determined VRID. The method may also include determining a virtual source MAC address of the virtual router based on the mapping and forwarding a second packet to the host device that specifies a virtual source MAC address for the second packet.

Source MAC access controls in a virtual redundant router protocol environment

A first network device may activate the first network device as being associated with a Virtual Router Redundancy Protocol (VRRP) group. The first network device may receive, from a second network device, a duplicate address detection message. The first network device may compare a data link layer address associated with the duplicate address detection message and a Virtual Media Access Control (VMAC) address of the VRRP group. The first network device may disregard the duplicate address detection message after comparing the data link layer address and the VMAC address of the VRRP group.

Avoiding false duplicate network address detection in virtual router redundancy protocol (VRRP) scenarios

Techniques are described for providing an indication of an impending control plane disruption of a router using forwarding plane liveliness detection protocols. A forwarding plane of the router outputs liveliness detection messages that, when received by a peer router, provide an indication that the forwarding plane is operational and able to forward packets. When constructing the liveliness detection messages, the forwarding plane may embed additional information indicative of any impending disruption in the control plane of the network device. In this way, the forwarding plane of the transmitting router provides an indication to the peer router that, although currently operational, the control plane of the router may in the near term become non-operational. The peer router, in response to receiving an enhanced liveliness detection message indicating an impending control plane disruption, suppresses a recovery action otherwise triggered by a loss of communication with a control plane of the network device.

Growing community of inventors

Hosur, India

Jimmy Jose