Mixed Cluster Attempt

OpenVMS x86 Field Test questions, reports, and feedback.
Post Reply

Topic author
afassl
Active Contributor
Posts: 27
Joined: Fri Jun 14, 2019 3:15 am
Reputation: 0
Status: Offline

Mixed Cluster Attempt

Post by afassl » Fri May 05, 2023 2:19 pm

Hi,

according to the specs - mixed clusters aren't supported. But - being curios - if tried to cluster a SIMH emulated VAX-VMS system with the X86 92. version.
Running as always @sys$manager:cluster_config.
...
...

Interesting:

Code: Select all

View of Cluster from system ID 1026  node: VAX2                                                                 5-MAY-2023 2┌───────────────────┬─────────┐
│      SYSTEMS      │ MEMBERS │
├────────┬──────────┼─────────┤
│  NODE  │ SOFTWARE │  STATUS │
├────────┼──────────┼─────────┤
│ VAX2   │ VMS V7.3 │ MEMBER  │
│ X861   │ VMS E9.2 │ MEMBER  │
└────────┴──────────┴─────────┘

Devices are visible on both ends:

Code: Select all

$ sho dev d

Device                  Device           Error   Volume          Free  Trans Mnt
 Name                   Status           Count    Label         Blocks Count Cnt
DNFS0:                  Online               0
X861$DKA0:              Online wrtlck        0
X861$DKA100:            Mounted              0 VMS92          61194096   223   1
X861$DKA200:            Mounted              0 DATA           26229855     1   1
X861$DKA300:            Mounted              0 DATA2          56594992     1   1
X861$DKA400:            Mounted              0 DATA3         563088324     1   1
X861$DKA500:            Online               0
X861$DMM0:              Offline              0
$2$DUA0:        (VAX2)  Online               0
$2$DUA1:        (VAX2)  Online               0
$2$DUA2:        (VAX2)  Mounted              0 (remote mount)                  1
$2$DUA3:        (VAX2)  Online               0
$2$DUB0:        (VAX2)  Online               0
$2$DUB1:        (VAX2)  Online               0
$2$DUB2:        (VAX2)  Online               0
$2$DUB3:        (VAX2)  Online               0

$ mount/system/cluster dka300: data2
%MOUNT-I-MOUNTED, DATA2 mounted on _X861$DKA300:

On VAX

Code: Select all

$ sho dev d

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
X861$DKA0:              Online               0
X861$DKA100:            Mounted              0  (remote mount)                 1
X861$DKA200:            Mounted              0  (remote mount)                 1
X861$DKA300:            Mounted              0  DATA2         56594991     1   2
X861$DKA400:            Mounted              0  (remote mount)                 1
X861$DKA500:            Online               0
$2$DUA0:        (VAX2)  Online               0
$2$DUA1:        (VAX2)  Online               0
$2$DUA2:        (VAX2)  Mounted              0  VAX2_73_DISK   1876230   182   1
$2$DUA3:        (VAX2)  Online               0
$2$DUB0:        (VAX2)  Online               0
$2$DUB1:        (VAX2)  Online               0
$2$DUB2:        (VAX2)  Online               0
$2$DUB3:        (VAX2)  Online               0
Was able to create a text file, and to add on both sides.

Code: Select all

$ dir

Directory X861$DKA300:<000000>

000000.DIR;1        ALTEMAIL.BCK;1      APACHE.DIR;1        A_TEST.DIR;1       
BACKUP.DIR;1        BACKUP.SYS;1        BADBLK.SYS;1        BADLOG.SYS;1       
BITMAP.SYS;1        BUILD_KITS.DIR;1    CLUSTER.DIR;1       CONTIN.SYS;1       
CORIMG.SYS;1        DATA.DIR;1          DATABASE.DIR;1      DATENBANK.DIR;1    
DFG.COM;1           DOMAIN.DIR;1        DOWNLOADS.DIR;1     ENTWICKLUNG.DIR;1  
GPT.SYS;1           INDEXF.SYS;1        SECURITY.SYS;1      SWSVE.DAT;1        
SYSEXE.DIR;1        TEST.TXT;2          TEST.TXT;1          VOLSET.SYS;1       

Total of 28 files.
$ type test.txt
Test-Text created on X86
         

Added data on VAX
Assuming that this isn't supported at all, but interesting as a test case :-)

Added in 22 minutes 54 seconds:
and some more testing with cluster wide tables:

Code: Select all

$ create/name_table/parent=lnm$syscluster_table onvax
$ define/table=onvax Value1 Created_on_Vax
$ show log value1/cluster
%DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and placement
 \CLUSTER\
But on the X86 side:

Code: Select all

$ create/name_table/parent=lnm$syscluster_table cluster_wide_test
$ define/table=cluster_wide_test Value1 ABCDEFG
$ show log value1/cluster
   "VALUE1" = "ABCDEFG" (CLUSTER_WIDE_TEST)
   "VALUE1" = "CREATED_ON_VAX" (ONVAX)
    
Added in 23 minutes 29 seconds:
But it is obvious - not to work really stable
On Field Test
cluster1.png
The brave Vax is giving its best, but
cluster1.png
Added in 1 minute 23 seconds:

Code: Select all

MONITOR> mon clus
%MONITOR-I-ESTABCON, establishing connection to remote node(s)...
%MONITOR-E-SRVMISMATCH, MONITOR server on remote node is an incompatible version
%MONITOR-I-CONT, continuing....
Attachments
cluster2.png

