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
Chapter 7: Link redundancy
You can build link redundancy into your network to:
• Help eliminate a single point of failure in your network (provide physical and link layer
redundancy)
• Prevent a service interruption caused by a faulty link (provide link layer redundancy)
This chapter explains the following design options that you can use to achieve link redundancy
(provide alternate data paths) :
• Physical layer redundancy
• MultiLink Trunking
• 802.1ad-based link aggregation
Physical layer redundancy
To ensure that a faulty link does not cause a service interruption, you can provide physical layer
redundancy in your network.
You can also configure the platform to detect link failures with, for example:
• Remote fault indication
• Virtual Link Aggregation Control Part (VLACP)
Gigabit Ethernet and remote fault indication
The 802.3z gigabit Ethernet standard defines remote fault indication (RFI) as part of the Auto-
Negotiation function.
Because RFI is part of the Auto-Negotiation function, if you disable Auto-Negotiation, you
automatically disable RFI.
The stations on both ends of a fiber pair use RFI to inform one another after a problem occurs on
one of the fibers.
Avaya recommends that you enable Auto-Negotiation on gigabit Ethernet links when the devices on
both ends of a fiber link support Auto-Negotiation because, without RFI support, if one of two
unidirectional fibers that form the connection between the two platforms fails, the transmitting side
cannot determine that the link is broken in one direction (see the following figure).
36 Network Design Reference for Avaya VSP 4000 Series June 2015
Comments on this document? infodev@avaya.com










