RIP手动汇总的问题

qz357

开启了协议RIPv2（已经检查都通告了相关的子网），开始的时候，R2和R4的S0/0都开启了ip rip triggered，
然后再在R4的s0/0那里ip summary-address rip 1.1.0.0 255.255.252.0
结果是R3\R1\R2都得不到通告的1.0.0.0子网，也没有手动汇总的路由
在R4 debug ip rip 一下，看到build update entries - suppressing null update
估计是汇总路由进入了黑洞，求大神解救！！！



《PS：在R3做的汇总则可以通告出去，会不会是serial链路的问题？》

qz357

m490198574

px5285177

我是按照你的IP搭的拓扑,接口编号不同. R4上面起了2个Lo ,没起4个.


在没有接口配trigger之前

C    192.168.12.0/24 is directly connected, FastEthernet0/1
     1.0.0.0/24 is subnetted, 2 subnets
R       1.1.1.0 [120/2] via 192.168.12.2, 00:00:04, FastEthernet0/1
R       1.1.2.0 [120/2] via 192.168.12.2, 00:00:04, FastEthernet0/1
     172.16.0.0/24 is subnetted, 1 subnets
R       172.16.0.0 [120/1] via 192.168.12.2, 00:00:28, FastEthernet0/1
     10.0.0.0/24 is subnetted, 1 subnets
R       10.1.1.0 [120/1] via 192.168.12.2, 00:00:28, FastEthernet0/1
R1#
=======================================================
R2,R4开  debug  ip rip
接口开R2(config-if)#ip rip tr    R4(config-if)#ip rip tr

*Aug  9 16:27:08.847: RIP: sending triggered request on Serial1/0 to 224.0.0.9
*Aug  9 16:27:08.959: RIP: received v2 triggered update from 172.16.0.4 on Serial1/0
*Aug  9 16:27:08.959: RIP: sending v2 ack to 172.16.0.4 via Serial1/0 (172.16.0.2),
     flush, seq# 0
*Aug  9 16:27:08.963: RIP: send v2 triggered flush update to 172.16.0.4 on Serial1/0 with no route
*Aug  9 16:27:08.963: RIP: start retransmit timer of 172.16.0.4
*Aug  9 16:27:08.967:      1.1.1.0/24 via 0.0.0.0 in 1 hops
*Aug  9 16:27:08.967:      1.1.2.0/24 via 0.0.0.0 in 1 hops
*Aug  9 16:27:09.075: RIP: received
R2(config-if)#v2 triggered ack from 172.16.0.4 on Serial1/0
     flush seq# 0
*Aug  9 16:27:09.079: RIP: send v2 triggered update to 172.16.0.4 on Serial1/0
*Aug  9 16:27:09.079: RIP: build update entries
*Aug  9 16:27:09.079:   route 1: 192.168.12.0/24 metric 1, tag 0
*Aug  9 16:27:09.079:   route 3: 10.1.1.0/24 metric 1, tag 0
*Aug  9 16:27:09.083: RIP: Update contains 2 routes, start 1, end 9
*Aug  9 16:27:09.083: RIP: start retransmit timer of 172.16.0.4
*Aug  9 16:27:09.159: RIP: received v2 triggered ack from 172.16.0.4 on Serial1/0

//debug 信息可以看出R2收到了R4的环回口明细路由. 并且R2也把自己的路由发给了R4

R4(config-if)#ip summary-address rip 1.0.0.0 255.0.0.0//在R4上做汇总.
R4(config-if)#
*Aug  9 16:27:47.143: RIP: send v2 triggered flush update to 172.16.0.2 on Serial1/0 with no route
*Aug  9 16:27:47.147: RIP: start retransmit timer of 172.16.0.2
*Aug  9 16:27:47.227: RIP: received v2 triggered ack from 172.16.0.2 on Serial1/0
     flush seq# 1
*Aug  9 16:27:47.227: RIP: send v2 triggered update to 172.16.0.2 on Serial1/0
*Aug  9 16:27:47.227: RIP: build update entries
*Aug  9 16:27:47.231:   route 1: 1.1.1.0/24 metric 16, tag 0
*Aug  9 16:27:47.231:   route 3: 1.1.2.0/24 metric 16, tag 0
*Aug  9 16:27:47.231:   route 10: 1.0.0.0/8 metric 1, tag 0
*Aug  9 16:27:47.235: RIP: Update contains 3 routes, start 1, end 10
R4(config-if)#
*Aug  9 16:27:47.235: RIP: start retransmit timer of 172.16.0.2
*Aug  9 16:27:47.295: RIP: received v2 triggered ack from 172.16.0.2 on Serial1/0
     seq# 2


