Juniper Networks, Inc.

Vinod Kumar N

Robert W Kebler

Hariharan Boopathy

Vikram Nagarajan

Ashok Patrick Jude Manoharan

Sunil Kumar

Dinesh Sivaraj

Ramakrishnan Shanmuga Sundaram

Michal Styszynski

Sudarsanan Codandam

Ravi M R

In some examples, a method includes receiving, by an egress network device for a network, messages from each of a plurality of ingress network devices for the network, wherein each of the messages specifies a multicast source, a multicast group, and an upstream multicast hop weight value for multicast traffic for the multicast source and the multicast group; selecting, by the egress network device and based on the upstream multicast hop weight values specified by the received messages, one of the plurality of ingress network devices to which to send a multicast join message of a plurality of multicast join messages for the multicast source and multicast group; and sending, by the egress network device, the multicast join message to the selected one of the plurality of ingress network devices.

Weighted multicast join load balance

Techniques are described for dynamically computing a segment routing policy for a segment routing for traffic engineering (SR-TE) path. For example, in a discontinuous SR network in which SR islands (e.g., groups of neighboring routers that are enabled for segment routing) are separated by one or more routers not enabled for segment routing, instead of returning a failure because one or more routers along a path are not enabled for SR, an ingress router may generate an SR-TE operations, administrations, and management (OAM) Multi-Protocol Label Switching (MPLS) traceroute packet send the packet to a first border router of the RSVP-enabled devices along a computed path to trigger the creation of a resource reservation Label Switched Path (LSP) through the RSVP-enabled devices. In this way, segment routed LSP may be established to tunnel through the resource reservation LSP for a SR-TE path used in an SR-TE policy.

Dynamic computation of SR-TE policy for SR-enabled devices connected over non-SR-enabled devices

An example egress network device includes at least one computer processor and a memory. The memory includes instructions that cause the at least one computer processor to receive messages from each of a plurality of ingress network devices. Each message specifies a multicast source as an anycast address that belongs to two or more sources, a multicast group, and a customer site identifier that uniquely identifies a customer network device via which the anycast address is reachable. The instructions cause the at least one computer processor to select, based on the customer site identifiers, one of the plurality of ingress network devices to which to send a multicast join message of a plurality of multicast join messages for the multicast source and multicast group. The instructions cause the at least one computer processor to send the multicast join message to the selected one of the plurality of ingress network devices.

Upstream multicast hop (UMH) extensions for anycast deployments

The techniques describe example network systems providing core-facing designated forwarder (DF) election to forward multicast traffic into an EVPN of a core network. For example, a first PE device of a plurality of PE devices participating in an EVPN comprises one or more processors operably coupled to a memory, wherein the one or more processors are configured to: determine that a first multicast traffic flow has started for the first PE device; in response, send a source-active (SA) route to indicate the first multicast traffic flow has started for the first PE device; receive, from a second PE device, a second SA route that indicates that a second multicast traffic flow has started for the second PE device; and perform an election of a core-facing DF from among the first PE device and second PE device, wherein the core-facing DF is configured to forward the multicast traffic into the EVPN.

EVPN multicast ingress forwarder election using source-active route

An example network device includes a memory; and processing circuitry configured to: determine a primary path between the network device and a second network device; determine candidate backup paths between the network device and the second network device; in response to a determination that a first candidate backup path of the candidate backup paths satisfies a first priority criteria, select the first candidate backup path as a backup path; in response to a determination that a second candidate backup path of the candidate backup paths satisfies a second priority criteria, select the second candidate backup path as the backup path; and program a packet processor of the network device with the primary path and the backup path. The first priority criteria and the second priority criteria can be based on a risk of simultaneous failure of the primary path and a candidate backup path of the plurality of backup path.

Determining shielded backup paths

In some examples, a network device may determine whether a first egress network device is segment routing (SR) aware. Based on the first egress network device being SR aware, the network device may initiate establishment of an SR tunnel toward the first egress network device. The network device may forward multicast traffic on the SR tunnel. The network device may also determine whether a second egress network device is SR aware. Based on the second egress network device not being segment routing aware, the network device may initiate establishment of a non-SR tunnel toward the second egress network device. The network device may forward multicast traffic on the non-SR tunnel.

Ingress replication procedures to facilitate migration to segment routing technology in a computer network

An example network device includes memory configured to store packet data and processor circuitry coupled to the memory. The processing circuitry is configured to determine that a first host device has moved from a first access network of an Ethernet virtual private network (EVPN) associated with the first PE router to a second access network of the EVPN, wherein the first host device is interested in receiving traffic of a first multicast group. The processing circuitry is configured to determine whether any other host device on the first access network of the network device is interested in receiving traffic of the first multicast group. Based on no other host device on the first access network of the network device being interested in receiving multicast traffic of the first multicast group, the processing circuitry is configured to delete state associated with the first multicast group.

Internet group management protocol host mobility in ethernet virtual private network multicast networks

The techniques describe example network systems for adaptively determining whether to perform ingress replication or assisted replication of a multicast flow based on classification of the multicast flow. For example, a provider edge (PE) device of a plurality of PE devices participating in an EVPN comprises one or more processors operably coupled to a memory, wherein the one or more processors are configured to: receive a multicast traffic flow, determine a classification of the multicast traffic flow, and perform, based at least in part on the classification of the multicast traffic flow, one of: ingress replication of the multicast traffic flow or assisted replication of the multicast traffic flow.

Replication mode selection for EVPN multicast

In general, techniques are described for providing Hot-Root Standby in Global Table Multicast (GTM) environments. For example, in such GTM environments, normally a single unicast route to the customer multicast source ('C-Source') will be available to egress provider edge (PE) routers. As described herein, ingress PE routers may advertise multiple routes to a C-Source, including unicast routes that include Route Import Extended Communities, which are imported by egress PE routers. This enables an egress PE router to have multiple paths to the C-Source, and the egress PE router may generate multiple C-multicast source tree joins for respective ingress PE routers in order to receive respective multicast streams sourced by the C-Source from the ingress PE routers.

Growing community of inventors

Bengaluru, India

Vinod Kumar N