Pim-Ssm Over Smlt/Rsmlt - Avaya 8800 Planning And Engineering, Network Design

In this configuration, both A and B forward traffic to the IGMP SNOOP switch, and the receiver
receives duplicate traffic.
The solution to this issue is to configure the metrics on the DVMRP interfaces so that either A or B
learns the source network route through the IST. In this way, the router that receives traffic from the
IST blocks traffic from the SMLT (receiver) port so that the IGMP switch receives traffic from only
one router.
Configure the metric of the DVMRP interface towards NETWORK on either A or B. For example,
configure Switch B so that the route metric through the DVMRP interface is greater than the metric
through the IST interface. Therefore, the NETWORK interface metric on B should be greater than 2.
If the metric of the NETWORK interface on B is configured to 3, B can learn route 10.10.10.0
through the NETWORK interface with a metric of 12 (because the metric is incremented by 2), and
through the IST interface with a metric of 11. So B learns route 10.10.10.0 with a cost of 11 to the
upstream neighbor through the IST link.
With these metrics, traffic from S goes from A to B only on the IST link. Because traffic received on
the IST cannot go to the SMLT link, the IGMP switch does not receive traffic from B. Therefore, R no
longer receives duplicate traffic; it receives traffic from switch A only.

PIM-SSM over SMLT/RSMLT

Fast failover for multicast traffic in a PIM-SSM network can be achieved using SMLT/RSMLT. PIM-
SSM is supported in triangle, square, and full mesh SMLT/RSMLT topologies.
The following figures show some examples of the supported topologies of PIM-SSM over SMLT.
The following figure shows a triangle topology in which all the Ethernet Routing Switch 8800/8600s
are running PIM-SSM at the core, and the Ethernet Routing Switch 8300 and the stackable Ethernet
Routing Switches (5xxx/4500/2500) are also running PIM-SSM at the edge.
June 2016 Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
Multicast and SMLT guidelines
225