BGP( Border

Gateway
Protocol with
Labs)
 IBGP with Loopback

Why we need to configure IBGP Neighbor ships on loopback and not on physical links?

For example we have configured IBGP neighbor ship on physical link and that particular link
goes down then reachability to that Router will be not there.

And same if we have IBGP on loopback and the link between R1 and R2 goes down we still have
IBGP up as it is configured on loopback.

Here we have performed link failure between R1 and R2:

We see that IBGP neighborship is still up, but we see that OSPF neighbor ship is down, as we
know that OSPF sends keep alive message after every 10 seconds and its dead interval is 40
seconds, and BGP by default keep alive is 60 seconds and dead interval is 180 seconds.

So OSPF will immediately calculate another path and BGP will not even know that there is any
link failure in the network.
Initially we have done only IBGP configuration in network, we will debug what issues we had
faced:

R1 config:

router bgp 100

neighbor [Link] remote-as 100
neighbor [Link] remote-as 100
network [Link]

R2 Config:

router bgp 100

neighbor [Link] remote-as 100
neighbor [Link] remote-as 100
network [Link]

R3 Config:

router bgp 100

neighbor [Link] remote-as 100
neighbor [Link] remote-as 100
network [Link]
After configuring IBGP in Routers, we see that IBGP Neighborship is not UP, it is in Active state.

What is BGP Active state?

1. Mismatch in Configuration.
2. Network is not reachable.

As we here see that BGP is in Active state.

After configuring IBGP Neighborship and advertising networks in IBGP we see that IBGP Neighborship is
not UP and only connected routes are seen in routing table. We see that the neighbors which we are
trying to form neighborship with that loopback address is not there in routing table.

So we can get this reachability via IGP (OSPF/ISIS/EIGRP), In lab scenario BGP is not used as IGP because
IGP convergence needs to be fast and as we know that BGP has keep alive/dead interval =60/180
seconds which is too high for IGP convergence and IBGP AD value is also 200 which is very poor.
We need to make sure that the loopback is advertised in IGP once you do that you will see that IBGP
neighborship will be up now.
 BGP Attributes

1. Weight
2. Local Preference
3. Origin
4. Next Hop
5. AS Path
6. MED (Multi exit discriminator)
7. Community
8. Route Aggregation
9. Router ID lowest
10. Cluster List
11. Neighbor Address Lowest
 Weight Attribute
1. It is local to a router, it is use to change routers own decision.
2. Paths with highest weight are most desirable.
3. Weight configured on router per neighbor basis.
4. Weight is not sent to any BGP Neighbors.

Topology:

On R2 we have configured Weight 1050 for Neighbor [Link] and 1000

for neighbor [Link]

router bgp 200

no synchronization
bgp log-neighbor-changes
network [Link]
 network [Link]
network [Link]
network [Link]
redistribute static
neighbor [Link] remote-as 100
neighbor [Link] weight 1050
neighbor [Link] remote-as 200
neighbor [Link] next-hop-self
neighbor [Link] weight 1000
no auto-summary
!

R2#sh ip bgp
BGP table version is 11, local router ID is [Link]
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

* [Link] [Link] 0 1050 100 i
*> [Link] 0 32768 i
* i2.0.0.0 [Link] 0 100 1000 i
*> [Link] 0 32768 i
* i5.0.0.0 [Link] 0 100 1000 100 i
*> [Link] 0 1050 100 i
*> [Link] [Link] 1050 100 i
*i [Link] 0 100 1000 i
* i10.0.0.0 [Link] 0 100 1000 100 i
*> [Link] 0 1050 100 i
*> [Link] [Link] 0 32768 i
*> [Link] [Link] 0 32768 ?
*> [Link] [Link] 1050 100 i
*i [Link] 0 100 1000 100 i
R2#

The router will influence its own decision as we have configured

weight 1050 for neighbor [Link] and 1000 for neighbor [Link]

For network [Link] at R2 there are 2 paths but it is marking best as

1050 weight whose NH is [Link] whose weight is higher than
neighbor [Link]
 Next Hop Attribute:
There is Next hop Rule for IBGP as well for EBGP:

IBGP: When EBGP Learned route is sent to IBGP neighbor NH will be retained, so
we don’t want the NH will be retained so we will configure NH self-command.

