Release Notes for Version 5.1B-6 > Chapter 3 Release Notes   

Cluster-Specific Installation and Removal Release Notes

This section provides information you need to be aware of if you are installing or removing patch kits from a TruCluster Server environment.

Extract dupatch Tools Before Cloning

When beginning a cloning process, first mount the Version 5.1B-6 CD (or extract the kit if downloaded from the Web) to your Version 5.1B-5 system and run the dupatch command to install the necessary cloning tools. See the Patch Kit Installation Instructions document for information about installing the latest dupatch tools.

dupclone Error Message Can Be Ignored

Installing this kit using the dupclone process on systems that do not have all of the operating system and TruCluster Server base subsets installed might result in a messages similar to the following to be displayed:

Problem installing:

- Tru64_UNIX_V5.1B:
       Patch 29034.00
requires the existence of the following un-installed/un-selected subset(s):

- Tru64_UNIX_V5.1B:
       Patch 29023.00

- Tru64_UNIX_V5.1B:
       Patch 29050.00 . . .

You can ignore this message. In all cases, the subsets are installed correctly.

Installed CSP Might Affect dupatch Cloning Process

If you have installed customer-specific patches (CSPs) on your system, you might see a message similar to the following when installing this kit using the dupatch cloning process, at which time the cloning process is terminated:

Inspecting 69 patches for possible system conflicts ...         
                is installed by Customer Specific Patch (CSP):   
- Tru64_UNIX_V5.1B / Installation Patches:         
       Patch 01682.00 - Fix for dupatch command

               and can not be replaced by this patch. To install this patch,
               ideally, you must first remove the CSP using dupatch. 
               Before performing this action, you should contact your
               HP Service Representative to determine if this patch kit
               contains the CSP. If it does not, you may need to obtain a new
               CSP from HP in order to install the patch kit and retain the
               CSP fix.  Or, you may use dupatch baselining to enable the
               patch installation.

The recommended action is to perform dupatch baselining on your existing system to enable the patch installation process and retain the CSP on your system. Removing the CSP (as mentioned in the message) could eliminate the fixes made by that CSP.

After running the baselining process on your existing system, you need to begin the cloning process from the beginning by reduplicating your system on an alternate set of disks and rerunning the dupatch cloning process. See the Patch Kit Installation Instructions for information about performing baselining and about the patch cloning process.

Migrating a Patched Standalone System to a Cluster

Installing only the base patches on a noncluster system omits various patches (including some security patches) because of dependencies on TruCluster Server patches. Such patches are not needed on standalone systems. However, if the standalone system is then clustered using the clu_create command and you attempt to apply the cluster patches, many patches fail with errors because some prerequisite patches failed.

These errors do not necessarily indicate that the patch process has failed, but they are numerous, can be confusing and might obscure genuine errors.

The preferred procedure for adding a standalone system into a cluster is as follows:

  1. Reinstall the operating system on the standalone system.

  2. Run the clu_create command and bring up the standalone system as a cluster node.

  3. Apply all base and cluster patches.

Disable vfast Utility If Running on Cluster Domains

If the vfast utility is running on the TruCluster domains cluster_root and cluster_var, deactivate it on the domains before installing or removing this kit. To deactivate vfast on the two domains, use the following command:

# vfast deactivate cluster_root
# vfast deactivate cluster_var

See the vfast(8) reference page for more information.

Creation of Some MFS File Systems Depends on Version Switch

During the installation of this kit, MFS file systems that are 4 GB and larger (or 2 GB and larger if a 1024-byte sector size is used) cannot be created until after the version switch is thrown. See the Patch Kit Installation Instructions for information about the version switch.

Workaround Saves Files to Enable Patch Kit Removal

If you upgrade the operating system and install a patch kit within the same roll, the contents of the patch backups are inadvertently removed. The result is that the patches most recently installed cannot be removed because the backups are missing.

The following procedure saves then restores backups so they are available if you later decided to remove the patch kit:

  1. Create backup files of the /backup and /doc directories after the postinstall step (clu_upgrade postinstall) as follows:

    # cd /var/adm/patch/backup
    # tar cvf /var/adm/patch/BACKUP.tar * 
    # cd /var/adm/patch/doc
    # tar cvf /var/adm/patch/DOC.tar *
  2. After the switch step (clu_upgrade switch) untar the files you created in step 1:

    # cd /var/adm/patch/backup
    # tar xvf /var/adm/patch/BACKUP.tar
    # cd /var/adm/patch/doc
    # tar xvf /var/adm/patch/DOC.tar 

    This restores the files under the following directories:

    • /var/adm/patch/backup

    • /var/adm/patch/doc

Enabling the Version Switch After Installation

Some patches require you to run the versw -switch command to enable the new functions delivered in those patches. (See the Patch Kit Installation Instructions for information about version switches.) Enter the command as follows after dupatch has completed the installation process:

# versw -switch

The new functionality is not available until after you reboot your system. You do not have to run the versw -switch command, but if you do not, your system cannot access the functionality provided in the version-switch patches.

Script Required to Reverse Version Switch

If you enabled version switches as described in “Enabling the Version Switch After Installation”, you must run the /usr/sbin/versw_enable_delete script before attempting to remove Version 5.1B-4. The steps for running this script require a complete cluster or single system shutdown, so choose a time when a shutdown has the least impact on your operations. The following steps describe the procedure:

  1. Make sure that all phases of the installation process have been completed.

  2. Run the /usr/sbin/versw_enable_delete script:

    # /usr/sbin/versw_enable_delete
  3. Shut down the entire cluster or the single system.

  4. Reboot the entire cluster or the single system.

  5. Run dupatch on your single system or on a cluster using the rolling upgrade procedure to delete Version 5.1B-5 (as described in the Patch Kit Installation Instructions), up to the point where the kernel is rebuilt and the system must be booted.

  6. Reboot the single system or each member of the cluster.

    NOTE: This step requires that you reboot each cluster member to remove Version 5.1B-6. Because the no-roll procedure automatically reboots the system after deleting the patches, you cannot use that method to remove the kit.

Restriction on Using No-Roll Procedure to Remove Kit

The section titled “Script Must Be Run When Returning to Prepatched System” describes actions you need to take before rebooting your system if removing this kit would restore your system to a pro-patched state. Because the no-roll procedure automatically boots your system, you cannot use that patch kit removal method if doing so would restore your system to a pre-patched state

Do Not Install Prior NHD Kits on a Patched System

Do not install the NHD-5 or NHD-6 kits on your TruCluster Server system if you have installed this patch kit or earlier patch kits. Doing so might cause an incorrect system configuration. The installation code for these new hardware delivery kits does not correctly preserve some cluster subset files.