Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!ncar!boulder!daemon
From: SHERWOOD@AC.DAL.CA (John Sherwood)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Bug in cisco bridging?
Message-ID: <24936@boulder.Colorado.EDU>
Date: 20 Aug 90 19:05:20 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 33

Hank:
 
>I have defined two ciscos (8.1(14)) each with bridging between the
>the two of them as well as routing.  I have two parallel 19.2kb lines
>between the two of them defined in a circuit group so as to perform
>load balancing.  I open a LAT connection from a Decserver 200 over to
>a Vaxstation 3100 and start typing a file.  The output is all being bridged.
>When I remove one of the lines physically from the router, the connection
>dies between the Decserver and the Vaxstation.
 
LAT is a very time-sensitive protocol. I would not be surprised to find
it will not work on a single 19.2k link. I am surprised that you can get it
to work at all even with 2 links sharing the load. Even minor delays
in packet delivery can give LAT heartburn.
 
>  This does not happen
>when I do a connect from one Vax station to another (using routing rather
>than bridging) and removing one of the cables (physically).
 
I am guessing that you are using DECnet CTERM rather than LAT. CTERM
(ie. $SET HOST xxxx) should work with no problems over slow links; we run
it at 4800 regularly.
 
I would try switching to CTERM as the terminal protocol and see if your
problems go away.
 
Cheers
 
John Sherwood
Dalhousie University
Halifax, Nova Scotia
 
sherwood@ac.dal.ca.