• Configure R6 to stop announcing itself as an RP.
• Configure R5 to join the group FF76:0640:2001:CC1E::8 on its VLAN 58
interface.
• Make sure R1 can still ping this group without any router in the domain
learning the RP information via the BSR.
------------------------------------------------------------------
R5:
interface FastEthernet 0/0
ipv6 mld join-group ff76:0640:2001:CC1E::8
R6:
no ipv6 pim bsr candidate rp FC00:1:0:6::6 priority 100
!
interface Loopback300
ipv6 address 2001:CC1E::6/128
ipv6 eigrp 100
ipv6 rip RIPNG enable
------------------------------------------------------------------
Rack1R5#show ipv6 pim range-list
Rack1R4#show ipv6 pim range-list
Rack1R1#ping ipv6 FF76:640:2001:CC1E::8 repeat 1000
Output Interface: FastEthernet0/0
Rack1R4#show ipv6 mroute
---------------------------
P.S 你應該不會從R1 ping的到R5 ,因為R5身上有過濾條件
Thanks for this correction.
i also had the same problem, and spent quite a bit of time scratching my head on why R4 was not getting the new group in the Range-List. The issue is definitely a result of the 9.25 filter (MLD_FILTER)..
In this particular task (9.27 Embedded RP), we are asked to join the group on R5's vlan58 (F0/0). However, as the previous task (9.25 MLD_FILTER) placed a filter on that interface, the new groups is never seen by R4 (as is needed).
Three Options (SG needs updating):
1. remove filter on F0/0 (as Belal suggests above)
2. or move the join group to another interface (which does not have the FILTER)
3. or modify the MLD_FILTER to include this new multicast group
i also had the same problem, and spent quite a bit of time scratching my head on why R4 was not getting the new group in the Range-List. The issue is definitely a result of the 9.25 filter (MLD_FILTER)..
In this particular task (9.27 Embedded RP), we are asked to join the group on R5's vlan58 (F0/0). However, as the previous task (9.25 MLD_FILTER) placed a filter on that interface, the new groups is never seen by R4 (as is needed).
Three Options (SG needs updating):
1. remove filter on F0/0 (as Belal suggests above)
2. or move the join group to another interface (which does not have the FILTER)
3. or modify the MLD_FILTER to include this new multicast group
沒有留言:
張貼留言