//这里看到R4把汇总发给R2,同时把明细的metric设为16.不可达.


//R2上只有汇总后的路由了...

//R1上只有汇总后的路由了...


实验现象没有问题

qz357

px5285177 发表于 2013-8-9 16:34
我是按照你的IP搭的拓扑,接口编号不同. R4上面起了2个Lo ,没起4个.

很奇怪，我这里不行。在排错中

px5285177

qz357 发表于 2013-8-9 17:00
很奇怪，我这里不行。在排错中

你检查一下 RIP的宣告....比如 宣告network 192.168.0.0   172.16.0.0.  1.0.0.0  
好像宣告0.0.0.0这样会有问题

qz357

px5285177 发表于 2013-8-9 17:28
你检查一下 RIP的宣告....比如 宣告network 192.168.0.0   172.16.0.0.  1.0.0.0  
好像宣告0.0.0.0这样 ...

请问我的步骤有漏吗？
R1:
interface Loopback0
ip address 192.168.1.1 255.255.255.0


interface Serial0/0
ip address 123.12.1.1 255.255.255.0
clock rate 64000


router rip
version 2
network 123.0.0.0
network 192.168.1.0
no auto-summary


sh ip route
     123.0.0.0/24 is subnetted, 1 subnets
C       123.12.1.0 is directly connected, Serial0/0
C    192.168.1.0/24 is directly connected, Loopback0


R2：
interface Loopback0
ip address 1.1.1.1 255.255.255.0 secondary
ip address 1.1.0.1 255.255.255.0


interface Serial0/0
ip address 123.12.1.2 255.255.255.0
ip summary-address rip 1.1.0.0 255.255.252.0
clock rate 64000


router rip
version 2
network 1.0.0.0
network 123.0.0.0
no auto-summary


sh ip route
     1.0.0.0/24 is subnetted, 2 subnets
C       1.1.0.0 is directly connected, Loopback0
C       1.1.1.0 is directly connected, Loopback0
     123.0.0.0/24 is subnetted, 1 subnets
C       123.12.1.0 is directly connected, Serial0/0
R    192.168.1.0/24 [120/1] via 123.12.1.1, 00:00:08, Serial0/0


debug ip rip
*Mar  1 00:18:44.543: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.2)
*Mar  1 00:18:44.543: RIP: build update entries - suppressing null update
R2(config-if)#
*Mar  1 00:18:49.007: RIP: received v2 update from 123.12.1.1 on Serial0/0
*Mar  1 00:18:49.011:      192.168.1.0/24 via 0.0.0.0 in 1 hops
R2(config-if)#
*Mar  1 00:18:51.347: RIP: sending v2 update to 224.0.0.9 via Loopback0 (1.1.0.1)
*Mar  1 00:18:51.347: RIP: build update entries
*Mar  1 00:18:51.347:   123.12.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:18:51.351:   192.168.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 00:18:51.355: RIP: ignored v2 packet from 1.1.0.1 (sourced from one of our addresses)
R2(config-if)#
*Mar  1 00:19:14.135: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.2)
*Mar  1 00:19:14.135: RIP: build update entries - suppressing null update
R2(config-if)#
*Mar  1 00:19:17.419: RIP: sending v2 update to 224.0.0.9 via Loopback0 (1.1.0.1)
*Mar  1 00:19:17.419: RIP: build update entries
*Mar  1 00:19:17.419:   123.12.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:19:17.423:   192.168.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 00:19:17.427: RIP: ignored v2 packet from 1.1.0.1 (sourced from one of our addresses)
*Mar  1 00:19:17.699: RIP: received v2 update from 123.12.1.1 on Serial0/0
*Mar  1 00:19:17.699:      192.168.1.0/24 via 0.0.0.0 in 1 hops
R2(config-if)#
*Mar  1 00:19:41.979: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.2)
*Mar  1 00:19:41.979: RIP: build update entries - suppressing null update
R2(config-if)#
*Mar  1 00:19:43.803: RIP: received v2 update from 123.12.1.1 on Serial0/0
*Mar  1 00:19:43.803:      192.168.1.0/24 via 0.0.0.0 in 1 hops
R2(config-if)#
*Mar  1 00:19:46.155: RIP: sending v2 update to 224.0.0.9 via Loopback0 (1.1.0.1)
*Mar  1 00:19:46.155: RIP: build update entries
*Mar  1 00:19:46.155:   123.12.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:19:46.159:   192.168.1.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 00:19:46.163: RIP: ignored v2 packet from 1.1.0.1 (sourced from one of our addresses)

现在的情况就是R1收不到汇总路由

px5285177

R1#sh ip ro
     1.0.0.0/22 is subnetted, 1 subnets
