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
Chapter 5: Network design fundamentals
To efficiently and cost-effectively use Avaya Virtual Services Platform 4000 Series, you must
properly design your network, which includes the following considerations:
• Reliability and availability
• Platform redundancy
• Desired level of redundancy
A robust network depends on the interaction between system hardware and software. System
software can be divided into different functions as shown in the following figure.
Figure 1: Hardware and software interaction
A driver is the lowest level of software that actually performs a function. Drivers reside on a single
module and do not interact with other modules or external devices. Drivers are very stable.
Statically configured MultiLink Trunking (MLT) is a prime example of local software because it
interacts with several modules within in the same device. No external interaction is needed, so you
can easily test the function.
Interacting software is the most complex level of software because it depends on interaction with
external devices. The Open Shortest Path First (OSPF) protocol is a good example of this software
level. Interaction can occur between devices of the same type or with devices of other vendors than
run a completely different implementation.
16 Network Design Reference for Avaya VSP 4000 Series December 2014
Comments? infodev@avaya.com










