From: CSBVAX::MRGATE!INFO-VAX-RELAY@KL.SRI.COM@SMTP 18-JUN-1988 07:59 To: ARISIA::EVERHART Subj: BITNET Mail follows Received: from CUNYVM.CUNY.EDU by KL.SRI.COM with TCP; Tue, 14 Jun 88 06:19:20 PDT Received: from NIHKLMB.BITNET by CUNYVM.CUNY.EDU (IBM VM SMTP R1.1) with BSMTP id 6373; Tue, 14 Jun 88 09:19:20 EDT Date: 14 JUN 88 09:17 From: GHC%NIHKLMB.BITNET@CUNYVM.CUNY.EDU To: INFO-VAX @ KL.SRI.COM Subject: BITNET Mail follows Date: 14-JUN-1988 09:07:47.72 From: Gerson H Cohen To : Original To: GATEWAY::"zwarts@hgrrug51",GATEWAY::"info-vax@kl.sri.com",GHC Subj: RE: Disk visibility in LAVC. >Date sent: Wed, 8 Jun 88 11:40:00 N >Received: by PSUVM (Mailer X1.25) id 0060; Tue, 14 Jun 88 01:52:45 EDT >Date: Wed, 8 Jun 88 11:40:00 N >Reply-To: INFO-VAX@KL.SRI.COM >Sender: INFO-VAX Discussion >From: ZWARTS%HGRRUG51.BITNET@CUNYVM.CUNY.EDU >Subject: Disk visibility in LAVC. >Comments: To: info-vax@kl.sri.com >To: GERSON H COHEN > >About half a year ago we started with a LAV cluster. A Vax 8300 is the boot >node. Up to last week we have had only diskless VAXstations 2000 as satellite >nodes. So, the only disks in the cluster were the disks of the Vax 8300. Those >disks were visible and accessible from all satellites. Last week we added a >VAXstation 2000 with its own disk. I modified MODPARAMS.DAT for this node to >include MSCP_LOAD=1, so that it would serve its disk for the cluster. Indeed, >all other satelite nodes see this disk and have access to this disk. However, >the Vax 8300 still only sees its own local disks. SHOW DEVICE on the boot >member does not show the disk of the satelite. Any attempt to access the disk >from the boot member fails with an error stating that there is no such device. >Is there a SYSGEN parameter to be set on the boot member to make it accept >disks served by satelites? > ------------------------------------------------------ When I first brought up my LAVC some 6 months ago I had a similar problem. Check to see if you have a process by the name CONFIGURE running on your 8300. We have an 8530 and the process was absent. It is the responsibility of this process to find new served disks when they come on line and the problem was that I had a "rich" SYCONFIG.COM that installed several drivers and then had the line "$ STARTUP$AUTOCONFIGURE_ALL == 0". This is OK with a non-cluster system, but as one of the system management manuals points out, if such language is used in a cluster environment, CONFIGURE does not start up and your satellite disks cannot be seen. BTW - if you reboot your 8300 without shutting down the VAXstation you should then see the missing disk(s). Below is part of my SYCONFIG.COM file: ---------------------------------------------------------------- $! $! Site-specific device configuration procedure. $! [---] $ STARTUP$AUTOCONFIGURE_ALL == 0 <- the culprit $ @SYS$SYSTEM:STARTUP CONFIGURE <- the fix