Juniper Networks, Inc.

Alex Baban

Nitin Kumar

Jamsheed R Wania

Sri Karthik Goud Gadela

Nayan S Patel

Sunanda L Kommula

Alok Khambatkone

Dmitry A Shokarev

Kireeti Kompella

Jean-Marc Frailong

Zhaohui Zhang

Swamy Sadashivaiah Renu Kananda

Eswaran Srinivasan

Murtuza S Attarwala

Amit Kumar Shrivastava

Timothy L Patrick

Kurt J Windisch

Nandan Paramashiva

Mohan Tatineni

Ashish Suresh Ghule

Swamy Sadashivaiah Kananda

Anand S Athreya

Sunanda Kommula

Surya Nimmagadda

Saravanan Masilamani

Vipul Deokar

Pratik Pradip Vyas

Dimitry Shokarev

Nayan Patel

A network device may receive IPv6 fragments of a flow. Source and/or destination port information may be encoded into an upper sixteen bits of an identification number of an IPv6 fragment header of each of the IPv6 fragments. The network device may extract the source and/or destination port information from the IPv6 fragments, and may perform a spoof check of the IPv6 fragments. The network device may drop any of the IPv6 fragments that fail the spoof check, to generate remaining IPv6 fragments, and may translate the remaining IPv6 fragments into IPv4 fragments based on the source and/or destination port information. The network device may forward the IPv4 fragments toward an IPv4 cloud network.

Internet protocol (IP) version 6 fragmentation and reassembly optimization for port-aware IP translators

A network device may receive a packet and may determine whether a next header of the packet is an Internet protocol (IP) header, an Internet control message protocol (ICMP) header, or a segment routing header. The network device may determine, when the next header of the packet is the IP header, whether policy processing of the packet is set to ultimate segment decapsulation and may discard the packet when the policy processing of the packet is not set to ultimate segment decapsulation. The network device may decapsulate an outer header of the packet when the policy processing of the packet is set to ultimate segment decapsulation and may process the packet after decapsulating the outer header of the packet, to generate a processed packet. The network device may forward the processed packet toward a destination.

Processing segment routing packets with two policy processing instructions in a segment routing domain

A device receives network information associated with a network and server information associated with one or more server devices, wherein the network is associated with a network device and the one or more server devices. The device generates, based on the network information and the server information, an encapsulation profile for a tunnel encapsulation path and a route profile for the tunnel encapsulation path. The device provides, to the network device, the encapsulation profile for the tunnel encapsulation path and the route profile for the tunnel encapsulation path, and provides, to the one or more server devices, the encapsulation profile for the tunnel encapsulation path. The tunnel encapsulation path is provided between the network device and the one or more server devices, via the network, based on the encapsulation profile for the tunnel encapsulation path and the route profile for the tunnel encapsulation path.

Generating flexible, programmable, and scalable network tunnels on demand

A network device that includes a plurality of packet processing components may receive traffic associated with one or more services. The network device may store state information for each of the plurality of packet processing components, while the plurality of packet processing components are receiving the traffic. The state information may include state configuration information and/or internal storage information. The state information may be stored using a data structure that is internal to the network device and external to the packet processing component. The network device may detect an error that prevents the packet processing component from processing at least a portion of the traffic. The network device may execute, based on detecting the error that prevents the packet processing component from processing at least the portion of the traffic, a recovery procedure that uses the state information to reset the packet processing component to an operational state.

Method for resetting a packet processing component to an operational state

A first network device may receive packets as part of a traffic flow of an internet protocol session, select a packet based on a rule, and add, to a packet replica of the selected packet, routing information capable of being used to generate performance indicators associated with the IP session. The first network device may modify a portion of the packet replica to include values that will cause the packet replica to fail to reach a destination device associated with the IP session, and provide the packet replica to other network devices to cause a second network device to perform a validation procedure to determine that the packet replica is unable to be validated based on the values, to generate the performance indicators using the packet replica or a group of packet replicas that have been modified, and to provide the performance indicators to a particular device.

Systems and methods for non-intrusive network performance monitoring

