Skip to main content


CISCO组播RPF逆向路径转发实验原理(2)

2012-06-29 00:31 浏览:

  在R3上面,我们可以看到:

  本来以前在R3上面没有再接口f1/0删除命令ip pim sparse-mode之前:

  R3#show ip rpf 1.1.1.1

  RPF information for ? (1.1.1.1)

  RPF interface: FastEthernet1/0

  RPF neighbor: ? (3.1.1.1)

  RPF route/mask: 1.1.1.0/24

  RPF type: unicast (ospf 1)

  RPF recursion count: 0

  Doing distance-preferred lookups across tables

  当删除以后,再去看看rpf的检测:

  R3#show ip rpf 1.1.1.1

  RPF information for ? (1.1.1.1) failed, no route exists

  原因在于,因为R3在f1/0移除了pim协议,所以和对端f1/0建立不起来邻居,自然组播流量不会经过以太口进行转发,R3只有从s2/0收到组播流量,但是,在R3上面的路由表由于是ospf会选择最短的路径,所以回去的时候走的是以太口,路径不匹配,丢包...

  R3#show ip route 1.1.1.1

  Routing entry for 1.1.1.0/24

  Known via "ospf 1", distance 110, metric 2, type intra area

  Last update from 3.1.1.1 on FastEthernet1/0, 00:04:10 ago

  Routing Descriptor Blocks:

  * 3.1.1.1, from 3.1.1.1, 00:04:10 ago, via FastEthernet1/0

  Route metric is 2, traffic share count is 1

  在RPF的源检测标准中,只能有一个输入接口,选举方法如下:

  lower AD>longest match>lower metric>higher ip

  本文出自 “hank--我,只关注原理” 博客