Refer to the exhibit.R3 is:•failing to accept multicast RP information from Domain-A•advertising MSDP SA messages to R1 and R4•receiving SA messages only from R4Which command must the engineer implement to resolve the issue?
Answer(s): A
SIMULATIONGuidelinesThis 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 doses 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.
1. Enable Multicast Routing on R2 and R3To 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 ip multicast-routing enables multicast routing globally.ip pim sparse-mode enables PIM in Sparse Mode on interfaces.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.1To 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.1ip igmp join-group <group>: Forces R1 to join the multicast group 239.100.100.1.Verification: Ensure Ping to Group 239.100.100.1 is Successful from R4To verify multicast group reachability:1. Send Multicast Traffic from R4:R4# ping 239.100.100.1 repeat 52. Verify Multicast Routing Table on R2 and R3:R2# show ip mrouteR3# show ip mroute3. Verify IGMP Group Membership on R1:R1# show ip igmp groupsComplete Summary of Configurations:1. R2 Configuration:ip multicast-routinginterface e0/0 ip pim sparse-modeinterface e0/1 ip pim sparse-modeinterface loopback 0 ip pim sparse-modeip pim rp-address 3.3.3.32. R3 Configuration:ip multicast-routinginterface e0/0 ip pim sparse-modeinterface e0/1 ip pim sparse-modeinterface loopback 0 ip pim sparse-modeip pim rp-address 3.3.3.33. R1 Configuration:interface e0/0 ip igmp join-group 239.100.100.1Verification Checklist:1. R3 is the RP: Use show ip pim rp mapping..2. R1 is a Group Member: Verify with show ip igmp groups.3. Multicast Traffic Flows: Use ping 239.100.100.1 from R4 and verify success.
Refer to the exhibit.A network operator is working to filter routes from being advertised that are covered underan aggregate announcement. The receiving router of the aggregate announcement block is still getting some of the more specific routes plus the aggregate. Which configuration change ensures that only the aggregate is announced now and in the future if other networks are to be added?
Refer to the exhibit.A network operator is getting the route for 10.11.11 0/24 from two upstream providers on #XR3. The network operator must configure #XR3 to force the 10.11.11.0/24 prefix to route via next hop of 10.0.0.9 as primary when available. Which of these can the operator use the routing policy language for, to enforce this traffic forwarding path?
Answer(s): C
Refer to the exhibit.XR1 and XR2 are sending the prefix 10.11.11.0/24 to XR3. A configured policy on XR1 isincorrectly prepending AS path 11 11 12 12 onto this prefix. A network operator wants to add a policy onto XR3 that will not allow the falsely prepending prefix from being installed. Which policy configuration applied to the XR3 neighbor configuration for XR1 can accomplish this requirement without impact to other or futurereceived routes?
Answer(s): D
https://www.cisco.com/c/en/us/td/docs/routers/crs/software/crs_r4-1/routing/command/reference/b_routing_cr41crs/b_routing_cr41crs_chapter_01000.html#wp3850885229
Post your Comments and Discuss Cisco 300-510 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the 300-510 content, but please register or login to continue.