3    Patch Installation and Removal Instructions

This chapter provides instructions for installing and removing patches from the Tru64 UNIX operating system and the TruCluster software products. Although the descriptions and examples in this chapter reflect the installation and removal steps of Release Patch Kits, the steps are basically the same for dupatch-based CSP and ERP kits.

Chapter 4 describes the procedure for patching a TruCluster Server Version 5.0A or higher cluster using the rolling upgrade function. If you are patching your system with that process, follow the steps described there. You will be returned to this chapter when it is time to run dupatch.

If you have not yet created your cluster, follow the steps in Section 1.8.3.

The -l of the setld command is disabled for patch subsets.

3.1    Before You Begin the Installation

Before beginning the installation, make sure that you have completed all of the following preliminary steps:

The following sections provide step-by-step instructions for installing and enabling patches.

3.2    Expanding the Patch Kit Tar File

If you are using patch tar files obtained via the Internet (see Patch Process Resources), you must expand the tar file to access the patch kits. The tar file can be expanded on any mountable file system. The following list describes procedure:

  1. Mount the file system and create a directory.

    # /usr/sbin/mount /dev/disk/dsk3g /patches
    # cd /patches  
    # mkdir pk5
    

    Note

    If you are installing successive patch kits, place and untar each kit in a separate directory.

    Copy or ftp the patch kit to the directory you created. For example:

    # cp T64V51BB26AS0005-20050215.tar  /patches/pk5
    

  2. Untar the patch kit, capturing the process to a log file. For example:

    # script untar.log
    # tar -xpvf /patches/pk5/T64V51BB26AS0005-20050215.tar
    # [Ctrl/d]
    

  3. View the untar.log for errors or failures untarring the file.

3.3    Choosing Single-User or Multiuser Mode

You can install patches from either single-user or multiuser modes. See Section 1.8.1 for information about selecting one of these modes. Section 3.3.1 describes the process from single-user mode and Section 3.3.2 describes the process from multiuser mode. Section 3.4 describes the remaining steps, which are common to installations from single-user and multiuser modes.

3.3.1    Installing Patches from Single-User Mode

The following steps describe a patch kit installation from single-user mode. Although these steps are the same whether installing an old or new style patch kit, the text that dupatch displays differs in minor ways. The examples used in these steps reflect the output of a new style patch kit installation.

  1. Halt the system. For example:

    # /usr/sbin/shutdown -h +5 "Applying 5.1B-3 OS and TCR  patches"
    

  2. Boot to single-user mode from the console prompt. For example:

    >>>boot -fl s 
    

  3. Run the init s command to change the run level to a single-user state with only essential kernel services:

    # /sbin/init s
    

  4. Run the bcheckrc command to check and mount all the UFS and AdvFS file systems, the kloadsrv command to load kernel modules into the kernel, and the lmf reset command to copy license details for all enabled products from the License Database to the kernel cache:

    # /sbin/bcheckrc
    # /sbin/kloadsrv
    # /usr/sbin/lmf reset
    

  5. For systems prior to 5.0A, issue the update command and activate your swap partition with the swapon command:

    # /sbin/update
    # /sbin/swapon -a
    

  6. Enter the rcinet command to start network services:

    # /usr/sbin/rcinet start
    

    Informational messages will appear on the screen.

  7. Run the dupatch utility. You will be asked to specify the path to the patch_kit file. For example:

    # cd /var/patch/pk5/patch_kit
    # ./dupatch
     
    Enter path to the top of the patch distribution, 
    or enter "q" to quit : .
     
     
     
    

  8. From the Main Menu, enter 1 at the Enter your choice prompt to invoke the patch installation session. For example:

    Tru64 UNIX Patch Utility (Rev. 48-00)
    ==========================
            - This dupatch session is logged in /var/adm/patch/log/session.log
     
        Main Menu:
        ---------
     
        1)  Patch Kit Installation
        2)  Patch Kit Deletion
        3)  Patch Kit Documentation
     
        4)  Patch Tracking
        5)  Patch Baseline Analysis/Adjustment
     
        h)  Help on Command Line Interface
     
        q)  Quit
     
    Enter your choice: 1
     
     
    

  9. When the patch installation menu is displayed, enter 2 at the Enter your choice prompt:

         Patch Installation Menu:
         -----------------------
     
        1)  Pre-Installation Check ONLY
        2)  Check & Install the patch kit in Single-User Mode
     
        b)  Back to Main Menu
        q)  Quit
     
    Enter your choice: 2
    

3.3.2    Installing Patches from Multiuser Mode

