HP OpenVMS Systems Documentation

During a rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster, creating a mixed-version cluster. Because rolling upgrades allow mixed-version clusters, the systems that you are not upgrading remain available. During a rolling upgrade, you keep some of the computers in the cluster running while you upgrade others (you must have more than one system disk).

6.5.2 Notes and Restrictions

The following restrictions apply to rolling upgrades. See the OpenVMS Version 7.3 Release Notes for additional compatibility issues and restrictions.

• Rolling upgrades are supported from Version 6.2x, 7.1x, and 7.2x of the Compaq OpenVMS Alpha operating system. Rolling upgrades in mixed-architecture OpenVMS Cluster environments are supported with VAX computers running Versions 7.2 or 6.2 of the Compaq OpenVMS VAX operating system (see Table 6-1).
• The upgraded system does not attempt to access any disk that is being accessed by one or more of the remaining OpenVMS Cluster systems.
• The remaining OpenVMS Cluster systems do not attempt to access the target disk of the system being upgraded.
  If the target disk being upgraded is locally attached to the system performing the upgrade, then it is not accessible to the remaining OpenVMS Cluster systems. (The OpenVMS system booted from the operating system CD-ROM does not MSCP serve local disks.) Whenever possible, Compaq recommends that you perform the upgrade on a local disk or that you perform a concurrent upgrade.
  During the upgrade, be sure that the target disk you select, as well as any disk you access from the DCL menu option, is either a local disk or one that is not being accessed by any of the remaining OpenVMS Cluster members.

  Note Any attempt to access the target disk from the remaining OpenVMS Cluster members will corrupt the target disk in most cases. Even if the target disk is mounted only by a remaining cluster member, and no file access is done, the target disk will probably be corrupted. If a disk is corrupted in this way, the only supported recovery is to restore the backup copy of the corrupted disk.

• Compaq recommends that all Alpha computers in a cluster run the same (and preferably the latest) version of the Compaq OpenVMS Alpha operating system.
• You cannot perform a rolling upgrade if all systems boot from a single system disk. Perform a concurrent upgrade instead.
• The upgrade procedure affects the queuing system as follows:
  • The queuing system is not active on the system you are upgrading; do not attempt to execute a START/QUEUE/ MANAGER command.
  • You cannot create a queue database on the operating system CD-ROM (because it is not writable).
  • The queue manager process on other nodes in the cluster can continue to run during the upgrade if the queue database is not on the disk being upgraded.

To prepare for a rolling upgrade:

1. Log in to any node where the target disk is mounted as a data disk, rather than as the system disk. (That disk must be the one on which you already performed the preupgrade tasks described in Chapter 5.)
2. Check the votes and make adjustments to maintain the proper quorum so the cluster can continue to operate throughout the upgrade. (OpenVMS Cluster Systems describes this procedure in detail.)
3. Use the DCL command DISMOUNT/CLUSTER to dismount the data disk. (You can also perform this operation using the SYSMAN utility.)
   Note that you can ignore messages from nodes where the specified data disk is being used as the system disk.
4. Verify that the data disk has been dismounted successfully by entering the following commands:

   $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO SHOW DEVICE disk-name

   
   Examine the display to be sure the disk is not mounted on any nodes as a data disk. Noting the value listed in the Trans Count field can help you make that determination: A value of less than 50 indicates that the disk is mounted as a data disk rather than as the system disk; a much larger value (for example, 300) indicates that the disk most likely is the system disk.
5. If the disk is still mounted on any nodes as a data disk, use the SYSMAN utility to dismount the disk; otherwise, exit from the SYSMAN utility.
6. Shut down all nodes that boot from the system disk you are upgrading, including the node from which you will perform the upgrade. Enter the following command on each node:

   $ @SYS$SYSTEM:SHUTDOWN

7. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key.
8. Choose the REMOVE_NODE option.
9. If proper quorum is not maintained at any time during the upgrade procedure, the shutdown procedure will hang the cluster. If the cluster hangs during a shutdown, enter the following commands on the system console of a system that is still a cluster member:

   $ [Ctrl/P] >>> D SIRR C >>> C IPC> Q IPC> [Ctrl/Z]

10. After the shutdown procedure is finished on all nodes, go to Chapter 7 to begin the upgrade procedure.

This chapter describes the following tasks:

• Beginning the upgrade from the operating system CD-ROM
• Specifying the target disk
• Specifying the volume label
• Updating time zone information
• Choosing descriptive help text
• Completing the upgrade
• Performing postupgrade tasks (including booting the upgraded system)
• Installing layered products

The Compaq OpenVMS Alpha Version 7.3 operating system includes procedures that allow you to easily upgrade the operating system using the POLYCENTER Software Installation utility. To get started, boot the Compaq OpenVMS Alpha operating system CD-ROM either from your local CD-ROM drive or from a CD-ROM drive connected to the InfoServer, as described in the following sections.

7.1.1 Booting from the Local Drive

To boot the operating system CD-ROM from the local drive, follow these steps:

