2.3 Mixed-Version Support in OpenVMS Cluster Systems

HP provides two levels of support for mixed-version and mixed-architecture OpenVMS Cluster systems: warranted support and migration support.

Warranted support means that HP has fully qualified the two specified versions coexisting in an OpenVMS Cluster and will address all problems identified by customers using this configuration.

Migration support means that HP has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX, OpenVMS Alpha, or OpenVMS Integrity servers. Problem reports submitted against these configurations will be answered by HP. However, in exceptional cases, HP may request that you move to a warranted configuration as part of the solution. Migration support helps customers move to warranted OpenVMS Cluster pairs. For the minimum version supported for an upgrade to OpenVMS Version 8.4, see Section 4.3.1.

Warranted support combinations with OpenVMS Integrity servers Version 8.4 and OpenVMS Alpha Version 8.4 are shown in Table 2-2.

Table 2-2 Warranted Cluster Support with OpenVMS Version 8.4

Operating system

Warranted in combination with

OpenVMS Alpha Version 8.4

OpenVMS Integrity servers Version 8.4

OpenVMS Alpha Version 8.4

Additional warranted combinations are included in the following list. This list does not show same platform and version combinations. OpenVMS systems of the same platform and version are always warranted.

OpenVMS Alpha V8.3 and OpenVMS Integrity servers V8.3 or V8.3-1H1
OpenVMS Alpha V8.2 and OpenVMS Integrity servers V8.2-1
OpenVMS Alpha V7.3-2 and OpenVMS Integrity servers V8.2-1
OpenVMS Alpha V8.2 and OpenVMS Alpha V7.3-2
OpenVMS VAX V7.3 and any version of OpenVMS Alpha, V7.3-2 and later
OpenVMS VAX systems are not supported with OpenVMS Integrity server systems in the same cluster.




	NOTE: Only two architectures are supported in the same OpenVMS Cluster. System disks are architecture specific and can be shared only by systems of the same architecture. An Alpha and Integrity servers system, or an Alpha and VAX system, cannot boot from the same system disk. However, cross-architecture satellite booting is supported between an Alpha and VAX system. When you configure an OpenVMS Cluster to take advantage of cross-architecture booting, make sure that at least one system from each architecture is configured with a disk that can be used for installations and upgrades. For more information, see the Guidelines for OpenVMS Cluster Configurations and HP OpenVMS Cluster Systems.

Table 2-3 shows the supported migration pairs.

Table 2-3 Supported Migration Pairing with Version 8.4 OpenVMS Alpha or Integrity servers

Supported with either of these migrating to OpenVMS Integrity servers Version 8.4

Supported with either of these migrating to OpenVMS Alpha Version 8.4

OpenVMS Integrity servers Version 8.3-1H1

OpenVMS Integrity servers Version 8.3

OpenVMS Integrity servers Version 8.2-1

OpenVMS Alpha Version 8.3

OpenVMS Alpha Version 8.2

OpenVMS Alpha Version 7.3-2

For more information, see the OpenVMS Technical Software Support Service website at:

http://www.hp.com/go/openvms/support

In addition, see the OpenVMS Operating System Support Chart at:

http://www.hp.com/go/openvms/supportchart

Before introducing an OpenVMS Version 8.4 system into an existing OpenVMS Cluster, you might need to install certain patch kits (also known as remedial kits) on cluster members running earlier versions of OpenVMS. For a complete list of required patch kits, see the HP OpenVMS Version 8.4 Release Notes.

For information about supporting the TDC_RT software in OpenVMS Clusters, see Section 7.9.9.5.