BGP Failover Troubleshooting Manual

Border Gateway Protocol

Border Gateway Protocol (BGP) is the protocol which is used to make core routing decisions on
the Internet; it involves a table of IP networks or "prefixes" which designate network reachability among
autonomous systems (AS). BGP is a path vector protocol or a variant of a Distance-vector routing
protocol. BGP does not involve traditional Interior Gateway Protocol (IGP) metrics, but routing decisions
are made based on path, network policies and/or rule-sets. For this reason, it is more appropriately
termed a reachability protocol rather than routing protocol.
BGP performs interdomain routing in Transmission-Control Protocol/Internet Protocol (TCP/IP)
networks. BGP is an exterior gateway protocol (EGP), which means that it performs routing between
multiple autonomous systems or domains and exchanges routing and reachability information with
other BGP systems.

BGP Adjacency States

Idle is the initial state of a BGP connection. The BGP speaker is waiting for a start event, generally either
the establishment of a TCP connection or the re-establishment of a previous connection. Once the
connection is established, BGP moves to the next state.

Idle State:

Refuse all incoming BGP connections

Start the initialization of event triggers.

Initiates a TCP connection with its configured BGP peer.

Listens for a TCP connection from its peer.

Changes its state to Connect.

If an error occurs at any state of the FSM process, the BGP session is terminated
immediately and returned to the Idle state. Some of the reasons why a router does not
progress from the Idle state are:

TCP port 179 is not open.

A random TCP port over 1023 is not open.

Peer address configured incorrectly on either router.

AS number configured incorrectly on either router.

Connect is the next state. If the TCP connection completes, BGP will move to the OpenSent stage if the
connection does not complete, BGP goes to Active.

Connect State:

Waits for successful TCP negotiation with peer.

BGP does not spend much time in this state if the TCP session has been successfully
established.

Sends Open message to peer and changes state to OpenSent.

If an error occurs, BGP moves to the Active state. Some reasons for the error are:

TCP port 179 is not open.

A random TCP port over 1023 is not open.

Peer address configured incorrectly on either router.

AS number configured incorrectly on either router.

Active indicates that the BGP speaker is continuing to create a peer relationship with the remote router.
If this is successful, the BGP state goes to OpenSent. You'll occasionally see a BGP connection flap
between Active and Connect. This indicates an issue with the physical cable itself, or with the
configuration.

Active State:

If the router was unable to establish a successful TCP session, then it ends up in the Active
state.

BGP FSM tries to restart another TCP session with the peer and, if successful, then it sends
an Open message to the peer.

If it is unsuccessful again, the FSM is reset to the Idle state.

Repeated failures may result in a router cycling between the Idle and Active states. Some of
the reasons for this include:

TCP port 179 is not open.

A random TCP port over 1023 is not open.

BGP configuration error.

Network congestion.

Flapping network interface.

OpenSent indicates that the BGP speaker has received an Open message from the peer. BGP will
determine whether the peer is in the same AS (iBGP) or a different AS (eBGP) in this state.

OpenSent State:

BGP FSM listens for an Open message from its peer.

Once the message has been received, the router checks the validity of the Open message.

If there is an error it is because one of the fields in the Open message doesnt match
between the peers, e.g., BGP version mismatch, MD5 password mismatch, the peering
router expects a different My AS, etc. The router then sends a Notification message to the
peer indicating why the error occurred.

If there is no error, a Keepalive message is sent, various timers are set and the state is
changed to OpenConfirm.

In OpenConfirm state, the BGP speaker is waiting for a keepalive message. If one is received, the state
moves to Established, and the neighbor relationship is complete. It is in the Established state that
update packets are actually exchanged.

OpenConfirm State:

The peer is listening for a Keepalive message from its peer.

If a Keepalive message is received and no timer has expired before reception of the
Keepalive, BGP transitions to the Established state.

If a timer expires before a Keepalive message is received, or if an error condition occurs, the
router transitions back to the Idle state.

In Established state, if one of keepalive message is received, the state moves to Established, and the
neighbor relationship is complete. It is in the Established state that update packets are actually
exchanged.

Established State:

In this state, the peers send Update messages to exchange information about each route
being advertised to the BGP peer.

