SYNFUL@DRYCAS.CLUB.CC.CMU.EDU (02/11/88)
I've just taken my dear uVAX-I (DRYCAS) and added to its plethora of useful
(-less?) software LAVC. I've managed to build up a small uVAX-I cluster
(DRYCAS and STREIX) and have them at least talking to each other.
[Note to those starting up uVAXen clusters using DEQNAs -- there is a very
nasty bug in the LAVC code which, if you are on a busy Ethernet, can cause
you to trash files and/or directories on your served disks. Information
about this bug (albeit brief) can be found in the VMS V4.7 release notes
under AUTOGEN.
Suffice it to say that you can enable software checksums on the LAVC packets
by setting the SYSGEN parameter PE5 to 2 (two). After trying to bring up
my boot node with a messed up TTDRIVER.EXE, I can assure you that this is
a worthwhile change if you might be afflicted with this problem.]
My first problem is that I cannot boot STREIX as a satellite node off of
DRYCAS using STREIX's XQA0 for booting. DRYCAS always times out (no matter
what I set the SERVICE TIMER to) trying to service STREIX. Has anyone seen
this problem and can offer a suggestion?
The other thing I wanted to ask was for suggestions on how to manage this
system. My current configuration includes DRYCAS and STREIX both being
boot nodes with:
DRYCAS STREIX
------ ------
3 Mb memory 3 Mb memory
Emulex QD21 RQDX1
140 Mb drive 30 Mb drive
2 RX50s
QVSS
STREIX is currently set up with a MINIMUM of VMS so that it can boot up
enough to get into the cluster, mount DRYCAS's system disk, and re-assign
its own SYS$COMMON to include the rest of VMS.
Any suggestions on how to run this type of a LAVC would be greatly
appreciated.
--Marc
crazy enough to try a LAVC
with uVAX-I's