BGP Lab

Objectives
 Configure EBGP and IBGP.

 Configure EIGRP in the ITA domain.
 Troubleshoot and resolve next hop issues in IBGP.
 Configure full-mesh IBGP to resolve routing issue within ITA
domain.
 Configure ITA so it is not a transit AS.
 Verify connectivity.
Step 0: Suggested starting configurations.

a. Apply the following configuration to each router along with the
appropriate hostname. The exec-timeout 0 0 command should only be
used in a lab environment.
Router(config)# no ip domain-lookup
Router(config)# line con 0
Router(config-line)# logging synchronous
Router(config-line)# exec-timeout 0 0
Step 1: Configure interface addresses on all

routers and EBGP on ISP1.
a. Using the addressing scheme in the diagram, create the
loopback interfaces and apply IPv4 addresses to these and the
serial interfaces on ISP (R1), SanJose1 (R2), and SanJose2 (R3).
Router R1 (hostname ISP1)
ISP(config)# interface Loopback0
ISP(config-if)# ip address 10.0.0.1 255.255.255.0
ISP(config-if)# exit
ISP(config)# interface GigabitEthernet0/0
ISP(config-if)# no shutdown
ISP(config)# interface Serial0/0/0
ISP(config-if)# clock rate 64000
ISP(config)# router bgp 65100

ISP(config-router)# bgp router-id 1.0.0.1
ISP(config-router)# neighbor 192.168.1.2 remote-as 65000
ISP(config-router)# network 10.1.0.0 mask 255.255.0.0
ISP(config-router)#
ISP1 has an EBGP peering session with SanJose1. ISP1 is

advertising the 10.1.0.0/16 network. A similar BGP configuration
is assumed on ISP2, which does not physically exist in this lab
topology.
Router R2 (hostname SanJose1)
SanJose1(config)# interface Loopback0
SanJose1(config-if)# ip address 172.17.2.1 255.255.255.0
SanJose1(config-if)# exit
SanJose1(config)# interface GigabitEthernet0/0
SanJose1(config-if)# no shutdown
SanJose1(config)# interface Serial0/0/0
SanJose1(config-if)# clock rate 64000
SanJose1(config-if)#

CCNP ROUTE Chapter 7 Lab 7-4, IBGP, Next
Hop and Synchronization (Version 7)
May 23, 2019 Last Updated: May 23, 2019 CCNP ROUTE LAB No Comments
Share TweetSharePin it
Topology
Objectives
 Configure EBGP and IBGP.
 Configure EIGRP in the ITA domain.
 Troubleshoot and resolve next hop issues in IBGP.
 Configure full-mesh IBGP to resolve routing issue within ITA
domain.
 Configure ITA so it is not a transit AS.
 Verify connectivity.
Background
The International Travel Agency (ITA) runs BGP on its SanJose1
and SanJose3 routers in AS 65000. SanJose1 in AS 65000 is
running EBGP with the ISP1 router in AS 65100. SanJose3 in AS
65000 is running EBGP with the ISP2 router in AS 65200. ITA
routers need to receive IPv4 networks from both ISPs. To ensure
AS 65000 is not a transit AS, SanJose1 and SanJose3 will only
include ITA networks 172.16.2.0/24 and 172.16.4.0/24 in its BGP
updates to the ISP routers. Your job is to configure EIGRP BGP
for this internetwork.
Note: The topology shows SanJose3 in AS 65000 is running EBGP

with the ISP2 router in AS 65200. ISP2 (router R5) does not
actually exist in the physical lab topology. This is done due to
the limitations of four routers in our CCNP NetLab topologies.
Note: This lab uses Cisco 1941 routers with Cisco IOS Release
15.4 with IP Base. The switches are Cisco WS-C2960-24TT-L with
Fast Ethernet interfaces, therefore the router will use routing
metrics associated with a 100 Mb/s interface. Depending on the
router or switch model and Cisco IOS Software version, the
commands available and output produced might vary from what
is shown in this lab.
Required Resources
 4 routers (Cisco IOS Release 15.2 or comparable)
 4 switches (LAN interfaces)
 Serial and Ethernet cables
Step 0: Suggested starting configurations.

a. Apply the following configuration to each router along with the
appropriate hostname. The exec-timeout 0 0 command should only be
used in a lab environment.
Router(config)# no ip domain-lookup
Router(config)# line con 0
Router(config-line)# logging synchronous
Router(config-line)# exec-timeout 0 0
Step 1: Configure interface addresses on all

routers and EBGP on ISP1.
a. Using the addressing scheme in the diagram, create the
loopback interfaces and apply IPv4 addresses to these and the
serial interfaces on ISP (R1), SanJose1 (R2), and SanJose2 (R3).
Router R1 (hostname ISP1)
ISP(config)# interface Loopback0
ISP(config)# interface GigabitEthernet0/0
ISP(config)# interface Serial0/0/0
ISP(config-if)# clock rate 64000
ISP(config)# router bgp 65100
ISP(config-router)# bgp router-id 1.0.0.1
ISP(config-router)# neighbor 192.168.1.2 remote-as 65000
ISP(config-router)# network 10.1.0.0 mask 255.255.0.0
ISP(config-router)#
ISP1 has an EBGP peering session with SanJose1. ISP1 is

advertising the 10.1.0.0/16 network. A similar BGP configuration
is assumed on ISP2, which does not physically exist in this lab
topology.

Step 2: Configure EIGRP on ITA routers.

Configure EIGRP on the SanJose1, SanJose2, and SanJose3
routers. Both routers should be able to ping the other router’s
LAN and loopback interfaces. (Note: If using an IOS prior to 15.0,
use the no auto-summary router configuration command to
disable automatic summarization. This command is the default
beginning with IOS 15.)
Configure EIGRP for IPv4 and IPv6 on SanJose1.
SanJose1(config)# router eigrp 1
SanJose1(config-router)# eigrp router-id 1.1.1.1
SanJose1(config-router)# network 172.16.0.0

Use ping to test the reachability between the ITA routers. For
example, SanJose3’s G0/0 interface should be able to ping
SanJose1’s G0/0 interface.
SanJose3# ping 172.16.2.0 source gig 0/0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.2.0, timeout is 2

seconds:
Packet sent with a source address of 172.16.4.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max =

52/55/56 ms
SanJose3#
Step 3: Configure BGP on SanJose1 and

SanJose3.
d. On SanJose1, configure EBGP to peer with ISP1. ISP1 has
already been configured to peer with SanJose1. Configure
SanJose1 to IBGP peer with SanJose3 using its loopback0
address. SanJose1 will be advertising the 172.16.2.0/24 network
in BGP.
SanJose1(config)# router bgp 65000
SanJose1(config-router)# bgp router-id 1.1.1.1
SanJose1(config-router)# neighbor 192.168.1.1 remote-as

65100
SanJose1(config-router)# neighbor 172.17.4.1 remote-as 65000
SanJose1(config-router)# neighbor 172.17.4.1 update-source

Loopback0
SanJose1(config-router)# network 172.16.2.0 mask

255.255.255.0
SanJose1(config-router)#
Configure SanJose3 to IBGP peer with SanJose1 using its

loopback0 address. SanJose3 will be advertising the
172.16.4.0/24 network in BGP.
SanJose3(config-router)# bgp router-id 3.3.3.3
SanJose3(config-router)# neighbor 172.17.2.1 remote-as 65000
SanJose3(config-router)# neighbor 172.17.2.1 update-source

Loopback0
SanJose3(config-router)# network 172.16.4.0 mask

255.255.255.0
Step 4: Verify BGP on SanJose1.
f. Examine SanJose1’s BGP table using the show ip bgp command.
SanJose1# show ip bgp
BGP table version is 7, 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, m multipath, b backup-

path, f RT-Filter,
x best-external, a additional-path, c RIB-

compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf

Weight Path
*> 10.1.0.0/16 192.168.1.1 0

0 65100 i
*> 172.16.2.0/24 0.0.0.0 0

