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
BackupMaster routes all traffic received on the BackupMaster IP interface according to the switch
routing table.
Figure 28: VRRP with BackupMaster
Avaya recommends that you stagger VRRP instances on a network or subnet basis. The following
figure shows the VRRP Masters and BackupMasters for two subnets. For more information about
how to configure VRRP using the Avaya Command Line Interface (ACLI) and Enterprise Device
Manager (EDM), see Configuration - IP Routing for Avaya Virtual Services Platform 4000 Series,
NN46251-505.
Figure 29: VRRP network configuration
The VRRP BackupMaster uses the VRRP standardized backup switch state machine. Thus, VRRP
BackupMaster is compatible with standard VRRP.
Avaya recommends that you use the following best practices to implement VRRP:
• Do not configure the virtual address as a physical interface that is used on the routing switches.
Instead, use a third address, for example:
- Interface IP address of VLAN A on Switch 1 = x.x.x.2
- Interface IP address of VLAN A on Switch 2 = x.x.x.3
- Virtual IP address of VLAN A = x.x.x.1
Note:
Avaya does not support a VRRP virtual IP address that is the same as the local physical
address of the device.
• Configure the VRRP holddown timer with enough time that the Interior Gateway Protocol (IGP)
routing protocol has time to update the routing table. In some cases, configuring the VRRP
Layer 3 network design
78 Network Design Reference for Avaya VSP 4000 Series June 2015
Comments on this document? infodev@avaya.com










