Avaya 8600 Technical Configuration Manual page 50

Site1:5# config ip bgp route-refresh enable
Site1:5# config ip bgp enable
Site1:5# config ip bgp quick-start enable
ACLI
Site1:5(config)# router bgp
Site1:5(config-bgp)# no auto-summary
Site1:5(config-bgp)# no synchronization
Site1:5(config-bgp)# no bgp aggregation
Site1:5(config-bgp)# quick-start enable
Site1:5(config-bgp)# traps enable
Site1:5(config-bgp)# route-refresh
Site1:5(config-bgp)# exit
Site1:5(config)# router bgp 65000 enable

Disable Auto-Summary if the IP networks advertised within the IP VPNs are not Class full
networks.

Always disable Synchronization since the IPVPN IP networks (VPNv4 routes) will never be
injected into the underlying IGP (OSPF). BGP Synchronization is only required in Transit AS
systems where EBGP learnt IP routes are injected into the AS's IGP and required by the interior
routers which are not running IBGP but have to forward traffic for those routes between the AS
BGP border routers. This never applies for IPVPN VPNv4 routes.

Enable Quick-Start for faster recovery. This allows the BGP speaker to begin establishing
peers immediately, instead of waiting for the peer's auto-restart timer to expire.

Always enable BGP Traps so that any BGP event will generate a message in the log file as well
as an SNMP Trap (if Trap receivers are configured).

Always enable BGP route-refresh capability when using BGP to advertise VPNv4 routes. A
BGP speaker only needs to keep VPNv4 routes, it received from a route-refresh capable peer,
for which it has matching import RTs on local VRFs while those that do not have a matching
import RT can be discarded without wasting resources. If a new VPN is created (hence a new
import RT) the BGP speaker is then able to request to his route-refresh capable peers that all
routes be refreshed.
Network Design Implementation to Provide L2 & L3 VPN Connectivity
November 2010
between Sites using SMLT and IPVPN-Lite for ERS 8600
Technical Configuration Guide
avaya.com
50