Scribd
Upload
100 views7 pages

Common Issues of BGP

Common issues with BGP include neighbor relationship problems, route advertisement issues, routes missing from routing tables, and address summarization problems. Neighbor relationships can fail to establish due to interface or layer 2 issues, incorrect BGP configuration, non-directly connected peers, or authentication mismatches. Route advertisements may not occur when routes do not exist in the routing table, route synchronization is enabled, or redistribution is improperly configured. Missing routes can result from default route misconfigurations, non-fully meshed iBGP neighbors, or unreachable iBGP next hops. Address summarization may fail if the aggregate range is not present in the routing table or if the aggregate statement is incorrectly configured.

Uploaded by

Pranav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
100 views7 pages

Common Issues of BGP

Common issues with BGP include neighbor relationship problems, route advertisement issues, routes missing from routing tables, and address summarization problems. Neighbor relationships can fail to establish due to interface or layer 2 issues, incorrect BGP configuration, non-directly connected peers, or authentication mismatches. Route advertisements may not occur when routes do not exist in the routing table, route synchronization is enabled, or redistribution is improperly configured. Missing routes can result from default route misconfigurations, non-fully meshed iBGP neighbors, or unreachable iBGP next hops. Address summarization may fail if the aggregate range is not present in the routing table or if the aggregate statement is incorrectly configured.

Uploaded by

Pranav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Common Issues of BGP

1. Neighbor relationship problems


2. Route advertisement issues
3. Routes missing from the table
4. Address summarization problems
Neighbor Relationship Problems

Possible Causes that may prevent neighbors from establishing a relationship. :


 

Cause 1: Layer 2 or Interface is down


Troubleshooting: If the Layer 2 process or Interface is down, it may prevent a neighbor relationship from
forming. The easiest way to determine that this is the problem when it’s stuck in the Active or Idle state is
by executing the show interface <slot/port>. For example, execute: show interfaces fastethernet 0/0
• If, the interface shows to be administratively down, then you can remedy that by simply issuing the no
shutdown command on the interface.
Cause 2: Incorrect IP address used in neighbor statement in BGP An incorrect IP address in the
neighbor statement in BGP may also cause neighbor relationship problems.
Troubleshooting : The easiest way to figure out if there’s a problem is to first execute the show ip bgp
summary command. It will show you the state of the neighbor relationship, how many prefixes if any are
being received, and whether the neighbor is stuck in Idle or Active state.
Cause 3: Configured eBGP peers are not directly connected Although eBGP peers that aren’t directly
connected can still have neighbor relationships, an additional command must be used and a special path
must be in place for the neighbor relationship to work.
Troubleshooting: You can determine whether the neighbor is more than one hop away by executing
the traceroute <peer ip> command. You’ll be able to tell very easily by the number of different sections
and hops shown in the output.
Cause 4: Misconfigured neighbor authentication Another cause that’s very common for neighbor
relationships not forming in BGP is the failure to configure the correct key in the password statement.
Troubleshooting : If you do a show ip bgp summary and you see that the neighbor relationships are
indeed stuck in Active or Idle, the easiest way to resolve this is to execute the show running
config command and then verify that the neighbor <peer ip> password <key> command is present on
both peers and that the configured keys match
Route Advertisement Issues

Cause 1: The advertisement does not match a route in the IP routing table If the particular route
being injected into BGP by the network statement is not matching a route in the IP routing table,
then you can encounter route advertisement problems
Troubleshooting: To remedy this, execute the show ip route command to discover whether the route
exists in the current routing table. If it is not there, troubleshoot the local router and the IGP to
determine the cause. See whether it was even configured in the router or check the IGP to see if
there is a particular issue that’s preventing the route from being installed in the routing table
Cause 2: Route synchronization is enabled By default, route synchronization is enabled in BGP.
Synchronization means that it has to exist in the IP routing table through an IGP, static routes, or
other means, or BGP will not advertise the route.
Troubleshooting: To solve this problem, first execute the show ip protocols command and check
whether the statement says IGP synchronization is enabled. If so, go back into the BGP
configuration and put in the no synchronization command in order for that behavior to be turned
off
 Cause 3: Route redistribution is not configured or is misconfigured  One more cause for a
problem with route advertisement issues may have to do with redistribution. Basically, if
redistribution has not been configured, BGP won’t pull those routes in. The table has to be
populated either through direct injection into BGP using the network statement or through
redistribution.
Troubleshooting: You may use the show ip protocols command and look to see if redistribution has
been configured. If it has, then investigate some more to see where the problem lies. It could be
that you may have put in an incorrect AS number or a process ID relating to OSPF.
Routes Missing from Table

Cause 1: Default route misconfigured If the default route is not showing up, then it’s probably
simply because it was not configured correctly.
Troubleshooting: To investigate, execute the show ip route and see whether there is a route to
0.0.0.0 network to begin with. If it’s missing from the table, it won’t be injected or advertised
from BGP.
Cause 2: iBGP neighbors not fully meshed You may have a problem with iBGP neighbors
because these neighbors are not full meshed
Troubleshooting: To verify that peerings are happening correctly, use the show ip bgp
neighbors command. You may also use the show running-config command and do a little bit
more investigative work in order to determine whether or not the neighbors are in fact fully
meshed.
Cause 3: iBGP next-hop is not reachable
Troubleshooting: One of the ways for you to check whether this is an issue is to do the show ip
route command and examine the IP routing table for the required static/IGP route. And this is
true with even eBGP. If the next-hop route is not reachable, it’s not going to be advertised.
• If a static route is required, configure it using the ip route <prefix> <mask> <next-
hop> command. Now, if for some reason, the IGP is failing to install the route leading to the
iBGP next-hop address, you may have a whole other set of issues just related to the IGP.
Address Summarization Problems

Cause 1: No subnets in the routing table in the range of the aggregate


address In terms of address summarization problems, one common cause
for an aggregate not being advertised is because there isn’t some part of the
IP address range within the aggregate that exists already in the routing
table
Troubleshooting: The easiest way to check that is to execute the show ip
route. See if any networks within that range currently exist. If you were
advertising an aggregate address 216.145.0.0 and the mask is
255.255.252.0 and there are no 216.145-any type addresses in terms of the
routing table, it’s not going to advertise the aggregate.
• Execute the show running-config to verify that the aggregate address
statement is correctly configured. If it is not, delete and recreate the
statement that need corrections.
Relevant Debug and Show Commands

• The troubleshooting process in BGP requires the use of several Show and a couple


of Debug commands
• BGP Show Commands Show ip protocols This will show the BGP status of your neighbor,
your Autonomous System Number (ASN), timer intervals, networks being advertised, and
neighbors/gateways. Consequently, it will be helpful in troubleshooting neighbor
relationships, missing routes, summarization issues, and filtering problems.
• Here’s a portion of an output resulting from a show ip protocols command:
• Show ip route bgp This will show BGP routes advertised by neighbors, the administrative
distance, MED value (if any), and the route source/interface. These information will be helpful
in troubleshooting missing routes, summarization issues, filtering problems, and general
troubleshooting tasks
• Show ip bgp summary This will show your configured peer IP addresses, your ASN, the
number of messages received and sent, how long the session has been up, the state (Active,
Idle, etc.), and prefixes received. This will be helpful in troubleshooting neighbor relationship
issues, local configuration issues, and routing problems.
• Show ip bgp neighbors There are two forms of this command. The first one is just show ip
bgp neighbors, which will show you the IP address of neighbors, router ID of neighbors, state
of a neighbor, peer-group (if configured), BGP messages/types received, and so forth.

You might also like