Mixed Cluster and OS

[Mark Fogleman]

I have a mixed cluster IE VAX/ALPHA. I am trying to get to VMS 8.3 on the ALPHA's. Is it recommended/feesable to run two system disks in the same cluster, one with VMS 7.3 for the VAX and another with VMS 8.3 for the Alpha equipment. Or should the cluster be split into two seperate?

[Jur van der Burg]

Alpha V8.3 and Vax V7.3 will cluster fine.

Jur.

[Hoff]

Official:

http://docs.hp.com/en/12700/SPDClusters.pdf

That's the Cluster Software Product Description. (These are all stashed at http://docs.hp.com now.) Top of page 12.

"Warranted Support"

[Steven Schweda]

http://docs.hp.com/en/OpenVMS.html
http://docs.hp.com/en/12700/SPDClusters.pdf

[...]
Table 2: OpenVMS Alpha and VAX Cluster
Support Table
[...]


> Or should the cluster be split into two
> seperate?

If you'd be happy with separate systems, why
cluster them?

[Jan van den Ende]

Steven wrote:

>>>
If you'd be happy with separate systems, why
cluster them?
<<<

I would rather reverse that question: if you CAN profit of cluster functionality, ie, you already HAVE the licenses, or the cost is not a problem for you(r organisation) the WHY would you NOT do it!

I have come to really LOVE it, and feel a bit restrained when I have to do without.

fwiw.

Proost.

Have one on me.

jpe

[Mark Fogleman]

I want to keep the cluster... But I am not sure the benifits will out weigh the problems. This will not be a short term situation and if it is going to be a constant headache then it will be easier to make two clusters instead of keeping the one.

[Steven Schweda]

> [...] if it is going to be a constant
> headache [...]

I don't know why it should be. Wouldn't you
(even) have a supported configuration?

[Steven Schweda]

> I have come to really LOVE it, [...]

Same here. I've been working a little on
OpenSSL lately, and at the moment I have my
VAX 4000 model 200 (VMS V7.3), XP1000 Alpha
(VMS V7.3-2), and zx2000 (VMS V8.3-1H1)
sharing disks quite happily.

I can blow up MONITOR on the Alpha if I say
/NODE = , but I could be behind on my
patches.

alp $ mon proc /topcpu /node = it
%MONITOR-I-ESTABCON, establishing connection to remote node(s)...
OpenVMS Monitor Utility
TOP CPU TIME PROCESSES
on node IT

[...]

%MONITOR-E-UNEXPERR, unexpected error
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000004F
6001, PC=0000000000060720, PS=0000001B

But that's a minor headache, at most.

[Mark Fogleman]

Thank You for your input