EBGP: When a route is sent to EBGP Neighbor Next Hop will be self.

R1 is having IBGP neighbor ship with R4, so when EBGP routes advertised in
IBGP for that NH will be retained.

R4(config-router)#do sh ip bgp
BGP table version is 9, local router ID is [Link]
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
* [Link] [Link] 0 200 i
*>i [Link] 0 100 0 i
*> [Link] [Link] 0 0 200 i
*i [Link] 0 100 0 200 i
* i5.0.0.0 [Link] 0 100 0 i
*> [Link] 0 32768 i
* [Link] [Link] 0 0 200 i
*> [Link] 0 32768 i
*>i10.0.0.0 [Link] 0 100 0 i
*> [Link] [Link] 0 200 i
*i [Link] 0 100 0 200 i
*> [Link] [Link] 0 200 ?
*i [Link] 0 100 0 200 ?
*> [Link] [Link] 0 32768 i

At R4, Network [Link], [Link], [Link] is advertised by R2 to R1 via

EBGP to IBGP and we can see that its NH is retained [Link]

We want that if R1 is advertising this route to R4, NH should be R1’s

interface IP.

So for that we need to configure Next-Hop self-command at R1.

neighbor [Link] next-hop-self

R4(config-router)#do sh ip bgp
BGP table version is 13, local router ID is [Link]
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
*>i1.0.0.0 [Link] 0 100 0 i
* [Link] 0 200 i
* i2.0.0.0 [Link] 0 100 0 200 i
*> [Link] 0 0 200 i
* i5.0.0.0 [Link] 0 100 0 i
*> [Link] 0 32768 i
* [Link] [Link] 0 0 200 i
*> [Link] 0 32768 i
*>i10.0.0.0 [Link] 0 100 0 i
* i20.0.0.0 [Link] 0 100 0 200 i
*> [Link] 0 200 i
* i30.0.0.0 [Link] 0 100 0 200 ?
*> [Link] 0 200 ?
*> [Link] [Link] 0 32768 i
R4(config-router)#

Now we can see that NH is changed which is R1’s interface [Link]

 Origin Attribute:

It is the attribute from which we can read BGP table correctly.

Origin codes are: Origin codes: i - IGP, e - EGP, ? – incomplete

Incomplete with ? is the attribute which we have redistributed via
static into BGP, redistributed route in BGP will be shown as ?

i-IGP: This indicates that route was injected via network command
under the BGP Process.

e-EGP: Originated from an External Gateway Protocol.

R4(config-router)#do sh ip bgp
BGP table version is 13, local router ID is [Link]
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

*>i1.0.0.0 [Link] 0 100 0 i
* [Link] 0 200 i
* i2.0.0.0 [Link] 0 100 0 200 i
*> [Link] 0 0 200 i
* i5.0.0.0 [Link] 0 100 0 i
*> [Link] 0 32768 i
* [Link] [Link] 0 0 200 i
*> [Link] 0 32768 i
*>i10.0.0.0 [Link] 0 100 0 i
* i20.0.0.0 [Link] 0 100 0 200 i
*> [Link] 0 200 i
* i30.0.0.0 [Link] 0 100 0 200 ?
*> [Link] 0 200 ?
*> [Link] [Link] 0 32768 i
R4(config-router)#
 Local Preference:
1. It is local to an AS.
2. Default value is 100.
3. It is sent to IBGP Neighbors only.
4. If set to one router in an AS will get updated to all the routers in
that AS.
5. Highest the preference better the path.

Topology:

Configure AS 100 such that all traffic destined for AS 200 should go through R2.
Use Local-Preference Attribute to accomplish this task.
Configure route-map using local-preference attribute to manipulate the routing
information on R3.

R3
Route-map list1 permit 10
Set local preference 50
Router bgp 200
Neighbor [Link] remote-as 200
Neighbor [Link] route-map list1 in
 AS Path:

If we need to reach a particular network, whichever path where

number of AS is less to reach that particular network that path will be
preferred and will be selected as an best path.

Now we will check this with lab:

R1(config-route-map)#do sh ip bgp
BGP table version is 8, local router ID is [Link]
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> [Link] [Link] 0 0 100 i
r [Link] 0 100 i
*> [Link] [Link] 0 0 100 i
* [Link] 0 0 100 i
r> [Link] [Link] 0 100 i
r [Link] 0 0 100 i
*> [Link] [Link] 0 0 100 i
* [Link] 0 100 i
*> [Link] [Link] 0 100 i
* [Link] 0 0 100 i
R1(config-route-map)#

