🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.dec
Article #1808

Re: Decnet Drops Connect (?)

#1808
From: tundra
Date: Fri, 03 Aug 1990 17:10
49 lines
2817 bytes

In case they are of any interest,
here is a summary of the responses I received on the 
LOST CONNECTION problem so far.  Thanks to everyone for the         
suggestions.  You would have to read a lot of manuals
and have a very sharp eye to come up with such good
ideas.  

I have run sys$system:dtsend tests.  I am currently 
trying the RECNEXINTERVAL parameter increase and looking 
at various memory and io parameters.  Only time will tell 
if these changes are successful.

Thanks again,
--------  john kemp            (  (  )_  internet - kemp@uiatma.atmos.uiuc.edu
  -----                       (  (   __)   decnet - uiatmb::kemp
   ---    univ of illinois   (_ (   __)    bitnet - {uunet,convex}
   --     dept of atmos sci  .(____).               !uiucuxc!uiatma!kemp
   -      105 s gregory ave    ...          phone - (217) 333-6881
    -     urbana, il 61801    ...             fax - (217) 444-4393


From: "Carl Karcher, Room 535 WC, 3-5896" <KARCHER@don.waisman.wisc.edu>
Subject: Re: Decnet Drops Connect (?)

The network is flakey. What the messages mean is SCS communications (not decnet)
has been lost and then restored in less than 20 seconds (if sysgen parameter
recnexinterval is at the default). Cluster traffic (ala SCS) is far more
sensitive to network problems that decnet. If the network disturbance lasts
longer than 20 seconds things will crash. I would increase recnexinterval
(say to 1 minute) until your network problems are solved. This is a dynamic
parameter so it can be done online (.e.g using SYSMAN commands PAR SET then PAR
WRITE ACTIVE commands). In a large network its a good idea to increase
recnexinterval permanently. Otherwise one misconnected PC can crash your LAVC.

Carl Karcher                             Internet: KARCHER@WAISMAN.WISC.EDU
University of Wisconsin-Waisman Center   Bitnet:   KARCHER@WISCPSL Madison,
Wisconsin, USA                  	 PSTnet:   (608) 263-5896

Subject: Decnet Drops Connect (?)
Sender: Craig Paul <PAUL@kuhub.cc.ukans.edu>
Reply-To: paul@kuhub.cc.ukans.edu

What does dtsend tell you about line utilization? If you get less than
6% line utilization you've probably got physical line problems. Since
your explanation makes these two nodes sounds as though it is your
entire network I'd expect line utilizations in the 10s of percents, at
least!
Technical Details
Message-ID: <16500003@ux1.cso.uiuc.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!tundra
References: <184519@<1990Aug2>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!tundra
From: tundra@ux1.cso.uiuc.edu
Newsgroups: comp.sys.dec
Subject: Re: Decnet Drops Connect (?)
Message-ID: <16500003@ux1.cso.uiuc.edu>
Date: 3 Aug 90 17:10:00 GMT
References: <184519@<1990Aug2>
Lines: 49
Nf-ID: #R:<1990Aug2:184519:ux1.cso.uiuc.edu:16500003:000:2325
Nf-From: ux1.cso.uiuc.edu!tundra    Aug  3 12:10:00 1990