32768 i
r>i 172.16.4.0/24 172.17.4.1 0 100

0 i
SanJose1#
Examine Notice that there are three entries in SanJose1’s BGP

table.
 10.1.0.0/16 – The status codes “*>” indicate that this network
is reachable using the next hop IPaddress 192.168.1.1.
 172.16.2.0/24 – The status codes “*>” indicate that this
network is reachable. The next hop address 0.0.0.0 indicates
that this router is originating the network.
 172.16.4.0/24 – The status “r>i” indicate that this network is
reachable. The “r” indicates a RIB failure and the “i” means
this entry was learned via IBGP.
Why is there a RIB failure for the 172.16.4.0/24 network? What
command would help you determine the cause?
Use the show ip bgp rib-failure command to examine the cause of the
RIB failure.
SanJose1# show ip bgp rib-failure
Network Next Hop RIB-

failure RIB-NH Matches
172.16.4.0/24 172.17.4.1 Higher admin distance

n/a
SanJose1#
As you might have answer in the previous question, the RIB

failure is due to SanJose1 having a better routing source to this
destination. SanJose routers are using EIGRP to share internal
ITA networks. IBGP has a higher administrative distance (200)
than EIGRP (90), so the EIGRP router is preferred.
h. Verify SanJose1’s routing table using the show ip

route command.
SanJose1# show ip route
Codes: L - local, 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, H -

NHRP, l - LISP
a - application route
+ - replicated route, % - next hop ov
Gateway of last resort is not set
10.0.0.0/16 is subnetted, 1 subnets
B 10.1.0.0 [20/0] via 192.168.1.1, 00:14:14
172.16.0.0/16 is variably subnetted, 7 subnets, 3

masks
C 172.16.1.0/30 is directly connected, Serial0/0/1
L 172.16.1.1/32 is directly connected, Serial0/0/1
D 172.16.1.4/30 [90/2681856] via 172.16.1.2,

00:30:41, Serial0/0/1
C 172.16.2.0/24 is directly connected,

GigabitEthernet0/0
L 172.16.2.1/32 is directly connected,

GigabitEthernet0/0
D 172.16.3.0/24 [90/2172416] via 172.16.1.2,
00:30:41, Serial0/0/1
D 172.16.4.0/24 [90/2684416] via 172.16.1.2,

00:29:42, Serial0/0/1

masks
C 172.17.2.0/24 is directly connected, Loopback0
L 172.17.2.1/32 is directly connected, Loopback0
D 172.17.3.0/24 [90/2297856] via 172.16.1.2,

00:30:41, Serial0/0/1
D 172.17.4.0/24 [90/2809856] via 172.16.1.2,

00:29:42, Serial0/0/1

masks
SanJose1#
Notice that SanJose1 has a BGP route to 10.1.0.0/16 on ISP1 and

an EIGRP route to the 172.16.4.0/24 network on SanJose3.
i. Verify SanJose1’s reachability to 10.1.0.0/16 on ISP1.
SanJose1# ping 10.1.0.1

seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max =

24/27/28 ms
SanJose1#
Step 5: Examine and troubleshoot IBGP next hop

reachability on SanJose3.

mobile, B - BGP

inter area

external type 2

- IS-IS level-2


NHRP, l - LISP
+ - replicated route, % - next hop override

masks
D 172.16.1.0/30 [90/2681856] via 172.16.1.5,
01:00:03, Serial0/0/0
D 172.16.2.0/24 [90/2684416] via 172.16.1.5,

01:00:03, Serial0/0/0
D 172.16.3.0/24 [90/2172416] via 172.16.1.5,

01:00:03, Serial0/0/0

GigabitEthernet0/0

GigabitEthernet0/0

masks
D 172.17.2.0/24 [90/2809856] via 172.16.1.5,

01:00:03, Serial0/0/0
D 172.17.3.0/24 [90/2297856] via 172.16.1.5,

01:00:03, Serial0/0/0
SanJose3#
Notice that SanJose3 does not include a route to the 10.1.0.0/16

network on ISP1.
b. Examine the BGP table on SanJose3 using the show ip bgp

