Refer to the exhibit. R5 should not receive any routes originated in the EIGRP domain. Which set of configuration changes removes the EIGRP routes from the R5 routing table to fix the issue?
Refer to the exhibit. R5 should not receive any routes originated in the EIGRP domain. Which set of configuration changes removes the EIGRP routes from the R5 routing table to fix the issue?
To prevent R5 from receiving routes originated in the EIGRP domain, you need to filter these routes when redistributing from OSPF to RIP on R4. The correct configuration involves denying the routes with the specific tag (111) and explicitly permitting other routes. The configuration in option A does this correctly by using a route-map that denies routes with tag 111 and then permits all other routes with the 'permit 20' statement. This ensures that the EIGRP routes are not passed to R5 while still allowing other necessary routes to be redistributed.
Permit always important at the end of a route map to allow other routes to flow
Chosen answer is correct R4 route-map O2R deny 10 match tag 111 route-map O2R permit 20 ! router rip redistribute ospf 1 route-map O2R metric 1
A is correct
A is the answer Explanation In this question, routes from EIGRP domain are redistributed into OSPF (with tag 111) then RIPv2 but without any filtering so R5 learns all routes from both EIGRP and OSPF domain. If we only want R5 to learn routes from OSPF domain then we must filter out routes with tag 111 and permit other routes. The line “route-map O2R permit 20” is important to allow other routes because of the implicit deny all at the end of each route-map