Design Reference
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in Release 4.0.50
- Chapter 3: New in Release 4.0.40
- Chapter 4: New in Release 4.0
- Chapter 5: Network design fundamentals
- Chapter 6: Hardware fundamentals and guidelines
- Chapter 7: Optical routing design
- Chapter 8: Platform redundancy
- Chapter 9: Link redundancy
- Chapter 10: Layer 2 loop prevention
- Chapter 11: Spanning tree
- Chapter 12: Layer 3 network design
- Chapter 13: SPBM design guidelines
- Chapter 14: 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 15: System and network stability and security
- Chapter 16: QoS design guidelines
- Chapter 17: Layer 1, 2, and 3 design examples
- Chapter 18: Software scaling capabilities
- Chapter 19: Supported standards, RFCs, and MIBs
- Glossary
• For a Layer 3 VSN, the I-SID is associated with a customer VRF, which is also virtualized
across the backbone. Layer 3 VSNs are always full-mesh topologies. Layer 3 VSNs associate
one VRF per I-SID.
• For a Layer 3 VSN with multicast, the BEB associates a data I-SID with the multicast stream
and a scope I-SID that defines the scope as a Layer 3 VSN. A multicast stream with a Layer 3
VSN scope can only transmit a multicast stream for the same Layer 3 VSN.
• For IP shortcuts with multicast, the BEB associates a data I-SID with the multicast stream and
defines the scope as Layer 3 Global Routing Table (GRT). A multicast stream with a scope of
Layer 3 GRT can only transmit a multicast stream for the Layer 3 GRT.
Encapsulating customer MAC addresses in backbone MAC addresses greatly improves network
scalability (no end-user C-MAC learning is required in the core) and also significantly improves
network robustness (loops have no effect on the backbone infrastructure).
The following figure shows the components of a basic SPBM architecture.
Figure 31: SPBM basic architecture
Related Links
SPBM design guidelines on page 71
VLANs without member ports
The Avaya Ethernet Routing Switch 8800 manages VLANs without member ports differently than
the VSP 9000 and VSP 4000.
• The ERS 8800 always designates the VLAN as operationally up if there is an attached I-SID.
• The VSP 9000 and VSP 4000 designate the VLAN as operationally up only if there is a
matching I-SID in the SPBM network. For more information, see the following sections.
VLANs without member ports
December 2014 Network Design Reference for Avaya VSP 4000 Series 73
Comments? infodev@avaya.com










