CCNPv6 ROUTE
CCNPv6 ROUTE
Configuration and Management of Networks ‐ 2012 Chapter
2 Lab 2-2,
EIGRP
Balancing
EIGRP
Configuration,
Bandwidth
and Load
Adjacencies
Chapter
2 Lab 2-2, EIGRP Load Balancing
Topology
The lab is built on the topology:
Topology
Objectives
Objectives
!
!
! Review
a basic
EIGRP
configuration.
Review
a basic
EIGRP
configuration.
! Explore
the EIGRP
topology
Explore
the EIGRP
topology
table.table.
!
! Identify
successors,
feasible
successors,
and feasible
distances.
Identify
successors,
feasible
successors,
and feasible
distances.
! Use
show
and debug
commands
the EIGRP
topology
Use
show
and debug
commands
for thefor
EIGRP
topology
table. table.
!
! Configure
and verify
equal-cost
load balancing
with EIGRP.
Configure
and verify
equal-cost
load balancing
with EIGRP.
!
! Configure
and verify
unequal-cost
load balancing
with EIGRP.
Configure
and verify
unequal-cost
load balancing
with EIGRP.
!
Background
Background
As aAs
senior
network
engineer,
you are
deploying
EIGRPEIGRP
in yourincorporation
and want
to want
evaluate
a senior
network
engineer,
youconsidering
are considering
deploying
your corporation
and
to evaluate
its
ability
to
converge
quickly
in
a
changing
environment.
You
are
also
interested
in
equal-cost
and
unequalits ability to converge quickly in a changing environment. You are also interested in equal-cost and unequalCCNPv6 ROUTE
cost cost
loadload
balancing
because
your network
contains
redundant
links. These
links are
notare
often
byused
otherby other
balancing
because
your network
contains
redundant
links. These
links
notused
often
link-state routing protocols because of high metrics. Because you are interested in testing the
EIGRP claims
Page 1 of 19
Page 1 of 19
that you have read about, you decide to implement and test on a set of three lab routers before deploying
EIGRP throughout your corporate network.
All contents
are Copyright
© 1992–2010
Cisco Systems,
Inc. All rights
This document
is Cisco Public
Information.
All contents
are Copyright
© 1992–2010
Cisco Systems,
Inc. Allreserved.
rights reserved.
This document
is Cisco
Public Information.
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 a 2801 or 2811) and
Instructions:
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 the addressing and serial links.
a. Create three loopback interfaces on each router and address them as 10.1.X.1/30, 10.1.X.5/30, and
10.1.X.9/30, where X is the number of the router. Use the following table or the initial configurations
located at the end of the lab.
shown in this lab.
Required Resources
!
3 routers Configuration and Management of Networks ‐ 2012 (Cisco 1841 with Cisco IOS Release 12.4(24)T1 Advanced IP Services or comparable)
!
Serial and console cables
Step 1: Configure the addressing and serial links.
a. Create three loopback interfaces on each router and address them as 10.1.X.1/30, 10.1.X.5/30, and
10.1.X.9/30, where X is the number of the router. Use the following table or the initial configurations
located at the end of the lab.
Router
Interface
IP Address/Mask
R1
Loopback11
10.1.1.1/30
R1
Loopback15
10.1.1.5/30
R1
Loopback19
10.1.1.9/30
R2
Loopback21
10.1.2.1/30
R2
Loopback25
10.1.2.5/30
R2
Loopback29
10.1.2.9/30
R3
Loopback31
10.1.3.1/30
R3
Loopback35
10.1.3.5/30
R3
Loopback39
10.1.3.9/30
R1(config)# interface Loopback 11
R1(config-if)# ip address 10.1.1.1 255.255.255.252
R1(config-if)# exit
R1(config)# interface Loopback 15
R1(config-if)# ip address 10.1.1.5 255.255.255.252
R1(config-if)# exit
R1(config)# interface Loopback 19
R1(config-if)# ip address 10.1.1.9 255.255.255.252
R1(config-if)# exit
R2(config)# interface Loopback 21
CCNPv6 ROUTE
R2(config-if)# ip address 10.1.2.1 255.255.255.252
R2(config-if)# exit
R2(config)#
interface
Loopback3125
R3(config)#
interface
Loopback
R2(config-if)#
ip
address
10.1.2.5255.255.255.252
255.255.255.252
R3(config-if)# ip address 10.1.3.1
R2(config-if)# exit
R3(config-if)#
exit
R2(config)# interface Loopback 29
R3(config)#
interface
Loopback
35
R2(config-if)#
ip address
10.1.2.9
255.255.255.252
CCNPv6ROUTE
ROUTE
CCNPv6
R3(config-if)#
ip
address
10.1.3.5
255.255.255.252
R2(config-if)# exit
R3(config-if)# exit
R3(config)#
interface
Loopback
31
R3(config)#
interface
Loopback
R3(config)#
interface
Loopback
3931
R3(config-if)#
ip
address
10.1.3.1
255.255.255.252
R3(config-if)#
ip
address
10.1.3.1
255.255.255.252
All contents are Copyright © 1992–2010
Cisco Systems, Inc.
All rights reserved.
This
document is Cisco Public Information.
R3(config-if)#
ip address
10.1.3.9
255.255.255.252
R3(config-if)#
exit
R3(config-if)#
exit
R3(config-if)# exit
b.
Page 2 of 19
R3(config)# interface
interface Loopback
Loopback 35
35
R3(config)#
R3(config-if)#
ip
address
10.1.3.5
255.255.255.252
R3(config-if)#
ip
address
10.1.3.5
255.255.255.252
Specify the addresses of the serial interfaces as shown
in the topology diagram. Set the clock rate to 64
R3(config-if)# exit
exit
R3(config-if)#
kb/s, and manually configure the interface bandwidth to 64 kb/s.
R3(config)# interface
interface Loopback
Loopback 39
39
R3(config)#
R3(config-if)#
ip
address
10.1.3.9
255.255.255.252
R3(config-if)#
ip
address
10.1.3.9
Note: If you have WIC-2A/S serial interfaces, the 255.255.255.252
maximum
clock rate is 128 kb/s. If you have WIC-2T
R3(config-if)#
exit
R3(config-if)#
exit
serial interfaces, the maximum clock rate is much higher (2.048 Mb/s or higher depending on the
hardware),
is more of
representative
of a modern
network
link.diagram.
However,
this
uses
64tokb/s
b. Specify
Specifywhich
theaddresses
addresses
of the
the serial
serial interfaces
interfaces
as shown
shown
in the
theWAN
topology
diagram.
b.
the
as
in
topology
Set
thelab
clock
rate
64
and kb/s,
128
kb/s
settings.
kb/s,and
andmanually
manuallyconfigure
configurethe
the interface
interface bandwidth
bandwidth to
to 64
64 kb/s.
kb/s.
R1(config)#
interface
Serial
0/0/0 the
Note:IfIfyou
youhave
haveWIC-2A/S
WIC-2A/S
serial interfaces,
interfaces,
the maximum
maximum clock
clock rate
rate is
is 128
128 kb/s.
kb/s. If you have WIC-2T
Note:
serial
R1(config-if)#
R1-->R2
serialinterfaces,
interfaces,description
themaximum
maximum clock
clock
rate is
is much
much higher
higher (2.048
(2.048 Mb/s
Mb/s or
or higher
higher depending
depending on the
serial
the
rate
R1(config-if)#
64000 of
hardware),which
whichclock
morerate
representative
of aa modern
modern network
network WAN
WAN link.
link. However,
However, this lab uses 64 kb/s
hardware),
isismore
representative
R1(config-if)# bandwidth 64
and128
128kb/s
kb/ssettings.
settings.
and
R1(config-if)# ip address 10.1.102.1 255.255.255.248
R1(config)# interface
interface
Serial 0/0/0
0/0/0
R1(config)#
Serial
R1(config-if)#
no shutdown
R1(config-if)#
description
R1-->R2
R1(config-if)#
description
R1-->R2
R1(config-if)# exit
R1(config-if)#
clockSerial
rate 64000
64000
R1(config-if)#
clock
rate
R1(config)#
interface
0/0/1
R1(config-if)#
bandwidth 64
64
R1(config-if)#
bandwidth
R1(config-if)#
description
R1-->R3
R1(config-if)#
ip address
address
10.1.102.1 255.255.255.248
255.255.255.248
R1(config-if)#
ip
R1(config-if)#
bandwidth
64 10.1.102.1
R1(config-if)# no
no shutdown
shutdown
R1(config-if)#
R1(config-if)# ip address 10.1.103.1 255.255.255.248
R1(config-if)# exit
exit
R1(config-if)#
R1(config-if)#
no shutdown
R1(config)# interface
interface
Serial 0/0/1
0/0/1
R1(config)#
Serial
R1(config-if)#
exit
R1(config-if)#
description R1-->R3
R1-->R3
R1(config-if)#
description
R1(config-if)# bandwidth
bandwidth 64
64
R1(config-if)#
R2(config)#
interface
Serial10.1.103.1
0/0/0
R1(config-if)#
ip address
address
10.1.103.1
255.255.255.248
R1(config-if)#
ip
255.255.255.248
R2(config-if)#
description
R2-->R1
R1(config-if)#
R1(config-if)# no
no shutdown
shutdown
R2(config-if)#
bandwidth
64
R1(config-if)#
exit
R1(config-if)#
exit
R2(config-if)# ip address 10.1.102.2 255.255.255.248
R2(config-if)#
no shutdown
R2(config)#
Serial
R2(config)# interface
interface
Serial 0/0/0
0/0/0
R2(config-if)#
description
R2(config-if)#
description R2-->R1
R2-->R1
R2(config-if)#
exit
R1(config)# interface Serial 0/0/0
R1(config-if)# description R1-->R2
R1(config-if)# clock rate 64000
R1(config-if)# bandwidth 64
R1(config-if)# Configuration and Management of Networks ‐ 2012 ip address 10.1.102.1 255.255.255.248
R1(config-if)# no shutdown
R1(config-if)# exit
R1(config)# interface Serial 0/0/1
R1(config-if)# description R1-->R3
R1(config-if)# bandwidth 64
R1(config-if)# ip address 10.1.103.1 255.255.255.248
R1(config-if)# no shutdown
R1(config-if)# exit
R2(config)# interface Serial 0/0/0
R2(config-if)# description R2-->R1
R2(config-if)# bandwidth 64
R2(config-if)# ip address 10.1.102.2 255.255.255.248
R2(config-if)# no shutdown
R2(config-if)# exit
R2(config)# interface Serial 0/0/1
R2(config-if)# description R2-->R3
R2(config-if)# clock rate 64000
R2(config-if)# bandwidth 64
R2(config-if)# ip address 10.1.203.2 255.255.255.248
R2(config-if)# no shutdown
R2(config-if)# exit
R3(config)# interface Serial 0/0/0
R3(config-if)# description R3-->R1
R3(config-if)# clock rate 64000
R3(config-if)# bandwidth 64
R3(config-if)# ip address 10.1.103.3 255.255.255.248
R3(config-if)# no shutdown
R3(config-if)# exit
R3(config)# interface Serial 0/0/1
R3(config-if)# description R3-->R2
R3(config-if)# bandwidth 64
R3(config-if)#
ip address 10.1.203.3 255.255.255.248
CCNPv6
ROUTE
R3(config-if)# no shutdown
R3(config-if)# exit
All contents are
1992–2010 Cisco
All rights
reserved.
This
document
is Ciscoconnected
Public Information.
c.Copyright
Verify©connectivity
bySystems,
pingingInc.
across
each
of the
local
networks
to each
router.
Page 3 of 19
d. Issue the show interfaces description command on each router. This command displays a brief listing
of the interfaces, their status, and a description (if a description is configured). Router R1 is shown as an
example.
R1# show interfaces description
Interface
Status
Fa0/0
admin down
Fa0/1
admin down
Se0/0/0
up
Se0/0/1
up
Vl1
up
Lo11
up
Lo15
up
Lo19
up
Protocol Description
down
down
up
R1-->R2
up
R1-->R3
down
up
up
up
e. Issue the show protocols command on each router. This command displays a brief listing of the
interfaces, their status, and the IP address and subnet mask configured (in prefix format /xx) for each
interface. Router R1 is shown as an example.
R1# show protocols
Global values:
Internet Protocol routing is enabled
FastEthernet0/0 is administratively down, line protocol is down
FastEthernet0/1 is administratively down, line protocol is down
Serial0/0/0 is up, line protocol is up
Internet address is 10.1.102.1/29
Serial0/0/1 is up, line protocol is up
Internet address is 10.1.103.1/29
Vlan1 is up, line protocol is down
Loopback11 is up, line protocol is up
Internet address is 10.1.1.1/30
Loopback15 is up, line protocol is up
Internet address is 10.1.1.5/30
Loopback19 is up, line protocol is up
Fa0/1
Fa0/0
Se0/0/0
Fa0/1
Se0/0/1
Se0/0/0
Se0/0/1
Vl1
Vl1
Lo11
Lo11
Lo15
Lo15
Lo19
Lo19
admin
down
down
admin down
down
up
up
R1-->R2
admin down
down
up
R1-->R3
up
up
R1-->R2
up
R1-->R3
up
down
down
up
up
Configuration and Management of Networks ‐ 2012 up
up
up
up
up
up
up
up
up
up
e. Issue the show protocols command on each router. This command displays a brief listing of the
e. Issue the show protocols command on each router. This command displays a brief listing of the
interfaces, their status, and the IP address and subnet mask configured (in prefix format /xx) for each
interfaces, their status, and the IP address and subnet mask configured (in prefix format /xx) for each
interface. Router R1 is shown as an example.
interface. Router R1 is shown as an example.
R1# show protocols
R1# show protocols
Global
Globalvalues:
values:
Internet
InternetProtocol
Protocol routing
routing is
is enabled
enabled
FastEthernet0/0
is
administratively
down, line
line protocol
protocolisisdown
down
FastEthernet0/0 is administratively down,
FastEthernet0/1
down, line
line protocol
protocolisisdown
down
FastEthernet0/1 is
is administratively
administratively down,
Serial0/0/0
is
up,
line
protocol
is
up
Serial0/0/0 is up, line protocol is up
Internet
Internetaddress
address is
is 10.1.102.1/29
10.1.102.1/29
Serial0/0/1
up
Serial0/0/1is
is up,
up, line
line protocol
protocol is up
Internet
Internetaddress
address is
is 10.1.103.1/29
10.1.103.1/29
Vlan1isisup,
up,line
line protocol
protocol is
is down
Vlan1
Loopback11is
isup,
up, line
line protocol
protocol is up
Loopback11
up
Internetaddress
address is
is 10.1.1.1/30
10.1.1.1/30
Internet
Loopback15is
isup,
up, line
line protocol
protocol is
is up
Loopback15
up
Internetaddress
address is
is 10.1.1.5/30
10.1.1.5/30
Internet
Loopback19is
isup,
up, line
line protocol
protocol is
Loopback19
is up
up
Internet
address
is
10.1.1.9/30
Internet address is 10.1.1.9/30
Step
ConfigureEIGRP.
EIGRP.
Step
2:2:
Configure
a. Enable EIGRP AS 100 for all interfaces on R1 and R2 using the commands used in the previous EIGRP
a. Enable EIGRP AS 100 for all interfaces on R1 and R2 using the commands used in the previous EIGRP
lab. Do not enable EIGRP yet on R3. For your reference, these are the commands which can be used:
lab. Do not enable EIGRP yet on R3. For your reference, these are the commands which can be used:
R1(config)# router eigrp 100
R1(config)#
router eigrp
10010.0.0.0
R1(config-router)#
network
R1(config-router)# network 10.0.0.0
R2(config)# router eigrp 100
R2(config)#
router eigrp
10010.0.0.0
R2(config-router)#
network
R2(config-router)# network 10.0.0.0
b. Use the debug ip eigrp 100 command to watch EIGRP install the routes in the routing table when your
b. Use
the debug
ipadjacent.
eigrp 100
command
to similar
watch to
EIGRP
install the routes in the routing table when your
routers
become
You
get output
the following.
routers
become
adjacent.
You
get
output
similar
to
the
following.
R3# debug ip eigrp 100
IP-EIGRP
Route
Events
R3#
debug ip
eigrp
100 debugging is on
R3# confRoute
t
IP-EIGRP
Events debugging is on
Enter
commands, one per line. End with CNTL/Z.
R3#
confconfiguration
t
Enter
configuration
commands,
one per line. End with CNTL/Z.
CCNPv6
ROUTE
R3(config)# router eigrp 100
CCNPv6 ROUTE
R3(config)# router eigrp 100
R3(config-router)#
network
10.0.0.0
R3(config-router)#
network
10.0.0.0
All contents are Copyright © 1992–2010 Cisco
Systems, Inc.
All rights reserved. This document is Cisco Public Information.
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 4 of 19
Page 4 of 19
R3(config-router)#
R3(config-router)#
*Feb 4 18:44:57.367:
18:44:57.367: %DUAL-5-NBRCHANGE:
%DUAL-5-NBRCHANGE: IP-EIGRP(0)
IP-EIGRP(0) 100:
100: Neighbor
Neighbor 10.1.103.1
10.1.103.1
(Serial0/0/0) is
is up:
up: new
new adjacency
adjacency
(Serial0/0/0)
18:44:57.367: %DUAL-5-NBRCHANGE:
%DUAL-5-NBRCHANGE: IP-EIGRP(0)
IP-EIGRP(0) 100:
100: Neighbor
Neighbor 10.1.203.2
10.1.203.2
*Feb 4 18:44:57.367:
(Serial0/0/1) is
is up:
up: new
new adjacency
adjacency
(Serial0/0/1)
*Feb 4 18:44:57.371:
18:44:57.371: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): Processing
Processing
UPDATE packet
packet
incoming UPDATE
18:44:57.379: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): Processing
Processing
*Feb 4 18:44:57.379:
UPDATE packet
packet
incoming UPDATE
*Feb 4 18:44:57.427:
18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): Processing
Processing
UPDATE packet
packet
incoming UPDATE
18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): Int
Int
*Feb 4 18:44:57.427:
10.1.102.0/29 MM 41024000
41024000 -- 40000000
40000000 1024000
1024000 SM
SM 40512000
40512000 -- 40000000
40000000 512000
512000
10.1.102.0/29
18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): route
route installed
installed
*Feb 4 18:44:57.427:
10.1.102.0 ()
()
for 10.1.102.0
18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): Int
Int 10.1.1.0/30
10.1.1.0/30
*Feb 4 18:44:57.427:
40000000 640000
640000 SM
SM 128256
128256 -- 256
256 128000
128000
M40640000 - 40000000
18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): route
route installed
installed
*Feb 4 18:44:57.427:
for 10.1.1.0
10.1.1.0 ()
()
*Feb 4 18:44:57.427:
18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): Int
Int 10.1.1.4/30
10.1.1.4/30
M 40640000 - 40000000
40000000 640000
640000 SM
SM 128256
128256 -- 256
256 128000
128000
*Feb 4 18:44:57.427:
18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): route
route installed
installed
for 10.1.1.4
10.1.1.4 ()
()
*Feb 4 18:44:57.431:
18:44:57.431: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): Int
Int 10.1.1.8/30
10.1.1.8/30
M40640000 - 40000000
40000000 640000
640000 SM
SM 128256
128256 -- 256
256 128000
128000
*Feb 4 18:44:57.431:
18:44:57.431: IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): route
route installed
installed
for 10.1.1.8
10.1.1.8 ()
()
<output omitted>
omitted>
10.1.102.0/29 M 41024000 - 40000000 1024000 SM 40512000 - 40000000 512000
*Feb 4 18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100): route installed
for 10.1.102.0 ()
*Feb 4 18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.1.0/30
M40640000 - Configuration and Management of Networks ‐ 2012 40000000 640000 SM 128256 - 256 128000
*Feb 4 18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100): route installed
for 10.1.1.0 ()
*Feb 4 18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.1.4/30
M 40640000 - 40000000 640000 SM 128256 - 256 128000
*Feb 4 18:44:57.427: IP-EIGRP(Default-IP-Routing-Table:100): route installed
for 10.1.1.4 ()
*Feb 4 18:44:57.431: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.1.8/30
M40640000 - 40000000 640000 SM 128256 - 256 128000
*Feb 4 18:44:57.431: IP-EIGRP(Default-IP-Routing-Table:100): route installed
for 10.1.1.8 ()
<output omitted>
Essentially, the EIGRP DUAL state machine has just computed the topology table for these routes and
installed them in the routing table.
CCNPv6 ROUTE
c. ROUTE
Check to see that these routes exist in the routing table with the show ip route command.
CCNPv6
C
10.1.103.0/29 is directly connected, Serial0/0/1
R1# show ip route
C
10.1.102.0/29 is directly connected, Serial0/0/0
Codes:
C - connected,
S - static,
R - RIP,
M - mobile, B - BGP
10.1.103.0/29
is
directly
connected,
Serial0/0/1
DC
10.1.203.0/29
[90/41024000]
via 10.1.103.3,
00:19:28, Serial0/0/1
D - EIGRP, is
EX directly
- EIGRP external,
- OSPF, IA - OSPF inter area
C
10.1.102.0/29
connected,O Serial0/0/0
[90/41024000]
via
10.1.102.2,
00:19:28,
Serial0/0/0
N1 - OSPF NSSA
external type
1, N2 - OSPF00:19:28,
NSSA
external
type 2
D
10.1.203.0/29
[90/41024000]
via 10.1.103.3,
Serial0/0/1
E1
OSPF
external
type
1,
E2
OSPF
external
type
2
[90/41024000]
via
10.1.102.2,
00:19:28,
Serial0/0/0
d. After you have full adjacency between the routers, ping all the remote loopbacks to ensure full
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
or
the
following
Tclarea,
script.
If you
have
never
Tclloopbacks
scripts
a refresher,
d. connectivity
After you have
full
between
the routers,
ping all
the used
remote
toneed
ensure
full
iause
- adjacency
IS-IS
inter
*
- candidate
default,
U - or
per-user
static see Lab
1–1.
route
connectivity or use the following Tcl script. If you have never used Tcl scripts or need a refresher, see Lab
1–1. tclsh o - ODR, P - periodic downloaded static route
R1#
R1#Gateway
tclsh of last resort is not set
foreach
address {
10.1.1.1
foreach
address {is variably subnetted, 12 subnets, 2 masks
10.0.0.0/8
10.1.1.5
10.1.1.1
D
10.1.3.8/30 [90/40640000] via 10.1.103.3, 00:19:28, Serial0/0/1
10.1.1.9
10.1.1.5
D
10.1.2.8/30 [90/40640000] via 10.1.102.2, 00:21:59, Serial0/0/0
10.1.2.1
10.1.1.9
C
10.1.1.8/30 is directly connected, Loopback19
10.1.2.5
10.1.2.1
D
10.1.3.0/30 [90/40640000] via 10.1.103.3, 00:19:28, Serial0/0/1
10.1.2.9
10.1.2.5
D
10.1.2.0/30 [90/40640000] via 10.1.102.2, 00:21:59, Serial0/0/0
10.1.3.1
10.1.2.9
C
10.1.1.0/30 is directly connected, Loopback11
10.1.3.5
10.1.3.1
D
10.1.3.4/30 [90/40640000] via 10.1.103.3, 00:19:28, Serial0/0/1
10.1.3.5
10.1.3.9
D
10.1.2.4/30 [90/40640000] via 10.1.102.2, 00:21:59, Serial0/0/0
CCNPv6
ROUTE
10.1.3.9
10.1.102.1
C
10.1.1.4/30 is directly connected, Loopback15
10.1.102.1
10.1.102.2
10.1.102.2
10.1.103.1
C are Copyright
10.1.103.0/29
is directly
connected,
Serial0/0/1
All contents
© 1992–2010 Cisco Systems,
Inc. All rights reserved.
This document
is Cisco Public Information.
Page 5 of 19
10.1.103.1
10.1.103.3
C
10.1.102.0/29
is
directly
connected,
Serial0/0/0
10.1.103.3
10.1.203.2
D
10.1.203.0/29 [90/41024000] via 10.1.103.3, 00:19:28, Serial0/0/1
10.1.203.2
10.1.203.3
[90/41024000] via 10.1.102.2, 00:19:28, Serial0/0/0
}10.1.203.3
{ ping $address }
}
{
ping
$address
}
d. After you have full adjacency between the routers, ping all the remote loopbacks to ensure full
You should receive ICMP echo replies for each address pinged. Make sure that you run the Tcl script on
connectivity
or useICMP
the following
Tcl script.
If you
havepinged.
never used
Tcl
scripts
need
a refresher,
You
should receive
echo replies
for each
address
Make
sure
that or
you
run the
Tcl scriptsee
on Lab
each
router
and
verify
connectivity
before
you
continue
with
the
lab.
1–1.router and verify connectivity before you continue with the lab.
each
e. Verify
EIGRP neighbor relationships with the show ip eigrp neighbors command.
R1# the
tclsh
e. Verify
the
EIGRP neighbor relationships with the show ip eigrp neighbors command.
R1# show ip eigrp neighbors
R1#
show ip
eigrp {neighbors
foreach
address
IP-EIGRP
neighbors
for process 100
IP-EIGRP
neighbors for process 100
10.1.1.1
HH
Address
Interface
HoldUptime
Uptime SRTT
SRTT RTO
RTOQ QSeqSeq
Address
Interface
Hold
10.1.1.5
(sec)
(ms)
Cnt
(sec)
(ms)
Cnt
NumNum
0010.1.1.9
10.1.102.2
Se0/0/0
10
00:00:22
1
5000
2
10.1.102.2
Se0/0/0
10 00:00:22
1 5000 2 0 0
1110.1.2.1
10.1.103.3
Se0/0/1
1300:04:36
00:04:36 2424 2280
22800 014 14
10.1.103.3
Se0/0/1
13
10.1.2.5
10.1.2.9
R2#
show
neighbors
R2#
show ip
ip eigrp
eigrp neighbors
10.1.3.1
IP-EIGRP
neighbors
for process
process 100
100
IP-EIGRP
neighbors
for
HH10.1.3.5
Address
Interface
HoldUptime
Uptime SRTT
SRTT RTO
RTOQ QSeqSeq
Address
Interface
Hold
10.1.3.9
(sec)
(ms)
Cnt
(sec)
(ms)
Cnt
NumNum
0010.1.102.1
10.1.102.1
Se0/0/0
00:00:37 1 1 5000
50001 122 22
10.1.102.1
Se0/0/0
141400:00:37
1110.1.102.2
10.1.203.3
Se0/0/1
00:03:29 143
143 2280
22800 015 15
10.1.203.3
Se0/0/1
111100:03:29
10.1.103.1
10.1.103.3
R3#
neighbors
R3# show
show ip eigrp neighbors
10.1.203.2
IP-EIGRP neighbors
neighbors for
IP-EIGRP
for process
process 100
100
10.1.203.3
Address
Interface
Hold
HH
Address
Interface
HoldUptime
Uptime SRTT
SRTT RTO
RTOQ QSeqSeq
} { ping $address }
(sec)
(ms)
Cnt
NumNum
(sec)
(ms)
Cnt
10.1.203.2
Se0/0/1
141400:03:43
241
11You10.1.203.2
Se0/0/1
00:03:43
241
2280
18 on
should receive ICMP echo replies
for each address pinged.
Make
sure that
you 2280
run
the 0
Tcl018
script
10.1.103.1
Se0/0/0
141400:05:05
3838 2280
0 017 17
00each
10.1.103.1
Se0/0/0
00:05:05
2280
router and verify connectivity before you continue with the lab.
e. Verify the EIGRP neighbor relationships with the show ip eigrp neighbors command.
R1# show ip eigrp neighbors
IP-EIGRP neighbors for process 100
R2# show ip eigrp neighbors
IP-EIGRP neighbors for process 100
H
Address
Interface
0
1
Hold Uptime
SRTT
RTO Q
(sec)
(ms)
Cnt
Configuration and Management of Networks ‐ 2012 10.1.102.1
Se0/0/0
14 00:00:37
1 5000 1
10.1.203.3
Se0/0/1
11 00:03:29 143 2280 0
R3# show ip eigrp neighbors
IP-EIGRP neighbors for process 100
H
Address
Interface
1
0
10.1.203.2
10.1.103.1
CCNPv6 ROUTE
CCNPv6 ROUTE
Se0/0/1
Se0/0/0
Hold Uptime
SRTT
(sec)
(ms)
14 00:03:43 241
14 00:05:05
38
RTO
Q
Cnt
2280 0
2280 0
Seq
Num
22
15
Seq
Num
18
17
Step3:3:Examine
Examine
the
EIGRP
topology
table.
Step
the
EIGRP
topology
table.
EIGRP
builds
a topology
table
containing
successor
routes.
The
course
content
covered
a. a. EIGRP
builds
a topology
table
containing
all all
successor
routes.
The
course
content
covered
thethe
vocabulary
for
EIGRP
routes
in
the
topology
table.
What
is
the
feasible
distance
of
route
10.1.1.0/30
vocabulary for EIGRP routes in the topology table. What is the feasible distance of route 10.1.1.0/30 in in
topology table
following
output?
thethe
R3R3
in in
thethe
following
output?
All contents are Copyright
©topology
1992–2010table
Cisco Systems,
Inc. All rights
reserved. This document is Cisco Public Information.
Page 6 of 19
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
R3#show
showipipeigrp
eigrptopology
topology
R3#
IP-EIGRP
Topology
Tablefor
forAS(100)/ID(10.1.3.9)
AS(100)/ID(10.1.3.9)
IP-EIGRP Topology Table
Codes:P
Codes:
r
Pr-
-Passive,
Passive,A A- -Active,
Active,
Update,
Q Query,
- Query,
- Reply,
U U
- Update,
Q R -R Reply,
-reply
replyStatus,
Status,s s
sia
Status
- sia Status
10.1.3.8/30,1 1successors,
successors,FDFD
128256
P P10.1.3.8/30,
isis
128256
via
Connected,
Loopback39
via Connected, Loopback39
10.1.2.8/30,1 1successors,
successors,FDFD
40640000
P P10.1.2.8/30,
isis
40640000
via
10.1.203.2
(40640000/128256),
Serial0/0/1
via 10.1.203.2 (40640000/128256), Serial0/0/1
10.1.1.8/30,1 1successors,
successors,FDFD
40640000
P P10.1.1.8/30,
isis
40640000
via10.1.103.1
10.1.103.1(40640000/128256),
(40640000/128256),
Serial0/0/0
via
Serial0/0/0
P
10.1.3.0/30,
1
successors,
FD
is
128256
P 10.1.3.0/30, 1 successors, FD is 128256
viaConnected,
Connected,Loopback31
Loopback31
via
10.1.2.0/30,1 1successors,
successors,FDFD
40640000
P P10.1.2.0/30,
isis
40640000
via
10.1.203.2
(40640000/128256),
Serial0/0/1
via 10.1.203.2 (40640000/128256), Serial0/0/1
10.1.1.0/30,1 1successors,
successors,FDFD
40640000
P P10.1.1.0/30,
isis
40640000
via10.1.103.1
10.1.103.1(40640000/128256),
(40640000/128256),
Serial0/0/0
via
Serial0/0/0
10.1.3.4/30,1 1successors,
successors,FDFD
128256
P P10.1.3.4/30,
isis
128256
viaConnected,
Connected,Loopback35
Loopback35
via
P
10.1.2.4/30,
1
successors,
40640000
P 10.1.2.4/30, 1 successors, FDFD
isis
40640000
via10.1.203.2
10.1.203.2(40640000/128256),
(40640000/128256),
Serial0/0/1
via
Serial0/0/1
10.1.1.4/30,1 1successors,
successors,FDFD
40640000
P P10.1.1.4/30,
isis
40640000
via10.1.103.1
10.1.103.1(40640000/128256),
(40640000/128256),
Serial0/0/0
via
Serial0/0/0
10.1.103.0/29,1 1successors,
successors,
40512000
P P10.1.103.0/29,
FDFD
isis
40512000
viaConnected,
Connected,Serial0/0/0
Serial0/0/0
via
10.1.102.0/29,2 2successors,
successors,
41024000
P P10.1.102.0/29,
FDFD
isis
41024000
via10.1.103.1
10.1.103.1(41024000/40512000),
(41024000/40512000),
Serial0/0/0
via
Serial0/0/0
via10.1.203.2
10.1.203.2(41024000/40512000),
(41024000/40512000),
Serial0/0/1
via
Serial0/0/1
10.1.203.0/29,1 1successors,
successors,
40512000
P P10.1.203.0/29,
FDFD
isis
40512000
viaConnected,
Connected,Serial0/0/1
Serial0/0/1
via
The
most
important
thing
is the
successor
routes
in the
passive
state
both
b. b. The
most
important
thing
is the
twotwo
successor
routes
in the
passive
state
on on
R3.R3.
R1 R1
andand
R2 R2
areare
both
advertising
their
connected
subnet
10.1.102.0/30.
Because
both
routes
have
same
feasible
advertising
their
connected
subnet
of of
10.1.102.0/30.
Because
both
routes
have
thethe
same
feasible
distance
41024000,
both
installed
in the
topology
table.
This
distance
of 41024000
reflects
distance
of of
41024000,
both
areare
installed
in the
topology
table.
This
distance
of 41024000
reflects
thethe
composite
metric
more
granular
properties
about
path
to the
destination
network.
view
composite
metric
of of
more
granular
properties
about
thethe
path
to the
destination
network.
CanCan
youyou
view
thethe
metrics
before
composite
metric
is computed?
metrics
before
thethe
composite
metric
is computed?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
All All
contents
areare
Copyright
© 1992–2010
Cisco
Systems,
Inc.Inc.
All rights
reserved.
ThisThis
document
is Cisco
Public
Information.
contents
Copyright
© 1992–2010
Cisco
Systems,
All rights
reserved.
document
is Cisco
Public
Information.
PagePage
7 of 19
7 of 19
CCNPv6 ROUTE
CCNPv6 ROUTE
Configuration and Management of Networks ‐ 2012 c. Use the show ip eigrp topology 10.1.102.0/29 command to view the information that EIGRP has
c. Use
the show
eigrp
topology
command to view the information that EIGRP has
received
aboutipthe
route
from R110.1.102.0/29
and R2.
received
about
the
route
from
R1
and
R2.
R3# show ip eigrp topology 10.1.102.0/29
R3#
show ip
IP-EIGRP
(ASeigrp
100):topology
Topology10.1.102.0/29
entry for 10.1.102.0/29
IP-EIGRP
(ASPassive,
100): Topology
entry for
State is
Query origin
flag10.1.102.0/29
is 1, 2 Successor(s), FD is 41024000
State
is Descriptor
Passive, Query
origin flag is 1, 2 Successor(s), FD is 41024000
Routing
Blocks:
Routing
Descriptor
Blocks: from 10.1.103.1, Send flag is 0x0
10.1.103.1
(Serial0/0/0),
10.1.103.1
(Serial0/0/0),
from 10.1.103.1, SendRoute
flag is
is Internal
0x0
Composite
metric is (41024000/40512000),
Composite
metric is (41024000/40512000), Route is Internal
Vector metric:
Vector
metric:
Minimum
bandwidth is 64 Kbit
Minimum
bandwidth
is 64
Kbit
Total delay
is 40000
microseconds
Total
delay is
microseconds
Reliability
is 40000
255/255
Reliability
is 255/255
Load is 1/255
Load
is 1/255
Minimum
MTU is 1500
Minimum
MTUisis1 1500
Hop count
Hop count
is 1
10.1.203.2
(Serial0/0/1),
from 10.1.203.2, Send flag is 0x0
10.1.203.2
(Serial0/0/1),
from 10.1.203.2, SendRoute
flag is
is Internal
0x0
Composite metric is (41024000/40512000),
Composite
metric is (41024000/40512000), Route is Internal
Vector metric:
Vector
metric:
Minimum
bandwidth is 64 Kbit
Minimum
bandwidth
is 64
Kbit
Total delay
is 40000
microseconds
Total
delay is
microseconds
Reliability
is 40000
255/255
Reliability
is 255/255
Load is 1/255
Load is 1/255
Minimum MTU is 1500
Minimum MTU is 1500
Hop count is 1
Hop count is 1
The output of this command shows the following information regarding EIGRP:
The output of this command shows the following information regarding EIGRP:
The bandwidth
bandwidthmetric
metricrepresents
representsthe
theminimum
minimumbandwidth
bandwidth
among
links
comprising
path
to the
!! The
among
allall
links
comprising
thethe
path
to the
destination
network.
destination network.
!!
!!
The delay
delaymetric
metricrepresents
representsthe
thetotal
totaldelay
delayover
overthe
thepath.
path.
The
The minimum
minimumMTU
MTUrepresents
representsthe
thesmallest
smallestMTU
MTUalong
along
the
path.
The
the
path.
!!
you do
donot
nothave
havefull
fullknowledge
knowledgeofofyour
yournetwork,
network,you
you
can
use
the
hop
count
information
to check
IfIf you
can
use
the
hop
count
information
to check
how many
manyLayer
Layer33devices
devicesare
arebetween
betweenthe
therouter
routerand
andthe
the
destination
network.
how
destination
network.
Step 4:
4: Observe
Observe equal-cost
equal-costload
loadbalancing.
balancing.
Step
EIGRP produces
producesequal-cost
equal-costload
loadbalancing
balancingtotothe
thedestination
destinationnetwork
network
10.1.102.0/29
from
Two
equal-cost
EIGRP
10.1.102.0/29
from
R1.R1.
Two
equal-cost
paths are
are available
availableto
tothis
thisdestination
destinationper
perthe
thetopology
topologytable
tableoutput
output
above.
paths
above.
Use the
the traceroute
traceroute10.1.102.1
10.1.102.1command
commandtotoview
viewthe
thehops
hopsfrom
from
this
address.
Notice
both
a. Use
R3R3
to to
this
R1R1
IP IP
address.
Notice
thatthat
both
R1 and
and R2
R2 are
arelisted
listedas
ashops
hopsbecause
becausethere
thereare
aretwo
twoequal-cost
equal-cost
paths
and
packets
can
reach
network
R1
paths
and
packets
can
reach
thisthis
network
via either
either link.
link.
via
R3# traceroute
traceroute 10.1.102.1
10.1.102.1
R3#
Type
Type escape
escape sequence
sequence to
to abort.
abort.
Tracing
Tracing the
the route
route to
to 10.1.102.1
10.1.102.1
11 10.1.203.2
10.1.203.2 12
12 msec
msec
10.1.103.1
10.1.103.1 12
12 msec
msec
10.1.203.2
10.1.203.2 12
12 msec
msec
Recent
(CEF),
which,
byby
default,
performs
perRecent Cisco
CiscoIOS
IOSreleases
releasesenable
enableCisco
CiscoExpress
ExpressForwarding
Forwarding
(CEF),
which,
default,
performs
perdestination
without
thethe
need
forfor
route
processing.
destinationload
loadbalancing.
balancing.CEF
CEFallows
allowsfor
forvery
veryrapid
rapidswitching
switching
without
need
route
processing.
However,
not
see
load
balancing
occurring
on on
a a
However, ifif you
youwere
weretotoping
pingthe
thedestination
destinationnetwork,
network,you
youwould
would
not
see
load
balancing
occurring
CCNPv6 ROUTE
packet
one
flow.
packet level
level because
becauseCEF
CEFtreats
treatsthe
theentire
entireseries
seriesofofpings
pingsasas
one
flow.
CEF on R3 overrides the per-packet balancing behavior of process switching with per-destination load
Page 8 of 19
Page 8 of 19
balancing.
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
b. To see the full effect of EIGRP equal-cost load balancing, temporarily disable CEF and route caching so
that all IP packets are processed individually and not fast-switched by CEF.
R3(config)# no ip cef
R3(config)# interface S0/0/0
R3(config-if)# no ip route-cache
R3(config-if)# interface S0/0/1
R3(config-if)# no ip route-cache
Note: Typically, you would not disable CEF in a production network. It is done here only to illustrate load
balancing. Another way to demonstrate per-packet load balancing, that does not disable CEF, is to use
the per-packet load balancing command ip load-share per-packet on outgoing interfaces S0/0/0 and
CCNPv6 ROUTE
Configuration and Management of Networks ‐ 2012 CEF on R3 overrides the per-packet balancing behavior of process switching with per-destination load
balancing.
b. To see the full effect of EIGRP equal-cost load balancing, temporarily disable CEF and route caching so
that all IP packets are processed individually and not fast-switched by CEF.
R3(config)# no ip cef
R3(config)# interface S0/0/0
R3(config-if)# no ip route-cache
R3(config-if)# interface S0/0/1
R3(config-if)# no ip route-cache
Note: Typically, you would not disable CEF in a production network. It is done here only to illustrate load
balancing. Another way to demonstrate per-packet load balancing, that does not disable CEF, is to use
the per-packet load balancing command ip load-share per-packet on outgoing interfaces S0/0/0 and
S0/0/1.
c.
Verify load balancing with the debug ip packet command, and then ping 10.1.102.1. You see output
similar to the following:
R3# debug ip packet
IP packet debugging is on
R3# ping 10.1.102.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.102.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms
R3#
*Feb 5 12:58:27.943: IP: tableid=0, s=10.1.103.3 (local), d=10.1.102.1
(Serial0/0/0), routed via RIB
*Feb 5 12:58:27.943: IP: s=10.1.103.3 (local), d=10.1.102.1 (Serial0/0/0),
len 100, sending
*Feb 5 12:58:27.947: IP: tableid=0, s=10.1.102.1 (Serial0/0/0), d=10.1.103.3
(Serial0/0/0), routed via RIB
*Feb 5 12:58:27.947: IP: s=10.1.102.1 (Serial0/0/0), d=10.1.103.3
(Serial0/0/0), len 100, rcvd 3
*Feb 5 12:58:27.947: IP: tableid=0, s=10.1.203.3 (local), d=10.1.102.1
(Serial0/0/1), routed via RIB
*Feb 5 12:58:27.947: IP: s=10.1.203.3 (local), d=10.1.102.1 (Serial0/0/1),
len 100, sending
<output omitted>
Notice that EIGRP load-balances between Serial0/0/0 (s=10.1.103.3) and Serial0/0/1 (s=10.1.203.3). This
CCNPv6
ROUTE
behavior
is part of EIGRP. It can help utilize underused links in a network, especially during periods of
congestion.
Step 5: Analyze alternate EIGRP paths not in the topology table.
a. Perhaps you expected to see more paths to the R1 and R2 loopback networks in the R3 topology table.
Why are these routes not shown in the topology table?
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 9 of 19
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
b. Issue the show ip eigrp topology all-links command to see all routes that R3 has learned through
EIGRP. This command shows all entries that EIGRP holds on this router for networks in the topology,
including the exit serial interface and IP address of the next hop to each destination network, and the
serial number (serno) that uniquely identifies a destination network in EIGRP.
R3# show ip eigrp topology all-links
IP-EIGRP Topology Table for AS(100)/ID(10.1.3.9)
_______________________________________________________________________________
_______________________________________________________________________________
_______________________________________________________________________________
Configuration and Management of Networks ‐ 2012 b. Issue the show ip eigrp topology all-links command to see all routes that R3 has learned through
EIGRP. This command shows all entries that EIGRP holds on this router for networks in the topology,
including the exit serial interface and IP address of the next hop to each destination network, and the
serial number (serno) that uniquely identifies a destination network in EIGRP.
R3# show ip eigrp topology all-links
IP-EIGRP Topology Table for AS(100)/ID(10.1.3.9)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 10.1.3.0/30, 1 successors, FD is 128256, serno 1
via Connected, Loopback31
P 10.1.3.4/30, 1 successors, FD is 128256, serno 2
via Connected, Loopback35
P 10.1.3.8/30, 1 successors, FD is 128256, serno 3
via Connected, Loopback39
P 10.1.2.8/30, 1 successors, FD is 40640000, serno 24
via 10.1.203.2 (40640000/128256), Serial0/0/1
via 10.1.103.1 (41152000/40640000), Serial0/0/0
P 10.1.1.8/30, 1 successors, FD is 40640000, serno 17
via 10.1.103.1 (40640000/128256), Serial0/0/0
via 10.1.203.2 (41152000/40640000), Serial0/0/1
P 10.1.2.0/30, 1 successors, FD is 40640000, serno 22
via 10.1.203.2 (40640000/128256), Serial0/0/1
via 10.1.103.1 (41152000/40640000), Serial0/0/0
P 10.1.1.0/30, 1 successors, FD is 40640000, serno 15
via 10.1.103.1 (40640000/128256), Serial0/0/0
via 10.1.203.2 (41152000/40640000), Serial0/0/1
P 10.1.2.4/30, 1 successors, FD is 40640000, serno 23
via 10.1.203.2 (40640000/128256), Serial0/0/1
CCNPv6 ROUTE via 10.1.103.1 (41152000/40640000), Serial0/0/0
P 10.1.1.4/30, 1 successors, FD is 40640000, serno 16
via
Serial0/0/0
via 10.1.103.1
10.1.203.2 (40640000/128256),
(41024000/40512000),
Serial0/0/1
via 10.1.203.2
(41152000/40640000),
Serial0/0/1
P 10.1.203.0/29,
1 successors,
FD is 40512000,
serno 12
P 10.1.103.0/29,
1
successors,
FD
is
40512000,
serno 13
via Connected, Serial0/0/1
via Connected, Serial0/0/0
is the advertised 2distance
of the R1 loopback
network routes
from R1
PWhat
10.1.102.0/29,
successors,
FD is 41024000,
serno
42 and R2?
CCNPv6 ROUTE via 10.1.103.1 (41024000/40512000), Serial0/0/0
_______________________________________________________________________________
_______________________________________________________________________________
via 10.1.203.2 (41024000/40512000), Serial0/0/1
Page 10 of 19
P 10.1.203.0/29, 1 successors, FD is 40512000, serno 12
_______________________________________________________________________________
via Connected, Serial0/0/1
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
_______________________________________________________________________________
What is the advertised distance of the R1 loopback network routes from R1 and R2?
_______________________________________________________________________________
_______________________________________________________________________________
c.
_______________________________________________________________________________
Use the show ip eigrp topology 10.1.2.0/30 command to see the granular view of the alternate paths to
_______________________________________________________________________________
10.1.2.0, including ones with a higher reported distance than the feasible distance.
R3# show ip eigrp topology 10.1.2.0/30
_______________________________________________________________________________
IP-EIGRP (AS 100): Topology entry for 10.1.2.0/30
_______________________________________________________________________________
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 40640000
c.
Routing Descriptor Blocks:
10.1.203.2 (Serial0/0/1), from 10.1.203.2, Send flag is 0x0
Composite metric is (40640000/128256), Route is Internal
Use the show
ip eigrp topology 10.1.2.0/30 command to see the granular view of the alternate paths to
Vector metric:
10.1.2.0, including
ones
with a higher
Minimum
bandwidth
is reported
64 Kbitdistance than the feasible distance.
delaytopology
is 2500010.1.2.0/30
microseconds
R3# show Total
ip eigrp
is 255/255
IP-EIGRP Reliability
(AS 100): Topology
entry for 10.1.2.0/30
Load
is 1/255Query origin flag is 1, 1 Successor(s), FD is 40640000
State is
Passive,
Minimum
MTU isBlocks:
1500
Routing Descriptor
Hop count is 1
10.1.203.2 (Serial0/0/1), from 10.1.203.2, Send flag is 0x0
10.1.103.1 (Serial0/0/0), from 10.1.103.1, Send flag is 0x0
Composite metric is (40640000/128256), Route is Internal
Composite metric is (41152000/40640000), Route is Internal
Vector
Vector metric:
metric:
Minimum
bandwidth is
is 64
64Kbit
Kbit
Minimum bandwidth
Total
delay
is
25000
microseconds
Total delay is 45000 microseconds
Reliability
is 255/255
255/255
Reliability is
Load
1/255
Load is
is 1/255
CCNPv6 ROUTE
c. Use the show ip eigrp topology 10.1.2.0/30 command to see the granular view of the alternate paths to
10.1.2.0, including ones with a higher reported distance than the feasible distance.
What is its feasible distance?
R3# show ip eigrp topology 10.1.2.0/30
_______________________________________________________________________________
IP-EIGRP
(AS Configuration and Management of Networks ‐ 2012 100): Topology entry for 10.1.2.0/30
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 40640000
If the R2 Serial0/0/1 interface were shut down, would EIGRP route through R1 to get to 10.1.2.0/30?
Routing Descriptor Blocks:
Would
the switch(Serial0/0/1),
be immediate?
10.1.203.2
from 10.1.203.2, Send flag is 0x0
Composite
metric is (40640000/128256), Route is Internal
_______________________________________________________________________________
Vector metric:
_______________________________________________________________________________
Minimum bandwidth is 64 Kbit
Total delay is 25000 microseconds
_______________________________________________________________________________
Reliability is 255/255
Load is 1/255
_______________________________________________________________________________
Minimum MTU is 1500
_______________________________________________________________________________
Hop count is 1
10.1.103.1
(Serial0/0/0), from 10.1.103.1, Send flag is 0x0
_______________________________________________________________________________
Composite metric is (41152000/40640000), Route is Internal
_______________________________________________________________________________
Vector metric:
Minimum bandwidth is 64 Kbit
_______________________________________________________________________________
Total delay is 45000 microseconds
Reliability is 255/255
Load is 1/255
Record your
answer,MTU
and then
experiment by shutting down the R1 s0/0/01 interface while an extended
Minimum
is 1500
ping is running
as described
Hop count
is 2below.
d. When
Startusing
a pingthe
with
a high
on R3
to the R1 why
Serial0/0/0
interface
10.1.102.1.
show
iprepeat
eigrp count
topology
command,
is the route
to 10.1.2.1
through R1 not listed in
the
topology
R3#
ping table?
10.1.102.1 repeat 10000
e. _______________________________________________________________________________
Enter interface configuration mode on R1 and shut down port Serial0/0/1, which is the direct link from R1
to R3.
_______________________________________________________________________________
R1(config)# interface serial 0/0/1
_______________________________________________________________________________
R1(config-if)# shutdown
f. _______________________________________________________________________________
When the adjacency between R1 and R3 goes down, some pings will be lost. After pings are again being
successfully received, stop the ping using Ctrl+Shift+^.
_______________________________________________________________________________
R3# ping 10.1.102.1 repeat 10000
Type escape sequence to abort.
What is its advertised distance from R1?
Sending 10000, 100-byte ICMP Echos to 10.1.102.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
_______________________________________________________________________________
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
CCNPv6
ROUTE
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!.
*Dec 11© 1992–2010
18:41:55.843:
%LINK-3-UPDOWN:
Interface
Serial0/0/0,
changed state 11to
All contents Note:
are Copyright
Cisco
Systems,
Inc.reconvergence
All rights reserved. This
document
is Cisco
Public Information.
of 19
When examining
the
EIGRP
speed
after
deactivating
the serial link between Page
R1 and
R3,
down
the
focus
should
not
be
on
the
count
of
lost
ping
packets
but
rather
on
the
duration
of
connectivity
loss
or
how
*Dec 11 18:41:55.847: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.1.103.1
long
it took to performisa successful
cutover. The
router waits for up to two seconds for each sent ICMP ECHO
(Serial0/0/0)
down: interface
down
request
a reply and only
then does it send anotherLine
ECHO
request. If on
the Interface
router did not wait for the
*Dec to
11receive
18:41:56.843:
%LINEPROTO-5-UPDOWN:
protocol
Serial0/0/0,
changed
tomuch
downhigher. Because two packets were lost, the cutover took
reply,
the count of lost
packetsstate
would be
.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
approximately
4 seconds.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Another
factor to consider is that an interface deliberately delays the information about loss of connectivity for
!!!!!!!!!!!!!!!!!!!!!!!!!!
istransient
99 percent
(374/376),
min/avg/max
= 28/39/96
2 Success
seconds torate
prevent
link flaps
(link going upround-trip
and down) from
introducing instability
into thems
network.
R3#
If the real speed of EIGRP is to be observed, this delay can be made as short as possible using the command
carrier-delay
msec 0were
on alldropped?
serial interfaces.
How many packets
g. _______________________________________________________________________________
Issue the no shutdown command on the R1 Serial0/0/1 interface before continuing to the next step.
Step 6: Observe unequal-cost load balancing.
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 12 of 19
a. Review the composite metrics advertised by EIGRP using the show ip eigrp topology 10.1.2.0/30
command,.
R3# show ip eigrp topology 10.1.2.0/30
IP-EIGRP (AS 100): Topology entry for 10.1.2.0/30
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 40640000
Routing Descriptor Blocks:
10.1.203.2 (Serial0/0/1), from 10.1.203.2, Send flag is 0x0
Composite metric is (40640000/128256), Route is Internal
Vector metric:
Minimum bandwidth is 64 Kbit
Total delay is 25000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
10.1.103.1 (Serial0/0/0), from 10.1.103.1, Send flag is 0x0
Composite metric is (41152000/40640000), Route is Internal
Vector metric:
Minimum bandwidth is 64 Kbit
Total delay is 45000 microseconds
a.a. Review
Reviewthe
thecomposite
compositemetrics
metricsadvertised
advertisedbybyEIGRP
EIGRPusing
usingthe
theshow
showipipeigrp
eigrptopology
topology10.1.2.0/30
10.1.2.0/30
command,.
command,.
R3#
R3#show
showipipeigrp
eigrptopology
topology10.1.2.0/30
10.1.2.0/30
IP-EIGRP
100):
IP-EIGRP(AS
(AS
100):Topology
Topologyentry
entryfor
for10.1.2.0/30
10.1.2.0/30
Configuration and Management of Networks ‐ 2012 State
StateisisPassive,
Passive,Query
Queryorigin
originflag
flagis
is1,
1,1 1Successor(s),
Successor(s),FD
FDis
is40640000
40640000
Routing
RoutingDescriptor
DescriptorBlocks:
Blocks:
10.1.203.2
10.1.203.2(Serial0/0/1),
(Serial0/0/1),from
from10.1.203.2,
10.1.203.2,Send
Sendflag
flagis
is0x0
0x0
Composite
Compositemetric
metricis
is(40640000/128256),
(40640000/128256),Route
Routeis
isInternal
Internal
Vector
Vectormetric:
metric:
Minimum
Minimumbandwidth
bandwidthis
is64
64Kbit
Kbit
Total
Totaldelay
delayis
is25000
25000microseconds
microseconds
Reliability
Reliabilityis
is255/255
255/255
Load
Loadisis1/255
1/255
Minimum
MinimumMTU
MTUis
is1500
1500
Hop
Hopcount
countis
is1 1
10.1.103.1
10.1.103.1(Serial0/0/0),
(Serial0/0/0),from
from10.1.103.1,
10.1.103.1,Send
Sendflag
flagis
is0x0
0x0
Composite
Compositemetric
metricis
is(41152000/40640000),
(41152000/40640000),Route
Routeis
isInternal
Internal
Vector
Vectormetric:
metric:
Minimum
Minimumbandwidth
bandwidthis
is64
64Kbit
Kbit
Total
Totaldelay
delayis
is45000
45000microseconds
microseconds
Reliability
Reliabilityis
is255/255
255/255
Load
Loadisis1/255
1/255
Minimum
MinimumMTU
MTUis
is1500
1500
Hop
Hopcount
countis
is2 2
The
Thereported
reporteddistance
distanceforfora aloopback
loopbacknetwork
networkisishigher
higherthan
thanthe
thefeasible
feasibledistance,
distance,sosoDUAL
DUALdoes
doesnot
not
consider
considerit ita afeasible
feasiblesuccessor
successorroute.
route.
demonstrateunequal-cost
unequal-costload
loadbalancing
balancingininyour
yourinternetwork,
internetwork,upgrade
upgradethe
thepath
pathtotothe
thedestination
destination
b.b. ToTodemonstrate
network
through
R1
with
a
higher
bandwidth.
Change
the
clock
rate
and
bandwidth
on
the
R1,
R2,and
and
network through R1 with a higher bandwidth. Change the clock rate and bandwidth on the R1, R2,
R3serial
serialinterfaces
interfacestoto128
128kb/s.
kb/s.
R3
R1(config)#interface
interfaceserial
serial0/0/0
0/0/0
R1(config)#
R1(config-if)#bandwidth
bandwidth128
128
R1(config-if)#
R1(config-if)#clock
clockrate
rate128000
128000
R1(config-if)#
R1(config-if)#interface
interfaceserial
serial0/0/1
0/0/1
R1(config-if)#
R1(config-if)#bandwidth
bandwidth128
128
R1(config-if)#
R2(config)#interface
interfaceserial
serial0/0/0
0/0/0
R2(config)#
R2(config-if)#bandwidth
bandwidth128
128
R2(config-if)#
CCNPv6
ROUTE
CCNPv6
ROUTE
R3(config)#
interface
serial
0/0/0
R3(config)#
interface
serial
0/0/0
R3(config-if)# clock rate 128000
R3(config-if)#
bandwidth
R3(config-if)#
bandwidth
128128
contents
Copyright
© 1992–2010
Cisco
Systems,
Inc.
All
rights
reserved.
This
document
Cisco
Public
Information.
AllAll
contents
areare
Copyright
© 1992–2010
Cisco
Systems,
Inc.
All128000
rights
reserved.
This
document
is is
Cisco
Public
Information.
R3(config-if)#
clock
rate
Page
Page
1313
of of
1919
Issue
show
ip eigrp
topology
10.1.2.0/30
command
again
on R3
to see
what
changed.
c. c.
Issue
the the
show
ip eigrp
topology
10.1.2.0/30
command
again
on R3
to see
what
hashas
changed.
show
eigrp
topology
10.1.2.0/30
R3#R3#
show
ip ip
eigrp
topology
10.1.2.0/30
IP-EIGRP
100):
Topology
entry
10.1.2.0/30
IP-EIGRP
(AS(AS
100):
Topology
entry
forfor
10.1.2.0/30
State
Passive,
Query
origin
flag
1 Successor(s),
21152000
State
is is
Passive,
Query
origin
flag
is is
1, 1,
1 Successor(s),
FD FD
is is
21152000
Routing
Descriptor
Blocks:
Routing
Descriptor
Blocks:
10.1.103.1
(Serial0/0/0),
from
10.1.103.1,
Send
flag
10.1.103.1
(Serial0/0/0),
from
10.1.103.1,
Send
flag
is is
0x00x0
Composite
metric
(21152000/20640000),
Route
Internal
Composite
metric
is is
(21152000/20640000),
Route
is is
Internal
Vector
metric:
Vector
metric:
Minimum
bandwidth
Kbit
Minimum
bandwidth
is is
128128
Kbit
Total
delay
45000
microseconds
Total
delay
is is
45000
microseconds
Reliability
255/255
Reliability
is is
255/255
Load
1/255
Load
is is
1/255
Minimum
1500
Minimum
MTUMTU
is is
1500
count
HopHop
count
is is
2 2
10.1.203.2
(Serial0/0/1),
from
10.1.203.2,
Send
flag
10.1.203.2
(Serial0/0/1),
from
10.1.203.2,
Send
flag
is is
0x00x0
Composite
metric
(40640000/128256),
Route
Internal
Composite
metric
is is
(40640000/128256),
Route
is is
Internal
Vector
metric:
Vector
metric:
Minimum
bandwidth
Kbit
Minimum
bandwidth
is is
64 64
Kbit
Total
delay
25000
microseconds
Total
delay
is is
25000
microseconds
Reliability
255/255
Reliability
is is
255/255
Load
1/255
Load
is is
1/255
Minimum
1500
Minimum
MTUMTU
is is
1500
count
HopHop
count
is is
1 1
manipulating
bandwidth
parameter,
preferred
to the
loopback
interfaces
of R2
AfterAfter
manipulating
the the
bandwidth
parameter,
the the
preferred
pathpath
for for
R3 R3
to the
loopback
interfaces
of R2
is is
now
through
R1.
Even
though
the
hop
count
is
two
and
the
delay
through
R1
is
nearly
twice
that
of
the
now through R1. Even though the hop count is two and the delay through R1 is nearly twice that of the R2 R2
path,
higher
bandwidth
lower
results
in this
being
preferred
route.
path,
the the
higher
bandwidth
andand
lower
FD FD
results
in this
being
the the
preferred
route.
Issue
show
ip route
command
to verify
preferred
route
to network
10.1.2.0
is through
d. d.
Issue
the the
show
ip route
command
to verify
thatthat
the the
preferred
route
to network
10.1.2.0
is through
R1 R1
viavia
Serial0/0/0
to next
10.1.103.1.
There
is only
route
to this
network
to the
difference
Serial0/0/0
to next
hophop
10.1.103.1.
There
is only
oneone
route
to this
network
duedue
to the
difference
in in
Composite metric is (40640000/128256), Route is Internal
Vector metric:
Minimum bandwidth is 64 Kbit
Total delay is 25000 microseconds
Reliability
is 255/255
Configuration and Management of Networks ‐ 2012 Load is 1/255
Minimum MTU is 1500
Hop count is 1
After manipulating the bandwidth parameter, the preferred path for R3 to the loopback interfaces of R2 is
now through R1. Even though the hop count is two and the delay through R1 is nearly twice that of the R2
path, the higher bandwidth and lower FD results in this being the preferred route.
d. Issue the show ip route command to verify that the preferred route to network 10.1.2.0 is through R1 via
Serial0/0/0 to next hop 10.1.103.1. There is only one route to this network due to the difference in
bandwidth.
R3# show ip route eigrp
10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks
D
10.1.2.8/30 [90/21152000] via 10.1.103.1, 00:16:52, Serial0/0/0
D
10.1.1.8/30 [90/20640000] via 10.1.103.1, 00:16:52, Serial0/0/0
D
10.1.2.0/30 [90/21152000] via 10.1.103.1, 00:16:52, Serial0/0/0
D
10.1.1.0/30 [90/20640000] via 10.1.103.1, 00:16:52, Serial0/0/0
D
10.1.2.4/30 [90/21152000] via 10.1.103.1, 00:16:52, Serial0/0/0
D
10.1.1.4/30 [90/20640000] via 10.1.103.1, 00:16:52, Serial0/0/0
D
10.1.102.0/29 [90/21024000] via 10.1.103.1, 00:16:52, Serial0/0/0
e. Issue the debug ip eigrp 100 command on R3 to show route events changing in real time. Then, under
the EIGRP router configuration on R3, issue the variance 2 command, which allows unequal-cost load
balancing bounded by a maximum distance of (2) ! (FD), where FD represents the feasible distance for
each route in the routing table.
R3# debug ip eigrp 100
IP-EIGRP Route Events debugging is on
R3# conf t
CCNPv6 ROUTE
ROUTE
CCNPv6
Enter configuration commands, one per line.
End with CNTL/Z.
R3(config)# router eigrp 100
R3(config)#
R3(config-router)# variance 2
R3(config-router)#
R3(config-router)#
*Feb 55 15:11:45.195:
15:11:45.195: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
routing table
table not updated thru 10.1.203.2
routing
*Feb 55 15:11:45.195:
15:11:45.195: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.2.8
10.1.2.8 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.2.8
10.1.2.8 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for
10.1.1.8
for 10.1.1.8 ()
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
routing table
table not updated thru 10.1.203.2
routing
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
routing table
table not updated thru 10.1.203.2
routing
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.2.0
10.1.2.0 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.2.0
10.1.2.0 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.1.0
10.1.1.0 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
routing table
table not updated thru 10.1.203.2
routing
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
routing table
table not updated thru 10.1.203.2
routing
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.2.4
10.1.2.4 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.2.4
10.1.2.4 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.1.4
10.1.1.4 ()
for
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
routing table
table not updated thru 10.1.203.2
routing
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
routing table
table not updated thru 10.1.203.2
routing
*Feb 55 15:11:45.199:
15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.102.0
10.1.102.0 ()
for
*Feb 55 15:11:45.203:
15:11:45.203: IP-EIGRP(Default-IP-Routing-Table:100):
*Feb
for 10.1.102.0
10.1.102.0 ()
for
R3(config-router)#
2 reserved. This document is Cisco Public Information.
All contents
are Copyright © 1992–2010 Ciscovariance
Systems, Inc. All rights
f.f.
Page 14 of 19
10.1.3.8/30
route installed
route installed
route installed
10.1.1.8/30
10.1.3.0/30
route installed
route installed
route installed
10.1.1.0/30
10.1.3.4/30
route installed
route installed
route installed
10.1.1.4/30
10.1.103.0/29
route installed
route installed
Issue the
the show
show ip route command again to verify that there are now two routes to network 10.1.2.0.
Issue
R3# show
show ip
ip route eigrp
R3#
*Feb table
5 15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100):
10.1.1.0/30
routing
not updated
thru 10.1.203.2
routing
table not updated
thru 10.1.203.2
*Feb
5 15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100):
10.1.3.4/30
*Feb table
5 15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100):
10.1.3.4/30
routing
not updated
thru 10.1.203.2
routing
table not updated
thru 10.1.203.2
*Feb
5 15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100):
route installed
*Feb
5
15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100):
route installed
for 10.1.2.4 Configuration and Management of Networks ‐ 2012 ()
for 510.1.2.4
()
*Feb
15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100): route installed
5 15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100): route installed
for*Feb
10.1.2.4
()
for
10.1.2.4
()
*Feb 5 15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100): route installed
5 15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100): route installed
for*Feb
10.1.1.4
()
for 10.1.1.4 ()
*Feb 5 15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100): 10.1.1.4/30
*Feb 5 15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100): 10.1.1.4/30
routing
table
not
updated
routing
table
not
updatedthru
thru10.1.203.2
10.1.203.2
*Feb
5
15:11:45.199:
IP-EIGRP(Default-IP-Routing-Table:100):
10.1.103.0/29
*Feb 5 15:11:45.199: IP-EIGRP(Default-IP-Routing-Table:100): 10.1.103.0/29
routing
table
not
updated
routing
table
not
updatedthru
thru10.1.203.2
10.1.203.2
*Feb
routeinstalled
installed
*Feb5 15:11:45.199:
5 15:11:45.199:IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): route
forfor
10.1.102.0
10.1.102.0()()
*Feb
routeinstalled
installed
*Feb5 15:11:45.203:
5 15:11:45.203:IP-EIGRP(Default-IP-Routing-Table:100):
IP-EIGRP(Default-IP-Routing-Table:100): route
forfor
10.1.102.0
10.1.102.0()()
f.
Issue
the the
show
ip route
command
again
two routes
routesto
tonetwork
network10.1.2.0.
10.1.2.0.
f. Issue
show
ip route
command
againtotoverify
verifythat
thatthere
there are
are now
now two
show
route
eigrp
R3#R3#
show
ip ip
route
eigrp
10.0.0.0/8
variablysubnetted,
subnetted, 12
12 subnets,
subnets, 2
10.0.0.0/8
isis
variably
2 masks
masks
10.1.2.8/30[90/40640000]
[90/40640000]via
via 10.1.203.2,
10.1.203.2, 00:02:27,
00:02:27, Serial0/0/1
10.1.2.8/30
Serial0/0/1
[90/21152000]via
via 10.1.103.1,
10.1.103.1, 00:02:27,
00:02:27, Serial0/0/0
[90/21152000]
Serial0/0/0
10.1.1.8/30[90/20640000]
[90/20640000]via
via 10.1.103.1,
10.1.103.1, 00:02:27,
00:02:27, Serial0/0/0
D D
10.1.1.8/30
Serial0/0/0
D
10.1.2.0/30
[90/40640000]
via
10.1.203.2,
00:02:27, Serial0/0/1
D
10.1.2.0/30 [90/40640000] via 10.1.203.2, 00:02:27,
Serial0/0/1
[90/21152000] via 10.1.103.1, 00:02:27, Serial0/0/0
[90/21152000]
via 10.1.103.1, 00:02:27, Serial0/0/0
D
10.1.1.0/30 [90/20640000] via 10.1.103.1, 00:02:27, Serial0/0/0
D
10.1.1.0/30 [90/20640000] via 10.1.103.1, 00:02:27, Serial0/0/0
D
10.1.2.4/30 [90/40640000] via 10.1.203.2, 00:02:27, Serial0/0/1
D
10.1.2.4/30 [90/40640000]
00:02:27, Serial0/0/0
Serial0/0/1
[90/21152000] via
via 10.1.203.2,
10.1.103.1, 00:02:27,
[90/21152000]
00:02:27, Serial0/0/0
Serial0/0/0
D
10.1.1.4/30
[90/20640000]via
via 10.1.103.1,
10.1.103.1, 00:02:27,
D D
10.1.1.4/30
[90/20640000]
viavia
10.1.103.1,
00:02:27,
10.1.102.0/29
[90/41024000]
10.1.203.2,
00:02:27,Serial0/0/0
Serial0/0/1
CCNPv6
ROUTE
D
10.1.102.0/29 [90/41024000]
via
10.1.203.2,
00:02:27, Serial0/0/0
Serial0/0/1
[90/21024000] via 10.1.103.1, 00:02:27,
[90/21024000] via 10.1.103.1, 00:02:27, Serial0/0/0
D
D
g. These unequal-cost routes also show up in the EIGRP topology table, even though they are not
considered feasible successor routes. Use the show ip eigrp topology command to verify this.
All contents are
Copyright
© 1992–2010
Cisco Systems,
Inc. All rights reserved. This document is Cisco Public Information.
R3#
show
ip eigrp
topology
All contents are Copyright
© 1992–2010
Cisco Systems,
Inc. All rights
This document is Cisco Public Information.
IP-EIGRP
Topology
Table
for reserved.
AS(100)/ID(10.1.3.9)
Page 15 of 19
Page 15 of 19
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 10.1.3.8/30, 1 successors, FD is 128256
via Connected, Loopback39
P 10.1.2.8/30, 1 successors, FD is 21152000
via 10.1.103.1 (21152000/20640000), Serial0/0/0
via 10.1.203.2 (40640000/128256), Serial0/0/1
P 10.1.1.8/30, 1 successors, FD is 20640000
via 10.1.103.1 (20640000/128256), Serial0/0/0
P 10.1.3.0/30, 1 successors, FD is 128256
via Connected, Loopback31
P 10.1.2.0/30, 1 successors, FD is 21152000
via 10.1.103.1 (21152000/20640000), Serial0/0/0
via 10.1.203.2 (40640000/128256), Serial0/0/1
P 10.1.1.0/30, 1 successors, FD is 20640000
via 10.1.103.1 (20640000/128256), Serial0/0/0
P 10.1.3.4/30, 1 successors, FD is 128256
via Connected, Loopback35
P 10.1.2.4/30, 1 successors, FD is 21152000
via 10.1.103.1 (21152000/20640000), Serial0/0/0
via 10.1.203.2 (40640000/128256), Serial0/0/1
P 10.1.1.4/30, 1 successors, FD is 20640000
via 10.1.103.1 (20640000/128256), Serial0/0/0
P 10.1.103.0/29, 1 successors, FD is 20512000
via Connected, Serial0/0/0
P 10.1.102.0/29, 1 successors, FD is 21024000
via 10.1.103.1 (21024000/20512000), Serial0/0/0
via 10.1.203.2 (41024000/20512000), Serial0/0/1
P 10.1.203.0/29, 1 successors, FD is 40512000
via Connected, Serial0/0/1
h. Load balancing over serial links occurs in blocks of packets, the number of which are recorded in the
routing table’s detailed routing information. Use the show ip route 10.1.2.0 command to get a detailed
view of how traffic is shared between the two links.
R3# show ip route 10.1.2.0
Routing entry for 10.1.2.0/30
Known via "eigrp 100", distance 90, metric 21152000, type internal
P 10.1.103.0/29, 1 successors, FD is 20512000
via Connected, Serial0/0/0
P 10.1.102.0/29, 1 successors, FD is 21024000
via 10.1.103.1 (21024000/20512000), Serial0/0/0
via Configuration and Management of Networks ‐ 2012 10.1.203.2 (41024000/20512000), Serial0/0/1
P 10.1.203.0/29, 1 successors, FD is 40512000
via Connected, Serial0/0/1
h. Load balancing over serial links occurs in blocks of packets, the number of which are recorded in the
routing table’s detailed routing information. Use the show ip route 10.1.2.0 command to get a detailed
view of how traffic is shared between the two links.
R3# show ip route 10.1.2.0
Routing entry for 10.1.2.0/30
Known via "eigrp 100", distance 90, metric 21152000, type internal
Redistributing via eigrp 100
Last update from 10.1.203.2 on Serial0/0/1, 00:05:41 ago
Routing Descriptor Blocks:
10.1.203.2, from 10.1.203.2, 00:05:41 ago, via Serial0/0/1
Route metric is 40640000, traffic share count is 25
Total delay is 25000 microseconds, minimum bandwidth is 64 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
* 10.1.103.1, from 10.1.103.1, 00:05:41 ago, via Serial0/0/0
Route metric is 21152000, traffic share count is 48
Total delay is 45000 microseconds, minimum bandwidth is 128 Kbit
Reliability 255/255, minimum MTU 1500 bytes
CCNPv6 ROUTE
Loading 1/255, Hops 2
i.
Check the actual load balancing using the debug ip packet command. Ping from R3 to 10.1.2.1 with a
Page 16 of 19
high enough repeat count to view the load balancing over both paths. In the case above, the traffic share
is 25 packets routed to R2 to every 48 packets routed to R1.
j.
To filter the debug output to make it more useful, use the following extended access list.
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
R3(config)# access-list 100 permit icmp any any echo
R3(config)# end
R3# debug ip packet 100
IP packet debugging is on for access list 100
R3# ping 10.1.2.1 repeat 50
Type escape sequence to abort.
Sending 50, 100-byte ICMP Echos to 10.1.2.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*Feb 5 15:20:54.215: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.215: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0),
100, sending
*Feb 5 15:20:54.231: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.231: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0),
100, sending
*Feb 5 15:20:54.247: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.247: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0),
100, sending
*Feb 5 15:20:54.263: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.263: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0),
100, sending
*Feb 5 15:20:54.279: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.279: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0),
100, sending
*Feb 5 15:20:54.295: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*Feb 5 15:20:54.295: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0),
100, sending
*Feb 5 15:20:54.311: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.311: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0),
100, sending
!
<output omitted until the switch to the other path takes place>
!
*Feb 5 15:20:55.395: IP: tableid=0, s=10.1.203.3 (local), d=10.1.2.1
(Serial0/0/1), routed via RIB
!
R3 just switched to load-share the outbound ICMP packets to Serial0/0/1.
len
len
len
len
len
len
len
*Feb 5 15:20:54.279: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.279: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0), len
100, sending
*Feb 5 15:20:54.295:
IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
Configuration and Management of Networks ‐ 2012 (Serial0/0/0), routed via RIB
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*Feb 5 15:20:54.295: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0), len
100, sending
*Feb 5 15:20:54.311: IP: tableid=0, s=10.1.103.3 (local), d=10.1.2.1
(Serial0/0/0), routed via RIB
*Feb 5 15:20:54.311: IP: s=10.1.103.3 (local), d=10.1.2.1 (Serial0/0/0), len
100, sending
!
<output omitted until the switch to the other path takes place>
!
*Feb 5 15:20:55.395: IP: tableid=0, s=10.1.203.3 (local), d=10.1.2.1
(Serial0/0/1), routed via RIB
!
R3 just switched to load-share the outbound ICMP packets to Serial0/0/1.
!
*Feb 5 15:20:55.395: IP: s=10.1.203.3 (local), d=10.1.2.1 (Serial0/0/1), len
100, sending
CCNPv6 ROUTE
15:20:55.423:
IP:
tableid=0,
s=10.1.203.3
(local),
d=10.1.2.1
All contents are*Feb
Copyright5© 1992–2010
Cisco Systems,
Inc. All
rights reserved. This
document is Cisco Public
Information.
(Serial0/0/1), routed
*Feb 5 15:20:55.423:
100, sending
*Feb 5 15:20:55.451:
(Serial0/0/1), routed
*Feb 5 15:20:55.451:
100, sending
*Feb 5 15:20:55.483:
(Serial0/0/1), routed
*Feb 5 15:20:55.483:
100, sending
Page 17 of 19
via RIB
IP: s=10.1.203.3 (local), d=10.1.2.1 (Serial0/0/1), len
IP: tableid=0, s=10.1.203.3 (local), d=10.1.2.1
via RIB
IP: s=10.1.203.3 (local), d=10.1.2.1 (Serial0/0/1), len
IP: tableid=0, s=10.1.203.3 (local), d=10.1.2.1
via RIB
IP: s=10.1.203.3 (local), d=10.1.2.1 (Serial0/0/1), len
<output omitted>
Note: If a deliberate metric manipulation is necessary on a router to force it to prefer one interface over
another for EIGRP-discovered routes, it is recommended to use the interface-level command "delay" for these
purposes. While the "bandwidth" command can also be used to influence the metrics of EIGRP-discovered
routes through a particular interface, it is discouraged because the "bandwidth" will also influence the amount
of bandwidth reserved for EIGRP packets and other IOS subsystems as well. The "delay" parameter specifies
the value of the interface delay that is used exclusively by EIGRP to perform metric calculations and does not
influence any other area of IOS operation.