command to try and determine the reason why the 10.1.0.0/16
network is not in its routing table.

best, i - internal,

path, f RT-Filter,

compressed,

Weight Path
* i 10.1.0.0/16 192.168.1.1 0 100

0 65100 i
r>i 172.16.2.0/24 172.17.2.1 0 100

0 i
*> 172.16.4.0/24 0.0.0.0 0

32768 i
SanJose3#
The output shows that the 10.1.0.0/16 network is in the BGP

table but is missing the “>” status code indicating that it is not
being offered to the IP routing table. The next hop address used
for this route is 192.168.1.1. SanJose3’s routing table in Step 3a
shows that SanJose3 does not have a route to this next hop
address. If the router does not have a route to the next hop
address then the route will not be included in the IP routing
table.
In routing, the term “next hop” does not always mean the next
hop is a physically adjacent interface. The next hop, as in this
case, can be more than one router away.
BGP specifies that routes learned through IBGP are never
propagated to other IBGP peers. SanJose1 has learned via EBGP
about the 10.1.0.0/16 network from ISP1 with a next hop address
of 192.168.1.1, the IP address of ISP1. SanJose1 uses this same
next hop address of 192.168.1.1 in its IBGP update to SanJose3.
What are two solutions to this problem?

________________________________________________________________
c. The decision is made to modify the behavior on SanJose1 so

that it uses its loopback0 interface as the next hop address in its
IBGP updates.
SanJose1(config-router)# neighbor 172.17.4.1 next-hop-self
Note: For consistency, a similar configuration for SanJose3 is

shown. You do not need to configure this. This would need to be
done if ISP2 router actually existed in our lab topology.
SanJose3(config-router)# neighbor 172.17.2.1 next-hop-self
d. Re-examine the BGP table on SanJose3 using the show ip

bgp command to see if SanJose3 now has a valid next hop to the
10.1.0.0/16 network.

best, i - internal,

path, f RT-Filter,
compressed,

Weight Path
*>i 10.1.0.0/16 172.17.2.1 0 100

0 65100 i
r>i 172.16.2.0/24 172.17.2.1 0 100

0 i
*> 172.16.4.0/24 0.0.0.0 0

32768 i
SanJose3#
Notice that the next hope address has been changed to

SanJose1’s loopback0 address 172.17.2.1 which is reachable
because it being advertised in EIGRP updates from SanJose1.
e. Re-examine the routing table on SanJose3 using the show ip

route command to see if SanJose3 now has a route to the
10.1.0.0/16 network.

mobile, B - BGP

inter area

external type 2

- IS-IS level-2


NHRP, l - LISP
+ - replicated route, % - next hop override
10.0.0.0/16 is subnetted, 1 subnets
B 10.1.0.0 [200/0] via 172.17.2.1, 00:03:17

masks
D 172.16.1.0/30 [90/2681856] via 172.16.1.5,

01:26:06, Serial0/0/0
D 172.16.2.0/24 [90/2684416] via 172.16.1.5,

01:26:06, Serial0/0/0
D 172.16.3.0/24 [90/2172416] via 172.16.1.5,

01:26:06, Serial0/0/0

GigabitEthernet0/0

GigabitEthernet0/0
masks
D 172.17.2.0/24 [90/2809856] via 172.16.1.5,

01:26:06, Serial0/0/0
D 172.17.3.0/24 [90/2297856] via 172.16.1.5,

01:26:06, Serial0/0/0
SanJose3#
f. In the previous output, SanJose3 shows a route to the

10.1.0.0/16 network. Verify reachability to this network by
pinging ISP1’s G0/0 interface.
SanJose3# ping 10.1.0.1

seconds:
U.U.U
Success rate is 0 percent (0/5)
SanJose3#
Notice that the ping was not successful. One reason is because
SanJose3 is not advertising the network used as the source IP
address in the ping, the 172.16.1.4/30 network.
SanJose3 is advertising its 172.16.4.0/24 network in its BGP

