Ccnpv6 Route Lab4-2

All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved.
This document is Cisco Public Information. Page 1 of 21

CCNPv6 ROUTE

Chapter 4 Lab 4-2, Redistribution Between EIGRP and OSPF
Topology

Objecti ves
Review EIGRP and OSPF configuration.
Redistribute into EIGRP.
Redistribute into OSPF.
Summarize routes in EIGRP.
Filter routes using route maps.
Modify EIGRP distances.
Modify OSPF distances.
Create passive interfaces in EIGRP.
Summarize in OSPF at an ABR and an ASBR.
CCNPv6 ROUTE

All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 21
Background
R1 is running EIGRP, and R3 is running multi-area OSPF. In this lab, you configure redistribution on R2 to
enable these two routing protocols to interact, allowing full connectivity between all networks. In Appendix A
of this lab, you explore black hole operation.
Note: This lab uses Cisco 1841 routers with Cisco IOS Release 12.4(24)T1 and the Advanced IP Services
image c1841-advipservicesk9-mz.124-24.T1.bin. You can use other routers (such as 2801 or 2811) and
Cisco IOS Software versions if they have comparable capabilities and features. Depending on the router
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 1841 with Cisco IOS Release 12.4(24)T1 Advanced IP Services or comparable)
Serial and console cables
Step 1: Configure loopbacks and additional addressing.
a. Start with the final configurations of Lab 4.1, Redistribution Between RIP and OSPF. On R1 and R2,
remove the RIPv2 configuration and the static route with the following commands.
R1( conf i g) # no router rip
R1( conf i g) # no ip route 192.168.48.0 255.255.252.0 null0
R1( conf i g) # no ip prefix-list RIP-OUT

R2( conf i g) # no router rip
R2( conf i g) # router ospf 1
R2( conf i g- r out er ) # no default-information originate
R2( conf i g- r out er ) # no redistribute rip
R2( conf i g- r out er ) # no default-metric 10000
b. Configure the additional loopback interfaces on R2 and R3, as shown in the diagram.
R2( conf i g) # interface loopback 100
R2( conf i g- i f ) # ip address 172.16.100.1 255.255.255.0

R3( conf i g- i f ) # interface loopback 9
Step 2: Configure EIGRP.
a. Configure R1 and R2 to run EIGRP in autonomous system 1. On R1, add in all connected interfaces
either with classful network commands or with wildcard masks. Use a classful network statement on R2
and disable automatic summarization.
R1( conf i g) # router eigrp 1
R1( conf i g- r out er ) # no auto-summary
R1( conf i g- r out er ) # network 172.16.0.0
CCNPv6 ROUTE


or

R1( conf i g- r out er ) # network 192.168.0.0 0.0.255.255

b. Verify the configuration with the show ip eigrp neighbors and show ip route ei grp commands on both
routers.
R1# show ip eigrp neighbors
I P- EI GRP nei ghbor s f or pr ocess 1
H Addr ess I nt er f ace Hol d Upt i me SRTT RTO Q Seq
( sec) ( ms) Cnt Num
0 172. 16. 12. 2 Se0/ 0/ 0 11 00: 00: 30 36 216 0 3

R1# show ip route eigrp
172. 16. 0. 0/ 24 i s subnet t ed, 5 subnet s
D 172. 16. 23. 0 [ 90/ 41024000] vi a 172. 16. 12. 2, 00: 01: 38, Ser i al 0/ 0/ 0
D 172. 16. 2. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 01: 16, Ser i al 0/ 0/ 0
D 172. 16. 100. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 02: 13, Ser i al 0/ 0/ 0

R2# show ip eigrp neighbors
I P- EI GRP nei ghbor s f or pr ocess 1
H Addr ess I nt er f ace Hol d Upt i me SRTT RTO Q Seq
( sec) ( ms) Cnt Num
0 172. 16. 12. 1 Se0/ 0/ 0 11 00: 01: 53 1604 5000 0 2

D 172. 16. 1. 0 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 01: 08, Ser i al 0/ 0/ 0
D 192. 168. 70. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 01: 08, Ser i al 0/ 0/ 0
D 192. 168. 51. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 01: 08, Ser i al 0/ 0/ 0
D 192. 168. 50. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 01: 08, Ser i al 0/ 0/ 0
D 192. 168. 49. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 01: 08, Ser i al 0/ 0/ 0
D 192. 168. 48. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 01: 08, Ser i al 0/ 0/ 0
Step 3: Create passive interfaces in EIGRP.
a. Issue the show ip eigrp interfaces command on R2.
R2# show ip eigrp interfaces
I P- EI GRP i nt er f aces f or pr ocess 1

Xmi t Queue Mean Paci ng Ti me Mul t i cast
Pendi ng
I nt er f ace Peer s Un/ Rel i abl e SRTT Un/ Rel i abl e Fl ow Ti mer Rout es
Se0/ 0/ 0 1 0/ 0 32 10/ 380 496 0
Se0/ 0/ 1 0 0/ 0 0 0/ 1 0 0
Lo0 0 0/ 0 0 0/ 1 0 0
Lo100 0 0/ 0 0 0/ 1 0 0
CCNPv6 ROUTE

Because you used the classful network command, both serial interfaces are involved with EIGRP.
b. To stop EIGRP from sending or processing received EIGRP packets on the serial interface going to R3,
use the passive-interface interface_type interface_number command.
R2( conf i g- r out er ) # passive-interface serial 0/0/1
c. Verify the change with the show ip eigrp interfaces and show ip protocols commands.
R2# show ip eigrp interfaces
I P- EI GRP i nt er f aces f or pr ocess 1

