• Tag : Multicast

 
 

Multicast tree control in multi-tiered fabrics

Description Multipath color is a new multicast multipath mode for controlling PIM RPF selection. In the default multipath deterministic mode, multiple PIM routers with the same set of ECMPs to the source may make a different RPF selection decision. This may result in wasted bandwidth consumption since traffic may be unnecessarily duplicated. In multipath color mode, all PIM routers with the same set of ECMPs to the source make the same RPF selection decision (per source-group). Traffic is load balanced across ECMPs by source-group. Upstream PIM routers advertise a multipath color value in the PIM Hello message that downstream PIM...
Continue reading →

Multicast

Need some guidance on multicast implementation where we need to enable for video streams. Standard Spine and Leaf setup with multiple vlans both receivers and source are located in Vlan 10 at different location/vtep enabled igmp snooping + querier on all vtep receiver located at different vtep from the source are not receiving any stream Trying to find documentation on what i may missed or if any experts can provide any clues.  

Support for multicast (S,G) counters

Description 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. As there is a limited number of hardware counter resources, selected multicast routes can be “prioritized” in order to provide them the needed hardware counter resources over the “non-priority” multicast routes in case of resource contention. Priority multicast routes can be configured if: Hardware counter resources are available: The priority multicast routes do not affect the existing non-priority multicast route counters. In case there are insufficient...
Continue reading →

Multicast EVPN All-Active Multihoming

Description [L2-EVPN] and  [Multicast EVPN IRB] solutions allow for the delivery of customer BUM (Broadcast, Unknown unicast and Multicast) traffic in a VLAN and L3VPNs respectively using multicast in the underlay network. This document describes the solution to support all-active multihoming for customer multicast traffic as described in [IGMP PROXY] . More information about VXLAN EVPN all-active multihoming may be found in [VXLAN EVPN All-Active Multihoming]. Multicast All-Active Multihoming IGMP PROXY support As described in [IGMP PROXY], in an all-active redundancy mode, IGMP reports from the CE may arrive at any one of the multihomed peers. The multihomed peer which...
Continue reading →

Multicast EVPN IRB

Description This solution allows delivery of multicast traffic in an IP-VRF using multicast in the underlay network. It builds on top of [L2-EVPN], adding support for L3 VPNs and Integrated Routing and Bridging (IRB).  The protocol used to build multicast trees in the underlay network is PIM Sparse Mode. In the figure above: VLAN 10 and VLAN 20 have SVIs provisioned on all VTEPs and are associated with the L3 VRF red. There are interested receivers in VLANs 10 and 20 on VTEP2, and in VLAN 20 on VTEP 3. Traffic arriving in VLAN 10 on VTEP 1 is: Delivered...
Continue reading →

Layer 2 Multicast EVPN

Description This solution allows the delivery of customer BUM (Broadcast, Unknown unicast and Multicast) traffic in a VLAN using multicast in the underlay network. BUM traffic can be classified into two traffic types: Flooded Traffic: This is broadcast, unknown unicast, and link-local multicast traffic, which is flooded to all VTEPs Multicast Traffic: This traffic is sent to VTEPs with interested receivers. The solution implements the procedures described in [IGMP PROXY], which use a BGP EVPN control plane and a VXLAN forwarding plane. Using multicast in the underlay network (as opposed to unicast) has the advantage of being bandwidth efficient. The...
Continue reading →

Arista Fabric Integration with Microsoft Network Load Balancing

Overview This article provides a brief introduction and configuration of Microsoft NLB with Arista L2LS (without VxLAN) and L3LS VxLAN fabric setup to avoid the most common issues during the deployments. NLB Introduction The Network Load Balancing (NLB) feature distributes traffic across several servers by using the TCP/IP networking protocol. By combining two or more computers that are running applications into a single virtual cluster, NLB provides reliability and performance for web servers and other mission-critical servers. Three modes of operation in NLB Unicast All the NICs assigned to a Microsoft NLB cluster share a common MAC address. The MAC...
Continue reading →

