Aug 29
20071.1 RIP定时器配置
Filed Under (三层路由) by boymg on 29-08-2007
实验目的:调试RIP协议定时器工作原理
R1:
- !
- interface Serial1/0
- ip address 13.1.1.1 255.255.255.0
- serial restart-delay 0
- !
- interface Serial1/1
- ip address 12.1.1.1 255.255.255.0
- serial restart-delay 0
- !
- router rip
- network 12.0.0.0
- network 13.0.0.0
- !
R2:
- !
- interface Loopback0
- ip address 2.2.2.2 255.255.255.0
- !
- !
- interface Serial1/0
- ip address 12.1.1.2 255.255.255.0
- serial restart-delay 0
- !
- router rip
- network 2.0.0.0
- network 12.0.0.0
- !
R3:
- !
- interface Loopback0
- ip address 3.3.3.3 255.255.255.0
- !
- !
- interface Serial1/1
- ip address 13.1.1.3 255.255.255.0
- serial restart-delay 0
- !
- !
- router rip
- network 3.0.0.0
- network 13.0.0.0
- !
监测配置:
R1#show ip route rip
- R 2.0.0.0/8 [120/1] via 12.1.1.2, 00:00:12, Serial1/1
- R 3.0.0.0/8 [120/1] via 13.1.1.3, 00:00:19, Serial1/0
R2#show ip route rip
- R 3.0.0.0/8 [120/2] via 12.1.1.1, 00:00:20, Serial1/0
- R 13.0.0.0/8 [120/1] via 12.1.1.1, 00:00:20, Serial1/0
R3#show ip route rip
- R 2.0.0.0/8 [120/2] via 13.1.1.1, 00:00:24, Serial1/1
- R 12.0.0.0/8 [120/1] via 13.1.1.1, 00:00:24, Serial1/1
接下来我们控制R1不接受R2的RIP更新信息(即认为R2链路down掉)
R1#debug ip routing
R1#debug ip rip
R1(config)#access-list 101 deny udp any any eq rip
R1(config)#access-list 101 permit ip any any
R1(config-if)#ip access-group 101 in
稍等大约180秒,看到如下信息
- *Aug 29 21:31:36.335: RT: delete route to 2.0.0.0 via 12.1.1.2, rip metric [120/1]
- *Aug 29 21:31:36.335: RT: no routes to 2.0.0.0, entering holddown
- *Aug 29 21:31:38.339: RIP: sending v1 flash update to 255.255.255.255 via Serial1/0 (13.1.1.1)
- *Aug 29 21:31:38.339: RIP: build flash update entries
- *Aug 29 21:31:38.343: network 2.0.0.0 metric 16
- *Aug 29 21:31:38.343: RIP: sending v1 flash update to 255.255.255.255 via Serial1/1 (12.1.1.1)
- *Aug 29 21:31:38.347: RIP: build flash update entries
- *Aug 29 21:31:38.347: network 2.0.0.0 metric 16
- *Aug 29 21:31:40.387: RIP: received v1 update from 13.1.1.3 on Serial1/0
- *Aug 29 21:31:40.391: 2.0.0.0 in 16 hops (inaccessible)
R1#show ip route rip
- R 2.0.0.0/8 is possibly down, routing via 12.1.1.2, Serial1/1
- R 3.0.0.0/8 [120/1] via 13.1.1.3, 00:00:09, Serial1/0
再过60秒钟(注意前面的时间)
- *Aug 29 21:32:36.339: RT: delete network route to 2.0.0.0
- *Aug 29 21:32:36.339: RT: NET-RED 2.0.0.0/8
R1#show ip route rip
- R 3.0.0.0/8 [120/1] via 13.1.1.3, 00:00:07, Serial1/0
进行定时器配置
R1(config)#int s1/1
R1(config-if)#no ip access-group 101 in
用法:timers basic 【Interval between updates】【Invalid】【Holddown】【Flush】
R1(config-router)#timers basic 5 10 30 20
R2(config-router)#timers basic 5 10 30 20
R3(config-router)#timers basic 5 10 30 20
接下来,仍进行上述配置
R1(config)#int s1/1
R1(config-if)#ip access-group 101 in
R1(config-if)#end
R1#debug ip routing
R1#debug ip rip
- *Aug 29 21:42:46.351: RT: delete route to 2.0.0.0 via 12.1.1.2, rip metric [120/1]
- *Aug 29 21:42:46.351: RT: no routes to 2.0.0.0, entering holddown
R1#show ip route rip
- R 2.0.0.0/8 is possibly down, routing via 12.1.1.2, Serial1/1
- R 3.0.0.0/8 [120/1] via 13.1.1.3, 00:00:03, Serial1/0
- *Aug 29 21:42:56.355: RT: delete network route to 2.0.0.0
- *Aug 29 21:42:56.355: RT: NET-RED 2.0.0.0/8
R1#show ip route rip
- R 3.0.0.0/8 [120/1] via 13.1.1.3, 00:00:02, Serial1/0
看到,从Holddown到路由消失间隔为10秒,即上面两段代码第一行的时间显示。Invail计时器与Flush计时器之差为10秒
补充知识:
关于rip计时器这一块内容,我觉得还是理解最重要,理论知识其实本身的意义并不大,我希望我们都可以通过实验来看到现象.
下面简单介绍一下,并且看一些实验结果.