On R1 we can see that best path selected is [Link] for each network, but why it
is selecting [Link] and not [Link]?

It will select Best path using below table, First it will check Weight if it is same
then it will check LP if it is same and so on, in our case here it is selecting the
lowest router ID so [Link] is preferred over [Link]
Now we need to manipulate the path and make [Link] as the best
path sing Attribute AS Path.

R1 Configuration:

To Neighbor [Link] we have prepended AS Paths 200 twice as now AS

path 200 will be added twice whichever route is coming via neighbor
[Link]

neighbor [Link] route-map ASPath in

route-map ASPath permit 10

set as-path prepend 200 200

R1(config-route-map)#do sh ip bgp
BGP table version is 11, local router ID is [Link]
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

*> [Link] [Link] 0 32768 i
* [Link] 0 0 200 200 100 i
* [Link] 0 100 i
* [Link] [Link] 0 0 200 200 100 i
*> [Link] 0 0 100 i
*> [Link] [Link] 0 32768 i
* [Link] 0 200 200 100 i
* [Link] 0 0 100 i
*> [Link] [Link] 0 32768 i
* [Link] [Link] 0 0 200 200 100 i
*> [Link] 0 100 i
* [Link] [Link] 0 200 200 100 i
*> [Link] 0 0 100 i
R1(config-route-map)#

As Now we can see that [Link] is selected as the best Path.

 MED (Multi Exit discriminator)
1. MED is used by Neighbor to influence your decision.
2. MED is sent to External BGP Neighbors only to influence its decision.
3. There is no default metric.
4. Lowest metric value will be preferred.

All ingress (incoming) traffic to AS 200 should use the path through R3 using the
MED attribute. Configure the MED on R1 to 100 and Configure the MED on R3 to
50. Lower MED will be preferred.
 BGP Community:
It is a Transitive Attribute; it is attached with route
when sent to another AS.
no-export Do not export to next AS (well-known community)

no-advertise Do not advertise to any peer (well-known community)

local-AS Do not send outside local AS (well-known community)

internet Internet (well-known community)

Topology:

R4, R2, R1 is in AS 100 and R3 is in AS 200.

R3(config-router)#do sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

B [Link]/8 [20/0] via [Link], [Link]

C [Link]/8 is directly connected, Serial4/2
B [Link]/8 [20/0] via [Link], [Link]
B [Link]/8 [20/0] via [Link], [Link]
B [Link]/8 [20/0] via [Link], [Link]
B [Link]/8 [20/0] via [Link], [Link]
C [Link]/8 is directly connected, FastEthernet0/0

As we can see R3 has a route of [Link]/8 network.

Network [Link] should not be sent outside AS 100 using no-export

community attribute, so after configuring community with no-export
on R1 towards Neighbor R2, R2 will not export this network to
another AS, Access-list will be used to specify only network [Link]

router bgp 100

network [Link]
network [Link]
neighbor [Link] remote-as 100
neighbor [Link] send-community
neighbor [Link] route-map no-exp out

access-list 1 permit [Link] [Link]

route-map no-exp permit 10
match ip address 1
set community no-export

R3(config-router)#do sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

B [Link]/8 [20/0] via [Link], [Link]

C [Link]/8 is directly connected, Serial4/2
B [Link]/8 [20/0] via [Link], [Link]
B [Link]/8 [20/0] via [Link], [Link]
B [Link]/8 [20/0] via [Link], [Link]
C [Link]/8 is directly connected, FastEthernet0/0

R2(config-router)#do sh ip bgp [Link]

BGP routing table entry for [Link]/8, version 28
Paths: (1 available, best #1, table Default-IP-Routing-Table, not
advertised to EBGP peer)
Flag: 0x820
Not advertised to any peer
Local
[Link] from [Link] ([Link])
Origin IGP, metric 0, localpref 100, valid, internal, best
 Community: no-export
R2(config-router)#do sh ip bgp [Link]
BGP routing table entry for [Link]/8, version 28
Paths: (1 available, best #1, table Default-IP-Routing-Table, not
advertised to EBGP peer)
Flag: 0x820
Not advertised to any peer
Local
[Link] from [Link] ([Link])
Origin IGP, metric 0, localpref 100, valid, internal, best
Community: no-export

