0% found this document useful (0 votes)

83 views22 pages

Chapter 7 Lab 7-3,: Configuring IBGP and EBGP Sessions, Local Preference, and MED

Uploaded by

LuisdeLeón

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

83 views22 pages

Chapter 7 Lab 7-3,: Configuring IBGP and EBGP Sessions, Local Preference, and MED

Uploaded by

LuisdeLeón

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

Configuring IBGP and EBGP Sessions
Advanced BGP Features

CCNPv7 ROUTE

Chapter 7 Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and
MED
Topology

Objectives
 For IBGP peers to correctly exchange routing information, use the next-hop-self command with the Local-
Preference and MED attributes.
 Ensure that the flat-rate, unlimited-use T1 link is used for sending and receiving data to and from the AS 200
on ISP and that the metered T1 only be used in the event that the primary T1 link has failed.

Background
The International Travel Agency runs BGP on its SanJose1 and SanJose2 routers externally with the ISP router in AS
200. IBGP is run internally between SanJose1 and SanJose2. Your job is to configure both EBGP and IBGP for this

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

internetwork to allow for redundancy. The metered T1 should only be used in the event that the primary T1 link has
failed. Traffic sent across the metered T1 link offers the same bandwidth of the primary link but at a huge expense.
Ensure that this link is not used unnecessarily.
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
 3 routers (Cisco IOS Release 15.2 or comparable)
 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.

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 ISP)
ISP(config)# interface Loopback0
ISP(config-if)# ip address [Link] [Link]
ISP(config-if)# exit
ISP(config)# interface Serial0/0/0
ISP(config-if)# ip address [Link] [Link]
ISP(config-if)# clock rate 128000
ISP(config-if)# no shutdown
ISP(config-if)# exit
ISP(config)# interface Serial0/0/1
ISP(config-if)# ip address [Link] [Link]
ISP(config-if)# no shutdown
ISP(config-if)# end
ISP#
Router R2 (hostname SanJose1)
SanJose1(config)# interface Loopback0
SanJose1(config-if)# ip address [Link] [Link]
SanJose1(config-if)# exit
SanJose1(config)# interface Serial0/0/0
SanJose1(config-if)# ip address [Link] [Link]
SanJose1(config-if)# no shutdown
SanJose1(config-if)# exit
SanJose1(config)# interface Serial0/0/1
SanJose1(config-if)# ip address [Link] [Link]
SanJose1(config-if)# clock rate 128000
SanJose1(config-if)# no shutdown
SanJose1(config-if)# end

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

SanJose1#

Router R3 (hostname SanJose2)

SanJose2(config)# interface Loopback0
SanJose2(config-if)# ip address [Link] [Link]
SanJose2(config-if)# exit
SanJose2(config)# interface Serial0/0/0
SanJose2(config-if)# ip address [Link] [Link]
SanJose2(config-if)# clock rate 128000
SanJose2(config-if)# no shutdown
SanJose2(config-if)# exit
SanJose2(config)# interface Serial0/0/1
SanJose2(config-if)# ip address [Link] [Link]
SanJose2(config-if)# no shutdown
SanJose2(config-if)# end
SanJose2#
b. Use ping to test the connectivity between the directly connected routers. Both SanJose routers should be able to
ping each other and their local ISP serial link IP address. The ISP router cannot reach the segment between
SanJose1 and SanJose2.

Step 2: Configure EIGRP.

Configure EIGRP between the SanJose1 and SanJose2 routers. (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.)
SanJose1(config)# router eigrp 1
SanJose1(config-router)# network [Link]

SanJose2(config)# router eigrp 1

SanJose2(config-router)# network [Link]

Step 3: Configure IBGP and verify BGP neighbors.

a. Configure IBGP between the SanJose1 and SanJose2 routers. On the SanJose1 router, enter the following
configuration.
SanJose1(config)# router bgp 64512
SanJose1(config-router)# neighbor [Link] remote-as 64512
SanJose1(config-router)# neighbor [Link] update-source lo0
If multiple pathways to the BGP neighbor exist, the router can use multiple IP interfaces to communicate with the
neighbor. The source IP address therefore depends on the outgoing interface. The update-source lo0 command
instructs the router to use the IP address of the interface Loopback0 as the source IP address for all BGP
messages sent to that neighbor.
b. Complete the IBGP configuration on SanJose2 using the following commands.
SanJose2(config)# router bgp 64512
SanJose2(config-router)# neighbor [Link] remote-as 64512
SanJose2(config-router)# neighbor [Link] update-source lo0
c. Verify that SanJose1 and SanJose2 become BGP neighbors by issuing the show ip bgp neighbors command
on SanJose1. View the following partial output. If the BGP state is not established, troubleshoot the connection.
SanJose2# show ip bgp neighbors
BGP neighbor is [Link], remote AS 64512, internal link
BGP version 4, remote router ID [Link]

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

BGP state = Established, up for [Link]

Last read [Link], last write [Link], hold time is 180, keepalive interval is
60 seconds
<output omitted>
The link between SanJose1 and SanJose2 should be identified as an internal link indicating an IBGP peering
relationship, as shown in the output.

Step 4: Configure EBGP and verify BGP neighbors.

a. Configure ISP to run EBGP with SanJose1 and SanJose2. Enter the following commands on ISP.
ISP(config)# router bgp 200
ISP(config-router)# neighbor [Link] remote-as 64512
ISP(config-router)# neighbor [Link] remote-as 64512
ISP(config-router)# network [Link]
Because EBGP sessions are almost always established over point-to-point links, there is no reason to use the
update-source keyword in this configuration. Only one path exists between the peers. If this path goes down,
alternative paths are not available.
b. Configure a discard static route for the [Link]/16 network. Any packets that do not have a more specific
match (longer match) for a [Link] subnet will be dropped instead of sent to the ISP. Later in this lab we will
configure a default route to the ISP.
SanJose1(config)# ip route [Link] [Link] null0
c. Configure SanJose1 as an EBGP peer to ISP.
SanJose1(config)# router bgp 64512
SanJose1(config-router)# neighbor [Link] remote-as 200
SanJose1(config-router)# network [Link]
d. Use the show ip bgp neighbors command to verify that SanJose1 and ISP have reached the established state.
Troubleshoot if necessary.
SanJose1# show ip bgp neighbors
BGP neighbor is [Link], remote AS 64512, internal link
BGP version 4, remote router ID [Link]
BGP state = Established, up for [Link]
<output omitted>

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

BGP version 4, remote router ID [Link]
BGP state = Established, up for [Link]
Last read [Link], last write [Link], hold time is 180, keepalive interval is
60 seconds
<output omitted>
Notice that the “external link” indicates that an EBGP peering session has been established. You should also see
an informational message indicating the establishment of the BGP neighbor relationship.
*Sep 8 [Link].699: %BGP-5-ADJCHANGE: neighbor [Link] Up
e. Configure a discard static route for [Link]/16 on SanJose2 and as an EBGP peer to ISP.
SanJose2(config)# ip route [Link] [Link] null0
SanJose2(config)# router bgp 64512
SanJose2(config-router)# neighbor [Link] remote-as 200
SanJose2(config-router)# network [Link]

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

Step 5: View BGP summary output.

In Step 4, the show ip bgp neighbors command was used to verify that SanJose1 and ISP had reached the
established state. A useful alternative command is show ip bgp summary. The output should be similar to the
following.
SanJose2# show ip bgp summary
BGP router identifier [Link], local AS number 64512
BGP table version is 6, main routing table version 6
2 network entries using 288 bytes of memory
4 path entries using 320 bytes of memory
4/2 BGP path/bestpath attribute entries using 640 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 1272 total bytes of memory
BGP activity 2/0 prefixes, 4/0 paths, scan interval 60 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down

State/PfxRcd
[Link] 4 64512 27 26 6 0 0 [Link] 2
[Link] 4 200 10 7 6 0 0 [Link] 1
SanJose2#

Step 6: Verify which path the traffic takes.

f. Clear the IP BGP conversation with the clear ip bgp * command on ISP. Wait for the conversations to reestablish
with each SanJose router.
ISP# clear ip bgp *
ISP#
*Nov 9 [Link].427: %BGP-5-ADJCHANGE: neighbor [Link] Down User reset
*Nov 9 [Link].427: %BGP_SESSION-5-ADJCHANGE: neighbor [Link] IPv4 Unicast
topology base removed from session User reset
*Nov 9 [Link].427: %BGP-5-ADJCHANGE: neighbor [Link] Down User reset
*Nov 9 [Link].427: %BGP_SESSION-5-ADJCHANGE: neighbor [Link] IPv4 Unicast
topology base removed from session User reset
*Nov 9 [Link].851: %BGP-5-ADJCHANGE: neighbor [Link] Up
*Nov 9 [Link].851: %BGP-
ISP#5-ADJCHANGE: neighbor [Link] Up
ISP#
g. Test whether ISP can ping the loopback 0 address of [Link] on SanJose1 and the serial link between
SanJose1 and SanJose2, [Link].
ISP# ping [Link]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
ISP#
ISP# ping [Link]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

ISP#
h. Now ping from ISP to the loopback 0 address of [Link] on SanJose2 and the serial link between SanJose1
and SanJose2, [Link].
ISP# ping [Link]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/14/16 ms
ISP# ping [Link]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/13/16 ms
ISP#
You should see successful pings to each IP address on SanJose2 router. Ping attempts to [Link] and
[Link] should fail. Why does this happen?
_______________________________________________________________________________
_______________________________________________________________________________
i. Issue the show ip bgp command on ISP to verify BGP routes and metrics.
ISP# show ip bgp
BGP table version is 3, 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,
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 0 64512 i
*> [Link] 0 0 64512 i
*> [Link] [Link] 0 32768 i
ISP#
ISP# show ip bgp

Notice that ISP has two valid routes to the [Link] network, as indicated by the . However, the link to
SanJose2 has been selected as the best path, indicated by the inclusion of the “>”. Why did the ISP prefer the
link to SanJose2 over SanJose1?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Would changing the bandwidth metric on each link help to correct this issue? Explain.
_______________________________________________________________________________
_______________________________________________________________________________
BGP operates differently than all other protocols. Unlike other routing protocols that use complex algorithms
involving factors such as bandwidth, delay, reliability, and load to formulate a metric, BGP is policy-based. BGP
determines the best path based on variables, such as AS path, weight, local preference, MED, and so on. If all

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

things are equal, BGP prefers the route leading to the BGP speaker with the lowest BGP router ID. The SanJose2
router with BGP router ID [Link] was preferred to the higher BGP router ID of the SanJose1 router
([Link]).
j. At this point, the ISP router should be able to get to each network connected to SanJose1 and SanJose2 from the
loopback address [Link]. Use the extended ping command and specify the source address of ISP Lo0 to
test.
ISP# ping [Link] source [Link]

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
Packet sent with a source address of [Link]
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/24 ms

ISP# ping [Link] source [Link]

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
Packet sent with a source address of [Link]
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/15/16 ms

ISP# ping [Link] source [Link]

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
Packet sent with a source address of [Link]
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/15/16 ms
ISP#

ISP# ping [Link] source [Link]

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
Packet sent with a source address of [Link]
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/24 ms
You can also use the extended ping dialogue to specify the source address, as shown in this example.
ISP# ping
Protocol [ip]:
Target IP address: [Link]
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: [Link]
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

Packet sent with a source address of [Link]

!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/20/24 ms
ISP#
Complete reachability has been demonstrated between the ISP router and both SanJose1 and SanJose2.

Step 7: Configure the BGP next-hop-self feature.

SanJose1 is unaware of the link between ISP and SanJose2, and SanJose2 is unaware of the link between ISP and
SanJose1. Before ISP can successfully ping all the internal serial interfaces of AS 64512, these serial links should be
advertised via BGP on the ISP router. This can also be resolved via EIGRP on each SanJose router. One method is
for ISP to advertise these links.
a. Issue the following commands on the ISP router.
ISP(config)# router bgp 200
ISP(config-router)# network [Link] mask [Link]
ISP(config-router)# network [Link] mask [Link]
b. Issue the show ip bgp command to verify that the ISP is correctly injecting its own WAN links into BGP.
ISP# show ip bgp
BGP table version is 5, 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,
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 0 64512 i
*> [Link] 0 0 64512 i
*> [Link]/30 [Link] 0 32768 i
*> [Link]/30 [Link] 0 32768 i
*> [Link] [Link] 0 32768 i
ISP#
c. Verify on SanJose1 and SanJose2 that the opposite WAN link is included in the routing table. The output from
SanJose2 is as follows.
SanJose2# 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 override

Gateway of last resort is not set

[Link]/16 is variably subnetted, 6 subnets, 3 masks

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