If there is any error in the Update message then a Notification message is sent to the peer,
and BGP transitions back to the idle state.

If a timer expires before a Keepalive message is received, or if an error condition occurs, the
router transitions back to the Idle state.

BGP path Selection

According to BGP best path Selection process, here is the order of BGP preference:
1.
2.
3.
4.
5.
6.
7.
8.

Prefers the highest weight.

Prefer the Highest local preference.
Prefer Locally Originated routes.
Prefer the shortest AS path.
Prefer the lowest Origin Code.
Prefer the Lowest MED value.
Prefer the routes learned by EBGP over the routes learned by IBGP.
Prefer the routes learned with the lowest router ID.

Keep in Mind the "Weight" attributes is locally significant and is Cisco proprietary, the default value for
locally originated routes are 32678.
The default Local preference attribute value for all learned routes is 100 "IF is not modified"
The default Origin Code is "IGP" if learned and advertised by Network Statement, while "Incomplete" If
the route is redistributed into BGP.
The default MED value for all learned route is 0 "Unless modified", bear in mind MED is compared by
default from routed learned from the Same AS number.
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094431.shtml

BGP Attributes
Attribute

Meaning

AS path

An ordered list of all the autonomous systems through which this update has
passed. Well-known, mandatory.

Origin

How BGP learned of this network. i = by network command, e = from EGP, ? =

redistributed from other source. Well-known, mandatory.

Local Preference

A value telling IBGP peers which path to select for traffic leaving the AS. Default
value is 100. Well-known, discretionary.

Multi-Exit
Discriminator (MED)

Suggests to a neighboring autonomous system which of multiple paths to select

for traffic bound into your autonomous system. Lowest MED is preferred.
Optional, non-transitive.

Weight

Cisco proprietary, to tell a router which of multiple local paths to select for traffic
leaving the AS. Highest weight is preferred. Only has local significance.

http://www.ciscopress.com/articles/article.asp?p=1565538&seqNum=4
IGPs, such as EIGRP or OSPF, choose routes based on lowest metric. They attempt to find the shortest,
fastest way to get traffic to its destination. BGP, however, has a different way of route selection. It
assigns various attributes to each path; these attributes can be administratively manipulated to control
the path that is selected. It then examines the value of these attributes in an ordered fashion until it can
narrow all the possible routes down to one path.
BGP chooses a route to a network based on the attributes of its path. Four categories of attributes exist
as follows:
Well-known mandatory: Must be recognized by all BGP routers, present in all BGP updates, and passed
on to other BGP routers. For example, AS path, origin, and next hop
Well-known discretionary: Must be recognized by all BGP routers and passed on to other BGP routers
but need not be present in an update, for example, local preference.
Optional transitive: Might or might not be recognized by a BGP router but is passed on to other BGP
routers. If not recognized, it is marked as partial, for example, aggregator, community.
Optional non-transitive: Might or might not be recognized by a BGP router and is not passed on to
other routers, for example, Multi-Exit Discriminator (MED), originator ID.

AS Override
The AS override feature allows a provider edge (PE) router to change the private autonomous
system (AS) number used by a customer edge (CE) device on an external BGP (EBGP) session running on
a VPN routing and forwarding (VRF) access link. The private AS number is changed to the PE AS number.
Another CE device connected to another PE device sees the EBGP route coming from the first site with
an AS path of provider-ASN provider-ASN, instead of provider-ASN site1-ASN. This allows enterprise
networks to use the same private ASN on all sites.
The AS override feature offers a clear management advantage to the service provider because
BGP by default does not accept BGP routes with an AS path attribute that contains the local AS number.
In an enterprise network with multiple sites, you might wish to use a single AS number across sites.
Suppose, for example that two CE devices are in AS 64512 and that the provider network is in AS 65534.
When the service provider configures a Layer 3 VPN with this setup, even if the MPLS network
has routes towards Device CE1 and Device CE2, Device CE1 and Device CE2 do not have routes to each
other because the AS path attribute would appear as 64512 65534 64512. BGP uses the AS path
attribute as its loop avoidance mechanism. If a site sees its own AS number more than once in the AS
path, the route is considered invalid.
One way to overcome this difficulty is with the as-override statement, which is applied to the PE
devices. The as-override statement replaces the CE device's AS number with that of the PE device, thus
preventing the customer AS number from appearing more than once in the AS path attribute.
If a customer uses AS path prepending to make certain paths less desirable and the service
provider uses AS override, each CE AS number occurrence in the AS-path is changed to the service
provider AS number. For example, suppose that all customer sites use the same AS number, say 64512.
If the ISP uses AS number 65534, one customer site sees the path to another site as 65534 65534. If the
customer prepends 64512 on a particular path to make it less desirable, another customer site sees that
path as 65534 65534 65534.

