Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!okstate!rjs
From: rjs@a.cs.okstate.edu (Roland Stolfa)
Newsgroups: comp.sys.intel,comp.unix.xenix
Subject: Intel 286/310's
Message-ID: <1910@a.cs.okstate.edu>
Date: Tue, 21-Apr-87 15:29:07 EST
Article-I.D.: a.1910
Posted: Tue Apr 21 15:29:07 1987
Date-Received: Wed, 22-Apr-87 04:53:50 EST
Organization: Oklahoma State Univ., Stillwater
Lines: 51
Xref: mnetor comp.sys.intel:173 comp.unix.xenix:263

Hello,

Several weeks ago, I submitted a letter about some Intel 286/310 boxes that
I was having problems with.  I wish to thank all those who answered my plea.
I am, however, still having problems.  Therefore, I would like restate the
problems that I am having, hoping that one of you in netland can help me out
some more...

Here at Oklahoma State University, we have 6 Intel 286/310's running
Xenix 3.0 (that's right 3.0) Update 1, with OpenNet 1.0 Update 1.
Each of the 310's has a 40M drive, 1M of memory (this is a correction),
and one iSBC 188/48 Version 1.1.

Currently this machine set is serving about 150 students (usually no
more than 25 at a time).  Each student has NO idea of which machine
they are logining onto.  When we originally set this system up, we
thought that the OpenNet product would handle the load of having any
student log onto any machine and have OpenNet route their session
to the correct home directory.  However, this seems to not be the case.

When the load reaches about 20 students (usually just before an assignment
is due :-) the system seems to handle everything just fine.  However,
after the system has sustained this for a "while", one machine in the
set will lock up.  By that, I mean that someone on machine A, trying
to access machine B (which is locked up), fails.  However, someone on
machine B trying to access ANY other machine succeeds.  Furthermore,
that student never even knows that machine B is unreachable by fellow
classmates who have home directories on machine B.

When I try to fix the situation, I plug a terminal into the console port
on machine B, and it just sits there.  No response to <CR>, <DEL>, etc.

My only apparent solution has been to shutdown machine B and reboot it.

However, this then usually causes the next machine in the "/net/data"
file to suffer the same problems that I was trying to fix on machine B.

Any and all assistance in this matter would be greatly appreciated.
Please mail any questions, comments, and/or help directly to me.


Roland J. Stolfa
Department of Computing and Information Sciences
Oklahoma State University

UUCP:  {cbosgd, ea, ihnp4, isucs1, mcvax, pesnta, uokvax}!okstate!rjs

Internet:       rjs@a.cs.okstate.edu

Disclaimer:	You have lost your MIND if you think ANYBODY speaks forin nein neiUND_