Lab - Implement eBGP for IPv4

Topology

Addressing Table
Device Interface IPv4 Address

R1 G0/0/0 [Link]/24

R1
S0/1/0 [Link]/25

R1
S0/1/1 [Link]/25

R1
Loopback0 [Link]/27

R1
Loopback1 [Link]/26
R2 G0/0/0 [Link]/24

R2
G0/0/1 [Link]/24

R2
Loopback0 [Link]/27

R2
Loopback1 [Link]/26
R3 G0/0/0 [Link]/24

R3
S0/1/0 [Link]/25

R3
S0/1/1 [Link]/25

R3
Loopback0 [Link]/27

R3
Loopback1 [Link]/26

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 18

-
 Lab - Implement eBGP for IPv4

Objectives
Part 1: Build the Network and Configure Basic Device Settings and Interface Addressing
Part 2: Configure and Verify eBGP for IPv4 on all Routers
Part 3: Configure and Verify Route Summarization and Atomic Aggregate
Part 4: Configure and Verify Route Summarization with Atomic Aggregate and AS-Set
Part 5: Configure and Verify the Advertising of a Default Route

Background / Scenario
In this lab you will configure eBGP for IPv4.
Note: This lab is an exercise in developing, deploying, and verifying various path manipulation tools for BGP,
and does not reflect networking best practices.
Note: The routers used with CCNP hands-on labs are Cisco 8300L with Cisco IOS XE Release 17.12.05c
(universalk9 image). Other routers and Cisco IOS versions can be used. Depending on the model and Cisco
IOS version, the commands available and the output produced might vary from what is shown in the labs.
Note: Ensure that the routers and switches have been erased and have no startup configurations. If you are
unsure contact your instructor.

Required Resources
• 3 Routers (Cisco Catalyst 8200L with Cisco IOS XE Release 17.12.05c universal image or comparable)
• 1 PC (Windows with a terminal emulation program, such as Tera Term)
• Console cables to configure the Cisco IOS devices via the console ports
• Ethernet and serial cables as shown in the topology

Instructions

Part 1: Build the Network and Configure Basic Device Settings and Interface
Addressing
In Part 1, you will set up the network topology and configure basic settings and interface addressing on
routers.

Step 1: Cable the network as shown in the topology.

Attach the devices as shown in the topology diagram, and cable as necessary.

Step 2: Configure basic settings for each router.

a. Console into each router, enter global configuration mode, and apply the basic settings and interface
addressing. A command list for each router is provided below.
Open configuration window

Router R1
hostname R1
no ip domain lookup
line con 0
logging sync
exec-time 0 0
exit

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 18

-
 Lab - Implement eBGP for IPv4

interface Loopback0
ip address [Link] [Link]
no shut
exit
interface Loopback1
ip address [Link] [Link]
no shut
exit
interface GigabitEthernet0/0/0
ip address [Link] [Link]
no shut
exit
interface Serial0/1/0
ip address [Link] [Link]
no shut
exit
interface Serial0/1/1
ip address [Link] [Link]
no shut
exit
Router R2
hostname R2
no ip domain lookup
line con 0
logging sync
exec-time 0 0
exit
interface Loopback0
ip address [Link] [Link]
no shut
exit
interface Loopback1
ip address [Link] [Link]
no shut
exit
interface GigabitEthernet0/0/0
ip address [Link] [Link]
no shut
exit
interface GigabitEthernet0/0/1
ip address [Link] [Link]
no shut
exit
Router R3
hostname R3

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 18

-
 Lab - Implement eBGP for IPv4

no ip domain lookup
line con 0
logging sync
exec-time 0 0
exit
interface Loopback0
ip address [Link] [Link]
no shut
exit
interface Loopback1
ip address [Link] [Link]
no shut
exit
interface GigabitEthernet0/0/0
ip address [Link] [Link]
negotiation auto
no shut
exit
interface Serial0/1/0
ip address [Link] [Link]
no shut
exit
interface Serial0/1/1
ip address [Link] [Link]
no shut
exit
b. Save the running configuration to startup-config.
Close configuration window

Part 2: Configure and Verify eBGP for IPv4 on all Routers

Step 1: Implement BGP and neighbor relationships on R1.
a. Enter BGP configuration mode from global configuration mode, specifying AS 1000.
Open configuration window

R1(config)# router bgp 1000

b. Configure the BGP router-id for R1.
R1(config-router)# bgp router-id [Link]
c. Based on the topology diagram, configure all the designated neighbors for R1.
R1(config-router)# neighbor [Link] remote-as 500
R1(config-router)# neighbor [Link] remote-as 300
R1(config-router)# neighbor [Link] remote-as 300
d. Configure R1 to advertise the IPv4 prefixes local to ASN 1000.
R1(config-router)# network [Link] mask [Link]
R1(config-router)# network [Link] mask [Link]
Close configuration window

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 18

-
 Lab - Implement eBGP for IPv4

Step 2: Implement BGP and neighbor relationships on R2.

a. Enter BGP configuration mode from global configuration mode, specifying AS 500.
Open configuration window

R2(config)# router bgp 500

b. Configure the BGP router-id for R2.
R2(config-router)# bgp router-id [Link]
c. Based on the topology diagram, configure all the designated neighbors for R2.
R2(config-router)# neighbor [Link] remote-as 1000
R2(config-router)# neighbor [Link] remote-as 300
d. Configure R2 to advertise the IPv4 prefixes local to ASN 500.
R2(config-router)# network [Link] mask [Link]
R2(config-router)# network [Link] mask [Link]
Close configuration window

Step 3: Implement BGP and neighbor relationships on R3.

a. Enter BGP configuration mode from global configuration mode, specifying AS 300.
Open configuration window

R3(config)# router bgp 300

b. Configure the BGP router-id for R3.
R3(config-router)# bgp router-id [Link]
c. Unlike the configuration on R1 and R2, disable the default IPv4 unicast behavior.
R3(config-router)# no bgp default ipv4-unicast
The default behavior in IOS is bgp default ipv4-unicast. Routers R1 and R2 were configured using this
default behavior. The bgp default ipv4-unicast command enables the automatic exchange of IPv4
address family prefixes. When this command is disabled using no bgp default ipv4-unicast, BGP
neighbors must be activated within IPv4 address family (AF) configuration mode. BGP network
commands must also be configured within IPv4 AF mode.
d. Based on the topology diagram, configure all the designated neighbors for R3.
R3(config-router)# neighbor [Link] remote-as 500
R3(config-router)# neighbor [Link] remote-as 1000
R3(config-router)# neighbor [Link] remote-as 1000
Close configuration window

Step 4: Verifying BGP neighbor relationships.

a. Examine the routing tables on each router. Notice that R1 and R2 are receiving BGP prefixes from each
other but not receiving BGP prefixes from R3. And R3 is not receiving any prefixes from R1 or R2. This is
because R3 was configured using no bgp default ipv4-unicast and the interfaces must be activated
within IPv4 address configuration mode.
Open configuration window

R1# show ip route bgp | begin Gateway

Gateway of last resort is not set

[Link]/24 is variably subnetted, 2 subnets, 2 masks

B [Link]/27 [20/0] via [Link], 00:28:40
B [Link]/26 [20/0] via [Link], 00:28:40

R2# show ip route bgp | begin Gateway

Gateway of last resort is not set

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 5 of 18

-
 Lab - Implement eBGP for IPv4

[Link]/24 is variably subnetted, 2 subnets, 2 masks

B [Link]/27 [20/0] via [Link], 00:29:41
B [Link]/26 [20/0] via [Link], 00:29:41

R3# show ip route bgp | begin Gateway

Gateway of last resort is not set

b. This can be further verified by examining the BGP neighbor adjacencies on R2. Notice the BGP state
between R2 and R1 is established, while the BGP state between R2 and R3 is idle.
R2# show ip bgp neighbors
BGP neighbor is [Link], remote AS 1000, external link
BGP version 4, remote router ID [Link]
BGP state = Established, up for 00:35:34
Last read 00:00:28, last write 00:00:35, hold time is 180, keepalive interval is 60
seconds
Neighbor sessions:
1 active, is not multisession capable (disabled)
<output omitted>

BGP neighbor is [Link], remote AS 300, external link

BGP version 4, remote router ID [Link]
BGP state = Idle, down for never
Neighbor sessions:
0 active, is not multisession capable (disabled)
<output omitted>

c. The interfaces on R3 need to be activated in IPv4 AF configuration mode. The neighbor activate
command in IPv4 AF configuration mode is required to enable the exchange of BGP information between
neighbors. This will enable R3 to form an established neighbor adjacency with both R1 and R2.
Additionally, because bgp default ipv4-unicast is disabled, network commands must be configured in
IPv4 AF configuration mode.
R3(config-router)# address-family ipv4
R3(config-router-af)# neighbor [Link] activate
R3(config-router-af)# neighbor [Link] activate
R3(config-router-af)# neighbor [Link] activate
R3(config-router-af)# network [Link] mask [Link]
R3(config-router-af)# network [Link] mask [Link]
d. Verify that all BGP speakers are receiving prefixes from their neighbors. The prefixes from R3 are
highlighted in the routing tables of R1 and R2.
Note: The prefixes in the lab are for example purposes only. Most service providers do not accept
prefixes larger than /24 for IPv4 (/25 through /32).
R1# show ip route bgp | begin Gateway
Gateway of last resort is not set

[Link]/24 is variably subnetted, 2 subnets, 2 masks

B [Link]/27 [20/0] via [Link], 00:51:09
B [Link]/26 [20/0] via [Link], 00:51:09
[Link]/24 is variably subnetted, 2 subnets, 2 masks
B [Link]/27 [20/0] via [Link], 00:01:43

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 6 of 18

-
 Lab - Implement eBGP for IPv4

B [Link]/26 [20/0] via [Link], 00:01:43

R2# show ip route bgp | begin Gateway

Gateway of last resort is not set

[Link]/24 is variably subnetted, 2 subnets, 2 masks

B [Link]/27 [20/0] via [Link], 00:51:17
B [Link]/26 [20/0] via [Link], 00:51:17
[Link]/24 is variably subnetted, 2 subnets, 2 masks
B [Link]/27 [20/0] via [Link], 00:01:51
B [Link]/26 [20/0] via [Link], 00:01:51

R3# show ip route bgp | begin Gateway

Gateway of last resort is not set

[Link]/24 is variably subnetted, 2 subnets, 2 masks

B [Link]/27 [20/0] via [Link], 00:02:11
B [Link]/26 [20/0] via [Link], 00:02:11
[Link]/24 is variably subnetted, 2 subnets, 2 masks
B [Link]/27 [20/0] via [Link], 00:02:11
B [Link]/26 [20/0] via [Link], 00:02:11

e. Verify that the BGP state between R2 and R3 has now been established.
R2# show ip bgp neighbors | begin BGP neighbor is [Link]
BGP neighbor is [Link], remote AS 300, external link
BGP version 4, remote router ID [Link]
BGP state = Established, up for 00:12:16
Last read 00:00:37, last write 00:00:52, hold time is 180, keepalive interval is 60
seconds
Last update received: 00:02:29
Neighbor sessions:
1 active, is not multisession capable (disabled)
<output omitted>
Close configuration window

Step 5: Examining the running-configs.

Examine the running-configs on all three routers. Because router R3 was configured using no bgp default
ipv4-unicast command, notice that the network commands were automatically entered under the IPv4 AF.
This is the same configuration mode where the neighbors were activated to exchange BGP information.
Open configuration window

R1# show running-config | section bgp

router bgp 1000
bgp router-id [Link]
bgp log-neighbor-changes
network [Link] mask [Link]
network [Link] mask [Link]
neighbor [Link] remote-as 500
neighbor [Link] remote-as 300
neighbor [Link] remote-as 300

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 7 of 18

-
 Lab - Implement eBGP for IPv4

R2# show running-config | section bgp

router bgp 500
bgp router-id [Link]
bgp log-neighbor-changes
network [Link] mask [Link]
network [Link] mask [Link]
neighbor [Link] remote-as 1000
neighbor [Link] remote-as 300