A network device receives multicast packets that include information identifying destinations in the network, identifies next hops associated with the destinations, and populates a cache with the destinations and addresses of the identified next hops. The network device receives a particular multicast packet that includes information identifying particular destinations included in the cache, identifies one or more next hops for the particular destinations from the cache, and forwards the particular multicast packet to the identified one or more next hops to permit the identified one or more next hops to forward the multicast packet toward the particular destinations.

Bit index explicit replication (BIER) forwarding for network device components

A system and method for selecting packets to be forwarded from redundant multicast streams. A primary multicast stream and a secondary multicast stream are received, wherein the primary multicast stream and the secondary multicast stream are redundant multicast streams received over disjoint multicast forwarding paths. A hardware-based analyzer in a forwarding plane of the network device is applied to detect when a quality of one of the primary multicast stream or the secondary multicast stream has fallen below a threshold. In response to detecting that a quality of one of the primary multicast stream or the secondary multicast stream has fallen below a threshold, selecting, via a thread executing in a forwarding component of the network device, a different one of the primary multicast stream or the secondary multicast stream having a quality that meets the threshold, wherein selecting includes dynamically rewriting next hop operations associated with the selected stream. Packets received on the selected one of the primary multicast stream or the secondary multicast stream are forwarded and packets of the multicast stream received on the other one of the primary multicast stream or the secondary multicast stream for which the quality has fallen below the threshold are discarded.

Fast reroute of redundant multicast streams

Bit index explicit replication (BIER)forwarding for network device components

In general, techniques are described for scheduling traffic for delivery over an aggregated bundle of links. A network device comprising an interface and a data plane may implement the techniques. The interface receives packets associated with packet flows. The data plane associates each of the packet flows with a different link of an aggregated bundle of links. The data plane monitors transmission of the packets via the links to determine a representation of an amount of data sent per link. The data plane further determines that bandwidth utilization does not conform to a desired bandwidth utilization based on the determined representation of the amount of data sent per link. The data plane then re-associates the packet flows to different links of the aggregated bundle based on the determination that the bandwidth utilization does not conform to the desired bandwidth utilization.

Scheduling traffic over aggregated bundles of links

Techniques are described for maintaining a forwarding information base (FIB) within a packet-forwarding engine (PFE) of a router, and programming a packet-forwarding integrated circuit (IC) with a hardware version of the FIB. Entries of the hardware version identify primary forwarding next hops and backup forwarding next hops for the LSPs, wherein the packet-forwarding IC includes a control logic module and internal selector block configured to produce a value indicating a state of the first physical link. The selector block outputs one of the primary forwarding next hop and the backup forwarding next hop of the entries for forwarding the MPLS packets based on the value in response to the packet-processing engine addressing one of the entries of the FIB for the LSPs. Packets are forwarded with the PFE to the one of the primary forwarding next hop and the backup forwarding next hop output by the selector block.

Fast reroute for multiple label switched paths sharing a single interface

A network device receives a packet with a multicast nexthop identifier, and creates a mask that includes addresses of egress packet forwarding engines, of the network device, to which to provide the packet. The network device divides the mask into two portions, generates two copies of the packet, provides a first portion of the mask in a first copy of the packet, and provides a second portion of the mask in a second copy of the packet. The network device also forwards the first copy of the packet to an address of a first egress packet forwarding engine provided in the first portion of the mask, and forwards the second copy of the packet to an address of a second egress packet forwarding engine provided in the second portion of the mask.

Data structure-less distributed fabric multicast

A network device provides a selector list that includes indices of child nexthops associated with the network device, where each of the child nexthops is associated with a corresponding child link provided in an aggregated bundle of child links. The network device also receives an indication of a failure of a child link in the aggregated bundle of child links, and removes, from the selector list, an index of a child nexthop associated with the failed child link. The network device further receives probabilities associated with the child links of the aggregated bundle of child links. Each of the probabilities indicates a probability of a packet exiting the network device on a child link. The network device also creates a distribution table based on the probabilities associated with the child links, and rearranges values provided in the distribution table.

Growing community of inventors

San Jose, CA, United States of America

Alex Baban