D [Link]/24 [90/2297856] via [Link], [Link], Serial0/0/1

[Link]/24 is variably subnetted, 3 subnets, 2 masks
C [Link]/30 is directly connected, Serial0/0/0
L [Link]/32 is directly connected, Serial0/0/0
B [Link]/30 [20/0] via [Link], [Link]
B [Link]/24 [20/0] via [Link], [Link]
SanJose2#
The next issue to consider is BGP policy routing between autonomous systems. The next-hop attribute of a route
in a different AS is set to the IP address of the border router in the next AS toward the destination, and this
attribute is not modified by default when advertising this route through IBGP. Therefore, for all IBGP peers, it is
either necessary to know the route to that border router (in a different neighboring AS), or our own border router
needs to advertise the foreign routes using the next-hop-self feature, overriding the next-hop address with its own
IP address. The SanJose2 router is passing a policy to SanJose1 and vice versa. The policy for routing from AS
64512 to AS 200 is to forward packets to the [Link] interface. SanJose1 has a similar yet opposite policy: it
forwards requests to the [Link] interface. If either WAN link fails, it is critical that the opposite router become
a valid gateway. This is achieved if the next-hop-self command is configured on SanJose1 and SanJose2.
d. To better understand the next-hop-self command we will remove ISP advertising its two WAN links and
shutdown the WAN link between ISP and SanJose2. The only possible path from SanJose2 to ISP’s
[Link]/24 is through SanJose1.
ISP(config)# router bgp 200
ISP(config-router)# no network [Link] mask [Link]
ISP(config-router)# no network [Link] mask [Link]
ISP(config-router)# exit
ISP(config)# interface serial 0/0/1
ISP(config-if)# shutdown
ISP(config-if)#
e. Display SanJose2’s BGP table using the show ip bgp command and the IPv4 routing table with show ip route.
SanJose2# show ip bgp
BGP table version is 1, 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,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

Network Next Hop Metric LocPrf Weight Path

* i [Link] [Link] 0 100 0 i
* i [Link] [Link] 0 100 0 200 i
SanJose2#

SanJose2# 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 override

Gateway of last resort is not set

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

[Link]/16 is variably subnetted, 6 subnets, 3 masks

S [Link]/16 is directly connected, Null0
C [Link]/24 is directly connected, Serial0/0/1
L [Link]/32 is directly connected, Serial0/0/1
C [Link]/24 is directly connected, Loopback0
L [Link]/32 is directly connected, Loopback0
D [Link]/24 [90/2297856] via [Link], [Link], Serial0/0/1
SanJose2#
Notice that SanJose2 has [Link] in it’s BGP table but not in its routing table. The BGP table shows the
next hop to [Link] as [Link]. Because SanJose2 does not have a route to this next hop address of
[Link] in its routing table, it will not install the [Link] network into the routing table. It won’t install a
route if it doesn’t know how to get to the next hop.
EBGP next hop addresses are carried into IBGP unchanged. As we saw previously, we could advertise the WAN
link using BGP, but this is not always desirable. It means advertising additional routes when we are usually trying
to minimize the size of the routing table. Another option is to have the routers within the IGP domain advertise
themselves as the next hop router using the next-hop-self command.
f. Issue the next-hop-self command on SanJose1 and SanJose2 to advertise themselves as the next hop to their
IBGP peer.
SanJose1(config)# router bgp 64512
SanJose1(config-router)# neighbor [Link] next-hop-self

SanJose2(config)# router bgp 64512

SanJose2(config-router)# neighbor [Link] next-hop-self
g. Reset BGP operation on either router with the clear ip bgp * command.
SanJose1# clear ip bgp *
SanJose1#

SanJose2# clear ip bgp *

SanJose2#
h. After the routers have returned to established BGP speakers, issue the show ip bgp command on SanJose2 and
notice that the next hop is now SanJose1 instead of ISP.
SanJose2# show ip bgp
BGP table version is 5, 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,
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 32768 i
* i [Link] 0 100 0 i
*>i [Link] [Link] 0 100 0 200 i
SanJose2#
i. The show ip route command on SanJose2 now displays the [Link]/24 network because SanJose1 is the
next hop, [Link], which is reachable from SanJose2.
SanJose2# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 10 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

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 override

Gateway of last resort is not set

[Link]/16 is variably subnetted, 6 subnets, 3 masks

SanJose2# show ip route

