Mixed-Version OpenVMS Cluster and the Cluster Protocol Version
2007-08-18 17:13
405 查看
Mixed-Version OpenVMS Cluster and the Cluster Protocol Version
http://64.223.189.234/node/412
Submitted by Hoff on July 9, 2007 - 19:50.
Tagged: Bootstrap • Cluster • OpenVMS • Servers
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:
You can display the cluster SCS protocol version with the following command:
Or within the processing of the SHOW CLUSTER /CONTINUOUS display, ADD PROTOCOL to the display.
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.
Login or register to post comments • Printer friendly version
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
http://64.223.189.234/node/412
Submitted by Hoff on July 9, 2007 - 19:50.
Tagged: Bootstrap • Cluster • OpenVMS • Servers
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.
Login or register to post comments • Printer friendly version
cluster version numbers
Submitted by imiller on July 10, 2007 - 08:28.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
相关文章推荐
- Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration info
- Mixed mode assembly is built against version 'v1.1.4322' of the runtime and...问题——C# DirectXSound
- Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additio
- Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additio
- “System.IO.FileLoadException: Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 错误
- Mixed mode assembly is built against version 'v1.1.4322' of the runtime and...问题——C# DirectXSound
- The mixed programming in terms of matlab and C++
- Less copies in Python with the buffer protocol and memoryviews
- There is a version mismatch between the spring client and the server
- svn:is not under version control and is not part of the commit, yet its child解决办法
- How to Determine the Version of Oracle XML Publisher for Oracle E-Business Suite 11i and Release 12 (Doc ID 362496.1)
- What is the different between a Cluster and MPP supercomputer architecture?
- Finding a service name, given the port and protocol
- nodejs采坑记录之-“Make sure you have the latest version of node.js and npm installed”
- It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-installing ___Error Installing APK
- how to change the ruby and rails version
- 更新android sdk后提示This Android SDK requires And...e ADT to the latest version.
- This Android SDK requires And...e ADT to the latest version.
- Could not load extension from . The 'manifest_version' key must be present and set to 2 (without quo
- SVN:is not under version control and is not part of the commit,yet its child