24-Feb-2015

Cluster completed
One big problem to create the cluster was the existence of the quorum disk, that both Itanium system cannot access directly. Plus, on one of these nodes, I set EXPERCTED_VOTES to 3. Even without specifying the quorum disk, that system waited, and waited… to join the cluster where the other one (with EXPECTED_VOTES set to 1) would happily join.

Probably not the right thing to do – but now all systems have NO quorum disk and expected_votes of 1 (each contributing one vote). Now I got my cleuster after rebooting all systems:

View of Cluster from system ID 21505  node: DIANA                                                              24-FEB-2018 20:28:18
┌───────────────────────┬─────────┐
│        SYSTEMS        │ MEMBERS │
├────────┬──────────────┼─────────┤
│  NODE  │   SOFTWARE   │  STATUS │
├────────┼──────────────┼─────────┤
│ DIANA  │ VMS V8.4     │ MEMBER  │
│ IRIS   │ VMS V8.4     │ MEMBER  │
│ INDRA  │ VMS V8.4     │ MEMBER  │
└────────┴──────────────┴─────────┘

Similar on the other nodes.
Now Daphne (the small Alpha system) and Inge (to be renamed to another (female) deity as all other systems are) need to be updates for the removed quorum disk. Plus I’ll set up a FreeAXP process on the consoie laptop to function as quorum node.

Startup procedures for IRIS are the same as on Diana – except (for now) that TCPIP is started in the main procedure, instead of the batch one. I will put that back where I defined it: The FTP-issue has also been solved: because SYLOGIN.COM was not accessible (owned by [SYSTEM] but protection states (W:) – so no access) login fails. Changed that to (W:RE) and it’s OK now…So it will probably as well when started in the batch-procedure – as well as SSH (which didn’t start either)
Should have thought about that; this is the one file that I changed in between….

Startup of INDRA will be copied from IRIS (and changed accordingly).

Fun part of reboot of Diana: it speeds up the blogs ….

Found out after publishing this post the first time: SHUTDOWN of both Itaniums caused loss of quorum on Diana, so I had to restart one of the Itaniums, invoke SHUTDOWN1 to add option “REMOVE_NODE”. It stops the server, but allows Diana to continue – since now quorum is adjusted. This should be added to the SHUTDOWN command on all systems – except Diana – to allow that system to continue, whatever happens to the other servers. Or adjust votes for the Itanium boxes to 0..
Or both.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.