• Tag : PIM

 
 

High CPU on FHR or RP due to PIM

Introduction High CPU due to PIM processes is not always a bug and may be caused by either a misconfiguration or a routing issue.  For the purposes of this document we will focus primarily on network misconfiguration. Overview Network wide choppy video, music on hold streams or loud speaker issues are commonly caused by multicast problems in the network.  Should the issue be network wide and not isolated to one area of the network, the next place to start looking is high CPU on the First Hop Routers (FHR) and/or the Rendezvous Point (RP).  When the CPU process is high...
Continue reading →

Multicast subscription from unknown networks

Hi all! I need some help with multicast on EOS. I have an Arista DCS-7050S-64-F with EOS version 4.18.11M The Arista is connected to the Juniper QFX via PIM and OSPF (vlan 3025). Vlan 7 is multicast vlan for our multicast receivers from L2 domain. I receive all RPs from PIM neighborhood. But I can’t see multicast if subscribe to multicast group from undirected network (any network which unknown for the Arista). And PIM-Join is not send  from the Arista to the Juniper. If I subscribe from directly connected network (vlan7) I see multicast TV. What should I do in...
Continue reading →

“ip address virtual” support for PIM and IGMP

Description 4.22.1F introduces support for ip address virtual for PIM and IGMP in MLAG and Vxlan. On a VLAN, the same IP address can be configured using ip address virtual on both mlag devices as well as on different VTEPs. Control packets are source NATed by the kernel to a chosen IP address. The source NATing fails for PIM and IGMP. To overcome this, users can configure pim ipv4 local-interface and borrow the IP address to be used on the VLAN.  PIM and IGMP bypass the source NATing in the kernel. The interface configuration pim ipv4 local-interface allows PIM and...
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 →

MBR (Multicast Border Router)

Intro Enabling PIM MBR on an interface (where we don’t have an upstream PIM neighbor) will allow multicast traffic from remote sources that are outside of our PIM domain to be treated as locally connected sources. We typically see this scenario when we are receiving multicast feeds from a remote Exchange and a PIM neighbourship is not established on our upstream links. In the current PIM implementation (EOS 4.14.0F and later) EOS will drop multicast traffic that is not considered to be locally connected by default and we need to configure MBR to allow this multicast data. In the interfaces...
Continue reading →

Layer 3 Leaf-Spine – Rendezvous Point Placement?

Hello everybody, I have configured a leaf-spine architecture (4 leafs, 2 spines), see attached image. L3 routing is enabled on leafs and spines and eBGP is used between them. To enable VXLAN (from VMware Hosts), multicast needs to be configured. So far, ip multicast-routing and ip pim sparse-mode is set. Where do I configure the rendezvous point (RP) and which method would I use? I would prefer to place it on the spine switches using anycast-rp, but one spine switches does not reach the other spine switch (as the route to spine1 is not announced to spine2 by the leafs...
Continue reading →

Follow

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

Join other followers: