Hung after "has joined VMS cluster"

[Colin Butcher]

Hi,

Sounds as if you'd benefit from using AMDS to monitor the nodes and be able to make changes to Quorum and Votes when it's in the "hung" state. AMDS might just get you the information you need.

Any evidence from the network layers? What are the cluster interconnections - all single rail, or multi-rail? Common DSSI busses?

What's the quorum scheme to avoid a partitioned cluster? If there's a quorum disc around - is it availabile during the boot sequence?

Assuming that you can't change the machines just yet then for a speed-up I'd be tempted to use Nemonix fast ethernet / SCSI boards in the VAXes and bring it all up to 100Mbit/sec fast ethernet. You could also look at moving the storage away from DSSI to something a litle more modern, such as HSZ70/80 based arrays. It would also probably help to reduce complexity by reducing the number of nodes and disc servers.

However, it's really difficult to provide much other than general guesses without actually seeing it and understanding it.

Cheers, Colin (http://www.xdelta.co.uk).

[Russ Carraro]

The server was rebooted before I had a chance to try any of the recommendations. Apparently this time it booted normally. Thanks for all the replies.