10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

Privacy Policy

BGP RACE CONDITION

UNDEFINED
UNDEFINEDNo comments    
UNDEFINED
categories: BGP

Share This:    Facebook  Twitter  Google+  Stumble  Digg

Topology is quite simple, we have two routers that are directly connected and they will form an eBGP (
BGP race condition occurs only in ebgp peering) neighbor relationship that is sourced by each loopback
address of the router.

OSPF is activated on the physical links and ont the lo0 of the routers and they are fully adjacent within
area 0.

 We configure a eBGP session between the routers:

 R1#conf t
 R1(config)#router bgp 1
 R1(config-router)#no auto
 R1(config-router)#no sync

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 1/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

 R1(config-router)#neighbor 2.2.2.2 remote-as 2

 R1(config-router)#neighbor 2.2.2.2 update-source lo0

 R2#conf t
 R2(config)#router bgp 2
 R2(config-router)#no auto
 R2(config-router)#no sync
 R2(config-router)#neighbor 1.1.1.1 remote-as 1
 R2(config-router)#neighbor 1.1.1.1 update-source lo0
 
As we will see the bgp neighborship will not come up! Why?
 Well as the routers try to start the BGP adjacency from their loopbacks they are not directly
connected.
 So we need to configure the bgp option “disable-connected-check”. This option makes directly
connected neighbors to build an adjacency even if they connect via their loopbacks.

 R1(config-router)#neighbor 2.2.2.2 disable-connected-check

R2(config-router)#neighbor 1.1.1.1 disable-connected-check

And the BGP adjacency will form.

 R1:
 *Mar 1 01:59:28.559: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Up
R2:
 *Mar 1 01:59:28.707: %BGP-5-ADJCHANGE: neighbor 1.1.1.1 Up

Now we are going to advertise the lo10 of each router into bgp to see if it works fine.

 R1(config-router)#network 10.10.10.10 mask 255.255.255.255

R2(config-router)#network 20.20.20.20 mask 255.255.255.255

Verifying on R2:
 R2#sh ip bgp
 BGP table version is 167, local router ID is 2.2.2.2
 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
 *> 10.10.10.10/32 1.1.1.1 0 0 1 i
 *> 20.20.20.20/32 0.0.0.0 0 32768 I
Verifying n R1:
  R1#sh ip bgp
 BGP table version is 172, local router ID is 1.1.1.1
 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
 r RIB-failure, S Stale
 Origin codes: i - IGP, e - EGP, ? - incomplete

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 2/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

Network Next Hop Metric LocPrf Weight Path

 *> 10.10.10.10/32 0.0.0.0 0 32768 i
 *> 20.20.20.20/32 2.2.2.2 0 0 2 i

Looks good.
 No we come to the “race condition”. We will now also advertise the lo0 of each router into BGP. Very
many people might do this as they say “Hey its good to have lo0 in it here”.

 R1(config-router)#network 1.1.1.1 mask 255.255.255.255

R2(config-router)#network 2.2.2.2 mask 255.255.255.255

Taking a look into the bgp table first looks good.

 R2#sh ip bgp
 BGP table version is 175, local router ID is 2.2.2.2
 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
 *> 1.1.1.1/32 1.1.1.1 0 0 1 i
 *> 2.2.2.2/32 0.0.0.0 0 32768 i
 *> 10.10.10.10/32 1.1.1.1 0 0 1 i
 *> 20.20.20.20/32 0.0.0.0 0 32768 i

R1#sh ip bgp
 BGP table version is 176, local router ID is 1.1.1.1
 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
 *> 1.1.1.1/32 0.0.0.0 0 32768 i
 *> 2.2.2.2/32 2.2.2.2 0 0 2 i
 *> 10.10.10.10/32 0.0.0.0 0 32768 i
 *> 20.20.20.20/32 2.2.2.2 0 0 2 i
But what we are going to see after some time is that the BGP adjacency will tear down!
 R1#
 *Mar 1 02:25:15.855: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Down BGP Notification sent
 R1#
 *Mar 1 02:25:15.855: %BGP-3-NOTIFICATION: sent to neighbor 2.2.2.2 4/0 (hold time expired) 0
bytes
 R2#
 *Mar 1 02:25:16.359: %BGP-5-ADJCHANGE: neighbor 1.1.1.1 Down BGP Notification sent
 R2#
 *Mar 1 02:25:16.359: %BGP-3-NOTIFICATION: sent to neighbor 1.1.1.1 4/0 (hold time expired) 0
bytes