PE End Cisco Routers Troubleshooting Commands

Provider Edge end BGP show Commands output for IPv4 unicast Neighborship
To Checked the bgp ipv4 neighbor status on cisco router below is the command. It shows the local
Router ID and AS number, Neighbor IP, Neighbor AS, Neighbor state and receive prefix numbers.
LDN-KHISTT-C3845>sh ip bgp summary
BGP router identifier 210.2.130.207, local AS number 23966
Neighbor
V AS
MsgRcvd
MsgSent TblVer InQ OutQ Up/Down
10.0.7.86
4 64616
0
0
0 0 0
never
10.0.8.46
4 64608 313625 313899 4117016 0 0
2d17h
10.5.23.194 4 64622 46421 46540
0 0 0
2w6d
172.22.15.250 4 65501 9302940 9310366 4117016 0 0
2d17h

State/PfxRcd
Idle
2
Active
1

To check what the received routes from this neighbor are, following command is used. This command
shows the network which is received from the neighbor. Metric of the receiving route along with local
preference, next hop, and origin and AS path can be viewed through this command. For redistributed
routes origin will be incomplete and showed by ? Sign
LDN-KHISTT-C3845>sh ip bgp neighbors 172.22.15.250 received-routes
BGP table version is 4117396, local router ID is 210.2.130.207
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network
Next Hop
* 172.22.0.0/20
172.22.15.250
Total number of prefixes 1

Metric
0

LocPrf Weight
0

Path
64594 65501 ?

To check what the advertised routes from this neighbor are, following command is used. This
command shows the network which is received from the neighbor. Metric of the receiving route along
with local preference, next hop, and origin and AS path can be viewed through this command. For
redistributed routes origin will be incomplete and showed by ? Sign
LDN-KHISTT-C3845>sh ip bgp neighbors 172.22.15.250 advertised-routes
BGP table version is 4117479, local router ID is 210.2.130.207
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network
Next Hop
*> 172.22.0.8/30
202.147.184.213
*> 210.2.181.16/28
202.147.184.213
Total number of prefixes 2

Metric LocPrf Weight

8
32768
1029
32768

Path
?
?

Provider Edge end BGP show Commands output for VPNv4 unicast Neighborship
To Checked the bgp vpnv4 vrf neighbor status on cisco router below is the command. It shows the
local Router ID and AS number, Neighbor IP, Neighbor AS, Neighbor state and receive prefix numbers.
LDN-KHISTT-C3845>sh ip bgp vpnv4 vrf VPN_LDNVOICE summary
BGP router identifier 210.2.130.207, local AS number 23966
Neighbor
10.0.7.226
10.0.22.146
10.0.122.70
10.5.24.78
10.5.24.194
10.5.26.78

V AS
4 64612
4 64599
4 64599
4 64639
4 64652
4 64773

MsgRcvd MsgSent TblVer InQ OutQ

0
0
0 0 0
0
0
0 0 0
310073 310958 2629899 0 0
232036 232442 2629899 0 0
51167 48114 2629899 0 0
12271 12363 2629899 0 0

Up/Down
never
never
2w1d
5d10h
01:42:54
00:46:05

State/PfxRcd
Idle (Admin)
Idle
1
1
1
1

In above show command output, 1 of the neighbor status is Never and state is Idle (Admin). Admin
means neighbor is shutdown administratively by NOC.
To check what the received routes from this neighbor are, following command is used. This command
shows the network which is received from the neighbor. Metric of the receiving route along with local
preference, next hop, and origin and AS path can be viewed through this command. For redistributed
routes origin will be incomplete and showed by ? Sign
LDN-KHISTT-C3845> sh ip bgp vpnv4 vrf VPN_LDNVOICE neighbors 10.5.24.194 received-routes
BGP table version is 2629953, local router ID is 210.2.130.207
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network

