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
• For routers that support both BGP and OSPF, you must configure the OSPF router ID
and the BGP identifier to the same IP address. The BGP router ID automatically uses the
OSPF router ID.
• In configurations where BGP speakers reside on routers that have multiple network
connections over multiple IP interfaces (the typical case for IBGP speakers), consider
using the address of the circuitless (virtual) IP interface as the local peer address. In this
configuration, you ensure that BGP is reachable as long as an active circuit exists on the
router.
• By default, BGP speakers do not advertise or inject routes into their IGP. You must
configure route policies to enable route advertisement.
• Coordinate routing policies among all BGP speakers within an AS so that every BGP
border router within an AS constructs the same path attributes for an external path.
• Configure accept and announce policies on all IBGP connections to accept and propagate
all routes. Make consistent routing policy decisions on external BGP connections.
• Use the max-prefix parameter to limit the number of routes BGP imports from a peer. Use
a configuration of 0 to accept an unlimited number of prefixes.
• You cannot enable or disable the MED selection process. BGP aggregation does not
occur when routes have different MEDs or next-hops.
BGP and OSPF interaction
RFC1745 defines the interaction between BGP and OSPF when OSPF is the IGP within an
autonomous system. For routers that run both protocols, the OSPF router ID and the BGP ID
must be the same IP address. You must configure a BGP route policy to allow BGP
advertisement of OSPF routes.
Interaction between BGPv4 and OSPF includes the ability to advertise supernets to support
CIDR. BGPv4 supports interdomain supernet advertisements; OSPF can carry supernet
advertisements within a routing domain.
BGP and other vendor interoperability
BGP interoperability is compatible between Virtual Services Platform 4000, Cisco 6500
Software Release IOS 11.3, and Juniper M20 Software Release 5.3R2.4.
For more information about BGP, see Avaya Virtual Services Platform 4000 Configuration —
BGP Services, NN46251-507.
BGP and Internet peering
By using BGP, you can perform Internet peering directly between Virtual Services Platform
4000 and another edge router. In such a scenario, you can use each Virtual Services Platform
4000 for aggregation and peer it with a Layer 3 edge router, as shown in the following figure.
Border Gateway Protocol
Network Design Reference for Avaya VSP 4000 February 2014 67