Some seconds after that log message the BGP session comes up again.

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 3/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

 R2#
 *Mar 1 02:25:45.999: %BGP-5-ADJCHANGE: neighbor 1.1.1.1 Up
 R1#
 *Mar 1 02:25:45.991: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Up

When you take a look into the routing table you can see the problem. Usually you should see the
loopback of the peering router known via the IGP (OSPF in that case).
 R1#sh ip route 2.2.2.2
 Routing entry for 2.2.2.2/32
 Known via "ospf 1", distance 110, metric 11, type intra area
 Last update from 172.16.21.2 on FastEthernet0/0, 00:00:15 ago
 Routing Descriptor Blocks:
 * 172.16.21.2, from 172.16.21.2, 00:00:15 ago, via FastEthernet0/0
 Route metric is 11, traffic share count is 1

When the BGP session comes up you see it know via BGP because the AD of eBGP is 20 and that is
lower than 110
 R1#sh ip route 2.2.2.2
 Routing entry for 2.2.2.2/32
 Known via "bgp 1", distance 20, metric 0
 Tag 2, type external
 Last update from 2.2.2.2 00:00:42 ago
 Routing Descriptor Blocks:
 * 2.2.2.2, from 2.2.2.2, 00:00:42 ago
 Route metric is 0, traffic share count is 1
 AS Hops 1
 Route tag 2

And this is the problem here. We know the loopback of R2 which is 2.2.2.2 via the loopback of R2. This
cannot work. In case of the BGP advertising the route to 2.2.2.2/32 thats problematic as BGP here
sets its BGP peer address as next-hop.
 So this route recursion points to the fact that the loopback addresses of the routers cannot reach
each other and the BGP session times out.

 Solution for that:

 - Never advertise the update-source of a BGP session into BGP itself, as BGP is not capable of
providing the transport for itself.
In IBGP peering, the Race condition doesn't occur because after advertising the peering loopbacks in
BGP they are not installed in the routing table ( hence no race condition) ,RIB , because of the fact that
the administrative Distance AD of IBGP is 200 which is more than any other routing protocol. Hence
due to " RIB failure " the ibgp NLRI is not installed in the routing table.

+1   Recommend this on Google

Related Posts:

BGP: 51 Points to Remember for BGP

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 4/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

A path vector protocol could be a network routing protocol that maintains the trail data
that gets updated dynamically. Updates that have coiled thro… Read More

BGP NSF( Non-Stop Forwarding)

BGP support for NSF requires that neighbor routers are NSF-aware or NSF-capable.
NSF awareness in BGP is also enabled by the graceful restart mechani… Read More

BGP RACE CONDITION

