🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.dcom.sys.cisco
1 messages
1 total messages Started by David R. Stampf Wed, 15 Aug 1990 20:17
Dealing with remote routers
#556
Author: David R. Stampf
Date: Wed, 15 Aug 1990 20:17
28 lines
1875 bytes
We are experiencing a tough problem in x-country communications. A connection
is set up between two unix hosts which are quite remote from each other.
Between them are several networks, some of which are connected by cisco
routers. This connection is in operation for a long period of time, then
suddenly disappears, killing the session and annoying the users. This
occurs intermittantly, >1 <20 times a day.

Some detective work with ping and traceroute shows that an intermediate
cisco router is (for no discernable reason) sending a "Host unreachable"
icmp message at infrequent and unpredictable intervals. Querying the 
router does not indicate the loss of a route,nor the toggling of an 
interface.

I've discussed this on other mailing lists, and found someone who had a
similar problem and solved it by turning off the icmp unreachable messages
on that interface. He did not understand why the messages appeared, but
it did solve his problem. When I discussed this solution with the owners
of the router, they didn't seem too enthusiastic about making such a change
in that it may break traceroute (that being more important than telnet ;-)).

So my questions are, 1) Does anybody know any other reasons for a cisco
router to generate this message, and 2) (the hard question) how do you
deal with a router many levels removed from you whose operation is having
a major impact on your operation?

	Thanks for any help or enlightenment.

	< dave
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads