
Troubleshooting
302272-A Rev. 00 C-23
Figure C-4. Network Topology for ping -t Examples
Given the topology in Figure 4, the command:
annex#
ping –t 132.254.33.4
displays output such as the following when a traceroute packet passes successfully
to the
ping –t destination and back:
PING hobbes: 56 data bytes
Dir Router Hops Speed (b/s)MTU
>>> 132.254.99.21 19200 1024
>>> 132.254.33.32 10000000 1500
<<< 132.254.99.31 19200 1024
<<< 132.254.66.22 10000000 1500
64 bytes from 132.254.33.4: time=10. ms line 7
In the next example, Router 2 is unable to forward the outbound packet, as
indicated by the asterisks (***) under the Dir heading. Note that the hop count
remains at 1, since the packet crossed only one router.
annex#
ping –t 132.254.33.4
PING hobbes: 56 data bytes
Dir Router Hops Speed (b/s) MTU
>>> 132.254.99.2 1 19200 1024
*** 132.254.33.3 1 0 0
Troubleshooting Tunnel Problems
Since the TMS is an extension of the proprietary erpcd, you can use essentially
the same troubleshooting procedures that you would use for other erpcd problems.
In general, tunnel problems fall into the following categories:
• User errors
DVS0005A
Router 1 Router 2
132.254.66.1
132.254.66.2 132.254.99.3
135.254.99.2 135.254.3.3.3 135.254.3.3.4
ping-t
source
ping-t
destination
Kommentare zu diesen Handbüchern