Topology is quite simple, we have two routers that are directly connected and they will
form an eBGP ( BGP race condition occurs only in ebgp peeri… Read More

BGP Route Aggregation

Route aggregation methodology helps in minimizing the number of routing tables in an
IP (Internet Protocol) network. Meaning, it consolidates selecte… Read More

BGP: Path Selection Criteria - Path Vector Protocol

#Cisco #Routing #BGP BGP ( Border Gateway Protocol ) Specifications TCP 179 port
local and an Application Protocol. AD: eBGP AD: 20; iBGP AD: 200 … Read More

Newer Post Home Older Post

0 comments:

Post a Comment

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 5/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

Enter your comment...

Comment as:  Unknown (Google) Sign out

Publish   Preview   Notify me

Links to this post

Create a Link

Subscribe to: Post Comments (Atom)

Popular Posts

OSI Model
The Open Systems Interconnection model ( OSI )is a conceptual model that characterizes
and standardizes the inner functions of a communica...

Secure Socket Layer ( SSL) Connection Setup

SSL (Secure Sockets Layer) is a standard security technology for establishing an
encrypted link between a server and a client—typically a w...

Traceroute
Traceroute, by default, sends a sequence of User Datagram Protocol (UDP) packets
addressed to a destination host; ICMP Echo Request or TCP ...

F5 Load Balancers: LTM vs GTM

F5® BIG-IP® Global Traffic Manager™ (GTM) distributes DNS and user application
requests based on business policies, data center and cloud s...

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 6/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

Comparison of Routers Cisco, Juniper and Huawei

Comparison of Routers Cisco, Juniper and Huawei # Cisco , Juniper and Huawei Router
comparison # CCI E Candidates only # MPLS requireme...

OSPF : "34 Things to remember"

Open Shortest Path First (OSPF) is a routing protocol for Internet Protocol (IP) networks. It uses a link
state routing algorithm and fal...

Cisco ASR 1002-X Basics

Cisco ASR 1002-X   # Cisco Routers #CCIE Candidates  # ASR Routers Specifications #
Capacity and Utilization # RP and ESP Processors ...

Interview questions for Networking Engineer's( CCNA/CCNP and CCIE candidates )

Please find some of the questions who are preparing for the interviews ( CCNA/CCNP) These are the
questions for the Network Engineer bas...

CISCO-JUNIPER COMMANDS REF

Cisco Command Juniper Command Co-Ordinating Definition show ip interface brief show interface
terse displays the status of interface...

LACP and PAgP

Hi so we have the Following descriptions of all these what is LACP and PAgP. What is Ether Channel?
Ether Channel links shaped while  or...


Search Search

TOTAL PAGEVIEWS

1,561,278

BLOG ARCHIVE

Blog Archive

LIKE US !!

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 7/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

Networks­Baseline
82,630 likes

Liked Sign Up

You like this

CATEGORIES
access Lists (3) ADSL (3) Alcatel-Lucent (2) ARP (4) ASA (8) ATM (2) Basic Commands (3) Basics (13)
BGP (31) Brocade (1) Cables (1) CatOS (1) CCIE (3) CCIE Datacenter (22) CCNA (7)
CCNP (1) Checkpoint (3) Cisco (4) Cisco ASR (7) Cisco Icons (1) Cisco MDS Switch Cisco Routers (12)
(1)
Cisco Switches (7) Cisco Wireless (2) Cloud Computing (2) Data Center (17) DHCP (4) DWDM (1)
EIGRP (7) Etherchannel (3) F5 (2) Fiber Optics (1) Firewall (2) Fortinet (1) GLBP (5) GNS3 (2) Huawei (4)
interview Questions (1) IOS (1) IOS Upgradation (3) IoT (1) IP Addressing (2) IPV6 (2) Juniper (13) LABS (2)

MPLS (21) MPLS Traffic Engg. (3) MTU (5) Multicast (3) Nexus (20) OSI
Load Balancing (5)
Model (1) OSPF (22) OTV (2) Palo-Alto (2) Password Recovery (1) Physical (1) PPP (2) Riverbed (3) RSTP
(2) SDN & NFV (2) SSL (1) Stack (1) subnetting (3) Switching (9) TACACS (1) TCP (2) TCP and UDP ports (2)
Technology (1) Terminal Server (1) Topologies (5) Traceroute (2) VLAN (4) VPN (3) VRRP (4) WAN
optimization (4)

FEEDJIT

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 8/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

Live Traffic Feed
A visitor from Stockton,
California viewed "Point­to­
Point Protocol (PPP), the
Link Control Protocol (LCP)
and CHAP (Challenge­
A visitor from Lansing,
Handshake Authentication
Michigan viewed "The
Protocol) ~" 1 min ago
Concept of PHP (Penultimate
Hop Popping) ­ MPLS ~" 2
A visitor from United States
mins ago
viewed "F5 Load Balancers:
LTM vs GTM ~" 6 mins ago
A visitor from La Paz viewed
"BGP: Path Selection Criteria
­ Path Vector Protocol ~" 7
A visitor from Ramsis, Al
mins ago
Buhayrah viewed ": BGP" 7
mins ago
A visitor from Pune,
Maharashtra viewed "F5 Load
Balancers: LTM vs GTM ~"
11 mins ago
A visitor from Karachi, Sindh
viewed "OSPF Area and LSAs
Propagation. ~" 20 mins ago
A visitor from Doha, Ad
Dawhah viewed "25 Things to
remember about EIGRP:
Short and Simple ~" 24 mins
A visitor from San Diego,
ago
California viewed "Point­to­
Point Protocol (PPP), the
Link Control Protocol (LCP)
and CHAP (Challenge­
A visitor from San Francisco,
Handshake Authentication
California viewed "The
Protocol) ~" 26 mins ago
Concept of PHP (Penultimate
Hop Popping) ­ MPLS ~" 34
Real­time view · Get Feedjit

ALEXA

Copyright@ 2006-2015 Networks-Baseline. Powered by Blogger.

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 9/10
10/24/2016 BGP RACE CONDITION ~ << Networks Baseline ­ Cisco Engineers Live >>

Copyright © 2016 << Networks Baseline - Cisco Engineers Live >> | Powered by Blogger
Design by BluChic | Blogger Theme by Lasantha - PremiumBloggerTemplates.com | BTheme.net | Distributed
By Gooyaabi Templates

http://www.networksbaseline.in/2014/08/bgp­race­condition.html 10/10