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 10: Layer 3 switch clustering and
RSMLT
This section describes designs for achieving network redundancy. Network redundancy minimizes
failure and ensures a faulty switch does not interrupt service.
Related Links
Routed SMLT on page 54
Switch clustering topologies and interoperability with other products on page 61
Routed SMLT
Core network convergence time usually depends on the length of time a routing protocol requires to
successfully converge. This convergence time can cause network interruptions that range from
seconds to minutes depending on the specific routing protocol. Routed Split Multilink Trunking
(RSMLT) allows rapid failover for core topologies by providing an active-active router concept to
core SMLT networks. Virtual Services Platform 4000 supports RSMLT on SMLT triangles, squares,
and SMLT full-mesh topologies that have routing enabled on the core VLANs. RSMLT provides
redundancy as well. If a core router fails, RSMLT provides packet forwarding. This eliminates
dropped packets during convergence.
Virtual Services Platform 4000 can use one of the following routing protocols to provide
convergence:
• IP or IPv6 unicast static routes
• Routing Information Protocol version 1 (RIPv1) or version 2 (RIPv2) (IPv4)
• Open Shortest Path First (OSPF) and OSPFv3
• Border Gateway Protocol (BGP) (IPv4) and BGP+
SMLT and RSMLT operation
SMLT and RSMLT in Layer 2 and 3 environments on page 55 shows a typical redundant network
with user aggregation, core, and server access layers. To minimize the creation of many IP subnets,
one VLAN (VLAN 1, IP subnet A) spans all wiring closets. SMLT provides loop prevention and
enables all links to forward to VLAN 1, IP Subnet A. RSMLT runs on the core.
54 Network Design Reference for Avaya VSP 4000 Series June 2015
Comments on this document? infodev@avaya.com