Curl’ing with EOS and third party devices

Perhaps you’re aware that EOS is based on Linux, which comes with many powerful & useful built-in utilities. I recently wrote an EOS Central article on sed. Even if you are not a pure networking person (perhaps you’re a server person), many of the familiar Linux tools you have used in your past exist on EOS natively today. One of my customers recently shared an experience with me that made me smile because they had now started to embrace the Linux underpinnings & power of EOS after running into a configuration challenge with a 3rd party (television) broadcast IP/SDI gateway...
Continue reading →

Support for multicast (S,G) counters

Description 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. As there is a limited number of hardware counter resources, selected multicast routes can be “prioritized” in order to provide them the needed hardware counter resources over the “non-priority” multicast routes in case of resource contention. Priority multicast routes can be configured if: Hardware counter resources are available: The priority multicast routes do not affect the existing non-priority multicast route counters. In case there are insufficient...
Continue reading →

Support for Multicast NAT

Description Multicast NAT is a feature that performs NAT translations on multicast traffic. The following multicast features are supported: Source Static NAT on egress interface Destination Static NAT on ingress interface Twice Static NAT on egress interface Can be enabled on SVI, VLAN, and Port Channel. Platform Compatibility CCS-720XP-24ZY4 CCS-720XP-24Y6 CCS-720XP-48Y6 CCS-720XP-48ZC2 DCS-7050SX3-48YC12 DCS-7050TX3-48C8 DCS-7050CX3M-32S DCS-7050CX3-32S DCS-7050SX3-48YC8 DCS-7050SX3-48C8 Configuration Configuration of Multicast NAT is similar to the existing NAT CLI configuration commands. Below are sample configurations for setting up static multicast NAT translation. 1) Twice NAT on egress interface Ethernet8 for multicast traffic 224.1.1.1 coming from host 192.168.20.1 ingressing on...
Continue reading →

Support for IPv6 multicast (S,G) counters

Description The IPv6 multicast route counters count packets and bytes per group, source and vrf  Every IPv6 multicast route will be counted when the feature is turned on if there are sufficient hardware counter resources available. As there is a limited number of hardware counter resources, selected IPv6 multicast routes can be “prioritized” in order to provide them the needed hardware counter resources over the “non-priority” IPv6 multicast routes in case of resource contention. Priority IPv6 multicast routes can be configured if: Hardware counter resources are available: The priority multicast routes do not affect the existing non-priority multicast route counters....
Continue reading →

Multicast Monitoring in CVP

Hi all, is there any way inside CVP to have a visual (table, graph, etc..) of the multicast flow, for example have a list of all multicast group and, for each group, details as: switch, position (Ingress, Egress, Core) and bitrate on the involved interfaces? Thanks! Andrea

Fastdrop static

Description Fastdrop static is a feature that allows the static multicast routing agent to respond to cache miss messages and dynamically create fastdrop routes. For 7280R/7500R based platforms, when multicast routing is enabled on an interface an mroute is needed to forward traffic to L3 and L2 OILs as the platform can only do S, G lookup or EthGroup lookup, not both. With dynamic multicast routing, this is taken care of by the PIM agent. The use case for this feature is when static multicast routing is being used, but there are not static mroutes for all S,Gs. If traffic...
Continue reading →

Multicast multipath router-ID (IPv4)

Description This feature provides multipath router-id, a new multipath mode to control the behavior of RPF selection. In the default multipath mode, it is possible that downstream Pim neighbors will select as RPF different upstream Pim neighbors despite having the same ECMP routes to the source. This may have the undesirable effect that the source has to deliver to multiple upstream Pim neighbors instead of one. When multipath router-id is configured, traffic for a group or source-group will be routed through only one upstream PIM neighbor for all downstream PIM neighbors given that these neighbors have the same ECMP routes...
Continue reading →

