View - ADTRAN Support Community
View - ADTRAN Support Community
View - ADTRAN Support Community
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Additional BGP Configuration<br />
Routes with lower administrative distances are favored.<br />
Distribute List<br />
Use the distribute-list command to add route filtering functionality by assigning inbound and outbound<br />
IPv4 access control lists (ACLs) to a BGP neighbor. Only one inbound/outbound pair of ACLs can be<br />
configured for a particular neighbor.<br />
(config-bgp-neighbor)#distribute-list [in | out]<br />
Specifies an IPv4 ACL name. This is a standard or extended IPv4 ACL against which the<br />
contents of the incoming/outgoing routing updates are matched.<br />
in Applies route filtering to inbound data.<br />
out Applies route filtering to outbound data.<br />
Refer to IP ACLs in AOS (<strong>ADTRAN</strong>’s Knowledge Base article 3087) for information on<br />
how to create a standard or extended IPv4 ACL.<br />
eBGP Multihop<br />
Use the ebgp-multihop command to configure the maximum hop count for BGP messages to a neighbor.<br />
(config-bgp-neighbor)#ebgp-multihop <br />
Specifies the maximum hop count of BGP messages to a neighbor. Range is 1 to 254 hops.<br />
This command allows an eBGP neighbor to be on a network that is not directly connected. The default<br />
time to live (TTL) for BGP messages is 1 since eBGP peers are normally directly connected. However, in<br />
certain applications, a non-BGP device, such as a firewall or router, might reside between eBGP peers. The<br />
ebgp multihop command is required in this case to allow updates to have a TTL greater than 1 and to<br />
allow received BGP updates to be added to the BGP table when the next-hop address is not directly<br />
connected.<br />
It is also good practice to create a static route to reach the eBGP neighbor when the neighbor is more than<br />
one hop away, as well as creating a backup route pointing to null 0 interface with a higher administrative<br />
distance. These routes prevent unnecessary BGP traffic from traversing the wrong connection and prevent<br />
the BGP neighbor relationship from incorrectly attempting to establish itself on that connection. It is also<br />
possible that sending invalid BGP traffic to some providers might result in the connection being<br />
automatically disabled by the provider as a security measure.<br />
Fast External Failover<br />
Use the bgp fast-external-failover command to enable the fast external failover feature.<br />
(config-bgp)#bgp fast-external-failover<br />
When failover is enabled, if the link interface goes down between this router and a BGP neighbor, the BGP<br />
session with the neighbor is immediately cleared. When failover is disabled and the link goes down, the<br />
session is maintained until the BGP hold timer expires (refer to Hold Timer on page 18).<br />
61200860L1-29.4E Copyright © 2012 <strong>ADTRAN</strong>, Inc. 17