[Info-vax] Weird problem with non-booting AlphaServer 800.

[Stephen Hoffman]

On 2013-01-15 23:02:01 +0000, Jan-Erik Soderholm said:

> Does this say that, on a system with FC connected storage, I should not 
> set ALLOCLASS to 1 (or 2) at all ?

FC devices are always using 1 for disk and always in 2 for tape, and 
the host and port allocation classes don't really matter — unless 
you're serving the disks through to non-FC-connected nodes, and then 
you have to play by those rules.

> I've seen that FC devices get a $1$ prefix already at the consol level.

FC disks always get allocation class 1, yes.

> And, if the system uses only FC storage and no local VOLSHAD, can I 
> leave ALLOCLASS at the dafault "0"?

Yes.

> And the disks seen from VMS will get a $1$ prefix anyway?

Yes.  None of which is what was being referenced earlier, which is 
whether allocation classes 1 and 2 are specifically reserved for FC 
SAN, which AFAIK they're not.  (But that's still not something I'd 
recommend doing on a "new" cluster configuration.)  You're quite free 
to stick other stuff into those two classes, though you do have to 
ensure the resulting device names are unique, and a large number of 
existing non-FC clusters have had disks or tapes in allocation class 1, 
either via ALLOCLASS and TAPE_ALLOCLASS, or via the port allocation 
classes.  And if you don't have FC around, it's a complete free-for-all.


-- 
Pure Personal Opinion | HoffmanLabs LLC