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
BGP and Internet peering
By using BGP, you can perform Internet peering directly between VSP 4000 and another edge
router. In such a scenario, you can use each VSP 4000 for aggregation and link it with a Layer 3
edge router, as shown in the following figure.
Figure 36: BGP and Internet peering
In cases where the Internet connection is single-homed, to reduce the size of the routing table,
Avaya recommends that you advertise Internet routes as the default route to the IGP. The VSP
4000 supports a total of 16,000 eBGP routes. The maximum FIB size for IPv4 routes is also 16,000.
Routing domain interconnection with BGP
You can implement BGP so that autonomous routing domains, such as OSPF routing domains,
connect. This connection allows the two different networks to begin communicating quickly over a
common infrastructure, thus providing additional time to plan the IGP merger. Such a scenario is
particularly effective when you need to merge two OSPF area 0.0.0.0s (see the following figure).
Figure 37: Routing domain interconnection with BGP
BGP and edge aggregation
You can perform edge aggregation with multiple point of presence or edge concentrations. VSP
4000 supports 12 pairs (peering services). You can use BGP to inject dynamic routes rather than
using static routes or RIP (see the following figure).
Border Gateway Protocol
June 2015 Network Design Reference for Avaya VSP 4000 Series 87
Comments on this document? infodev@avaya.com










