When bootstrapping an OpenVMS system into a cluster, a cluster protocol check is performed; the value of the communications protocol must be within one to allow the node to join or form a cluster.
This protocol check is an absolute limit to the OpenVMS version span, the warranty and migration support matrix may be (will be?) more constrained in the permitted versions.
The following OpenVMS Alpha system BUGCHECK (system crash) shows an attempt to bootstrap a cluster with OpenVMS versions too far apart; too great a span of versions:CLUSWVER - Software version incompatible with existing VMScluster
(R0 = %SYSTEM-F-REJECT, R1=00008106 = CLMDRS$C_VERSION = version mismatch).
You can display the cluster SCS protocol version with the following command:$ ANALYZE/SYSTEM
SDA> READ/EXECUTIVE
…
SDA> EXAMINE CLU$GB_CLUVER
CLU$GB_CLUVER: 00000000.00000018 "........"
Or within the processing of the SHOW CLUSTER /CONTINUOUS display, ADD PROTOCOL to the display.
| OpenVMS Version | Cluster Protocol | Comments |
|---|---|---|
| OpenVMS VAX V5.5-2 | 23 | |
| OpenVMS Alpha V6.1 | 24 | |
| OpenVMS Alpha V7.1 | 26 |
This based on a posting to comp.os.vms. SHOW CLUSTER /CONTINUOUS and ANALYZE/SYSTEM can be used to retrieve this value; additional version submissions are welcome.
Adjacent protocol versions are permitted. A difference of two or more protocol versions is not.
Seeking to Build Out the Table of CLU$GB_CLUVER Versions
Submissions of additional cluster version numbers associated with OpenVMS versions are welcome, either as comments here or via an offline message.
扫一扫
1784
到【灌水乐园】发言
cluster version numbers
Alpha V8.3 30.0
VAX V7.3 27.1
I64 V8.3 30.0
Alpha V7.3-2 28.0
The results above are from one cluster. Does this not show a difference of more than 2?
Alpha V7.2-2 27.1
VAX V6.2 25.0
Alpha V6.2 25.0
VAX V7.2 27.1
The above is from another cluster
VAX V7.3 x 27.1
VAX VMS V7.2 x 27.1
Alpha V8.3 x 30.0
A third cluster
________
Ian Miller