The following list describes the steps you take and the type of output you will see when you install patches from multiuser mode.

  1. Run the dupatch utility and enter 1 at the Enter your choice prompt to the invoke the patch installation session:

    # /patches/pk4/patch_kit/dupatch
    Tru64 UNIX Patch Utility (Rev. 48-00)
    ==========================
            - This dupatch session is logged in /var/adm/patch/log/session.log
     
        Main Menu:
        ---------
     
        1)  Patch Kit Installation
        2)  Patch Kit Deletion
        3)  Patch Kit Documentation
     
        4)  Patch Tracking
        5)  Patch Baseline Analysis/Adjustment
     
        h)  Help on Command Line Interface
     
        q)  Quit
     
         Enter your choice: 1
    

  2. When the patch installation menu is displayed. Enter 3, at the Enter your choice prompt. Read the warning message and press Return if you want to continue the installation in multi-user mode:

         Patch Kit Installation Menu:
         -----------------------
     
        1)  Pre-Installation Check ONLY
        2)  Check & Install in single-user mode w/ network services
        3)  Check & Install in Multi-User mode
     
        b)  Back to Main Menu
        q)  Quit
     
    Enter your choice: 3
     
                    *** Installation Warning ***
     
    You have chosen to install the patch kit onto this system while it is
    running in Multi-User mode. Some patches may directly affect core operating
    system operations. To ensure the proper operation of all applications, it is
    strongly suggested that you install these patches while the system is in
    Single-User mode. If this cannot be done, install these patches when the
    system is as lightly loaded as possible (i.e. not running production
    environments, no users logged on, etc.).
     
    Do you wish to continue? (y/n) [y]:
    

3.4    Common Installation Steps

The following steps provide instructions for continuing the installation of Tru64 UNIX and TruCluster software patches after you have selected either single-user or multiuser mode.

  1. Specify whether or not you accept the license agreement. You can read the license on screen or you can read the license before beginning the installation process in the Patch Summary and Release Notes that comes with the patch kit. In the following output, the license is removed to save space:

    Tru64 Unix License Agreement
    ** ... **
     
    To read the license again, type 'license'.
    Do you accept the license agreement? (y/n) : y
     
    Checking patch kit for transmission errors during download...
     
    Finished Checking patch kit checksums
    

  2. You have the option to make patches reversible so you can return the system to its state prior to the installation of a patch. Enter y or press Return to make the patches reversible. For example:

    Do you want the patches to be reversible? [y]:
    

    By default, backup copies of the installed patches are saved in /var/adm/patch/backup. If you have limited space in /var, you may want to make the backup directory the mount point for a separate disk partition, an NFS-mounted directory, or a symbolic link to another file system.

    If you answer no to this question, the existing system files will not be saved and the installed patches will not be reversible. HP recommends that you install patches so they are reversible.

  3. The program describes your backup setup and asks you if you want to proceed:

    Do you want to proceed with the installation with this setup? [y]: 
     
    

  4. You are asked to record your name as the person installing the patches and to add any comments you would like stored for future reference. For example:

    Your name: Joe C.
    

    Enter any notes about this operation that you would like stored for future reference. To end your input, enter a period (.) and press Return.

    : Installing Patch Kit 5
    : . [Return]
    

  5. The next action depends on the type of kit you are installing:

3.5    Rebuilding the Kernel

The dupatch utility determines whether the installation or removal of patches requires that the kernel be rebuilt. This action is performed automatically or manually, depending upon the method you used to install the patches:

After the patch kit is installed you will see output similar to the following:

Configuring "Patch: SP04 OSFADVFSBIN540" (OSFPAT02500300540)
 
Configuring "Patch: SP04 OSFADVFS540 (SSRT2275)" (OSFPAT02500200540)
 
Beginning kernel build...
 
 
Do you have a pre-existing configuration file?:

If you answer yes, dupatch will build the kernel noninteractively, enabling all (mandatory and optional) kernel options automatically. This procedure is similar to running the doconfig -a command.

If you answer no, dupatch will build the kernel interactively. This procedure is similar to running the doconfig -c command. The following steps describe this procedure and provide some guidance for making your selections:

  1. Enter a new name for the kernel configuration file or accept the default. If you accept the default you will be asked if you want to replace it. For example:

      *** KERNEL CONFIGURATION AND BUILD PROCEDURE ***
     
    Enter a name for the kernel configuration file. [IDIOM2]: [Return]
     
    A configuration file with the name 'IDIOM2' already exists.
    Do you want to replace it? (y/n) [n]: y
    Saving /sys/conf/IDIOM2 as /sys/conf/IDIOM2.bck
    

  2. Specify the kernel options you want. If you are unsure of which options to specify, consider the following:

    The following output is similar to what you will see. The procedure gives you the opportunity to edit the configuration file:

    *** KERNEL OPTION SELECTION ***
     
        Selection   Kernel Option
    --------------------------------------------------------------
    	1	System V Devices
    	2	NTP V3 Kernel Phase Lock Loop (NTP_TIME)
    	3	Kernel Breakpoint Debugger (KDEBUG)
    	4	Packetfilter driver (PACKETFILTER)
    	5	IP-in-IP Tunneling (IPTUNNEL)
    	6	IP Version 6 (IPV6)
    	7	Point-to-Point Protocol (PPP)
    	8	STREAMS pckt module (PCKT)
    	9	Data Link Bridge (DLPI V2.0 Service Class 1)
    	10	X/Open Transport Interface (XTISO, TIMOD, TIRDWR)
    	11	Digital Versatile Disk File System (DVDFS)
    	12	ISO 9660 Compact Disc File System (CDFS)
    	13	Audit Subsystem
    	14	ATM UNI 3.0/3.1 ILMI (ATMILMI3X)
    --- MORE TO FOLLOW ---
    Enter your choices or press <Return>
    to display the next screen.
     
    Choices (for example, 1 2 4-6): 2-12
    	15	IP Switching over ATM (ATMIFMP)
    	16	LAN Emulation over ATM (LANE)
    	17	Classical IP over ATM (ATMIP)
    	18	ATM UNI 3.0/3.1 Signalling for SVCs (UNI3X)
    	19	Asynchronous Transfer Mode (ATM)
     
    The following choices override your
    previous selections:
     
    	20	All of the above
    	21	None of the above
    	22	Help
    	23	Display all options again
    --------------------------------------------------------------
     
     
    Enter your choices, choose an overriding action or
    press <Return> to confirm previous selections.
     
    Choices (for example, 1 2 4-6): [Return] 
     
    You selected the following kernel options:
    	NTP V3 Kernel Phase Lock Loop (NTP_TIME)
    	Kernel Breakpoint Debugger (KDEBUG)
    	Packetfilter driver (PACKETFILTER)
    	IP-in-IP Tunneling (IPTUNNEL)
    	IP Version 6 (IPV6)
    	Point-to-Point Protocol (PPP)
    	STREAMS pckt module (PCKT)
    	Data Link Bridge (DLPI V2.0 Service Class 1)
    	X/Open Transport Interface (XTISO, TIMOD, TIRDWR)
    	Digital Versatile Disk File System (DVDFS)
    	ISO 9660 Compact Disc File System (CDFS)
     
    Is that correct? (y/n) [y]: [Return]
     
    Do you want to edit the configuration file? (y/n) [n]: [Return]
     
     
    *** PERFORMING KERNEL BUILD ***
     
    A log file listing special device files is located in /dev/MAKEDEV.log
    	Working....Tue Mar  9 11:36:33 EST 2004
     
    The new kernel is /sys/IDIOM2/vmunix
    

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

3.6    Rebooting the System

The action that dupatch takes to reboot your system depends upon whether you used the command-line or menu-based interface or performed the action in single-user or multiuser mode. The following sections describe these actions.

Before rebooting, review the dupatch session log, /var/adm/patch/log/session.log, to ensure that the installation was successful. Note any special patch instructions, informational messages, and error messages. Certain patches may require you to take a particular action, such as running a script, before rebooting. (See Appendix A for information about dupatch logs.)

3.6.1    In Single-User Mode

When performing a patch installation or removal in single-user mode from the command line, the system automatically reboots after the command line operation is completed.

When performing a patch installation or removal in single-user mode using the menu-based interface, dupatch asks if you want to reboot the system after the patch installation or removal is completed:

3.6.2    In Multiuser Mode

When installing patches in multiuser mode from the command line, you are given a message informing you that a reboot is necessary to complete the patch installation. However, the system does not reboot itself.

When installing patches in multiuser mode using the menu-based interface, dupatch gives you three options if a reboot is necessary:

3.7    Post-Installation Actions

The following sections describe actions for you to take after you have completed the dupatch installation procedure.

3.7.1    Enabling the Version Switch After Installing a New Style Patch Kit

Some patches may require you to run the versw -switch command to enable the new functions delivered in those patches. (See Section 1.7 for information about version switches.) You perform this action after dupatch has completed the installation:

# versw -switch

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

3.7.2    Remove Temporary Directory

Once your patch kit is installed, delete the temporary directory in which you expanded the patch kit tar file. For example:

