Juniper Networks, Inc.

Arijit Paul

Sunesh Rustagi

Tapraj Singh

Vinay K Nallamothu

Vikas Vidyalal Patel

Mahesh Sivakumar

Ashutosh K Grewal

Maruthi Kishore Tiruveedhula

Himanshu Agarwal

Srinivas Akkipeddi

Suneel Kumar Pentala

Amit J Upadhyay

Manoj Sharma

Sudhin Jacob

Sushant Kumar

Jenchieh Tsai

Deepesh Sudhakaran Nair

Prasantha Kumar Gudipati

Naga Hari Prasad V V Chintakunta

Naga Hari Prasad VV Chintakunta

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 leveraging a containerized routing protocol process to implement virtual private networks using routing protocols. In an example, a system comprises a container orchestration system for a cluster of computing devices, the cluster of computing devices including a computing device, wherein the container orchestration system is configured to: deploy a containerized application to a compute node; and in response to deploying the containerized application to the compute node, configure in the compute node a virtual routing and forwarding (VRF) instance to implement a virtual private network (VPN) for the containerized application.

Containerized routing protocol process for virtual private networks

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, techniques are described for reporting dynamic tunnels to a path computation element (PCE) of a network to inform path computation by the PCE for traffic engineering within the network. In some examples, a method comprises generating, by a network device configured to route network packets within a network, a dynamic tunnel report message that includes dynamic tunnel description data for a dynamic tunnel that transports the network packets through the network, wherein the network packets transported by the dynamic tunnel each comprises an outer header that does not include a multiprotocol label switching (MPLS) transport label; and sending, by the network device, the dynamic tunnel report message to a path computation element (PCE) for a path computation domain to report the dynamic tunnel to the PCE for inclusion in path computation by the PCE for label switched paths of the network.

Dynamic tunnel report for path computation and traffic engineering within a computer network

Techniques are described for migrating data traffic, based on a new protocol priority value, from one Label Switched Path (LSP) assigned a higher initial protocol priority value to another LSP assigned a lower initial protocol priority value. For example, a network may initially establish a resource reservation LSP associated with a resource reservation protocol assigned a higher initial protocol priority value than a segment routing protocol used to establish a segment routed LSP. Rather than being unable to send data traffic on an established segment routed LSP because the segment routing protocol has a lower initial protocol priority than the resource reservation protocol, an ingress router may receive from a centralized controller a message specifying a new protocol priority value assigned to the segment routed LSP in response to which the ingress router may create or update its initial protocol priorities, and forward data traffic along the segment routed LSP.

Migrating data traffic between label switched paths (LSPs) based on per-LSP protocol priority value

Techniques are described for establishing a segment routed label switched path (LSP) regardless of whether a router along the shortest path is not enabled for segment routing. For example, a resource reservation LSP (e.g., a resource reservation protocol (RSVP) LSP) is established across the router that is not enabled for segment routing, such that the segment routed LSP may be established to tunnel through the resource reservation LSP. For example, when a centralized controller receives a request to establish a path using segment routing, one or more routers along the shortest path may not be enabled for segment routing. Instead of rejecting the request to establish the segment routed LSP in response to determining that one or more routers in a selected path are not enabled for segment routing, the controller may establish a resource reservation LSP to tunnel around the router that is not enabled for segment routing.

Segment routing label switched path for non-segment routing enabled routers

A network device operable as a provide edge router is described. The network device comprises one or more processors operably coupled to a memory; a configuration interface configured for execution by the one or more processors to receive configuration data configuring the network device as a provider edge router of an intermediate layer 3 network to provide multi-homed layer 2 virtual bridge connectivity to a customer edge device using an active-standby mode of operation; and a routing process configured for execution by the one or more processors to send, to a remote provider edge router in response to determining the network device is able to send layer 2 packets to the customer edge device, a route advertisement that includes a static route specifying a layer 3 address of the customer edge device as a next-hop for a layer 3 subnet.

Static route advertisement

In one example, a method includes performing L2 learning of a C-MAC address included in a first L2 data message by a first provider edge (PE) router included in an Ethernet Segment of a Provider-Backbone Bridging Ethernet Virtual Private Network (PBB-EVPN); sending to a second PE router within the Ethernet Segment an L2 control message comprising the C-MAC address and a B-MAC address corresponding to the Ethernet Segment of the PBB-EVPN, wherein the L2 control message informs the second PE router of the reachability of the C-MAC address through the first PE router; receiving, by the first PE router and from the second PE router, a second L2 data message as unicast traffic destined for the C-MAC address; and forwarding the second L2 data message to the first CE router.

System for avoiding traffic flooding due to asymmetric MAC learning and achieving predictable convergence for PBB-EVPN active-active redundancy

In one example, a method includes configuring a first provider edge (PE) router of a Provider Backbone Bridging (PBB) Ethernet Virtual Private Network (EVPN) to join an Ethernet Segment in active-active mode with at least a second PE router that is operating as a designated forwarder for the Ethernet Segment; receiving, by the first PE router from a remote PE router and prior to the first PE router performing Media Access Control (MAC) learning of a customer-MAC (C-MAC) address that is reachable via a backbone-MAC (B-MAC) address associated with the Ethernet Segment, a network packet that includes the C-MAC address; and in response to determining that the C-MAC address has not been learned by the first PE router and the B-MAC address included in the network packet is associated with the Ethernet Segment, forwarding, by the first PE router, the network packet to a destination identified by the C-MAC address.

Growing community of inventors

Cupertino, CA, United States of America

Arijit Paul