Section 9: Multicast (4 Points)
Enable your network to allow hosts on VLAN4 to receive and send multicast traffic from and to VLAN2; only perform configuration on R5 and R6 using PIM sparse dense mode.
This question simply requires basic multicast setup between R5 and R6 using PIM sparse-dense-mode. If you have configured this correctly as shown in Example 1-65 and Example 1-66, you have scored 1 point.
Example 1-65 R5 Multicast Configuration
ip multicast-routing ! interface FastEthernet0/0 ip pim sparse-dense-mode ! interface ATM3/0 ip pim sparse-dense-mode
Example 1-66 R6 Multicast Configuration
ip multicast-routing ! interface FastEthernet0/0 ip pim sparse-dense-mode ! interface ATM1/0.99 point-to-point ip pim sparse-dense-mode
Configure R6 to respond to pings from R5 to the multicast address of 184.108.40.206.
Configure ip igmp join-group 220.127.116.11 under R6 fastEthernet0/0. If you have configured this correctly, you have scored 1 point.
Do not allow R5 to fully participate in the PIM process by not allowing it to become a neighbor but do allow any IGMP messages generated by hosts on VLAN4 to be received by R6.
This question requires Stub Multicast Routing. This allows you to configure remote/stub routers as IGMP proxy agents. The stub router does not fully participating in PIM and, hence, is not seen as a PIM neighbor; access-list 11 blocks the neighbor. If you have configured this correctly as in Example 1-67, you have scored 2 points.
Example 1-67 R6 Stub Multicast Configuration
interface ATM1/0.99 point-to-point ip pim neighbor-filter 11 ! access-list 11 deny 10.99.99.2