updates using the network command in its initial BGP
configuration. Use the ping command changing the source IP
address for the ping to use SanJose3’s G0/0 IP address
172.16.4.1.
SanJose3# ping 10.1.0.1 source gig 0/0

seconds:
Packet sent with a source address of 172.16.4.1
U.U.U
Success rate is 0 percent (0/5)
SanJose3#
Even with the correct source IP address the ping does not
succeed.
Even though SanJose3 has a route to ISP1’s 10.1.0.0/16 network,

why do the pings from SanJose3 fail to 10.1.0.1?
______________________________________

BGP Lab

Uploaded by

Copyright:

Available Formats

BGP Lab

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BGP Lab

Uploaded by

Copyright:

Available Formats

Objectives

 Configure EBGP and IBGP.

Step 0: Suggested starting configurations.

Router(config)# line con 0

Router(config-line)# logging synchronous

Step 1: Configure interface addresses on all

ISP(config-if)# ip address 10.0.0.1 255.255.255.0

ISP(config)# interface GigabitEthernet0/0

ISP(config-if)# ip address 10.1.0.1 255.255.0.0

ISP(config)# interface Serial0/0/0

ISP(config-if)# ip address 192.168.1.1 255.255.255.252

ISP(config-if)# clock rate 64000

ISP(config)# router bgp 65100

ISP(config-router)# neighbor 192.168.1.2 remote-as 65000

ISP(config-router)# network 10.1.0.0 mask 255.255.0.0

ISP1 has an EBGP peering session with SanJose1. ISP1 is

SanJose1(config-if)# ip address 172.17.2.1 255.255.255.0

SanJose1(config)# interface GigabitEthernet0/0

SanJose1(config-if)# ip address 172.16.2.1 255.255.255.0

SanJose1(config)# interface Serial0/0/0

SanJose1(config-if)# ip address 192.168.1.2 255.255.255.252

SanJose1(config)# interface Serial0/0/1

SanJose1(config-if)# ip address 172.16.1.1 255.255.255.252

SanJose1(config-if)# clock rate 64000

Router R3 (hostname SanJose2)

SanJose2(config-if)# ip address 172.17.3.1 255.255.255.0

SanJose2(config)# interface GigabitEthernet0/0

SanJose2(config-if)# ip address 172.16.3.1 255.255.255.0

SanJose2(config)# interface Serial0/0/1

SanJose2(config-if)# ip address 172.16.1.2 255.255.255.252

SanJose2(config)# interface Serial0/1/0

SanJose2(config-if)# ip address 172.16.1.5 255.255.255.252

SanJose2(config-if)# clock rate 64000

Note: The topology shows SanJose3 in AS 65000 is running EBGP

Step 0: Suggested starting configurations.

Router(config)# line con 0

Router(config-line)# logging synchronous

Step 1: Configure interface addresses on all

ISP(config)# interface Loopback0

ISP(config-if)# ip address 10.0.0.1 255.255.255.0

ISP(config)# interface GigabitEthernet0/0

ISP(config-if)# ip address 10.1.0.1 255.255.0.0

ISP(config)# interface Serial0/0/0

ISP(config-if)# ip address 192.168.1.1 255.255.255.252

ISP(config-if)# clock rate 64000

ISP(config-router)# bgp router-id 1.0.0.1

ISP(config-router)# neighbor 192.168.1.2 remote-as 65000

ISP(config-router)# network 10.1.0.0 mask 255.255.0.0

ISP1 has an EBGP peering session with SanJose1. ISP1 is

SanJose1(config)# interface Loopback0

SanJose1(config-if)# ip address 172.17.2.1 255.255.255.0

SanJose1(config)# interface GigabitEthernet0/0

SanJose1(config-if)# ip address 172.16.2.1 255.255.255.0

SanJose1(config)# interface Serial0/0/0

SanJose1(config-if)# ip address 192.168.1.2 255.255.255.252

SanJose1(config)# interface Serial0/0/1

SanJose1(config-if)# ip address 172.16.1.1 255.255.255.252

SanJose1(config-if)# clock rate 64000

Router R3 (hostname SanJose2)