Network labs Docs Open simulator →

Ping, traceroute, and netverdict's diagnose ping

Two routers, one cable, both addressed. Send packets across the link three ways: classic ping, classic traceroute, and the netverdict-only diagnose ping cause-analysis walker.

Open this lab in your browser →

Free · no install · no account

Scenario

Two routers R1 and R2 are pre-configured on a /30 link: - R1 Gi0/0 = 10.0.0.1/30 - R2 Gi0/0 = 10.0.0.2/30 No routing protocol — they're directly connected, so connected routes give them each other for free. This lab introduces three diagnostic commands. The first two are standard Cisco. The third — diagnose ping — is netverdict's own: instead of sending a packet and reporting whether it came back, it walks the FIB / ARP / ACL / reverse-path chain *before* the packet is sent and tells you exactly which step would fail.

Topology

2 × router · Cisco IOS-style

What you will do

  1. From R1, ping R2 at 10.0.0.2.

  2. Traceroute to R2 from R1. With one hop, the output is short — but the mechanism is the same as a 30-hop trace.

  3. Run diagnose ping 10.0.0.2 from R1. Read the numbered, traffic-light walkthrough.

Open this lab in your browser →

More labs on this topic

This lab in other languages

Ping, traceroute und netverdicts diagnose pingPing, traceroute y el diagnose ping de netverdictPing, traceroute e o diagnose ping do netverdictPing, traceroute, et le diagnose ping de netverdictPing, traceroute, और netverdict का diagnose pingPing、traceroute 与 netverdict 的 diagnose pingPing, traceroute e il diagnose ping di netverdictPing、traceroute、そして netverdict の diagnose pingPing, traceroute, 그리고 netverdict의 diagnose pingPing, traceroute и diagnose ping от netverdictPing, traceroute ve netverdict'in diagnose ping'iPing, traceroute và diagnose ping của netverdict