# rm -r /Patches/PK4

Removing the temporary directory will preclude the possibility of using that directory for subsequent patch kit installations. When performing a patch kit installation, using a directory that contains files from a previous patch kit installation can leave your system in an unstable condition.

Remember that if you want to save the patch kit tar file, remove it from the temporary directory before deleting the directory.

3.7.3    Adding the Worldwide Language Support

Inclusive patch kits provide patches to the Tru64 UNIX Worldwide Language Support subset (WLS). If the WLS subset is installed on your system, the WLS patches will be installed automatically when you install the patch kit. However, if you install the WLS subset after patching your system, you will have to rerun dupatch to install the WLS patches. The dupatch utility will see the WLS subset, recognize that the patches have not been installed, and will install them.

3.8    Removing Patches

To remove patches from your system, use the Patch Deletion option of the dupatch Main Menu. The following sections describe actions describe the patch removal process.

3.8.1    Overview

Beginning with the version of dupatch delivered in the Version 5.1B-3 kit, the patch removal process depends upon whether you installed the new form of patch kits, called Inclusive Patch Kits. These kits began shipping with Version 5.1B-2.

With Inclusive Patch Kits you must remove the entire kit rather than individual patches. However, once you have removed any Inclusive Patch Kits installed on your system, you can then remove individual patches from earlier kits.

To do this, dupatch recognizes the type of kit you have installed. When you select the patch deletion menu, dupatch lists the most current Inclusive Patch Kit installed on your system as well as any customer-specific patches (CSPs) that depend upon that kit.

After you remove that kit and reboot your system, you can rerun dupatch to remove the next most current Inclusive Patch Kit and the CSPs that depend on it.

Once all inclusive patch kits have been removed, the next time you run the patch deletion program, dupatch will list all of the patches on your system and you can selectively remove any of those patches.

Caution

With the old-style patch kits, the Patch Deletion menu lists every setld-based patch on your system, regardless of which patch kit installed them. If you select the ALL of the above menu item, it will remove all setld-based patches from your system. Therefore, you want to remove all of the patches from a patch kit, but do not want to delete setld-based patches, you will have to specify the patch ID of all of that kit's patches.

The latest version of dupatch also gives you the option to delete patches in single-user mode or in multiuser mode. As with the installation process, using single-user mode is safer and is the recommended procedure. See Section 1.8.1 for more information.

The dupatch utility issues the following warning when you are deleting patches in multiuser mode.

*** Multi-User Deletion Warning ***
 
You have chosen to delete patches from this system while it is running in
Multi-User mode. Some patches may directly affect core operating system
operations. To ensure the proper operation of all applications, it is
strongly suggested that you delete these patches while the system is in
Single-User mode. If this cannot be done, delete these patches when the
system is as lightly loaded as possible (i.e. not running production
environments, no users logged on, etc.).
 
Do you want to continue? (y/n):

If you want to continue, answer yes. If you do not want to delete the patch kit in multiuser mode, answer no and bring your system down to single-user mode as described in Section 3.3.1.

3.8.2    Important Tasks Required Before Removing Patches and Rebooting System

Before running the patch deletion process you may have to perform the tasks described in the following sections.

3.8.2.1    Run Mandatory Script Before Removing New Style Patch Kits

If you enabled version switches as described in Section 3.7.1 for an Inclusive Patch Kit, you must run the /usr/sbin/versw_enable_delete script before attempting to remove the patch kit. The steps for running this script require a complete cluster or single system shutdown, so choose a time when a shutdown will have the least impact on your operations. The following steps describe the procedure:

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

  2. Run /usr/sbin/versw_enable_delete:

    # /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 the patch kit.

    Note

    The next step requires that you reboot each cluster member to remove the patch kit. Because the no-roll procedure automatically reboots the system after deleting the patches, you would not be able to perform the next steps as required. Therefore, you cannot use the no-roll procedure to remove this patch kit.

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

3.8.2.2    Changes to System May Need to Be Reversed

If you made the following changes to your system after installing the patch kit, you will have to undo those changes before you can uninstall the patch kit:

To uninstall the patch kit, do the following:

  1. Remove all new hardware and new cluster members that you added after installing the patch kit.

  2. Run dupatch to uninstall the patch kit.

  3. Verify that the patch kit was successfully uninstalled.

You can now add the cluster members you removed and reinstall the hardware you removed, as long as the support for it existed in the pre-patched system. You can also reinstall the patch kit.

3.8.2.3    Script Must Be Run Prior to Reboot on Certain Version 5.1B Systems

