Study Smart

CCNA by Naeem Abbas

 What is Routing? (cont.)
10.120.2.0 172.16.1.0

E0
S0

Network Destination Exit

Protocol Network Interface

Connected 10.120.2.0 E0
Routed Protocol: IP
Learned 172.16.1.0 S0

– Routers must learn destinations that are not

directly connected
Identifying Static and Dynamic Routes

•Static Route •Dynamic Route

Uses a route that a network
Uses a route that a
routing protocol adjusts
network administrator automatically for topology or
enters into the router traffic changes
manually
 STATIC ROUTING
• Static Routing: The administrator must hand-type all
network locations into the routing table.
– In Static Routing, the administrator is responsible
for updating all changes by hand into all routers.
 IP Route command

ip route [destination_network ][mask ]

[next_hop_address or exit interface ]
It is a Global configuration mode command.

Above command is used for configuring

routing table in Static Routing
 Static Routing
The following list describes each command in the string:
ip route The command used to create the static route.
destination network The network you are placing in the routing
table.
mask Indicates the subnet mask being used on the network.
next hop address The address of the next hop router that will
receive the packet and forward it to the remote network. This is a
router interface that is on a directly connected network. You
must be able to ping the router interface before you add
the route.
 Static Route Example
Stub Network

172.16.1.0
SO
Network A B
B
172.16.2.2 172.16.2.1

ip route 172.16.1.0 255.255.255.0 172.16.2.1

This is a unidirectional route. You must have a route configured in the

opposite direction.
 Default Routing

• Default routing is used to send packets with a

remote destination network not in the routing
table to the next hop router.
• You can only use default routing on stub
networks, which means that they have only one
exit port out of the network.
 Default Routes
Stub Network

172.16.1.0
SO
Network A BB
172.16.2.2 172.16.2.1

ip route 0.0.0.0 0.0.0.0 172.16.2.2

This route allows the stub network to reach all known networks beyond
router A.
 Static Routing
• Static Routing is the process of an administrator manually adding routes in each router’s
routing table.
• Benefits of Static Routing
– No overhead on the Router CPU
– No Bandwidth usage between routers
– Security (Administrator can allow routing to selected networks)
• Disadvantage of Static Routing
– The administrator must really understand the full internetwork to configure routes
correctly.
– If one network is added to the internetwork the administrator must add a route to it
on all routers.
– It is not feasible in large networks because it would be a full-time job.
© 2002, Cisco Systems, Inc. All rights reserved.
 What is a Routing Protocol?

10.120.2.0 172.16.1.0

• Routing protocols are E0

S0
used between
routers to determine paths
and maintain
routing tables.
• Once the path is
determined a router can
route a routed protocol. Network Destination Exit 172.17.3.0
Protocol Network Interface
Connected 10.120.2.0 E0
RIP 172.16.2.0 S0
IGRP 172.17.3.0 S1

Routed Protocol: IP
Routing protocol: RIP, IGRP
 Autonomous Systems: Interior or Exterior
Routing Protocols
IGPs: RIP, IGRP EGPs: BGP

Autonomous System 100 Autonomous System 200

– An autonomous system is a collection of networks under

a common administrative domain
– IGPs operate within an autonomous system
– EGPs connect different autonomous systems
 Administrative Distance:
Ranking Routes

I need to send a packet to

Network E. Both router B IGRP
and C will get it there. Administrative
Which route is best? Distance=100

Router A Router B

RIP
Administrative
Distance=120

E
Router C Router D
 Distance Vector versus Link State
• Distance vector
– Sends routing table info only to neighbors, so change
communication may need one min/router
– Also called “routing by rumor”
– Easy to configure, but slow
• Link state
– Floods routing information about itself to all nodes, so changes
are known immediately
– Efficient, but complex to configure
• Cisco’s EIGRP hybrid
– Efficient and easy to configure
 Routing Protocol Evolutions
