10/24/2016 BGP Route Aggregation ~ << Networks Baseline ­ Cisco Engineers Live >>

Privacy Policy

BGP Route Aggregation

UNDEFINED
UNDEFINEDNo comments    
UNDEFINED
categories: BGP

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

Route aggregation happens where multiple routes are rolled up into a series of shorter prefixes (ie 4
/24′s become a /22). The idea is to reduce the number of routes that need to be processed. Often, the
specifics don’t matter. If I’m advertising the 4 /24′s as above and they all go the the same place, why
does the whole Internet need to know about all four of them when a single /22 will describe the whole
lot?
This also leads to some global routing stability. If one of the /24′s went down, I don’t have to tell the
rest of the Internet since the /22 covers three other networks that are working. Yes, any packets
destined to the downed network will return an error, but it’s a small price to pay to reduce the amount
of flapping on the Internet.
While getting the size of the global route tables down is a great idea, sites that are multihomed face
challenges with route aggregation, which means that BGP has to handle the exceptions.
To illustrate the last point, consider this example network. It’s similar to what we’ve been following
along with except that I split AS1 into two separate ASNs for later examples.
Imagine that AS1 advertised a /24 prefix (1.1.42.0/24) to AS2 and AS3, and that AS2 aggregated this
to a /16 (1.1.0.0/16) before sending it to AS3. Now, further imagine that both AS2 and AS3 were
transit providers to the rest of the Internet, and advertised their prefixes out.
The rest of the Internet would see a /24 via AS3, and a /16 via AS2. Following the longest match rule,
all packets to anything in 1.1.42.0/24 would go via AS3 even though R3 in AS1 indicated that both
links were available.
The solution is that AS2 must also advertise the /24 in addition to the /16. It is not necessary to
advertise all the component routes, just the ones that need to stand alone on the Internet. This is
called “punching a hole”, and is often necessary for sites to be properly multihomed. This comes up in
many cases where an AS got its address space from a provider rather than obtaining provider
independant space from ARIN. In this example, it is possible that AS1 started off with address space
from AS2 before becoming multihomed.
In the example above, R3 has several networks in the 10/8 space it can aggregate to R0 in AS4:

http://www.networksbaseline.in/2012/10/bgp­route­aggregation.html 1/9
10/24/2016 BGP Route Aggregation ~ << Networks Baseline ­ Cisco Engineers Live >>

r0#show ip bgp 10.0.0.0/8 longer­prefixes 
BGP table version is 7, local router ID is 10.0.0.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
*> 10.1.1.0/24      10.50.0.2                              0 1 2 i
*> 10.2.2.0/24      10.50.0.2                              0 1 3 i
*> 10.3.3.0/24      10.50.0.2                0             0 1 i

Using “aggregate-address” under the BGP configuration on R3, we can force it to only advertise a
summary route:

r3(config­router)#aggregate­address 10.0.0.0 255.0.0.0 summary­only 

r0#show ip bgp 10.0.0.0/8 longer­prefixes 
BGP table version is 11, local router ID is 10.0.0.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
*> 10.0.0.0         10.50.0.2                              0 1 i

R3 doesn’t discriminate when it sends out the summary, so R2 and R1 also see it:

r2#show ip bgp 10.0.0.0/8 longer­prefixes 
BGP table version is 14, local router ID is 10.2.2.1
Status codes: s suppressed, d damped, h history, * valid, > best, i ­ internal
Origin codes: i ­ IGP, e ­ EGP, ? ­ incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 10.0.0.0         192.168.3.5                            0 1 i
*> 10.1.1.0/24      192.168.3.9              0    200      0 2 i
*> 10.2.2.0/24      0.0.0.0                  0         32768 i

Interestingly enough, r3 shows that it is suppressing the more specific routes, and has created a route
to Null0 representing the aggregate (remember anything more specific that exists will be in R3′s
routing table, and won’t hit the Null0 bit bucket)

r3#show ip bgp
BGP table version is 16, local router ID is 10.3.3.1
Status codes: s suppressed, d damped, h history, * valid, > best, i ­ internal
Origin codes: i ­ IGP, e ­ EGP, ? ­ incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 10.0.0.0         0.0.0.0                            32768 i
s> 10.1.1.0/24      192.168.3.2              0             0 2 i
s> 10.2.2.0/24      192.168.3.6              0             0 3 i
s                   192.168.3.2                            0 2 3 i
s> 10.3.3.0/24      0.0.0.0                  0         32768 i
r3#show ip route
...
     10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
http://www.networksbaseline.in/2012/10/bgp­route­aggregation.html 2/9
10/24/2016 BGP Route Aggregation ~ << Networks Baseline ­ Cisco Engineers Live >>
B       10.0.0.0/8 [200/0] via 0.0.0.0, 00:44:14, Null0
B       10.2.2.0/24 [20/0] via 192.168.3.6, 02:37:15
B       10.1.1.0/24 [20/0] via 192.168.3.2, 02:42:55
C       10.3.3.0/24 is directly connected, Loopback5
C       10.50.0.0/24 is directly connected, Ethernet0

In this case it’s fine because the intended goal is met, but if anything in the 10/8 space existed
elsewhere we might find some bad routing.
On R0 it knows this is an aggregate:

