Lab 7-3 – Configuring RIP Timers
In this lab you will learn how to modify the update timer, invalid timer, hold down timer and flush timer to decrease convergence time of a RIP routed network.
Real World Application & Core Knowledge
In today’s networks the convergence time for RIP just isn’t fast enough. With the default timers, RIP convergence can take longer than three minutes which is just completely unacceptable in today’s networks.
If you take a look back to lab 7-1 – Configuring Routing Information Protocol (RIP) it discusses the different types of timers and what they do. In this lab you’ll learn how to modify the timers to decrease convergence time.
The timers are configured in rip router configuration mode as a global setting however the update timer can be configured on a per interface basis.
To set the timers you’ll use the timers basic update# invalid# holddown# flush#. Each # is represented as a value in seconds. i.e; timers basic 30 40 10 60
To set the update timers manually per interface you’ll use the ip rip advertise # where as # is the interval in seconds at which updates are sent.
This lab will use the same logical topology as used in Lab 7-2 which is shown below;
In this lab you will configure the timers on all routers to 30 second updates, 40 second invalid, 10 second hold down and 60 second flush and manually set R3 to send updates to R2 every 10 seconds over interface Serial0/0.322
Familiarize yourself with the following new command(s);
timers basic 30 40 10 60 – This command is executed in rip router configuration mode to globally set the update, invalid, hold down and flush timers of the RIP routing process.
ip rip advertise # – This command is executed in interface configuration mode to specify the interval in seconds at which RIP updates are sent out the specific interface.
Lab Prerequisites
- If you are using GNS3 than load the Stub Area Networking GNS3 topology than start devices; R1, R2 and R3.
- Establish a console session with devices R1, R2 and R3 than load the initial configurations provided below by copying the config from the textbox and pasting it into the respected routers console.
Lab Objectives
- Configure the RIP timers on R1, R2 and R3 to 30 second updates, 40 second invalid, 10 second hold and 60 second flush. Verify your configuring.
- On R3 configure Serial0/0.322 to send updates every 10 seconds towards R2. Verify your configuration.
Lab Instruction
Objective 1. – Configure the RIP timers on R1, R2 and R3 to 30 second updates, 40 second invalid, 10 second hold and 60 second flush. Verify your configuring.
R1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R1(config)#router rip R1(config-router)#timers basic 30 40 10 60 R1(config-router)#end R1#show ip protocols Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 26 seconds Invalid after 40 seconds, hold down 10, flushed after 60 Redistributing: rip Default version control: send version 2, receive version 2 Interface Send Recv Triggered RIP Key-chain Serial0/0.122 2 2 Serial0/1 2 2 Loopback0 2 2 Loopback1 2 2 Automatic network summarization is in effect Maximum path: 4 Routing for Networks: 10.0.0.0 Routing Information Sources: Gateway Distance Last Update 10.70.12.2 120 00:00:05 10.70.21.2 120 00:00:05 Distance: (default is 120) R1#
R2#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R2(config)#router rip R2(config-router)#timers basic 30 40 10 60 R2(config-router)#end R2#show ip protocols Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 16 seconds Invalid after 40 seconds, hold down 10, flushed after 60 Redistributing: rip Default version control: send version 2, receive version 2 Interface Send Recv Triggered RIP Key-chain Serial0/0.221 2 2 Serial0/0.223 2 2 Serial0/1 2 2 Loopback0 2 2 Automatic network summarization is in effect Maximum path: 4 Routing for Networks: 10.0.0.0 Routing Information Sources: Gateway Distance Last Update 10.70.12.1 120 00:00:15 10.70.23.2 120 00:00:03 10.70.21.1 120 00:00:06 Distance: (default is 120) R2#
R3#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R3(config)#router rip R3(config-router)#timers basic 30 40 10 60 R3(config-router)#end R3#show ip protocols Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 22 seconds Invalid after 40 seconds, hold down 10, flushed after 60 Redistributing: rip Default version control: send version 2, receive version 2 Interface Send Recv Triggered RIP Key-chain Serial0/0.322 2 2 Loopback0 2 2 Automatic network summarization is in effect Maximum path: 4 Routing for Networks: 10.0.0.0 Routing Information Sources: Gateway Distance Last Update 10.70.23.1 120 00:00:21 Distance: (default is 120) R3#
Objective 2. – On R3 configure Serial0/0.322 to send updates every 10 seconds towards R2. Verify your configuration.
R3#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R3(config)#interface Serial0/0.322 R3(config-subif)#ip rip advertise 10 R3(config-subif)#end
There are three ways to verify that the interface timer that you’ve configured is operating properly. The first method of verification is that you can run debug ip rip events on R2 to view how often the updates are coming from R3, they should be approximately 10 seconds apart give or take a few seconds.
The second method you can use to verify that the interface specific advertisement timer is operating correctly is using the show ip protocols command on R2 and you should see the last update received from 10.70.23.2 never go above 10 seconds.
And the last method of verification however is not documented in any Cisco documentation and the command is a hidden command that will not show up when using the ?. The command is called show ip rip timers This command is very vague and does not display any details at all however it does show the update intervals on a per interface basis. This command will show the time it the router will wait before it sends another update through an interface.
When you do show ip protocols under rip you’ll see the interfaces listed in order as shown below;
R3#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 6 seconds
Invalid after 40 seconds, hold down 10, flushed after 60
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0.322 2 2
Loopback0 2 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
Routing Information Sources:
Gateway Distance Last Update
10.70.23.1 120 00:00:11
Distance: (default is 120)
R3#
You can see that Serial0/0.322 is listed first and Loopback0 is second. Now when you execute the show ip rip timers command in privileged mode you’ll see the following output;
R3#show ip rip timers
RIP timers
Expiration Type
| 3.680 (parent)
| 3.680 Ager interval
| 7.172 (parent)
| 7.172 Periodic update
| 25.722 Periodic update
R3#
When you look at the output you’ll see two Periodic update timers, the first one being Serial0/0.322 which will send its next update in 7.172 seconds and Loopback0 which will send its next update in 25.722 seconds.
Note that the Ager interval is the “hold down” timer.
>>>>>>Hi<<<<<<<
R1(config-if)#shu
R1(config-if)#
RIP-DB: flush route of 10.70.10.0/24 on Loopback0
RIP-DB: Remove 10.70.10.0/24, (metric 4294967295) via 0.0.0.0, Loopback0 (permanent)
R2#
RIP-DB: Remove 10.70.10.0/24, (metric 4294967295) via 10.70.21.1, Serial1/1
RIP-DB: Remove 10.70.10.0/24, (metric 4294967295) via 10.70.12.1, Serial1/0.221
As you can see Flushing happened immediately without considering all timers which we studied! R2 has same story too !
So in RIP v2 or newer upgraded ,the Invalid or Flush timer are not applied?
When you administratively shut down an interface an update is automatically triggered. Route information regarding the prefix connected to Lo0 on R1 is advertised to R2 via Serial0/1 and Serial0/0.122
You should shut down Serial0/1 then shutdown Serial0/0.122 and that would demonstrate the operation of the different timers on R2 using debugs.
-Free CCNA Workbook Author
i am instructor and dont have good labs to give
and now i have 
, if pdf version is also avialable for labs it will be good
in love with this website ……..
thanks and regards
atul sharma