Similarly if we don’t want to advertise a network to any peer we will

use no-advertise in place of no-export.

Community with Numeric Values:

In the previous lab, we used ACL to identify routes then match them
in a route map then assign one of the four standard well-known
communities (tags) , In such case routers know what to do with these
tagged routes based on which one of the four standard well-known
communities we are using.

However, when using numeric values for tagging, we will have specific
actions to do with these tagged routes, actions such as using Local
preference or setting specific next hop for these routes.

Therefore, we will need ACL to identify tags then apply action on this
ACL, in this case, this is not called ACL but called Community List.
Once you configure your Named Community list , you can match these
lists in route-map configuration with match community command.

Topology:

R1 and R2 is in AS 1, R3 is in AS 100, R4 is in AS200.

AS 1 represents Customer, AS 100 represents ISP 1, and AS 200

represents ISP 2

R3 (ISP 1) received prefix [Link]/24 from R4 (ISP 2) and R1

(Customer)

Since Weight and Local Preferences are left at their default values so
R3 will choose the best path to [Link]/24 with the shortest AS
Path which is R1 .
Our objective here will be to influence R3 to send his traffic through
R3 instead of R1.

How we will accomplish that?

You as a Customer agreed with ISP1 that 100:17 communities will set
the Local Preferences to 50 on ISP 1 side, since default LP is 100 so
when we set it to 50 it will not choose as the best path.

Configuration at R1:

neighbor [Link] route-map CLN out

neighbor [Link] send-community
route-map CLN permit 10
set community 100:17
Configuration at R3:

neighbor [Link] route-map setLP in

ip community-list 7 permit 100:17
route-map setLP permit 10
match community 7
set local-preference 50
Notice that community is displayed as a single 32-bit value , if you
want it to be in a form of as:nn then use the following command:

R3(config)#ip bgp-community new-format.

 BGP Confederations:

1. Used only when in single AS where there are 60-70 routers, which is a
huge numbers which comes under Service Provider Network.
2. It is use to divide single AS into Sub AS.
3. In the AS where we will do sub division of AS, IBGP Peering will be inside
AS and EBGP Peering will be done in between of AS, for EBGP
configuration there is a command of confederations.
4. Customer End side we will only observe the Main AS, for example there is
an AS 600 and inside it we have subdivided AS into 2 sub sections: 2300
and 4000, one more thing is Main AS should be in Public AS and
Subdivided AS should be in Private AS.
5. So In Customer End side we won’t see this subdivided AS we will only see
that the routes are coming from AS 600.
6. And Inside SP network where we have subdivided AS there we will
observe AS path in (2300) (bracket and subdivided AS number) so from
that we can know it is an subdivided AS.
R2 Configuration:
R2:

int f0/0
ip add [Link] [Link]
no sh

int s4/0

ip add [Link] [Link]

no sh

int s4/1

ip add [Link] [Link]

no sh

router bgp 2300 (SUB AS)

no synchronization
bgp log-neighbor-changes
bgp confederation identifier 600 (MAIN AS, we need to mention that 600 is our main AS)
neighbor [Link] remote-as 500
neighbor [Link] remote-as 2300 (For IBGP No extra configuration is required)

network [Link]
network [Link]
network [Link]

R3:

int s4/1

ip add [Link] [Link]

no sh

int f0/0
ip add [Link] [Link]
no sh

int s4/3

ip add [Link] [Link]

no sh

router bgp 2300

bgp confederation identifier 600

neighbor [Link] remote-as 2300

bgp confederation peer 4000 ( When configuring EBGP in confederation required this
command)
neighbor [Link] remote-as 4000

network [Link]
network [Link]
network [Link]

OUTPUT
 BGP Route Dampening:

Why we required BGP Route Dampening?