Next Hop

Metric LocPrf

Weight

Path

Route Distinguisher: 23966:2099 (default for vrf VPN_LDNVOICE)

*
*
*
*

119.30.126.48/29
192.168.0.24/29
192.168.1.0
192.168.6.0

10.5.24.194
10.5.24.194
10.5.24.194
10.5.24.194

Total number of prefixes 4

10
10
10
10

0
0
0
0

64652 i
64652 i
64652 i
64652 i

To check what the advertised routes from this neighbor are, following command is used. This
command shows the network which is received from the neighbor. Metric of the receiving route along
with local preference, next hop, and origin and AS path can be viewed through this command. For
redistributed routes origin will be incomplete and showed by ? Sign
LDN-KHISTT-C3845> sh ip bgp vpnv4 vrf VPN_LDNVOICE neighbors 10.5.24.194 advertised-routes
BGP table version is 2629985, local router ID is 210.2.130.207
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Originating default network 0.0.0.0
Network

Next Hop

Metric LocPrf Weight Path

Total number of prefixes 0

In above show command output, total number of prefixes is 0 as we are only advertising default route
and on cisco router under BGP process by configuring the command originate-default route on any
neighbor, default route will be originated.

PE End Juniper BRAS Routers Troubleshooting Commands

Provider Edge end BGP show Commands output for IPv4 unicast Neighborship
LDN-KHIMRD-BRAS1440>sh ip bgp summary
Local router ID 202.147.184.251, local AS 23966
BGP Operational state is Up
Default local preference is 100
IGP synchronization is disabled
Default originate is disabled
Auto summary is disabled
Always compare MED is disabled
BGP administrative distances are 20 (ext), 200 (int), and 200 (local)
Redistribution of iBGP routes is disabled
Graceful restart is globally disabled
Global graceful-restart restart time is 120 seconds
Global graceful-restart stale paths time is 360 seconds
Graceful-restart path selection defer time is 360 seconds
Graceful-restart is ready to switch to the standby SRP
The last restart was graceful

Neighbor
10.0.7.110
10.0.8.210
10.0.8.238
10.0.22.122
10.0.42.14

Messages
AS
State
Up/down time Sent
64609 Active 294d 00:33:56 620128
64581 Established 1d 13:13:47 1663950
64608 Connect
01:05:22
130923
64556 Established 4d 12:26:32 26613827
64533 Connect 587d 16:03:03
0

Messages
Received
465199
885726
71387
24539043
0

Prefixes
Received
0
1
0
1
0

LDN-KHIMRD-BRAS1440>sh ip bgp neighbors 10.0.65.74 advertised-routes

% RIB-out is disabled for peer 10.0.65.74 in address family ipv4:unicast
LDN-KHIMRD-BRAS1440>sh ip bgp neighbors 10.0.65.74 received-routes
Local BGP identifier 202.147.184.251, local AS 23966
Status codes: > best, * invalid, s suppressed, d dampened, r rejected,
Prefix
Peer
Next-hop
MED LocPrf Weight Origin
r 0.0.0.0/0
10.0.65.74 10.0.65.74
10
0 IGP
202.61.42.104/29 10.0.65.74 10.0.65.74
10
0 IGP
210.2.128.240/29 10.0.65.74 10.0.65.74
10
0 IGP

a auto-summarized

Provider Edge end BGP show Commands output for VPNv4 unicast Neighborship
LDN-KHIMRD-BRAS1440>sh ip bgp vpnv4 vrf VPN_MAKRO summary
Local router ID 202.147.184.251, local AS 23966
BGP Operational state is Up
Default local preference is 100
Default originate is disabled
Auto summary is disabled
Log neighbor changes is enabled
BGP administrative distances are 20 (ext), 200 (int), and 200 (local)
Graceful restart is globally disabled
Global graceful-restart restart time is 120 seconds
Global graceful-restart stale paths time is 360 seconds
Graceful-restart path selection defer time is 360 seconds
Graceful-restart is ready to switch to the standby SRP
The last restart was graceful
Route Distinguisher: 23966:2122
Messages Messages
Neighbor
AS State
Up/down time Sent Received
10.0.7.174 64534 Established 16:35:27 3540341 11712586
10.0.115.126 64534 Active 587d 16:10:38
0
0

