[Info-vax] Alpha doesn't want to work in a cluster

[Stephen Hoffman]

On 2012-10-26 13:55:16 +0000, victor.esin at gmail.com said:

>   I removed DISK_QUORUM and QDSKVOTES from Alpha and it booted 
> successfully. Integrity entered later with quorum disk. So now two 
> nodes and quorum disk are in the cluster, but Alpha doesn't know about 
> quorum disk.  So network was proven to work normally. The configuration 
> is working but looks somewhat ..inaccurate. Yes, I can live with it and 
> can connect Alpha and Interity directly with crossover ethernet cable 
> to leave network folks out of game. But I still have no idea why Alpha 
> doesn't want to work with fibre quorum disk.

The cluster must have quorum before the quorum disk file on the quorum 
disk can be created, and before its votes counted.  (Part of the 
"simplify" mantra.)

Assuming the system parameter settings are now correct, this 
misbehavior implies an allocation class collision or a device name 
collision might exist.  Is the Alpha host itself also configured in 
ALLOCLASS allocation class 1?   (Check both boxes.)

And FWIW and for testing purposes, I usually use a decent-quality 
unmanaged GbE switch as a way to bypass a managed network.   And FWIW, 
a decent GbE NIC or a decent GbE switch has automatic cross-over 
(auto-MDIX) detection, too.  A back-to-back host-to-host connection 
does work, it's cable-dependent when you don't have auto-MDIX, and you 
don't get the switch lights as a diagnostic.  Spotting a dead NIC or a 
"wrong port" NIC connection is much easier with even a cheap switch.

-- 
Pure Personal Opinion | HoffmanLabs LLC