Troubleshooting
Diagnostic Tools
If A Network Condition Prevents Traceroute from Reaching the
Destination.
Common reasons for Traceroute failing to reach a destination
include:
■
Timeouts (indicated by one asterisk per probe, per hop; refer to Figure
C-17, above.)
■
Unreachable hosts
■
Unreachable networks
■
Interference from firewalls
■
Hosts configured to avoid responding
Executing traceroute where the route becomes blocked or otherwise fails
results in an output marked by timeouts for all probes beyond the last detected
hop. For example with a maximum hop count of 7 (
maxttl
= 7), where the route
becomes blocked or otherwise fails, the output appears similar to this:
At hop 3, the first and
third probes timed out
but the second probe
reached the router.
All further probes
within the
maxttl
timed-out without
finding a router or the
destination IP
address.
An asterisk indicates a timeout
without finding the next hop.
Figure C-18. Example of Traceroute Failing to Reach the Destination Address
C-57
Summary of Contents for PROCURVE 2520
Page 2: ......
Page 3: ...HP ProCurve 2520 Switches November 2009 S 14 03 Management and Configuration Guide ...
Page 60: ...Using the Menu Interface Where To Go From Here 3 16 ...
Page 82: ...Using the Command Line Interface CLI CLI Editing Shortcuts 4 22 ...
Page 146: ...Switch Memory and Configuration Automatic Configuration Update with DHCP Option 66 6 40 ...
Page 164: ...Interface Access and System Information System Information 7 18 ...
Page 292: ...Port Trunking Outbound Traffic Distribution Across Trunked Links 12 30 ...
Page 374: ...Configuring for Network Management Applications LLDP Link Layer Discovery Protocol 13 82 ...
Page 434: ...Monitoring and Analyzing Switch Operation Locating a Device B 30 ...
Page 514: ...Troubleshooting DNS Resolver C 80 ...
Page 524: ...Daylight Savings Time on ProCurve Switches E 4 ...
Page 542: ...16 Index ...
Page 543: ......