Juniper Networks, Inc.

Robert W Kebler

Vikram Nagarajan

Anish Peter

Vinod Kumar N

Kapil Arora

Princy T Elizabeth

Hariharan Boopathy

Soumyodeep Joarder

Ashok Patrick Jude Manoharan

Sanoj Kadavil Vivekanandan

Sunil Kumar

Alia Karin Atlas

Rahul Unnikrishnan

Maciek Konstantynowicz

Himanshu Agarwal

Ramesh Kandula

Dinesh Sivaraj

Venkata Lakshmana Murthy Varahabhotla

Nitin Kumar

Wen Lin

Nischal Sheth

Eric C Rosen

Michal Styszynski

Bharath RadhaKrishna Bhat

Abhishek Asthana

Naveen Ashik

Jayakumar Ramalingam

Satish Ramachandran

Vikram Nagaranjan

N Vinod Kumar

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

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

In general, techniques are described for enabling a network of network devices (or 'nodes') to provide redundant multicast streams from redundant multicast sources to an egress network node. In some examples, the egress network node (or a controller for the network) computes maximally redundant trees (MRTs) from the egress network node to a virtual proxy node virtually added to the network topology by the egress network node for redundant multicast sources of redundant multicast streams.

Maximally redundant trees to redundant multicast source nodes for multicast protection

A device may store first information regarding a first pseudowire connection with a first device, wherein the first pseudowire connection provides access to an Ethernet virtual private network (EVPN) to communicate with a host device. The device may store second information regarding a second pseudowire connection with a second device, wherein the second pseudowire connection provides access to the EVPN to communicate with the host device. The device may receive a message that includes a configuration identifier and identify the configuration identifier. The device may change a first characteristic of the first pseudowire connection based on the configuration identifier. The device may change a second characteristic of the second pseudowire connection based on the configuration identifier. The device may receive data from the host device based on changing the first characteristic of the first pseudowire connection and changing the second characteristic of the second pseudowire connection.

Coordinating pseudowire connection characteristics and multi-homed provider edge device capabtilities

Techniques are described for facilitating node protection for Broadcast, unknown Unicast, and Multicast (BUM) traffic for a multi-homed node failure. For example, each VTEP (e.g., PE device) may advertise a protected VTEP address that indicates an IP address of a remote PE device that is to be protected in the event of a node failure. In the event a multi-homed PE device fails, the ingress PE device sends a BUM packet including the protected VTEP address for the failed node. When an egress PE device receives the BUM packet, the egress PE device determines whether the BUM packet includes the protected VTEP address and whether the egress PE device is operating as a backup designated forwarder (DF). If the BUM packet includes the protected VTEP address and the egress PE device is a backup DF, the egress PE device forwards the BUM traffic to the ESI.

Node protection for bum traffic for multi-homed node failure

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

The potential problem of too many unique protocol independent multicast (PIM) joins (corresponding to unique (Source, Group) combinations) in PIM join/prune messages being received by a router may be solved by controlling (e.g., limiting) a number of unique PIM joins to be sent to the router from a downstream device. This may be accomplished, for example, by communicating a limit (or multiple different limits) from a PIM device to one or more downstream PIM neighbors. For example, the limit may be encoded in a PIM Hello message (e.g., as an Option Type-Length-Value (TLV)).

Controlling an aggregate number of unique PIM joins in one or more PIM join/prune messages received from a PIM neighbor

The potential problem of sending (or resending) PIM join/prune messages (referred to as 'PIM join(s)') too infrequently may be solved by: (a) sending a PIM join, including a unique message identifier value, to an upstream PIM peer; (b) responsive to sending the PIM join, (1) starting a quick refresh timer, and (2) starting a standard refresh timer, which is longer than the quick refresh timer; (c) responsive to a determination that the quick refresh timer expired, (1) resending the PIM join to the upstream PIM peer, and (2) restarting the quick refresh timer; (d) responsive to a determination that the standard refresh timer expired, (1) resending the PIM join message to the upstream PIM peer, and (2) restarting the standard refresh timer; (e) receiving a PIM join response from the upstream PIM peer, wherein the PIM join response includes a unique message identifier value; (f) responsive to receiving the PIM join response and determining that the unique message identifier value in the PIM join response matches the unique message identifier value in the PIM join/prune message, stopping the quick refresh timer. The potential problem of sending (or resending) PIM joins too frequently may be solved by having the PIM join response further include a long refresh timer value, and responsive to receiving the PIM join response from the upstream peer, further (1) stopping the standard refresh timer, and (2) starting a long fresh timer using the long refresh timer value, and responsive to determining that the long refresh timer expired, (1) resending the PIM join/prune message to the upstream PIM peer, and (2) restarting the long refresh timer.

Controlling protocol independent multicast (PIM) join/prune messages from a downstream PIM neighbor using a PIM join/prune response(s) from an upstream PIM neighbor

Techniques are described for multicast flow prioritization in protocol independent multicast (PIM) networks with multicast flow limits. According to the disclosed techniques, once a router has reached its multicast flow limit, the router may preempt an installed lower priority multicast flow with a newly requested higher priority multicast flow. For example, if a maximum number of multicast flows are installed on the router, then, upon receiving a PIM join for a higher priority flow as compared to the installed flows, the router replaces one of the installed lower priority flows with the received higher priority flow. Furthermore, according to the disclosed techniques, priority values for multicast flows are consistent across a PIM domain and each of the routers within the PIM domain is configured to use the priority values to select a higher priority flow over a lower priority flow.

Multicast flow prioritization

Techniques are described for facilitating node protection for Broadcast, unknown Unicast, and Multicast (BUM) traffic for a multi-homed node failure. For example, multi-homed provider edge (PE) devices each advertise egress node protection labels to an ingress PE device. In the event one of the multi-homed PE devices fails, the ingress PE device sends a BUM packet including the egress node protection labels for the failed node. When an egress PE device receives the BUM packet, the egress PE device determines whether the BUM packet includes the egress node protection labels and whether the egress PE device is operating as a backup designated forwarder (DF) on an Ethernet segment identifier (ESI) for which the failed node was the DF. If the BUM packet includes the egress node protection labels and the egress PE device is operating as a backup DF, the egress PE device forwards the BUM traffic to the ESI.

Growing community of inventors

Newburyport, MA, United States of America

Robert W Kebler