The multicast boundary specifies subnets where the source traffic entering an interface is filtered to prevent the creation of mroute states on the interface. The multicast boundary can be specified through one standard ACL. However, when providing multicast services via a range of groups per service, an interface could potentially join arbitrary groups and, hence, need arbitrary combinations of ACL rules.

The Media Controller Service provides a deterministic high performance service with an easy to use API interface to manage and monitor real-time broadcast workflows in IP networks. It allows fast programming of static multicast routes and igmp snooping across L2/L3 interfaces with real-time tallies for feedback.

Multicast EOS 4.28.0F MCS

Source port filtering is enabled by default to prevent traffic from egressing out the same interface it ingressed on.

In network deployments, where border leaf or Superspine act as PEG and it is in the transit path to other multicast VTEPs, the multicast stream will not pass since the border leaf will decapsulate the packet even if it doesn't have a receiver. This transit node is called the Bud Node. The device should be able to send decapsulated packets to any local receivers as well as send the encapsulated packets to other VTEPs.

EOS currently supports EVPN Multicast by setting up PIM tunnels in the underlay with VXLAN as the transport. While this is an efficient delivery mechanism, it requires PIM to be deployed in the underlay. In certain cases, the overheads of provisioning/maintaining the multicast routers and the multicast routing state in the underlay may be significant. To support such scenarios, Ingress Replication (IR) or Head-End Replication (HER) can be used in the underlay to distribute overlay multicast traffic.

Fastdrop static is a feature that allows the static multicast routing agent to respond to cache miss messages and

IPv6 multicast routing protocols are used to distribute IPv6 datagrams to one or more recipients. IPv6 PIM builds and

Multicast Ipv6 4.21.0F

This solution allows delivery of IPv6 multicast traffic in an IP-VRF using an IPv4 multicast in the underlay network. The protocol used to build multicast trees in the underlay network is PIM Sparse Mode.

This feature provides support for packet and byte ingress counters for IPv6 multicast routes.

This feature adds support for PIM SSM (Source Specific Multicast) for IPv6 Multicast Routing on platforms listed

Multicast Ipv6 4.22.0F PIM6

This solution allows the delivery of customer BUM (Broadcast, Unknown unicast and Multicast) traffic in a VLAN using

Multicast EVPN 4.25.1

In networks where source and destination of multicast traffic all reside in the same VLAN, IPv6 multicast traffic is flooded to all ports in the VLAN by default. MLD snooping can be enabled to optimize the inefficient transmission, pruning out ports with no receivers.

This solution optimizes the delivery of multicast to a VLAN over an Ethernet VPN (EVPN) network. Without this solution IPv6 multicast traffic in a VLAN is flooded to all Provider Edge(PE) devices which contain the VLAN.

[L2 EVPN] and  [Multicast EVPN IRB] solutions allow for the delivery of customer BUM (Broadcast, Unknown unicast

This solution allows delivery of multicast traffic in an IP VRF using multicast in the underlay network. It builds on

Multicast EVPN IRB solution allows for the delivery of customer BUM (Broadcast, Unknown unicast and Multicast) traffic in L3VPNs using multicast in the underlay network. This document contains only partial information that is new or different for the Multicast EVPN Multiple Underlay Groups solution.

Multicast EVPN VXLAN EOS 4.29.1F

[L2 EVPN] and  [Multicast EVPN IRB] solutions allow for the delivery of customer BUM (Broadcast, Unknown unicast and Multicast) traffic in a L2VPN and L3VPNs respectively using multicast in the underlay network.

This feature provides multipath router id, a new multipath mode to control the behavior of RPF selection. In the

Multipath color is a new multicast multipath mode for controlling PIM RPF selection. In the default multipath

The solution described in this document allows multicast traffic arriving on a VRF interface on a Provider’s Edge (PE) router to be delivered to Customer’s Edge (CE) routers with downstream receivers in the same VPN.

The PIM routing protocol builds multicast routing state based on control packets and multicast data events. In our

BGP Multicast 4.22.0F MFA

PIM External Gateways (PEGs) allow an EVPN overlay multicast network to interface with an external PIM domain. They can be used to interconnect two data centers using an external PIM domain in between them.

Multicast EVPN 4.27.1F Oism Peg

In a Mlag setup with Pim SSM, one peer becomes the DR for a layer 3 interface and is responsible for routing multicast

The IPv6 multicast route counters count packets and bytes per group, source and vrf . Every IPv6

Multicast Counters

The multicast route counters count packets and bytes per group, source and vrf. Every multicast route will be counted when the feature is turned on if there are sufficient hardware counter resources available. 

Multicast NAT is a feature that performs NAT translations on multicast traffic. It can be configured under SVIs,

PimReg Filtering provides the ability to prevent unauthorized sources and groups from registering with a rendezvous-point (RP) router.  This is accomplished by adding the unauthorized source/group to a standard access-list. When the ACL is used on the RP, the RP inspects the source information on the PIM Register packet for a match before accepting/dropping the message.  

Multicast PimReg EOS 4.31.0F

PimReg DR Filtering provides the ability to prevent unauthorized unicast addresses from registering with a rendezvous-point (RP) router.  This is accomplished by adding the unauthorized unicast address to a standard access-list. When the ACL is used on the RP, the RP inspects the source information on the PIM Register packet for a match before accepting/dropping the message. 

Multicast EOS 4.30.2F PimReg

This feature introduces hardware forwarding support of IPv4 multicast traffic over IPv4 GRE tunnel interfaces in Arista Switches. Multicast source traffic can reach the receivers which are separated by an IP cloud which is not configured for IP multicast routing by utilizing a GRE tunnel.