Higgins [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 1:24 AM
To: [EMAIL PROTECTED]
Subject: RE: Trace failure indication [7:12191]
This problem shows up on any cisco router that I have tried, about 20
routers. It appears from a debug packet and debug icmp on the final
des
[EMAIL PROTECTED]
Subject: RE: Trace failure indication [7:12191]
This problem shows up on any cisco router that I have tried, about 20
routers. It appears from a debug packet and debug icmp on the final
destination router that the final destination router still has the
port
[mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 1:24 AM
To: [EMAIL PROTECTED]
Subject: RE: Trace failure indication [7:12191]
This problem shows up on any cisco router that I have tried, about 20
routers. It appears from a debug packet and debug icmp on the final
destination router
Pardon my ignorance, but would you happen to be using unnumbered interfaces
to connect theses routers?
-E
-Original Message-
From: Joseph Higgins [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 1:24 AM
To: [EMAIL PROTECTED]
Subject: RE: Trace failure indication [7:12191
When I trace from a cisco router to another Cisco router I get a timeout
failure every other probe on the last hop It fails on every type of
cisco router I have tried, 7513,25xx abd 36xx. I think that it must be
normal but I cannot find anything in the archives here or at the Cisco
site that
Have you checked duplex? Sometimes speed and duplex settings have a similar
effect. Things seem to work properly, but you are dropping packets which
slows the application down. Obviously if you have one end at 10 and the
other is at 100, you will run into major issues, but sometimes
Hi,
I think you'll find this is quite normal.
The device exist #msecs , port non-existent *, device exists #msecs
and so on.
Basically the device exists but the socket you are attempting is not open.
Spot on trace I'd say
Just a thoought
Teunis,
Hobart, Tasmania
Australia
On Thursday,
This problem shows up on any cisco router that I have tried, about 20
routers. It appears from a debug packet and debug icmp on the final
destination router that the final destination router still has the port open
while it is handling the previous trace probe. I want to know if anyone can
get
Even the example at http://www.cisco.com/warp/public/105/ext_ping_trace.html
shows this failure but provides no explanation.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=12246t=12191
--
FAQ, list archives, and subscription info:
9 matches
Mail list logo