Prefixes
Received
2
0

LDN-KHIMRD-BRAS1440>sh ip bgp vpnv4 vrf VPN_MAKRO neighbors 10.0.7.174 advertised-routes

% RIB-out is disabled for peer 10.0.7.174 in address family ipv4:unicast
LDN-KHIMRD-BRAS1440>sh ip bgp vpnv4 vrf VPN_MAKRO neighbors 10.0.7.174 received-routes
Local BGP identifier 202.147.184.251, local AS 23966
Status codes: > best, * invalid, s suppressed, d dampened, r rejected,
a auto-summarized
Prefix
> 10.83.8.0/23
> 172.16.4.0/30

Peer
10.0.7.174
10.0.7.174

Next-hop
10.0.7.174
10.0.7.174

MED LocPrf Weight

20
0
20
0

Origin
IGP
IGP

PE End Juniper M-Series Routers Troubleshooting Commands

Provider Edge end BGP show Commands output for IPv4 unicast Neighborship
usman.ahmed@LDN-KHINTO-M10i> show bgp neighbor 10.0.7.90
Peer: 10.0.7.90+2668 AS 64616 Local: 10.0.7.89+179 AS 23966
Type: External State: Established Flags: <Sync>
Last State: OpenConfirm Last Event: RecvKeepAlive
Last Error: Cease
Export: [ pl-Groupm-KhybneJmiLLVPN-S-Fiber-INT-Export ]
Import: [ pl-Groupm-KhybneJmiLLVPN-S-Fiber-INT-Import ]
Holdtime: 90 Preference: 20 Localpref: 20
Number of flaps: 240
Last flap event: HoldTime
Error: 'Hold Timer Expired Error' Sent: 89 Recv: 20
Error: 'Cease' Sent: 31 Recv: 107
Local Interface: ge-0/0/0.27
Send state: in sync
Active prefixes:
0
Received prefixes:
2
Accepted prefixes:
1
Suppressed due to damping: 0
Advertised prefixes:
1
Last traffic (seconds): Received 4 Sent 2 Checked 4
Input messages: Total 8184 Updates 13 Refreshes 0 Octets 156012
Output messages: Total 8741 Updates 5
Refreshes 0 Octets 166289
Output Queue[0]: 0
usman.ahmed@LDN-KHINTO-M10i> show route advertising-protocol bgp 10.0.7.90
inet.0: 5137 destinations, 5223 routes (5127 active, 0 holddown, 77 hidden)
Prefix
Nexthop
MED Lclpref
AS path
* 202.147.184.248/32 Self
4
I
usman.ahmed@LDN-KHINTO-M10i> show route receive-protocol bgp 10.0.7.90
inet.0: 5138 destinations, 5224 routes (5128 active, 0 holddown, 77 hidden)
Prefix
Nexthop
MED Lclpref
AS path
10.0.7.100/32
10.0.7.90
10
64616 I

Provider Edge end BGP show Commands output for VPNv4 unicast Neighborship
usman.ahmed@LDN-KHINTO-M10i> show bgp neighbor instance VPN_GROUPM
Peer: 192.168.1.2+17688 AS 64616 Local: 192.168.1.1+179 AS 23966
Type: External State: Established Flags: <Sync>
Last State: OpenConfirm Last Event: RecvKeepAlive
Last Error: Hold Timer Expired Error
Export: [ pl-GROUPM-Export ] Import: [ pl-GROUPM-Import ]
Options: <Preference Localpref PeerAS Refresh>
Holdtime: 90 Preference: 20 Localpref: 20
Number of flaps: 223
Last flap event: HoldTime
Error: 'Hold Timer Expired Error' Sent: 136 Recv: 16
Error: 'Cease' Sent: 26 Recv: 48
Local Interface: ge-0/0/0.26
Send state: in sync
Active prefixes:
0
Received prefixes:
2
Accepted prefixes:
1
Suppressed due to damping: 0
Advertised prefixes:
1
Last traffic (seconds): Received 1 Sent 7 Checked 32
Input messages: Total 8187 Updates 13 Refreshes 0 Octets 156073
Output messages: Total 8740 Updates 1
Refreshes 0 Octets 166138
Output Queue[46]: 0
usman.ahmed@LDN-KHINTO-M10i> show route advertising-protocol bgp 192.168.1.2
VPN_GROUPM.inet.0: 29 destinations, 30 routes (28 active, 0 holddown, 1 hidden)
Prefix
Nexthop
MED Lclpref
AS path
* 10.10.10.10/32
Self
?
usman.ahmed@LDN-KHINTO-M10i> show route receive-protocol bgp 192.168.1.2
VPN_GROUPM.inet.0: 29 destinations, 30 routes (28 active, 0 holddown, 1 hidden)
Prefix
Nexthop
MED Lclpref
AS path
11.11.11.11/32
192.168.1.2
10
64616 I

