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: Layer 2 switch clustering and SMLT
- Chapter 10: Layer 3 switch clustering and RSMLT
- Chapter 11: Layer 3 switch clustering and multicast SMLT
- Chapter 12: Spanning tree
- Chapter 13: Layer 3 network design
- Chapter 14: SPBM design guidelines
- Chapter 15: 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
- Split-subnet and multicast
- Protocol Independent Multicast-Sparse Mode guidelines
- Protocol Independent Multicast-Source Specific Multicast guidelines
- Multicast for multimedia
- Chapter 16: System and network stability and security
- Chapter 17: QoS design guidelines
- Chapter 18: Layer 1, 2, and 3 design examples
- Glossary
Prioritization of control traffic
VSP 4000 uses a sophisticated prioritization scheme to schedule control packets on physical ports.
This scheme involves two levels with both hardware and software queues to guarantee proper
handling of control packets regardless of the switch load. In turn, this scheme guarantees the
stability of the network. Prioritization also guarantees that applications that use many broadcasts are
handled with lower priority.
You cannot view, configure, or modify control-traffic queues.
ARP request threshold recommendations
The Address Resolution Protocol (ARP) request threshold defines the maximum number of
outstanding unresolved ARP requests. The default value for this function is 500 ARP requests. To
avoid excessive amounts of subnet scanning that a virus can cause, Avaya recommends that you
change the ARP request threshold to a value between 100 and 50. This configuration protects the
CPU from causing excessive ARP requests, protects the network, and lessens the spread of the
virus to other PCs. The following list provides further recommended ARP threshold values:
• Default: 500
• Severe conditions: 50
• Continuous scanning conditions: 100
• Moderate: 200
• Relaxed: 500
For more information about how to configure the ARP threshold, see Configuration - IP Routing for
Avaya Virtual Services Platform 4000 Series, NN46251-505.
Multicast Learning Limitation
The Multicast Learning Limitation feature protects the CPU from multicast data packet bursts
generated by malicious applications. If more than a certain number of multicast streams enter the
CPU through a port during a sampling interval, the port is shut down until the user or administrator
takes the appropriate action.
For more information, see Configuring IP Multicast Routing Protocols on Avaya Virtual Services
Platform 4000 Series , NN46251-504.
Damage prevention
To further reduce the chance that unauthorized users can use your network to damage other
existing networks, take the following actions:
1. Prevent IP spoofing.
You can use the spoof-detect feature.
2. Prevent the use of the network as a broadcast amplification site.
3. To block illegal IP addresses, enable the hsecure flag (High Secure mode).
For more information, see Security for Avaya Virtual Services Platform 4000 Series,
NN46251-601.
Damage prevention
June 2015 Network Design Reference for Avaya VSP 4000 Series 149
Comments on this document? infodev@avaya.com