EIGRP
EIGRP
•• Hybrid
Hybridprotocol
protocol
IGRP
IGRP •• Developed
DevelopedbybyCisco
Cisco
••Distance
Distancevector •• Superior
vector Superiorconvergence
convergenceand and
••Developed
Developedby byCisco operating
Cisco operatingefficiency
efficiency
••Addresses
Addressesproblems
problemsinin •• Merges
Mergesbenefits
benefitsofoflink
linkstate
state
large,
large,heterogeneous
heterogeneous &&distance vector
distance vector
RIP
RIP
••Distance vector networks
networks
Distance vector
••Most common IGP
Most common IGP
••Uses hop count OSPF
OSPF
Uses hop count •• Link
Linkstate,
state,hierarchical
hierarchical
•• Successor
SuccessortotoRIP
RIP
•• Uses
Usesleast-cost
least-costrouting,
routing,
Distance Vector multipath
multipathrouting,
routing,and
andload
load
balancing
balancing
Hybrid •• Derived
Derivedfrom
fromIS-IS
IS-IS
Link State
 Classes of Routing Protocols
B
Distance
Distance Vector
Vector
C A

Hybrid
Hybrid Routing
Routing

B
Link State
C A

D
 Distance Vector Routing Protocols

C A

Distance—How
Distance—How farfar
Vector—In
Vector—In which
which direction
direction D

D C B A

Routing
Routing Routing
Routing Routing
Routing Routing
Routing
Table
Table Table
Table Table
Table Table
Table

•Pass periodic copies of routing table to neighbor

routers and accumulate distance vectors
 Distance Vector—Sources of Information and
Discovering Routes

10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0

E0 A S0 S0 B S1 S0 C E0

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table
10.1.0.0
10.1.0.0 E0 0 10.2.0.0
10.2.0.0 S0 00 10.3.0.0
10.3.0.0 S0 00
10.2.0.0
10.2.0.0 S0 0 10.3.0.0
10.3.0.0 S1 00 10.4.0.0
10.4.0.0 E0 00

•Routers discover the best path to

destinations from each neighbor
 Distance Vector—Sources of Information and
Discovering Routes
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table
10.1.0.0
10.1.0.0 E0 0 10.2.0.0
10.2.0.0 S0 00 10.3.0.0
10.3.0.0 S0 00
10.2.0.0
10.2.0.0 S0 0 10.3.0.0
10.3.0.0 S1 00 10.4.0.0
10.4.0.0 E0 00
10.3.0.0
10.3.0.0 S0 11 10.4.0.0
10.4.0.0 S1 11 10.2.0.0
10.2.0.0 S0 11
10.1.0.0
10.1.0.0 S0 11

•Routers discover the best path to

destinations from each neighbor
 Distance Vector—Sources of Information and
Discovering Routes
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table
10.1.0.0
10.1.0.0 E0 0 10.2.0.0
10.2.0.0 S0 00 10.3.0.0
10.3.0.0 S0 00
10.2.0.0
10.2.0.0 S0 0 10.3.0.0
10.3.0.0 S1 00 10.4.0.0
10.4.0.0 E0 00
10.3.0.0
10.3.0.0 S0 11 10.4.0.0
10.4.0.0 S1 11 10.2.0.0
10.2.0.0 S0 11
10.4.0.0
10.4.0.0 S0 22 10.1.0.0
10.1.0.0 S0 11 10.1.0.0
10.1.0.0 S0 22

•Routers discover the best path to

destinations from each neighbor
 Distance Vector—Selecting Best Route
with Metrics
A IGRP

Bandwidth
56
RIP Delay

Hop
Hop count
count
T1 56

T1

Information used to select the best path for routing

Distance Vector—Maintaining Routing
Information
Process
Process toto
update
update this
this
routing
routing
table
table

Topology
change
causes
routing
A table
update

•Updates proceed step-by-step

from router to router
Distance Vector—Maintaining Routing
Information
Process
Process toto
update
update this
this
routing
routing
table
table

Router A sends Topology