User avatar

volkerhalle
Master
Posts: 196
Joined: Fri Aug 14, 2020 11:31 am
Reputation: 0
Status: Offline

Re: Mixed Cluster Attempt

Post by volkerhalle » Sat May 06, 2023 3:06 am

Andreas,

rest assured: none of the 'problems' you've seen has anything to do with VSI OpenVMS x86-64. You would have seen the same with a mixed version or mixed architecture cluster including V8.x nodes (VAX and Alpha and/or Itanium).

Now: OpenVMS is OpenVMS is OpenVMS is OpenVMS ;-)

It always was an OpenVMS design principle to not break any functionality during upgrades. There are only very few exceptions: e.g. don't try to bring an OpenVMS VAX V5.5-2 (or earlier) or OpenVMS Alpha V1.5 (or earlier) node into a cluster running V7.2 (or higher) nodes - or vice versa: the node trying to join the cluster will crash with 'CLUSWVER - Software version incompatible with existing VMScluster'

The MONITOR utility also had some incompatible protocol version change.

There just was no cluster-wide logical name support in OpenVMS VAX V7.3, so the SHOW LOG /CLUSTER command does not exist.

While running a mixed version/architecture including OpenVMS x86-64 and OpenVMS VAX cluster would - understandably - not supported, it may still work.

Volker.


sodjan
Active Contributor
Posts: 40
Joined: Mon Apr 24, 2023 3:51 am
Reputation: 0
Status: Offline

Re: Mixed Cluster Attempt

Post by sodjan » Sat May 06, 2023 6:29 am

What if you do this instead of using the /cluster switch (this are just examples from an 8.4-2L2 Alpha...):

Code: Select all

$ show log value1/table=*
   "VALUE1" = "CREATED_ON_VAX" (ONVAX)
$
Or:

Code: Select all

$ show log value1/tab=onvax
   "VALUE1" = "CREATED_ON_VAX" (ONVAX)
$
Or:

Code: Select all

$ write sys$output f$trnlnm("VALUE1", "ONVAX")
CREATED_ON_VAX
$
And what if you try this on the VAX with the logical name create from the "other side":

Code: Select all

$ write sys$output f$trnlnm("VALUE1", "CLUSTER_WIDE_TEST")
EDIT:
B.t.w., what is the "reverse" of "$ create /name_table ...." ?
It doesn't seam to be "$ delete /name_table ...."
Last edited by sodjan on Sat May 06, 2023 6:44 am, edited 1 time in total.

User avatar

volkerhalle
Master
Posts: 196
Joined: Fri Aug 14, 2020 11:31 am
Reputation: 0
Status: Offline

Re: Mixed Cluster Attempt

Post by volkerhalle » Sat May 06, 2023 7:22 am

sodjan wrote:
Sat May 06, 2023 6:29 am
B.t.w., what is the "reverse" of "$ create /name_table ...." ?
It doesn't seam to be "$ delete /name_table ...."
Jan-Erik,

from OpenVMS User's Manual:

To delete a logical name table, specify the table that contains it (the system or process directory logical name table) and the name of the table. All logical names in descendant tables (and the descendant tables themselves) are deleted when you delete a parent logical name table.

Volker.


sodjan
Active Contributor
Posts: 40
Joined: Mon Apr 24, 2023 3:51 am
Reputation: 0
Status: Offline

Re: Mixed Cluster Attempt

Post by sodjan » Sat May 06, 2023 7:52 am

Hi and thanks!
I do understand *that* part... :)
But is it using Delete?
What would the complete command be to revetse the "$ cre/name" command in original post?

User avatar

volkerhalle
Master
Posts: 196
Joined: Fri Aug 14, 2020 11:31 am
Reputation: 0
Status: Offline

Re: Mixed Cluster Attempt

Post by volkerhalle » Sat May 06, 2023 9:02 am

sodjan wrote:
Sat May 06, 2023 7:52 am
But is it using Delete?
What would the complete command be to reverse the "$ cre/name" command in original post?
VSIAXP $ create/name_table/parent=lnm$syscluster_table onvax
VSIAXP $ sho log/table=* onvax
"ONVAX" [table] = "" (LNM$SYSTEM_DIRECTORY)
VSIAXP $ deass/table=LNM$SYSTEM_DIRECTORY onvax
VSIAXP $ sho log/table=* onvax
%SHOW-S-NOTRAN, no translation for logical name ONVAX

Volker.


Topic author
afassl
Active Contributor
Posts: 27
Joined: Fri Jun 14, 2019 3:15 am
Reputation: 0
Status: Offline

Re: Mixed Cluster Attempt

Post by afassl » Tue May 09, 2023 2:29 am

Nice

Code: Select all

View of Cluster from system ID 1  node: VMAL01              9-MAY-2023 08:27:50
+-----------------------+---------+
|        SYSTEMS        | MEMBERS |
+--------+--------------+---------+
|  NODE  |   SOFTWARE   |  STATUS |
+--------+--------------+---------+
| VMAL01 | VMS V8.4     | MEMBER  |
| VAX2   | VMS V7.3     | MEMBER  |
| VAX3   | VMS V7.3     | MEMBER  |
| VAX1   | VMS V7.3     | MEMBER  |
| X861   | VMS E9.2-1   | MEMBER  |
+--------+--------------+---------+

Post Reply