CE End Juniper SSG5 Troubleshooting Commands and Configuration

BGP Config
set vrouter "trust-vr"
set protocol bgp 64591
set enable
set neighbor 10.5.23.129 remote-as 23966 local-ip 10.5.23.130/30 outgoing-interface ethernet0/1.1
set neighbor 10.5.23.129 enable
set neighbor 10.5.23.129 md5-authentication ldn@64591
set neighbor 10.5.23.213 remote-as 23966 local-ip 10.5.23.214/30 outgoing-interface ethernet0/0
set neighbor 10.5.23.213 enable
set neighbor 10.5.23.213 md5-authentication ldn@64591
set neighbor 10.5.23.129 activate
set neighbor 10.5.23.129 med 10
set neighbor 10.5.23.213 activate
set neighbor 10.5.23.213 weight 70
set neighbor 10.5.23.213 med 20
set network 202.147.187.0/27
set network 202.61.43.64/27
set network 11.11.11.11/32
exit
exit
set interface ethernet0/1.1 protocol bgp
set interface ethernet0/0 protocol bgp
LNH-StadiumRoad-S-Fiber-> get vrouter trust-vr protocol bgp neighbor
Peer AS Remote IP
Local IP
Wt Status State ConnID Up/Down
-------------------------------------------------------------------------------------23966 10.5.23.129 10.5.23.130
50 Enabled ESTABLISH 8 18:34:01
23966 10.5.23.213 10.5.23.214
70 Enabled ACTIVE
0 19d;14:51:52
Total 2 BGP peers shown

LNH-StadiumRoad-S-Fiber-> get vrouter trust-vr protocol bgp network

network
weight check reachable-prefix rib-in route-map
-------------------------------------------------------------------------------------202.147.187.0/27 32768 no none
yes null
202.61.43.64/27 32768 no none
yes null
11.11.11.11/32 32768 no none
yes null

LNH-StadiumRoad-S-Fiber-> get vrouter trust-vr protocol bgp rib-in

i: IBGP route, e: EBGP route, >: best route, *: valid route
Prefix
Nexthop Wt Pref Med Orig AS-Path
-------------------------------------------------------------------------------------Total ipv4 routes in rib-in: 7 (0 in flap-damping history)
------------------------------------------------------------------------------------->e*
0.0.0.0/0 10.5.26.73 100 100 0 IGP 23966
e
0.0.0.0/0 10.5.23.129 50 100 0 IGP 23966
>e* 10.10.10.10/32 192.168.10.205 100 100 0 INC 23966
e 10.10.10.10/32 192.168.10.201 50 100 0 INC 23966
>i 11.11.11.11/32
0.0.0.0 32768 100 0 IGP
>i 202.61.43.64/27
0.0.0.0 32768 100 0 IGP
>i 202.147.187.0/27
0.0.0.0 32768 100 0 IGP
Total no. of ipv4 entries shown: 7
In case of as-override you will be observing more than 1 AS number i.e. 23966 under AS-Path
LHR-GRM-> get vrouter trust-vr protocol bgp rib-in

CE End Cisco Troubleshooting Commands and Configuration