1. When there is a network instability which can lead to BGP route flap due
to which routes/prefix are also getting flapped.
2. An unstable network can cause BGP routes to flap, which can cause other
BGP routes in the network to constantly re-coverage.
3. This wastes valuable CPU cycles and can cause severe problems in the
network.
4. In this case there are 2 options:
a. Route Summarization.
b. Route Dampening.
5. In Route summarization, if there is 4 network for example
[Link]/24,[Link]/24,[Link]/24,[Link]/24 these routes will be
summarized as [Link]/22, so whenever 1 network link flap for example
[Link]/24 is flap it will not send an update about it and when all the
network link flap happens then only it will send update about it further,
so this how it will solve the problem of link flap.
6. Route Dampening only used in EBGP, each time an EBGP route flaps it
gets 1000 penalty points (This cannot be configured and changed).
a. Suppress: The value at which route is damped, means after this value
routes will not be advertised, and default is 2000.
b. Reuse: when the route/prefix gets stable after getting damped, so
after reducing the value less than 750 again that routes will be
advertised, default value is 750.
c. Max-suppress-time: Maximum time to suppress the route is
60 minutes (default), the prefix which is damped and the
suppress value keeps on increasing, this value will get
increased up to a certain limit of time which is 60 minutes
after that it will recalculate again.
 d. Half Life: Decay time in which penalty is halved, default is 15
minutes, for example penalty is 3000 after reaching the half
time which is 15 minutes penalty will reduce to 1500 which is
half of 3000, which means if the link is still flapping it will
again increase and if the link is not flapping it has a better
chance to reduce penalty below 750 and route gets stable and
then it will be advertised into BGP.

History state in BGP Route Dampening:

After a single route flap, the route is assigned a penalty and the
dampening state of the route is set to history. Default penalty for a
route flap is 1000, each the route flaps penalty increases.

LAB:
After configuring BGP dampening on R2, we can see default timers
below:

BGP output on R2:

Now we will flap [Link]/24 network and check the behavior, we can
see that after flapping [Link]/24 network it has gone in history
state.
As default value for suppression is 2000, after some flaps if that value
reaches above 2000 then [Link]/24 will go in damped state and the
routes will not be advertised to R1.

Output at R1 as we see that Route is damped and not advertised on

R1:
When the penalty goes below 750 then the network is stable and now
it will advertise the route in BGP.
 Route Aggregator/Summarization:

BGP Route aggregator reduces the number of BGP entries in the

routing table, helping to increase internet routing stability by hiding
route flaps.
In Route summarization, if there is 4 network for example
[Link]/24,[Link]/24,[Link]/24,[Link]/24 these routes will be
summarized as [Link]/22, so whenever 1 network link flap for example
[Link]/24 is flap it will not send an update about it and when all the network
link flap happens then only it will send update about it further, so this how it
will solve the problem of link flap.

On R3 we are doing summary of route, configuring route aggregator,

summary only is configured which means it will only advertised
summary network which we are advertising in BGP.
Output on R3:

Output on R2:
R2(config-router)#do sh ip bgp
BGP table version is 37, local router ID is [Link]
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

R2(config-router)#do sh ip bgp
BGP table version is 37, local router ID is [Link]
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

* [Link] [Link] 0 0 100 i
*> [Link] 0 32768 i
* [Link] [Link] 0 0 300 i
*> [Link] 0 32768 i
*> [Link] [Link] 0 0 300 i
*> [Link] [Link] 0 0 100 i
*> [Link]/22 [Link] 0 0 300 i
s> [Link]/24 [Link] 0 300 400 i
*> [Link]/22 [Link] 32768 i
s> [Link]/24 [Link] 0 300 400 i
s> [Link]/24 [Link] 0 300 400 i
s> [Link]/24 [Link] 0 300 400 i
*> [Link] [Link] 0 32768 i
*> [Link] [Link] 0 0 300 i

On R2 when we check for summary route for [Link]/22, we see that

Next Hop is [Link] which is directly connected, weight is 32768 and
AS path is I, which means AS path information is lost, as we know that
route [Link]/24 is originating from R4 and we are summarizing it on
R2, after summarizing AS path, NH weight information is lost, which
may leads to routing loops.

R2(config-router)#do sh ip bgp [Link]/22

BGP routing table entry for [Link]/22, version 38
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Flag: 0x820
Advertised to update-groups:
2
300 400, (aggregated by 200 [Link])
[Link] from [Link] ([Link])
Origin IGP, localpref 100, weight 32768, valid, aggregated, local, best
So to avoiding routing loops we need to configure as set option in
route aggregator, it will add the required information of AS path as
shown below.
R2(config-router)#aggregate-address [Link] [Link] summary-only as
R2(config-router)#$ddress [Link] [Link] summary-only as-set
R2(config-router)#do sh ip bgp
BGP table version is 38, local router ID is [Link]
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

