Chapter 9: Determining IP Routes

Chapter 9
Determining IP
Routes
© 1999, Cisco Systems, Inc. 91
Objectives
Upon completion of this chapter, you will
be able to complete the following tasks:
• Distinguish the use and operation of static and
dynamic routes
• Configure and verify a static route
• Identify how distance vector IP routing protocols
such as RIP and IGRP operate on Cisco routers
• Enable Routing Information Protocol (RIP)
• Enable Interior Gateway Routing Protocol (IGRP)
• Verify IP routing with show and debug commands
© 1999, Cisco Systems, Inc. www.cisco.com ICND—92

What is Routing?
10.120.2.0 172.16.1.0
To route a router need to know:
• Destination addresses
• Sources it can learn from
• Possible routes
• Best route
• Maintain and verify routing information
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 Uses a route that a
network network routing
administrator enters protocol adjusts
into the router automatically for
manually topology or traffic
changes

Static Routes
Stub Network
172.16.1.0
SO
Network A B
B
172.16.2.2 172.16.2.1
Configure unidirectional static routes to and from a stub
network to allow communications to occur.

Static Route Configuration
Router(config)#ip route network [mask]
{address | interface}[distance] [permanent]
Defines a path to an IP destination network or subnet

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 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.
What is a Routing Protocol?
10.120.2.0 172.16.1.0
E0
Routing protocols are S0
used between
routers to determine
paths and maintain
routing tables.
Once the path is Network Destination Exit 172.17.3.0
determined a router can Protocol Network Interface
route a routed protocol.
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

Classes of Routing Protocols
B
Distance Vector
C A
Hybrid Routing
B
Link State
C A

Distance Vector Routing
Protocols
B
C A
Distance—How far
Vector—In which direction D
D C B A
Routing Routing Routing Routing

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 Table Routing Table Routing Table

10.1.0.0 E0 0 10.2.0.0 S0 0 10.3.0.0 S0 0
10.2.0.0 S0 0 10.3.0.0 S1 0 10.4.0.0 E0 0

Routers discover the best path to
destinations from each neighbor

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

10.1.0.0 E0 0 10.2.0.0 S0 0 10.3.0.0 S0 0
10.2.0.0 S0 0 10.3.0.0 S1 0 10.4.0.0 E0 0
10.3.0.0 S0 1 10.4.0.0 S1 1 10.2.0.0 S0 1
10.1.0.0 S0 1

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

10.1.0.0 E0 0 10.2.0.0 S0 0 10.3.0.0 S0 0
10.2.0.0 S0 0 10.3.0.0 S1 0 10.4.0.0 E0 0
10.3.0.0 S0 1 10.4.0.0 S1 1 10.2.0.0 S0 1
10.4.0.0 S0 2 10.1.0.0 S0 1 10.1.0.0 S0 2

Distance Vector—Selecting
Best Route with Metrics
A IGRP
Bandwidth
56
Delay
RIP
Load
Hop count
T1 56 Reliability
IPX MTU
Ticks, hop count T1
Information used to select the best path for routing

Do not delete

Distance Vector—Maintaining
Routing Information
Process to
update this
routing
table
Topology
change
causes
routing
A table
update
Updates proceed stepbystep
from router to router
Routing Information
Process to
update this
routing
table
Router A sends Topology
out this updated change
routing table causes
after the routing
next period A table
expires update
Routing Information
Process to Process to
update this update this
routing routing
table table
Router A sends Topology
out this updated change
routing table causes
after the routing
B next period A
table
expires update
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

10.1.0.0 E0 0 10.2.0.0 S0 0 10.3.0.0 S0 0
10.2.0.0 S0 0 10.3.0.0 S1 0 10.4.0.0 E0 0
10.3.0.0 S0 1 10.4.0.0 S1 1 10.2.0.0 S0 1
10.4.0.0 S0 2 10.1.0.0 S0 1 10.1.0.0 S0 2
Each node maintains the distance from itself to each
possible destination network

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
1 1 1
2 1 2
Slow convergence produces inconsistent routing

10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
1 1 1
2 1 2
Router C concludes that the best path to network
10.4.0.0 is through Router B

10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
1 3 1
4 1 2
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
1 5 1
6 1 2
• 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

10.1.0.0 E0 0 10.2.0.0 S0 0 10.3.0.0 S0 0
10.2.0.0 S0 0 10.3.0.0 S1 0 10.4.0.0 S0 16
10.3.0.0 S0 1 10.4.0.0 S1 16 10.2.0.0 S0 1
10.4.0.0 S0 16 10.1.0.0 S0 1 10.1.0.0 S0 2
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 B C X
X X
S0 S1 S0 E0
1 1 1
2 2 2
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

10.1.0.0 E0 0 10.2.0.0 S0 0 10.3.0.0 S0 0
10.2.0.0 S0 0 10.3.0.0 S1 0 10.4.0.0 S0 Infinity
10.3.0.0 S0 1 10.4.0.0 S1 1 10.2.0.0 S0 1
10.4.0.0 S0 2 10.1.0.0 E1 2 10.1.0.0 S0 2
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
Poison
Reverse
10.1.0.0 E0 0 10.2.0.0 S0 0 10.3.0.0 S0 0
10.2.0.0 S0 0 10.3.0.0 S1 0 10.4.0.0 S0 Infinity
Possibly
10.3.0.0 S0 1 10.4.0.0 S1 Down 10.2.0.0 S0 1
10.4.0.0 S0 2 10.1.0.0 E1 2 10.1.0.0 S0 2
Poison Reverse overrides split horizon

Solution: HoldDown Timers
Network 10.4.0.0
Update after is unreachable
holddown Time
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0
Update after
holddown 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 10.4.0.0 Network 10.4.0.0 Network 10.4.0.0

is unreachable is unreachable is unreachable
10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0

Router sends updates when a change in its routing
table occurs

Blank Slide for Instructor Notes

Implementing Solutions in
Multiple Routes
10.4.0.0
E B X C

Multiple Routes (cont.)
Holddown
10.4.0.0
E B X C
Holddown
Holddown

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

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

10.4.0.0
E B C
Link up!

10.4.0.0
E B C
Link up!

LinkState Routing Protocols
C A
D
LinkState Packets
Topological
Database
Routing
SPF Table
Algorithm
Shortest Path First Tree
After initial flood, pass small eventtriggered linkstate
updates to all other routers
Hybrid Routing
Choose a
routing path based
on distance vectors
Balanced Hybrid Routing
Converge rapidly using
changebased
updates
Share attributes of both distancevector
and linkstate routing

IP Routing
Configuration Tasks
Network 172.16.0.0
Router configuration RIP
• Select routing protocols IGRP, IGRP

RIP
• Specify networks or Network
interfaces 160.89.0.0
RIP
Network 172.30.0.0

Dynamic Routing
Configuration
ter(config)#router protocol [keyword]
• Defines an IP routing protocol
r(configrouter)#network networknumber
• 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
ter(config)#router rip
•Starts the RIP routing process
(configrouter)#network networknumber
• 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
2.3.0.0
router rip 2.3.0.0
router rip
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 Keychain
Ethernet0 1 1 2
Serial2 1 1 2
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 ISIS, L1 ISIS level1, L2 ISIS level2, * candidate
default
U peruser 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
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
• Multiplepath support

IGRP Composite Metric
19.2 kbps 19.2 kbps
Source
Destination
•Bandwidth
•Delay
•Reliability
•Loading
•MTU
Blank Slide for Instructor
Notes

IGRP Unequal Multiple Paths
New Route
Source
Initial
Route Destination
•Maximum six paths
•Nexthop router closer to destination
•Within metric variance
Configuring IGRP
Router(config)#router igrp autonomoussystem
• Defines IGRP as the IP routing protocol
configrouter)#network networknumber
• Selects participating attached networks

Configuring IGRP (cont.)
Router(configrouter)#variance multiplier
• Control IGRP load balancing
ter(configrouter)#trafficshare
alanced | min }
• Control how loadbalanced 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
i ISIS, L1 ISIS level1, L2 ISIS level2, * candidate default
C 172.16.1.0 is directly connected, Ethernet0
I 10.2.2.0 [100/90956] via 10.1.1.2, 00:00:23, 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

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: %LINEPROTO5UPDOWN: Line protocol on Interface Ethernet0, changed state to down
00:31:15: IGRP: edition is now 3
00:31:15: network 172.16.0.0, metric=4294967295
00:31:16: IGRP: broadcasting request 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)

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: subnet 10.1.1.0, metric=88956
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: subnet 10.2.2.0, metric=88956
1d19h: subnet 10.1.1.0, metric=88956
Example (cont.)
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
RouterB#sh ip route
I 172.16.0.0/16 is possibly down, routing via 10.1.1.1, Serial2
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, 100byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RouterB#

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
I 172.16.0.0/16 is possibly down, routing via 10.1.1.1, Serial2
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, 100byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), roundtrip min/avg/max = 32/38/48 ms
ip classless Command
Default route
E0 S0
172.16.0.0
10.1.0.0 10.2.0.0
Router(config)#ip classless
Network Destination Exit
Protocol Network Interface
C 10.1.0.0 E0
To get to 10.7.1.1: C 10.2.0.0 S0
RIP 172.16.0.0 via S0
•With ip classless Default 0.0.0.0 E0
•With no ip classless Drop

Visual Objective
pod ro’s s0 ro’s e0 sw
wg_pc_a A 10.140.1.2 10.2.2.3 10.2.2.11
10.2.2.12 B 10.140.2.2 10.3.3.3 10.3.3.11
RIP C 10.140.3.2 10.4.4.3 10.4.4.11
e0/1 D 10.140.4.2 10.5.5.3 10.5.5.11
e0/2 e0
wg_ro_a E 10.140.5.2 10.6.6.3 10.6.6.11
10.2.2.3 F 10.140.6.2 10.7.7.3 10.7.7.11
s0
wg_sw_a 10.140.1.2/24 G 10.140.7.2 10.8.8.3 10.8.8.11
10.2.2.11 H 10.140.8.2 10.9.9.3 10.9.9.11
I 10.140.9.2 10.10.10.3 10.3.3.11
wg_pc_l J 10.140.10.2 10.11.11.3 10.11.11.11
10.13.13.12 K 10.140.11.2 10.12.12.3 10.12.12.11
L 10.140.12.2 10.13.13.3 10.13.13.11
e0/1 RIP
wg_ro_l
e0/2 e0
LL
10.13.13.3
wg_sw_l s0
10.13.13.11 10.140.12.2/24
... s1/0 s2/3
10.140.1.1/24 … 10.140.12.1/24
fa0/24 fa0/23 fa0/0

core_ server core_sw_a core_ro
10.1.1.1 10.1.1.2 10.1.1.3
Visual Objective
pod ro’s s0 ro’s e0 sw
wg_pc_a A 10.140.1.2 10.2.2.3 10.2.2.11
10.2.2.12 B 10.140.2.2 10.3.3.3 10.3.3.11
IGRP C 10.140.3.2 10.4.4.3 10.4.4.11
e0/1 D 10.140.4.2 10.5.5.3 10.5.5.11
e0/2 e0
wg_ro_a E 10.140.5.2 10.6.6.3 10.6.6.11
10.2.2.3 F 10.140.6.2 10.7.7.3 10.7.7.11
wg_sw_a s0
G 10.140.7.2 10.8.8.3 10.8.8.11
10.2.2.11 10.140.1.2/24
H 10.140.8.2 10.9.9.3 10.9.9.11
I 10.140.9.2 10.10.10.3 10.3.3.11
wg_pc_l J 10.140.10.2 10.11.11.3 10.11.11.11
10.13.13.12 K 10.140.11.2 10.12.12.3 10.12.12.11
L 10.140.12.2 10.13.13.3 10.13.13.11
IGRP
e0/1
e0/2 e0 wg_ro_l
10.13.13.3
LL
wg_sw_l
10.13.13.11 s0
10.140.12.2/24
s1/0 s2/3
...
10.140.1.1/24 … 10.140.12.1/24
fa0/24 fa0/23 fa0/0

core_ server core_sw_a core_ro
10.1.1.1 10.1.1.2 10.1.1.3

Summary
After completing this chapter, you should be
able to perform the following tasks:
• Determine when to use a static or dynamic route.
• Configure a static route on a Cisco Router.
• Describe how distance vector routing protocols operate.
• Configure the RIP and IGRP routing protocols on a Cisco
router.
• Use show ip route, show ip protocols, and other show and
debug commands to verify proper routing operation.

Review Questions
1. What is an advantage of using a static
route rather than a dynamic route?
What is a disadvantage?
2. What is the advantage of using IGRP
rather then RIP? What is a possible
disadvantage?
3. To scale up to very large IP networks,
what routing protocols are recommended?

Chapter 9: Determining IP Routes

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Chapter 9: Determining IP Routes

Загружено:

Авторское право:

Доступные форматы

Chapter 9

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­2

Network Destination Exit

Connected 10.120.2.0 E0 Routed Protocol: IP

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­5

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­6

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­7

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­12

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­13

Routing Routing Routing Routing

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­15

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­16

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­17

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­18

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­19

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­23

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­24

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­25

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­26

Routing Table Routing Table Routing Table

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­28

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­29

Routing Table Routing Table Routing Table

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­30

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­31

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­32

Network 10.4.0.0 Network 10.4.0.0 Network 10.4.0.0

10.1.0.0 10.2.0.0 10.3.0.0 10.4.0.0

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­33

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­34

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­35

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­36

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­37

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­38

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­39

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­40

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­42

• Select routing protocols IGRP, IGRP

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­43

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­46

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­47

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­48

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­49

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­50

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­51

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­53

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­55

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­56

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­57

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­58

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­59

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­60

© 1999, Cisco Systems, Inc. www.cisco.com ICND—9­61

© 1999, Cisco Systems, Inc. www.cisco.com ICND—92

© 1999, Cisco Systems, Inc. www.cisco.com ICND—95

© 1999, Cisco Systems, Inc. www.cisco.com ICND—96

© 1999, Cisco Systems, Inc. www.cisco.com ICND—97

© 1999, Cisco Systems, Inc. www.cisco.com ICND—912

© 1999, Cisco Systems, Inc. www.cisco.com ICND—913

© 1999, Cisco Systems, Inc. www.cisco.com ICND—915

© 1999, Cisco Systems, Inc. www.cisco.com ICND—916

© 1999, Cisco Systems, Inc. www.cisco.com ICND—917

© 1999, Cisco Systems, Inc. www.cisco.com ICND—918

© 1999, Cisco Systems, Inc. www.cisco.com ICND—919

© 1999, Cisco Systems, Inc. www.cisco.com ICND—923

© 1999, Cisco Systems, Inc. www.cisco.com ICND—924

© 1999, Cisco Systems, Inc. www.cisco.com ICND—925

© 1999, Cisco Systems, Inc. www.cisco.com ICND—926

© 1999, Cisco Systems, Inc. www.cisco.com ICND—928

© 1999, Cisco Systems, Inc. www.cisco.com ICND—929

© 1999, Cisco Systems, Inc. www.cisco.com ICND—930

© 1999, Cisco Systems, Inc. www.cisco.com ICND—931

© 1999, Cisco Systems, Inc. www.cisco.com ICND—932

© 1999, Cisco Systems, Inc. www.cisco.com ICND—933

© 1999, Cisco Systems, Inc. www.cisco.com ICND—934

© 1999, Cisco Systems, Inc. www.cisco.com ICND—935

© 1999, Cisco Systems, Inc. www.cisco.com ICND—936

© 1999, Cisco Systems, Inc. www.cisco.com ICND—937

© 1999, Cisco Systems, Inc. www.cisco.com ICND—938

© 1999, Cisco Systems, Inc. www.cisco.com ICND—939

© 1999, Cisco Systems, Inc. www.cisco.com ICND—940

© 1999, Cisco Systems, Inc. www.cisco.com ICND—942

© 1999, Cisco Systems, Inc. www.cisco.com ICND—943

© 1999, Cisco Systems, Inc. www.cisco.com ICND—946

© 1999, Cisco Systems, Inc. www.cisco.com ICND—947

© 1999, Cisco Systems, Inc. www.cisco.com ICND—948

© 1999, Cisco Systems, Inc. www.cisco.com ICND—949

© 1999, Cisco Systems, Inc. www.cisco.com ICND—950

© 1999, Cisco Systems, Inc. www.cisco.com ICND—951

© 1999, Cisco Systems, Inc. www.cisco.com ICND—953

© 1999, Cisco Systems, Inc. www.cisco.com ICND—955

© 1999, Cisco Systems, Inc. www.cisco.com ICND—956

© 1999, Cisco Systems, Inc. www.cisco.com ICND—957

© 1999, Cisco Systems, Inc. www.cisco.com ICND—958

© 1999, Cisco Systems, Inc. www.cisco.com ICND—959

© 1999, Cisco Systems, Inc. www.cisco.com ICND—960

© 1999, Cisco Systems, Inc. www.cisco.com ICND—961

© 1999, Cisco Systems, Inc. www.cisco.com ICND—962

© 1999, Cisco Systems, Inc. www.cisco.com ICND—964

© 1999, Cisco Systems, Inc. www.cisco.com ICND—966

© 1999, Cisco Systems, Inc. www.cisco.com ICND—968

© 1999, Cisco Systems, Inc. www.cisco.com ICND—969

© 1999, Cisco Systems, Inc. www.cisco.com ICND—970