![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
To upgrade a standalone system, go to Chapter 7.
To upgrade a VAXcluster environment, go to Chapter 6.
This chapter describes how to upgrade a VAXcluster environment. Refer to OpenVMS Cluster Systems for more detailed information on VAXcluster environments.
If your cluster environment has both VAX and Alpha systems, you should also refer to the Migrating an Environment from OpenVMS VAX to OpenVMS Alpha.
There are two types of cluster upgrades: concurrent and rolling. 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.
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 VAX computer. If all systems in the VAXcluster environment are booted from one system disk, you must perform a concurrent upgrade.
Note
For OpenVMS VAX Version 7.1 concurrent upgrades, all nodes in the cluster must be running at least OpenVMS VAX Version 6.1. (See Section 5.2.10 for more information.)
To perform a concurrent upgrade, go to Section 6.3.
During a rolling upgrade, you can keep some of the VAX computers in the cluster running while you upgrade others (you must have more than one system disk). The cluster runs temporarily with different versions of the operating system.
Note
For OpenVMS VAX Version 7.1 rolling upgrades, all nodes in the cluster must be running at least OpenVMS VAX Version 6.1. (See Section 5.2.10 for more information.)
To perform a rolling upgrade, go to Section 6.4.
You perform a concurrent upgrade by shutting down the entire cluster, upgrading each system disk, and rebooting each VAX computer in the cluster. When the cluster reboots, each VAX computer will be running the upgraded version of the operating system. Users cannot access the cluster until you upgrade each system disk and reboot each VAX computer.
To perform a concurrent upgrade, use the following procedure:
$ @SYS$SYSTEM:SHUTDOWN
Caution
You cannot use the system disk that you usually use as the quorum disk to hold the save sets from the distribution kit.
SYSBOOT> USE CURRENT SYSBOOT> SET VOTES 1 SYSBOOT> SET EXPECTED_VOTES 1 SYSBOOT> CONTINUE
During a rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together temporarily in the same cluster. Clusters running two versions of the operating system are called mixed-version clusters. Because rolling upgrades allow mixed-version clusters, the systems that you are not upgrading remain available.
The following restrictions apply to rolling upgrades:
To perform a rolling upgrade follow these steps:
$ @SYS$SYSTEM:SHUTDOWN.COM
$ SET CLUSTER/EXPECTED_VOTES
$ [Ctrl/P] >>> H >>> D/I 14 C >>> C IPC> Q IPC> [Ctrl/Z]
Caution
The upgrade procedure requires exclusive access to the drive that holds the distribution media. Do not mount the distribution media on other nodes.
* Are the other system disks running OpenVMS V6.1 or higher?
If you need to add a new CPU supported by OpenVMS VAX Version 7.1 to an existing Version 6.1 VAXcluster, Digital supports two options, listed in the following preferred order:
This chapter explains the procedure for upgrading a single OpenVMS VAX system disk, including:
You must complete each phase of the upgrade procedure. On most VAX computers the upgrade procedure continues automatically from phase to phase. Read the screen displays carefully and, if you need to reboot your VAX computer manually, refer to the upgrade and installation supplement for your VAX computer and Appendix C of this manual.
The time required to complete an upgrade varies depending on your hardware configuration and on the distribution media you are using. In most cases, magnetic tapes and tape cartridges require more time than compact discs.
Before you begin the upgrade procedure, read the overview of the upgrade procedure described in Chapter 1 and complete the preupgrade tasks described in Chapter 5. If you are upgrading a VAXcluster, you must also read Chapter 6.
During the upgrade procedure, you are asked to boot the system from the [SYSF] directory on the system disk. The [SYSF] directory is a root directory created on the system disk by the upgrade procedure. It temporarily holds the system files used in the upgrade until the procedure moves the files to their permanent location. The upgrade procedure then removes the [SYSF] directory from the system disk.
If you do not know how to boot from [SYSF], read the upgrade and installation supplement for your VAX computer and Appendix C of this manual.
Ignore any error messages after the first reboot that indicate an invalid dump header version. These messages are normal and are to be expected.
Some VAX computers require a special command procedure to boot from [SYSF]. If you are performing an upgrade on one of the following VAX computers you must modify the boot command procedures, DEFBOO and dddGEN before beginning the upgrade procedure:
To modify the boot command procedures, exit from the OpenVMS VAX operating system (but do not shut it down) and enter the appropriate console mode. Make copies of DEFBOO and dddGEN before you modify them. Name the copies DEFBOO.SAV and dddGEN.SAV.
The upgrade and installation supplement for your VAX computer describes the procedures for copying and modifying DEFBOO and dddGEN. Use these procedures to modify DEFBOO and dddGEN so that they specify [SYSF] as the directory from which to boot.
In DEFBOO, change the DEPOSIT command that sets boot flags in register 5 (R5) as follows:
DEPOSIT R5=F0000000
In dddGEN, change the DEPOSIT command as follows:
DEPOSIT R5 F0000001
If you are upgrading a VAX 8200, 8250, 8300, or 8350 computer, you must create a boot command procedure that allows you to boot from the [SYSF] directory before beginning the upgrade. The upgrade and installation supplement for your VAX computer describes how to create this boot command procedure.
Because you rebooted your system with minimum startup, the system did not automatically configure all devices. However, you might need access to some of the devices to perform the upgrade.
To make sure you can access the devices that might be needed for the upgrade, run SYSGEN to reconfigure the devices on the system and run STARTUP CONFIGURE by entering the following commands:
$ RUN SYS$SYSTEM:SYSGEN SYSGEN> AUTOCONFIGURE ALL SYSGEN> EXIT $ @SYS$SYSTEM:STARTUP CONFIGURE
This section describes how to start the upgrade procedure using VMSINSTAL. You can type a question mark (?) for help at any time while running VMSINSTAL.
The instructions refer to the source drive and the target drive, where:
Put the distribution compact disc or tape in the source drive. If your OpenVMS VAX distribution kit contains several tapes, put the first one in the drive. The paper labels on the tapes indicate the order in which you use them.
If you are not using an InfoServer device, go to Section 7.3.3.
If you are using an InfoServer device, proceed to the next step.
If upgrading from an InfoServer device, perform the following steps:
$ @SYS$STARTUP:ESS$STARTUP CLIENT
%LASTCP-I-VERSION, LASTDRIVER X1.5 is stopped %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyy
$ RUN SYS$SYSTEM:ESS$LADCP LADCP> BIND/CONNECT/SYSTEM VAXVMS071 %LADCP-I-BIND, service bound to logical unit DAD$VMS071 (_DADn:) LADCP> EXIT
To start VMSINSTAL, use the following procedure:
VMSINSTAL displays a message similar to the following, depending on which version of the operating system is currently running on your system:
OpenVMS VAX Software Product Installation Procedure V7.0
It is 22-NOV-1996 at 15:00.00.00
Enter a question mark (?) at any time for help.
VMSINSTAL checks your system's account quotas. If it finds account quotas that are less than it expects, VMSINSTAL displays a message similar to the following:
%VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low.
-VMSINSTAL-W-LOWQUOTA, If you want to modify these account quotas, type NO to
-VMSINSTAL-W-LOWQUOTA, the next question, modify the appropriate quotas, log out
-VMSINSTAL-W-LOWQUOTA, then log back in and restart this procedure.
BYTLM: currently 32512; minimum expected 32768
* Do you want to continue anyway [NO]?
You should have verified that your SYSTEM account quotas were sufficient before beginning the upgrade. (See Section 5.6.8 for the minimum required values and for instructions for modifying quotas and limits.)
To modify the account quotas now, do the following:
To continue the upgrade without modifying the account quotas, type Yes and press the Return key.
The procedure displays the following message:
* Are you satisfied with the backup of your system disk [YES]?
If you have made a standalone backup of the system disk, press Return and go to Section 7.3.5.
If you have not made a standalone image backup of the system disk, do the following:
VMSINSTAL asks for the name of the drive that holds the distribution media:
* Where will the distribution volumes be mounted:
Enter the device name of the source drive. For example, if you have a VAX 6000 series computer that has a TK70 with a device name of MUC6, type MUC6 and press the Return key.
If the drive is connected to an HSC, enter the HSC name and the device name of the drive separated by a dollar sign ($). (If you do not enter the device name in this manner, it will cause a failure in Phase 2.) For example, if the HSC name is MUTT and the device name is MUA0, enter the following and press Return:
* Where will the distribution volumes be mounted: MUTT$MUA0
If you are not using an InfoServer device, proceed to Section 7.3.6.
If you are upgrading from a compact disc drive connected to an InfoServer, the device name is DADn. The n part of the device name was displayed when you bound to the distribution compact disc as previously described in Section 7.3.2.
If VMSINSTAL displays an error message, make sure the drive is connected and set up properly. Enter the name again. If VMSINSTAL displays another error message, use the following procedure to verify the device name:
If VMSINSTAL does not display an error message, proceed to Section 7.3.6.
When VMSINSTAL displays the following message, type VMS071 and press the Return key. Make sure that you use the number zero (not the letter O) when you type VMS071. For example:
* Products: VMS071When the procedure displays the following message, press Return:
* Enter installation options you wish to use (none):
VMSINSTAL displays a message similar to the following:
Please mount the first volume of the set on _MUA0.
When the procedure displays the following message, type Y (for Yes) S) and press Return:
* Are you ready? Y
The procedure displays messages similar to the following:
%MOUNT-I-MOUNTED, VMS071 mounted on _MUA0: The following products will be processed: OpenVMS V7.1
After a slight pause, the procedure displays a message similar to the following:
Beginning installation of OpenVMS V7.1 at 15:05 %VMSINSTAL-I-RESTORE, Restoring product saveset A...
The upgrade procedure displays several important messages that provide you with the following information:
Read these messages carefully to decide whether or not you need to interrupt the upgrade procedure. An interruption is allowed before Phase 1. The procedure displays the following message:
* Do you want to continue? (Y/N):
To continue the upgrade, type Yes and press the Return key.
To interrupt the upgrade, do the following:
The procedure displays the current date and time. If the date and time are correct, type Yes. If they are incorrect, type No. Enter the correct date and time using the 24-hour clock format and press Return. For example:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 22-NOV-1996 15:10
This section describes Phase 1 of the upgrade. During this phase, you provide passwords for system accounts and select OpenVMS options, and the procedure restores the files in the OpenVMS required save set (VMS071.B).
At the end of this phase, the procedure shuts down your VAX computer. If your computer uses console media when booting and the boot file was modified as described in Section 7.2, the system should reboot automatically. Otherwise, you must reboot manually from the SYSF directory.
At the beginning of Phase 1, the procedure displays a message similar to the following:
Upgrade Phase 1 22-NOV-1996 15:11:17.05 * Are you performing a rolling upgrade? (Y/N):If you are performing a concurrent upgrade or an upgrade on a standalone system, type No and press the Return key.
If you are performing a rolling upgrade, type Yes and press Return. The procedure will ask you several questions to determine if all system disks in the cluster (other than the one you are upgrading) are running at least OpenVMS VAX Version 6.0. Follow the instructions in Section 6.4.
To ensure system security, the upgrade procedure requires you to enter passwords for the SYSTEM, SYSTEST, and FIELD accounts before continuing. Passwords must contain at least 8 characters; they are not displayed by the system. Press Return after you enter each password and it will be verified. For example:
To help provide a more secure system, you are asked to enter passwords
for key system accounts. Passwords must be a minimum of 8 characters
in length. You can enter new or existing passwords.
Enter passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
* Enter password for SYSTEM:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified
* Enter Password for SYSTEST
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEST verified
The SYSTEST_CLIG account will be disabled. You must re-enable
it before running UETP but do not assign a password.
%UAF-I-MDFYMSG, user record(s) updated
Enter password for FIELD:
Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD-OKAY, account password for FIELD verified
If you enter a password incorrectly or if the password is too easy to guess, the procedure displays error messages similar to the following:
%VMS-W-PWD-INVALID, account password for FIELD is invalid %VMS-I-PWD-WEAK, password is too easy to guess Because of the preceding error, you must take action to secure this account. You must either disable this account, change its password, or do both.
When the procedure asks if you want to disable the account, type No and press the Return key. When the procedure asks if you want to enter a new password, type Yes and press Return. Then enter a new password. For example:
Do you want to disable the account (Y/N)? N Do you want to change the account password (Y/N)? Y You must now select a new primary password for the FIELD account. The password you select must be at least 8 characters in length and cannot be the same as the name of the account. New password: Verification: %UAF-I-MDFMSG, user record(s) updated %VMS-I-PWD-SET, primary password for account FIELD set
After you have correctly entered the passwords, the procedure does the following:
If your VAX computer is not one of the following, go to Section 7.4.4.
If your VAX computer is included in the preceding list, the procedure can temporarily modify the DEFBOO.CMD (or DEFBOO.COM if you have a VAX 8600 computer) to boot from the [SYSF] directory. During Phase 4 of the upgrade, the procedure restores the DEFBOO.CMD (or DEFBOO.COM) file that is set up to boot from the current system disk and system root.
6487P006.HTM OSSG Documentation 9-DEC-1996 10:53:58.65
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.