r0#show ip bgp 10.0.0.0
BGP routing table entry for 10.0.0.0/8, version 11
Paths: (1 available, best #1, table Default­IP­Routing­Table)
  Not advertised to any peer
  1, (aggregated by 1 10.3.3.1)
    10.50.0.2 from 10.50.0.2 (10.3.3.1)
      Origin IGP, localpref 100, valid, external, atomic­aggregate, best

The problem, though, is that the AS-PATH to the aggregate doesn’t include any of the component
ASNs. Since this is used for loop avoidance, routing loops can be introduced in larger systems.
The as-set option to the aggregate-address command brings forward some of these things:

r3(config)#router bgp 1
r3(config­router)#no  aggregate­address 10.0.0.0 255.0.0.0 summary­only
r3(config­router)# aggregate­address 10.0.0.0 255.0.0.0 summary­only as­set 
r0#show ip bgp 10.0.0.0 255.0.0.0 longer­prefixes 
...
   Network          Next Hop            Metric LocPrf Weight Path
*> 10.0.0.0         10.50.0.2                              0 1 {2,3} i
r0#show ip bgp 10.0.0.0
BGP routing table entry for 10.0.0.0/8, version 19
Paths: (1 available, best #1, table Default­IP­Routing­Table)
Flag: 0x820
  Not advertised to any peer
  1 {2,3}, (aggregated by 1 10.3.3.1)
    10.50.0.2 from 10.50.0.2 (10.3.3.1)
      Origin IGP, localpref 100, valid, external, best

The {2,3} shows that these AS contributed to the aggregate. atomic-aggregate has also disappeared,
since the information has been included.
The last thing I’ll try today is leaving out summary-only and putting in as-set:

r3#show ip bgp 10.0.0.0 255.0.0.0 longer­prefixes 
BGP table version is 5, local router ID is 10.3.3.1
Status codes: s suppressed, d damped, h history, * valid, > best, i ­ internal
Origin codes: i ­ IGP, e ­ EGP, ? ­ incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 10.0.0.0         0.0.0.0                            32768 {2,3} i
*> 10.1.1.0/24      192.168.3.2              0             0 2 i
*> 10.2.2.0/24      192.168.3.6              0             0 3 i
*                   192.168.3.2                            0 2 3 i
*> 10.3.3.0/24      0.0.0.0                  0         32768 i
r0#show ip bgp 10.0.0.0 255.0.0.0 longer­prefixes 
BGP table version is 30, local router ID is 10.0.0.1

http://www.networksbaseline.in/2012/10/bgp­route­aggregation.html 3/9
10/24/2016 BGP Route Aggregation ~ << Networks Baseline ­ Cisco Engineers Live >>
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.0.0.0         10.50.0.2                              0 1 {2,3} i
*> 10.1.1.0/24      10.50.0.2                              0 1 2 i
*> 10.2.2.0/24      10.50.0.2                              0 1 3 i
*> 10.3.3.0/24      10.50.0.2                0             0 1 i

As expected, we see an aggregate and the specific routes.

+1   Recommend this on Google

Related Posts:

BGP Unequal Load Cost Sharing

We are going to make R4 use both links when reaching prefixes on the internet.  25% of
the traffic will go via AS2, and 75% of the traffic will go v… 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 Community: No-Export

BGP No-Export ensures prefixes to not get advertised outside of an AS. In the diagram
below, I’m going to configure R2 to advertise the 100.100.100.… Read More

Remove BGP Private-AS

The BGP private-as numbers range from 64512 – 65535. Because they are private, it
means they are not globally unique. This means that ISP’s need to… Read More

BGP: 51 Points to Remember for BGP

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

Newer Post Home Older Post

0 comments:

Post a Comment

http://www.networksbaseline.in/2012/10/bgp­route­aggregation.html 4/9
10/24/2016 BGP Route Aggregation ~ << 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/2012/10/bgp­route­aggregation.html 5/9
10/24/2016 BGP Route Aggregation ~ << 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,340

BLOG ARCHIVE

Blog Archive

LIKE US !!

http://www.networksbaseline.in/2012/10/bgp­route­aggregation.html 6/9
10/24/2016 BGP Route Aggregation ~ << 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/2012/10/bgp­route­aggregation.html 7/9
10/24/2016 BGP Route Aggregation ~ << Networks Baseline ­ Cisco Engineers Live >>

Live Traffic Feed
A visitor from Islamabad
arrived 6 mins ago
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) ~" 10 mins ago
Concept of PHP (Penultimate
Hop Popping) ­ MPLS ~" 10
A visitor from United States
mins ago
viewed "F5 Load Balancers:
LTM vs GTM ~" 14 mins ago
A visitor from La Paz viewed
"BGP: Path Selection Criteria
­ Path Vector Protocol ~" 15
A visitor from Ramsis, Al
mins ago
Buhayrah viewed ": BGP" 15
mins ago
A visitor from Pune,
Maharashtra viewed "F5 Load
Balancers: LTM vs GTM ~"
19 mins ago
A visitor from Karachi, Sindh
viewed "OSPF Area and LSAs
Propagation. ~" 29 mins ago
A visitor from Doha, Ad
Dawhah viewed "25 Things to
remember about EIGRP:
Short and Simple ~" 32 mins
A visitor from San Diego,
ago
California viewed "Point­to­
Point Protocol (PPP), the
Link Control Protocol (LCP)
and CHAP (Challenge­
Real­time view · Get Feedjit

ALEXA

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

http://www.networksbaseline.in/2012/10/bgp­route­aggregation.html 8/9
10/24/2016 BGP Route Aggregation ~ << 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/2012/10/bgp­route­aggregation.html 9/9