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
Figure 69: RP failover with default unicast routes
Because failover is determined by unicast routing behavior, carefully consider the unicast routing
design, as well as the IP address you select for the RP. Static RP failover performance depends on
the convergence time of the unicast routing protocol. For quick convergence, Avaya recommends
that you use a link state protocol, such as OSPF. For example, if you use RIP as the routing
protocol, an RP failure can take minutes to detect. Depending on the application, this situation can
be unacceptable.
Static RP failover time does not affect routers that have already switched over to the SPT; failover
time only affects newly-joining routers.
Unsupported static RP configurations
If you use static RP, you disable dynamic RP learning. The following figure shows an unsupported
configuration for static RP. In this example because of inter-operation between static RP and
dynamic RP, no RP exists at switch 2. However, (S,G) creation and deletion occurs every 210
seconds at switch 16.
Protocol Independent Multicast-Sparse Mode guidelines
June 2015 Network Design Reference for Avaya VSP 4000 Series 139
Comments on this document? infodev@avaya.com