Xmi t Queue Mean Paci ng Ti me Mul t i cast
Pendi ng
I nt er f ace Peer s Un/ Rel i abl e SRTT Un/ Rel i abl e Fl ow Ti mer Rout es
Se0/ 0/ 0 1 0/ 0 32 10/ 380 496 0
Lo0 0 0/ 0 0 0/ 1 0 0
Lo100 0 0/ 0 0 0/ 1 0 0

R2# show ip protocols
Rout i ng Pr ot ocol i s " ospf 1"
<out put omi t t ed>

Rout i ng Pr ot ocol i s " ei gr p 1"
Out goi ng updat e f i l t er l i st f or al l i nt er f aces i s not set
I ncomi ng updat e f i l t er l i st f or al l i nt er f aces i s not set
Def aul t net wor ks f l agged i n out goi ng updat es
Def aul t net wor ks accept ed f r omi ncomi ng updat es
EI GRP met r i c wei ght K1=1, K2=0, K3=1, K4=0, K5=0
EI GRP maxi mumhopcount 100
EI GRP maxi mummet r i c var i ance 1
Redi st r i but i ng: ei gr p 1
EI GRP NSF- awar e r out e hol d t i mer i s 240s
Aut omat i c net wor k summar i zat i on i s not i n ef f ect
Maxi mumpat h: 4
Rout i ng f or Net wor ks:
172. 16. 0. 0
Passi ve I nt er f ace( s) :
Ser i al 0/ 0/ 1
Rout i ng I nf or mat i on Sour ces:
Gat eway Di st ance Last Updat e
172. 16. 12. 1 90 00: 27: 57
Di st ance: i nt er nal 90 ext er nal 170
How does preventing hello packets out of an interface affect the update capabilities of EIGRP out that
interface?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________

CCNPv6 ROUTE

Is this behavior more like RIP or like OSPF in regard to the passive-interface command?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Step 4: Manually summarize with EIGRP.
You can have EIGRP summarize routes sent out an interface to make routing updates more efficient by using
the ip summary-address eigrp as network mask command.
a. Have R1 advertise one supernet for loopbacks 48 and 49 to R2. Do not summarize loopbacks 50 and 51
in this statement, because these will be summarized in Step 9.
R1( conf i g) # interface serial 0/0/0
R1( conf i g- i f ) # ip summary-address eigrp 1 192.168.48.0 255.255.254.0

*Feb 23 18: 20: 21. 219: %DUAL- 5- NBRCHANGE: I P- EI GRP( 0) 1: Nei ghbor 172. 16. 12. 2
( Ser i al 0/ 0/ 0) i s r esync: summar y conf i gur ed

D 172. 16. 23. 0 [ 90/ 41024000] vi a 172. 16. 12. 2, 00: 45: 21, Ser i al 0/ 0/ 0
D 172. 16. 2. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 45: 21, Ser i al 0/ 0/ 0
D 172. 16. 100. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 08: 12, Ser i al 0/ 0/ 0
D 192. 168. 48. 0/ 23 i s a summar y, 04: 27: 07, Nul l 0
b. Verify the configuration with the show ip route eigrp and show ip route 192.168.48.0 255.255.254.0
commands on R1. Notice the administrative distance for this route.
R1# show ip route 192.168.48.0 255.255.254.0
Rout i ng ent r y f or 192. 168. 48. 0/ 23, super net
Known vi a " ei gr p 1" , di st ance 5, met r i c 128256, t ype i nt er nal
Redi st r i but i ng vi a ei gr p 1
Rout i ng Descr i pt or Bl ocks:
* di r ect l y connect ed, vi a Nul l 0
Rout e met r i c i s 128256, t r af f i c shar e count i s 1
Tot al del ay i s 5000 mi cr oseconds, mi ni mumbandwi dt h i s 10000000 Kbi t
Rel i abi l i t y 255/ 255, mi ni mumMTU 1514 byt es
Loadi ng 1/ 255, Hops 0
Why does EIGRP make the administrative distance different for summary routes?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Step 5: Additional OSPF configuration.
OSPF is already partially configured on R2 and R3.
a. You need to add the area 10 configuration to R2 and the area 20 configuration to R3 to complete the
configuration.
R2( conf i g- r out er ) # network 172.16.100.0 0.0.0.255 area 10
CCNPv6 ROUTE


R3( conf i g- r out er ) # network 192.168.8.0 0.0.3.255 area 20
b. Verify that your adjacencies come up with the show ip ospf neighbor command, and make sure that you
have routes from OSPF populating the R2 routing table using the show ip route ospf command.
R2# show ip ospf neighbor

Nei ghbor I D Pr i St at e Dead Ti me Addr ess I nt er f ace
192. 168. 40. 1 0 FULL/ - 00: 00: 35 172. 16. 23. 3 Ser i al 0/ 0/ 1

R3# show ip ospf neighbor

Nei ghbor I D Pr i St at e Dead Ti me Addr ess I nt er f ace
172. 16. 2. 1 0 FULL/ - 00: 00: 35 172. 16. 23. 2 Ser i al 0/ 0/ 1

R2# show ip route ospf
O 192. 168. 30. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 12: 10, Ser i al 0/ 0/ 1
O I A 192. 168. 8. 1 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 20: 48, Ser i al 0/ 0/ 1
O 192. 168. 25. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 12: 10, Ser i al 0/ 0/ 1
O I A 192. 168. 9. 1 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 20: 48, Ser i al 0/ 0/ 1
O I A 192. 168. 10. 1 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 20: 48, Ser i al 0/ 0/ 1
O 192. 168. 40. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 12: 10, Ser i al 0/ 0/ 1
O 172. 16. 3. 0 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 21: 26, Ser i al 0/ 0/ 1
O I A 192. 168. 11. 1 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 20: 48, Ser i al 0/ 0/ 1
O 192. 168. 20. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 12: 10, Ser i al 0/ 0/ 1
O 192. 168. 35. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 12: 10, Ser i al 0/ 0/ 1

172. 16. 0. 0/ 16 i s var i abl y subnet t ed, 3 subnet s, 2 masks
O I A 172. 16. 100. 1/ 32 [ 110/ 1563] vi a 172. 16. 23. 2, 00: 00: 15, Ser i al 0/ 0/ 1
Notice that for the newly added loopback interfaces, OSPF advertised /32 destination prefixes (for
example, R2 has a route to 192.168.8.1/32 in its routing table).
c. Override this default behavior by using the ip ospf network point-to-point command on the OSPF
loopback interfaces on R2 and R3. You can copy and paste the following configurations to save time.
Router R2:
interface loopback 100
ip ospf network point-to-point
Router R3:
(Only configure the point-to-point network type for the newly added loopbacks in area 20. The area 0
loopbacks were configured in Lab 4-1.)


CCNPv6 ROUTE


Note: You can also use the interface range command to configure multiple interfaces simultaneously, as
shown below.
interface range lo 8 - 11
d. Verify the configuration with the show ip route command on R2. Notice that the routes now each show
on one line with the /24 major network mask.
R2# show ip route

Gat eway of l ast r esor t i s not set

O 192. 168. 30. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 27: 11, Ser i al 0/ 0/ 1
O I A 192. 168. 8. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 08: 39, Ser i al 0/ 0/ 1
O 192. 168. 25. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 27: 11, Ser i al 0/ 0/ 1
O I A 192. 168. 9. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 08: 39, Ser i al 0/ 0/ 1
O I A 192. 168. 10. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 08: 39, Ser i al 0/ 0/ 1
O 192. 168. 40. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 27: 11, Ser i al 0/ 0/ 1
C 172. 16. 23. 0 i s di r ect l y connect ed, Ser i al 0/ 0/ 1
D 172. 16. 1. 0 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 47: 33, Ser i al 0/ 0/ 0
C 172. 16. 2. 0 i s di r ect l y connect ed, Loopback0
O 172. 16. 3. 0 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 36: 27, Ser i al 0/ 0/ 1
O I A 192. 168. 11. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 08: 41, Ser i al 0/ 0/ 1
O 192. 168. 20. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 27: 13, Ser i al 0/ 0/ 1
D 192. 168. 51. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 47: 36, Ser i al 0/ 0/ 0
D 192. 168. 50. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 47: 36, Ser i al 0/ 0/ 0
O 192. 168. 35. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 27: 13, Ser i al 0/ 0/ 1
D 192. 168. 70. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 47: 36, Ser i al 0/ 0/ 0
D 192. 168. 48. 0/ 23 [ 90/ 40640000] vi a 172. 16. 12. 1, 00: 40: 01, Ser i al 0/ 0/ 0
Notice that R2 is the only router with knowledge of all routes in the topology at this point, because it is
involved with both routing protocols.
Step 6: Summarize OSPF areas at the ABR.
Review the R2 routing table. Notice the inter-area routes for the R3 loopbacks in area 20.
a. Summarize the areas into a single inter-area route using the area area range network mask command on
R3.
R3( conf i g- r out er ) # area 20 range 192.168.8.0 255.255.252.0
b. On R2, verify the summarization with the show ip route ospf command on R2.
O 192. 168. 30. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 02: 38: 46, Ser i al 0/ 0/ 1
O 192. 168. 25. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 02: 38: 46, Ser i al 0/ 0/ 1
O 192. 168. 40. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 02: 38: 46, Ser i al 0/ 0/ 1
O 172. 16. 3. 0 [ 110/ 1563] vi a 172. 16. 23. 3, 02: 38: 46, Ser i al 0/ 0/ 1
CCNPv6 ROUTE

O 192. 168. 20. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 02: 38: 46, Ser i al 0/ 0/ 1
O 192. 168. 35. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 02: 38: 46, Ser i al 0/ 0/ 1
O I A 192. 168. 8. 0/ 22 [ 110/ 1563] vi a 172. 16. 23. 3, 00: 00: 07, Ser i al 0/ 0/ 1
Where can you summarize in OSPF?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Compare and contrast OSPF and EIGRP in terms of where summarization takes place.
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Explain the synchronization requirement in OSPF that eliminates other routers as points of
summarization.
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Why or why not does EIGRP have this requirement?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Step 7: Configure mutual redistribution between OSPF and EIGRP.
a. Under the OSPF process on R2, issue the redistribute eigrp 1 subnets command. The subnets
command is necessary because, by default, OSPF only redistributes classful networks and supernets. A
default seed metric is not required for OSPF. Under the EIGRP process, issue the redi stribute ospf 1
metric 10000 100 255 1 1500 command, which tells EIGRP to redistribute OSPF process 1 with these
metrics: bandwidth of 10000, delay of 100, reliability of 255/255, load of 1/255, and a MTU of 1500. Like
RIP, EIGRP requires a seed metric. You can also set a default seed metric with the default-metric
command.
R2( conf i g- r out er ) # redistribute eigrp 1 subnets
R2( conf i g- r out er ) # exit

