From:	SMTP%"Leonard@Arizona.EDU" 13-JUL-1994 08:46:14.25
To:	EVERHART
CC:	
Subj:	Re: ? LAT Timing Parameters

From: leonard@telcom.arizona.edu (Aaron Leonard)
X-Newsgroups: comp.os.vms,comp.sys.dec
Subject: Re: ? LAT Timing Parameters
Date: 11 Jul 1994 23:27:48 GMT
Organization: University of Arizona Telecommunications
Lines: 41
Sender: leonard@Rena.Telcom.Arizona.EDU (Aaron Leonard)
Distribution: world
Message-Id: <2vskhk$dd2@news.CCIT.Arizona.EDU>
Reply-To: Leonard@Arizona.EDU
Nntp-Posting-Host: rena.telcom.arizona.edu
X-Newsreader: mxrn 6.18-6
To: Info-VAX@CRVAX.SRI.COM
X-Gateway-Source-Info: USENET


In article <1994Jun30.142251.22300@cc.usu.edu>, hodges@npt.nuwc.navy.mil 
(Benjamin F Hodges) writes:
|We are trying to find out what the LAT timing parameters are. This is
|in an attempt to avoid potential problems as our "LAT" network grows in
|size.

IMO, the default LAT parameter settings are pretty bad.  They were
designed to support three DECserver 100s and two VAX 785s on a 
single coax segment.  We run LAT over about a square mile region 
with frames typically going thru 5 or 8 bridges, so need more robustness 
than the default settings offer.

|  Also, does anyone know where more detailed protocol info can be found?

I dunno how to get "the specs"; they're proprietary, so you'd need
to pay DEC big bucks to get them (provided you could find anyone at
DEC to take your money.)  You can read a writeup I did a few months
ago with suggested settings for LAT parameters: it can be found
on Arizona.EDU in [arizonet.lat]lat-params.standard.  Here are some
of the most crucial setting differences:

KEEPALIVE TIMER
   Default: 20 seconds
   Should be: 255 (the max)

RETRANSMIT LIMIT
   Default: 8 retransmits (seconds)
   Should be: 120 retransmits (the max)

NODE LIMIT
   Default: 100
   Should be: 0 (or NONE)

Good luck,

Aaron

Aaron Leonard (AL104), <Leonard@Arizona.EDU>
University of Arizona Network Operations, Tucson AZ 85721
  \ Don't lock yourself into open systems. /