<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Ahhhh IPv6 - that changes it:<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_10.html#wp2654545">http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_10.html#wp2654545</a><br>
<br>
'Table 42'<br>
<meta charset="utf-8">
<meta charset="utf-8">
!<br>
<br>
Each exclamation point indicates receipt of a reply.<br>
<br>
.<br>
<br>
Each period indicates that the network server timed out while
waiting for a reply.<br>
<br>
?<br>
<br>
Unknown error.<br>
<br>
@<br>
<br>
Unreachable for unknown reason.<br>
<br>
A<br>
<br>
Administratively unreachable. Usually, this output indicates that an
access list is blocking traffic.<br>
<br>
B<br>
<br>
Packet too big.<br>
<br>
H<br>
<br>
Host unreachable.<br>
<br>
N<br>
<br>
Network unreachable (beyond scope).<br>
<br>
P<br>
<br>
Port unreachable.<br>
<br>
R<br>
<br>
Parameter problem.<br>
<br>
S<br>
<br>
Source address failed ingress/egress policy.<br>
<br>
T<br>
<br>
Time exceeded.<br>
<br>
U<br>
<br>
No route to host.<br>
<br>
X<br>
<br>
Reject route to destination.<br>
<br>
<br>
On 10/06/12 4:43 PM, Karl Auer wrote:
<blockquote cite="mid:1339310593.15324.125.camel@karl" type="cite">
<pre wrap="">On Sun, 2012-06-10 at 16:17 +1000, Joseph Goldman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">What model router and IOS version?
</pre>
</blockquote>
<pre wrap="">
Small, old. Think Yoda without the Force:
xx-router-1# sho ver
Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version
12.4(24)T, RELEASE SOFTWARE (fc1)
[...]
</pre>
<blockquote type="cite">
<pre wrap="">Can you paste the exact output with sensitive information hidden?
</pre>
</blockquote>
<pre wrap="">
xx-router-1#ping aaaa:bbbb:cccc:dddd::2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to aaaa:bbbb:cccc:dddd::2, timeout is 2
seconds:
TTTTT
Success rate is 0 percent (0/5)
xx-router-1#
The problem went away when the correct ports got cabled together :-) An
example of the frustrations of remote troubleshooting: Labels on devices
did not match reality.
But I'd still like to know what "T" means. I'm wondering if it's IPv6
specific, like maybe an ND failure.
Regards, K.
</pre>
</blockquote>
<br>
</body>
</html>