Design Reference
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in this release
- Chapter 3: Network design fundamentals
- Chapter 4: Hardware fundamentals and guidelines
- Chapter 5: Optical routing design
- Chapter 6: Platform redundancy
- Chapter 7: Link redundancy
- Chapter 8: Layer 2 loop prevention
- Chapter 9: Spanning tree
- Chapter 10: Layer 3 network design
- Chapter 11: SPBM design guidelines
- Chapter 12: IP multicast network design
- Multicast and VRF-Lite
- Multicast and MultiLink Trunking considerations
- Multicast scalability design rules
- IP multicast address range restrictions
- Multicast MAC address mapping considerations
- Dynamic multicast configuration changes
- IGMPv3 backward compatibility
- IGMP Layer 2 Querier
- TTL in IP multicast packets
- Multicast MAC filtering
- Guidelines for multicast access policies
- Multicast for multimedia
- Chapter 13: System and network stability and security
- Chapter 14: QoS design guidelines
- Chapter 15: Layer 1, 2, and 3 design examples
- Chapter 16: Software scaling capabilities
- Chapter 17: Supported standards, RFCs, and MIBs
- Glossary
Although you can configure addresses starting with 01.00.5E, which are reserved for IP multicast
address mapping, do not enable IP multicast with streams that match the configured addresses.
This configuration can result in incorrect IP multicast forwarding and incorrect multicast MAC
filtering.
Guidelines for multicast access policies
Use the following guidelines when you configure multicast access policies:
• Use masks to specify a range of hosts. For example, 10.177.10.8 with a mask of
255.255.255.248 matches hosts addresses 10.177.10.8 through 10.177.10.15. The host
subnet address and the host mask must be equal to the host subnet address. An easy way to
determine this is to ensure that the mask has an equal or fewer number of trailing zeros than
the host subnet address. For example, 3.3.0.0/255.255.0.0 and 3.3.0.0/255.255.255.0 are
valid. However, 3.3.0.0/255.0.0.0 is not.
• Apply receive-access policies to all eligible receivers on a segment. Otherwise, one host joining
a group makes that multicast stream available to all.
• Receive access policies are initiated after the switch receives reports with addresses that
match the filter criteria.
• Transmit access policies apply after the switch receives the first packet of a multicast stream.
Multicast access policies can apply to a routed PIM interface if Internet Group Management Protocol
(IGMP) reports the reception of multicast traffic.
The following rules and limitations apply to IGMP access policy parameters when you use them with
IGMP instead of PIM:
• The static member parameter applies to IGMP snooping and PIM on both interconnected links
and edge ports.
• The Static Not Allowed to Join parameter applies to IGMP snooping and PIM on both
interconnected links and edge ports.
• For multicast access control, the denyRx parameter applies to IGMP snooping and PIM. The
DenyTx and DenyBoth parameters apply only to IGMP snooping.
Multicast for multimedia
Avaya Virtual Services Platform 4000 Series provides a flexible and scalable multicast
implementation for multimedia applications. Several features are dedicated to multimedia
applications and in particular to television distribution.
Join and leave performance
For TV applications, you can attach several TVs directly, or through an IGMP-capable Ethernet
switch, to the VSP 4000. Base this implementation on IGMP; the set-top boxes use IGMP reports to
Guidelines for multicast access policies
January 2015 Network Design Reference for Avaya VSP 4000 Series 113
Comments? infodev@avaya.com










