Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!spool.mu.edu!mips!swrinde!elroy.jpl.nasa.gov!ncar!csn!boulder!daemon
From: dd@ariel.unm.edu (Don Doerner)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Terminal server hangs
Message-ID: <35120@boulder.Colorado.EDU>
Date: 16 May 91 08:53:05 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 38

Folks-

Several people in this mail alias are having problems with terminal
servers having degraded response, for example:

<bill chen> We've had and are still having
<bill chen> the problem. We run csc/2s with
<bill chen> 8.1 (14) software. I don't think
<bill chen> we've ever had it hang for up
<bill chen> to 2 minutes, but definitely 30 seconds.

<mike rackley> For months we have been chasing the
<mike rackley> following problem.  We had it with
<mike rackley> our original csc2 processor and are
<mike rackley> having it with our recent csc3
<mike rackley> upgrade.  We are running 8.2(2)
<mike rackley> software, but we saw the same problem
<mike rackley> with previous versions of the software.

<mike rackley> The problem is that output coming back
<mike rackley> to dial up terminals through the 
<mike rackley> terminal server will hang for anywhere
<mike rackley> from 30 seconds to 2 minutes at a 
<mike rackley> time.  Once output resumes, it will
<mike rackley> run fine for varying lengths of time
<mike rackley> and then hang again.  On bad days, a
<mike rackley> user might see such hangs every few ...

If none of your terminal servers are used extensively across wide area
networks, you might want to try the configuration command "no service
nagle".  The nagle algorithm is an algorithm for minimizing the
overhead, and improving general throughput on a TCP/IP network with
slow links - appropriate if you are using a wide area net, but not so
appropriate if you are using a local area net.  We had some problems
like this with our terminal servers, and this turned out to be the
source...

Hope this helps!