101 · Question #566
Ping and Traceroute outputs are provided for a connectivity issue. What is the cause of these results?
The correct answer is A. routing loop. A routing loop causes packets to bounce between routers with no path to the destination, producing repeating hops in traceroute output and request timeouts or TTL-exceeded messages in ping.
Question
Ping and Traceroute outputs are provided for a connectivity issue. What is the cause of these results?
Options
- Arouting loop
- Bpackets that are routed with a high metric
- Cmultiple paths toward the destination
How the community answered
(36 responses)- A83% (30)
- B6% (2)
- C11% (4)
Why each option
A routing loop causes packets to bounce between routers with no path to the destination, producing repeating hops in traceroute output and request timeouts or TTL-exceeded messages in ping.
A routing loop occurs when two or more routers forward packets toward each other in a cycle due to inconsistent or missing routing information. Traceroute reveals this as the same set of router addresses repeating across multiple TTL increments, while ping shows persistent timeouts or TTL-exceeded ICMP replies because packets never reach the destination and are eventually discarded.
A high-metric route would still deliver packets to the destination along a less-preferred path - it would not produce non-terminating cyclic hop output in traceroute.
Multiple equal-cost paths result in different next-hop addresses per probe in traceroute, not the same repeating sequence of routers that characterizes a routing loop.
Concept tested: Routing loop identification via traceroute output
Source: https://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/13769-5.html
Topics
Community Discussion
No community discussion yet for this question.