Tap Aggregation PTP Sync & Transparent Clock (TC) PTP Multicast Configuration

 Description This article covers the configuration required to run the PTP TC with multicast transport environment, and Tap Aggregation DUT time sync with PTP GM. Platform Compatibility DCS-7020 DCS-7280SE/ DCS-7500E DCS-7280R/RX DCS-7500R/RX DCS-7150 DCS-7050X/XX DCS-7060X/XX Topology Diagrams     Configuration In this PTP implementation example, the NY1 will act as BC and NY4 as GM. Both are configured as PTP BC clocks but NY4 due to its lower Priority1 value will win the BCMA election and becomes the master. The NY2 and NY3 are configured as E2E TC clocks and will require PIM to forward the PTP messages generated by...
Continue reading →

IGMP Host-proxy

Interfaces on the switch can be configured to serve as IGMP host proxies. An IGMP host proxy exchanges IGMP reports (joins/leaves) between networks whose connection does not support PIM along network boundaries. Let’s take the example shown below: The customer network connects to the sender network through the edge switch’s Ethernet 1 interface, which is configured as an IGMP host proxy. PIM is enabled within the publisher and customer networks but not on the connection between the networks.   When only “ip igmp host-proxy” is configured on the interface, IGMP reports will be sent for any (*,G) or (S,G) entry...
Continue reading →

Pim SSM IPV4 Non-DR OIF Installation for Fast Failover

Description In a Mlag setup with Pim SSM, one peer becomes the DR for a layer 3 interface and is responsible for routing multicast traffic on that interface. If this DR fails, the other peer, who was originally non-DR but becomes the new DR, may need to establish  SPT trees to get the multicast traffic or at the very least, add interfaces to OIF list of many multicast routes. This can be very disruptive to multicast traffic flow if there are thousands of routes.  This feature “Pim SSM Non-DR OIF Installation” helps to reduce convergence times and decrease traffic loss...
Continue reading →

Enable source specific multicast

We currently have a querier (v3) running on VLAN 400 and it perfectly works for multicast group joins within that VLAN. However when performing a source specific group join it seems to forward traffic from other sources as well. My transmitting part is sending on group 239.211.4.99 with source address 172.216.0.25 My receiving part is subscribed to group 239.211.4.99 with source address 172.216.0.11 There is not multicast traffic to group 239.211.4.99 from source 172.216.0.11; Expected result is that no multicast packets would be received, but it receives all traffic from 172.216.0.25. What configuration is required to enable source specific multicast...
Continue reading →

Multicast forwarding using BESS (MFA)

Description The PIM routing protocol builds multicast routing state based on control packets and multicast data events. In our current implementation, we rely on the Linux kernel to notify the PIM agents regarding the multicast data events. Also, the Linux kernel forwards a multicast data packet before hardware gets programmed to do so. As an alternative to the Linux kernel, Multicast Forwarding based on BESS ( Berkeley Extensible Soft Switch ), MFA, can be used to generate multicast data events and forward multicast data packets. As the first release of MFA, it is officially supported for IPv6 PIM SSM. Although...
Continue reading →

IPv6 support for PIM source specific multicast

Description This feature adds support for PIM-SSM ( Source Specific Multicast ) for IPv6 Multicast Routing on platforms listed below. The TOI for the support in earlier versions/platforms is available here. Reference TOI for support of IPv6 Multicast Routing support is available here. Basic configuration commands can be found in the aforementioned TOI for enabling Ipv6 multicast routing Platform compatibility The following platforms are supported from software version 4.22.0 DCS-7050QX, DCS-7050SX, DCS-7050TX DCS-7050QX2, DCS-7050SX2, DCS-7050TX2 DCS-7050CX3, DCS-7050SX3 DCS-7060CX, DCS-7060CX2, DCS-7060SX2 DCS-7260CX, DCS-7260CX3, DCS-7260QX DCS-7300X, DCS-7300X3 series Show Commands The below commands can be leveraged in order to view the multicast...
Continue reading →

Follow

Get every new post on this blog delivered to your Inbox.

Join other followers: