Professional Documents
Culture Documents
Dynamic Routing
Holddown timer This sets the amount of time during which routing
information is suppressed. Routes will enter into the holddown state
when an update packet is received that indicated the route is
unreachable. This continues until either an update packet is received
with a better metric or until the holddown timer expires. The default is
180 seconds.
Route flush timer Sets the time between a route becoming invalid
and its removal from the routing table (240 seconds). Before its
removed from the table, the router notifies its neighbors of that routes
impending demise. The value of the route invalid timer must be less
than that of the route flush timer. This gives the router enough time to
tell its neighbors about the invalid route before the local routing table
is updated.
Once the static routes are deleted from the configuration, you
can add the RIP routing protocol by using the router rip
command and the network command. The network command
tells the routing protocol which network to advertise.
Lab_A(config)#router rip
Lab_A(config-router)#network 192.168.10.0
Lab_A(config-router)#network 192.168.20.0
Lab_A(config-router)#^Z
Lab_B
To configure RIP on the Lab_B router, you need to remove the
two static routes you added from the earlier example. Once you
make sure no routes are in the routing table with a better
administrative distance than 120, you can add RIP. The Lab_B
router has three directly connected networks and we want RIP to
advertise them all, so we will add three network statements.
Again, if you dont remove the static routes, RIP routes will never
be found in the routing table even though RIP will still be running
in the background causing a bunch of CPU processing on the
routers and gobbling up precious bandwidth.
Lab_B#config t
Enter configuration commands, one per line. End with CNTL/Z.
Lab_B(config)#no ip route 192.168.10.0 255.255.255.0 192.168.20.1
Lab_B(config)#no ip route 192.168.50.0 255.255.255.0 192.168.40.2
Lab_B(config)#router rip
Lab_B(config-router)#network 192.168.20.0
Lab_B(config-router)#network 192.168.30.0
Lab_B(config-router)#network 192.168.40.0
Lab_B(config-router)#^Z
Lab_C
Weve already removed the static routes on the Lab_C router
because we placed a default route on it. So all thats needed
here is to remove the default route from the Lab_C router.
Once its dust, you can turn on RIP routing for the two
directly connected routes.
Lab_C#config t
Enter configuration commands, one per line. End with CNTL/Z.
Lab_C(config)#no ip route 0.0.0.0 0.0.0.0 192.168.40.1
Lab_C(config)#router rip
Lab_C(config-router)#network 192.168.40.0
Lab_C(config-router)#network 192.168.50.0
Lab_C(config-router)#^Z
Lab_C#
Lab_A#sh ip route
[output cut]
Looking at this, you can see that the routing table has the same
entries that they had when we were using static routes, except for
that R. The R means that the networks were added dynamically
using the RIP routing protocol. The [120/1] is the administrative
distance of the route (120) along with the number of hops to that
Lab B
Lab_B#sh ip route
[output cut]
R 192.168.50.0 [120/1] via 172.16.40.2, 00:00:11, Serial0/1
C 192.168.40.0 is directly connected, Serial0/1
C 192.168.30.0 is directly connected, FastEthernet0/0
C 192.168.20.0 is directly connected, Serial0/0
R 192.168.10.0 [120/1] via 172.16.20.1, 00:00:21, Serial0/0
Lab_B#
Notice that here again the same networks are in the routing
table and they werent added manually.
So while yes, its true that RIP has worked really well in our little
internetwork, its not the solution for every enterprise. Thats
because this technique has a maximum hop count of only 15 (16 is
deemed unreachable) and it performs full routing-table updates
every 30 seconds, both
things that can wreak havoc in a larger internetwork.
Note one thing about RIP routing tables and the parameters used
to advertise remote networks. Notice, as an example, that the
following routing table shows [120/15] in the 192.168.10.0
network metric. This means that the administrative distance is
120, the default for RIP, but the hop count is 15. Remember that
each time a router sends out an update to a neighbor router, it
increments the hop count by one for each route
Lab_C#sh ip route
[output cut]
M
Lab_C(config)#router rip
Lab_C(config-router)#network 192.168.40.0
Lab_C(config-router)#network 192.168.50.0
Lab_C(config-router)#version 2
IGRP Timers
Lab_A#sh ip route
[output cut]