Design Reference

ManualsBrandsExtreme Networks ManualsComputers & AccessoriesFabric-enabled multi-service edge switches

121

122

123

124

125

126

127

128

129

130

Table Of Contents

Contents
Chapter 1: Introduction
- Purpose
- Related resources
- Support
Chapter 2: New in Release 4.0.50
- Features
- Other changes
Chapter 3: New in Release 4.0.40
- Features
- Other changes
Chapter 4: New in Release 4.0
- Features
- Other changes
Chapter 5: Network design fundamentals
Chapter 6: Hardware fundamentals and guidelines
- Supported hardware
- Platform considerations
- Hardware compatibility
- Supported optical devices
- Dispersion considerations for long reach
- 10/100BASE-X and 1000BASE-TX reach
- 10/100/1000BASE-TX Auto-Negotiation recommendations
- Auto MDIX
- CANA
Chapter 7: Optical routing design
- Optical routing system components
Chapter 8: Platform redundancy
- Power redundancy
- Input/output port redundancy
- Configuration redundancy
- Link redundancy
Chapter 9: Link redundancy
- Physical layer redundancy
- MultiLink Trunking
- 802.3ad-based link aggregation
Chapter 10: Layer 2 loop prevention
- Loop prevention and detection
- SLPP example scenarios
Chapter 11: Spanning tree
- Spanning tree and protection against isolated VLANs
- MSTP and RSTP considerations
Chapter 12: Layer 3 network design
- VRF Lite
- Virtual Router Redundancy Protocol
- Open Shortest Path First
- Border Gateway Protocol
- IP routed interface scaling
Chapter 13: SPBM design guidelines
- 802.1aq standard
- VLANs without member ports
- Provisioning
- Implementation options
- Reference architectures
- Solution-specific reference architectures
- Best practices
- SPBM restrictions and limitations
- IP multicast over SPBM restrictions
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
- DoS protection mechanisms
- Damage prevention
- Data plane security
- Control plane security
- Additional information
Chapter 16: QoS design guidelines
- QoS mechanisms
- QoS interface considerations
- Network congestion and QoS design
- QoS examples and recommendations
Chapter 17: Layer 1, 2, and 3 design examples
- Layer 1 example
- Layer 2 example
- Layer 3 example
Chapter 18: Software scaling capabilities
Chapter 19: Supported standards, RFCs, and MIBs
- Supported IEEE standards
- Supported RFCs
- Quality of service
- Network management
- MIBs
- Standard MIBs
- Proprietary MIBs
Glossary

Traffic category Application example ASC

Routing table updates Network

Real-Time, Delay Intolerant IP telephony; interhuman

communication

Premium

Real-Time, Delay Tolerant Video conferencing; interhuman

communication.

Platinum

Audio and video on demand; human-

host communication

Gold

NonReal-Time

Mission Critical

Interactive eBusiness (B2B, B2C) transaction

processing

Silver

NonInteractive Email; store and forward Bronze

NonReal Time, NonMission Critical FTP; best effort Standard

PointCast; Background/standby Custom/ best effort

QoS and filters

Filters help you provide QoS by permitting or dropping traffic based on the parameters you

configure. You can use filters to mark packets for specific treatment.

Typically, filters act as firewalls or are used for Layer 3 redirection. In more advanced cases, traffic

filters can identify Layer 3 and Layer 4 traffic streams. The filters cause the streams to be re-marked

and classified to attain a specific QoS level at both Layer 2 (802.1p) and Layer 3 (DSCP).

Traffic filtering is a key QoS feature. VSP 4000, by default, determines incoming packet 802.1p or

DiffServ markings, and forwards traffic based on their assigned QoS levels. However, situations

exist where the markings are incorrect, or the originating user application does not have 802.1p or

DiffServ marking capabilities. Also, you can give a higher priority to select users (executive class). In

these situations, use filters to prioritize specific traffic streams.

You can use filters to assign QoS levels to devices and applications. To help you decide whether to

use a filter, key questions include:

1. Does the user or application have the ability to mark QoS information on data packets?

2. Is the traffic source trusted? Are the QoS levels configured appropriately for each data

source?

Users can maliciously configure QoS levels on their devices to take advantage of higher

priority levels.

3. Do you want to prioritize traffic streams?

This decision-making process is outlined in the following figure.

QoS mechanisms

December 2014 Network Design Reference for Avaya VSP 4000 Series 127

Comments? infodev@avaya.com