Open Shortest Path First - Avaya 8800 Planning And Engineering

Layer 3 network design
BGPv6 peering, route exchanges, and data traffic. Native BGPv6 peering is not supported in
Release 7.0.
Ethernet Routing Switch 8800/8600 supports the exchange of BGP+ reachability information
over IPv4 transport. To support BGP+, the Ethernet Routing Switch supports two BGP protocol
extensions, standards RFC 4760 (multi-protocol extensions to BGP) and RFC 2545 (MP-
BGP for IPv6). These extensions allow BGPv4 peering to be enabled with IPv6 address family
capabilities.
The Ethernet Routing Switch 8800/8600 implementation of BGP+ uses an existing TCPv4
stack to establish a BGPv4 connection. Optional, nontransitive BGP properties are used to
transfer IPv6 routes over the BGPv4 connection. Any BGP+ speaker has to maintain at least
one IPv4 address to establish a BGPv4 connection.
Different from IPv4, IPv6 introduces scoped unicast addresses, identifying whether the address
is global or link-local. When BGP+ is used to convey IPv6 reachability information for inter-
domain routing, it is sometimes necessary to announce a next hop attribute that consists of a
global address and a link-local address. For BGP+, no distinction is made between global and
site-local addresses.
The BGP+ implementation includes support for BGPv6 policies, including redistributing BGPv6
into OSPFv3, and advertising OSPFv3, static, and local routes into BGPv6 (through BGP+). It
also supports the aggregation of global unicast IPv6 addresses and partial HA.
BGP+ does not support confederations. In this release, you can configure confederations for
IPv4 routes only.
The basic configuration of BGP+ is the same as BGPv4 with one additional parameter added
and some existing commands altered to support IPv6 capabilities. You can enable and disable
IPv6 route exchange by specifying the address family attribute as IPv6. Note that an IPv6
tunnel is required for the flow of IPv6 data traffic.
BGP+ is only supported on the global VRF instance.
Limitations
IPv6 BGP convergence in case of SMLT scenarios cannot be guaranteed. Avaya does not
recommend to configure BGP peers between SMLT core routers or in between the core router
and any switch connecting through SMLT links for the failover scenarios.

Open Shortest Path First

Use Open Shortest Path First to ensure that the switch can communicate with other OSPF-
speaking routers. This section describes some general design considerations and presents a
number of design scenarios for OSPF.
For more information about OSPF and a list of OSPF commands see Avaya Ethernet Routing
Switch 8800/8600 Configuration — OSPF and RIP, NN46205-522.
138 Planning and Engineering — Network Design November 2010