Multicast For Multimedia; Static Routes; Join And Leave Performance - Avaya 8800 Planning And Engineering, Network Design

Multicast network design

Multicast for multimedia

The Avaya Ethernet Routing Switch 8800/8600 provides a flexible and scalable multicast
implementation for multimedia applications. Several features are dedicated to multimedia
applications and in particular, to television distribution.
Multicast for multimedia navigation
•

Static routes

on page 232
•

Join and leave performance

• Fast Leave on page 233
• Last Member Query Interval tuning
Static routes
You can configure DVMRP static mroutes. This feature is useful in cases where streams must flow
continuously and not become aged. Be careful in using this feature—ensure that the programmed
entries do not remain on a switch when they are no longer necessary.
You can also use IGMP static receivers for PIM static (S,G)s. The main difference between static
mroutes and static (S,G) pairs is that static mroute entries only require the group address. You can
use static receivers in edge configurations or on interconnected links between switches.
Join and leave performance
For TV applications, you can attach several TV sets directly to the Avaya Ethernet Routing Switch
8800/8600. Base this implementation on IGMP; the set-top boxes use IGMP reports to join a TV
channel and IGMP Leaves to exit the channel. When a viewer changes channels, an IGMPv2 Leave
for the old channel (multicast group) is issued, and a membership report for the new channel is sent.
If viewers change channels continuously, the number of joins and leaves can become large,
particularly when many viewers are attached to the switch.
The Avaya Ethernet Routing Switch 8800/8600 supports more than a thousand Joins/Leaves per
second, which is well adapted to TV applications.
Important:
For IGMPv3, Avaya recommends that you ensure a Join rate of 250 per second or less. If the
Avaya Ethernet Routing Switch 8800/8600 must process more than 250 Joins per second,
users may have to resend Joins.
June 2016
on page 232
on page 233
Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
232