out this updated change
routing table causes
after the routing
next period A table
expires update

•Updates proceed step-by-step

from router to router
 Distance Vector—Maintaining Routing
Information
Process
Process toto Process
Process toto
update
update this
this update
update this
this
routing
routing routing
routing
table
table table
table

Router A sends Topology

out this updated change
routing table causes
after the routing
B next period A table
expires update

•Updates proceed step-by-step

from router to router
 Maintaining Routing Information Problem—
Routing Loops
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table
10.1.0.0 E0 0 10.2.0.0S0 0 10.3.0.0S0 0
10.2.0.0 S0 0 10.3.0.0S1 0 10.4.0.0E0 0
10.3.0.0 S0 11 10.4.0.0S1 11 10.2.0.0S0 11
10.4.0.0 S0 22 10.1.0.0S0 11 10.1.0.0S0 22

•Each node maintains the distance from itself to each possible destination network
 Maintaining Routing Information Problem—
Routing Loops
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table

11 11 11
22 11 22

• Slow convergence produces inconsistent routing

 Maintaining Routing Information Problem—
Routing Loops
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table

11 11 11
22 11 22

Router C concludes that the best path to network

10.4.0.0 is through Router B
 Maintaining Routing Information Problem—
Routing Loops
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table

11 33 11
44 11 22

Router A updates its table to reflect the new but

erroneous hop count
 Symptom: Counting to Infinity
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table

11 55 11
66 11 22

• Packets for network 10.4.0.0 bounce between routers A, B, and C

• Hop count for network 10.4.0.0 counts to infinity
 Solution: Defining a Maximum
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table
10.1.0.0E0 0 10.2.0.0S0 0 10.3.0.0 S0 0
10.2.0.0S0 0 10.3.0.0S1 0 10.4.0.0 S0 16
10.3.0.0 S0 11 10.4.0.0 S1 16
16 10.2.0.0 S0 11
10.4.0.0 S0 16
16 10.1.0.0 S0 11 10.1.0.0 S0 22

•Define a limit on the number of hops to prevent infinite

loops
 Solution: Split Horizon
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X
X X
Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table

11 11 11
22 22 22

•It is never useful to send information about a route back in the direction from which
the original packet came
 Solution: Route Poisoning
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X

Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table
10.1.0.0E0 0 10.2.0.0S0 0 10.3.0.0 S0 0
10.2.0.0S0 0 10.3.0.0S1 0 10.4.0.0 S0 Infinity
10.3.0.0 S0 11 10.4.0.0S1 11 10.2.0.0 S0 11
10.4.0.0 S0 22 10.1.0.0E1 22 10.1.0.0 S0 22

•Routers set the distance of routes that have gone down to infinity
 Solution: Poison Reverse
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X
Poison
Reverse
Routing
Routing Table
Table Routing
Routing Table
Table Routing
Routing Table
Table
10.1.0.0E0 0 10.2.0.0S0 0 10.3.0.0 S0 0
10.2.0.0S0 0 10.3.0.0S1 0 10.4.0.0 S0 Infinity
Possibly
Possibly
10.3.0.0 S0 11 10.4.0.0S1 Down
Down 10.2.0.0 S0 11
10.4.0.0 S0 22 10.1.0.0E1 22 10.1.0.0 S0 22

• Poison Reverse overrides split horizon

 Solution: Hold-Down Timers

Network
Network 10.4.0.0
10.4.0.0
Update
Update after
after is
is unreachable
unreachable
hold-down
hold-down Time
Time
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
E0 A S0 S0 B S1 S0 C E0 X
Update
Update after
after
hold-down
hold-down Time
Time Network 10.4.0.0 is down
then back up
then back down

•Router keeps an entry for the network possibly down state, allowing
time for other routers to recompute for this topology change
 Solution: Triggered Updates

Network
Network 10.4.0.0
10.4.0.0 Network
Network 10.4.0.0
10.4.0.0 Network
Network 10.4.0.0
10.4.0.0
is
is unreachable
unreachable is
is unreachable
unreachable is
is unreachable
unreachable

10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0

E0 A S0 S0 B S1 S0 C E0 X

•Router sends updates when a change in its routing table occurs

Implementing Solutions in Multiple Routes

10.4.0.0

E B X C

A
 Implementing Solutions in Multiple Routes
(cont.)
Holddown
Holddown

10.4.0.0

E B X C
Holddown
Holddown

Holddown
Holddown
 Implementing Solutions in Multiple Routes
(cont.)
Holddown
Holddown

Poison
Poison Reverse
Reverse
D
Poison
Poison Reverse
Reverse

10.4.0.0

E B X C
Holddown
Holddown
Poison
Poison Reverse
Reverse
Poison
Poison Reverse
Reverse
A

Holddown
Holddown
 Implementing Solutions in Multiple Routes
(cont.)
Holddown
Holddown

10.4.0.0

E B X C
Holddown
Holddown
Packet
Packet for
for
Packet
Packet for
for Network
Network 10.4.0.0
10.4.0.0
Network
Network 10.4.0.0
10.4.0.0
A

Holddown
Holddown
Implementing Solutions in Multiple Routes
(cont.)

10.4.0.0

E B C
Link up!

A
Implementing Solutions in Multiple Routes
(cont.)

10.4.0.0

E B C
Link up!

A
 Link-State Routing Protocols
B

C A

D
Link-State Packets
Topological
Database
Routing
Routing
SPF Table
Table
Algorithm

Shortest Path First Tree

• After initial flood, pass small event-triggered link-state
updates to all other routers
 Hybrid Routing
Choose a
routing path based
on distance vectors

Balanced Hybrid
Hybrid Routing

Converge rapidly using

change-based
updates

•Share attributes of both distance-vector

and link-state routing
 IP Routing
Configuration Tasks

Network 172.16.0.0
RIP
• Router configuration
IGRP, IGRP
– Select routing protocols RIP
– Specify networks or interfaces Network
160.89.0.0

RIP
Network 172.30.0.0
 Dynamic Routing Configuration

Router(config)#router protocol [keyword]

– Defines an IP routing protocol

Router(config-router)#network network-number

• Mandatory configuration command for each

IP routing process

• Identifies the physically connected network

that routing updates are forwarded to
 RIP Overview

19.2 kbps

T1 T1

T1

– Hop count metric selects the path

– Routes update every 30 seconds
 RIP Configuration

Router(config)#router rip

–Starts the RIP routing process

Router(config-router)#network network-number

• Selects participating attached networks

• The network number must be a major classful
network number
 RIP Configuration Example
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

router rip 2.3.0.0 router rip 2.3.0.0

network 172.16.0.0 network 192.168.1.0
network 10.0.0.0 network 10.0.0.0

router rip
network 10.0.0.0
 Verifying the Routing Protocol—RIP
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA#sh ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 0 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is
Incoming update filter list for all interfaces is
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Key-chain
Ethernet0 1 12
Serial2 1 12
Routing for Networks:
10.0.0.0
172.16.0.0
Routing Information Sources:
Gateway Distance Last Update
10.1.1.2 120 00:00:10
Distance: (default is 120)
 Displaying the
IP Routing Table
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
T - traffic engineered route

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets

C 172.16.1.0 is directly connected, Ethernet0
10.0.0.0/24 is subnetted, 2 subnets
R 10.2.2.0 [120/1] via 10.1.1.2, 00:00:07, Serial2
C 10.1.1.0 is directly connected, Serial2
R 192.168.1.0/24 [120/2] via 10.1.1.2, 00:00:07, Serial2
 debug ip rip Command
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA#debug ip rip
RIP protocol debugging is on
RouterA#
00:06:24: RIP: received v1 update from 10.1.1.2 on Serial2
00:06:24: 10.2.2.0 in 1 hops
00:06:24: 192.168.1.0 in 2 hops
00:06:33: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (172.16.1.1)
00:06:34: network 10.0.0.0, metric 1
00:06:34: network 192.168.1.0, metric 3
00:06:34: RIP: sending v1 update to 255.255.255.255 via Serial2 (10.1.1.1)
00:06:34: network 172.16.0.0, metric 1
Introduction to IGRP

IGRP

– More scalable than RIP

– Sophisticated metric
– Multiple-path support
 IGRP Composite Metric
19.2 kbps 19.2 kbps

Source

Destination

–Bandwidth
–Delay
–Reliability
–Loading
–MTU
 IGRP Unequal Multiple Paths

New Route

Source

Initial
Route Destination

–Maximum six paths

–Next-hop router closer to destination
–Within metric variance
 Configuring IGRP

Router(config)#router igrp autonomous-system

• Defines IGRP as the IP routing protocol

Router(config-router)#network network-number

• Selects participating attached networks

 Configuring IGRP (cont.)

Router(config-router)#variance multiplier
• Control IGRP load balancing

Router(config-router)#traffic-share
{ balanced | min }

• Control how load-balanced traffic is distributed

 IGRP Configuration Example
Autonomous System = 100
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

router igrp 100 router igrp 100

network 172.16.0.0 network 192.168.1.0
network 10.0.0.0 network 10.0.0.0

router igrp 100

network 10.0.0.0
 Verifying the Routing Protocol—IGRP
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA#sh ip protocols
Routing Protocol is "igrp 100"
Sending updates every 90 seconds, next due in 21 seconds
Invalid after 270 seconds, hold down 280, flushed after 630
Outgoing update filter list for all interfaces is
Incoming update filter list for all interfaces is
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
IGRP maximum hopcount 100
IGRP maximum metric variance 1
Redistributing: igrp 100
Routing for Networks:
10.0.0.0
172.16.0.0
Routing Information Sources:
Gateway Distance Last Update
10.1.1.2 100 00:01:01
Distance: (default is 100)
 Displaying the
IP Routing Table
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
T - traffic engineered route

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets

C 172.16.1.0 is directly connected, Ethernet0
10.0.0.0/24 is subnetted, 2 subnets
I 10.2.2.0 [100/90956] via 10.1.1.2, 00:00:23, Serial2
C 10.1.1.0 is directly connected, Serial2
I 192.168.1.0/24 [100/91056] via 10.1.1.2, 00:00:23, Serial2
 debug ip igrp transaction Command
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA#debug ip igrp transactions

IGRP protocol debugging is on
RouterA#
00:21:06: IGRP: sending update to 255.255.255.255 via Ethernet0 (172.16.1.1)
00:21:06: network 10.0.0.0, metric=88956
00:21:06: network 192.168.1.0, metric=91056
00:21:07: IGRP: sending update to 255.255.255.255 via Serial2 (10.1.1.1)
00:21:07: network 172.16.0.0, metric=1100
00:21:16: IGRP: received update from 10.1.1.2 on Serial2
00:21:16: subnet 10.2.2.0, metric 90956 (neighbor 88956)
00:21:16: network 192.168.1.0, metric 91056 (neighbor 89056)
 debug ip igrp events Command
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA#debug ip igrp events

IGRP event debugging is on
RouterA#
00:23:44: IGRP: sending update to 255.255.255.255 via Ethernet0 (172.16.1.1)
00:23:44: IGRP: Update contains 0 interior, 2 system, and 0 exterior routes.
00:23:44: IGRP: Total routes in update: 2
00:23:44: IGRP: sending update to 255.255.255.255 via Serial2 (10.1.1.1)
00:23:45: IGRP: Update contains 0 interior, 1 system, and 0 exterior routes.
00:23:45: IGRP: Total routes in update: 1
00:23:48: IGRP: received update from 10.1.1.2 on Serial2
00:23:48: IGRP: Update contains 1 interior, 1 system, and 0 exterior routes.
00:23:48: IGRP: Total routes in update: 2
 Updating Routing Information Example
E0

172.16.1.0 X A
S2 S2
B
S3 S3
C
E0
192.168.1.0
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1

RouterA# debug ip igrp trans

00:31:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed state to down
00:31:15: IGRP: edition is now 3
00:31:15: IGRP: sending update to 255.255.255.255 via Serial2 (10.1.1.1)
00:31:15: network 172.16.0.0, metric=4294967295
00:31:16: IGRP: Update contains 0 interior, 1 system, and 0 exterior routes.
00:31:16: IGRP: Total routes in update: 1
00:31:16: IGRP: broadcasting request on Serial2
00:31:16: IGRP: received update from 10.1.1.2 on Serial2
00:31:16: subnet 10.2.2.0, metric 90956 (neighbor 88956)
00:31:16: network 172.16.0.0, metric 4294967295 (inaccessible)
00:31:16: network 192.168.1.0, metric 91056 (neighbor 89056)
00:31:16: IGRP: Update contains 1 interior, 2 system, and 0 exterior routes.
00:31:16: IGRP: Total routes in update: 3
 Updating Routing Information Example
(cont.)
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1
RouterB#debug ip igrp trans
IGRP protocol debugging is on
RouterB#
1d19h: IGRP: sending update to 255.255.255.255 via Serial2 (10.1.1.2)
1d19h: subnet 10.2.2.0, metric=88956
1d19h: network 192.168.1.0, metric=89056
1d19h: IGRP: sending update to 255.255.255.255 via Serial3 (10.2.2.2)
1d19h: subnet 10.1.1.0, metric=88956
1d19h: network 172.16.0.0, metric=89056
1d19h: IGRP: received update from 10.1.1.1 on Serial2
1d19h: network 172.16.0.0, metric 4294967295 (inaccessible)
1d19h: IGRP: edition is now 10
1d19h: IGRP: sending update to 255.255.255.255 via Serial2 (10.1.1.2)
1d19h: subnet 10.2.2.0, metric=88956
1d19h: network 172.16.0.0, metric=4294967295
1d19h: network 192.168.1.0, metric=89056
1d19h: IGRP: sending update to 255.255.255.255 via Serial3 (10.2.2.2)
1d19h: subnet 10.1.1.0, metric=88956
1d19h: network 172.16.0.0, metric=4294967295
 Updating Routing Information Example
(cont.)
E0
X
S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1
RouterB#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
T - traffic engineered route

Gateway of last resort is not set

I 172.16.0.0/16 is possibly down, routing via 10.1.1.1, Serial2

10.0.0.0/24 is subnetted, 2 subnets
C 10.1.1.0 is directly connected, Serial2
C 10.2.2.0 is directly connected, Serial3
I 192.168.1.0/24 [100/89056] via 10.2.2.3, 00:00:14, Serial3
RouterB#ping 172.16.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RouterB#
 Updating Routing Information Example
(cont.)
E0 S2 S2 S3 S3 E0
172.16.1.0 A 192.168.1.0
B C
172.16.1.1 10.1.1.1 10.1.1.2 10.2.2.2 10.2.2.3 192.168.1.1
RouterB#debug ip igrp transactions
RouterB#
1d20h: IGRP: received update from 10.1.1.1 on Serial2
1d20h: network 172.16.0.0, metric 89056 (neighbor 1100)
RouterB#
RouterB#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
T - traffic engineered route

Gateway of last resort is not set

I 172.16.0.0/16 is possibly down, routing via 10.1.1.1, Serial2

10.0.0.0/24 is subnetted, 2 subnets
C 10.1.1.0 is directly connected, Serial2
C 10.2.2.0 is directly connected, Serial3
I 192.168.1.0/24 [100/89056] via 10.2.2.3, 00:00:18, Serial3
RouterB#ping 172.16.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/38/48 ms
 EIGRP Overview

© 2000, Cisco Systems, Inc. www.cisco.com 6-67