R       1.1.0.0 [120/1] via 123.12.1.2, 00:00:17, Serial0/0
     123.0.0.0/24 is subnetted, 1 subnets
C       123.12.1.0 is directly connected, Serial0/0
C    192.168.1.0/24 is directly connected, Loopback0
R1#sh ip rip data
1.0.0.0/8    auto-summary
1.1.0.0/22
    [1] via 123.12.1.2, 00:00:22, Serial0/0
123.0.0.0/8    auto-summary
123.12.1.0/24    directly connected, Serial0/0
192.168.1.0/24    auto-summary
192.168.1.0/24    directly connected, Loopback0


=====================================================


     1.0.0.0/24 is subnetted, 2 subnets
C       1.1.0.0 is directly connected, Loopback0
C       1.1.1.0 is directly connected, Loopback0
     123.0.0.0/24 is subnetted, 1 subnets
C       123.12.1.0 is directly connected, Serial0/0
R    192.168.1.0/24 [120/1] via 123.12.1.1, 00:00:01, Serial0/0

R2#sh ip rip data
1.0.0.0/8    auto-summary
1.1.0.0/22    int-summary
1.1.0.0/24    directly connected, Loopback0
1.1.1.0/24    directly connected, Loopback0
123.0.0.0/8    auto-summary
123.12.1.0/24    directly connected, Serial0/0
192.168.1.0/24    auto-summary
192.168.1.0/24
    [1] via 123.12.1.1, 00:00:07, Serial0/0


=========================================================
R2#
*Mar  1 00:04:33.007: RIP: received v2 update from 123.12.1.1 on Serial0/0
*Mar  1 00:04:33.007:      192.168.1.0/24 via 0.0.0.0 in 1 hops
R2#
*Mar  1 00:04:39.335: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.2)
*Mar  1 00:04:39.335: RIP: build update entries
*Mar  1 00:04:39.335:   1.1.0.0/22 via 0.0.0.0, metric 1, tag 0
R2#
*Mar  1 00:05:00.555: RIP: received v2 update from 123.12.1.1 on Serial0/0
*Mar  1 00:05:00.555:      192.168.1.0/24 via 0.0.0.0 in 1 hops
R2#
*Mar  1 00:05:05.415: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.2)
*Mar  1 00:05:05.415: RIP: build update entries
*Mar  1 00:05:05.415:   1.1.0.0/22 via 0.0.0.0, metric 1, tag 0
R2#
===============================================
R1#
*Mar  1 00:03:57.931: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.1)
*Mar  1 00:03:57.931: RIP: build update entries
*Mar  1 00:03:57.931:   192.168.1.0/24 via 0.0.0.0, metric 1, tag 0
R1#
*Mar  1 00:04:03.147: RIP: received v2 update from 123.12.1.2 on Serial0/0
*Mar  1 00:04:03.147:      1.1.0.0/22 via 0.0.0.0 in 1 hops
R1#
*Mar  1 00:04:24.299: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.1)
*Mar  1 00:04:24.299: RIP: build update entries
*Mar  1 00:04:24.299:   192.168.1.0/24 via 0.0.0.0, metric 1, tag 0
R1#
*Mar  1 00:04:30.687: RIP: received v2 update from 123.12.1.2 on Serial0/0
*Mar  1 00:04:30.687:      1.1.0.0/22 via 0.0.0.0 in 1 hops
R1#
*Mar  1 00:04:51.831: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (123.12.1.1)
*Mar  1 00:04:51.831: RIP: build update entries
*Mar  1 00:04:51.831:   192.168.1.0/24 via 0.0.0.0, metric 1, tag 0
R1#
*Mar  1 00:04:56.735: RIP: received v2 update from 123.12.1.2 on Serial0/0
*Mar  1 00:04:56.735:      1.1.0.0/22 via 0.0.0.0 in 1 hops




我开了2台路由器,把你的配置直接刷上去..开了debug.  
一切都正常呀..你要不要试试清表  cle ip ro *

px5285177

QQ号码已经留言给你,你可以加

qz357

px5285177 发表于 2013-8-9 21:02
R1#sh ip ro
     1.0.0.0/22 is subnetted, 1 subnets
R       1.1.0.0 [120/1] via 123.12.1.2, 00:00: ...

已经用了很多次clear ip route *，估计是IOS问题了。。。我用的是2691

px5285177

平时我都用7200...用到3层交换机才用3725.

yuhucheng

trigger,你把这个特性关掉试试，我记得这个特性是开启纯触发更新，开启此特性后，周期性更新就停止了，仅当拓朴出现了改变影响到路由表的时候，才会回复发生周期
性更新，，，

ぺ啭裑の楛澀

zhznetwork

jlzhaoyunhua