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
The following figure illustrates the actions performed on three different bridged traffic flows (that is
VoIP, video conference, and email) at access and core ports throughout the network.
Figure 60: Trusted bridged traffic
For bridged, untrusted traffic, if you configure the port to access, mark and prioritize traffic on the
access node using global filters. Reclassify the traffic to ensure it complies with the class of service
specified in the SLA.
For Resilient Packet Ring (RPR) interworking, you can assume that, for all incoming traffic, the QoS
configuration is properly marked by the access nodes. The core switch ports, configured as core or
trunk ports, perform the RPR interworking. These ports preserve the DSCP marking and re-mark the
802.1p bit to match the 802.1p bit of the RPR. The following figure shows the actions performed on
three different traffic flows (VoIP, video conference, and email) over an RPR core network.
QoS design guidelines
132 Network Design Reference for Avaya VSP 4000 Series December 2014
Comments? infodev@avaya.com