R3# show running-config | section bgp

router bgp 300
bgp router-id [Link]
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor [Link] remote-as 1000
neighbor [Link] remote-as 1000
neighbor [Link] remote-as 500
!
address-family ipv4
network [Link] mask [Link]
network [Link] mask [Link]
neighbor [Link] activate
neighbor [Link] activate
neighbor [Link] activate
exit-address-family
Close configuration window

Step 6: Verifying BGP operations.

a. To verify the BGP operation on R2, issue the show ip bgp command.
Open configuration window

R2# show 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, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
t secondary path, L long-lived-stale,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

Network Next Hop Metric LocPrf Weight Path

* [Link]/27 [Link] 0 300 1000 i
*> [Link] 0 0 1000 i
* [Link]/26 [Link] 0 300 1000 i
*> [Link] 0 0 1000 i
*> [Link]/27 [Link] 0 32768 i
*> [Link]/26 [Link] 0 32768 i
*> [Link]/27 [Link] 0 0 300 i
* [Link] 0 1000 300 i
*> [Link]/26 [Link] 0 0 300 i

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 8 of 18

-
 Lab - Implement eBGP for IPv4

* [Link] 0 1000 300 i

Questions:

What does the * at the beginning of an entry indicate?

Type your answers here.

What does the angle bracket (>) in an entry indicate?

Type your answers here.

What is the address of the preferred next hop router to reach the [Link]/27 network? Explain.
Type your answers here.

How can you verify that [Link] is the next hop router used to reach [Link]/27?
Type your answers here.

What does a next hop of [Link] indicate?

Type your answers here.