各段计时器时间如上图所示,下面具体谈谈每一段.
在距离矢量路由协议里面,路由器会将它学习的整张路由表信息更新发出去,Rip使用4种计时器来管理它的性能.
周期更新计时器 周期更新计时器用于设置定期路由更新的时间间隔(一般为30s),在这个间隔里路由器发送一个自己路由表的完整拷贝到所有相邻的路由器.下面看看实验现象.
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:02, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:06, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:17, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:26, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:00, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:05, Serial1/0
周期更新计时器就如上面显示的实验现象一样,不断的更新自己的路由表信息.
无效计时器 用于决定一个时间长度,即路由器在认定一个路由成为无效路由之前所需要等待的时间(180s,实际情况往往略大于180s).如果路由器在更新计时器期间没有得到关于某个指定路由的任何更新消息,它将认为这个路由失效,这时就会进入到无效计时器阶段.当这一情况发生时,这个路由器将会给它所有的邻居发送一个更新消息以通知它们这个路由已经无效.下面看看实验现象.这是进入到无效计时器后的状态.
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:09, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:28, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:30, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:32, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:36, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:49, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:00:54, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:01:59, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:02:50, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:02:58, Serial1/0
R 192.168.2.0/24 [120/1] via 148.1.1.2, 00:03:02, Serial1/0
保持计时器 用于设置路由信息被抑制的时间数量.当上述无效计时器计时完毕后,就会进入到保持计数器阶段.也可理解为,当指示某个路由为不可达的更新数据包被接受到时,路由器将会进入保持失效状态.这个状态将会一直持续到一个带有更好度量的更新数据包被接受到或者这个保持计时器到期.默认时,它的取值是180s.在进入到这个阶段的前60s,会显示一个如下的路由信息possibly down,这时路由器并没有直接删除这条路由信息,但记住,若此时该路由恢复正常通讯,路由表信息也不会更新,在接下来的120s会起到一个保持网络稳定的作用,此时会通告其他相连接的路由器删除这条路由信息。(关于后120s的作用,若有高人能解释的更详细,希望多多指教,让大家也更清楚一点).
R 192.168.2.0/24 is possibly down, routing via 148.1.1.2, Serial1/0
刷新计时器 用于设置某个路由成为无效路由并将它从路由表中删除的时间间隔(240s).这个计时器是刚开始就启动的,一直到保持计时器进行到60s时,它将路由表刷新.
以上就是关于Rip计时器的简单介绍,希望大家都可以自己去做做实验去看一下计时器的现象.