If removing a PK4 or higher patch kit restores your Version 5.1B system to a pre-patched state, you must run the script /etc/dn_fix_dat.sh before rebooting your system during the patch deletion process. This would occur if the inclusive patch kit you are uninstalling is the only patch kit installed on your Version 5.1B system

You must also run this script if you are removing a specific patch from previous Version 5.1B patch kits if those kits are the only patch kit on your system. The affected patch in those kits will be noted in a Special Instruction that is displayed when you run the dupatch installation and deletion processes.

Failing to run this script will result in your system being unable to boot normally. If this occurs, do the following:

  1. Boot your system in single-user mode:

     >>> boot -fl s 
    

  2. Run the script:

    # /etc/dn_fix_dat.sh
    

  3. Reboot normally.

If you also need to reverse the version switch as described in Section 3.8.2.1, run the /etc/dn_fix_dat.sh script after step 5 in that process.

3.8.3    Running dupatch to Remove Patches

The process for removing patches is similar to the one for installing them.

The following steps describe the patch removal process for an Inclusive Patch Kit with the system running in single-user mode. In mutiuser mode the steps would be the same except you would see the multiuser deletion warning described in Section 3.8.1.

See Section 3.3.1 for the steps on bringing down your system to single-user mode.

  1. Run dupatch and select 2 for patch removal:

    # /patch/pk4/patch_kit/dupatch
     
    Tru64 UNIX Patch Utility (Rev. 48-00)
    ==========================
            - This dupatch session is logged in /var/adm/patch/log/session.log
     
        Main Menu:
        ---------
     
        1)  Patch Kit Installation
        2)  Patch Kit Deletion
        3)  Patch Kit Documentation
     
        4)  Patch Tracking
        5)  Patch Baseline Analysis/Adjustment
     
        h)  Help on Command Line Interface
     
        q)  Quit
     
    Enter your choice: 2
    

  2. Select the current patch kit. This menu will change if no Inclusive patch kits are installed.

    There may be more patches than can be presented on a single
         screen. If this is the case, you can choose patches screen by screen
         or all at once on the last screen. All of the choices you make will
         be collected for your confirmation before any patches are deleted.
     
         1) CSP C688.00  drag-and-drop or cut-and-paste may fail
         2) CSP C718.00  Debug version of ping 
         3) CSP C752.00  page on o/h list panic 
         4) CSP C882.00  Fix for memory leak and slowdown in rpc.lockd
         5) T64V51BB26AS0005-20050215 and all CSP's dependent upon it 
     
    Or you may choose one of the following options:
     
         2) ALL of the above 
         3) CANCEL selections and redisplay menus
         4) EXIT without deleting any patches 
     
    Enter your choices or press RETURN to redisplay menus.
     
    Choices (for example, 1 2 4-6): 7
     
    You are deleting the following patches:
     
            T64V51BB26AS0005-20050215 and all CSP's dependent upon it               
     
    Is this correct? (y/n):y
     
                    ***  Start of Special Instructions  ***
     
     
     
    If you delete this patch kit, you MUST run the following script prior to 
    rebooting your system:  /etc/dn_fix_dat.sh
    
    .
    .
    .

  3. You are asked to record your name as the person removing the patches and to add any comments you would like stored for future reference in the log file. For example:

    Your name: Betty
    

    Enter any notes about this operation that you would like stored for future reference. To end your input, enter a period (.) and press Return.

    : Uninstalling V5.1B-3
    : . [Return]
     
    Checking patch dependency...
      (depending upon the number of patches you select, this may take awhile)
     
     
       *** The Patch Kit will delete 67 patches ***
     
    ************************** CAUTION ************************************ 
     
    	Interruption of this phase of the operation will corrupt your 
    	operating system software and compromise the patch database 
    	integrity. 
     
    	DO NOT Ctrl/C, power off your system, or in any other way 
    	interrupt the patch operation. The patch operation is complete 
    	when you are returned to the Patch Utility menus.
     
    ***********************************************************************
    Deleting "Patch: SP05 OSFEXER540" (OSFPAT02603100540).
    Deleting "Patch: SP05 OSFEXAMPLES540" (OSFPAT02603000540).
    Deleting "Patch: SP05 OSFENVMON540" (OSFPAT02602800540).
    
    .
    .
    .

  4. Rebuild the kernel. This step is the same as for the installation process. See Section 3.5 for details.

  5. Review the session log to ensure the removal was successful. Note any special patch instructions, informational messages, and error messages. This is especially important to identify any actions that you may have to take (such as running a script) before rebooting your system.

  6. Run the script described in Section 3.8.2.3.

  7. Reboot the system. See Section 3.6 for details.