1. Insert the operating system CD-ROM into the local CD-ROM drive.
2. At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD-ROM drive (for example, DKA400:)
3. Enter the boot command in the following format:

   BOOT -FLAGS 0,0 source-drive

   
   Substitute the device name of the CD-ROM drive (as listed in the SHOW DEVICE display) for source-drive.
   For example, if the SHOW DEVICE display lists the device name of your CD-ROM drive as DKA400, enter the following command and press the Return key:

   >>> BOOT -FLAGS 0,0 DKA400

To boot the operating system CD-ROM using the InfoServer, follow these steps:

1. At the console prompt (>>>), enter the SHOW DEVICE command and scan the devices listed in the output to determine the name of the CD-ROM drive. Look for a device listed with its hardware address; for example, see the last line in the following example:

   >>>SHOW DEVICE dva0.0.0.1000.0 DVA0 RX23 dka200.2.0.5.0 DKA200 RZ28M 1004 dka300.3.0.5.0 DKA300 RZ29B 0016 dka400.4.0.5.0 DKA400 RZ26L 442E ewa0.0.0.3.0 00-00-F8-1F-70-3D Twisted-Pair

   
   For additional information, refer to the Compaq OpenVMS Operating System for Alpha and VAX Software Product Description and the hardware manuals that you received with your Alpha computer.
2. At the console prompt, enter the following command:

   >>> BOOT -FLAGS 0,0 -FILE APB-filename lan-device-name

   
   Note the following conventions:
   • APB-filename is the unique file name that was assigned to the APB.EXE file when it was copied from the operating system CD-ROM to the InfoServer (for example, APB_V73). This file is the name of the APB program used for the initial system load (ISL) boot program.
   • lan-device-name is the name of the local area network (LAN) device identified with your computer, as determined by using the SHOW DEVICE command in the previous step.

   Note If you are using a DEC 3000 or 4000 series system, note the following: On DEC 3000 series systems, you can boot through the InfoServer with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as "n/ESA0". The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8. On DEC 4000 series, you must specify the ISL file name in uppercase (APB_073).

3. The InfoServer ISL program then displays the following menu:

   Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value:

4. Respond to the prompts as follows, pressing the Return key after each entry:
   1. Enter 3 for the function ID.
   2. Enter 2 for the option ID.
   3. Enter the service name (ALPHA073).
   
   A sample display follows:

   Enter a function ID value: 3[Return] OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2[Return] Enter a Known Service Name: ALPHA073[Return]

The following sections describe how to upgrade from the operating system CD-ROM.

7.2.1 Upgrading from the CD-ROM

After you boot the operating system CD-ROM, choose the upgrade option (1) from the menu displayed on the screen. The display is similar to the following:

     OpenVMS (TM) Alpha Operating System, Version 7.3

    Copyright (c) 2001 Compaq Computer Corporation.  All rights reserved.



    Installing required known files...

    Configuring devices...

    ****************************************************************

    You can install or upgrade the OpenVMS Alpha operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS Alpha operating system CD-ROM.

    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk.

    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS Alpha Version 7.3
        2)  Display products and patches that this procedure can install
        3)  Install or upgrade layered products and patches
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Execute DCL commands and procedures
        8)  Shut down this system

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1

The Compaq OpenVMS Alpha operating system CD-ROM may contain patch kits. If it does, information similar to the following will be displayed:

            The following PATCH kits are present on the OpenVMS Alpha
            distribution media.

        ----------------------------------- ----------- ----------
        PRODUCT                             KIT TYPE    KIT FORMAT
        ----------------------------------- ----------- ----------
        DEC AXPVMS UCXECO_42_1 V1.0         Patch       Sequential
        ----------------------------------- ----------- ----------

        1 item found

            Please consult the OpenVMS Alpha Upgrade and Installation Manual,
            the Release Notes, and the Cover Letter to determine if any or
            all of these patches may be required for your system.

After you choose the upgrade option, the system displays the following information and prompts:

    ***********************************************************

    The installation procedure will ask a series of questions.

          () - encloses acceptable answers
          [] - encloses default answers

    Type your response and press the <Return> key.  Type:

          ? - to repeat an explanation
          ^ - to change prior input (not always possible)
          Ctrl/Y - to exit the installation procedure

    There are two choices for Installation/Upgrade:

    INITIALIZE - removes all software and data files that were
        previously on the target disk and installs OpenVMS Alpha.

    PRESERVE -- installs or upgrades OpenVMS Alpha on the target disk
        and retains all other contents of the target disk.

   * NOTE: You cannot use PRESERVE to install OpenVMS Alpha on a disk on
        which OpenVMS VAX or any other operating system is installed.

Do you want to INITIALIZE or to PRESERVE? [PRESERVE])

For an upgrade, press the Return key to accept the default (PRESERVE).

7.2.3 Specifying the Target Disk

Next, the procedure asks you for the name of the target disk. If you enter a question mark (?), the system displays a list of devices on your system. Select the appropriate disk and respond to the prompt. For example:

