From: ccie candidate (ccie1@xxxxxxxxx)
Date: Fri Aug 09 2002 - 06:43:36 GMT-3
in sparse-dense-mode when there is no RP mapped to certain group , the router
will work dense mode , that is why R2 can ping .
try to change to sparse mode only and see .
--On Fri, 09 Aug 2002 07:40:08 Gordan Chan wrote: >Hi Group, > >I am doing exercise on multicast and encounter some problems. > >e0-R1-s0-------s0-R2 > >R1's ethernet has join two groups. I hope it becomes the rp of only 1 group >by adding an access list >I expect R2 can only ping the 230.1.1.1, but R2 can ping both groups. Could >someone give me some hints? > > >Thank you. > >Chan > >R1's config > >ip multicast-routing >interface Ethernet0 >ip address 172.16.10.1 255.255.255.0 >no ip directed-broadcast >ip pim sparse-dense-mode >ip igmp join-group 230.1.1.1 >ip igmp join-group 230.2.2.2 >no keepalive > >interface Serial0 >ip address 172.16.12.1 255.255.255.0 >ip pim sparse-dense-mode > >ip pim send-rp-discovery Loopback0 scope 15 >ip pim send-rp-announce Loopback0 scope 15 group-list 91 >! >access-list 91 permit 230.1.1.1 > > >R2 >ip multicast-routing >interface Serial0 >ip address 172.16.12.2 255.255.255.0 >no ip directed-broadcast >ip pim sparse-dense-mode > >R2#ping 230.1.1.1 > >Type escape sequence to abort. >Sending 1, 100-byte ICMP Echos to 230.1.1.1, timeout is 2 seconds: > >Reply to request 0 from 172.16.12.1, 40 ms >Reply to request 0 from 172.16.12.1, 48 ms >R2#ping 230.2.2.2 > >Type escape sequence to abort. >Sending 1, 100-byte ICMP Echos to 230.2.2.2, timeout is 2 seconds: > >Reply to request 0 from 172.16.12.1, 44 ms >Reply to request 0 from 172.16.12.1, 52 ms > >R2#sh ip pim rp >Group: 230.1.1.1, RP: 172.16.1.1, v2, v1, uptime 00:03:21, expires 00:02:40 > >R2#sh ip pim rp map >PIM Group-to-RP Mappings > >Group(s) 230.1.1.1/32 > RP 172.16.1.1 (?), v2v1 > Info source: 172.16.1.1 (?), via Auto-RP > Uptime: 00:03:38, expires: 00:02:16 > > > > >
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:21 GMT-3