300-410 EIGRP OSPF Redistribution and PBR Simulation
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
Troubleshoot and resolve the issues to achieve these goals:
1. Ensure that R1 reaches the prefix 10.6.66.6 without any single point of failure in the path. Do not use a static route or policy-based routing to accomplish this.
2. Ensure that R1 loopback 1 reaches to R6’s loopback 1 by following the path through R1, R3, R5 to R6 and vice versa. Use metric values K1 = 100000, K2=1, K3=255, K4=10, K5=1500 to modify the default metric in EIGRP if required. Do not use a route-map.
3. Ensure that on R3, prefix 10.0.56.6/32 uses the SP1 to route to the Internet, whereas prefix 172.16.12.2/32 uses the SP2 to route to the Internet. Do not use BGP to accomplish this. Use the pre-configured route-maps SP1 and SP2 and modify to accomplish the task if required. Use the ping and trace commands from R6 and R2 to prefixes 209.165.202.132 and 209.165.202.128, respectively to verify the results.
Community Insight
The core challenge is resolving routing conflicts caused by mutual redistribution and incorrect Administrative Distance settings, while fixing broken ACLs in pre-configured route-maps to direct specific prefixes to different Service Providers.
This CCNP Enterprise simulation tests troubleshooting of EIGRP/OSPF redistribution, administrative distance manipulation, and Policy-Based Routing (PBR) using pre-configured route-maps. The solution requires adjusting metrics and removing conflicting static configurations to ensure specific traffic flows.
Candidates often fail to check for existing 'deny' statements in the provided ACLs within the route-maps, which block the required traffic before it can be matched. Additionally, many forget that R4's mutual redistribution creates a routing loop or suboptimal path unless Administrative Distance is manually adjusted on R3.
Community Discussion (34 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The simulation requires three distinct actions: first, ensuring redundancy for 10.6.66.6 by manipulating Administrative Distance (AD) so R3 prefers the EIGRP path over the OSPF external path learned via R4; second, configuring EIGRP metrics (K-values) to force the specific path through R5; and third, fixing the PBR on R3 by editing the SP1 and SP2 route-maps. The community confirms that the pre-configured ACLs often contain 'deny' entries for the target networks, which must be removed or corrected to permit the traffic.Why Other Candidate Answers Are Wrong
Incorrect approaches typically involve adding static routes, which violates the explicit constraint "Do not use a static route." Another common error is ignoring the AD conflict between EIGRP (AD 90) and OSPF External (AD 110); if R4 redistributes OSPF into EIGRP and vice versa, R3 might prefer the longer path via R4 unless the AD for the external prefix is raised above 110 or the internal EIGRP AD is lowered. Failing to fix the ACLs results in all traffic being dropped by the route-map rather than being forwarded to the correct ISP.Community Comment Notes
Users highlight that the ACLs are a major trap: "the ACLs were already created and matched in the route map... have a Deny for the networks... So you need to delete it". Others note the importance of AD adjustment: "we use distance command to make EIGRP distance higher..." to prevent R3 from choosing the suboptimal path through R4. One user confirmed the exact configuration needed: "route-map SP-1 permit 10 match ip address 10 set ip next-hop 209.165.201.2".Exam Strategy
Always inspect the running configuration for pre-existing objects like ACLs and Route-Maps before starting. If a task seems impossible with standard routing protocols, check for hidden 'deny' rules in ACLs or incorrect Administrative Distance settings that override your intended path selection.
Frequently Asked Questions
Why do I need to change the Administrative Distance on R3?
R4 mutually redistributes EIGRP and OSPF, creating multiple paths. Changing the AD ensures R3 prefers the direct EIGRP path over the OSPF external path via R4.
What is wrong with the pre-configured ACLs in this lab?
The pre-configured ACLs often contain 'deny' statements for the target networks (e.g., 10.0.0.0), blocking traffic. You must remove these denies or modify them to 'permit' the specific prefixes.
Related Analysis
Practice All 300-410 Questions
Access 159 questions with complete answers and detailed explanations.
View Full 300-410 Practice Test →