R2( conf i g- r out er ) # redistribute ospf 1 metric 10000 100 255 1 1500

CCNPv6 ROUTE

or

R2( conf i g- r out er ) # default-metric 10000 100 255 1 1500
R2( conf i g- r out er ) # redistribute ospf 1
b. Issue the show ip protocols command on the redistributing router, R2. Compare your output with the
following output.
Rout er I D 172. 16. 2. 1
I t i s an ar ea bor der and aut onomous syst emboundar y r out er
Redi st r i but i ng Ext er nal Rout es f r om,
ei gr p 1, i ncl udes subnet s i n r edi st r i but i on
Number of ar eas i n t hi s r out er i s 2. 2 nor mal 0 st ub 0 nssa
Maxi mumpat h: 4
172. 16. 23. 0 0. 0. 0. 255 ar ea 0
172. 16. 100. 0 0. 0. 0. 255 ar ea 10
Ref er ence bandwi dt h uni t i s 100 mbps
192. 168. 40. 1 110 00: 00: 33
Di st ance: ( def aul t i s 110)

Def aul t net wor ks f l agged i n out goi ng updat es
Def aul t net wor ks accept ed f r omi ncomi ng updat es
EI GRP met r i c wei ght K1=1, K2=0, K3=1, K4=0, K5=0
EI GRP maxi mumhopcount 100
EI GRP maxi mummet r i c var i ance 1
Redi st r i but i ng: ospf 1, ei gr p 1
EI GRP NSF- awar e r out e hol d t i mer i s 240s
Aut omat i c net wor k summar i zat i on i s not i n ef f ect
Maxi mumpat h: 4
172. 16. 0. 0
Ser i al 0/ 0/ 1
172. 16. 12. 1 90 00: 00: 49

c. Display the routing tables on R1 and R3 so that you can see the redistributed routes. Redistributed OSPF
routes display on R1 as D EX, which means that they are external EIGRP routes. Redistributed EIGRP
routes are tagged in the R3 routing table as O E2, which means that they are OSPF external type 2. Type
2 is the default OSPF external type.
R1# show ip route


CCNPv6 ROUTE

D EX 192. 168. 30. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 00: 05, Ser i al 0/ 0/ 0
D EX 192. 168. 25. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 00: 05, Ser i al 0/ 0/ 0
D EX 192. 168. 40. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 00: 05, Ser i al 0/ 0/ 0
D 172. 16. 100. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 38: 02, Ser i al 0/ 0/ 0
D 172. 16. 23. 0 [ 90/ 41024000] vi a 172. 16. 12. 2, 00: 38: 02, Ser i al 0/ 0/ 0
D 172. 16. 2. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 38: 02, Ser i al 0/ 0/ 0
D EX 172. 16. 3. 0 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 00: 06, Ser i al 0/ 0/ 0
D EX 192. 168. 20. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 00: 06, Ser i al 0/ 0/ 0
C 192. 168. 51. 0/ 24 i s di r ect l y connect ed, Loopback51
D EX 192. 168. 35. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 00: 06, Ser i al 0/ 0/ 0
D EX 192. 168. 8. 0/ 22 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 00: 07, Ser i al 0/ 0/ 0

R3# show ip route


O E2 172. 16. 12. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
O E2 172. 16. 1. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
O E2 172. 16. 2. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
O I A 172. 16. 100. 0 [ 110/ 1563] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
O E2 192. 168. 51. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
O E2 192. 168. 50. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
O E2 192. 168. 70. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
O 192. 168. 8. 0/ 22 i s a summar y, 01: 34: 48, Nul l 0
O E2 192. 168. 48. 0/ 23 [ 110/ 20] vi a 172. 16. 23. 2, 00: 41: 48, Ser i al 0/ 0/ 1
d. Verify full connectivity with the following Tcl script:
R1# tclsh

f or each addr ess {
172. 16. 1. 1
192. 168. 48. 1
192. 168. 49. 1
192. 168. 50. 1
192. 168. 51. 1
192. 168. 70. 1
172. 16. 12. 1
CCNPv6 ROUTE

172. 16. 2. 1
172. 16. 100. 1
172. 16. 12. 2
172. 16. 23. 2
172. 16. 3. 1
192. 168. 20. 1
192. 168. 25. 1
192. 168. 30. 1
192. 168. 35. 1
192. 168. 40. 1
192. 168. 8. 1
192. 168. 9. 1
192. 168. 10. 1
192. 168. 11. 1
172. 16. 23. 3
} { pi ng $addr ess }
Step 8: Filter redistribution with route maps.
One way to filter prefixes is with a route map. When used for filtering prefixes, a route map works like an
access list. It has multiple statements that are read in a sequential order. Each statement can be a deny or
permit and can have a match clause for a variety of attributes, such as the route or a route tag. You can also
include route attributes in each statement that will be set if the match clause is met.
a. Before filtering the R3 loopback 25 and 30 networks from being redistributed into EIGRP on R2, display
the R1 routing table and verify that those two routes currently appear there.
D EX 192. 168. 30. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 28, Ser i al 0/ 0/ 0
D EX 192. 168. 25. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 28, Ser i al 0/ 0/ 0
D EX 192. 168. 40. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 28, Ser i al 0/ 0/ 0
D 172. 16. 23. 0 [ 90/ 41024000] vi a 172. 16. 12. 2, 00: 42: 25, Ser i al 0/ 0/ 0
D 172. 16. 2. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 42: 25, Ser i al 0/ 0/ 0
D EX 172. 16. 3. 0 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 28, Ser i al 0/ 0/ 0
D 172. 16. 100. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 01: 34: 26, Ser i al 0/ 0/ 0
D EX 192. 168. 20. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 28, Ser i al 0/ 0/ 0
D EX 192. 168. 35. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 28, Ser i al 0/ 0/ 0
D EX 192. 168. 8. 0/ 22 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 28, Ser i al 0/ 0/ 0
There are multiple ways to configure this filtering. For this exercise, configure an access list that matches
these two network addresses and a route map that denies based on a match for that access list.
b. Configure the access list as follows:
R2( conf i g) # access-list 1 permit 192.168.25.0
R2( conf i g) # access-list 1 permit 192.168.30.0
c. Configure a route map with a statement that denies based on a match with this access list. Then add a
permit statement without a match statement, which acts as an explicit permit all.
R2( conf i g) # route-map SELECTED-DENY deny 10
R2( conf i g- r out e- map) # match ip address 1
R2( conf i g- r out e- map) # route-map SELECTED-DENY permit 20
d. Apply this route map by redoing the redistribute command with the route map under the EIGRP process.
R2( conf i g- r out er ) # redistribute ospf 1 route-map SELECTED-DENY metric 64 100
255 1 1500
CCNPv6 ROUTE

e. As an alternative, if you previously configured a default metric under EIGRP, you can simply use the
following command.
R2( conf i g- r out er ) # redistribute ospf 1 route-map SELECTED-DENY
f. Verify that these routes are filtered out in the R1 routing table.
D EX 192. 168. 40. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 07: 24, Ser i al 0/ 0/ 0
D 172. 16. 23. 0 [ 90/ 41024000] vi a 172. 16. 12. 2, 00: 45: 21, Ser i al 0/ 0/ 0
D 172. 16. 2. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 45: 21, Ser i al 0/ 0/ 0
D EX 172. 16. 3. 0 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 07: 24, Ser i al 0/ 0/ 0
D 172. 16. 100. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 45: 21, Ser i al 0/ 0/ 0
D EX 192. 168. 20. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 07: 24, Ser i al 0/ 0/ 0
D EX 192. 168. 35. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 07: 24, Ser i al 0/ 0/ 0
D EX 192. 168. 8. 0/ 22 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 07: 24, Ser i al 0/ 0/ 0
Step 9: Summarize external routes into OSPF at the ASBR.
You cannot summarize routes redistributed into OSPF using the area range command. This command is
effective only on routes internal to the specified area. Instead, use the OSPF summary-address network
mask command.
a. Before you make any changes, display the R3 routing table.
O E2 172. 16. 12. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
O E2 172. 16. 1. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
O E2 172. 16. 2. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
O I A 172. 16. 100. 0 [ 110/ 1563] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
O E2 192. 168. 70. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
O E2 192. 168. 51. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
O E2 192. 168. 50. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
O E2 192. 168. 48. 0/ 23 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 07, Ser i al 0/ 0/ 1
Notice the three external routes for the R1 loopback interfaces 48 through 51. Two of the loopbacks are
already summarized to one /23.
Which mask should you use to summarize all four of the loopbacks to one prefix?
_______________________________________________________________________________
b. You can summarize this all into one supernet on R2 using the following commands.
R2( conf i g- r out er ) # summary-address 192.168.48.0 255.255.252.0
c. Verify this action in the R3 routing table.
O E2 172. 16. 12. 0 [ 110/ 20] vi a 172. 16. 23. 2, 01: 40: 45, Ser i al 0/ 0/ 1
O E2 172. 16. 1. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 48: 54, Ser i al 0/ 0/ 1
O E2 172. 16. 2. 0 [ 110/ 20] vi a 172. 16. 23. 2, 01: 40: 45, Ser i al 0/ 0/ 1
O I A 172. 16. 100. 0 [ 110/ 1563] vi a 172. 16. 23. 2, 01: 40: 45, Ser i al 0/ 0/ 1
O E2 192. 168. 70. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 48: 54, Ser i al 0/ 0/ 1
O E2 192. 168. 48. 0/ 22 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 08, Ser i al 0/ 0/ 1
CCNPv6 ROUTE