BGP Config
router bgp 64513
no synchronization
bgp log-neighbor-changes
network 10.104.15.0 mask 255.255.255.252
network 202.147.188.248 mask 255.255.255.248
network 210.2.140.12 mask 255.255.255.252
network 210.2.140.72 mask 255.255.255.248
neighbor 10.104.15.5 remote-as 23966
neighbor 10.104.15.5 soft-reconfiguration inbound
neighbor 10.104.15.5 prefix-list PRFX-DATA out
neighbor 10.104.15.5 route-map PRI-DATA-LOCAL-PRE in
neighbor 10.104.15.5 route-map PRI-DATA-MED out
neighbor 10.104.15.9 remote-as 23966
neighbor 10.104.15.9 soft-reconfiguration inbound
neighbor 10.104.15.9 prefix-list PRFX-INTERNET out
neighbor 10.104.15.9 route-map PRI-LOCAL-PREF in
neighbor 10.104.15.9 route-map PRI-INTERNET-MED out
neighbor 10.104.15.21 remote-as 23966
neighbor 10.104.15.21 soft-reconfiguration inbound
neighbor 10.104.15.21 prefix-list PRFX-DATA out
neighbor 10.104.15.21 route-map BCK-DATA-LOCAL-PRE in
neighbor 10.104.15.21 route-map BCK-DATA-MED out
neighbor 10.104.15.25 remote-as 23966
neighbor 10.104.15.25 soft-reconfiguration inbound
neighbor 10.104.15.25 prefix-list PRFX-INTERNET out
neighbor 10.104.15.25 route-map BCK-LOCAL-PREF in
neighbor 10.104.15.25 route-map BCK-INTERNET-MED out
no auto-summary
ip access-list standard DEFAULT-ROUTE
permit any
ip access-list extended DATA-ROUTES
permit ip 10.0.0.0 0.255.255.255 any

ip access-list extended PRFX-DATA

permit ip 10.104.15.0 0.0.0.3 any
ip access-list extended PRFX-INTERNET
ip prefix-list PRFX-DATA seq 10 permit 10.104.15.0/30
ip prefix-list PRFX-INTERNET seq 10 permit 210.2.140.72/29
ip prefix-list PRFX-INTERNET seq 20 permit 210.2.140.12/30
ip prefix-list PRFX-INTERNET seq 30 permit 202.147.188.248/29
route-map BCK-LOCAL-PREF permit 10
match ip address DEFAULT-ROUTE
set local-preference 50
route-map PRI-LOCAL-PREF permit 10
match ip address DEFAULT-ROUTE
set local-preference 100
route-map BCK-DATA-MED permit 10
match ip address prefix-list PRFX-DATA
set metric 10
route-map PRI-DATA-MED permit 10
match ip address prefix-list PRFX-DATA
set metric 1
route-map PRI-INTERNET-MED permit 10
match ip address prefix-list PRFX-INTERNET
set metric 1
route-map BCK-INTERNET-MED permit 10
match ip address prefix-list PRFX-INTERNET
set metric 10
route-map PRI-DATA-LOCAL-PRE permit 10
match ip address DATA-ROUTES
set local-preference 100
route-map BCK-DATA-LOCAL-PRE permit 10
match ip address DATA-ROUTES
set local-preference 50

ISM_HO#sh ip bgp summary

BGP router identifier 192.168.2.1, local AS number 64537
Neighbor

V AS MsgRcvd MsgSent TblVer InQ OutQ

Up/Down State/PfxRcd

10.0.57.105

4 23966 178982 168096 15512 0 0

1w4d

10.0.57.109

4 23966 169958 177956 15512 0 0

03:44:44

ISM_HO#sh ip bgp

ISM_HO#sh ip bgp neighbors 10.0.57.105 advertised-routes

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network
Next Hop
*> 192.168.2.0 0.0.0.0

Metric LocPrf Weight Path

0
32768 i

Total number of prefixes 1

ISM_HO#sh ip bgp neighbors 10.0.57.105 received-routes
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network
Next Hop
Metric LocPrf Weight Path
r 0.0.0.0
10.0.57.105
0 23966 i
* 6.6.6.6/32
10.0.57.105
0 23966 ?
* 7.7.7.7/32
10.0.57.105
0 23966 ?
r 10.0.57.104/30 10.0.57.105
0 23966 i

22
23

Troubleshooting BGP (Flow Charts)

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a008009478a.shtml

Main Troubleshooting Flowchart

Troubleshooting BGP Neighbor Establishment

Troubleshooting Routes Missing from the Routing Table

Troubleshooting BGP Route Advertisement