Refer to the exhibit. An engineer troubleshoots a connectivity problem that is impacting the communication from the users at segment 172.16.3.16 /28 to the server farm at 192.168.5.16/
28. Which configuration resolves the issue on router R1?
Refer to the exhibit. An engineer troubleshoots a connectivity problem that is impacting the communication from the users at segment 172.16.3.16 /28 to the server farm at 192.168.5.16/
28. Which configuration resolves the issue on router R1?
RIP (Routing Information Protocol) uses the hop count as a routing metric, and the maximum number of hops allowed is 15. Any value greater than 15 is considered to be unreachable. Therefore, setting the metric for the redistributed OSPF routes to 16 would make them unreachable in RIP. To ensure proper communication and route advertisement, setting the metric to 14 is necessary. This configuration ensures that the hop count remains below the maximum limit of 15, thereby resolving the connectivity issue between the segments 172.16.3.16/28 and 192.168.5.16/28.
After investigating a little bit more Im going with C. I have found this article that actually agrees with Pietjeplukgeluk. Any value greater than 15 will be considered infinite. https://www.cisco.com/c/en/us/support/docs/ip/enhanced-interior-gateway-routing-protocol-eigrp/8606-redist.html
I would pick "A" because of poison reverse.
C seems correct as 16 will be "unreachable", we should reduce hop count to allow adjacent router to keep hop-count below 16==unreachable
A works for me in a lab
My choice is C: "RIP uses the hop count as a routing metric. RIP prevents routing loops by implementing a limit on the number of hops allowed in a path from the source to a destination. The maximum number of hops allowed for RIP is 15. This hop limit, however, also limits the size of networks that RIP can support." https://community.cisco.com/t5/networking-knowledge-base/ripv2-routing-information-protocol/ta-p/3117425
wrong: R2(config)#router rip R2(config-router)#redi R2(config-router)#redistribute os R2(config-router)#redistribute ospf 1 me R2(config-router)#redistribute ospf 1 metric ? <0-16> Default metric transparent Transparently redistribute metric R2(config-router)#redistribute ospf 1 metric
If you see the metric in R3 it is [110/15], in R4 you do not get the route, in my opinion, C is wrong because if the metric is configured in 15 reducing it to 14 will not help to deliver the route.