Gateway of last resort is not set

[Link]/16 is variably subnetted, 6 subnets, 3 masks

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 11 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

Step 8: Set BGP local preference.

At this point, everything looks good, with the exception of default routes, the outbound flow of data, and inbound
packet flow.
a. Because the local preference value is shared between IBGP neighbors, configure a simple route map that
references the local preference value on SanJose1 and SanJose2. This policy adjusts outbound traffic to prefer
the link off the SanJose1 router instead of the metered T1 off SanJose2.
SanJose1(config)# route-map PRIMARY_T1_IN permit 10
SanJose1(config-route-map)# set local-preference 150
SanJose1(config-route-map)# exit
SanJose1(config)# router bgp 64512
SanJose1(config-router)# neighbor [Link] route-map PRIMARY_T1_IN in

SanJose2(config)# route-map SECONDARY_T1_IN permit 10

SanJose2(config-route-map)# set local-preference 125
SanJose1(config-route-map)# exit
SanJose2(config)# router bgp 64512
SanJose2(config-router)# neighbor [Link] route-map SECONDARY_T1_IN in
b. Use the clear ip bgp * soft command after configuring this new policy. When the conversations have been
reestablished, issue the show ip bgp command on SanJose1 and SanJose2.
SanJose1# clear ip bgp * soft
SanJose2# clear ip bgp * soft

SanJose1# show ip bgp

BGP table version is 3, 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,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

Network Next Hop Metric LocPrf Weight Path

* i [Link] [Link] 0 100 0 i
*> [Link] 0 32768 i
*> [Link] [Link] 0 150 0 200 i
SanJose1#

SanJose2# show ip bgp

BGP table version is 7, 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,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

Network Next Hop Metric LocPrf Weight Path

* i [Link] [Link] 0 100 0 i
*> [Link] 0 32768 i
*>i [Link] [Link] 0 150 0 200 i
* [Link] 0 125 0 200 i
SanJose2#

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 12 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

This now indicates that routing to the loopback segment for ISP [Link] /24 can be reached only through
the link common to SanJose1 and ISP. SanJose2’s next hop to [Link]/24 is SanJose1 because both
routers have been configured using the next-hop-self command.

Step 9: Set BGP MED.

a. In the previous step we saw that SanJose1 and SanJose2 will route traffic for [Link]/24 using the link
between SanJose1 and ISP. Examine what the return path ISP takes to reach AS 64512. Notice that the return
path is different from the original path. This is known as asymmetric routing and is not necessarily an unwanted
trait.
ISP# 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,
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 0 64512 i
*> [Link] 0 0 64512 i
*> [Link] [Link] 0 32768 i
ISP# 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 override

Gateway of last resort is not set

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

[Link]/24 is variably subnetted, 4 subnets, 2 masks
C [Link]/30 is directly connected, Serial0/0/1
L [Link]/32 is directly connected, Serial0/0/1
C [Link]/30 is directly connected, Serial0/0/0
L [Link]/32 is directly connected, Serial0/0/0
[Link]/24 is variably subnetted, 2 subnets, 2 masks
C [Link]/24 is directly connected, Loopback0
L [Link]/32 is directly connected, Loopback0
ISP#
How will traffic from network [Link] /24 on ISP return to SanJose1 or SanJose2? Will it be routed through
SanJose1 or SanJose2?
__________________________________________________________________________________
__________________________________________________________________________________

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 13 of 22
CCNPv7 ROUTE Lab 7-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED

__________________________________________________________________________________
To verify this, the simplest solution is to issue the show ip bgp command on the ISP router as was done above. What
if access was not given to the ISP router? Traffic returning from the Internet should not be passed across the metered
T1. Is there a simple way to verify before receiving the monthly bill? How can it be checked instantly?
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
a. Use an extended ping command to verify this situation. Specify the record option and compare your output to the
following. Notice the return path using the exit interface [Link] to SanJose2.
SanJose2# ping
Protocol [ip]:
Target IP address: [Link]
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: [Link]
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: record
Number of hops [ 9 ]:
Loose, Strict, Record, Timestamp, Verbose[RV]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
Packet sent with a source address of [Link]
Packet has IP options: Total option bytes= 39, padded length=40
Record route: <*>
([Link])
([Link])
([Link])
([Link])
([Link])
([Link])
([Link])
([Link])
([Link])