Juniper Networks, Inc.

Ashutosh K Grewal

Jaihari V Loganathan

Sanjay Khanna

Kaliraj Vairavakkalai

Raghavendra Mallya

Babu Singarayan

Mahesh Sivakumar

Vinay K Nallamothu

Jeyananth Minto Jeganathan

Srinivas Akkipeddi

Aman Kapoor

Arijit Paul

Kevin F Wang

Yuvaraja Mariappan

Shailender Sharma

Sachchidanand Vaidya

Kiran K N

Pranavadatta D N

Narendranath Karjala Subramanyam

Pavan Kumar Kurapati

Philip M Goddard

Sivakumar Ganapathy

In general, this disclosure describes techniques for a containerized router operating within a cloud native orchestration framework. In an example, a computing device comprises processing circuitry; a containerized set of workloads; a containerized routing protocol process configured to execute on the processing circuitry and configured to receive routing information; a kernel network stack executing on the processing circuitry and configured to forward packets based on first routing information from the containerized routing protocol process; and a data plane development kit (DPDK)-based virtual router executing on processing circuitry and configured to forward traffic to and from the workloads based on second routing information from the containerized routing protocol process.

Containerized router with a disjoint data plane

In general, this disclosure describes techniques for a containerized router operating within a cloud native orchestration framework. In an example, a virtualized cell site router comprises a computing device configured with a containerized router, the computing device comprising: a containerized virtual router configured to execute on the processing circuitry and configured to implement a data plane for the containerized router; a containerized routing protocol process configured to execute on the processing circuitry and configured to implement a control plane for the containerized router; and a pod comprising a containerized distributed unit, wherein the containerized routing protocol process is configured to advertise routing information comprising reachability information for the containerized distributed unit.

Containerized router with virtual networking

A network device, associated with peer network devices, may receive policy information for a protocol; and compute a first update message based on information regarding a route associated with the policy information. The network device may determine that an upper utilization threshold for one or more of peer queues, associated with the peer network devices, is not satisfied; and write the first update message to the peer queues based on determining that the upper utilization threshold is not satisfied. The network device may compute a second update message based on the information regarding the route; determine that the upper utilization threshold for one or more of the peer queues is satisfied; and pause writing the second update message to the peer queues based on the upper utilization threshold being satisfied. The network device may permit the peer network devices to obtain data from corresponding ones of the peer queues.

Regulating enqueueing and dequeuing border gateway protocol (BGP) update messages

In general, this disclosure describes techniques for a containerized router operating within a cloud native orchestration framework. In an example, a computing device comprises processing circuity; a containerized set of workloads; a containerized routing protocol process configured to execute on the processing circuitry and configured to receive routing information; a kernel network stack executing on the processing circuitry and configured to forward packets based on first routing information from the containerized routing protocol process; and a data plane development kit (DPDK)-based virtual router executing on processing circuitry and configured to forward traffic to and from the workloads based on second routing information from the containerized routing protocol process.

In general, the disclosure describes techniques for lockless management of immutable objects by multi-threaded processes. A device comprising a processor may implement the techniques, where the processor execute a multi-threaded process including a producer thread and a consumer thread. The producer thread may instantiate an immutable object, and provide, to the consumer thread, a reference to the immutable object. The producer thread may also increment a reference counter to indicate that the reference has been provided to the consumer thread, where the reference counter is local to the producer thread and inaccessible to the at least two consumer threads. The producer thread may receive, from the consumer thread, a notification that the consumer thread has finished processing the immutable object, and decrement, responsive to receiving the notification, the reference counter. The producer thread may then delete, based on the reference counter, the immutable object.

Lockless management of immutable objects by multi-threaded processes using multiple counters

In general, the disclosure describes techniques for distributing processing of routes among multiple execution threads of a network device. In some examples, a method includes partitioning a routing information base (RIB) into a plurality of RIB partitions, assigning a route processing thread to each RIB partition, processing BGP routing protocol messages at each of the route processing threads, and receiving, at a BGP update thread serving a BGP peer group, from two or more of the route processing threads, route update information for routes to be advertised. The route update information includes a BGP route tuple having a network prefix value and a pointer to an outgoing attribute. The method further includes collecting, based on the BGP route tuples, route update information for routes having the same outgoing attribute and constructing a BGP update message from the collected route update information.

Border gateway protocol update packing for a distributed routing information base

In some examples, a method includes selecting, by a first virtual routing node of a single-chassis network device having a plurality of forwarding components and a plurality of fabric links coupling respective pairs of the plurality of forwarding components at respective fabric interfaces of the plurality of forwarding components, a fabric interface of a forwarding component of the plurality of forwarding components that has an egress interface toward a network destination and that is associated with the first virtual routing node; advertising, to the second virtual routing node, the fabric interface as a next hop for the network destination and a label for use in establishing a transport label switched path (LSP); and computing, by the second virtual routing node, a path for the transport LSP to include the fabric interface, and establishing the transport LSP along the computed path.

Transport LSP setup using selected fabric path between virtual nodes

In some examples, a method includes selecting, by a first virtual routing node of a single-chassis network device having a plurality of forwarding components and a plurality of fabric links coupling respective pairs of the plurality of forwarding components at respective fabric interfaces of the plurality of forwarding components, a fabric interface of a forwarding component having an egress interface toward a network destination and that is associated with the first virtual routing node; advertising, to the second virtual routing node, the fabric interface as a next hop for the network destination; storing, by the second virtual routing node to a context data structure of the second virtual node, the fabric interface as a next hop for the network destination; selecting the fabric interface from among a plurality of fabric interfaces as a next hop for the network destination; and forwarding network traffic destined for the network destination to the selected fabric interface.

Advertising selected fabric paths for service routes in virtual nodes

In some examples, a method includes selecting, by a first virtual routing node of a single-chassis network device having a plurality of forwarding components and a plurality of fabric links coupling respective pairs of the plurality of forwarding components at respective fabric interfaces of the plurality of forwarding components, a fabric interface of a forwarding component of the plurality of forwarding components that has an egress interface toward a network destination and that is associated with the first virtual routing node; in response to receiving a message specifying the fabric interface, storing, by the second virtual routing node to a context forwarding table of the second virtual node, the fabric interface as a next hop for the network destination; selecting, by the second virtual routing node and based on the context forwarding table and a context next hop in a first forwarding table pointing to the context forwarding table, the fabric interface for forwarding network packets destined for the network destination.

Growing community of inventors

Sunnyvale, CA, United States of America

Ashutosh K Grewal