* [Link] [Link] 0 0 100 i
*> [Link] 0 32768 i
* [Link] [Link] 0 0 300 i
*> [Link] 0 32768 i
*> [Link] [Link] 0 0 300 i
*> [Link] [Link] 0 0 100 i
*> [Link]/22 [Link] 0 0 300 i
s> [Link]/24 [Link] 0 300 400 i
*> [Link]/22 [Link] 100 32768 300 400 i
s> [Link]/24 [Link] 0 300 400 i
s> [Link]/24 [Link] 0 300 400 i
s> [Link]/24 [Link] 0 300 400 i
*> [Link] [Link] 0 32768 i
*> [Link] [Link] 0 0 300 i
R2(config-router)#do sh ip bgp [Link]/22
BGP routing table entry for [Link]/22, version 38
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Flag: 0x820
Advertised to update-groups:
2
300 400, (aggregated by 200 [Link])
[Link] from [Link] ([Link])
Origin IGP, localpref 100, weight 32768, valid, aggregated, local, best
R2(config-router)#do wr
Building configuration...
[OK]
R2(config-router)#

Suppress Map:

We have configured loopback on R1 and condition is we need to

summarize only 2 routes out of 4 with suppress only.
access-list 1 deny [Link] [Link]
access-list 1 deny [Link] [Link]
access-list 1 permit any

The network which we don’t want to suppress, so here we don’t want to suppress [Link] and [Link] network
so we are denying in access list, rest all network will be suppressed.

R1(config)#do sh run | sec route-map

route-map aggregator permit 10
match ip address 1
R1(config)#do sh run | sec aggregat
aggregate-address [Link] [Link] summary-only suppress-map aggregator
route-map aggregator permit 10
match ip address 1
R1(config)#

In access list which prefix we will deny other than that prefixes all will
be suppressed by suppress map.

Suppressed route is marked as s>

R1(config)#do sh ip bgp
BGP table version is 20, local router ID is [Link]
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

*> [Link] [Link] 0 32768 i
* [Link] 0 0 200 i
*> [Link] [Link] 0 0 200 i
*> [Link] [Link] 0 200 300 i
*> [Link] [Link] 0 32768 i
s> [Link]/24 [Link] 0 32768 i
*> [Link]/22 [Link] 32768 i
s> [Link]/24 [Link] 0 32768 i
s> [Link]/24 [Link] 0 32768 i
s> [Link]/24 [Link] 0 32768 i
*> [Link]/22 [Link] 0 200 300 i
*> [Link]/22 [Link] 0 0 200 300 400 i
*> [Link] [Link] 0 0 200 i
*> [Link] [Link] 0 200 300 i

After suppress-map applied:

R1(config)#do sh ip bgp
BGP table version is 34, local router ID is [Link]
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
*> [Link] [Link] 0 32768 i
* [Link] 0 0 200 i
*> [Link] [Link] 0 0 200 i
*> [Link] [Link] 0 200 300 i
*> [Link] [Link] 0 32768 i
*> [Link]/24 [Link] 0 32768 i
*> [Link]/22 [Link] 32768 i
*> [Link]/24 [Link] 0 32768 i
s> [Link]/24 [Link] 0 32768 i
s> [Link]/24 [Link] 0 32768 i
*> [Link]/22 [Link] 0 200 300 i
*> [Link]/22 [Link] 0 0 200 300 400 i
*> [Link] [Link] 0 0 200 i
*> [Link] [Link] 0 200 300 i

Another term is Unsuppressed Map, where we will deny network in

access list, that network will be suppressed and all other network will
not be suppressed.

Route Reflector Basics:

1. It is used to break split horizon rule.

2. For example there are 10 routers in a network.
3. We made 2 Router as reflector and 5 as client and 4 as Non-
client.
4. RR will receive the update from Client as well as Non-client.
5. RR will send updates received from Client to Non-client.
6. RR will not send updates received from Non-client to client.
7. If one single AS is divided into 2 clusters, which means 2
different cluster has different RR, route originating from one
cluster will add some extra information that from which Router
this prefix is originated, that will be the originator ID.
8. Cluster ID is nothing but the router ID of the route reflector in
that particular cluster.