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
Figure 41: IP multicast over SPBM streams
The following list describes how multicast senders and receivers connect to the SPBM cloud
using BEBs in the preceding diagram:
1. The sender sends multicast traffic with group IP address 233.252.0.1.
2. After the BEB receives the IP multicast stream from the sender, the BEB allocates
data I-SID 16000001 for the S,G multicast stream. The BEB sends an LSP with the
IPMC TLV (for Layer 2 VSN and Layer 3 VSN) or IPVPN TLV (for IP Shortcuts for
multicast) with the transmit bit set. The BEB also sends an IS-IS service identifier
and unicast address sub-TLV (where the unicast address has the multicast bit set
and the I-SID is the data I-SID).
3. The receiver sends a join request to group 233.252.0.1.
4. The BEB (acting as the IGMP querier) queries the IS-IS database to find all senders
for group 233.252.0.1. If the group exists, the BEB sends IS-IS service identifier and
unicast address sub-TLV (where the unicast address has the multicast bit set and
the nickname is the stream transmitter BEB and the I-SID is the data I-SID). If the
requested stream does not exist, the BEB keeps the IGMP information, but no
further action is taken.
5. IS-IS acts dynamically using the TLV information it receives from BEBs that connect
to the sender and receivers to create a multicast tree between them and the data
starts flowing from the sender.
For conceptual and configuration information on IP multicast over SPBM, see Configuring
Avaya VENA Fabric Connect on Avaya Virtual Services Platform 4000, NN46251–510.
Reference architectures
Network Design Reference for Avaya VSP 4000 February 2014 91