SIMULATION Guidelines This is a lab item in which tasks will be performed on virtual devices. - Refer to the Tasks tab to view the tasks for this lab item. - Refer to the Topology tab to access the de

SIMULATION Guidelines This is a lab item in which tasks will be performed on virtual devices. - Refer to the Tasks tab to view the tasks for this lab item. - Refer to the Topology tab to access the device console(s) and perform the tasks. - Console access is available for all required devices by clicking the device icon or using the tab(s) above the console window. - All necessary preconfigurations have been applied. - Do not change the enable password or hostname for any device. - Save your configurations to NVRAM before moving to the next item. - Click Next at the bottom of the screen to submit this lab and move to the next question. - When Next is clicked, the lab closes and cannot be reopened. Topology Tasks R2 and R3 are routers that perform multicast operations. Candidates are required to perform the below configuration and verification tasks on R1 and R2. 1. Configure R2 and R3 to be able to process, route and forward multicast packets. 2. Configure R3 as the root of the shared tree for the any source multicast domain. 3. Configure R1 as the receiver for group 239.100.100.1 and ensure a ping to that group from R4 is successful. Initial configuration with IP addressing has been completed. The candidate must not make any changes to the configurations except to fulfill the tasks listed above. Use non-proprietary protocol where needed. Only use the provided logical interface for the applicable task. Answer: 1. Enable Multicast Routing on R2 and R3 To process, route, and forward multicast packets, multicast routing must be enabled globally, and PIM (Protocol Independent Multicast) must be configured on the appropriate interfaces. Commands on R2 and R3: R2(config)# ip multicast-routing R2(config)# interface e0/0 R2(config-if)# ip pim sparse-mode R2(config)# interface e0/1 R2(config-if)# ip pim sparse-mode R2(config)# interface loopback 0 R2(config-if)# ip pim sparse-mode R3(config)# ip multicast-routing R3(config)# interface e0/0 R3(config-if)# ip pim sparse-mode R3(config)# interface e0/1 R3(config-if)# ip pim sparse-mode R3(config)# interface loopback 0 R3(config-if)# ip pim sparse-mode enables multicast routing globally. ip multicast-routing enables PIM in Sparse Mode on interfaces. ip pim sparse-mode 2. Configure R3 as the Root of the Shared Tree (Rendezvous Point - RP) To configure R3 as the RP for the multicast domain, use Auto-RP or Static RP. Here, we configure Static RP for group 239.100.100.1. Commands on R2 and R3: R2(config)# ip pim rp-address 3.3.3.3 R3(config)# ip pim rp-address 3.3.3.3 ip pim rp-address <RP-IP>: Configures R3's Loopback0 IP (3.3.3.3) as the RP for the multicast domain. Task 3: Configure R1 as the Receiver for Group 239.100.100.1 To configure R1 as a multicast receiver, enable IGMP (Internet Group Management Protocol) on R1's e0/0 interface. Commands on R1: R1(config)# interface e0/0 R1(config-if)# ip igmp join-group 239.100.100.1 <group>: Forces R1 to join the multicast group 239.100.100.1. ip igmp join-group Verification: Ensure Ping to Group 239.100.100.1 is Successful from R4 To verify multicast group reachability: 1. Send Multicast Traffic from R4: R4# ping 239.100.100.1 repeat 5 2. Verify Multicast Routing Table on R2 and R3: R2# show ip mroute R3# show ip mroute 3. Verify IGMP Group Membership on R1: R1# show ip igmp groups Complete Summary of Configurations: 1. R2 Configuration: ip multicast-routing interface e0/0 ip pim sparse-mode interface e0/1 ip pim sparse-mode interface loopback 0 ip pim sparse-mode ip pim rp-address 3.3.3.3 2. R3 Configuration: ip multicast-routing interface e0/0 ip pim sparse-mode interface e0/1 ip pim sparse-mode interface loopback 0 ip pim sparse-mode ip pim rp-address 3.3.3.3 3. R1 Configuration: interface e0/0 ip igmp join-group 239.100.100.1 Verification Checklist: 1. R3 is the RP: Use mapping.. show ip pim rp 2. R1 is a Group Member: Verify with groups. show ip igmp 3. Multicast Traffic Flows: Use ping 239.100.100.1 from R4 and verify success.