You must enter the device name for the target disk on which
    OpenVMS Alpha will be installed.

Enter device name for target disk: (? for choices) dkb400

If you select a device that is not available or that cannot be used for some other reason, the system displays information indicating why the device cannot be used. For example, if you enter MKA500, a tape device, a message similar to the following is displayed:

MKA500 is not a disk device

The system then prompts you for the volume label and asks if the information is correct. You can accept the default label assigned by the system (AXPVMSSYS) or specify a different volume label (with a limit of 12 characters that can be letters A-Z, numbers 0-9, dollar signs ($), hyphens (-), or underscores (_)).

After you select the volume label, the target disk is mounted and page and swap files are created. For example:

    DKB400: is now labeled ALPHAUPGIV.

Do you want to keep this label? (Yes/No) [Yes]

    OpenVMS Alpha will be upgraded on DKB400:.

At this point the upgrade performs checks of some related software products.

7.2.5.1 Spiralog

If your system has Spiralog installed, the following message is displayed:

Either SPIRALOG is installed or SYS$SYSTEM:SPIRALOG.EXE is present on
the target system. SPIRALOG is no longer supported; it will not work
and can cause serious problems that are difficult to diagnose.

If installed, SPIRALOG must be removed before upgrading.

If SPIRALOG is not installed but SYS$SYSTEM:SPIRALOG.EXE is present
on the target system, this file must be deleted in order to prevent
the upgraded system from generating errors.
(Check common and specific directories for SPIRALOG.EXE.)

Termination is strongly recommended.

Do you want to terminate? (Yes/No) [YES]

Spiralog will not work with Compaq OpenVMS Alpha Version 7.3. If you have any version of Spiralog installed on your system, uninstall it before upgrading to Compaq OpenVMS Alpha Version 7.3.

7.2.5.2 DECamds

Beginning with OpenVMS Version 7.2 and DECamds Version 7.2, certain parts of DECamds that were previously supplied with the layered product kit are now incorporated into OpenVMS. Because of this, prior versions of DECamds must be removed.

If the upgrade procedure detects a prior version of DECamds, it will display the following message and automatically remove the prior version of DECamds. Note that you must reinstall DECamds if you wish to continue using it.

            The target system contains a version of DECamds that is not
            compatible with this version of the operating system.

            If you continue DECamds will be removed.  A current version of
            DECamds can be installed after the upgrade completes.

If PATHWORKS is installed on the system, OpenVMS Version 7.3 requires PATHWORKS Version V6.0D or later. The installation determines the PATHWORKS version and displays one of the following messages if an earlier version of PATHWORKS is present.

If PATHWORKS Version 5 or earlier is present:

PATHWORKS V5 is installed on the target system.

This version of PATHWORKS will not work on OpenVMS V7.3.
You must upgrade to PATHWORKS V6.0D or later, or disable
PATHWORKS on the target system, before upgrading OpenVMS.

Please refer to the release notes for additional information.

Do you want to continue? (Yes/No) [NO]

PATHWORKS V6.0-000 is installed on the target system.

This version of PATHWORKS is not supported on OpenVMS V7.3.
PATHWORKS V6.0D and later are supported on OpenVMS V7.3.
You may wish to upgrade to PATHWORKS V6.0D or later before
upgrading OpenVMS.

Please refer to the release notes for additional information.

Do you want to continue? (Yes/No) [NO]

In both cases the default is to terminate the upgrade. You must explicitly enter Yes and press the Return key to continue.

7.2.6 Checking OpenVMS Cluster Membership

The procedure now asks if your system will be part of a cluster. The display is similar to the following:

Will this system be a member of an OpenVMS Cluster? (Yes/No) Yes

You should answer Yes if the system will be an OpenVMS Galaxy instance or a member of an OpenVMS cluster. Unlike an installation, answering Yes to this question will not cause SYS$MANAGER:CLUSTER_CONFIG.COM to be run. However, correct cluster membership information is required by the upgrade procedure.

7.2.7 Becoming an OpenVMS Galaxy Instance

The procedure next asks if your system will be an instance in an OpenVMS Galaxy. The display is similar to the following:

Will this system be an instance in an OpenVMS Galaxy? (Yes/No) Yes

If you answer Yes to this question, and you also answered Yes to the OpenVMS Cluster question, then information about required remedial kits is displayed.

For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster that are running versions of OpenVMS prior to Version 7.1-2 must have a remedial kit installed. The following display indicates the correct remedial kits for various Compaq OpenVMS Alpha and VAX systems:

   For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster
   that are running versions of OpenVMS prior to V7.1-2 must have a
   remedial kit installed.  The appropriate kit from the following list
   must be installed on all system disks used by these systems.
   (Later versions of these remedial kits may be used if available.)

        Alpha V7.1 and V7.1-1xx         ALPSYSB02_071
        Alpha V6.2 and V6.2-1xx         ALPSYSB02_062

        VAX V7.1                        VAXSYSB01_071
        VAX V6.2                        VAXSYSB01_062