b. Use the show ip bgp ip-prefix command to display all the paths for a specific route and the BGP path
attributes for that route.
R2# show ip bgp [Link]
BGP routing table entry for [Link]/27, version 14
Paths: (2 available, best #2, table default)
Advertised to update-groups:
1
Refresh Epoch 2
300 1000
[Link] from [Link] ([Link])
Origin IGP, localpref 100, valid, external
rx pathid: 0, tx pathid: 0
Updated on Sep 23 2025 03:57:40 UTC
Refresh Epoch 1
1000
[Link] from [Link] ([Link])
Origin IGP, metric 0, localpref 100, valid, external, best
rx pathid: 0, tx pathid: 0x0
Updated on Sep 23 2025 02:24:24 UTC
Question:

What is the IPv4 address of the next hop router with the best path?
Type your answers here.

c. Examine the BGP neighbor relationships on R2 using the show ip bgp neighbors command.
R2# show ip bgp neighbors
BGP neighbor is [Link], remote AS 1000, external link
BGP version 4, remote router ID [Link]
BGP state = Established, up for 01:45:22
Last read 00:00:45, last write 00:00:06, hold time is 180, keepalive interval is 60
seconds

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 9 of 18

-
 Lab - Implement eBGP for IPv4

Last update received: 00:11:25

Neighbor sessions:
1 active, is not multisession capable (disabled)
Neighbor capabilities:
Route refresh: advertised and received(new)
Four-octets ASN Capability: advertised and received
Address family IPv4 Unicast: advertised and received
Enhanced Refresh Capability: advertised and received
Multisession Capability:
Stateful switchover support enabled: NO for session 1
Message statistics:
InQ depth is 0
OutQ depth is 0

Sent Rcvd
Opens: 1 1
Notifications: 0 0
Updates: 3 3
Keepalives: 116 118
Route Refresh: 0 0
Total: 120 122
<output omitted>

BGP neighbor is [Link], remote AS 300, external link

BGP version 4, remote router ID [Link]
BGP state = Established, up for 16:23:45
Last read 00:00:33, last write 00:00:51, hold time is 180, keepalive interval is 60
seconds
Last update received: 00:13:19
Neighbor sessions:
1 active, is not multisession capable (disabled)
Neighbor capabilities:
Route refresh: advertised and received(new)
Four-octets ASN Capability: advertised and received
Address family IPv4 Unicast: advertised and received
Enhanced Refresh Capability: advertised and received
Multisession Capability:
Stateful switchover support enabled: NO for session 1
Message statistics:
InQ depth is 0
OutQ depth is 0

Sent Rcvd
Opens: 1 1
Notifications: 0 0
Updates: 5 4
Keepalives: 17 16
Route Refresh: 0 0
Total: 25 23
Do log neighbor state changes (via global configuration)

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 10 of 18

-
 Lab - Implement eBGP for IPv4

Default minimum time between advertisement runs is 30 seconds

<output omitted>
Questions:

How many neighbors does R2 have and what are their router IDs?
Type your answers here.

What is the BGP state of both neighbors?

Type your answers here.

What are the keepalive and hold time value for both neighbors?
Type your answers here.

d. To further verify the state of the BGP session, enter the show ip bgp summary command.
For example, the BGP router ID for R2 is [Link] and the local AS number is 500. The BGP table is now
at version 7, and when the table is updated, this number will increase.
In the table, R2 has two established sessions with the neighbors, [Link] (R1 G0/0/0) in AS 1000 and
[Link] (R3 G0/0/0) in AS 300.
R1# show ip bgp summary
BGP router identifier [Link], local AS number 1000
BGP table version is 7, main routing table version 7
6 network entries using 1488 bytes of memory
14 path entries using 1904 bytes of memory
5/3 BGP path/bestpath attribute entries using 1480 bytes of memory
4 BGP AS-PATH entries using 128 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 5000 total bytes of memory
BGP activity 7/1 prefixes, 15/1 paths, scan interval 60 secs
6 networks peaked at 02:22:06 Sep 23 2025 UTC (00:12:29.428 ago)

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

[Link] 4 500 20 20 7 0 0 00:15:02 4
[Link] 4 300 20 22 7 0 0 00:12:29 4
[Link] 4 300 22 22 7 0 0 00:12:22 4

R2# show ip bgp summary

BGP router identifier [Link], local AS number 500
BGP table version is 9, main routing table version 7
6 network entries using 1488 bytes of memory
10 path entries using 1360 bytes of memory
5/3 BGP path/bestpath attribute entries using 1480 bytes of memory
4 BGP AS-PATH entries using 128 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 4456 total bytes of memory
BGP activity 8/2 prefixes, 12/2 paths, scan interval 60 secs
6 networks peaked at 02:22:05 Sep 23 2025 UTC (00:11:01.980 ago)

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 11 of 18

-
 Lab - Implement eBGP for IPv4

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

[Link] 4 1000 19 19 9 0 0 00:13:34 4
[Link] 4 300 20 21 9 0 0 00:10:55 4

R3# show ip bgp summary

BGP router identifier [Link], local AS number 300
BGP table version is 9, main routing table version 9
6 network entries using 1488 bytes of memory
14 path entries using 1904 bytes of memory
5/3 BGP path/bestpath attribute entries using 1480 bytes of memory
4 BGP AS-PATH entries using 128 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 5000 total bytes of memory
BGP activity 6/0 prefixes, 14/0 paths, scan interval 60 secs
6 networks peaked at 19:26:01 Sep 23 2025 UTC (00:22:12.895 ago)

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

[Link] 4 1000 33 31 9 0 0 00:22:12 4
[Link] 4 1000 32 33 9 0 0 00:22:05 4
[Link] 4 500 34 32 9 0 0 00:22:07 4
Close configuration window

Part 3: Configure and Verify Route Summarization and Atomic Aggregate

Step 1: Configure route summarization using atomic aggregate.
Summarizing prefixes conserves router resources and accelerates best-path calculation by reducing the size
of the table. Summarization can be configured either for prefixes originated by the AS or prefixes received
from downstream providers. Summarization also provides the benefits of stability by hiding flapping routes or
having to install new prefixes when they are contained within a summary.
Although AS 1000 only has two prefixes [Link]/27 and [Link]/26, this customer has been
allocated the entire [Link]/24 prefix. R3 in AS 300 has two prefixes [Link]/27 and [Link]/26
but has been allocated the entire [Link]/24 prefix.
Configure R1 and R3 to advertise a summary or aggregate route using the aggregate-address command.
The summary-only option suppresses the specific prefixes that are summarized from also being advertised.
Notice that this command is configured in address-family ipv4 configuration mode on R3.
Open configuration window

R1(config)# router bgp 1000

R1(config-router)# aggregate-address [Link] [Link] summary-only

R3(config)# router bgp 300

R3(config-router)# address-family ipv4
R3(config-router-af)# aggregate-address [Link] [Link] summary-only

Step 2: Verify route summarization using atomic aggregate.

a. Examine the routing tables on each router to verify the route summarization for the two prefixes. Verify
that R1 and R3 are each receiving the summary route from the other router. Verify that R2 is receiving
aggregate routes from both R1 and R3.
R1# show ip route bgp | begin Gateway
Gateway of last resort is not set

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 12 of 18

-
 Lab - Implement eBGP for IPv4

[Link]/24 is variably subnetted, 5 subnets, 4 masks

B [Link]/24 [200/0], 00:27:47, Null0
[Link]/24 is variably subnetted, 2 subnets, 2 masks
B [Link]/27 [20/0] via [Link], 13:34:31
B [Link]/26 [20/0] via [Link], 13:34:31
B [Link]/24 [20/0] via [Link], 00:26:01

R2# show ip route bgp | begin Gateway

Gateway of last resort is not set

B [Link]/24 [20/0] via [Link], 00:33:53

B [Link]/24 [20/0] via [Link], 00:32:08

R3# show ip route bgp | begin Gateway

Gateway of last resort is not set

B [Link]/24 [20/0] via [Link], 00:36:52

[Link]/24 is variably subnetted, 2 subnets, 2 masks
B [Link]/27 [20/0] via [Link], 02:10:48
B [Link]/26 [20/0] via [Link], 02:10:48
[Link]/24 is variably subnetted, 5 subnets, 4 masks
B [Link]/24 [200/0], 00:35:07, Null0
Question:

Why do R1 and R3 contain an entry with a next hop address of Null0? What is the result of having this
Null0 route in the routing table?
Type your answers here.

b. Examine the BGP table on router R2 to verify the route summarization. When a prefix has the default
classful mask, the subnet mask is not displayed. Both [Link] and [Link] prefixes have a /24
prefix length which would be the default mask for a Class C address.
R2# show ip bgp
BGP table version is 69, local router ID is [Link]
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
<output omitted>

Network Next Hop Metric LocPrf Weight Path

* [Link] [Link] 0 300 1000 i
*> [Link] 0 0 1000 i
*> [Link]/27 [Link] 0 32768 i
*> [Link]/26 [Link] 0 32768 i
* [Link] [Link] 0 1000 300 i
*> [Link] 0 0 300 i

c. Examine the BGP table on routers R2 and R3 and verify that each router is receiving the summary route
from the other router.
R1# show ip bgp
BGP table version is 69, local router ID is [Link]

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 13 of 18

-
 Lab - Implement eBGP for IPv4

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

<output omitted>

Network Next Hop Metric LocPrf Weight Path

s> [Link]/27 [Link] 0 32768 i
*> [Link] [Link] 32768 i
s> [Link]/26 [Link] 0 32768 i
* [Link]/27 [Link] 0 300 500 i
* [Link] 0 300 500 i
*> [Link] 0 0 500 i
* [Link]/26 [Link] 0 300 500 i
* [Link] 0 300 500 i
*> [Link] 0 0 500 i
* [Link] [Link] 0 500 300 i
* [Link] 0 0 300 i
*> [Link] 0 0 300 i

R3# show ip bgp

BGP table version is 22, local router ID is [Link]
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
t secondary path, L long-lived-stale,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

Network Next Hop Metric LocPrf Weight Path

* [Link] [Link] 0 500 1000 i
*> [Link] 0 0 1000 i
* [Link] 0 0 1000 i
* [Link]/27 [Link] 0 1000 500 i
* [Link] 0 1000 500 i
*> [Link] 0 0 500 i
* [Link]/26 [Link] 0 1000 500 i
* [Link] 0 1000 500 i
*> [Link] 0 0 500 i
s> [Link]/27 [Link] 0 32768 i
*> [Link] [Link] 32768 i
s> [Link]/26 [Link] 0 32768 i
Question:

Why do two of the entries have the status code of "s"? Specifically, this is the result of what command or
option that was configured on these two routers?
Type your answers here.

d. Examine the explicit [Link] prefix entry in R2's BGP table. The route's NLRI information indicates
that the route was aggregated in AS 1000 by router with the RID [Link].
R2# show ip bgp [Link]
BGP routing table entry for [Link]/24, version 45
Paths: (2 available, best #2, table default)

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 14 of 18

-
 Lab - Implement eBGP for IPv4

Advertised to update-groups:
1
Refresh Epoch 2
300 1000, (aggregated by 1000 [Link])
[Link] from [Link] ([Link])
Origin IGP, localpref 100, valid, external, atomic-aggregate
rx pathid: 0, tx pathid: 0
Updated on Sep 23 2025 04:14:33 UTC
Refresh Epoch 1
1000, (aggregated by 1000 [Link])
[Link] from [Link] ([Link])
Origin IGP, metric 0, localpref 100, valid, external, atomic-aggregate, best
rx pathid: 0, tx pathid: 0x0
Updated on Sep 23 2025 04:14:03 UTC
Close configuration window

Part 4: Configure and Verify Route Summarization with Atomic Aggregate and
AS-Set
Step 1: Configure route summarization using atomic aggregate and AS-Set.
a. Shut down both serial interfaces on R1. This will create a single path from R1 (AS 1000) to R2 (AS 500)
to R3 (AS 300).
Open configuration window

R1(config)# interface s0/1/0

R1(config-if)# shutdown
R1(config-if)# exit
R1(config)# interface s0/1/1
R1(config-if)# shutdown
b. Remove route aggregation previously configured on R1.
R1(config)# router bgp 1000
R1(config-router)# no aggregate-address [Link] [Link] summary-
only
c. Verify that R3 is now receiving the non-summarized prefixes [Link]/27 and [Link]/26.
R3# show ip route [Link]
Routing entry for [Link]/24, 2 known subnets
Variably subnetted with 2 masks
B [Link]/27 [20/0] via [Link], 00:01:26
B [Link]/26 [20/0] via [Link], 00:01:26

d. On R2, summarize the prefixes [Link]/27 and [Link]/26 received from R1 as [Link]/24.
R2(config)# router bgp 500
R2(config-router)# aggregate-address [Link] [Link] summary-only
Close configuration window

Step 2: Verify route summarization using atomic aggregate and AS-Set.

a. Verify that R3 is receiving the aggregated prefix [Link]/24.
Open configuration window

R3# show ip route bgp | begin Gateway

Gateway of last resort is not set

B [Link]/24 [20/0] via [Link], 00:00:51

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 15 of 18

-
 Lab - Implement eBGP for IPv4

[Link]/24 is variably subnetted, 2 subnets, 2 masks

B [Link]/27 [20/0] via [Link], 08:46:37
B [Link]/26 [20/0] via [Link], 08:46:37
[Link]/24 is variably subnetted, 5 subnets, 4 masks
B [Link]/24 [200/0], 08:46:07, Null0

b. Examine R3's BGP table. Notice that the AS path only includes the AS that summarized the route, AS
500, router R2.
R3# show ip bgp
<output omitted>

Network Next Hop Metric LocPrf Weight Path

*> [Link] [Link] 0 0 500 i
*> [Link]/27 [Link] 0 0 500 i
*> [Link]/26 [Link] 0 0 500 i
s> [Link]/27 [Link] 0 32768 i
*> [Link] [Link] 32768 i
s> [Link]/26 [Link] 0 32768 i

c. Issue the show ip bgp summary command. The BGP session between R1 and R3 is in the idle state
and is not attempting to form a connection. The output confirms that serial link between R1 and R3 are
down because the serial interfaces on R1 were shut down in a previous step in this activity.
R3# show ip bgp summary
BGP router identifier [Link], local AS number 300
BGP table version is 26, main routing table version 26
6 network entries using 1488 bytes of memory
6 path entries using 816 bytes of memory
4/4 BGP path/bestpath attribute entries using 1184 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 3512 total bytes of memory
BGP activity 11/5 prefixes, 21/15 paths, scan interval 60 secs
8 networks peaked at 19:51:01 Sep 23 2025 UTC (00:12:45.846 ago)

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

[Link] 4 1000 0 0 1 0 0 00:02:30 Idle
[Link] 4 1000 0 0 1 0 0 00:02:28 Idle
[Link] 4 500 59 55 26 0 0 00:37:39 3

d. On R2, remove the current route aggregation for the [Link]/24 prefix and configure it again, this
time using the as-set option.
R2(config)# router bgp 500
R2(config-router)# no aggregate-address [Link] [Link] summary-
only
R2(config-router)# aggregate-address [Link] [Link] as-set
summary-only
e. Verify that R3 is receiving the aggregated prefix [Link]/24.
R3# show ip route bgp | begin Gateway
Gateway of last resort is not set

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 16 of 18

-
 Lab - Implement eBGP for IPv4

B [Link]/24 [20/0] via [Link], 00:01:35

[Link]/24 is variably subnetted, 2 subnets, 2 masks
B [Link]/27 [20/0] via [Link], 08:50:02
B [Link]/26 [20/0] via [Link], 08:50:02
[Link]/24 is variably subnetted, 5 subnets, 4 masks
B [Link]/24 [200/0], 08:49:32, Null0

f. Examine R3's BGP table again. Notice that the entry for [Link] this time includes the entire AS path.
The output from the show ip bgp [Link] command displays both AS numbers and identifies that R2
([Link]) aggregated the route.
R3# show ip bgp
<output omitted>
Network Next Hop Metric LocPrf Weight Path
*> [Link] [Link] 0 0 500 {1000} i
*> [Link]/27 [Link] 0 0 500 i
*> [Link]/26 [Link] 0 0 500 i
s> [Link]/27 [Link] 0 32768 i
*> [Link] [Link] 32768 i
s> [Link]/26 [Link] 0 32768 i

R3# show ip bgp [Link] | begin Refresh

Refresh Epoch 2
500 {1000}, (aggregated by 500 [Link])
[Link] from [Link] ([Link])
Origin IGP, metric 0, localpref 100, valid, external, best
rx pathid: 0, tx pathid: 0x0
Updated on Sep 23 2025 04:33:22 UTC
Close configuration window

Part 5: Configure and Verify the Advertising of a Default Route

Step 1: Configure default route advertisement on R2.
Configure R2 to advertise a default router to R1. R2 does not necessarily have to have a default route of its
own. Core internet routers that have full internet routing tables and do not require a default route are referred
to as being in a default-free zone (DFZ).
Open configuration window

R2(config)# router bgp 500

R2(config-router)# neighbor [Link] default-originate

Step 2: Verify default route advertisement on R1.

a. Examine R1's routing table to verify that it has received a default route.
Note: This will take a few minutes to converge.
R1# show ip route bgp | begin Gateway
Gateway of last resort is [Link] to network [Link]

B* [Link]/0 [20/0] via [Link], 00:00:37

[Link]/24 is variably subnetted, 2 subnets, 2 masks
B [Link]/27 [20/0] via [Link], 21:24:43
B [Link]/26 [20/0] via [Link], 21:24:43
B [Link]/24 [20/0] via [Link], 12:41:58

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 17 of 18

-
 Lab - Implement eBGP for IPv4

b. Examine R1's BGP table to verify that it has received a default route.
R1# show ip bgp
<output omitted>

Network Next Hop Metric LocPrf Weight Path

*> [Link] [Link] 0 500 i
*> [Link]/27 [Link] 0 32768 i
*> [Link]/26 [Link] 0 32768 i
*> [Link]/27 [Link] 0 0 500 i
*> [Link]/26 [Link] 0 0 500 i
*> [Link] [Link] 0 500 300 i
Close configuration window
End of document

© 2019 - 2026 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 18 of 18