Re: Cluster mystery: one-way MSCP disk serving?

sms_at_antinode.org
Date: 01/30/04 

Date: Fri, 30 Jan 2004 15:54:14 -0600 (CST)

From: lewis@mazda.mitre.org (Keith A. Lewis)

> I'm on the CONFIGURE bandwagon now. Why isn't that process running on your
> systems? It's running on all of my cluster systems but not my standalone
> ones.

   It's a consensus, and I believe that I've found the reason.

   Once upon a time, I got tired of the spurious SCSI every-LUN devices
associated with my (apparently lame) Yamaha CRW4416S CD-R/RW drive, so I
followed the hints and created a SYS$MANAGER:SYCONFIG.COM which said:

$ STARTUP$AUTOCONFIGURE_ALL == 0
$!
$ mcr sysman
   io connect fta0 /noadapter /driver = sys$ftdriver
   io connect mpa0 /noadapter /driver = sys$pipedriver
   io autoconfigure /exclude = (dka5*)
   io autoconfigure /select = (dka500)
   exit

(I suspect that I did the corresponding thing on the VAXstation, too.)

   This gave me a nice DKA500: without the usual DKA501: - DKA507: which
appear if a plain "sysman io autoconfigure" (or "sysgen autoconfigure
all") is used.

   The comments in the template file say:

$! Remove the comment from the line below if you wish to prevent
$! VMS from configuring devices with a SYSMAN IO AUTOCONFIGURE
$! command. This is typically only required if you are debugging
$! new device drivers.
$!
$! STARTUP$AUTOCONFIGURE_ALL == 0

What the comments in the template file do _not_ say is that that's not
_all_ it does, and that the other thing is to cause
SYS$STARTUP:VMS$DEVICE_STARTUP.COM to skip over the critical line:

$if .not. startup$autoconfigure_all .or. f$getsyi("NOAUTOCONFIG") -
then goto configure_started
$@sys$startup:vms$initial-050_configure
$configure_started:

   So, it appears that I just need to drag that bit of code up to
SYS$MANAGER:SYCONFIG.COM, and all should be well again, at long last.
When I made my original SYS$MANAGER:SYCONFIG.COM, I did manage to steal
the "fta0" and "mpa0" stuff, but I failed to steal the
"@sys$startup:vms$initial-050_configure" thing, too. Sigh.

--------

> Reasons to use a non-zero ALLOCLASS or PORT ALLOCLASS:
>
> * Required for volume shadowing.

   No plans.

> * Required for SCSI cluster.

   No plans. (I sold off my one KZPBA-CY, and there are not enough PCI
slots in the AlpSta 200 4/233 for graphics, fast Ethernet, and a SCSI
card.)

> * If you leave it 0 for now and change it later, and forget to dismount one
> or more affected disks when you make the change, your entire cluster will
> crash when the changed node re-joins.

   If I ever have a reason to change it, I'll probably crash the cluster
repeatedly for a variety of reasons.

> * Saves typing (assuming you use single-digit values)

   This _is_ a powerful argument, and it's why all my node names are
three or four characters long, but with non-shared disks, I'd have to
remember which box "$1" was in. I can puzzle out "ALP$" easily enough,
but with non-zero allocation classes, I'd need many more Post-it (tm)
notes than I do now. (And now I save one use of the Shift key.)

   Thanks again to the helpers for the useful help on this particular
bafflement.

------------------------------------------------------------------------

   Steven M. Schweda (+1) 651-699-9818
   382 South Warwick Street sms@antinode-org
   Saint Paul MN 55105-2547

Relevant Pages

  • Re: cluster nodes as AD or not?
    ... and all the others reference articles, ... > The reason for my post is that I told my customer that this was nothing ... This goes back to the original thinking behind building a cluster. ... If a company deems it worth spending the extra money to build a cluster, ...
    (microsoft.public.windows.server.clustering)
  • Re: cluster nodes as AD or not?
    ... Clustering AD DCs is an unnecessary practice. ... MVP - Windows Server - Clustering ... >> The reason for my post is that I told my customer that this was nothing ... > This goes back to the original thinking behind building a cluster. ...
    (microsoft.public.windows.server.clustering)
  • RE: Printer Pruning
    ... appears the DC is looking for the cluster name in AD: ... I was just looking for a reason to why the ... >on Kerberos on my Cluster Name resource but for some ... If you don't need Printer Pruning ...
    (microsoft.public.win2000.printing)
  • Re: Unauthorized PF CARP server bring down network connection
    ... there is no reason to continue the communication. ... listeners to figure out which messages it should pay attention to. ... If a machine is part of a cluster #10, then there is no reason for it ... Perhaps I misunderstood original message: ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Unauthorized PF CARP server bring down network connection
    ... >>check for authentication the password only. ... there is no reason to continue the communication. ... > If a machine is part of a cluster #10, then there is no reason for it ... > Perhaps I misunderstood original message: ...
    (comp.unix.bsd.freebsd.misc)