Filter
Top Products
earlier versions of OpenVMS. In a mixed-architecture cluster, you need to install an LMF patch
on any OpenVMS Version 7.3-2 Alpha members. For a complete list of required patch kits, see
the HP OpenVMS Version 8.4 Release Notes.
For information about supporting the Performance Data Collector base software (TDC_RT) in
OpenVMS Clusters, see Section 7.9.9.5 (page 149).
5.4 Adding a New System to an OpenVMS Cluster
To add a new OpenVMS Version 8.4 Alpha or Integrity servers system to an existing OpenVMS
Cluster configuration, all existing Alpha nodes in the cluster must be running OpenVMS Alpha
Version 7.3-2 or later, and all existing OpenVMS Integrity server nodes must be running OpenVMS
Integrity servers Version 8.2-1 or later. Any node in the cluster that is running an older version
of OpenVMS must be upgraded appropriately before you can add a Version 8.4 node. If you
have a VAXcluster, any node running an older version of OpenVMS VAX must be upgraded to
Version 7.3 of OpenVMS VAX before you can add an Alpha Version 8.4 node.
Alternatively, any OpenVMS Alpha or Integrity servers node that needs to be upgraded can be
removed temporarily from the cluster and added back after it has been upgraded. This allows
you to form a supported cluster immediately, adding nodes back into the cluster as they are
upgraded. Note that, depending on the number of nodes being added, you might need to adjust
the EXPECTED_VOTES system parameter to reflect the number of voting nodes and any quorum
disk votes (if a quorum disk is being used). In addition, for any node being removed from the
cluster, you should specify the REMOVE_NODE option during system shutdown so that the
quorum for the remaining nodes is correctly adjusted.
5.5 Types of Upgrades
Two types of cluster upgrades are available: a concurrent upgrade and a rolling upgrade. The
type of upgrade you use depends on whether you want to maintain the availability of the cluster
during the upgrade and whether you have more than one system disk. Review this chapter and
then perform the preliminary tasks for the upgrade procedure (concurrent or rolling) that best
suit your configuration.
5.5.1 Concurrent Upgrade
This section describes the following:
• How a concurrent upgrade works
• Preparing your system for a concurrent upgrade
5.5.1.1 How a Concurrent Upgrade Works
During a concurrent upgrade, you must shut down the entire cluster and upgrade each system
disk. No one can use the cluster until you upgrade each system disk and reboot each computer.
When the cluster reboots, each computer will run the upgraded version of the OpenVMS operating
system.
If all systems in the OpenVMS Cluster environment are booted from one system disk, you must
perform a concurrent upgrade.
5.5.1.2 Preparing Your System for a Concurrent Upgrade
To prepare for a concurrent upgrade, follow these steps:
5.4 Adding a New System to an OpenVMS Cluster 97