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 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
• VLACP
Gigabit Ethernet and remote fault indication
The 802.3z Gigabit Ethernet (GbE) 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 GbE 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).
Network Design Reference for Avaya VSP 4000 February 2014 35