Here's an old one I saved in my archives but you could probably search
for it on nexial as well. The main situation it addresses is the use
of a router as a commserver, with a dumb terminal attached or dialed up.
Marty Adkins Email: [EMAIL PROTECTED]
Mentor Technologies Phone: 410-280-8840 x3006
275 West Street, Plaza 70 WWW: http://www.mentortech.com
Annapolis, MD 21401 Cisco CCIE #1289
> Received: from spot.Colorado.EDU ([EMAIL PROTECTED] [128.138.129.2]) by
>ccci.com (8.8.5/8.7.3) with ESMTP id TAA18611; Wed, 26 Feb 1997 19:27:06 -0500 (EST)
> Received: (from daemon@localhost)
> by spot.Colorado.EDU (8.8.5/8.8.4/CNS-4.1p)
> id QAA17553 for cisco-ml1; Wed, 26 Feb 1997 16:19:40 -0700 (MST)
> Received: from puli.cisco.com (puli.cisco.com [171.69.1.174])
> by spot.Colorado.EDU (8.8.5/8.8.4/CNS-4.1p) with SMTP
> id QAA17120 for <[EMAIL PROTECTED]>; Wed, 26 Feb 1997 16:19:19 -0700
>(MST)
> Received: (billw@localhost) by puli.cisco.com (8.6.12/8.6.5) id PAA13961; Wed, 26
>Feb 1997 15:16:43 -0800
> Date: Wed, 26 Feb 97 15:16:43 PST
> From: William "Chops" Westfield <[EMAIL PROTECTED]>
> To: Crocker Sean SSgt 786CS/SCBM <[EMAIL PROTECTED]>
> Cc: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
> "'KRATOCHVIL.KEITH'" <[EMAIL PROTECTED]>,
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> Subject: RE: Nagle question
> In-Reply-To: Your message of Wed, 26 Feb 1997 21:27:23 +0100
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text
>
> Actually Paul did, just in a truncated manner. What he is saying is
> that enabling the Nagle algorithm on the router will affect the traffic
> that is originated directly FROM the router or is addressed directly TO
> the router (hence "terminated").
>
> So your guess is correct, it's the characteristics for the router as a
> host or end-station. Service nagle is especially good to enable if you
> are, say, telnetting to the router via a 56 kbps link or slower.
>
> I asked the same question last year, answered by Paul. I had to reread
> the docs for a bit before the filament would start glowing :-).
>
> It's worth pointing out while we're talking about this, that as far as I can
> tell, the "slow start congestion avoidance" algorithms mandated by various
> sources pretty much devolve to the Nagle algorithm for connections with
> non-continuous traffic (ie always doing "slow start" == "Nagle algorithm")
>
> I thought that was pretty neat when I realized it, but it also means that
> a slow-start tcp might be subject to some of the weird interactions that
> cause the Nagle algorithm to be off by default in a cisco...
>
> BillW
> cisco
>
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]