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.
See
Appendix C
for examples (log files) of complete patch installation and removal procedures.
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 2.6.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:
Make sure your system meets the installation prerequisites described in Section 2.1.
Make the patch distribution available to your system, as described in Section 2.2.
Load any new patch tools, as described in Section 2.3.
Perform the patch preinstallation check, as described in Section 2.4.
Set a system patch baseline, if needed, as described in Section 2.5.
Review the list of issues and restrictions in Section 2.6 and in the Patch Summary and Release Notes document that comes with your patch kit.
The following sections provide step-by-step instructions for
installing and enabling patches.
3.2 Choosing Single-User or Multiuser Mode
You can install patches from either single-user or multiuser modes.
See
Section 2.6.1
for information about selecting
one of these modes.
Section 3.2.1
describes the process
from single-user mode and
Section 3.2.2
describes the process
from multiuser mode.
Section 3.3
describes the remaining
steps, which are common to installations from single-user and multiuser modes.
3.2.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.
Halt the system. For example:
# /usr/sbin/shutdown -h +5 "Applying 5.1 and TCR Patches"
Boot to single-user mode from the console prompt. For example:
>>>boot -fl s
Run the
init s
command to change the run level to a single-user state with only essential
kernel services:
# /sbin/init s
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
For systems prior to 5.0A, issue the
update
command and activate your swap partition with the
swapon
command:
# /sbin/update # /sbin/swapon -a
Enter the
rcinet
command to start network
services:
# /usr/sbin/rcinet start
Informational messages will appear on the screen.
Run the
dupatch
utility.
You will be asked
to specify the path to the patch_kit file.
For example:
# cd /var/patch/patch_kit # ./dupatch Enter path to the top of the patch distribution, or enter "q" to quit : .
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. 46-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
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.2.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.
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. 46-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
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]:
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.
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.
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]:
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 4
:
.
[Return]
The next action depends on the type of kit you are installing:
Inclusive patch kit
With this type of kit
dupatch
peforms a preinstallation
check and begins to install the patches if it finds no problems.
For example:
Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take awhile). *** Installing 78 patches ***
If any patches fail the preinstallation check, do one of the following:
If the failure is the result of a file conflict, you will need to run the patch baseline process, as described in Section 2.5.
If the failure is caused by an installed CSP that is not included in the current patch kit, you will have to remove the CSP, install the patch kit, and reinstall the CSP. See Section B.1.8 for more information.
Old style patch kit
With this type of kit,
dupatch
lists the patches
available for installation on your system.
This list may be different from
system to system because
dupatch
does not display available
patches that are already installed on your system.
You can install all patches (as we recommend) or selectively choose patches for installation. You can also cancel selections and redisplay menus, or exit without installing any patches. For example:
130) Patch 0381.00 - Motif Toolkit Correction 131) Patch 0384.00 - Various X11 Server Corrections Choices (for example, 1 2 4-6) : Or you may choose one of the following options: 134) ALL of the above 133) CANCEL selections and redisplay menus 134) EXIT without installing any patches
Selecting CANCEL cancels your patch selections and returns to the patch
list and selection menus so you can reselect patches for installation.
Selecting
EXIT returns you to the
dupatch
installation menu.
If
dupatch
finds a problems during the preinstallation
check, it lists the specific patches that fail and asks how you want to proceed:
Select the action you'd like to take: 1) proceed with the patches that passed the check 2) select patches again 3) go back to the previous menu
If you choose to proceed with patches that passed the preinstallation
check,
dupatch
installs those patches and displays informational
messages.
The entire
dupatch
session is logged to ensure
you can view any messages that may scroll off the screen.
If patch installation is blocked due to missing or unknown system files, refer to Section 2.5.
Customer-Specific patch kit
With this type of kit you must install all patches. You can, however, remove individual CSPs after the installation process is completed and the system has been rebooted.
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:
When using the menu-based interface, you will be prompted
for actions to take.
Those prompts are the same ones you would see if you
ran the
doconfig
command.
The
dupatch
utility asks if your system has a custom configuration file and if you want
to change it.
When using
dupatch
from the command line,
the kernel is built automatically.
It does this by calling the
doconfig
-a
command.
If you specify the
dupatch
-cfgfile
command,
dupatch
calls
doconfig
with the
-a-c
options.
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:
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
Specify the kernel options you want. If you are unsure of which options to specify, consider the following:
Selecting the
All of the Above
option ensures
that you can access any new functions provided by the patch kit.
You may,
however, create a kernel that is larger than you need.
If you know of options you do not need, you can ignore those and specify all of the other options, thereby ensuring that you will have access to the new functions you need but with a smaller kernel than if you had selected all of the options.
Selecting the
None of the Above
option
will result in a kernel build that is similar to using the
doconfig
-ac
command.
This is the default.
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)3.5 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.5.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:
If you answer yes, the system reboots immediately.
If you answer no,
dupatch
returns to the
appropriate menu either installation or removal, depending on the
operation.
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:
Reboot now
Schedule a reboot for a later time
Do not reboot
The following sections describe actions for you to take after you have
completed the
dupatch
installation procedure.
3.6.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.8
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.6.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.6.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.7 Removing Patches
To remove patches from
your system, use the Patch Deletion option of the
dupatch
Main Menu.
The system must be in single-user mode to remove patches.
Note
that the
-d
option to the
setld
command
is disabled for patch subsets.
If you installed a new style patch kit, you cannot selectively remove patches; you must remove all of the patches delivered in that kit. For the old style patch kits, you can remove all or selective patches.
Caution
The Patch Deletion menu lists every
setld
-based patch on your system, regardless of which patch kit installed them. If you select theALL of the above
menu item, it will remove allsetld
-based patches from your system. Therefore, you want to remove all of the patches from a patch kit, for example Version 5.1B Patch Kit 4, but do not want to delete other installedsetld
-based patches, you will have to specify the patch ID of all of that kit's patches.See Section C.2 for an example of the patch deletion process in which only the Patch Kit 4 patches are selected for removal.
The following sections describe actions you have to take if you decided
to uninstall the patch kit.
3.7.1 Run Mandatory Script with New Style Patch Kits
If you enabled version switches as described in
Section 3.6.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:
Make sure that all phases of the patch kit installation process have been completed.
Run
/usr/sbin/versw_enable_delete
:
# /usr/sbin/versw_enable_delete
Shut down the entire cluster or the single system.
Reboot the entire cluster or the single system.
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.
Reboot the single system or each member of the cluster.
3.7.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:
If you changed your hardware configuration (for example, by adding a new disk), the system configuration that existed prior to installing the patch kit might not recognize the new devices or may not provide the necessary support for them.
If you added new cluster members, the new members will not have an older state to revert to if you attempt to uninstall the patch kit.
To uninstall the patch kit, do the following:
Remove all new hardware and new cluster members that you added after installing the patch kit.
Run
dupatch
to uninstall the patch kit.
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.7.3 Running dupatch to Remove Patches
The process for removing patches is similar to the one for installing them. Differences between the two procedures are described in the following list. :
Run
dupatch
and select
2
for patch removal:
# /patch/pk4/patch_kit/dupatch Tru64 UNIX Patch Utility (Rev. 46-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
Enter your name and any notes about the operation that you would like included in the log.
Select the patches that you want to remove:
Inclusive patch kits
With these kits you must select all of the patches in the kit. If you do not, you will receive an error message and no patches will be deleted. Refer to the Caution at the start of this section before beginning the procedure.
Patches in inclusive patch kits are identified with the letters SP and the number of the patch kit. For example, the patches in the Version 5.1B PK4 patch kit are identified as SP04.
Old style patch kits
With these kits, you can select the patches that you want to remove. If you want to remove all of the patches in a specific patch kit but leave any CSPs, ERPs, or patches from earlier kits, you will have to select each patch in the kit you want to remove. Refer to the Caution in Section 3.7 before beginning the procedure.
Rebuild the kernel. This step is the same as for the installation process. See Section 3.4 for details.
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.
Reboot the system. See Section 3.5 for details.
3.7.4 Script May Be Required 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:
Boot your system in single-user mode:
>>> boot -fl s
Run the script:
# /etc/dn_fix_dat.sh
Reboot normally.
If you also need to reverse the version switch as described in
Section 3.7.1, run the
/etc/dn_fix_dat.sh
script after step 5 in that process.