What would happen if loopback 50 on R1 were to become unreachable by R2?
_______________________________________________________________________________
_______________________________________________________________________________
Would data destined for 192.168.50.0/24 from R3 still be sent to R2?
_______________________________________________________________________________
_______________________________________________________________________________
Would data destined for 192.168.50.0/24 from R2 continue to be sent to R1?
_______________________________________________________________________________
_______________________________________________________________________________
d. If you are unsure of the outcome, shut down the interface on R1. Issue the ICMP traceroute command to
192.168.50.1 from R3 and then from R2. Check your output against the output and analysis in Appendix
A. Remember to issue the no shutdown command when you are finished checking.
Is this a desirable outcome? Explain.
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Step 10: Modify EIGRP distances.
a. By default, EIGRP uses an administrative distance of 90 for internal routes and 170 for external routes.
You can see this in the R1 routing table and in the output of the show ip protocols command.
D EX 192. 168. 40. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 172. 16. 23. 0 [ 90/ 41024000] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 172. 16. 2. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 172. 16. 3. 0 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 172. 16. 100. 0 [ 90/ 40640000] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 192. 168. 20. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 192. 168. 35. 0/ 24 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 192. 168. 8. 0/ 22 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 192. 168. 48. 0/ 23 i s a summar y, 3d17h, Nul l 0
D EX 192. 168. 48. 0/ 22 [ 170/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0


Addr ess Summar i zat i on:
192. 168. 48. 0/ 23 f or Ser i al 0/ 0/ 0
Summar i zi ng wi t h met r i c 128256
Maxi mumpat h: 4
172. 16. 0. 0
192. 168. 0. 0/ 16
CCNPv6 ROUTE

( t hi s r out er ) 90 00: 34: 33
172. 16. 12. 2 90 00: 16: 35
b. You can change the administrative distance with the di stance eigrp internal external command. This
command is only applicable locally. Change the distance to 95 for internal routes and 165 for external
routes.
R1( conf i g- r out er ) # distance eigrp 95 165

Note: The EIGRP neighbor adjacency will be re-negotiated:

R1#
*May 3 00: 28: 38. 379: %DUAL- 5- NBRCHANGE: I P- EI GRP( 0) 1: Nei ghbor 172. 16. 12. 2
( Ser i al 0/ 0/ 0) i s down: r out e conf i gur at i on changed
*May 3 00: 28: 41. 503: %DUAL- 5- NBRCHANGE: I P- EI GRP( 0) 1: Nei ghbor 172. 16. 12. 2
( Ser i al 0/ 0/ 0) i s up: new adj acency
c. Verify the change in the routing table with the show ip route eigrp and show ip protocols commands.
D EX 192. 168. 40. 0/ 24 [ 165/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 172. 16. 23. 0 [ 95/ 41024000] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 172. 16. 2. 0 [ 95/ 40640000] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 172. 16. 3. 0 [ 165/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 172. 16. 100. 0 [ 95/ 40640000] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 192. 168. 20. 0/ 24 [ 165/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 192. 168. 35. 0/ 24 [ 165/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D EX 192. 168. 8. 0/ 22 [ 165/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0
D 192. 168. 48. 0/ 23 i s a summar y, 3d17h, Nul l 0
D EX 192. 168. 48. 0/ 22 [ 165/ 40537600] vi a 172. 16. 12. 2, 00: 04: 03, Ser i al 0/ 0/ 0


172. 16. 12. 2 95 00: 00: 00
Step 11: Modify OSPF distances.
You can also modify individual OSPF distances. By default, all OSPF distances are 110, but you can change
the intra-area, inter-area, and external route distances using the distance ospf intra-area distance inter-
area distance external distance command. All the command arguments are optional, so you can change only
what you need to.
a. Before changing anything, display the R3 routing table.
O E2 172. 16. 12. 0 [ 110/ 20] vi a 172. 16. 23. 2, 01: 40: 45, Ser i al 0/ 0/ 1
O E2 172. 16. 1. 0 [ 110/ 20] vi a 172. 16. 23. 2, 00: 48: 54, Ser i al 0/ 0/ 1
O E2 172. 16. 2. 0 [ 110/ 20] vi a 172. 16. 23. 2, 01: 40: 45, Ser i al 0/ 0/ 1
O I A 172. 16. 100. 0 [ 110/ 1563] vi a 172. 16. 23. 2, 01: 40: 45, Ser i al 0/ 0/ 1
O E2 192. 168. 70. 0/ 24 [ 110/ 20] vi a 172. 16. 23. 2, 00: 48: 54, Ser i al 0/ 0/ 1
CCNPv6 ROUTE

O E2 192. 168. 48. 0/ 22 [ 110/ 20] vi a 172. 16. 23. 2, 00: 00: 08, Ser i al 0/ 0/ 1
b. Change the intra-area distance to 105, inter-area distance to 115, and external routes to 175 on R3.
R3( conf i g- r out er ) # distance ospf intra-area 105 inter-area 115 external 175
c. Verify the change in the routing table. Unfortunately, the only information that you can get from the output
of the show ip protocols command is the default distance, which is the intra-area distance.
O E2 172. 16. 12. 0 [ 175/ 20] vi a 172. 16. 23. 2, 00: 00: 05, Ser i al 0/ 0/ 1
O E2 172. 16. 1. 0 [ 175/ 20] vi a 172. 16. 23. 2, 00: 00: 05, Ser i al 0/ 0/ 1
O E2 172. 16. 2. 0 [ 175/ 20] vi a 172. 16. 23. 2, 00: 00: 05, Ser i al 0/ 0/ 1
O I A 172. 16. 100. 0 [ 115/ 1563] vi a 172. 16. 23. 2, 00: 00: 05, Ser i al 0/ 0/ 1
O E2 192. 168. 70. 0/ 24 [ 175/ 20] vi a 172. 16. 23. 2, 00: 00: 05, Ser i al 0/ 0/ 1
O E2 192. 168. 48. 0/ 22 [ 175/ 20] vi a 172. 16. 23. 2, 00: 00: 05, Ser i al 0/ 0/ 1

Rout er I D 192. 168. 40. 1
I t i s an ar ea bor der r out er
Number of ar eas i n t hi s r out er i s 2. 2 nor mal 0 st ub 0 nssa
Maxi mumpat h: 4
172. 16. 0. 0 0. 0. 255. 255 ar ea 0
192. 168. 8. 0 0. 0. 3. 255 ar ea 20
192. 168. 0. 0 0. 0. 255. 255 ar ea 0
Ref er ence bandwi dt h uni t i s 100 mbps
Fast Et her net 0/ 0
Fast Et her net 0/ 1
Ser i al 0/ 0/ 0
Ser i al 0/ 1/ 0
Ser i al 0/ 1/ 1
Loopback0
Loopback8
Loopback9
Loopback10
Loopback11
Loopback20
Loopback25
Loopback30
Loopback35
Loopback40
VoI P- Nul l 0
( t hi s r out er ) 110 00: 03: 04
172. 16. 2. 1 110 00: 03: 04
Di st ance: ( def aul t i s 105)

CCNPv6 ROUTE

Challenge: Change the Administrati ve Distance on R2
The previous two steps demonstrated using the distance command in a fairly inconsequential environment.
In which types of scenarios would the distance command be more valuable?
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
On R2, you are running both EIGRP and OSPF. Imagine a fourth router, R4, connected to both R1 and R3.
R4 is redistributing between the two routing protocols.
Using the default administrative distances for EIGRP and OSPF, which protocol would be preferred in the
routing table for destination prefixes in native OSPF networks and why?
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
Which protocol would be preferred in the routing table for destination prefixes for native EIGRP networks?
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
Instead of adding the 172.16.1.0/24 networks natively to EIGRP using a network statement, add the
networks using the redistri bute connected command in EIGRP configuration mode on R1.
__________________________________________________________________________________
__________________________________________________________________________________
With the default administrative distances set, what would the administrative distance be for that prefix on R2
in EIGRP and in OSPF? Explain why.
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
How could you make the EIGRP path prefer this route? Is there more than one way?
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
CCNPv6 ROUTE

Could using the di stance command in this situation cause asymmetric routing? Explain.
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________
__________________________________________________________________________________

CCNPv6 ROUTE

Router Interface Summary Table
Router Interface Summary
Router Model Ethernet Interface
#1
Ethernet Interface
#2
Serial Interface
#1
Serial Interface
#2
1700 Fast Ethernet 0
(FA0)
Fast Ethernet 1
(FA1)
Serial 0 (S0) Serial 1 (S1)
1800 Fast Ethernet 0/0
FA0/0)
Fast Ethernet 0/1
(FA0/1)
Serial 0/0/0
(S0/0/0)
Serial 0/0/1
(S0/0/1)
(FA0/0)
Fast Ethernet 0/1
(FA0/1)
Serial 0/0 (S0/0) Serial 0/1 (S0/1)
(FA0/0)
Fast Ethernet 0/1
(FA0/1)
Serial 0/0/0
(S0/0/0)
Serial 0/0/1
(S0/0/1)
Note: To find out how the router is configured, look at the interfaces to identify the type of router
and how many interfaces the router has. Rather than list all combinations of configurations for each
router class, this table includes identifiers for the possible combinations of Ethernet and serial
interfaces in the device. The table does not include any other type of interface, even though a
specific router might contain one. For example, for an ISDN BRI interface, the string in parenthesis
is the legal abbreviation that can be used in Cisco IOS commands to represent the interface.

Appendix A: Exploring Black Hole Operations
a. Configure R1 and shut down the loopback 50 interface:
R1( conf i g- i f ) # shutdown
b. On R2, you should see the following output.
R2# show ip route


O 192. 168. 30. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 18: 53: 52, Ser i al 0/ 0/ 1
O 192. 168. 25. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 18: 53: 52, Ser i al 0/ 0/ 1
O 192. 168. 40. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 18: 53: 52, Ser i al 0/ 0/ 1
D 172. 16. 1. 0 [ 90/ 40640000] vi a 172. 16. 12. 1, 18: 54: 06, Ser i al 0/ 0/ 0
O 172. 16. 3. 0 [ 110/ 1563] vi a 172. 16. 23. 3, 18: 53: 53, Ser i al 0/ 0/ 1
O 192. 168. 20. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 18: 53: 53, Ser i al 0/ 0/ 1
D 192. 168. 51. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 18: 54: 07, Ser i al 0/ 0/ 0
O 192. 168. 35. 0/ 24 [ 110/ 1563] vi a 172. 16. 23. 3, 18: 53: 53, Ser i al 0/ 0/ 1
D 192. 168. 70. 0/ 24 [ 90/ 40640000] vi a 172. 16. 12. 1, 18: 54: 07, Ser i al 0/ 0/ 0
O I A 192. 168. 8. 0/ 22 [ 110/ 1563] vi a 172. 16. 23. 3, 18: 53: 54, Ser i al 0/ 0/ 1
D 192. 168. 48. 0/ 23 [ 90/ 40640000] vi a 172. 16. 12. 1, 18: 54: 08, Ser i al 0/ 0/ 0
Notice the absence of 192.168.50.0/24 in a specific route in the R2 routing table.
c. Begin debugging all incoming IP packets on R2, and then issue the ping 192.168.50.1 command.
R2# debug ip packet
CCNPv6 ROUTE


R2# ping 192.168.50.1
( debug out put cl eaned up so as t o be r eadabl e)

Type escape sequence t o abor t .
Sendi ng 5, 100- byt e I CMP Echos t o 192. 168. 50. 1, t i meout i s 2 seconds:
. . . . .
Success r at e i s 0 per cent ( 0/ 5)

*Oct 17 16: 39: 14. 147: I P: s=172. 16. 2. 1 ( l ocal ) , d=192. 168. 50. 1 ( Nul l 0) , l en
100, sendi ng
. . .

R2# undebug all

R2# traceroute 192.168.50.1

Tr aci ng t he r out e t o 192. 168. 50. 1

1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *

The summary route, pointing to the Null0 interface as the next hop, acts as a catch all for any traffic
generated by R2 or forwarded to R2 with the destination network 192.168.48.0/24. R2 sends traffic to the
Null0 virtual interface, as shown by the IP packet debugging output highlighted above.
R2 is not able to ping the R1 shutdown loopback interface because the 192.168.50.0/24 route no longer
exists in the routing table.
Check to see if network 192.168.50.0/24, or a supernet of it, is in the routing table of R3.
R3# show ip route 192.168.50.1
Rout i ng ent r y f or 192. 168. 48. 0/ 22, super net
Known vi a " ospf 1" , di st ance 110, met r i c 20, t ype ext er n 2, f or war d met r i c
1562
Last updat e f r om172. 16. 23. 2 on Ser i al 0/ 0/ 1, 00: 39: 17 ago
Rout i ng Descr i pt or Bl ocks:
* 172. 16. 23. 2, f r om172. 16. 2. 1, 00: 39: 17 ago, vi a Ser i al 0/ 0/ 1
Rout e met r i c i s 20, t r af f i c shar e count i s 1
d. Begin debugging all IP and ICMP packets on R3. Ping the address 192.168.50.1 from R3. Try to trace the
route from R3 to 192.168.50.1.
R3# debug ip packet
R3# debug ip icmp

R3# ping 192.168.50.1

CCNPv6 ROUTE

Sendi ng 5, 100- byt e I CMP Echos t o 192. 168. 50. 1, t i meout i s 2 seconds:
U. U. U
Success r at e i s 0 per cent ( 0/ 5)

*Oct 17 16: 49: 21. 023: I P: t abl ei d=0, s=172. 16. 23. 3 ( l ocal ) , d=192. 168. 50. 1
( Ser i al 0/ 0/ 1) , r out ed vi a FI B

*Oct 17 16: 49: 21. 047: I CMP: dst ( 172. 16. 23. 3) host unr eachabl e r cv f r om
172. 16. 23. 2

R3# undebug all

R3# traceroute 192.168.50.1

Tr aci ng t he r out e t o 192. 168. 50. 1

1 172. 16. 23. 2 12 msec 12 msec 16 msec
2 172. 16. 23. 2 ! H ! H *
Analyze the process indicated by the ICMP responses. You might also want to refer to debugging
messages for ICMP and IP packets on R2.
1. R3 generates an ICMP echo request (ping) to 192.168.50.1.
2. R3 looks up the (next-hop address, outgoing interface) pair for the longest matching prefix containing
192.168.50.1 in the IP routing table. It finds (172.16.23.2, Serial0/0/1).
3. R3 routes the IP packet to (172.16.23.2, Serial0/0/1).
4. R2 receives the IP packet from R3 on interface Serial0/0/1.
5. R2 looks up the (next-hop address, outgoing interface) pair for the longest prefix matching containing
192.168.50.1 in the IP routing table. The longest matching prefix that the routing table returns is
192.168.48.0/22, for which the routing table responds with (null, Null0) because it has no next-hop
address or physical outgoing interface.
6. R2 realizes that this packet was routed remotely to it but that it has no route, so it sends an ICMP
Type 3, Code 1 (host unreachable) packet to the source address of the packet, 172.16.23.3.
7. R2 looks up the (next-hop address, outgoing interface) pair for 172.16.23.3 and resolves it to
(172.16.23.3, Serial0/0/1).
8. R2 then routes the ICMP packet for destination 172.16.23.3, normally 172.16.23.3 through
Serial0/0/1.
9. R3 receives a packet destined for its local address 172.16.23.3 and reads the packet, sending the
ICMP Host Unreachable message to the ping output.
Note: For more information about how routers respond to unreachable hosts, see RFC 792 (ICMP) at
http://tools.ietf.org/html/rfc792 and RFC 4443 (ICMPv6) at http://tools.ietf.org/html/rfc4443.
Notice that R2 sends R3 an ICMP Type 3, Code 1 reply indicating that it does not have a route to the host
192.168.50.1. This ICMP Host Unreachable message is not only sent in response to pings or
traceroutes (also a form of ICMP) but for all IP traffic.
e. If you were to use Telnet to 192.168.50.1, you would receive the following message based on the ICMP
response from R2:
R3#telnet 192.168.50.1
Tr yi ng 192. 168. 50. 1 . . .
CCNPv6 ROUTE

%Dest i nat i on unr eachabl e; gat eway or host down

R3#
This is not an example of Telnet timing out, but of intelligent network protocols responding to routing
issues in the network.
This summarization problem is a classic example of a black hole in a domain, which simply means traffic
passing through the network destined for that subnet is discarded at some point along the way.
Thankfully, ICMP informs sources of when their traffic is being discarded.
f. Do not forget to issue the no shutdown command on the R1 loopback 50 interface to re-enable routing
to this network.
R1( conf i g- i f ) # no shutdown

Ccnpv6 Route Lab4-2

Uploaded by

Copyright:

Available Formats

Ccnpv6 Route Lab4-2

Uploaded by

Document Information

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

Ccnpv6 Route Lab4-2

Uploaded by

Copyright:

Available Formats

All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved.

This document is Cisco Public Information. Page 1 of 21

You might also like