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: Spanning tree
- Chapter 10: Layer 3 network design
- Chapter 11: SPBM design guidelines
- Chapter 12: 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 13: System and network stability and security
- Chapter 14: QoS design guidelines
- Chapter 15: Layer 1, 2, and 3 design examples
- Chapter 16: Software scaling capabilities
- Chapter 17: Supported standards, RFCs, and MIBs
- Glossary
Chapter 3: Network design fundamentals
To efficiently and cost-effectively use Avaya Virtual Services Platform 4000, you must properly design
your network. Use the information in this section to help you properly design the network. To design
networks, you must consider
• 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
These levels are based on the software function. 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.
Network Design Reference for Avaya VSP 4000 February 2014 17