HP Tru64 UNIX Patch Kit Installation Instructions This manual provides instructions for installing and removing patches using the dddduuuuppppaaaattttcccchhhh utility, which is included with HP Tru64 UNIX and TruCluster software patch kits. It also describes baselining techniques and provides other information for working with patches. For information about individual patches, see the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s document for the kit you are installing. __________________________________________________ Hewlett-Packard Company Palo Alto, California Copyright 2003 Hewlett-Packard Development Company, L.P. UNIX(R), and The Open GroupTM are trademarks of The Open Group in the U.S. and/or other countries. All other product names mentioned herein may be trademarks of their respective owners. Proprietary computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. Contents About This Manual Audience ............................................ ix Organization ........................................ ix Patch Process Resources ............................. x Reader's Comments ................................... xi Conventions ......................................... xi 1 Introduction 1.1 Overview ...................................... 1-1 1.2 Types of Patches .............................. 1-2 1.3 Patch Kit Distribution and Naming ............. 1-2 1.3.1 Release Patch Kits ....................... 1-3 1.3.2 Customer-Specific and Early Release Patch Kits ....................................... 1-5 1.4 Patch Process Resources ....................... 1-7 1.4.1 Sites for Patching and General Information . 1-7 1.4.2 Related Documentation .................... 1-7 2 Patch Management Utility 2.1 Overview of dupatch ........................... 2-1 2.2 Log Files Created by dupatch Processes ........ 2-2 2.3 Patch Installation and Removal ................ 2-4 2.3.1 Patch Applicability ...................... 2-4 2.3.2 Patch Dependency Management .............. 2-5 2.3.3 Patch Reversibility ...................... 2-6 2.4 Viewing the Patch Documentation ............... 2-6 2.5 Viewing Patch Tracking Information ............ 2-8 2.6 Handling Manually Installed System Files with Baselining .................................... 2-15 2.6.1 Phase 1 - System Evaluation .............. 2-16 2.6.2 Phase 2 - Patch Layered Product Conflicts 2-17 2.6.3 Phase 3 - Identifying Manually Installed Patches .................................... 2-17 2.6.4 Phase 4 - Handling Missing or Unknown Files on Your System ............................. 2-17 2.6.4.1 Manually Installed Customer-Specific Patches ................................ 2-18 2.6.4.2 Manually Installed Release Patches . 2-18 2.6.4.3 User Customized Commands and Utilities .............................. 2-19 2.6.5 Phase 5 - Enabling dupatch to Overwrite Changed System Files ....................... 2-19 3 Issues and Restrictions 3.1 When Single-User Mode Is Recommended .......... 3-1 3.2 Caution on Removing Version Switched Patches .. 3-1 3.3 Impact on System Upgrades to Later Versions of Tru64 UNIX .................................... 3-1 3.4 Patching a System Prior to Creating a Cluster . 3-1 3.5 Restriction on Loading New dupatch Tools from the Command Line .............................. 3-2 3.6 No RIS or DMS Installation of Patches ......... 3-2 3.7 Direct setld Installation and Removal of Patch Subsets Is Not Allowed ........................ 3-2 iv Contents 3.8 Limitation for /var/adm/patch/backup Directory Handling ...................................... 3-3 3.9 Do Not Enter Ctrl/c During Installation Phase . 3-3 3.10 Removing Patches Containing Customized Files . 3-3 3.11 Release Patches Do Not Automatically Supersede CSPs .......................................... 3-4 4 Patch Installation and Removal Instructions 4.1 Summary of Steps for Using Patch Kits ......... 4-1 4.2 Preparing to Install Patches .................. 4-2 4.3 Making the Patch Distribution Available ....... 4-2 4.4 Loading New Patch Tools ....................... 4-3 4.5 Invoking the Main dupatch Menu ................ 4-4 4.6 Performing Patch Preinstallation Check Instructions .................................. 4-4 4.7 Setting the System Patch Baseline ............. 4-9 4.8 Installing and Enabling Patches ............... 4-11 4.8.1 Choosing Single-User or Multiuser Mode ... 4-12 4.8.1.1 Installing Patches from Single-User Mode ................................... 4-12 4.8.1.2 Installing Patches from Multiuser Mode ................................... 4-14 4.8.2 Common Installation Steps ................ 4-15 4.9 Rebuilding the Kernel ......................... 4-17 4.10 Rebooting the System ......................... 4-18 4.10.1 In Single-User Mode ..................... 4-18 4.10.2 In Multiuser Mode ....................... 4-18 4.11 Post-Installation Actions .................... 4-19 Contents v 4.12 Removing Patches ............................. 4-19 5 Rolling Upgrade 5.1 Overview ...................................... 5-1 5.1.1 Tagged Files ............................. 5-2 5.1.2 Version Switch ........................... 5-4 5.2 Rolling Upgrade Stages ........................ 5-4 5.2.1 Preparation Stage ........................ 5-5 5.2.2 Setup Stage .............................. 5-7 5.2.3 Preinstall Stage ......................... 5-8 5.2.4 Install Stage ............................ 5-9 5.2.5 Postinstallation Stage ................... 5-10 5.2.6 Roll Stage ............................... 5-10 5.2.7 Switch Stage ............................. 5-11 5.2.8 Clean Stage .............................. 5-12 5.3 Rolling Upgrade Procedure ..................... 5-12 5.4 Displaying the Status of a Rolling Upgrade .... 5-20 5.5 Installing Multiple Patch Kits ................ 5-21 5.6 Undoing a Stage ............................... 5-21 5.7 Removing Patches Installed During a Rolling Upgrade ....................................... 5-23 5.7.1 Caution on Removing Version Switched Patches .................................... 5-23 5.7.2 Steps Prior to the Switch Stage .......... 5-24 5.7.3 Steps for After the Switch Stage ......... 5-24 6 No-Roll Patching 6.1 Overview ...................................... 6-1 6.2 Steps for Running a No-Roll Procedure ......... 6-2 6.3 Throwing the Version Switch ................... 6-3 6.4 Removing Patches .............................. 6-4 vi Contents A Common Error, Warning, and Informational Messages A.1 Patch Preinstallation Check and Installation Messages ...................................... A-1 A.1.1 Patch Installation Blocked by Unknown System File ................................ A-1 A.1.2 Patch Installation Blocked by Missing System File ................................ A-2 A.1.3 Installation Blocked by Layered Product Collision .................................. A-3 A.1.4 Patch Installation Blocked by Dependencies on Other Patches ........................... A-4 A.1.5 Patch Installation Blocked by Missing Product Subset ............................. A-5 A.1.6 Patch Installation Blocked by Disk Space . A-6 A.1.7 Patch Installation Blocked by Installed Patch or Subset ............................ A-6 A.1.8 Patch Installation Blocked by an Existing CSP ........................................ A-7 A.1.9 The dupatch Tools Are Outdated ........... A-8 A.1.10 Some Patches Must Be Made Reversible .... A-8 A.2 Patch Removal Messages ........................ A-9 A.2.1 Patch Removal Blocked by Missing Patch Backup Files ............................... A-9 A.2.2 Patch Removal Blocked by Dependencies on Other Patches .............................. A-10 A.2.3 No Original Files Restored When Patch Is Removed .................................... A-10 A.3 TruCluster Specific dupatch Messages .......... A-11 A.3.1 System Not Adequately Prepared ........... A-11 A.3.2 Rolling Upgrade in Progress (Installation) . A-11 A.3.3 Rolling Upgrade in Progress (Baselining) . A-12 A.3.3.1 Version 5.0 Wave 4 Cluster is Unsupported ............................ A-12 A.3.4 Patch Removal Fails Because Needed File Is Unavailable ................................ A-12 A.3.5 Patch Removal Fails Because of a Version Switch ..................................... A-13 A.3.6 dupatch Cannot Create Needed File ........ A-13 A.3.7 Insufficient Free Space (File System Full) . A-14 Contents vii B Sample Patch-Kit Installations B.1 Typical Patch Kit Installation ................ B-1 B.2 TruCluster Patch Installation in Rolling Upgrade..B-12 B.3 Gathering Baseline Information ................ B-29 B.4 Removing Patches .............................. B-34 B.5 Installing and Removing CSPs and ERPs ......... B-40 C Using dupatch from the Command Line Glossary viii Contents About This Manual This manual provides instructions for installing and removing patches that are provided by Hewlett-Packard Company in its Tru64 UNIX and TruCluster software products patch kits. It also describes baselining techniques and provides other information for working with patches. The information applies to Release Patch Kits, Customer-Specific Patch Kits (CSPs), and Early Release Patch Kits (ERPs) installed on Versions 4.0F and higher. The differences in dealing with the different product versions and patch-kit types are minimal; this manual alerts you to those differences during process discussions and step-by-step instructions. For information about individual patches, see the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s document for the kit you are installing. _A_u_d_i_e_n_c_e This manual is for those who install and remove patch kits and manage patches after they are installed. _O_r_g_a_n_i_z_a_t_i_o_n The first two chapters describe the concepts of the patching process and provide an overview of the patch management utility, dddduuuuppppaaaattttcccchhhh. Chapter 3 lists issues and restrictions you should be aware of before you begin to work with the patch kits following the step-by-step procedures in Chapter 4. This manual is organized as follows: ______________________________________________________________________________ Chapter 1 Provides an overview of the concepts and features of the patch kits. Chapter 2 Introduces the dddduuuuppppaaaattttcccchhhh utility and describes its features. Chapter 3 Provides information you must be aware of when installing and removing patches. Chapter 4 Describes the procedures for installing and removing patches. Chapter 5 Describes the rolling upgrade process for patching a system running TruCluster Server Version 5.0A or higher while the cluster is in operation. This process is also used for upgrading to a new version of the TruCluster software software or for doing an upgrade and a patch together. Chapter 6 Describes the no-roll patch process, which provides a way to apply patches to a cluster quickly in order to minimize downtime and reduce the number of reboots required. Appendix A Describes error messages you might see while installing, removing, or maintaining patches. Appendix B Provides examples of a typical patch installation, a TruCluster software patch installation in a rolling upgrade, a baselining process, and a patch removal process. Appendix C Provides information about using the dddduuuuppppaaaattttcccchhhh command-line interface and documents the dddduuuuppppaaaattttcccchhhh(8) reference page. ______________________________________________________________________________ _P_a_t_c_h _P_r_o_c_e_s_s _R_e_s_o_u_r_c_e_s We provide Web sites to help you with the patching process: +o To obtain the latest patch kit for your operating system and cluster: hhhhttttttttpppp::::////////ffffttttpppp1111....ssssuuuuppppppppoooorrrrtttt....ccccoooommmmppppaaaaqqqq....ccccoooommmm////ppppuuuubbbblllliiiicccc////uuuunnnniiiixxxx//// +o To view or print the latest version of the _P_a_t_c_h _K_i_t _I_n_s_t_a_l_l_a_t_i_o_n _I_n_s_t_r_u_c_t_i_o_n_s or the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s for a specific patch kit: hhhhttttttttpppp::::////////hhhh33330000000099997777....wwwwwwwwwwww3333....hhhhpppp....ccccoooommmm////ddddooooccccssss////ppppaaaattttcccchhhh////iiiinnnnddddeeeexxxx....hhhhttttmmmmllll +o To visit our main support page: hhhhttttttttpppp::::////////hhhh77771111000022225555....wwwwwwwwwwww7777....hhhhpppp....ccccoooommmm////ssssuuuuppppppppoooorrrrtttt////hhhhoooommmmeeee////iiiinnnnddddeeeexxxx....aaaasssspppp +o To visit the Tru64 UNIX homepage: hhhhttttttttpppp::::////////hhhh33330000000099997777....wwwwwwwwwwww3333....hhhhpppp....ccccoooommmm//// x About This Manual _R_e_a_d_e_r'_s _C_o_m_m_e_n_t_s We welcome any comments and suggestions you have on this and other Tru64 UNIX manuals. You can send your comments in the following ways: +o Fax: 603-884-0120 Attn: HCTO Information Development, ZK03-3/Y32 +o Internet electronic mail: rrrreeeeaaaaddddeeeerrrrssss____ccccoooommmmmmmmeeeennnntttt@@@@zzzzkkkk3333....ddddeeeecccc....ccccoooommmm A Reader's Comment form is located on your system in the following location: ////uuuussssrrrr////ddddoooocccc////rrrreeeeaaaaddddeeeerrrrssss____ccccoooommmmmmmmeeeennnntttt....ttttxxxxtttt +o Mail: Hewlett-Packard Company HCTO Information Development Manager ZK03-3/Y32 110 Spit Brook Road Nashua, NH 03062-9987 Please include the following information along with your comments: +o The full title of this document. +o The section numbers and page numbers of the information on which you are commenting. +o The version of Tru64 UNIX that you are using. +o If known, the type of processor that is running the Tru64 UNIX software. The Tru64 UNIX Publications group cannot respond to system problems or technical support inquiries. Please address technical questions to your local system vendor or to the appropriate technical support office. Information provided with the software media explains how to send problem reports. _C_o_n_v_e_n_t_i_o_n_s This guide uses the following conventions: _f_i_l_e Italic (slanted) type indicates variable values, placeholders, and function argument names. About This Manual xi [[[[CCCCttttrrrrllll////_x] This symbol indicates that you hold down the first named key while pressing the key or mouse button that follows the slash. In examples, this key combination is enclosed in a box (for example, [[[[CCCCttttrrrrllll////CCCC]]]] ). %%%% ccccaaaatttt Boldface type in interactive examples indicates typed user input. device names Operating system versions before Version 5.0 use different names than those of Version 5.0 and higher. In general, this manual uses the Version 5.0 names. For example, where a partition name is represented by ////ddddeeeevvvv////ddddiiiisssskkkk////ddddsssskkkk3333gggg, the Version 4.0n name might be ////ddddeeeevvvv////rrrrzzzz3333gggg.... 000 This symbol is used in output examples to replace redundant information. This is information you would see on your terminal screen or in a log file created by dddduuuuppppaaaattttcccchhhh, but is not particularly useful in the examples in this manual. Glossary Terms In the online version of this document, various terms are linked to the Glossary. By clicking on the term, you will be taken to its definition. You can easily return to the place you were reading by clicking on your browser's Back button. xii About This Manual Introduction 1 This chapter provides an overview of the concepts and features of the patch kits for the Tru64 UNIX operating system and TruCluster software products. _1._1 _O_v_e_r_v_i_e_w A patch is a collection of files that contain fixes to problems. When possible, patches are merged together, into one patch, if they have intersecting files or codependencies. A patch may correct more than one problem. The Tru64 UNIX and TruCluster software patch kits contain patches for critical problems for those software products. These kits, which are distributed as needed, provide interim maintenance that prevents the occurrence of known critical problems. The patch kits contain the following elements: +o Version-specific patches and patch-specific documentation +o The dddduuuuppppaaaattttcccchhhh patch-management utility, which you use to install, view, remove, and manage patches Patch kits are not intended to provide general maintenance and new functions; applying them to your system does not eliminate the need to upgrade to later versions of Tru64 UNIX and TruCluster software. Patches are applicable to a specific version of the software products, unless stated otherwise in the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s. You cannot install version-specific kits on other software versions. HP recommends that you install all of the patches included in the kits and that you update the TruCluster software products (if applicable) at the same time you update your operating system. To install Tru64 UNIX and TruCluster software patches, your system must meet the following requirements: +o Be running the appropriate version of Tru64 UNIX and TruCluster software +o Contain the necessary temporary and permanent storage space described in the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s document for the kit you are installing After you install the patches, the following items are left on the system: +o The dddduuuuppppaaaattttcccchhhh utility +o Patch-specific documentation that you can view with dddduuuuppppaaaattttcccchhhh +o Optionally, the archived system files that were updated by the installed patches _1._2 _T_y_p_e_s _o_f _P_a_t_c_h_e_s HP distributes three kinds of patches for its Tru64 UNIX and TruCluster software products — Release Patch Kits, Customer-Specific Patch Kits, and Early Release Patch Kits: +o Release Patches Release patches provide interim maintenance that prevents the occurrence of known critical problems. Release patches (sometimes referred to as official patches) are provided in kits grouped by software product versions. They are available from the Internet and on a CD-ROM you can order from HP. +o Customer-Specific Patches (CSPs) CSPs are provided in response to Tru64 UNIX and TruCluster software problems on specific hardware and software configurations. They are provided directly from your service provider. +o Early Release Patches (ERPs) ERPs provide one or more patches that will be incorporated into the next Release Patch Kit. They may be provided by your service provider or made available on the Internet. ERPs are a type of Customer-Specific Patch Kit. Most of the information about CSPs in this manual also pertains to ERPs. _1._3 _P_a_t_c_h _K_i_t _D_i_s_t_r_i_b_u_t_i_o_n _a_n_d _N_a_m_i_n_g Tru64 UNIX patches for specific operating system and TruCluster software releases and Customer-Specific patches are packaged together in tar files. Each patch kit contains the following components: +o Patch management utility (dddduuuuppppaaaattttcccchhhh) and other patch management tools Installs, removes, and manages patches for Tru64 UNIX and TruCluster software. This utility is installed and left on the system through the successful installation of a patch kit. 1-2 Introduction +o Patch subsets for the operating system and TruCluster software products +o Documentation Packaged with Release Patch Kits is a document called _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s, which summarizes the problems that the patches in that kit correct and provides any information you may need to know about specific patches. The information in this document also exists in separate files that you can access using the dddduuuuppppaaaattttcccchhhh utility. (See Section 2.4.) Release Patch Kits also contain the _I_n_s_t_a_l_l_a_t_i_o_n _I_n_s_t_r_u_c_t_i_o_n_s (the manual you are reading), which is common to all patch kits. Both of these manuals are provided in PDF and HTML formats. The PDF version is easy to view and print using Adobe Acrobat Reader, which is provided on the Tru64 UNIX Documentation CD-ROM, and is also available at the Adobe Web site (hhhhttttttttpppp::::////////wwwwwwwwwwww....aaaaddddoooobbbbeeee....ccccoooommmm////). The HTML version is viewed with your Internet browser, such as Netscape. Beginning with kits shipped after March 2001, the dddduuuuppppaaaattttcccchhhh(8) reference page is installed with the patch tools. Once installed, you can view the reference page by using the mmmmaaaannnn command. The contents of the tar file varies, depending on the type of kit. For example, a CSP kit might contain patches for several operating system versions, while Release Patch Kits always contain patches for only one operating system version. Also, the tar file may or may not contain TruCluster software patches. However, the structure of the tar file is the same for each type of kit. Figure 1-1 illustrates the contents of a patch tar file. _F_i_g_u_r_e _1-_1: _S_t_r_u_c_t_u_r_e _o_f _a _P_a_t_c_h _K_i_t _T_a_r _F_i_l_e The following sections describe Release and Customer-Specific Patch Kits. _1._3._1 _R_e_l_e_a_s_e _P_a_t_c_h _K_i_t_s Tru64 UNIX and TruCluster software Release Patch Kits are available from the Internet and on CD-ROM. +o Patch Kits on the Internet Patch kits are available publicly on the Internet through the HP Services Web page located at: hhhhttttttttpppp::::////////wwwwwwwwwwww....ssssuuuuppppppppoooorrrrtttt....ccccoooommmmppppaaaaqqqq....ccccoooommmm////ppppaaaattttcccchhhheeeessss//// Release patches distributed over the Internet are provided in a tar file that you must unpack on your system or on an NFS-mountable file system. The tar file for each operating system version will contain patch kits for that version of the operating system and patch kits for the applicable Introduction 1-3 TruCluster software products. +o Patch kits on CD-ROM The Tru64 UNIX Patch CD-ROM contains all of the latest patch kits for the supported versions of Tru64 UNIX and TruCluster software. The patch kits on the CD-ROM are provided in an expanded form (rather than a tar file) so they can be installed directly from the disk. The _0_0-_R_E_A_D-_M_E-_F_I_R_S_T file on the CD-ROM lists the contents of the disk and provides other information. You can order a Patch CD-ROM in the United States by calling 1-800-344- 4825; customers in other countries should contact your local HP sales office or authorized reseller for pricing and availability. Release patch kit names have the following syntax: OOOOSSSS PPPPrrrroooodddduuuucccctttt||||VVVVeeeerrrrssssiiiioooonnnn||||BBBBaaaasssseeeeLLLLeeeevvvveeeellll||||KKKKiiiittttTTTTyyyyppppeeee||||KKKKiiiitttt####||||----MMMMffffggggDDDDaaaatttteeee For example, a file named TTTT66664444VVVV55551111BBBB11118888AAAASSSS0000000000003333----22220000000011111111000022220000....ttttaaaarrrr contains Patch Kit 0003, built in base level 18 for Tru64 UNIX Version 5.1 and TruCluster software Version 5.1, and manufactured on October 20, 2001. The following list describes the attributes currently used in patch kit names: OOOOSSSS PPPPrrrroooodddduuuucccctttt T64 = Tru64 UNIX DU = DIGITAL UNIX VVVVeeeerrrrssssiiiioooonnnn OOOOppppeeeerrrraaaattttiiiinnnngggg SSSSyyyysssstttteeeemmmm VVVVeeeerrrrssssiiiioooonnnn V51B V51A V51 V50A V50 V40G V40F V40E V40D BBBBaaaasssseeeeLLLLeeeevvvveeeellll The support pool in which the kit was built. This formerly internal number 1-4 Introduction has become a common way of identifying kits. KKKKiiiittttTTTTyyyyppppeeee AS = Aggregate Selective installation patch kit SS = A patch kit containing a single patch KKKKiiiitttt#### The numeric identifier that HP uses to track the kit contents ----MMMMffffggggDDDDaaaatttteeee The year, month, and day the kit was built in the form of YYYYMMDD _1._3._2 _C_u_s_t_o_m_e_r-_S_p_e_c_i_f_i_c _a_n_d _E_a_r_l_y _R_e_l_e_a_s_e _P_a_t_c_h _K_i_t_s Customer-Specific Patch Kits provide interim patches for a specific customer's problem and computing environment. Early Release Patch Kits, which provide one or more patches that will be incorporated into a future Release Patch Kit, are a type of Customer-Specific Patch Kit. Most of the information about CSPs in this manual also pertains to ERPs. ESP and ERP kits have names similar to the following: TTTT66664444KKKKIIIITTTT0000000011113333888822225555----VVVV55551111BBBB22222222----EEEESSSS----22220000000033330000777700008888....ttttaaaarrrr This tar file contains an an early release patch for Tru64 UNIX Version 5.1B, built in base level 22, with a patch identification of KIT0013825, and built on July 8, 2003. The following list describes the attributes currently used in these patch kit names: PPPPrrrroooodddduuuucccctttt T64 = Tru64 UNIX TCR = TruCluster DUX = DIGITAL UNIX (the name of the operating system prior to the Version 4.0F release) KKKKiiiitttt IIIIddddeeeennnnttttiiiiffffccccaaaattttiiiioooonnnn NNNNuuuummmmbbbbeeeerrrr A seven-digit number. OOOOppppeeeerrrraaaattttiiiinnnngggg SSSSyyyysssstttteeeemmmm VVVVeeeerrrrssssiiiioooonnnn Introduction 1-5 V51B V51A V51 V50A V50 V40G V40F V40E V40D BBBBaaaasssseeee LLLLeeeevvvveeeellll The Release patch base level the Customer-Specific patch is built against, for example, 22. This field is used by the service provider. KKKKiiiitttt TTTTyyyyppppeeee E = Early Release PPPPaaaattttcccchhhhIIIIDDDD The numeric identifier used to track patches that are relative to the product version patch kit. Patch identifiers have the following format: MMMMaaaajjjjoooorrrrIIIIDDDD Five numeric digits, for example 00223. MMMMiiiinnnnoooorrrrIIIIDDDD Two numeric digits, for example, 00. ----UUUUnnnniiiiqqqquuuueeeeIIIIDDDD A unique kitting ID for the patch, for example, 1875. ----OOOOppppttttiiiioooonnnnaaaallllFFFFiiiieeeelllldddd A field that provides information about the type of patch and its installation method. TTTTyyyyppppeeee:::: E = Early release S = Security 1-6 Introduction M = Manual installation VVVVaaaalllliiiidddd OOOOppppttttiiiioooonnnnaaaallll FFFFiiiieeeelllldddd ccccoooommmmbbbbiiiinnnnaaaattttiiiioooonnnnssss:::: E = Early release patch — dupatch installation EM = Early release patch — Manual installation ES = Early release patch — Security EMS = Early release patch — Manual installation — Security M = Manually installed CSP ----MMMMffffggggDDDDaaaatttteeee The year, month, and day the kit was built, in the form of YYYYMMDD. _1._4 _P_a_t_c_h _P_r_o_c_e_s_s _R_e_s_o_u_r_c_e_s HP provides Web sites to help you with the patching process. The following sections provide pointers to general information and additional documents you can use. _1._4._1 _S_i_t_e_s _f_o_r _P_a_t_c_h_i_n_g _a_n_d _G_e_n_e_r_a_l _I_n_f_o_r_m_a_t_i_o_n +o To obtain a listing of the kit number, base level, and month of release for current and previous Release Patch Kits see the Patch Kit Roadmap: hhhhttttttttpppp::::////////wwwwwwwwwwww....ttttrrrruuuu66664444uuuunnnniiiixxxx....ccccoooommmmppppaaaaqqqq....ccccoooommmm////ddddooooccccssss////ppppaaaattttcccchhhh////rrrrooooaaaaddddmmmmaaaapppp....hhhhttttmmmmllll +o To obtain the latest patch kit for your operating system and cluster go to: hhhhttttttttpppp::::////////ffffttttpppp1111....ssssuuuuppppppppoooorrrrtttt....ccccoooommmmppppaaaaqqqq....ccccoooommmm////ppppuuuubbbblllliiiicccc////uuuunnnniiiixxxx//// +o To visit the support homepage page go to: hhhhttttttttpppp::::////////wwwwwwwwssssssss1111pppprrrroooo....ccccoooommmmppppaaaaqqqq....ccccoooommmm////ssssuuuuppppppppoooorrrrtttt////hhhhoooommmmeeee////iiiinnnnddddeeeexxxx....aaaasssspppp +o To visit the Tru64 UNIX homepage go to: hhhhttttttttpppp::::////////wwwwwwwwwwww....ttttrrrruuuu66664444uuuunnnniiiixxxx....ccccoooommmmppppaaaaqqqq....ccccoooommmm//// _1._4._2 _R_e_l_a_t_e_d _D_o_c_u_m_e_n_t_a_t_i_o_n The following documentation can help you work with patch kits: Introduction 1-7 +o _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s Included in each Release Patch Kit, this document lists the changes made by the patches and provides information you should know before and after installing specific patches. The _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s for current and previously released Release Patch Kits are available on the Web. +o Best Practice for Patching Tru64 UNIX Describes issues to consider before beginning to install a Tru64 UNIX Release Patch Kit and steps to take to prepare a system for the installation process. +o The dddduuuuppppaaaattttcccchhhh(8) reference page, which is installed on you system when you install the patch tools +o The Tru64 UNIX _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e and _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n manuals +o Tru64 UNIX manual +o TruCluster _C_l_u_s_t_e_r _I_n_s_t_a_l_l_a_t_i_o_n and _C_l_u_s_t_e_r _A_d_m_i_n_i_s_t_r_a_t_i_o_n manuals +o Any release-specific documentation, specifically the _R_e_l_e_a_s_e _N_o_t_e_s for the version you are patching You can find the patch-specific documentation at the following Web site: hhhhttttttttpppp::::////////wwwwwwwwwwww....ttttrrrruuuu66664444uuuunnnniiiixxxx....ccccoooommmmppppaaaaqqqq....ccccoooommmm////ddddooooccccssss////ppppaaaattttcccchhhh//// You can find Tru64 UNIX and TruCluster software documentation at the following Web site: hhhhttttttttpppp::::////////wwwwwwwwwwww....ttttrrrruuuu66664444uuuunnnniiiixxxx....ccccoooommmmppppaaaaqqqq....ccccoooommmm////ddddooooccccssss 1-8 Introduction Patch Management Utility 2 This chapter introduces you to the dddduuuuppppaaaattttcccchhhh utility for installing, removing, and managing patches. It also provides information you must be aware of when installing patches. See Chapter 4 for instructions on installing and removing patches from the Tru64 UNIX operating system and the TruCluster software products. _2._1 _O_v_e_r_v_i_e_w _o_f _d_u_p_a_t_c_h All Tru64 UNIX and TruCluster software patches are installed, removed, and managed using the sssseeeettttlllldddd-based dddduuuuppppaaaattttcccchhhh utility, which provides you with menus that step you though the various tasks. For clustered systems running TruCluster Server Version 5.0A or higher, dddduuuuppppaaaattttcccchhhh is run in conjunction with the rolling upgrade procedure described in Chapter 5. The dddduuuuppppaaaattttcccchhhh utility also provides a command-line interface from which you can specify options to invoke all functions, except for baselining. The functions have the same operation and definition as the menu-driven interface. For information about using the command-line interface, see Appendix C and the dddduuuuppppaaaattttcccchhhh(8) reference page. With dddduuuuppppaaaattttcccchhhh, you can perform the following actions: +o Install and remove all or selected patches. +o View the patch-specific documentation. +o View patch tracking and management information. +o Establish a baseline for systems that had manually installed system files placed on them. Directions for enabling or disabling patches are provided after the successful installation or removal of all selected patches (for example, kernel rebuild and system reboot). The dddduuuuppppaaaattttcccchhhh utility also manages the system inventory for Tru64 UNIX and TruCluster software patches. This enables patch tracking and management of patch activity such as: +o Tracking current dddduuuuppppaaaattttcccchhhh-installed patches. +o Ensuring correct handling of customized system configuration files so that customizations are not lost (for example, ccccoooonnnnffff....cccc). These files are also referred to as system-protected files (....nnnneeeewwww........). +o Validating patch applicability to existing system files (collision detection). Because dddduuuuppppaaaattttcccchhhh manages patch interdependencies, direct sssseeeettttlllldddd installations and deinstallations (sssseeeettttlllldddd -l -d) are disabled. _2._2 _L_o_g _F_i_l_e_s _C_r_e_a_t_e_d _b_y _d_u_p_a_t_c_h _P_r_o_c_e_s_s_e_s The dddduuuuppppaaaattttcccchhhh utility captures patching activities in the following log files: +o ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////sssseeeessssssssiiiioooonnnn....lllloooogggg Every time you run dddduuuuppppaaaattttcccchhhh it creates a session log that captures dddduuuuppppaaaattttcccchhhh activities. The sssseeeessssssssiiiioooonnnn....lllloooogggg files from the previous 25 sessions are saved. The order is first in, first out, with sssseeeessssssssiiiioooonnnn....lllloooogggg....22225555 as the oldest file. +o ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////DDDDuuuuppppaaaattttcccchhhh____llllooooaaaadddd_____D_a_t_e.log When you run dddduuuuppppaaaattttcccchhhh from the newly untarred kit or from the mounted Tru64 UNIX Patch CD-ROM, dddduuuuppppaaaattttcccchhhh determines if the patch distribution contains new patch tools, and loads them if necessary. This log file has a name similar to this: DDDDuuuuppppaaaattttcccchhhh____llllooooaaaadddd____2222000000000000JJJJuuuullll1111::::11115555::::44443333::::33335555....lllloooogggg +o ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////bbbbaaaasssseeeelllliiiinnnneeee....lllloooogggg When you run the system baselining feature, dddduuuuppppaaaattttcccchhhh creates a baseline log. The sssseeeessssssssiiiioooonnnn....lllloooogggg files from the previous 25 sessions are saved. The order is first in, first out, with bbbbaaaasssseeeelllliiiinnnneeee....lllloooogggg....22225555 as the oldest file. +o ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////eeeevvvveeeennnntttt....lllloooogggg When patches are installed or removed, an event log captures that information. Only one copy of the file is updated each time patches are installed or removed. The information in the patch event log is not 2-2 Patch Management Utility available through the dddduuuuppppaaaattttcccchhhh user interface, but the log is a text file that you can view with a command such as mmmmoooorrrreeee. The following list describes the types of information an event log provides, although the format and content are subject to change. Example 2-1 shows a typical event log. ______________________________________________________________________________ DUPATCH_REV> The revision of dddduuuuppppaaaattttcccchhhh being used TYPE> The type of action that was taken; either install or remove NAME> The name entered by the user through a dddduuuuppppaaaattttcccchhhh query USER> The name of the user performing the action NOTES> Notes that were entered by the user through a dddduuuuppppaaaattttcccchhhh query KITLOC> The directory from which the patch kit was installed KITNAME> The name of the patch kit that was installed REVERT> The choice made on whether or not the patch installation is reversible BACKUP_DIRECTORY> A pointer to the directory that contains the original files before they were patched BACKUP_SETUP> A plain directory; not a mount point or a symbolic link SUCCEED> A list of patches for which the action succeeded FAIL> A list of patches for which the action failed ______________________________________________________________________________ _E_x_a_m_p_l_e _2-_1: _S_a_m_p_l_e _E_v_e_n_t _L_o_g DUPATCH_REV>30-01 TYPE>install NAME>mstone USER>mstone DATE>Mon Jul 3 13:03:33 EST 2000 NOTES>Install BL13 patches from CD-ROM > KITLOC>/cdrom/DIGITAL_UNIX_V4.0F/patch_kit/DIGITAL_UNIX_V4.0F/kit KITNAME> OSF440 Patch Management Utility 2-3 REVERT>Y BACKUP_DIRECTORY>//var/adm/patch/backup BACKUP_SETUP> SUCCEED>OSFPAT00001900440 _2._3 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _R_e_m_o_v_a_l When installing and removing patches, dddduuuuppppaaaattttcccchhhh manages the following: +o The applicability of patches +o Patch dependencies +o Patch reversibility +o System inventory changes for patches _2._3._1 _P_a_t_c_h _A_p_p_l_i_c_a_b_i_l_i_t_y Patch applicability to the existing system files is done on a file-by-file basis for each patch. This ensures that the installation of a patch will not degrade or crash the system. The installation of a patch is blocked if any system files to be replaced by a patch are not valid predecessors of the patch files. Patch applicability also enables consistency checking and reporting for the installation of Tru64 UNIX and TruCluster software patches. In all cases where a patch is blocked, informative messages are provided to assist you in determining how to proceed. Appendix A lists common error messages and suggested corrective actions. The installation of a patch is blocked if any of the following conditions exist: +o The underlying software product subset is not installed; for example, if the applicable Tru64 UNIX or TruCluster software release subset is not installed. +o The sssseeeettttlllldddd inventory is inconsistent with the existing system files. This occurs when an operating system or TruCluster software sssseeeettttlllldddd subset is installed and individual operating system files that are part of that subset are moved, deleted, or replaced. 2-4 Patch Management Utility +o If any of the existing system files (files that are targeted to be updated by a patch) have changed and cannot be related to previous versions of the patch. This ensures that operating system files that change due to other explicit system administrator action (for example, layered product patches or non-dddduuuuppppaaaattttcccchhhh installed CSP installations) are not inadvertently overwritten. You must take special action, through the baseline feature, to enable patch installation in this situation. _2._3._2 _P_a_t_c_h _D_e_p_e_n_d_e_n_c_y _M_a_n_a_g_e_m_e_n_t Selective patch installation and removal is allowed in the Tru64 UNIX and TruCluster software patch kits. When patches are selectively chosen, dddduuuuppppaaaattttcccchhhh provides warning messages regarding other dependent patches requiring installation or removal for correct system operation. The dddduuuuppppaaaattttcccchhhh utility manages the dependencies between patches within each product patch kit and across product patch kits. For example, dddduuuuppppaaaattttcccchhhh manages the following kinds of dependencies when patches on systems where both Tru64 UNIX Version 4.0F and TruCluster software Version 1.6 are installed or removed: +o Patch dependencies within a product patch kit If, for example, you choose to install Tru64 UNIX 4.0F Patch 1.00 and it depends upon Tru64 UNIX 4.0F Patch 5.00, which is not already installed or chosen for installation, the dddduuuuppppaaaattttcccchhhh preinstallation check will warn you of the dependency and prevent the installation of Tru64 UNIX 4.0F Patch 1.00. If the patch selections are reversed, dddduuuuppppaaaattttcccchhhh will warn you and prevent installation of the chosen patch. +o Patch dependencies across product patch kits If, for example, you choose to install Tru64 UNIX 4.0F Patch 1.00 and it depends upon TruCluster 1.6 Patch 17.00, which is not already installed or chosen for installation, the dddduuuuppppaaaattttcccchhhh preinstallation check will warn you of the dependency and prevent the installation of the Tru64 UNIX 4.0F Patch 1.00. If the patch selections are reversed, dddduuuuppppaaaattttcccchhhh will warn you and prevent installation of the chosen patch. _N_o_t_e Even though selective patch installation capabilities exist, HP recommends that you install all patches in each kit for Tru64 UNIX and TruCluster software to prevent the occurrence of known and corrected software problems. Patch Management Utility 2-5 _2._3._3 _P_a_t_c_h _R_e_v_e_r_s_i_b_i_l_i_t_y Enabling patch reversibility during patch installation allows you to revert the system to its state prior to the installation of a particular patch. By default, the reversibility installation option is set to enable reversibility for patches. If you choose to make patch subsets nonreversible, then those patches will become nonremovable upon the successful installation of those patches. _N_o_t_e Customer-Specific patches are forced to be reversible when the CSP kit is manufactured. This forced reversibility overrides the reversibility option provided by dddduuuuppppaaaattttcccchhhh during installation. Patch reversibility is dependent upon saving the existing system files that will be updated by the patch. Saving these files requires the availability of adequate storage space in ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp, which can be a mount point for a separate disk partition, an NFS mount point, or a symbolic link to another file system. This allows you to configure your system to reduce the impact on system disk space for the ////, ////uuuussssrrrr, and ////vvvvaaaarrrr partitions. To further reduce the storage space required to save existing system files, the patch kits for Tru64 UNIX and TruCluster software use the ggggzzzziiiipppp utility to save each patch file in a compressed tar image. This results in a file with a name like _f_i_l_e_n_a_m_e....ttttaaaarrrr....ggggzzzz. The dddduuuuppppaaaattttcccchhhh utility checks for the required storage space prior to patch installation. Patch installation is prevented if adequate backup space is unavailable. _2._4 _V_i_e_w_i_n_g _t_h_e _P_a_t_c_h _D_o_c_u_m_e_n_t_a_t_i_o_n When you select the Patch Documentation item of the main menu, dddduuuuppppaaaattttcccchhhh returns a menu that gives you access to different information: +o Problem summaries Provide brief descriptions of the problems corrected by the patches. You can view the problems corrected by installed patches or by patches available from a specific kit. +o Full descriptions Provide complete descriptions of the problems corrected by the individual patches. You can view the problem descriptions for installed patches or for patches available from a specific kit. +o Special Instructions These files describe special instructions you need to be aware of for 2-6 Patch Management Utility individual patches. You can view the instructions for installed patches or for patches available from a specific kit. +o Report identifiers +o Revision control strings The following output shows the Patch Documentation menu and a typical session: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Documentation Menu: ------------------------ Installed patches on the system 1) View problem summaries 2) View full descriptions 3) View special instructions 4) View Problem Report Identifiers 5) View Revision Control Strings Patches in the patch kit 6) View problem summaries 7) View full descriptions 8) View special instructions 9) View Problem Report Identifiers 10) View Revision Control Strings All (installed and non-installed) patches 11) View patch problem summaries 12) View patch full descriptions 13) View patch special instructions 14) View Problem Report Identifiers 15) View Revision Control Strings b) Back to Main Menu q) Quit Enter your choice: 6666 Patch Documentation Selection Menu: ----------------------------------- 1) List Release problem summaries 2) List Customer Specific problem summaries 3) List All problem summaries b) Back to Documentation Menu q) Quit Enter your choice: 1111 Enter path to the top of the patch distribution, Patch Management Utility 2-7 or enter "q" to get back to the menu [/mnt/PatchKit/kit2/patch_kit]: [[[[RRRReeeettttuuuurrrrnnnn]]]] 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 examined. - Tru64_UNIX_V5.0A / Cluster Kernel Patches: 1) Patch 00090.00 - versw command can core dump during rolling upgrade 2) Patch 00186.00 - Disks can become inaccessible on a cluster node - Tru64_UNIX_V5.0A / Commands, Shells, & Utilities Patches: 3) Patch 00015.00 - Fixes a problem that occurs in multibyte locales 4) Patch 00019 000 The patch description information and special instructions are conveniently organized in the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s document that is packaged with each kit. _2._5 _V_i_e_w_i_n_g _P_a_t_c_h _T_r_a_c_k_i_n_g _I_n_f_o_r_m_a_t_i_o_n The dddduuuuppppaaaattttcccchhhh utility allows you to view the following patch installation and removal information: _L_i_s_t _o_f _d_u_p_a_t_c_h-_i_n_s_t_a_l_l_e_d _p_a_t_c_h_e_s _o_n _t_h_e _s_y_s_t_e_m The following sample log shows how you can list the installed dddduuuuppppaaaattttcccchhhh-based Customer-Specific patches: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Tracking Menu: ------------------- 1) List installed patches 2) List installed patch files 3) List patch kit information for installed patches 4) Show Patch History for selected patches 5) Show System Patch History b) Back to Main Menu q) Quit Enter your choice: 1111 Patch Tracking Selection Menu: ------------------------------ 1) List Release Patches 2) List Customer Specific Patches 3) List All Patches b) Back to Tracking Menu 2-8 Patch Management Utility q) Quit Enter your choice: 2222 Gathering details of relevant patches, this may take a bit of time Patches installed on the system: ------------------------------- (depending upon the number of patches you installed, this may take a while) - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch C 00045.00 - Fix for QAR 61365 - DIGITAL_UNIX_V4.0F / Security Related Patches: Patch C 00043.00 - Fix for SSRT0585U Patch C 00052.00 - Fix for SSRT0585U - DIGITAL_UNIX_V4.0F / X11 Patches: Patch C 00044.00 - Fix for QAR 57198 Press RETURN to get back to the Patch Tracking Menu... _L_i_s_t _o_f _p_a_t_c_h_e_d _f_i_l_e_s _o_n _t_h_e _s_y_s_t_e_m The following sample log shows how you can list the installed patch files for Customer-Specific patches: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Tracking Menu: ------------------- 1) List installed patches 2) List installed patch files 3) List patch kit information for installed patches 4) Show Patch History for selected patches 5) Show System Patch History b) Back to Main Menu q) Quit Enter your choice: 2222 Patch Tracking Selection Menu: ------------------------------ 1) List Release Files 2) List Customer Specific Files Patch Management Utility 2-9 3) List All Files b) Back to Tracking Menu q) Quit Enter your choice: 2222 Gathering details of relevant patches, this may take a bit of time The list of all patched files on your system: -------------------------------------------- (depending upon the number of patches you installed, this may take a while) \&./usr/bin/X11/dxpause (DIGITAL_UNIX_V4.0F Patch C 00044.00) \&./usr/dt/bin/dtappintegrate (DIGITAL_UNIX_V4.0F Patch C 00043.00) \&./usr/dt/bin/dtappintegrate (DIGITAL_UNIX_V4.0F Patch C 00052.00) \&./usr/sbin/quotaoff (DIGITAL_UNIX_V4.0F Patch C 00045.00) \&./usr/sbin/quotaon (DIGITAL_UNIX_V4.0F Patch C 00045.00) Press RETURN to get back to the Patch Tracking Menu... _L_i_s_t _o_f _p_a_t_c_h _k_i_t _i_n_f_o_r_m_a_t_i_o_n _o_n _i_n_s_t_a_l_l_e_d _p_a_t_c_h_e_s The following sample log shows how you can list the patch kits for the installed patches on your system: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Tracking Menu: ------------------- 1) List installed patches 2) List installed patch files 3) List patch kit information for installed patches 4) Show Patch History for selected patches 5) Show System Patch History b) Back to Main Menu q) Quit Enter your choice: 3333 Patch Tracking Selection Menu: ------------------------------ 1) List Release kit information 2) List Customer Specific kit information 3) List All kit information 2-10 Patch Management Utility b) Back to Tracking Menu q) Quit Enter your choice: 3 Gathering details of relevant patches, this may take a bit of time Patches installed on the system came from following patch kits: -------------------------------------------------------------- - DUV40F1-C0004300-1367-20011104 OSF440 - DUV40F1-C0004400-1372-20011105 OSF440 - DUV40F1-C0004500-1373-20011105 OSF440 - DUV40F1-C0005200-1377-20011105 OSF440 - DUV40FAS0001-20010609 OSF440 NOTE When a patch kit is listed, it does not necessarily mean all patches on that kit are installed on your system. Press RETURN to get back to the Patch Tracking Menu... If no patches are installed on the system, you will receive a message similar to the following: There are no patches installed on your system. _L_i_s_t _h_i_s_t_o_r_y _f_o_r _s_e_l_e_c_t_e_d _p_a_t_c_h_e_s The following sample log shows you how to show the patch history for selected patches: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Tracking Menu: ------------------- 1) List installed patches 2) List installed patch files 3) List patch kit information for installed patches 4) Show Patch History for selected patches 5) Show System Patch History Patch Management Utility 2-11 b) Back to Main Menu q) Quit Enter your choice: 4444 Patch Tracking Selection Menu: ------------------------------ 1) List Release Patch History for selected patches 2) List Customer Specific Patch History for selected patches 3) List All Patch History for selected patches b) Back to Tracking Menu q) Quit Enter your choice: 3333 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 listed. - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: 1) Patch 00020.00 - Cannot Use ipcs Cmd On System Not Booted With vmunix 2) Patch 00025.00 - Fix For ksh, file, tail, nawk, awk, And pax 3) Patch 00032.00 - mkdir -p Not Returning Error 4) Patch 00038.00 - quotaon Returns Incorrect Error Status 5) Patch 00040.00 - binmail Delivers Only Partial Messages 6) Patch 00041.00 - Fix For nroff Y2K Problem 7) Patch 00045.00 - Fix For sort -i Abort Problem 8) Patch 00047.00 - vi Puts Server Port INTO PASSALL MODE 9) Patch C 00045.00 - Fix for QAR 61365 10) Patch C 00046.00 - Fix for TLAQ90041 - DIGITAL_UNIX_V4.0F / Common Desktop Environment (CDE) Patches: 11) Patch 00005.00 - dtfile May Leave Defunct Processes - DIGITAL_UNIX_V4.0F / Filesystem Patches: 12) Patch 00039.00 - System Panic When Accessing ISO9660 Format CDROM 13) Patch 00054.00 - AdvFS volumes Not Setting I/O Byte Transfer Size - DIGITAL_UNIX_V4.0F / Hardware Configuration Patches: 14) Patch 00018.00 - Resolves Corrupt EV6 Binary Error Log Entries 15) Patch 00072.00 - Updates FORE ATM (lfa) driver to Rev. V1.0.14 - DIGITAL_UNIX_V4.0F / I/O Device Handling Patches: 16) Patch 00053.00 - Fix For spo_process_rsp Panic 17) Patch 00056.00 - KZPCA Host Bus Adapter May Hang 18) Patch 00058.00 - Additional Error Detection for FC Driver 19) Patch 00060.00 - Fix For spo_misc_errors errlog Entries 20) Patch 00073.00 - Problems With Driver Support For ELSA Gloria Synergy - DIGITAL_UNIX_V4.0F / Kernel Patches: 21) Patch 00016.00 - Fixes Kernel Memory Fault Caused By SMP Race 2-12 Patch Management Utility 22) Patch 00034.00 - Fix For kio Subsystem Panic 23) Patch 00044.00 - Fix For Kernel Memory Fault 24) Patch 00055.00 - New Functionality To Detect Unlinked Reference Files - DIGITAL_UNIX_V4.0F / Library Patches: 25) Patch 00046.00 - Shared Library Fix For curses-based Applications 26) Patch 00048.00 - DECthreads Library Fix - DIGITAL_UNIX_V4.0F / Network Patches: 27) Patch 00008.00 - Fix For POP Mail Handler 28) Patch 00017.00 - Fix For BIND Server 29) Patch 00021.00 - Fix For XTI And DECnet/OSI 30) Patch 00022.00 - automount Daemon Hangs 31) Patch 00043.00 - Fix For XTI Over TCP/IP 32) Patch 00057.00 - Fixes Several NFS Problems 33) Patch 00059.00 - Characters Randomly Repeated Using tip - DIGITAL_UNIX_V4.0F / Security Related Patches: 34) Patch 00002.00 - Security (SSRT0571U) 35) Patch 00003.00 - Security (SSRT0585U) 36) Patch 00004.00 - Security (SSRT0580U) 37) Patch 00006.00 - Security (SSRT0600U) 38) Patch 00011.00 - Security (SSRT0596U) 39) Patch 00012.00 - Security (SSRT0567U) 40) Patch 00028.00 - Security (SSRT0556U) 41) Patch 00031.00 - Security (SSRT0563U) 42) Patch C 00043.00 - Fix for SSRT0585U 43) Patch C 00052.00 - Fix for SSRT0585U - DIGITAL_UNIX_V4.0F / X11 Patches: 44) Patch 00007.00 - dxcalendar Reminder Displays Through dxpause Screen 45) Patch 00062.00 - Fix For Motif Drag-and-Drop 46) Patch 00063.00 - xfs Fails With Segmentation Fault 47) Patch 00074.00 - Fix For ELSA Gloria Synergy Graphics Board 48) Patch C 00044.00 - Fix for QAR 57198 Or you may choose one of the following options: 49) ALL of the above 50) CANCEL selections and redisplay menus 51) EXIT without listing any patches Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 44449999 You are listing the following patches: - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch 00020.00 - Cannot Use ipcs Cmd On System Not Booted With vmunix Patch 00025.00 - Fix For ksh, file, tail, nawk, awk, And pax Patch 00032.00 - mkdir -p Not Returning Error Patch 00038.00 - quotaon Returns Incorrect Error Status Patch 00040.00 - binmail Delivers Only Partial Messages Patch Management Utility 2-13 Patch 00041.00 - Fix For nroff Y2K Problem Patch 00045.00 - Fix For sort -i Abort Problem Patch 00047.00 - vi Puts Server Port INTO PASSALL MODE Patch C 00045.00 - Fix for QAR 61365 Patch C 00046.00 - Fix for TLAQ90041 - DIGITAL_UNIX_V4.0F / Common Desktop Environment (CDE) Patches: Patch 00005.00 - dtfile May Leave Defunct Processes - DIGITAL_UNIX_V4.0F / Filesystem Patches: Patch 00039.00 - System Panic When Accessing ISO9660 Format CDROM Patch 00054.00 - AdvFS volumes Not Setting I/O Byte Transfer Size - DIGITAL_UNIX_V4.0F / Hardware Configuration Patches: Patch 00018.00 - Resolves Corrupt EV6 Binary Error Log Entries Patch 00072.00 - Updates FORE ATM (lfa) driver to Rev. V1.0.14 - DIGITAL_UNIX_V4.0F / I/O Device Handling Patches: Patch 00053.00 - Fix For spo_process_rsp Panic Patch 00056.00 - KZPCA Host Bus Adapter May Hang Patch 00058.00 - Additional Error Detection for FC Driver Patch 00060.00 - Fix For spo_misc_errors errlog Entries Patch 00073.00 - Problems With Driver Support For ELSA Gloria Synergy - DIGITAL_UNIX_V4.0F / Kernel Patches: Patch 00016.00 - Fixes Kernel Memory Fault Caused By SMP Race Patch 00034.00 - Fix For kio Subsystem Panic Patch 00044.00 - Fix For Kernel Memory Fault Patch 00055.00 - New Functionality To Detect Unlinked Reference Files - DIGITAL_UNIX_V4.0F / Library Patches: Patch 00046.00 - Shared Library Fix For curses-based Applications Patch 00048.00 - DECthreads Library Fix - DIGITAL_UNIX_V4.0F / Network Patches: Patch 00008.00 - Fix For POP Mail Handler Patch 00017.00 - Fix For BIND Server Patch 00021.00 - Fix For XTI And DECnet/OSI Patch 00022.00 - automount Daemon Hangs Patch 00043.00 - Fix For XTI Over TCP/IP Patch 00057.00 - Fixes Several NFS Problems Patch 00059.00 - Characters Randomly Repeated Using tip - DIGITAL_UNIX_V4.0F / Security Related Patches: Patch 00002.00 - Security (SSRT0571U) Patch 00003.00 - Security (SSRT0585U) Patch 00004.00 - Security (SSRT0580U) Patch 00006.00 - Security (SSRT0600U) Patch 00011.00 - Security (SSRT0596U) Patch 00012.00 - Security (SSRT0567U) Patch 00028.00 - Security (SSRT0556U) Patch 00031.00 - Security (SSRT0563U) Patch C 00043.00 - Fix for SSRT0585U Patch C 00052.00 - Fix for SSRT0585U 2-14 Patch Management Utility - DIGITAL_UNIX_V4.0F / X11 Patches: Patch 00007.00 - dxcalendar Reminder Displays Through dxpause Screen Patch 00062.00 - Fix For Motif Drag-and-Drop Patch 00063.00 - xfs Fails With Segmentation Fault Patch 00074.00 - Fix For ELSA Gloria Synergy Graphics Board Patch C 00044.00 - Fix for QAR 57198 Is this correct? (y/n): y Patch History for selected patches Date Time Prd Patch Operation KitName ---- ---- ___ _____ _________ _______ 2001/11/05 13:13 DU Patch C 00052.00 Installed DUV40F1-C0005200-1377-20011105 2001/11/05 12:56 DU Patch C 00046.00 Removed 2001/11/05 10:53 DU Patch C 00046.00 Installed DUV40F1-C0004600-1374-20011105 2001/11/05 10:50 DU Patch C 00045.00 Installed DUV40F1-C0004500-1373-20011105 2001/11/05 10:48 DU Patch C 00044.00 Installed DUV40F1-C0004400-1372-20011105 2001/11/05 10:43 DU Patch C 00043.00 Installed DUV40F1-C0004300-1367-20011104 0000001/11/04 10:11 DU Patch 00003.00 Installed DUV40FAS0001-20010609 2001/11/04 10:11 DU Patch 00002.00 Installed DUV40FAS0001-20010609 Press RETURN to get back to the Patch Tracking Menu... _2._6 _H_a_n_d_l_i_n_g _M_a_n_u_a_l_l_y _I_n_s_t_a_l_l_e_d _S_y_s_t_e_m _F_i_l_e_s _w_i_t_h _B_a_s_e_l_i_n_i_n_g The dddduuuuppppaaaattttcccchhhh baselining process looks at the files installed on a system, compares them to the files it expects to find, and prevents the installation of any patch files that might cause an incompatibility among system files. This section provides an overview of the baselining process. See Section 4.7 for instructions on setting a baseline. Unknown system files occur when the files are replaced through non-standard system file installation methods such as the following: +o The manual installation of system files such as system administration customizations or manually installed patches +o Using the sssseeeettttlllldddd utility to install system files from user-derived sssseeeettttlllldddd subsets +o Using the sssseeeettttlllldddd utility to install files for layered software products +o Changes that result from weak system control programs (usually named _f_i_l_e....ssssccccpppp) Missing system files result from a root user manually deleting system files Patch Management Utility 2-15 that were installed during a standard full or update installation procedure or with the dddduuuuppppaaaattttcccchhhh utility. The file is removed but the system inventory records are still in place. Unknown and missing system files will block patch installations until you take corrective action. However, before taking any action, it is important that you understand the origin of the unknown system files or why missing files are no longer present on your system. Changing the system without this knowledge could leave your operating system or layered product software environment in an inconsistent and nonoperational state. For example, a file whose origin is unknown that is blocking the installation of a Release patch could be part of a manually installed Customer-Specific patch that is not contained in the Release patch. Removing that one file will disrupt the operation of your CSP and possibly the operation of the system. When you run the dddduuuuppppaaaattttcccchhhh system baseline feature, a baseline log file is captured in ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////bbbbaaaasssseeeelllliiiinnnneeee....lllloooogggg. (See Section 2.2 for information about log files.) You may need to set the patch baseline for your system if you have manually installed system files or if dddduuuuppppaaaattttcccchhhh informs you that patch installation is blocked by system files that are missing or unknown. _W_a_r_n_i_n_g Misusing the baselining feature can cause serious problems with your system. It is important to be aware of the following potential problems: +o Enabling baselining to override its applicability checking could leave your operating system or layered product software environment in an inconsistent and nonoperational state. +o Enabling baselining to update your system sets a new baseline for your operating system or TruCluster software environments. You will not be able to revert to the previous system state for manually installed patches that were marked as installed by baselining. HP recommends that you backup your ////, ////uuuussssrrrr, and ////vvvvaaaarrrr file systems before enabling system updates through dddduuuuppppaaaattttcccchhhh baselining. Baselining is divided into five phases that provide system information and optionally allow you to take actions that change the patch baseline of your system. You can run through all phases of baselining to get the system analysis without enabling changes to your system. You can run baselining in multiuser mode when you are the root user. _2._6._1 _P_h_a_s_e _1 - _S_y_s_t_e_m _E_v_a_l_u_a_t_i_o_n The primary goal of Phase 1 is to evaluate your system relative to the patch kit that is being installed. However, the baselining feature will report all missing and unknown files to assist you in better understanding the state of 2-16 Patch Management Utility the changed files on the system. The rest of the baselining phases use the information gathered in Phase 1 to inform you of any installation conflicts for patches contained in the patch kit. The amount of time needed to evaluate the state of the system varies greatly depending on the size of the patch kit, the version of the software product, and the performance of the system. _2._6._2 _P_h_a_s_e _2 - _P_a_t_c_h _L_a_y_e_r_e_d _P_r_o_d_u_c_t _C_o_n_f_l_i_c_t_s Phase 2 reports information for patches whose installation is blocked by system files that were installed by layered products. Baselining will not override layered product patch installation collision detection mechanisms as it is likely that the layered product or application customizations are not contained in the patch. Installation of the patch in this situation would leave the layered product or application nonoperational. To resolve this situation, contact your layered product or application Customer Services or HP Services if you have purchased Business Critical Services. _2._6._3 _P_h_a_s_e _3 - _I_d_e_n_t_i_f_y_i_n_g _M_a_n_u_a_l_l_y _I_n_s_t_a_l_l_e_d _P_a_t_c_h_e_s Phase 3 reports patches that exactly match existing files on your system that are not marked as _i_n_s_t_a_l_l_e_d by the system inventory. For example, in earlier kits, TruCluster software Release patches were installed manually. This phase will report any manually installed Release patch files that exactly match a patch contained in the current dddduuuuppppaaaattttcccchhhh-based TruCluster software patch kit. You can optionally enable dddduuuuppppaaaattttcccchhhh to mark these patches as _i_n_s_t_a_l_l_e_d, which involves copying valid sssseeeettttlllldddd database information to your system. The dddduuuuppppaaaattttcccchhhh utility will copy the appropriate _p_a_t_c_h__s_u_b_s_e_t.inv, _p_a_t_c_h__s_u_b_s_e_t.scp, and _p_a_t_c_h__s_u_b_s_e_t....ccccttttrrrrllll files into place for these patches. If you do not want to enable dddduuuuppppaaaattttcccchhhh to mark these patches as installed, you must manually remove the patched system files so the normal dddduuuuppppaaaattttcccchhhh installation can install the affected patches. _2._6._4 _P_h_a_s_e _4 - _H_a_n_d_l_i_n_g _M_i_s_s_i_n_g _o_r _U_n_k_n_o_w_n _F_i_l_e_s _o_n _Y_o_u_r _S_y_s_t_e_m Phase 4 reports information about any unknown and missing system files. These files should be considered as intentional customizations which are important to correct system operation. As such, care should be taken to understand why system files have been customized. Before enabling any patch installations in Phase 5, review the information reported in Phase 4 against your log of manual system changes to ensure you understand why the system was intentionally customized and to determine how to Patch Management Utility 2-17 proceed. In some cases you may need to remove customizations to ensure proper system operation. To assist you in identifying the origin of changed system files, baselining now reports all missing or unknown system files. The following sections provide general guidance for some of the normal situations where system files are intentionally customized manually. _2._6._4._1 _M_a_n_u_a_l_l_y _I_n_s_t_a_l_l_e_d _C_u_s_t_o_m_e_r-_S_p_e_c_i_f_i_c _P_a_t_c_h_e_s In response to a problem report, you may receive a manually installable Customer-Specific patch from your service provider. Customer-Specific patches are a set of compatible files that deliver fixes to the problems you reported. Additionally, the patch may include instrumentation necessary for debugging purposes. If your system was customized through a manual installation of Customer- Specific patches, you must ensure that the fixes delivered by the Customer- Specific patches are included in the current Release Patch Kit before enabling dddduuuuppppaaaattttcccchhhh to overwrite any unknown or missing system files. _W_a_r_n_i_n_g If you are unsure if the Customer-Specific patch is included in the Release Patch Kit, do not enable dddduuuuppppaaaattttcccchhhh to overwrite the manually installed Customer-Specific patch. If you must install the Release patch being blocked by a Customer-Specific patch, contact your service provider for assistance. If the unknown or missing files are attributable to manually installed Customer-Specific patches that are included in a Release Patch Kit, perform one of the following steps: +o If all Customer-Specific patch files are overwritten by the patches noted in Phase 5, you can safely enable dddduuuuppppaaaattttcccchhhh to overwrite applicable missing or unknown system files. +o If some of the Customer-Specific patch files are not overwritten by the patches noted in Phase 5, contact your service provider for assistance. To determine if your Customer-Specific patch is included in the Release Patch Kit, refer to the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s for the Release Patch Kit. See Section 1.4 for information about viewing patch documentation on the Web. _2._6._4._2 _M_a_n_u_a_l_l_y _I_n_s_t_a_l_l_e_d _R_e_l_e_a_s_e _P_a_t_c_h_e_s For some software products, manual installation has been the practiced method for patch installation. For example, patches for TruCluster software used to be installed manually. 2-18 Patch Management Utility You must determine whether the fixes delivered by the manually installed Release patches are included in the current dddduuuuppppaaaattttcccchhhh-based Release Patch Kit before enabling dddduuuuppppaaaattttcccchhhh to overwrite any unknown or missing system files. Once you have made this determination, proceed as follows: +o If the unknown or missing system files are attributable to the manual installation of Release patches and those patches are included in the current dddduuuuppppaaaattttcccchhhh-based Release Patch Kit, you can safely enable dddduuuuppppaaaattttcccchhhh to overwrite applicable missing or unknown system files. +o If the unknown or missing system files are not attributable to manual installation, you must understand the origin of the unknown or missing system files by reviewing the information reported in Phase 4 against your log of manual system changes to ensure you understand why the system was intentionally customized, and to determine how to proceed. _2._6._4._3 _U_s_e_r _C_u_s_t_o_m_i_z_e_d _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s Periodically, system administrators of production computing environments replace Tru64 UNIX commands or utilities with freeware or their own customized version of the command or utility. In this situation you must ensure the unknown or missing files are attributable to intentional replacement of commands, utilities, or other system files. If the unknown or missing system files are attributable to the replacement of commands, utilities, or other system files with customized versions for the computing environment, do not enable dddduuuuppppaaaattttcccchhhh to overwrite the manually installed customized files. Instead, determine the reason for the customization and then decide how to proceed. _2._6._5 _P_h_a_s_e _5 - _E_n_a_b_l_i_n_g _d_u_p_a_t_c_h _t_o _O_v_e_r_w_r_i_t_e _C_h_a_n_g_e_d _S_y_s_t_e_m _F_i_l_e_s Phase 5 reports patches that are blocked due to missing or unknown system files, and optionally allows you to override the dddduuuuppppaaaattttcccchhhh conflict management mechanism so the dddduuuuppppaaaattttcccchhhh-based patch may be installed. For each patch that is blocked by a missing or unknown system file you are presented with the following information: +o Software product identifier +o Patch category +o Patch identifier +o Patch subset description +o The list of unknown and missing files that block the patch installation Patch Management Utility 2-19 +o The origin of all other files contained in the patch Optionally, you can enable dddduuuuppppaaaattttcccchhhh to override the collision detection mechanisms and install any of these patches. Use the missing and unknown file information presented in Phase 4 and your system administration log of manual system changes to make Phase 5 patch installation enabling decisions. _W_a_r_n_i_n_g Do not enable dddduuuuppppaaaattttcccchhhh to install patches over missing or unknown system files for which you do not know the origin. Doing so may leave your operating system and TruCluster software environment in an inconsistent and nonoperational state. 2-20 Patch Management Utility Issues and Restrictions 3 This chapter provides information you must be aware of when installing or removing patches. Be sure to check the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s document of the kit you are installing for any issues and restrictions that pertain to that installation. _3._1 _W_h_e_n _S_i_n_g_l_e-_U_s_e_r _M_o_d_e _I_s _R_e_c_o_m_m_e_n_d_e_d Although you can install patches in multiuser mode, HP recommends that you bring down your system to single-user mode when installing patches that affect the operation of the Tru64 UNIX operating system or the product you are patching. If your system must remain in multiuser mode, it is recommended that you apply the patches when the system is as lightly loaded as possible. There are no restrictions on performing patch selection and preinstallation checking in multiuser mode. Patch removals can only be done in single-user mode. _3._2 _C_a_u_t_i_o_n _o_n _R_e_m_o_v_i_n_g _V_e_r_s_i_o_n _S_w_i_t_c_h_e_d _P_a_t_c_h_e_s See Section 5.7.1 for cautionary information about removing version switched patches that were successfully installed during a previous rolling upgrade on a cluster. _3._3 _I_m_p_a_c_t _o_n _S_y_s_t_e_m _U_p_g_r_a_d_e_s _t_o _L_a_t_e_r _V_e_r_s_i_o_n_s _o_f _T_r_u_6_4 _U_N_I_X In the presence of patches of layered products, certain procedures used to upgrade a system to a later version of Tru64 UNIX can lead to inconsistencies among operating system and layered product objects. _N_o_t_e After successfully installing a new version of Tru64 UNIX, you should obtain and install the latest patch kit that is applicable to that version of Tru64 UNIX. _3._4 _P_a_t_c_h_i_n_g _a _S_y_s_t_e_m _P_r_i_o_r _t_o _C_r_e_a_t_i_n_g _a _C_l_u_s_t_e_r If you have not yet created your cluster, you can save time by patching your system first. The sequence of events when patching the initial installation of Tru64 UNIX is as follows: 1. Install and configure the Tru64 UNIX operating system. 2. Use the sssseeeettttlllldddd command to install the TruCluster software kit. If the TruCluster software kit is not loaded before the patch operation, patches for TruCluster software will not be loaded. 3. Patch the system. 4. Use the cccclllluuuu____ccccrrrreeeeaaaatttteeee command to create the single-member cluster. _N_o_t_e Once you have completed step 4 and created your cluster, do not remove patches installed during step 3. To do so may cause your system to become unusable if dddduuuuppppaaaattttcccchhhh replaces certain patched files with ones that are not cluster enabled. If you have identified patches that you want to remove, contact your HP service representative to find out if you can do so safely. See the Tru64 UNIX _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information about installing the operating system and the TruCluster _C_l_u_s_t_e_r _I_n_s_t_a_l_l_a_t_i_o_n manual for information about creating your cluster. _3._5 _R_e_s_t_r_i_c_t_i_o_n _o_n _L_o_a_d_i_n_g _N_e_w _d_u_p_a_t_c_h _T_o_o_l_s _f_r_o_m _t_h_e _C_o_m_m_a_n_d _L_i_n_e The new patch tools cannot be loaded using the ddddeeeelllleeeetttteeee command on the command line. Doing that will cause the following error to be displayed: product_map does not exist or is empty, Cannot continue. If you want to use ddddeeeelllleeeetttteeee from the command line, you can first load the new tools, without affecting the system, by issuing the iiiinnnnssssttttaaaallllllll command with the -precheck_only option. This will load the tools and not cause changes to your system. _3._6 _N_o _R_I_S _o_r _D_M_S _I_n_s_t_a_l_l_a_t_i_o_n _o_f _P_a_t_c_h_e_s Remote Installation Services (RIS) and Dataless Management Services (DMS) installations of patches are not supported. However, the patch kit installation mechanism does support network installation via NFS. _3._7 _D_i_r_e_c_t _s_e_t_l_d _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _R_e_m_o_v_a_l _o_f _P_a_t_c_h _S_u_b_s_e_t_s _I_s _N_o_t _A_l_l_o_w_e_d You can install and remove Tru64 UNIX and TruCluster software patches only through dddduuuuppppaaaattttcccchhhh. You cannot directly install or reinstall the patch subsets with sssseeeettttlllldddd. This ensures that patch tracking and management are not compromised. 3-2 Issues and Restrictions _3._8 _L_i_m_i_t_a_t_i_o_n _f_o_r /_v_a_r/_a_d_m/_p_a_t_c_h/_b_a_c_k_u_p _D_i_r_e_c_t_o_r_y _H_a_n_d_l_i_n_g The patch management utility assumes there is one ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp directory per system. It does not handle placement of archived original files for multiple systems in one directory. _3._9 _D_o _N_o_t _E_n_t_e_r _C_t_r_l/_c _D_u_r_i_n_g _I_n_s_t_a_l_l_a_t_i_o_n _P_h_a_s_e Do not enter a Ctrl/c command during the installation phase of the patch kit. _C_a_u_t_i_o_n As with any system update, entering a Ctrl/c during this phase will leave the operating system software environment in an inconsistent and nonrecoverable state. _3._1_0 _R_e_m_o_v_i_n_g _P_a_t_c_h_e_s _C_o_n_t_a_i_n_i_n_g _C_u_s_t_o_m_i_z_e_d _F_i_l_e_s If you use dddduuuuppppaaaattttcccchhhh to remove a patch containing a customized file, messages similar to the following may appear in the session log file, ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////sssseeeessssssssiiiioooonnnn....lllloooogggg: Customization found in //filename Before the backup was restored, we had saved a copy of this file in: //filename.PreDel_OSFPATyyy Please compare //filename with this saved copy. If there are extra customizations you want to keep, you would need to merge them into /filename manually. //filename.PreDel_OSFPATyyy can be removed afterwards. In this message, ////////ffffiiiilllleeeennnnaaaammmmeeee is the full path of the customized file being replaced, and yyyyyyyyyyyy is the patch subset ID number. This message warns you to examine the removed patch for any customized files it may contain. In order to keep those customizations, you will have to manually add them. The following are examples of such customized files: +o ////uuuussssrrrr////vvvvaaaarrrr////ssssppppoooooooollll////ccccrrrroooonnnn////ccccrrrroooonnnnttttaaaabbbbssss////rrrrooooooootttt +o ////eeeettttcccc////ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb +o ////uuuussssrrrr////vvvvaaaarrrr////aaaaddddmmmm////sssseeeennnnddddmmmmaaaaiiiillll////sssseeeennnnddddmmmmaaaaiiiillll....ccccffff Issues and Restrictions 3-3 _3._1_1 _R_e_l_e_a_s_e _P_a_t_c_h_e_s _D_o _N_o_t _A_u_t_o_m_a_t_i_c_a_l_l_y _S_u_p_e_r_s_e_d_e _C_S_P_s Currently, Release patches cannot automatically supersede dddduuuuppppaaaattttcccchhhh-based Customer-Specific patches (CSPs). Any Release patch blocked by a CSP will result in a dddduuuuppppaaaattttcccchhhh message. See Section A.1.7 for more information. 3-4 Issues and Restrictions Patch Installation and Removal Instructions 4 This chapter provides instructions for installing and removing patches from the Tru64 UNIX operating system and the TruCluster software products. _N_o_t_e Chapter 5 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 in Chapter 5, and then return to this chapter for help in running the dddduuuuppppaaaattttcccchhhh utility. If you have not yet created your cluster, follow the steps in Section 3.4. _4._1 _S_u_m_m_a_r_y _o_f _S_t_e_p_s _f_o_r _U_s_i_n_g _P_a_t_c_h _K_i_t_s The following list summarizes the steps necessary to install patches on your system. The referenced sections provide the full details. HP recommends that you familiarize yourself with these steps before attempting to install Tru64 UNIX or TruCluster software patch kits. 1. Review the list of issues and restrictions in Chapter 3 and in the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s document that comes with your patch kit. 2. Prepare your system for patch installation (Section 4.2). 3. Make the patch distribution available to your system (Section 4.3). 4. Load any new patch tools provided with the new patch distribution (Section 4.4). 5. Set the patch baseline if system files have been changed manually (Section 4.7). 6. Perform patch preinstallation check (Section 4.6). 7. Install patches mode (Section 4.8). 8. Rebuild the kernel and reboot the system (Section 4.9). _4._2 _P_r_e_p_a_r_i_n_g _t_o _I_n_s_t_a_l_l _P_a_t_c_h_e_s Before using the latest Tru64 UNIX or TruCluster software patch distribution, make sure that your system meets the required criteria and that you perform certain preinstallation tasks, as described in the following list: +o Make sure you have the correct software You must have the appropriate versions of Tru64 UNIX and TruCluster software installed on your system to install patch kits. There are separate patch kits for each version of the Tru64 UNIX and TruCluster software products. The patch kits will not install on any other version of those products. For example, the Tru64 UNIX 5.0 patch kit will only install on Tru64 UNIX Version 5.0. +o Back up your system It is recommended that you backup your ////, ////uuuussssrrrr, and ////vvvvaaaarrrr file systems prior to installing patches or baselining your system. +o Make sure you have enough storage space Refer to the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s for the required storage space. _4._3 _M_a_k_i_n_g _t_h_e _P_a_t_c_h _D_i_s_t_r_i_b_u_t_i_o_n _A_v_a_i_l_a_b_l_e Tru64 UNIX and TruCluster softwaree patches are available from the HP Services Web page or the Tru64 UNIX Patch CD-ROM. Once you have obtained the patch distributions use the following instructions to make the patch kits available to the system targeted for update: 1. Ensure the installation prerequisites described in Section 4.2 are met. 2. If you are using patch tar files obtained via the Internet from HP (see Section 1.4), you must expand the tar file to access the patch kits. The tar file can be expanded on any NFS mountable file system. For example: # ////uuuussssrrrr////ssssbbbbiiiinnnn////mmmmoooouuuunnnntttt ////ddddeeeevvvv////ddddiiiisssskkkk////ddddsssskkkk3333gggg ////PPPPaaaattttcccchhhhKKKKiiiittttssss # ccccdddd ////PPPPaaaattttcccchhhhKKKKiiiittttssss # mmmmkkkkddddiiiirrrr kkkkiiiitttt2222 _N_o_t_e If you are installing successive patch kits, place and untar each kit in a separate directory. Copy or ftp the patch kit to ////PPPPaaaattttcccchhhhKKKKiiiittttssss////kkkkiiiitttt2222. For example: 4-2 Patch Installation and Removal Instructions # ccccpppp TTTT66664444VVVV55551111BBBB11118888AAAASSSS0000000000003333----22220000000011111111000022220000....ttttaaaarrrr ////PPPPaaaattttcccchhhhKKKKiiiittttssss////kkkkiiiitttt2222 # ssssccccrrrriiiipppptttt uuuunnnnttttaaaarrrr....lllloooogggg # ttttaaaarrrr ----xxxxppppvvvvffff TTTT66664444VVVV55551111BBBB11118888AAAASSSS0000000000003333----22220000000011111111000022220000....ttttaaaarrrr # [[[[CCCCttttrrrrllll////dddd]]]] Or alternatively: # eeeexxxxiiiitttt View the uuuunnnnttttaaaarrrr....lllloooogggg for errors or failures untarring the file. Once the tar file has been expanded, make the file system containing the patch kits available to the system being patched. For example, on the system you are patching do the following: # ////uuuussssrrrr////ssssbbbbiiiinnnn////mmmmoooouuuunnnntttt ////PPPPaaaattttcccchhhhKKKKiiiittttssss////kkkkiiiitttt2222@@@@hhhhoooossssttttnnnnaaaammmmeeee ////mmmmnnnntttt 3. If you are using the Tru64 UNIX Patch CD-ROM you need only mount the CD- ROM, as the information on the CD-ROM is already expanded. For example: # uuuussssrrrr////ssssbbbbiiiinnnn////mmmmoooouuuunnnntttt ----rrrr ////ddddeeeevvvv////ddddiiiisssskkkk////ccccddddrrrroooommmm0000cccc ////mmmmnnnntttt _4._4 _L_o_a_d_i_n_g _N_e_w _P_a_t_c_h _T_o_o_l_s The patch kits deliver updated patch tools to your system. It is important that you run the dddduuuuppppaaaattttcccchhhh utility located in the ////ppppaaaattttcccchhhh____kkkkiiiitttt directory every time you obtain new patch tar files or a new Tru64 UNIX Patch CD-ROM. After you have made the patch kits available to the system being patched, run dddduuuuppppaaaattttcccchhhh as follows: # ////_m_n_t/PatchKits/kit2/patch_kit/dupatch If new patch tools are available they will be loaded and you will see messages similar to the following: * A new version of patch tools required for patch management is now being installed on your system. * Tools updated, invoking the updated Patch Utility... The dddduuuuppppaaaattttcccchhhh utility saves information on the tools that have been loaded to the log file ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////DDDDuuuuppppaaaattttcccchhhh____llllooooaaaadddd_____d_a_t_e.log. (See Section 2.2 for information about log files.) Patch Installation and Removal Instructions 4-3 _4._5 _I_n_v_o_k_i_n_g _t_h_e _M_a_i_n _d_u_p_a_t_c_h _M_e_n_u Once the new tools have been loaded, dddduuuuppppaaaattttcccchhhh prompts you for the path to the patch kit files. After you specify the path (or press Return if the patch kit is your current directory) you will see the main menu. For example: Enter path to the top of the patch distribution, or enter "q" to get back to the menu : ////mmmmnnnntttt////PPPPaaaattttcccchhhhKKKKiiiitttt////kkkkiiiitttt2222////ppppaaaattttcccchhhh____kkkkiiiitttt Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: _4._6 _P_e_r_f_o_r_m_i_n_g _P_a_t_c_h _P_r_e_i_n_s_t_a_l_l_a_t_i_o_n _C_h_e_c_k _I_n_s_t_r_u_c_t_i_o_n_s To minimize system down time, you can perform the preinstallation check on a system running in multiuser mode, even if you will perform the actual installation in single-user mode. Note that the menu you see will differ slightly, depending upon whether you log in from a pseudo-terminal or a system console. The following steps assume you logged in from a pseudo-terminal. 1. Log in as root. 2. From the main dddduuuuppppaaaattttcccchhhh menu, enter 1111 at the EEEEnnnntttteeeerrrr yyyyoooouuuurrrr cccchhhhooooiiiicccceeee prompt: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 4-4 Patch Installation and Removal Instructions 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 3. The program responds with the Patch Installation Menu. Enter 1111 at the EEEEnnnntttteeeerrrr yyyyoooouuuurrrr cccchhhhooooiiiicccceeee prompt: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Installation Menu: ------------------------ 1) Pre-Installation Check ONLY 2) Check & Install in single-user mode w/ network services 3) Check and Install in Multi-User mode b) Back to Main Menu q) Quit Enter your choice: 1111 Checking patch kit for transmission errors during download... Finished Checking patch kit checksums Gathering patch information... (depending upon the size of the patch kit, this may take awhile) *** Start of Special Instructions *** *** There are NO Special Instructions *** Patch Installation and Removal Instructions 4-5 Press RETURN to proceed... 4. You have the option to make the patches reversible so you can revert the system to its state prior to the installation of a patch. The dddduuuuppppaaaattttcccchhhh utility lists the following information. Press Return at the prompt to make the patches reversible. This is the recommended action. ------------------------------------------------------------------------ To Make Patches Reversible - PLEASE READ THE FOLLOWING INFORMATION: - You have the option to make the patches reversible so you can revert the system to its state prior to the installation of a patch. - Reversibility is achieved by compressing and saving a copy of the files being replaced by the patches. These files would be restored to the system if you choose to delete a patch. - If you choose to make patches NON-reversible, then the system cannot be restored to the state prior to the installation of a patch; you will not be able to delete the patches later. - This patch kit may force a small set of patches to be reversible to ensure your upgrades to future versions of Tru64 UNIX are successful. The Patch Utility will make those patches reversible automatically. Refer to the Release Notes / Installation Instructions provided with this patch kit. Do you want the patches to be reversible? [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] By default, the backup copies of the installed patches will be 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. You must ensure the backup directory is configured the same way during any patch removal operations. Your current setup of "/var/adm/patch/backup" is: * A plain directory (not a mount point or a symbolic link) Do you want the patches to be reversible? [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] By default, the backup copies of the installed patches will be saved in ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp. If you have limited space in ////vvvvaaaarrrr, 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. 4-6 Patch Installation and Removal Instructions 5. Answer yyyyeeeessss when asked if you want to perform the preinstallation check with this setup: Do you want to proceed with the pre-installation check with this setup? [y]: 6. The program then lists the optional patches that apply to your system. You can perform the preinstallation check on specific patches or on all patches. Because we recommend that you install all of a kit's patches, we recommend running the preinstallation check on all of them. The patches you select during this process are only analyzed in relation to your system; they are not installed. The option that reads EEEEXXXXIIIITTTT wwwwiiiitttthhhhoooouuuutttt iiiinnnnssssttttaaaalllllllliiiinnnngggg aaaannnnyyyy ppppaaaattttcccchhhheeeessss is misleading in that no patches are installed regardless of which option you select during the preinstallation check. The patches listed below are optional: There may be more optional 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 installed. - Tru64_UNIX_V5.0A/ Cluster Kernel Patches: 1) Patch 00090.00 - versw command can core dump during rolling upgrade 2) Patch 00186.00 - Disks can become inaccessible on a cluster node - Tru64_UNIX_V5.0A / Commands, Shells, & Utilities Patches: 3) Patch 00015.00 - Fixes a problem that occurs in multibyte locales 4) Patch 00019.00 - Fixes a problem with the grep command 00004) Patch 00152.00 - Memory leak when creating and destroying widgets 95) Patch 00174.00 - Fix for memory leaks in Xlib 96) Patch 00176.00 - Memory leaks occur when creating widgets 97) Patch 00180.00 - Fixes memory leak in libXm 98) Patch 00182.00 - libXm memory leak when creating widgets Or you may choose one of the following options: 99) ALL of the above 100) CANCEL selections and redisplay menus 101) EXIT without installing any patches Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 99999999 You are installing the following optional patches: _N_o_t_e Patch Installation and Removal Instructions 4-7 You are not actually installing any patches at this time. This message only refers to patches that will undergo the preinstallation check. After the program lists the patches you have selected, it asks you to confirm the selection and runs the preinstallation check if you answer yyyyeeeessss: Is this correct? (y/n): yyyy Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take awhile) *** You have selected 98 patches *** Checking system space needed for patch installation and backup... ************************************************************** Pre-Installation Check COMPLETED with the following results: 98 patches passed Pre-Installation Check 0 patches failed Pre-Installation Check ************************************************************** Press RETURN to continue... 7. The program lists any patches that fail the prerequisite and applicability checks, and asks how you want to proceed. You have the following choices: 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 the patches are prevented from being installed because of missing or unknown system files, set the system patch baseline, as described in Section 4.7. If patches are prevented from being installed because dependent patches were not selected, choose the sssseeeelllleeeecccctttt ppppaaaattttcccchhhheeeessss aaaaggggaaaaiiiinnnn item and add the required patches that are missing. Otherwise, proceed to the installation phase, as described in Section 4.8. 4-8 Patch Installation and Removal Instructions _4._7 _S_e_t_t_i_n_g _t_h_e _S_y_s_t_e_m _P_a_t_c_h _B_a_s_e_l_i_n_e If your system was customized as a result of the manual installation of any system files, you will need to set the patch baseline for your system. If you do not need to set the patch baseline for your system, proceed to Section 4.8. _N_o_t_e You will need to be familiar with the concepts of baselining in Section 2.6 before preforming the steps in this section. You can set the patch baseline in multiuser mode, thereby minimizing system down time. The following steps show you how to set a patch baseline. 1. Log in as root. 2. Run dddduuuuppppaaaattttcccchhhh and enter 5555 in response to the EEEEnnnntttteeeerrrr yyyyoooouuuurrrr cccchhhhooooiiiicccceeee prompt of the Main Menu: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 5555 A summary of the patch baselining phases will be displayed on the screen. 3. Answer yyyy or nnnn when asked if you want to proceed with setting the patch baseline (you must provide an answer; there is no default answer): Do you want to proceed with the analysis and adjustment? [y/n]: yyyy If you answer yes, dddduuuuppppaaaattttcccchhhh asks you to enter the location of the patch distribution as follows: Patch Installation and Removal Instructions 4-9 Enter path to the top of the patch distribution, or enter "q" to get back to the menu : ////mmmmnnnntttt////PPPPaaaattttcccchhhhKKKKiiiitttt////kkkkiiiitttt2222////ppppaaaattttcccchhhh____kkkkiiiitttt The summary of the patch baselining phases provides the following information: +o Baselining Phase 1 evaluates your system relative to the patch kit. +o Baselining Phase 2 reports information for patches whose installation is blocked by system files that were installed by layered products. You cannot enable dddduuuuppppaaaattttcccchhhh to install patches that replace system files installed by layered products. You must contact your layered product customer services or HP Services if you have purchased Business Critical Services. +o Baselining Phase 3 reports on patches that match existing files on your system, but are not marked as _i_n_s_t_a_l_l_e_d by the system inventory. You can tell dddduuuuppppaaaattttcccchhhh to mark these patches as _i_n_s_t_a_l_l_e_d. This involves copying valid sssseeeettttlllldddd database information to your system. If exact matches are found you will be asked the following question: Do you want to mark these patches as installed ? [y/n] You must provide an answer; there is no default answer. +o Baselining Phase 4 reports information about any unknown or missing system files. This information is provided to assist you in understanding the state of files that may prevent patch installation. Consider this information carefully when making decisions to override patch-installation checks for patches noted in Phase 5. +o Phase 5 reports patches that do not pass installation applicability tests due to the current state of your system. The installation of these patches is prevented by missing or unknown system files. The dddduuuuppppaaaattttcccchhhh utility reports the known information about the files contained in each patch and asks if you want to enable the installation: Do you want to enable the installation of any of these patches? [y/n]: You must provide an answer; there is no default answer. Answer nnnn, until you know the origin of the files that are preventing the patch installation. The changed system files that are preventing the Release patch installation may be part of a manually installed Customer- Specific patch or an intentionally customized utility or file. If, for example, the file that is preventing the installation of an Release patch is one of many files that are part of a Customer-Specific patch, you must determine how to proceed. For more information, see Section 2.6.4.1 4-10 Patch Installation and Removal Instructions and Section 2.6.5. If you answer yyyy to this question, you can selectively enable dddduuuuppppaaaattttcccchhhh to install patches that are prevented from being installed by missing or unknown files. The dddduuuuppppaaaattttcccchhhh utility will present the list of patches so you can optionally enable installation. It then asks you how to proceed. If you select patches for installation, dddduuuuppppaaaattttcccchhhh asks you to confirm your selections and then enables installation of the selected patches. Perform the patch installation as described in Section 4.8. _C_a_u_t_i_o_n Do not enable dddduuuuppppaaaattttcccchhhh to install patches over missing or unknown system files for which you do not know the origin. To do so might leave your operating system or TruCluster software environments in an inconsistent or nonoperational state. _4._8 _I_n_s_t_a_l_l_i_n_g _a_n_d _E_n_a_b_l_i_n_g _P_a_t_c_h_e_s Patch installation is performed through dddduuuuppppaaaattttcccchhhh. The -l of the sssseeeettttlllldddd command is disabled for patch subsets. Before beginning the installation, make sure that you have completed all of the preliminary steps: +o Make sure you have met the installation prerequisites described in Section 4.2. +o Make sure you made the patch distribution available to your system, as described in Section 4.3. +o Make sure you loaded any new patch tools, as described in Section 4.4. +o Make sure that you performed the patch preinstallation check, as described in Section 4.6. +o If needed, make sure that system patch baseline has been set, as described in Section 4.7. The following sections provide step-by-step instructions for installing and enabling patches. _N_o_t_e If you are installing patches on a cluster, see Chapter 5 before you begin the patching process. Patch Installation and Removal Instructions 4-11 _4._8._1 _C_h_o_o_s_i_n_g _S_i_n_g_l_e-_U_s_e_r _o_r _M_u_l_t_i_u_s_e_r _M_o_d_e You can install patches from either single-user or multiuser modes. See Section 3.1 for information about selecting one of these modes. Section 4.8.1.1 describes the process from single-user mode and Section 4.8.1.2 describes the process from multiuser mode. Section 4.8.2 describes the remaining steps, which are common to installations from single-user and multiuser modes. _4._8._1._1 _I_n_s_t_a_l_l_i_n_g _P_a_t_c_h_e_s _f_r_o_m _S_i_n_g_l_e-_U_s_e_r _M_o_d_e The following list describes the steps you take and the type of output you will see when you install patches from single-user mode. 1. Halt the system. For example: # ////uuuussssrrrr////ssssbbbbiiiinnnn////sssshhhhuuuuttttddddoooowwwwnnnn ----hhhh ++++5555 """"AAAAppppppppllllyyyyiiiinnnngggg 5555....1111 aaaannnndddd TTTTCCCCRRRR PPPPaaaattttcccchhhheeeessss"""" 2. Boot to single-user mode from the console prompt. For example: >>>bbbbooooooootttt ----ffffllll ssss 3. Run the iiiinnnniiiitttt ssss command to change the run level to a single-user state with only essential kernel services: # ////ssssbbbbiiiinnnn////iiiinnnniiiitttt ssss 4. Run the bbbbcccchhhheeeecccckkkkrrrrcccc command to check and mount all the UFS and AdvFS file systems, the kkkkllllooooaaaaddddssssrrrrvvvv command to load kernel modules into the kernel, and the llllmmmmffff rrrreeeesssseeeetttt command to copy license details for all enabled products from the License Database to the kernel cache: # ////ssssbbbbiiiinnnn////bbbbcccchhhheeeecccckkkkrrrrcccc # ////ssssbbbbiiiinnnn////kkkkllllooooaaaaddddssssrrrrvvvv # ////uuuussssrrrr////ssssbbbbiiiinnnn////llllmmmmffff rrrreeeesssseeeetttt 5. For systems prior to 5.0A, issue the uuuuppppddddaaaatttteeee command and activate your swap partition with the sssswwwwaaaappppoooonnnn command: # ////ssssbbbbiiiinnnn////uuuuppppddddaaaatttteeee # ////ssssbbbbiiiinnnn////sssswwwwaaaappppoooonnnn ----aaaa 6. Enter the rrrrcccciiiinnnneeeetttt command to start network services: 4-12 Patch Installation and Removal Instructions # ////uuuussssrrrr////ssssbbbbiiiinnnn////rrrrcccciiiinnnneeeetttt ssssttttaaaarrrrtttt Informational messages will appear on the screen. 7. Run the dddduuuuppppaaaattttcccchhhh utility. (This step assumes that the patch kit is available to your system, as described in Section 4.3, and that the new patch tools have been loaded, as described in Section 4.4.) Enter 1111 at the EEEEnnnntttteeeerrrr yyyyoooouuuurrrr cccchhhhooooiiiicccceeee prompt to the invoke the patch installation session: #### dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 8. When the patch installation menu is displayed, enter 2222, at the EEEEnnnntttteeeerrrr yyyyoooouuuurrrr cccchhhhooooiiiicccceeee prompt: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Installation Menu: ----------------------- 1) Pre-Installation Check ONLY 2) Check & Install patches in Single-User Mode b) Back to Main Menu q) Quit Enter your choice: 2222 Patch Installation and Removal Instructions 4-13 _4._8._1._2 _I_n_s_t_a_l_l_i_n_g _P_a_t_c_h_e_s _f_r_o_m _M_u_l_t_i_u_s_e_r _M_o_d_e 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 dddduuuuppppaaaattttcccchhhh utility. (This step assumes that the patch kit is available to your system, as described in Section 4.3, and that the new patch tools have been loaded, as described in Section 4.4). Enter 1111 at the EEEEnnnntttteeeerrrr yyyyoooouuuurrrr cccchhhhooooiiiicccceeee prompt to the invoke the patch installation session: #### dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 2. When the patch installation menu is displayed. Enter 3333, at the EEEEnnnntttteeeerrrr yyyyoooouuuurrrr cccchhhhooooiiiicccceeee prompt: Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in //var/adm/patch/log/session.log Patch Installation Menu: ----------------------- 1) Pre-Installation Check ONLY 2) Check & Install in single-user mode w/ network services 3) Check and Install in Multi-User mode b) Back to Main Menu q) Quit 4-14 Patch Installation and Removal Instructions Enter your choice: 3333 *** Installation Warning *** You have chosen to install patches onto this system while it is running in Multi-User mode. Some patches may directly affect core operating system operations. To insure 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]: _4._8._2 _C_o_m_m_o_n _I_n_s_t_a_l_l_a_t_i_o_n _S_t_e_p_s 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. 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 yyyy 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 ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp. If you have limited space in ////vvvvaaaarrrr, 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. 2. 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]: 3. 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: JJJJooooeeee Patch Installation and Removal Instructions 4-15 Enter any notes about this operation that you would like stored for future reference. To end your input, enter a period (.) and press Return. :::: IIIInnnnssssttttaaaalllllllliiiinnnngggg PPPPaaaattttcccchhhh KKKKiiiitttt 3333 :::: .... [[[[RRRReeeettttuuuurrrrnnnn]]]] 4. The program lists the patches available for installation on your system. This list may be different from system to system because dddduuuuppppaaaattttcccchhhh does not display available patches that are already installed on your system. You can install all patches (as recommended by HP) or selectively choose patches for installation. You can also cancel selections and redisplay menus, or exit without installing any patches. The following is an example of the dddduuuuppppaaaattttcccchhhh output: Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6) : 000030) Patch 0381.00 - Motif Toolkit Correction 131) Patch 0384.00 - Various X11 Server Corrections 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 dddduuuuppppaaaattttcccchhhh installation menu. _N_o_t_e When installing Customer-Specific patches, you do not have the option of selecting individual patches; you must install them all. You can, however, remove individual CSPs after the installation process is completed and the system has been rebooted. 5. The preinstallation check verifies that the patches will install. If the preinstallation check is successful, dddduuuuppppaaaattttcccchhhh proceeds with the installation. If the preinstallation check fails, dddduuuuppppaaaattttcccchhhh 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 4-16 Patch Installation and Removal Instructions check, dddduuuuppppaaaattttcccchhhh will start installing those patches and provide informational messages on the screen. The entire dddduuuuppppaaaattttcccchhhh 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 4.7. 6. Review the dddduuuuppppaaaattttcccchhhh session log, ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////sssseeeessssssssiiiioooonnnn....lllloooogggg, to ensure that the installation was successful. Note any special patch instructions, informational messages, and error messages. (See Section 2.2 for information about dddduuuuppppaaaattttcccchhhh logs.) 7. Assuming the patch installation was successful, rebuild the kernel (vvvvmmmmuuuunnnniiiixxxx), save the existing kernel, move the new kernel into place, and reboot the system. For more information, see the Tru64 UNIX _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual. The following steps show the typical process: 1. Configure a new vvvvmmmmuuuunnnniiiixxxx. For example: # ddddooooccccoooonnnnffffiiiigggg ----cccc _H_O_S_T_N_A_M_E 2. Save the existing vvvvmmmmuuuunnnniiiixxxx. For example: # ccccpppp ////vvvvmmmmuuuunnnniiiixxxx ////uuuussssrrrr////vvvvmmmmuuuunnnniiiixxxx....pppprrrreeeekkkkiiiitttt11111111---- 3. Install the newly built kernel (vvvvmmmmuuuunnnniiiixxxx). For example: # ccccpppp ////uuuussssrrrr////ssssyyyyssss////_H_O_S_T_N_A_M_E/vmunix /vmunix 4. Reboot the system. For example: # ////uuuussssrrrr////ssssbbbbiiiinnnn////sssshhhhuuuuttttddddoooowwwwnnnn ----rrrr ++++5555 \\\\ """"RRRReeeebbbbooooooootttt wwwwiiiitttthhhh nnnneeeewwwwllllyyyy iiiinnnnssssttttaaaalllllllleeeedddd ppppaaaattttcccchhhheeeessss"""" _4._9 _R_e_b_u_i_l_d_i_n_g _t_h_e _K_e_r_n_e_l The dddduuuuppppaaaattttcccchhhh utility determines whether the installation or removal of patches requires that the kernel be rebuilt and the system rebooted. This action is then performed automatically or manually, depending upon the method you used to install the patches: +o When using the command line, the kernel is built automatically with the ddddooooccccoooonnnnffffiiiigggg utility, using the -a option. It also uses the -c option of the Patch Installation and Removal Instructions 4-17 -cfgfile command line option if that command was used. +o When using the menu-based interface, the kernel build occurs as if ddddooooccccoooonnnnffffiiiigggg was entered from the command line. The dddduuuuppppaaaattttcccchhhh utility asks if your system has a custom configuration file and if you want to change it. _4._1_0 _R_e_b_o_o_t_i_n_g _t_h_e _S_y_s_t_e_m The action that dddduuuuppppaaaattttcccchhhh 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. _4._1_0._1 _I_n _S_i_n_g_l_e-_U_s_e_r _M_o_d_e 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, dddduuuuppppaaaattttcccchhhh asks if you want to reboot the system after the patch installation or removal is completed: +o If you answer yes, the system reboots immediately. +o If you answer no, dddduuuuppppaaaattttcccchhhh returns to the appropriate menu — either installation or removal, depending on the operation. _4._1_0._2 _I_n _M_u_l_t_i_u_s_e_r _M_o_d_e 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, dddduuuuppppaaaattttcccchhhh gives you three options if a reboot is necessary: +o Reboot now +o Schedule a reboot for a later time +o Do not reboot 4-18 Patch Installation and Removal Instructions _4._1_1 _P_o_s_t-_I_n_s_t_a_l_l_a_t_i_o_n _A_c_t_i_o_n_s Once your patch kit is installed, delete the temporary directory in which you expanded the patch kit tar file. For example: #### rrrrmmmm ----rrrr ////PPPPaaaattttcccchhhhKKKKiiiittttssss 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. _4._1_2 _R_e_m_o_v_i_n_g _P_a_t_c_h_e_s To remove patches from your system , use the Patch Deletion option of the dddduuuuppppaaaattttcccchhhh Main Menu. The system must be in single-user mode to remove patches. Note that the -d option to the sssseeeettttlllldddd command is disabled for patch subsets. The following steps show how to remove patches: _C_a_u_t_i_o_n The Patch Deletion menu lists every sssseeeettttlllldddd-based patch on your system, regardless of which patch kit installed them. Therefore, if you select the AAAALLLLLLLL ooooffff tttthhhheeee aaaabbbboooovvvveeee menu item, it will remove all sssseeeettttlllldddd-based patches from your system. For example, if you chose the AAAALLLLLLLL ooooffff tttthhhheeee aaaabbbboooovvvveeee menu item when installing Patch Kit-0003 and then decide to remove those patches, you will have to specify the patch ID of all Patch Kit-0003 patches in the DDDDeeeelllleeeetttteeee PPPPaaaattttcccchhhh menu. If, instead, you select the AAAALLLLLLLL ooooffff tttthhhheeee aaaabbbboooovvvveeee menu item, then all sssseeeettttlllldddd-based patches that are installed on your system are removed, not only those from Patch Kit-0003. 1. Halt the system and bring it up in single-user mode, as described in Section 4.8.1.1. 2. Run dddduuuuppppaaaattttcccchhhh and select 2222 for patch removal: #### dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility ========================== (This dupatch session is logged in /var/adm/patch/log/session.log) Main Menu: ---------- 1) Patch Installation 2) Patch Deletion Patch Installation and Removal Instructions 4-19 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 2222 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. For example: Your name: MMMMiiiikkkkeeee Enter any notes about this operation that you would like stored for future reference. To end your input, enter a period (.) and press Return. :::: RRRReeeemmmmoooovvvviiiinnnngggg ppppaaaattttcccchhhheeeessss 6666....00000000,,,, 11112222....00000000,,,, aaaannnndddd 22222222....00000000 uuuunnnnttttiiiillll tttthhhheeee :::: ffffiiiirrrrmmmmwwwwaaaarrrreeee ccccaaaannnn bbbbeeee uuuuppppddddaaaatttteeeedddd ttttoooo tttthhhheeee pppprrrrooooppppeeeerrrr rrrreeeevvvviiiissssiiiioooonnnn.... : .... [[[[RRRReeeettttuuuurrrrnnnn]]]] 4. Select and verify the patches to be removed through the patch selection menus. Once the patch selection is done, dddduuuuppppaaaattttcccchhhh removes the selected patches and provides informational messages on the screen. The dddduuuuppppaaaattttcccchhhh session is logged to ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////sssseeeessssssssiiiioooonnnn....lllloooogggg. (See Section 2.2 for information about dddduuuuppppaaaattttcccchhhh logs.) _N_o_t_e When removing patches after incremental installations, you may see Special Instructions from previously installed patches that have since been superseded. You should ignore these instructions and instead follow any Special Instructions relating to the most current patch. 5. Review the session log to ensure the removal was successful. Note any special patch instructions, informational messages, and error messages. 6. If there are no error messages, follow the instructions for disabling the patches that are listed in the session log. Depending on the removed patches, you may need to rebuild the kernel or reboot the system. 4-20 Patch Installation and Removal Instructions Rolling Upgrade 5 TruCluster Server Version 5.0A and higher provides the infrastructure that makes a rolling upgrade possible. For more detailed information about using the rolling upgrade process to install a new operating system or TruCluster software version, see the Version 5.1 or higher _C_l_u_s_t_e_r _I_n_s_t_a_l_l_a_t_i_o_n manual. _N_o_t_e If you have not yet created your cluster, HP recommends that you patch your system first. See Section 3.4 for this time-saving procedure. This chapter provides the following information: +o An overview of the rolling upgrade process. (Section 5.1) +o A description of the rolling upgrade stages. (Section 5.2) +o The step-by-step procedure for performing a rolling upgrade on your cluster. (Section 5.3) +o How to display the status of a rolling upgrade. (Section 5.4) +o How to undo a stage. (Section 5.6) +o How to remove patches installed during a rolling upgrade. (Section 5.7) Because TruCluster Server software Version 5.1A contains some minor changes to the rolling upgrade interface, the output you see may differ slightly from the examples presented in this chapter. _5._1 _O_v_e_r_v_i_e_w A rolling upgrade is a software upgrade of a cluster that is performed while the cluster is in operation. One member at a time is rolled and returned to operation while the cluster transparently maintains a mixed-version environment for the base operating system, cluster, and Worldwide Language Support (WLS) software. Clients accessing services are not aware that a rolling upgrade is in progress. When performing a rolling upgrade, the same procedure is used for patching your system as for upgrading to a new operating system or TruCluster version. The only difference is that for a rolling patch you use the dddduuuuppppaaaattttcccchhhh utility and for a rolling upgrade you use the iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee utility during the install stage. _N_o_t_e See Chapter 2 for an overview of the dddduuuuppppaaaattttcccchhhh utility and Chapter 4 for step- by-step instructions for using dddduuuuppppaaaattttcccchhhh. A roll consists of a series of stages (described in Section 5.2) that must be performed in a fixed order. When patching a cluster, the commands that control a rolling upgrade to enforce this order are cccclllluuuu____uuuuppppggggrrrraaaaddddeeee and dddduuuuppppaaaattttcccchhhh. You can perform only one rolling upgrade at a time. You cannot start another roll until the first roll is completed. _N_o_t_e A rolling upgrade updates the file systems and disks that the cluster currently uses; it does not update the disk or disks that contain the Tru64 UNIX operating system that were used to create the cluster (the operating system on which you ran cccclllluuuu____ccccrrrreeeeaaaatttteeee). Although you can boot the original operating system in an emergency, remember that the differences between the current cluster and the original operating system increase with each roll. _5._1._1 _T_a_g_g_e_d _F_i_l_e_s A rolling upgrade updates the software on one cluster member at a time so that you can test the new software without disrupting critical services. In order to support two versions of software in the cluster during a roll, cccclllluuuu____uuuuppppggggrrrraaaaddddeeee creates a set of tagged files in the setup stage. These tagged files are copies of current files with ....OOOOlllldddd........ prepended to the file name. For example, the tagged file for the vvvvdddduuuummmmpppp command is ////ssssbbbbiiiinnnn////....OOOOlllldddd........vvvvdddduuuummmmpppp. Tagged files are created in the same file system as the original files. Each tagged file has an AdvFS property, DDDDEEEECCCC____VVVVEEEERRRRSSSSIIIIOOOONNNN____TTTTAAAAGGGG, set on it. If a member's ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb rrrroooollllllllssss____vvvveeeerrrr____llllooooooookkkkuuuupppp attribute is set to 1111, pathname resolution includes determining whether a specified filename has a ....OOOOlllldddd........_f_i_l_e_n_a_m_e copy and whether the copy has the DDDDEEEECCCC____VVVVEEEERRRRSSSSIIIIOOOONNNN____TTTTAAAAGGGG property set on it. If both conditions are met, the requested file operation is transparently diverted to use the ....OOOOlllldddd........_f_i_l_e_n_a_m_e version of the file. Note that file system operations on directories are not bound by this ....OOOOlllldddd........ restraint. For example, you will see both versions of a file listed when you issue the llllssss command of a directory on any cluster member during a rolling upgrade. The upgrade commands control when a member runs on tagged files by setting that member's ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb rrrroooollllllllssss____vvvveeeerrrr____llllooooooookkkkuuuupppp variable. The commands set the value to 1111 when the member must run on tagged files, and to 0000 when the member must not run on tagged files. The only member that never runs on tagged files 5-2 Rolling Upgrade is the lead member (the first member to roll). The following rules determine which files have tagged files automatically created for them in the setup stage: +o Tagged files are created for the following product codes: base operating system (OOOOSSSSFFFF), TruCluster software (TTTTCCCCRRRR), and Worldwide Language Support (IIIIOOOOSSSS). The subsets for each product use that product's three-letter product code as a prefix for each subset name. For example, TruCluster software subset names start with the TruCluster software three-letter product code: TTTTCCCCRRRRBBBBAAAASSSSEEEE555500005555, TTTTCCCCRRRRMMMMAAAANNNN555500005555, and TTTTCCCCRRRRMMMMIIIIGGGGRRRRAAAATTTTEEEE555500005555. +o By default, files that are associated with other layered products do not have tagged files created for them. Tagged files are created only for layered products that have been modified to support tagged files during a rolling upgrade. _C_a_u_t_i_o_n Unless a layered product's documentation specifically states that you can install a newer version of the product on the first rolled member, and that the layered product knows what actions to take in a mixed-version cluster, HP strongly recommend that you do not install either a new layered product or a new version of a currently installed layered product during a rolling upgrade. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee command provides several command options to manipulate tagged files: cccchhhheeeecccckkkk, aaaadddddddd, rrrreeeemmmmoooovvvveeee, eeeennnnaaaabbbblllleeee, and ddddiiiissssaaaabbbblllleeee. When dealing with tagged files, take the following into consideration: +o During a normal rolling upgrade you do not have to manually add or remove tagged files. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee command calls the ttttaaaaggggggggeeeedddd commands as needed to control the creation and removal of tagged files. +o The target for a cccchhhheeeecccckkkk, aaaadddddddd, or rrrreeeemmmmoooovvvveeee tagged file operation is a product code that represents an entire product. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ttttaaaaggggggggeeeedddd commands operate on all files in the specified product or products. For example, the following command verifies the correctness of all the tagged files created for the TTTTCCCCRRRR kernel layered product (the TruCluster software subsets): # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ttttaaaaggggggggeeeedddd cccchhhheeeecccckkkk TTTTCCCCRRRR If you inadvertently remove a ....OOOOlllldddd........ copy of a file, you must create tagged files for the entire layered product to re-create that one file. For example, the vvvvdddduuuummmmpppp command is in the OOOOSSSSFFFFAAAADDDDVVVVFFFFSSSS_n_n_n subset, which is part of the OOOOSSSSFFFF product. If you mistakenly remove ////ssssbbbbiiiinnnn////....OOOOlllldddd........vvvvdddduuuummmmpppp, run the following command to re-create tagged files for the entire layered product: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ttttaaaaggggggggeeeedddd aaaadddddddd OOOOSSSSFFFF Rolling Upgrade 5-3 +o The eeeennnnaaaabbbblllleeee and ddddiiiissssaaaabbbblllleeee commands enable or disable the use of tagged files by a cluster member. You do not have to use eeeennnnaaaabbbblllleeee or ddddiiiissssaaaabbbblllleeee during a normal rolling upgrade. The ddddiiiissssaaaabbbblllleeee command is useful if you have to undo the setup stage. Because no members can be running with tagged files when undoing the setup stage, you can use the ddddiiiissssaaaabbbblllleeee command to disable tagged files on any cluster member that is currently running on tagged files. For example, to disable tagged files for a member whose ID is 3m, issue the following command: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ttttaaaaggggggggeeeedddd ddddiiiissssaaaabbbblllleeee 3333 The eeeennnnaaaabbbblllleeee command is provided in case you make a mistake with the ddddiiiissssaaaabbbblllleeee command. _5._1._2 _V_e_r_s_i_o_n _S_w_i_t_c_h A version switch manages the transition of the active version to the new version of an operating system. The active version is the one that is currently in use. The purpose of a version switch in a cluster is to prevent the introduction of potentially incompatible new features until all members have been updated. For example, if a new version introduces a change to a kernel structure that is incompatible with the current structure, you do not want cluster members to use that new feature until all members have updated to the version that supports the new features. At the start of a rolling upgrade, all members' active versions are the same as their new versions. During a roll, each member's new version is updated when it rolls. After all members have rolled, the switch stage sets the active version to the new version on all members. At the completion of the upgrade, all members' active versions are once again the same as their new versions. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee command uses the vvvveeeerrrrsssswwww command (described in vvvveeeerrrrsssswwww(8)) to manage version transitions. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee command manages all the version switch activity when rolling individual members. In the switch stage, after all members have rolled, run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh command to complete the transition to the new software. _5._2 _R_o_l_l_i_n_g _U_p_g_r_a_d_e _S_t_a_g_e_s This section takes a closer look at each of the rolling upgrade stages. Figure 5-1 provides a flow chart of the tasks and stages that are required to perform a rolling upgrade. (See Section 5.3 for the rolling upgrade procedure.) _F_i_g_u_r_e _5-_1: _R_o_l_l_i_n_g _U_p_g_r_a_d_e _F_l_o_w _C_h_a_r_t 5-4 Rolling Upgrade The stages are performed in the following order: 1. Preparation stage (Section 5.2.1) 2. Setup stage (Section 5.2.2) 3. Preinstall stage (Section 5.2.3) 4. Install stage (Section 5.2.4) 5. Postinstallation stage (Section 5.2.5) 6. Roll stage (Section 5.2.6) 7. Switch stage (Section 5.2.7) 8. Clean stage (Section 5.2.8) _5._2._1 _P_r_e_p_a_r_a_t_i_o_n _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv cccchhhheeeecccckkkk sssseeeettttuuuupppp any member multiuser mode _l_e_a_d__m_e_m_b_e_r_i_d ______________________________________________________________________________ During the preparation stage, you back up all important cluster data and verify that the cluster is ready for a roll. Before beginning a rolling upgrade, do the following: 1. Back up the clusterwide root (////), ////uuuussssrrrr, and ////vvvvaaaarrrr file systems. The backups should include all member-specific files in these file systems. If the cluster has a separate iiii11118888nnnn file system, back up that file system. In addition, back up any other file systems that contain critical user or application data. _N_o_t_e If you perform an incremental or full backup of the cluster during a rolling upgrade, make sure to perform the backup on a member that is not running on tagged files. If you back up from a member that is using tagged files, you will back up the contents of the ....OOOOlllldddd........ files. Because the lead Rolling Upgrade 5-5 member never uses tagged files, you can back up the cluster from the lead member (or any other member that has rolled) during a rolling upgrade. Most sites have automated backup procedures. If you know that an automatic backup will take place while the cluster is in the middle of a rolling upgrade, make sure that backups are done on the lead member or on a member that has rolled. 2. Choose one member of the cluster as the first member to roll. This member, known as the lead member, must have direct access to the root (////), ////uuuussssrrrr, ////vvvvaaaarrrr, and if used, iiii11118888nnnn file systems. Make sure that the lead member can run any critical applications. You can test these applications after you update this member during the install stage, but before you roll any other members. If there is a problem, you can try to resolve it on this member before you continue. If there is a problem that you cannot resolve, you can undo the rolling upgrade and return the cluster to its pre-roll state. (Section 5.6 describes how to undo rolling upgrade stages.) 3. Run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv cccchhhheeeecccckkkk sssseeeettttuuuupppp _l_e_a_d__m_e_m_b_e_r_i_d command, which verifies that: - No rolling upgrade is in progress. - All members are running the same versions of the base operating system and cluster software. - No members are running on tagged files. _N_o_t_e The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv cccchhhheeeecccckkkk sssseeeettttuuuupppp _l_e_a_d__m_e_m_b_e_r_i_d command may check some — but not all — file systems for adequate space. Make sure that you manually check that your system meets the disk space requirements described later in this section. A cluster can continue to operate during a rolling upgrade or a patch because there are two copies of almost every file. (There is only one copy of some configuration files so that changes made by any member are visible to all members.) This approach makes it possible to run two different versions of the base operating system and the cluster software at the same time in the same cluster. The trade-off is that, before you start an upgrade or patch, you must make sure that there is adequate free space in each of the clusterwide root (////), ////uuuussssrrrr, and ////vvvvaaaarrrr file systems, and if there is a separate domain for the Worldwide Language Support (WLS) subsets, iiii11118888nnnn file systems. A rolling upgrade has the following disk space requirements: 5-6 Rolling Upgrade +o At least 50 percent free space in root (////), cccclllluuuusssstttteeeerrrr____rrrrooooooootttt####rrrrooooooootttt. +o At least 50 percent free space in ////uuuussssrrrr, cccclllluuuusssstttteeeerrrr____uuuussssrrrr####uuuussssrrrr. +o At least 50 percent free space in ////vvvvaaaarrrr, cccclllluuuusssstttteeeerrrr____vvvvaaaarrrr####vvvvaaaarrrr, plus an additional 425 MB to hold the subsets for the new version of the base operating system. +o If there is a separate iiii11118888nnnn domain, at least 50 percent free space in that file system. +o See the _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s included with each patch kit to find out the amount of space you will need to install the patch kit for your system. If a file system needs more free space, use AdvFS utilities such as aaaaddddddddvvvvoooollll to add volumes to domains as needed. For information on managing AdvFS domains, see the _A_d_v_F_S _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual. Note that you can expand the clusterwide root (////) domain. _5._2._2 _S_e_t_u_p _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp any member multiuser mode _l_e_a_d__m_e_m_b_e_r_i_d ______________________________________________________________________________ The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp _l_e_a_d__m_e_m_b_e_r_i_d command performs the following tasks: _C_a_u_t_i_o_n Make sure your system meets the space requirements described in Section 5.2.1 before issuing the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp command. +o Makes the ----vvvv cccchhhheeeecccckkkk sssseeeettttuuuupppp tests listed in Section 5.2.1. +o Asks whether you are going to patch (run dddduuuuppppaaaattttcccchhhh) or update (run iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee) your cluster. +o Creates the log file ////cccclllluuuusssstttteeeerrrr////aaaaddddmmmmiiiinnnn////cccclllluuuu____uuuuppppggggrrrraaaaddddeeee....lllloooogggg. +o Makes on-disk backup copies of the lead member's member-specific files. Rolling Upgrade 5-7 +o Creates the mandatory set of tagged files (copies of existing files, but with ....OOOOlllldddd........ prepended to the file name) for the OOOOSSSSFFFF (base), TTTTCCCCRRRR (cluster), and IIIIOOOOSSSS (Worldwide Language Support) products. _C_a_u_t_i_o_n If, for any reason, during an upgrade you need to create ....OOOOlllldddd........ files for a layered product, see Section 5.1.1. +o Sets the ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb variable rrrroooollllllllssss____vvvveeeerrrr____llllooooooookkkkuuuupppp====1111 on all members except the lead member. When rrrroooollllllllssss____vvvveeeerrrr____llllooooooookkkkuuuupppp====1111, a member uses the tagged files. As a result, the lead member can upgrade while the remaining members run on the ....OOOOlllldddd........ files from the current release. +o Prompts you to reboot all cluster members except the lead member. When the sssseeeettttuuuupppp command completes, reboot these members (one at a time so that the cluster can maintain quorum). This reboot is required for each member that uses tagged files in the mixed-version cluster. When the reboots complete, all members except the lead member use tagged files. _5._2._3 _P_r_e_i_n_s_t_a_l_l _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ cccclllluuuu____uuuuppppggggrrrraaaaddddeeee pppprrrreeeeiiiinnnnssssttttaaaallllllll lead member multiuser mode ______________________________________________________________________________ The purpose of the preinstall stage is to verify that the cluster is ready for the lead member to run the iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee or dddduuuuppppaaaattttcccchhhh commands and, if the upgrade includes update installation, to copy the new TruCluster software kit so that the kit will be available during the install stage. If you will perform an update installation when you perform the step-by-step upgrade procedure in Section 5.3, remember to mount the new TruCluster software kit before you run the pppprrrreeeeiiiinnnnssssttttaaaallllllll command. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee pppprrrreeeeiiiinnnnssssttttaaaallllllll command performs the following tasks: +o Verifies that the command is being run on the lead member, that the lead member is not running on tagged files, and that any other cluster members that are up are running on tagged files. 5-8 Rolling Upgrade +o Verifies that tagged files are present, that they match their product's inventory files, and that each tagged file's AdvFS property is set correctly. (This process can take a while, but not as long as it does to create the tagged files in the setup stage.) +o If you are performing a rolling upgrade, cccclllluuuu____uuuuppppggggrrrraaaaddddeeee pppprrrreeeeiiiinnnnssssttttaaaallllllll prompts you for the location of the new TruCluster software kit, and then copies the kit to ////vvvvaaaarrrr////aaaaddddmmmm////uuuuppppddddaaaatttteeee////TTTTrrrruuuuCCCClllluuuusssstttteeeerrrrKKKKiiiitttt on the lead member so that the kit will be available to the iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee command during the install stage. (The iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee command copies the operating system kit to ////vvvvaaaarrrr////aaaaddddmmmm////uuuuppppddddaaaatttteeee////OOOOSSSSKKKKiiiitttt during the install stage.) _C_a_u_t_i_o_n The files in ////vvvvaaaarrrr////aaaaddddmmmm////uuuuppppddddaaaatttteeee are critical to the roll process. Do not remove or modify files in this directory. Doing so can cause a rolling upgrade to fail. _5._2._4 _I_n_s_t_a_l_l _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee lead member single-user mode dddduuuuppppaaaattttcccchhhh lead member single-user mode or multiuser ______________________________________________________________________________ The install stage starts when the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee pppprrrreeeeiiiinnnnssssttttaaaallllllll command completes, and continues until you run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll command. The lead member must be in single-user mode to run the iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee command, and single-user mode is recommended for the dddduuuuppppaaaattttcccchhhh command. When taking the system to single-user mode, you must halt the system and then boot it to single-user mode. When the system is in single-user mode, run the bbbbcccchhhheeeecccckkkkrrrrcccc and iiiinnnniiiitttt -s commands before you run either the iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee or dddduuuuppppaaaattttcccchhhh command. See the Tru64 UNIX _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information on how to use these commands. In the install stage, you can perform one of the following: Rolling Upgrade 5-9 +o An update installation: iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee +o A patch: dddduuuuppppaaaattttcccchhhh _N_o_t_e If you run cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ssssttttaaaattttuuuussss after running iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee, cccclllluuuu____uuuuppppggggrrrraaaaddddeeee will print a line indicating that the install stage is complete. However, the install stage is not complete until you run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll command. _5._2._5 _P_o_s_t_i_n_s_t_a_l_l_a_t_i_o_n _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll lead member multiuser mode ______________________________________________________________________________ The postinstallation stage verifies that the lead member has completed an update installation, a patch, or both. If an update installation was performed, cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll verifies that the lead member has rolled to the new version of the base operating system. _5._2._6 _R_o_l_l _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ cccclllluuuu____uuuuppppggggrrrraaaaddddeeee rrrroooollllllll member being rolled single-user mode ______________________________________________________________________________ The lead member was upgraded in the install stage. The remaining members are upgraded one at a time in the roll stage. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee rrrroooollllllll command performs the following tasks: 5-10 Rolling Upgrade +o Verifies that the member is not the lead member, that the member has not already been rolled, and that the member is in single-user mode. +o Backs up the member's member-specific files. +o Sets up the iiiitttt(8) scripts that will be run on reboot to perform the roll. +o Reboots the member. During this boot, the iiiitttt scripts roll the member, build a customized kernel, and reboot with the customized kernel. _5._2._7 _S_w_i_t_c_h _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh any member multiuser mode ______________________________________________________________________________ The switch stage sets the active version of the software to the new version, which results in turning on any new features that had been deliberately disabled during the rolling upgrade. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh command performs the following tasks: +o Verifies that all members have rolled, that all members are running the same versions of the base operating system and cluster software, and that no members are running on tagged files. +o Sets the new version ID in each member's ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb file and running kernel. +o Sets the active version to the new version for all cluster members. _N_o_t_e After the switch stage completes, you must reboot each member of the cluster, one at a time. Rolling Upgrade 5-11 _5._2._8 _C_l_e_a_n _S_t_a_g_e ______________________________________________________________________________ CCCCoooommmmmmmmaaaannnndddd WWWWhhhheeeerrrreeee RRRRuuuunnnn RRRRuuuunnnn LLLLeeeevvvveeeellll ______________________________________________________________________________ cccclllluuuu____uuuuppppggggrrrraaaaddddeeee cccclllleeeeaaaannnn any member multiuser mode ______________________________________________________________________________ The clean stage cleans up the files and directories that were used for the rolling upgrade. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee cccclllleeeeaaaannnn command performs the following tasks: +o Verifies that the switch stage has completed, that all members are running the same versions of the base operating system and cluster software, and that no members are running on tagged files. +o Removes all tagged ....OOOOlllldddd........ files. +o Removes any on-disk backup archives that cccclllluuuu____uuuuppppggggrrrraaaaddddeeee created. +o Deletes the following directories: ////vvvvaaaarrrr////aaaaddddmmmm////uuuuppppddddaaaatttteeee////TTTTrrrruuuuCCCClllluuuusssstttteeeerrrrKKKKiiiitttt and ////vvvvaaaarrrr////aaaaddddmmmm////cccclllluuuu____uuuuppppggggrrrraaaaddddeeee////OOOOSSSSKKKKiiiitttt. +o If an update installation was performed, gives you the option of running the Update Administration Utility (uuuuppppddddaaaaddddmmmmiiiinnnn) to manage the files that were saved during an update installation. +o Creates an archive directory for this upgrade, ////cccclllluuuusssstttteeeerrrr////aaaaddddmmmmiiiinnnn////cccclllluuuu____uuuuppppggggrrrraaaaddddeeee////hhhhiiiissssttttoooorrrryyyy////_b_a_s_e__O_S__v_e_r_s_i_o_n, and moves the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee....lllloooogggg file to the archive directory. _5._3 _R_o_l_l_i_n_g _U_p_g_r_a_d_e _P_r_o_c_e_d_u_r_e In the following procedure, unless otherwise stated, run commands in multiuser mode. _N_o_t_e If you have not yet created your cluster, it is recommended that you patch the operating system and TruCluster software before performing a rolling upgrade. See Section 3.4 for information. 5-12 Rolling Upgrade _N_o_t_e During a rolling upgrade, do not use the ////uuuussssrrrr////ssssbbbbiiiinnnn////sssseeeettttlllldddd command to add or delete any of the following subsets: +o Base Operating System subsets (those with the prefix OOOOSSSSFFFF). +o TruCluster Server subsets (those with the prefix TTTTCCCCRRRR). +o Worldwide Language Support (WLS) subsets (those with the prefix IIIIOOOOSSSSWWWWWWWW). Adding or deleting these subsets during a rollng upgrade creates inconsistencies in the tagged files. Some stages of a rolling upgrade take longer to complete than others. Table 5-1 lists the approximate time it takes to complete each stage. _T_a_b_l_e _5-_1: _T_i_m_e _E_s_t_i_m_a_t_i_o_n_s _f_o_r _a _R_o_l_l_i_n_g _U_p_g_r_a_d_e ______________________________________________________________________________ SSSSttttaaaaggggeeee DDDDuuuurrrraaaattttiiiioooonnnn ______________________________________________________________________________ Preparation Not under program control. Setup 45 - 120 minutes. [Footnote 1] Preinstall 15 - 30 minutes. [Footnote 1] Install The same as installing a patch kit on a single system. Approximately 35 minutes, depending upon the size of the patch kit. Postinstall Less than 1 minute. Roll (per member) Patch: less than 5 minutes. Update installation: about the same amount of time it takes to add a member. Switch Less than 1 minute. Clean 30 - 90 minutes. [Footnote 1] ______________________________________________________________________________ 1. Prepare the cluster (see Section 5.2.1): Rolling Upgrade 5-13 1. Back up the cluster. 2. Choose a cluster member to be the lead member (the first member to roll). The examples in this procedure use the member whose mmmmeeeemmmmbbbbeeeerrrriiiidddd is 2222 as the lead member. The member's host name is pppprrrroooovvvvoooolllloooonnnneeee. 3. Make sure that your system contains the required space in all file systems as described in Section 5.2.1. If a file system needs more free space, use AdvFS utilities such as aaaaddddddddvvvvoooollll to add volumes to domains as needed. For information on managing AdvFS domains, see the _A_d_v_F_S _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual. Note that the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv cccchhhheeeecccckkkk sssseeeettttuuuupppp _l_e_a_d__m_e_m_b_e_r_i_d command may check some — but not all — file systems for adequate space. Make sure that you manually check that your system meets the disk space requirements described in Section 5.2.1. 4. On any member, run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv cccchhhheeeecccckkkk sssseeeettttuuuupppp _l_e_a_d__m_e_m_b_e_r_i_d command to determine whether the cluster is ready for an upgrade. For example: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv cccchhhheeeecccckkkk sssseeeettttuuuupppp 2222 2. Perform the setup stage (Section 5.2.2). On any member, run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp _l_e_a_d__m_e_m_b_e_r_i_d command. For example: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp 2222 _C_a_u_t_i_o_n If any file system fails to meet the minimum space requirements, the program will fail and generate an error message similar to the following: *** Error *** The tar commands used to create tagged files in the '/' file system have reported the following errors and warnings: NOTE: CFS: File system full: / tar: sbin/lsm.d/raid5/volsd : No space left on device tar: sbin/lsm.d/raid5/volume : No space left on device NOTE: CFS: File system full: / \&.NOTE: CFS: File system full: / If you receive this message, run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----uuuunnnnddddoooo sssseeeettttuuuupppp command, free up the required amount of space on the affected file systems, and then rerun the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp command. During the setup stage, cccclllluuuu____uuuuppppggggrrrraaaaddddeeee asks whether you are performing a update installation or a patch. However, the wording of the prompts in the Version 5.0A command is somewhat ambiguous: 5-14 Rolling Upgrade Are you running the clu_upgrade command to upgrade to a new version of the base operating system and cluster software? [yes]: Are you running the clu_upgrade command in order to apply a rolling patch? [yes] The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee command does not display the second prompt until it receives an answer for the first. An administrator might be tempted to answer yes to the ............ uuuuppppggggrrrraaaaddddeeee ttttoooo aaaa nnnneeeewwww vvvveeeerrrrssssiiiioooonnnn ............ prompt when performing a rolling upgrade to patch the cluster because a patch is an upgrade to new software. However, if you see these prompts, answer yes to the first prompt only if you plan to run iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee during the install stage. _N_o_t_e: _N_o _W_L_S _a_n_d _D_i_s_k _S_p_a_c_e Additional space is required in the cccclllluuuusssstttteeeerrrr____rrrrooooooootttt domain for backing up member files on clusters without Worldwide Language Support (WLS). If no space is available, the following message is displayed: *** Error *** There is no space available in the root (/), /usr, or /var file systems to back up member ''???'' member-specific files. Increase the available disk space on one of these file systems and rerun this stage of the upgrade. The minimum required available space in the cccclllluuuusssstttteeeerrrr____rrrrooooooootttt domain must be greater than the sum of all of the member directories in the root (////), ////uuuussssrrrr, or ////vvvvaaaarrrr file systems. To view the available space in the cccclllluuuusssstttteeeerrrr____rrrrooooooootttt domain, enter the following command: # ddddffff //// For example: #### ddddffff //// Filesystem 512-blocks Used Available Capacity Mounted on cluster_root#root 524288 175710 330512 35% / To calculate the minimum required value, enter the following command: # kkkksssshhhh ''''dddduuuu ----ssss {{{{,,,,////uuuussssrrrr,,,,////vvvvaaaarrrr}}}}////cccclllluuuusssstttteeeerrrr////mmmmeeeemmmmbbbbeeeerrrrssss////mmmmeeeemmmmbbbbeeeerrrr????****////'''' |||| \\\\ aaaawwwwkkkk ''''{{{{mmmmiiiinnnniiiimmmmuuuummmm++++====$$$$1111}}}};;;; EEEENNNNDDDD{{{{pppprrrriiiinnnntttt mmmmiiiinnnniiiimmmmuuuummmm}}}}'''' For example: # kkkksssshhhh ''''dddduuuu ----ssss {{{{,,,,////uuuussssrrrr,,,,////vvvvaaaarrrr}}}}////cccclllluuuusssstttteeeerrrr////mmmmeeeemmmmbbbbeeeerrrrssss////mmmmeeeemmmmbbbbeeeerrrr????****////'''' |||| \\\\ >>>> aaaawwwwkkkk ''''{{{{mmmmiiiinnnniiiimmmmuuuummmm++++====$$$$1111}}}};;;; EEEENNNNDDDD{{{{pppprrrriiiinnnntttt mmmmiiiinnnniiiimmmmuuuummmm}}}}'''' 679030 The example indicates that cccclllluuuusssstttteeeerrrr____rrrrooooooootttt domain needs 348518 more blocks (679030 minus 330512), or approximately 175 MB of disk space. Use the aaaaddddddddvvvvoooollll command to add additional volumes to the cccclllluuuusssstttteeeerrrr____rrrrooooooootttt domain. Rolling Upgrade 5-15 3. When asked if you want to continue the cluster upgrade, accept the default of yes: This is the cluster upgrade program. You have indicated that you want to perform the 'setup' stage of the upgrade. Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Are you running the clu_upgrade command to upgrade to a new version of the base operating system and cluster software? [yes]: nnnnoooo Are you running the clu_upgrade command to apply a rolling patch? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Note that these prompts will change if you run the upgrade to its conclusion and then rerun it to remove patches. See Section 5.7 for more information (including the prompts you will see). 4. One at a time, reboot all cluster members except the lead member. 5. Perform the preinstall stage (Section 5.2.3). _N_o_t_e If you plan to run iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee in the install stage, mount the device or directory that contains the new TruCluster software kit before running cccclllluuuu____uuuuppppggggrrrraaaaddddeeee pppprrrreeeeiiiinnnnssssttttaaaallllllll. The pppprrrreeeeiiiinnnnssssttttaaaallllllll command will copy the kit to the ////vvvvaaaarrrr////aaaaddddmmmm////uuuuppppddddaaaatttteeee////TTTTrrrruuuuCCCClllluuuusssstttteeeerrrrKKKKiiiitttt directory. On the lead member, run the following command: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee pppprrrreeeeiiiinnnnssssttttaaaallllllll 6. Manually relocate CAA services from the lead member to another cluster member before performing the install stage. For example: # ////uuuussssrrrr////ssssbbbbiiiinnnn////ccccaaaaaaaa____rrrreeeellllooooccccaaaatttteeee ----ssss _l_e_a_d__m_e_m_b_e_r -c _n_o_n__l_e_a_d__m_e_m_b_e_r 7. Perform the install stage (Section 5.2.4). _N_o_t_e If while running dddduuuuppppaaaattttcccchhhh you encounter a situation in which the lead member falls into an unrecoverable state, you will have to run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo iiiinnnnssssttttaaaallllllll command. Any subsequent patch installations may need to be enabled via the dddduuuuppppaaaattttcccchhhh baseline procedure. See Section 4.7 for information about baselining. See Section 5.6 for information about undoing a rolling upgrade stage. You can patch a cluster or update cluster and operating system software. You can perform a rolling upgrade to patch a cluster in either single-user 5-16 Rolling Upgrade mode, which is recommended, or in multiuser mode: - To patch the system in single-user mode, follow the instructions in Section 4.8.1.1. - To patch the system in multiuser mode, run the dddduuuuppppaaaattttcccchhhh command. See Chapter 4 for information about using the dddduuuuppppaaaattttcccchhhh utility. 1. Run the llllmmmmffff rrrreeeesssseeeetttt command: # llllmmmmffff rrrreeeesssseeeetttt If you are performing a roll that includes both an upgrade and a patch, do the update installation first and then the patch installation. After the lead member performs its final reboot with its new custom kernel, perform the following manual tests before you roll any additional members: Verify that the newly rolled lead member can serve the shared root (////) file system. 1. Use the ccccffffssssmmmmggggrrrr command to determine which cluster member is currently serving the root file system. For example: # ccccffffssssmmmmggggrrrr ----vvvv ----aaaa sssseeeerrrrvvvveeeerrrr //// Domain or filesystem name = / Server Name = polishham Server Status : OK 2. Relocate the root (////) file system to the lead member. For example: # ccccffffssssmmmmggggrrrr ----hhhh ppppoooolllliiiisssshhhhhhhhaaaammmm ----rrrr ----aaaa SSSSEEEERRRRVVVVEEEERRRR====pppprrrroooovvvvoooolllloooonnnneeee //// Verify that the lead member can serve applications to clients. Make sure that the lead member can serve all important applications that the cluster makes available to its clients. You decide how and what to test. Thoroughly exercise all critical applications and satisfy yourself that the lead member can serve these applications to clients before continuing the roll. For example, you can: 1. Manually relocate CAA services to the lead member. For example, to relocate an application resource named cccclllloooocccckkkk to lead member pppprrrroooovvvvoooolllloooonnnneeee: # ccccaaaaaaaa____rrrreeeellllooooccccaaaatttteeee cccclllloooocccckkkk ----cccc pppprrrroooovvvvoooolllloooonnnneeee Rolling Upgrade 5-17 2. Temporarily modify the default cluster alias attributes for the lead member so that it handles routing for the alias and serves all client requests that are directed to the alias. For example: # cccclllluuuuaaaammmmggggrrrr ----aaaa aaaalllliiiiaaaassss====DDDDEEEEFFFFAAAAUUUULLLLTTTTAAAALLLLIIIIAAAASSSS,,,,rrrrpppprrrriiii====111100000000,,,,sssseeeellllpppp====111100000000 # cccclllluuuuaaaammmmggggrrrr ----rrrr ssssttttaaaarrrrtttt The lead member is now handling all traffic that is addressed to the default cluster alias. (You can use the aaaarrrrpppp ----aaaa command to verify that the lead member has the ppppeeeerrrrmmmmaaaannnneeeennnntttt ppppuuuubbbblllliiiisssshhhheeeedddd entry for the default cluster alias.) From another member or from an outside client, use services such as tttteeeellllnnnneeeetttt and ffffttttpppp to verify that the lead member can handle alias traffic. Test client access to all important services that the cluster provides. When you are satisfied, reset the alias attributes on the lead member to their original values. 8. Perform the postinstallation stage (Section 5.2.5). On the lead member, run: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll 9. Perform the roll stage (Section 5.2.6). One at a time, on each member of the cluster that has not rolled, do the following: 1. Manually relocate CAA services from the member to another cluster member before performing the roll stage. For example: # ////uuuussssrrrr////ssssbbbbiiiinnnn////ccccaaaaaaaa____rrrreeeellllooooccccaaaatttteeee ----ssss _m_e_m_b_e_r__t_o__r_o_l_l \ -c _a_n_o_t_h_e_r__m_e_m_b_e_r 2. Take the member to single-user mode by first halting the member and then booting to single-user mode. Before halting the member, make sure that the cluster can maintain quorum without the member's vote. For information about maintaining quorum when shutting down a member, see the chapter on Managing Cluster Members in the Version 5.1A _C_l_u_s_t_e_r _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual. # ////ssssbbbbiiiinnnn////sssshhhhuuuuttttddddoooowwwwnnnn ----hhhh nnnnoooowwww _N_o_t_e Halting and booting the system ensures that it provides the minimal set of services to the cluster and that the running cluster has a minimal reliance on the member running in single-user mode. In particular, halting the member satisfies services that require the cluster member to 5-18 Rolling Upgrade have a status of DOWN before completing a service failover. If you do not first halt the cluster member, there is a high probability that services will not fail over as expected. 3. Boot the member: >>> bbbbooooooootttt ----ffffllll ssss 4. When the system reaches single-user mode, run the iiiinnnniiiitttt ssss, bbbbcccchhhheeeecccckkkkrrrrcccc, kkkkllllooooaaaaddddssssrrrrvvvv, and llllmmmmffff rrrreeeesssseeeetttt commands. For example: # ////ssssbbbbiiiinnnn////iiiinnnniiiitttt ssss # ////ssssbbbbiiiinnnn////bbbbcccchhhheeeecccckkkkrrrrcccc # ////ssssbbbbiiiinnnn////kkkkllllooooaaaaddddssssrrrrvvvv # ////uuuussssrrrr////ssssbbbbiiiinnnn////llllmmmmffff rrrreeeesssseeeetttt 5. Roll the member: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee rrrroooollllllll When the member boots its new kernel, it has completed its roll and is no longer running on tagged files. Continue to roll members until all members of the cluster have rolled. _N_o_t_e: /_v_a_r _D_i_s_k _S_p_a_c_e The following messages might be displayed while running the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee rrrroooollllllll command: Backing up member-specific data for member: _n ...NOTE: CFS: File system full: /var tar: /dev/tty Unavailable *** Error *** An error was detected while backing up member '_n' \ member-specific files. Additional space in the cccclllluuuusssstttteeeerrrr____vvvvaaaarrrr domain is required. To view the available space in the cccclllluuuusssstttteeeerrrr____vvvvaaaarrrr domain, enter the following command: # ddddffff ////vvvvaaaarrrr To calculate the required value, enter the following command: # kkkksssshhhh ''''dddduuuu ----ssss {{{{,,,,////uuuussssrrrr,,,,////vvvvaaaarrrr}}}}////cccclllluuuusssstttteeeerrrr////mmmmeeeemmmmbbbbeeeerrrrssss////mmmmeeeemmmmbbbbeeeerrrr????****////'''' |||| \\\\ aaaawwwwkkkk ''''{{{{mmmmiiiinnnniiiimmmmuuuummmm++++====$$$$1111}}}};;;; EEEENNNNDDDD{{{{pppprrrriiiinnnntttt mmmmiiiinnnniiiimmmmuuuummmm}}}}'''' Use the aaaaddddddddvvvvoooollll command to add additional volumes to the cccclllluuuusssstttteeeerrrr____vvvvaaaarrrr domain. Rolling Upgrade 5-19 10.Perform the switch stage (Section 5.2.7). After all members have rolled, run the following command on any member to enable any new software features that were deliberately disabled until all members have rolled: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh 11.One at a time, reboot each member of the cluster. 12.Perform the clean stage (Section 5.2.8). Run the following command on any member to remove the tagged (....OOOOlllldddd........) files from the cluster and complete the upgrade. # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee cccclllleeeeaaaannnn _5._4 _D_i_s_p_l_a_y_i_n_g _t_h_e _S_t_a_t_u_s _o_f _a _R_o_l_l_i_n_g _U_p_g_r_a_d_e The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee command provides the following options for displaying the status of a rolling upgrade or patch. You can run status commands at any time. _N_o_t_e During a roll, there might be two versions of the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee in the cluster — an older version used by members that have not yet rolled, and a newer version (if included in the update distribution or patch kit). When checking status, the information that is displayed by the ssssttttaaaattttuuuussss command might differ depending on whether the command is run on a member that has rolled. Therefore, if you run the ssssttttaaaattttuuuussss command on two members, do not be surprised if the format and content of the displayed output are not the same. +o To display the overall status of a rolling upgrade or patch: cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv or cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv ssssttttaaaattttuuuussss. _N_o_t_e If you run cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ssssttttaaaattttuuuussss after running iiiinnnnssssttttaaaalllllllluuuuppppddddaaaatttteeee, cccclllluuuu____uuuuppppggggrrrraaaaddddeeee will print a line indicating that the install stage is complete. However, the install stage is not complete until you run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll command. +o To determine whether you can run a stage: cccclllluuuu____uuuuppppggggrrrraaaaddddeeee cccchhhheeeecccckkkk [[[[_s_t_a_g_e]. If you do not specify a _s_t_a_g_e, the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee tests whether the next stage can be run. 5-20 Rolling Upgrade +o To determine whether a stage has started or completed: cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ssssttttaaaarrrrtttteeeedddd _s_t_a_g_e and cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ccccoooommmmpppplllleeeetttteeeedddd _s_t_a_g_e. +o To determine whether a member has rolled: cccclllluuuu____uuuuppppggggrrrraaaaddddeeee cccchhhheeeecccckkkk rrrroooollllllll _m_e_m_b_e_r_i_d. +o To verify whether tagged files have been created for a layered product: cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ttttaaaaggggggggeeeedddd cccchhhheeeecccckkkk [[[[_p_r_o_d__c_o_d_e [_p_r_o_d__c_o_d_e \&...]]. If you do not specify a product code, cccclllluuuu____uuuuppppggggrrrraaaaddddeeee inspects all tagged files in the cluster. _5._5 _I_n_s_t_a_l_l_i_n_g _M_u_l_t_i_p_l_e _P_a_t_c_h _K_i_t_s During the install stage you can install multiple patch kits. For example, you could run dddduuuuppppaaaattttcccchhhh to install an inaugural patch kit (such as Patch Kit 0001 for Version 5.1A) and then run dddduuuuppppaaaattttcccchhhh again to install an Early Release Patch (ERP) Kit. The benefit of installing multiple patch kits is the time you save by not having to run the rolling upgrade procedure multiple times. You should be aware, however, that installing multiple patch kits could make troubleshooting more difficult if you subsequently experience a problem with your system. Prior to issuing the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh command, you can remove any patches from the last of the multiple patch kits you installed. See Section 4.12 for information about removing patches. _5._6 _U_n_d_o_i_n_g _a _S_t_a_g_e The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo command provides the ability to undo a rolling upgrade that has not completed the switch stage. You can undo any stage except the switch stage and the clean stage. _N_o_t_e See Section 5.7 for information about deleting patches installed during a rolling upgrade. To undo a stage, use the uuuunnnnddddoooo command with the stage that you want to undo. The cccclllluuuu____uuuuppppggggrrrraaaaddddeeee command determines whether the specified stage is a valid stage to undo. Table 5-2 outlines the requirements for undoing a stage: _N_o_t_e If while running dddduuuuppppaaaattttcccchhhh you encounter a situation in which the lead member falls into an unrecoverable state, you will have to run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo iiiinnnnssssttttaaaallllllll command. Any subsequent patch installations may need to be enabled via the dddduuuuppppaaaattttcccchhhh baseline procedure. See Section 4.7 for information about baselining. _T_a_b_l_e _5-_2: _U_n_d_o_i_n_g _a _S_t_a_g_e Rolling Upgrade 5-21 ______________________________________________________________________________ SSSSttttaaaaggggeeee ttttoooo UUUUnnnnddddoooo CCCCoooommmmmmmmaaaannnndddd CCCCoooommmmmmmmeeeennnnttttssss ______________________________________________________________________________ Setup cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo sssseeeettttuuuupppp You must run this command on the lead member. In addition, no members can be running on tagged files when you undo the setup stage. Before you undo the setup stage, use the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----vvvv ssssttttaaaattttuuuussss command to determine which members are running on tagged files. Then use the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ttttaaaaggggggggeeeedddd ddddiiiissssaaaabbbblllleeee _m_e_m_b_e_r_i_d command to disable tagged files on those members. When no members are running on tagged files, run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo sssseeeettttuuuupppp command on the lead member. Preinstall cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo pppprrrreeeeiiiinnnnssssttttaaaallllllll You must run this command on the lead member. Install cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo iiiinnnnssssttttaaaallllllll When patching a cluster, perform this operation only in a situations where the lead member is in an unrecoverable state. If the lead member is not in an unrecoverable state, use the dddduuuuppppaaaattttcccchhhh utility to undo a patching operation, as described in Section 5.7. If you do need to run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo iiiinnnnssssttttaaaallllllll command, you can run it on any member except the lead member. Halt the lead member. Then run the command on any member that has access to the halted lead member's boot disk. When the command completes, boot the lead member. 5-22 Rolling Upgrade Postinstall cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo ppppoooossssttttiiiinnnnssssttttaaaallllllll You must run this command on the lead member. Roll cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo rrrroooollllllll You can run this command on _m_e_m_b_e_r_i_d any member except the member whose roll is being undone. Halt the member whose roll stage is being undone. Then run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo rrrroooollllllll _m_e_m_b_e_r_i_d command on any other member that has access to the halted member's boot disk. When the command completes, boot the halted member. The member will now be using tagged files. ______________________________________________________________________________ _N_o_t_e You might see the following error message when running the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo ppppoooossssttttiiiinnnnssssttttaaaallllllll command: *** Error *** The 'undo' option cannot be run at the 'postinstall' stage, either because the next stage has already been started or because the stage specified for undo has not been started. If you see the message, remove the following file before running the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee uuuunnnnddddoooo ppppoooossssttttiiiinnnnssssttttaaaallllllll command: # rrrrmmmm ////cccclllluuuusssstttteeeerrrr////aaaaddddmmmmiiiinnnn////cccclllluuuu____uuuuppppggggrrrraaaaddddeeee////rrrroooollllllll....ssssttttaaaarrrrtttteeeedddd _5._7 _R_e_m_o_v_i_n_g _P_a_t_c_h_e_s _I_n_s_t_a_l_l_e_d _D_u_r_i_n_g _a _R_o_l_l_i_n_g _U_p_g_r_a_d_e The following sections describe how to remove or reinstall patches during a rolling upgrade. _5._7._1 _C_a_u_t_i_o_n _o_n _R_e_m_o_v_i_n_g _V_e_r_s_i_o_n _S_w_i_t_c_h_e_d _P_a_t_c_h_e_s When removing version switched patches on a cluster, do not remove version switched patches that were successfully installed in a previous rolling upgrade. This situation can occur because more than one patch subset may contain the same version switched patch. Although both the new and old patches can be removed during a roll, only the most recently installed, newer version switched patch can be properly removed. Rolling Upgrade 5-23 The older version switched patch can only be properly removed according to the documented procedure associated with that patch. This usually requires running some program before beginning the rolling upgrade to remove the patch. If you accidentally remove the older version switched patch, the rolling upgrade will most likely fail on the switch stage. To correct this situation, you will have to undo the upgrade by undoing all the stages up to and including the "install" stage. You will then need to reinstall the original version switched patch from the original patch kit that contained it. _5._7._2 _S_t_e_p_s _P_r_i_o_r _t_o _t_h_e _S_w_i_t_c_h _S_t_a_g_e At any time prior to issuing the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh command, you can remove some or all of the patches you installed during the rolling upgrade by returning to the install stage, rerunning dddduuuuppppaaaattttcccchhhh, and selecting the PPPPaaaattttcccchhhh DDDDeeeelllleeeettttiiiioooonnnn item in the Main Menu. See Section 4.12 for information about removing patches with dddduuuuppppaaaattttcccchhhh. You can also reinstall some or all of the patches you removed by rerunning dddduuuuppppaaaattttcccchhhh. After you are done running dddduuuuppppaaaattttcccchhhh, you can then proceed to the postinstall stage by running the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll command on the lead member. See Section 5.6 for information about undoing any of the rolling upgrade stages. _5._7._3 _S_t_e_p_s _f_o_r _A_f_t_e_r _t_h_e _S_w_i_t_c_h _S_t_a_g_e To remove patches after you have issued the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh command, you will have to complete the current rolling upgrade procedure and then rerun the procedure from the beginning (starting with the setup stage). When you run the install stage, you must bring down your system to single-user mode as described in steps 1 through 6 of Section 4.8.1.1. When you rerun dddduuuuppppaaaattttcccchhhh (step 7), select the PPPPaaaattttcccchhhh DDDDeeeelllleeeettttiiiioooonnnn item in the Main Menu. See Section 4.12 for information about removing patches with dddduuuuppppaaaattttcccchhhh. If the patch uses the version switch, you can still remove the patch, even after you have issued the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee switch command. Do this as follows: 1. Complete the current rolling upgrade procedure. 2. Undo the patch that uses the version switch by following the instructions in the release note for that patch. Note that the last step to undo the patch will require a shutdown of the entire cluster. 3. Rerun the rolling upgrade procedure from the beginning (starting with the setup stage). When you rerun dddduuuuppppaaaattttcccchhhh, select the PPPPaaaattttcccchhhh DDDDeeeelllleeeettttiiiioooonnnn item in the Main Menu. 5-24 Rolling Upgrade Use the ggggrrrreeeepppp command to learn which patches use the version switch. For example, in the C shell: For information about version switches, see Section 5.1.2. _N_o_t_e If you rerun the rolling upgrade procedure to remove patches, the prompts you receive during the setup stage will be different from those issued during the initial rolling upgrade. Those prompts will look as follows: Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] What type of upgrade will be performed? 1) Rolling upgrade using the installupdate command 2) Rolling patch using the dupatch command 3) Both a rolling upgrade and a rolling patch 4) Exit cluster software upgrade Enter your choice: 2222 The sample installation in Section B.2 shows the prompts you will see during the initial rolling upgrade. Rolling Upgrade 5-25 No-Roll Patching 6 The no-roll patch process lets you install patches on a cluster without performing a rolling upgrade. This chapter provides the following information: +o An overview of the no-roll patch process +o A step-by-step description of the process as it differs from a normal dddduuuuppppaaaattttcccchhhh session +o Throwing the version switch +o How to remove patches from a cluster using the no-roll patch method _N_o_t_e The no-roll technology is included in Rev. 34-00 and higher of the dddduuuuppppaaaattttcccchhhh utility. You can find the revision number on the first output line you see when you run dddduuuuppppaaaattttcccchhhh (see the example in Section 6.2). The first kit that includes this technology was issued in April 2002. _6._1 _O_v_e_r_v_i_e_w A rolling upgrade lets you perform a software upgrade on a cluster while maintaining high availability of the cluster. To provide this high availability, a certain amount of setup work is required to build tagged files and to reboot the cluster members to use the tagged files. This can take a considerable amount of time. However, if you have a mission-critical environment and want to use a patch method that applies patches quickly, minimizes down time of the cluster, and reduces the number of reboots required, you might want to use the no-roll patch process. This process patches your cluster in one operation that requires only one or two reboots of the whole cluster to complete the operation. You will need the second reboot only if you install a patch that contains a version switch (see Section 6.3). The no-roll patch process is a modification of dddduuuuppppaaaattttcccchhhh; that is, all patches are installed or removed entirely using the dddduuuuppppaaaattttcccchhhh utility, as opposed to the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee and dddduuuuppppaaaattttcccchhhh utilities used in the rolling upgrade procedure. The no-roll process conducts significantly fewer operations than the rolling upgrade procedure. While a no-roll patch installation is in progress, no other critical operations should be running on the cluster because the cluster will change state and reboot automatically at various stages of the procedure. In addition, the no-roll patch procedure employs the use of the Tru64 UNIX Event Management System (EVM) to send cluster-wide events. As a result, patches must be applied to the system in multiuser mode. If you attempt to use the no-roll procedure while in single-user mode, you will be advised to change the cluster to multiuser mode before continuing. _6._2 _S_t_e_p_s _f_o_r _R_u_n_n_i_n_g _a _N_o-_R_o_l_l _P_r_o_c_e_d_u_r_e The following steps describe how to patch your cluster using the no-roll procedure. _N_O_T_E To use the no-roll patch method, you must not use the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee utility to prepare the cluster, as you would for a rolling upgrade prior to running dddduuuuppppaaaattttcccchhhh. If a rolling upgrade is in progress before attempting to run dddduuuuppppaaaattttcccchhhh, then the no-roll option will not be available until the cluster is restored to the state prior to the roll attempt. 1. With your system running in multiuser mode, enter the dddduuuuppppaaaattttcccchhhh command: #### dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 2. From the main menu select the patch installation or patch deletion option. 6-2 No-Roll Patching (See Section 4.8.1.2.) 3. If dddduuuuppppaaaattttcccchhhh determines it is running on a cluster that has not been prepared to do a rolling patch, it asks if you want to do the patch operation without rolling. You will see a message similar to the following: Checking Cluster State...done This system is part of a cluster which has not been prepared to do a rolling patch installation or deletion. Do you wish to perform this patch operation cluster-wide without using the rolling-patch mechanism? Please answer y or n ? [y/n]: If you choose yyyyeeeessss, dddduuuuppppaaaattttcccchhhh proceeds by allowing you to do the analysis and selection of patches to be installed or removed, after which the whole cluster is brought down to iiiinnnniiiitttt level 2 via an Event Management System event. If you are using dddduuuuppppaaaattttcccchhhh from the command line and do not specify the -proceed option, you will need to press Return in order to transition the cluster from level 3 to level 2. If the -proceed option was set, the transition will occur automatically. After dddduuuuppppaaaattttcccchhhh completes its patch analysis, it will perform the patch operation on the member on which you ran dddduuuuppppaaaattttcccchhhh. After the patches are installed or removed, dddduuuuppppaaaattttcccchhhh will issue a second event to the remaining cluster members that will instruct them to complete their patch operations in parallel. The dddduuuuppppaaaattttcccchhhh utility then waits a calculated time-out period for all the other cluster members to complete their operations. The time-out period is based on the time it took to perform the patch operation on the member running dddduuuuppppaaaattttcccchhhh. After the patch operation is completed on all other cluster members, dddduuuuppppaaaattttcccchhhh will complete the procedure on the member on which the dddduuuuppppaaaattttcccchhhh command was issued. If a cluster member times out or encounters an error, dddduuuuppppaaaattttcccchhhh will report the problem, suspend the process, and send you a message to check the problematic member in order to resolve the problem. Once dddduuuuppppaaaattttcccchhhh has resumed, it will complete the patch process on the rest of the cluster. If a cluster member is known to be down when you issue the dddduuuuppppaaaattttcccchhhh command, an ////ssssbbbbiiiinnnn////iiiitttt job will be posted for the member to run the cluster patch script upon reboot. (For more information, see the iiiitttt(8) reference page.) Because all patches currently require a reboot, the whole cluster will reboot after all the members report back. _6._3 _T_h_r_o_w_i_n_g _t_h_e _V_e_r_s_i_o_n _S_w_i_t_c_h If a patch applied to the system requires the use of a version switch, you No-Roll Patching 6-3 will see a message similar to the following at the end of the dddduuuuppppaaaattttcccchhhh session: ********************************************************************* Patch OSFPAT00074200510 has been identified as needing a version switch. Once the following reboot is complete, please enter the "/var/adm/patch/noroll/noroll_versw" command from any cluster member. ********************************************************************* As indicated by the message, you must enter the ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////nnnnoooorrrroooollllllll////nnnnoooorrrroooollllllll____vvvveeeerrrrsssswwww command from any cluster member. This is a manual operation that you must perform after the reboot is complete. All cluster members must be up prior to running the nnnnoooorrrroooollllllll____vvvveeeerrrrsssswwww command. If they are not, the nnnnoooorrrroooollllllll____vvvveeeerrrrsssswwww command will fail and the version switch will not take place. After issuing the nnnnoooorrrroooollllllll____vvvveeeerrrrsssswwww command, reboot your system to ensure system integrity. _6._4 _R_e_m_o_v_i_n_g _P_a_t_c_h_e_s You can use the no-roll patch process to remove patches from a cluster regardless of whether the patches were installed on the cluster using either the no-roll or the rolling upgrade procedures. However, if the version switch was thrown after the installation of the patches, it is necessary to undo the version switch as described in the instructions in Section 5.7 prior to attempting to remove the patch requiring the version switch. 6-4 No-Roll Patching Common Error, Warning, and Informational Messages A This appendix describes error, warning, and informational messages for the dddduuuuppppaaaattttcccchhhh utility. The following information is provided for each message: SSSSoooouuuurrrrcccceeee:::: The function that generates the message. PPPPrrrroooobbbblllleeeemmmm:::: A brief description of possible causes for the message. CCCCaaaauuuusssseeeessss:::: A summary of situations that cause the message. AAAAccccttttiiiioooonnnn:::: General recovery guidance. OOOOuuuuttttppppuuuutttt:::: A sample of the message. _A._1 _P_a_t_c_h _P_r_e_i_n_s_t_a_l_l_a_t_i_o_n _C_h_e_c_k _a_n_d _I_n_s_t_a_l_l_a_t_i_o_n _M_e_s_s_a_g_e_s The following sections describe messages you might see when running the dddduuuuppppaaaattttcccchhhh preinstallation check or installation functions. _A._1._1 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _U_n_k_n_o_w_n _S_y_s_t_e_m _F_i_l_e SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: The installation of a specific patch is blocked due to an existing system file that is unknown. CCCCaaaauuuusssseeee:::: This situation usually occurs when system files are placed on the system through manual intervention. For example, this may have been the result of installing a Customer-Specific patch received from HP Services or a system administrator's customization of a Tru64 UNIX file. Until you confirm otherwise, the unknown system files should be viewed as intentional customizations that are important for proper system operation. As such, care should be taken to understand why the system files have been customized. AAAAccccttttiiiioooonnnn:::: Determine the origin of the existing unknown system files. The steps you take will be determined by the reason your system files were manually changed. See Section 2.6 for more information. OOOOuuuuttttppppuuuutttt:::: Checking patch prerequisites and patch file applicability ... (depending upon the number of patches you select, this may take a while) ------------------------------------------------------------------------- Problem installing: - DIGITAL_UNIX_V4.0F / Common Desktop Environment (CDE) Patches: Patch 0326.00 - CDE Login Correction ./usr/dt/bin/dtwm: its origin cannot be identified. This patch will not be installed. ------------------------------------------------------------------------- * Following patch(es) failed in prerequisite/file applicability check: - TRU64_UNIX_V4.0D / Common Desktop Environment (CDE) Patches: Patch 0326.00 - CDE Login Correction _A._1._2 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _M_i_s_s_i_n_g _S_y_s_t_e_m _F_i_l_e SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: Installation of a specific patch is blocked due to missing system file. CCCCaaaauuuusssseeeessss:::: This situation usually occurs when a system file that was installed with sssseeeettttlllldddd is manually removed from the system. The file is marked as installed in the system inventory records. AAAAccccttttiiiioooonnnn:::: Determine why the system file is missing and whether it is safe to enable dddduuuuppppaaaattttcccchhhh to install the blocked patch. See Section 2.6 for more information. OOOOuuuuttttppppuuuutttt:::: Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take a while) ------------------------------------------------------------------------- Problem installing: - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch 0236.00 - vi Editor Correction A-2 Common Error, Warning, and Informational Messages ./usr/bin/vedit: does not exist on your system, however, it is in the inventory of installed subsets. This patch will not be installed. ------------------------------------------------------------------------- * Following patch(es) failed in prerequisite/file applicability check: - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch 0236.00 - vi Editor Correction _A._1._3 _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _L_a_y_e_r_e_d _P_r_o_d_u_c_t _C_o_l_l_i_s_i_o_n SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: The installation of a specific patch is blocked due to an existing system file that is installed by a layered product. CCCCaaaauuuusssseeeessss:::: A small set of layered products deliver updated Tru64 UNIX operating system files. AAAAccccttttiiiioooonnnn:::: To resolve this situation contact the Product Customer Services representative. OOOOuuuuttttppppuuuutttt:::: Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take a while) ------------------------------------------------------------------------- Problem installing: - TRU_UNIX_V4.0F / Network Patches: Patch 0182.00 - xti/streams Interface Module Correction ./sys/BINARY/xtiso.mod: is installed by: BLTLPCONFLICTTEST410 and can not be replaced by this patch. This patch will not be installed. ------------------------------------------------------------------------- * Following patch(es) failed in prerequisite/file applicability check: Common Error, Warning, and Informational Messages A-3 - DIGITAL_UNIX_V4.0F / Network Patches: Patch 0182.00 - xti/streams Interface Module Correction _A._1._4 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _D_e_p_e_n_d_e_n_c_i_e_s _o_n _O_t_h_e_r _P_a_t_c_h_e_s SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: The installation of a specific patch is blocked due to its dependency on other uninstalled patches. CCCCaaaauuuusssseeeessss:::: This usually occurs when you miss the selection of all dependent patches. AAAAccccttttiiiioooonnnn:::: Through the dddduuuuppppaaaattttcccchhhh Installation Menu, take one of the following actions: +o Reselect the patches including the noted dependent patch and attempt reinstallation; dddduuuuppppaaaattttcccchhhh will notify you of other missing dependent patches. +o Select all patches and proceed with patch installation. OOOOuuuuttttppppuuuutttt:::: SAMPLE OUTPUT: Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take a while) ------------------------------------------------------------------------- Problem installing: - DIGITAL_UNIX_V4.0F / Security Related Patches: Patch 0579.01 - Security, Various Kernel Fixes (SSRT0482U) requires the existence of the following un-installed/un-selected subset(s): - TruCluster_V1.6 / Filesystem Patches: Patch 0037.00 - Support For New AdvFS Mount Option "-o noatimes" - TruCluster_V1.6 / ASE Availability Manager (AM) Patches: Patch 0033.00 - Kern Mem Fault And simple_lock Panic Correction This patch will not be installed. ------------------------------------------------------------------------- A-4 Common Error, Warning, and Informational Messages * Following patch(es) failed in prerequisite/file applicability check: - TRU64L_UNIX_V4.0F / Security Related Patches: Patch 0579.01 - Security, Various Kernel Fixes (SSRT0482U) _A._1._5 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _M_i_s_s_i_n_g _P_r_o_d_u_c_t _S_u_b_s_e_t SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: A specific patch cannot be installed because the product software subset is not installed on your system. CCCCaaaauuuusssseeeessss:::: This is usually a informational message and no further action is required. However, this message may also occur due to an internal patch kit error that results in an incorrectly specified patch dependencies. AAAAccccttttiiiioooonnnn:::: If the specific patch being blocked is the only patch being blocked you can assume this is an informational message. It may be an internal patch kit error if there are other patches whose installation is blocked by the patch whose subset is not installed. As a workaround, if you need one of the other patches whose installation is blocked, you can install the optional Tru64 UNIX or TCR release subset and reinstall the patches. OOOOuuuuttttppppuuuutttt:::: Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take a while) ------------------------------------------------------------------------- Problem installing: - TruCluster_V1.6 / Cluster Kernel Patches: Patch 0035.00 - rm_spur Driver Correction requires the existence of the following un-installed/un-selected subset(s): - TruCluster_V1.6 - subset: TCRMCA141 This patch will not be installed. ------------------------------------------------------------------------- * Following patch(es) failed in prerequisite/file applicability check: - TruCluster_V1.6 / Cluster Kernel Patches: Patch 0035.00 - rm_spur Driver Correction Common Error, Warning, and Informational Messages A-5 _A._1._6 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _D_i_s_k _S_p_a_c_e SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: The system disk did not have enough space to install patches. CCCCaaaauuuusssseeeessss:::: This occurs when there is not enough disk space in ////, ////vvvvaaaarrrr, or ////uuuussssrrrr partitions for dddduuuuppppaaaattttcccchhhh to archive the existing system files and move the patched files into place. AAAAccccttttiiiioooonnnn:::: Provide the necessary disk space and reinstall patches. If you cannot provide enough system disk space through other means, you may want to make ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp a symbolic link to or NFS-mount another file system that is not related to the ////, ////vvvvaaaarrrr, or ////uuuussssrrrr partitions. OOOOuuuuttttppppuuuutttt:::: Checking patch prerequisites once more... (depending upon the number of patches you select, this may take a while) ./usr/lbin/fitset: file system /whd needs 65829 Kbytes more to install the software specified. There is not enough file system space to install all the patches. you have selected. Please press RETURN to start another selection. . . . _A._1._7 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _I_n_s_t_a_l_l_e_d _P_a_t_c_h _o_r _S_u_b_s_e_t SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: The patch you are trying to install is built so it cannot supersede the later revision patch or subset that is installed on your system. CCCCaaaauuuusssseeeessss:::: This applicability feature is used to ensure that your system is not regressed through the installation of older code. AAAAccccttttiiiioooonnnn:::: If the situation is caused by a Release patch being blocked by a layered product or other subsets, contact your service provider. A-6 Common Error, Warning, and Informational Messages OOOOuuuuttttppppuuuutttt:::: Problem installing: - DIGITAL_UNIX_V4.0D / Filesystem Patches: Patch 00016.01 - System Run Level Correction ./sbin/.new..bcheckrc: is installed by: - DIGITAL_UNIX_V4.0D: Patch C 00484.01 and can not be replaced by this patch. This patch will not be installed. _A._1._8 _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _B_l_o_c_k_e_d _b_y _a_n _E_x_i_s_t_i_n_g _C_S_P SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: Release patches will not automatically supersede a Customer-Specific patch (CSP). CCCCaaaauuuusssseeeessss:::: A file you are trying to update with a Release patch has been previously updated through the installation of a CSP. The Release patch does not have any knowlege as to whether it contains fixes contained in CSPs. AAAAccccttttiiiioooonnnn:::: Determine if the CSP is included in the Release Patch Kit: +o If yes, then you can safely remove the CSP (via dddduuuuppppaaaattttcccchhhh) and reinstall the Release patch . +o If no, contact your service provider to determine how to proceed. OOOOuuuuttttppppuuuutttt:::: Problem installing: - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch 00444.00 - Fixes sort problem when running in Japanese locale ./usr/bin/sort: is installed by Customer Specific Patch (CSP): Common Error, Warning, and Informational Messages A-7 - DIGITAL_UNIX_V4.0F: Patch C 00187.00 and can not be replaced by this patch. To install this patch, you must first remove the CSP using dupatch. Before performing this action, you should contact your Compaq Service Representative to determine if this patch kit contains the CSP. If it does not, you may need to obtain a new CSP from Compaq in order to install the patch kit and retain the CSP fix. _A._1._9 _T_h_e _d_u_p_a_t_c_h _T_o_o_l_s _A_r_e _O_u_t_d_a_t_e_d SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: Patch tool set residing on system are not the most recent version. CCCCaaaauuuusssseeeessss:::: If the dddduuuuppppaaaattttcccchhhh utility delivered with the patch kit determines that the tools residing on the system are not consistent with the patch kit, it will copy over updated versions of utilities used by dddduuuuppppaaaattttcccchhhh. AAAAccccttttiiiioooonnnn:::: This is an informational message and no further action is required. OOOOuuuuttttppppuuuutttt:::: Patch tools need to be installed or updated on your system. Please invoke the command as the super-user (root) first. * A new version of patch tools required for patch management is now being installed on your system. _A._1._1_0 _S_o_m_e _P_a_t_c_h_e_s _M_u_s_t _B_e _M_a_d_e _R_e_v_e_r_s_i_b_l_e SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh preinstallation check or installation. PPPPrrrroooobbbblllleeeemmmm:::: Patch tool set residing on system is not the most recent version. CCCCaaaauuuusssseeeessss:::: The user tried to install a patch as nonreversible; however, the patch in question must be installed as reversible. A-8 Common Error, Warning, and Informational Messages AAAAccccttttiiiioooonnnn:::: This is an informational message and no further action is required. OOOOuuuuttttppppuuuutttt:::: * The following patch(es) are required to be reversible and will be made reversible automatically: - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch C 00187.00 - v 4.0f patch E C187.00 _A._2 _P_a_t_c_h _R_e_m_o_v_a_l _M_e_s_s_a_g_e_s The following sections describe messages you might see when running the dddduuuuppppaaaattttcccchhhh patch deletion function. _A._2._1 _P_a_t_c_h _R_e_m_o_v_a_l _B_l_o_c_k_e_d _b_y _M_i_s_s_i_n_g _P_a_t_c_h _B_a_c_k_u_p _F_i_l_e_s SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh deletion. PPPPrrrroooobbbblllleeeemmmm:::: An attempt to remove a specific patch or all patches fails because the backup of the prepatch system files is not available to dddduuuuppppaaaattttcccchhhh. CCCCaaaauuuusssseeeessss:::: The ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp area does not contain the prepatch system files. AAAAccccttttiiiioooonnnn:::: Ensure that dddduuuuppppaaaattttcccchhhh can access the////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp area and that the area is set up as it was when the patches were installed. For example, if you were using ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp as a mount point for another file system, make sure that file system is mounted. Once you have solved the ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp access or content problem, remove patches through the dddduuuuppppaaaattttcccchhhh Delete Menu. OOOOuuuuttttppppuuuutttt:::: Checking patch dependency... (depending upon the number of patches you select, this may take a while) ------------------------------------------------------------------------- - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch 0019.00 - quota Command Correction cannot be deleted. Can not find the backup copy for this patch in /var/adm/patch/backup. ------------------------------------------------------------------------- * Following patch(es) failed in dependency check: Common Error, Warning, and Informational Messages A-9 - DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches: Patch 0019.00 - quota Command Correction _A._2._2 _P_a_t_c_h _R_e_m_o_v_a_l _B_l_o_c_k_e_d _b_y _D_e_p_e_n_d_e_n_c_i_e_s _o_n _O_t_h_e_r _P_a_t_c_h_e_s SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh deletion. PPPPrrrroooobbbblllleeeemmmm:::: A specific patch cannot be removed because of its dependency on other installed patches. CCCCaaaauuuusssseeeessss:::: Generally this occurs when you miss the selection of all dependent patches. AAAAccccttttiiiioooonnnn:::: Through the dddduuuuppppaaaattttcccchhhh Delete Menu, reselect the patches including the noted dependent patch and try to remove them. The program will notify you of any other dependent patches you might have missed. OOOOuuuuttttppppuuuutttt:::: Checking patch dependency... (depending upon the number of patches you select, this may take a while) ------------------------------------------------------------------------- - DIGITAL_UNIX_V4.0F / Library Patches: Patch 0262.00 - libm Corrections can not be deleted unless the following patches are also selected or deleted first: - DIGITAL_UNIX_V4.0F / Library Patches: Patch 0676.00 - libm Corrections ------------------------------------------------------------------------- * Following patch(es) failed in dependency check: - DIGITAL_UNIX_V4.0F / Library Patches: Patch 0262.00 - libm Corrections _A._2._3 _N_o _O_r_i_g_i_n_a_l _F_i_l_e_s _R_e_s_t_o_r_e_d _W_h_e_n _P_a_t_c_h _I_s _R_e_m_o_v_e_d SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh deletion. PPPPrrrroooobbbblllleeeemmmm:::: The removal of a specific patch results in no original system files A-10 Common Error, Warning, and Informational Messages being restored. CCCCaaaauuuusssseeeessss:::: This occurs when a patch delivers files to your system that were not shipped in the initial release of the product. For example, the sample output shows the removal of Tru64 UNIX 4.0F Patch 314.00; the patch delivers files that were not shipped with the initial release of Tru64 UNIX 4.0F. AAAAccccttttiiiioooonnnn:::: This is an informational message and no further action is required. OOOOuuuuttttppppuuuutttt:::: === Deleting "DIGITAL UNIX V4.0F": Deleting "Patch: AdvFS Command Correction " (OSFPAT00031400425). ------------------------------------------------------------------------- Patch OSFPAT00031400425 delivered all new files to your system so there are no original files to be restored. No user action is necessary. ------------------------------------------------------------------------- _A._3 _T_r_u_C_l_u_s_t_e_r _S_p_e_c_i_f_i_c _d_u_p_a_t_c_h _M_e_s_s_a_g_e_s The following sections show the output of informational messages you might see when running dddduuuuppppaaaattttcccchhhh on a TruCluster system: _A._3._1 _S_y_s_t_e_m _N_o_t _A_d_e_q_u_a_t_e_l_y _P_r_e_p_a_r_e_d OOOOuuuuttttppppuuuutttt:::: This system is part of a V5.0 cluster which has not been prepared to do a rolling patch installation. Refer to the Patch Installation Guide as to the proper procedure to start a rolling patch. _A._3._2 _R_o_l_l_i_n_g _U_p_g_r_a_d_e _i_n _P_r_o_g_r_e_s_s (_I_n_s_t_a_l_l_a_t_i_o_n) OOOOuuuuttttppppuuuutttt:::: Common Error, Warning, and Informational Messages A-11 This system is part of a V5.0 cluster which is currently in the process of being installed via the rolling upgrade/ rolling patch procedure. New patches cannot be installed on the system until the rolling installation procedure has completed on all cluster members. _A._3._3 _R_o_l_l_i_n_g _U_p_g_r_a_d_e _i_n _P_r_o_g_r_e_s_s (_B_a_s_e_l_i_n_i_n_g) OOOOuuuuttttppppuuuutttt:::: This Cluster is in the process of a roll. Baselining is not permitted until the cluster is out of the roll. _A._3._3._1 _V_e_r_s_i_o_n _5._0 _W_a_v_e _4 _C_l_u_s_t_e_r _i_s _U_n_s_u_p_p_o_r_t_e_d OOOOuuuuttttppppuuuutttt:::: This system is a Version 5.0 - Wave 4 Cluster. Dupatch cannot patch this type of cluster. This is an unsupported operation and dupatch will now exit. _A._3._4 _P_a_t_c_h _R_e_m_o_v_a_l _F_a_i_l_s _B_e_c_a_u_s_e _N_e_e_d_e_d _F_i_l_e _I_s _U_n_a_v_a_i_l_a_b_l_e SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh deletion. PPPPrrrroooobbbblllleeeemmmm:::: An attempt to remove patches fails because the file ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////vvvveeeerrrrssssiiiioooonnnnsssswwwwiiiittttcccchhhh....ttttxxxxtttt is not available to dddduuuuppppaaaattttcccchhhh. CCCCaaaauuuusssseeee:::: At least one of the patches selected for deletion in dddduuuuppppaaaattttcccchhhh has a version switch associated with it (defined by having the attribute PATCH_REQUIRES_VERSION_SWITCH set to "Y" in its _p_a_t_c_h._c_t_r_l file). The vvvveeeerrrrssssiiiioooonnnnsssswwwwiiiittttcccchhhh....ttttxxxxtttt file is necessary to determine whether the version switch has been thrown. A-12 Common Error, Warning, and Informational Messages AAAAccccttttiiiioooonnnn::::The dddduuuuppppaaaattttcccchhhh utility returns to the main menu. In order to proceed with the delete operation, you need to determine if the version switch was updated. If it has been thrown, you must run the undo script included with the patch to enable patch deletion (see Section 5.7). If the switch has not been thrown, you can enable the deletion of this patch by reconstructing the vvvveeeerrrrssssiiiioooonnnnsssswwwwiiiittttcccchhhh....ttttxxxxtttt file. You can also reselect patches for deletion, omitting the patch containing the version switch. Contact your Customer Service Representative for assistance. OOOOuuuuttttppppuuuutttt:::: /var/adm/patch/versionswitch.txt file not found! Cannot delete patches selected since _p_a_t_c_h__I_D requires a version switch. Please reselect patches or resolve missing /var/adm/patch/versionswitch.txt Please contact your Customer Service Representative for assistance. _A._3._5 _P_a_t_c_h _R_e_m_o_v_a_l _F_a_i_l_s _B_e_c_a_u_s_e _o_f _a _V_e_r_s_i_o_n _S_w_i_t_c_h SSSSoooouuuurrrrcccceeee:::: dddduuuuppppaaaattttcccchhhh deletion. PPPPrrrroooobbbblllleeeemmmm:::: The deletion of a patch containing a version switch has been blocked because the switch has been thrown. AAAAccccttttiiiioooonnnn::::The dddduuuuppppaaaattttcccchhhh utility returns to the main menu. In order to proceed with the delete operation, you need to determine if the version switch was indeed updated. You can also reselect patches for deletion, omitting the patch containing the version switch. OOOOuuuuttttppppuuuutttt:::: Version switch thrown for patch _p_a_t_c_h__I_D You cannot delete patch _p_a_t_c_h__I_D Please refer to the Patch Kit Release Notes for instructions on allowing the patch deletion to proceed. _A._3._6 _d_u_p_a_t_c_h _C_a_n_n_o_t _C_r_e_a_t_e _N_e_e_d_e_d _F_i_l_e SSSSoooouuuurrrrcccceeee:::: Patch installation Common Error, Warning, and Informational Messages A-13 PPPPrrrroooobbbblllleeeemmmm:::: The dddduuuuppppaaaattttcccchhhh utility cannot create the file ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////vvvveeeerrrrssssiiiioooonnnnsssswwwwiiiittttcccchhhh....ttttxxxxtttt because it cannot obtain the version switch state from ////eeeettttcccc////ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb. CCCCaaaauuuusssseeee:::: At least one of the patches selected for installation contains a version switch. dddduuuuppppaaaattttcccchhhh records the current version switch state in the file ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////vvvveeeerrrrssssiiiioooonnnnsssswwwwiiiittttcccchhhh....ttttxxxxtttt. In order to facilitate the installation of this patch, this file must be created. While attempting to create this file, dddduuuuppppaaaattttcccchhhh could not read the ////eeeettttcccc////ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb file AAAAccccttttiiiioooonnnn:::: Verify that the file ////eeeettttcccc////ssssyyyyssssccccoooonnnnffffiiiiggggttttaaaabbbb contains the entry nnnneeeewwww____vvvveeeerrrrssss____lllloooowwww. OOOOuuuuttttppppuuuutttt:::: Cannot obtain version switch info from system files! Cannot create versionswitch.txt file Please contact your Customer Service Representative for assistance. _A._3._7 _I_n_s_u_f_f_i_c_i_e_n_t _F_r_e_e _S_p_a_c_e (_F_i_l_e _S_y_s_t_e_m _F_u_l_l) SSSSoooouuuurrrrcccceeee:::: cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp stage of the rolling upgrade procedure. PPPPrrrroooobbbblllleeeemmmm:::: The rolling upgrade cannot proceed because required space allocations are not met. CCCCaaaauuuusssseeeessss:::: The ////, ////uuuussssrrrr, ////vvvvaaaarrrr, and/or ////iiii11118888nnnn file systems do not have the required amount of free space. AAAAccccttttiiiioooonnnn:::: Run the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----uuuunnnnddddoooo sssseeeettttuuuupppp command, free up enough space in the affected file systems to meet the requirements listed in Section 5.2.1, and rerun the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ----uuuunnnnddddoooo sssseeeettttuuuupppp command. OOOOuuuuttttppppuuuutttt:::: *** Error *** The tar commands used to create tagged files in the '/' file system have reported the following errors and warnings: NOTE: CFS: File system full: / tar: sbin/lsm.d/raid5/volsd : No space left on device tar: sbin/lsm.d/raid5/volume : No space left on device A-14 Common Error, Warning, and Informational Messages Sample Patch-Kit Installations B This appendix provides samples of using dddduuuuppppaaaattttcccchhhh to do the following: +o Perform a typical patch kit installation (Section B.1) +o Install Tru64 UNIX and TruCluster Server patches using the rolling upgrade procedure (Section B.2) +o Perform a baseline analysis (Section B.3) +o Remove patches (Section B.4) +o Install and remove CSPs and ERPs (Section B.5) _B._1 _T_y_p_i_c_a_l _P_a_t_c_h _K_i_t _I_n_s_t_a_l_l_a_t_i_o_n # ////mmmmnnnntttt////PPPPaaaattttcccchhhhKKKKiiiittttssss////KKKKiiiitttt2222////ppppaaaattttcccchhhh____kkkkiiiitttt////dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Installation Menu: ----------------------- 1) Pre-Installation Check ONLY 2) Check & Install patches in Single-User Mode b) Back to Main Menu q) Quit Enter your choice: 2222 Checking patch kit for transmission errors during download... Finished Checking patch kit checksums Gathering patch information... (depending upon the size of the patch kit, this may take awhile) *** Start of Special Instructions *** *** There are NO Special Instructions *** Press RETURN to proceed... ------------------------------------------------------------------------ To Make Patches Reversible - PLEASE READ THE FOLLOWING INFORMATION: - You have the option to make the patches reversible so you can revert the system to its state prior to the installation of a patch. - Reversibility is achieved by compressing and saving a copy of the files being replaced by the patches. These files would be restored to the system if you choose to delete a patch. - If you choose to make patches NON-reversible, then the system cannot be restored to the state prior to the installation of a patch; you will not be able to delete the patches later. - This patch kit may force a small set of patches to be reversible to ensure your upgrades to future versions of Tru64 UNIX are successful. The Patch Utility will make those patches reversible automatically. Refer to the Release Notes / Installation Instructions provided with this patch kit. Do you want the patches to be reversible? [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] By default, the backup copies of the installed patches will be saved in "/var/adm/patch/backup". B-2 Sample Patch-Kit Installations 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. You must ensure the backup directory is configured the same way during any patch removal operations. Your current setup of "/var/adm/patch/backup" is: * A plain directory (not a mount point or a symbolic link) Do you want to proceed with the installation with this setup? [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Your name: MMMMiiiikkkkeeee Enter any notes about this operation that you would like stored for future reference (To end your input, enter a "."): : IIIInnnnssssttttaaaalllllllliiiinnnngggg aaaallllllll ppppaaaattttcccchhhheeeessss ffffoooorrrr VVVV5555....0000AAAA KKKKiiiitttt2222 : .... The patches listed below are optional: There may be more optional 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 installed. - Tru64_UNIX_V5.0A / Cluster Kernel Patches: 1) Patch 00090.00 - versw command can core dump during rolling upgrade 2) Patch 00186.00 - Disks can become inaccessible on a cluster node - Tru64_UNIX_V5.0A / Commands, Shells, & Utilities Patches: 3) Patch 00015.00 - Fixes a problem that occurs in multibyte locales 4) Patch 00019.00 - Fixes a problem with the grep command 5) Patch 00035.00 - Fixes a problem with the find command 6) Patch 00041.00 - Corrects problem with the fgrep command 7) Patch 00042.00 - Fixes problem with the restore command 8) Patch 00064.00 - Fixes btcreate and btextract problems --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 9) Patch 00065.00 - Fixes a hang in the shutdown process 10) Patch 00068.00 - Fix for vrestore problems 11) Patch 00079.00 - Fix for pax and vdump problems 12) Patch 00098.00 - pax opens and truncated pre-existing files - Tru64_UNIX_V5.0A / Commands, Shells, & Utility Patches: 13) Patch 00116.00 - Fixes a problem in uucp 14) Patch 00192.00 - Fix for what command 15) Patch 00205.00 - Corrects problem with mv command deleting files 16) Patch 00211.00 - Fixes cron problems Sample Patch-Kit Installations B-3 - Tru64_UNIX_V5.0A / Common Desktop Environment (CDE) Patches: 17) Patch 00001.00 - CDE does not recreate list of application groups 18) Patch 00165.00 - dtlogin core dumps from XDMCP clients 19) Patch 00200.00 - Fix for dtmail problem 20) Patch 00209.00 - dtwm hangs on system using multiple displays --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Filesystem Patches: 21) Patch 00027.00 - Changes quotactl prototype to meet POSIX standards 22) Patch 00031.00 - Fix for nfscast error message 23) Patch 00047.00 - UFS disk quotas are not updating automatically 24) Patch 00130.00 - Incorrect warning messages about mounted filesystems 25) Patch 00134.00 - Fixes problems with vdf 26) Patch 00190.00 - b-tree index for directory could become corrupted 27) Patch 00207.00 - Potential hang on booting a cluster - Tru64_UNIX_V5.0A / Hardware Configuration Patches: 28) Patch 00061.00 - Hardware manager inaccurately reports CPU speed 29) Patch 00081.00 - Fix for dn_setup core dump 30) Patch 00083.00 - SCSI_MC_GENERIC-READ_ELEMENT_STATUS fails - Tru64_UNIX_V5.0A / I/O Device Handling Patches: 31) Patch 00051.00 - Provides the latest driver for PowerStorm 4D10T 32) Patch 00084.00 - Corrects a hardware probe time hang --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 33) Patch 00122.00 - Fixes a timeout table overflow system panic 34) Patch 00154.00 - Improper handling of PCI options cards 35) Patch 00159.00 - Fixes AdvFS domain panic 36) Patch 00194.00 - Fixes potential source code computability problem - Tru64_UNIX_V5.0A / I18N Patches: 37) Patch 00014.00 - Updates the Danish (da_DK.ISO8859-1) locale 38) Patch 00124.00 - Adds support for euro character to keymap files - Tru64_UNIX_V5.0A / Kernel Patches: 39) Patch 00036.00 - OS only looks in slot 0 for primary CPU 40) Patch 00057.00 - Fixes panic caused when deleting process group 41) Patch 00062.00 - Cursor displays incorrectly when image plane set to 1 42) Patch 00141.00 - System hangs when running granularity hints 43) Patch 00178.00 - Incorrect bcache size returned to kernel from HWRPB 44) Patch 00184.00 - Bootlink can fail on AlphaStations 600, 600A, 500/400 --- MORE TO FOLLOW --- B-4 Sample Patch-Kit Installations Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Library Patches: 45) Patch 00008.00 - Provides missing compose definitions for ISO8859-15 46) Patch 00022.00 - Fix for EVM problems on some Alpha EV6 systems 47) Patch 00071.00 - Static library fix for libevm 48) Patch 00095.00 - Overlap checking in MKFDMN and NEWFS fails 49) Patch 00097.00 - Fixes a problem with the dlsym routine 50) Patch 00099.00 - MKFDMN NEWFS fails for third party drivers in cluster 51) Patch 00163.00 - Fixes conflicting cuserid declarations - Tru64_UNIX_V5.0A / Memory Channel Patches: 52) Patch 00086.00 - Fix for rm_state_change panic - Tru64_UNIX_V5.0A / Network Patches: 53) Patch 00023.00 - Fixes a kernel memory fault when using ATM 54) Patch 00025.00 - Fix for VMAC functionality when used with NETrain 55) Patch 00032.00 - Kernel panics Classical IP over lfa ATM driver 56) Patch 00033.00 - System panics when running ATM --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 57) Patch 00037.00 - Fixes a tftpd problem 58) Patch 00069.00 - Updates the lfa ATM device driver to V1.0.17 59) Patch 00118.00 - Corrects a problem in the lat driver 60) Patch 00148.00 - Performance problem in Cluster File System 61) Patch 00161.00 - Updates emx Fiber Channel driver to revision 1.22 62) Patch 00170.00 - ATM LAN emulation fails with ATM Meteor 351 board - Tru64_UNIX_V5.0A / Printers Patches: 63) Patch 00157.00 - Unnecessary error messages written to lpr log file - Tru64_UNIX_V5.0A / Security Related Patches: 64) Patch 00074.00 - Security (SSRT0636U) 65) Patch 00076.00 - Security (SSRT0656U) 66) Patch 00100.00 - Security (SSRT0656U) 67) Patch 00114.00 - Security (SSRT0636U) 68) Patch 00120.00 - System panic occurs when auditing is enabled 69) Patch 00188.00 - advscan does not display bootable partitions properly 70) Patch 00196.00 - Security (SSRT0683U) --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 71) Patch 00202.00 - Upgrades sys_check utility to version 119 Sample Patch-Kit Installations B-5 - Tru64_UNIX_V5.0A / Software Development Environment Patches: 72) Patch 00038.00 - Fixes linker (ld) problems 73) Patch 00053.00 - Fixes errors seen when compiling with the -om switch 74) Patch 00066.00 - Problems with kdbx extensions mount and swap 75) Patch 00067.00 - Fixes a problem with routines in the libst library 76) Patch 00072.00 - Cannot change file permission using libst routines 77) Patch 00073.00 - prof profiling tool causes segmentation fault 78) Patch 00198.00 - Fixes problems in the Compaq C compiler - Tru64_UNIX_V5.0A / System Administration Patches: 79) Patch 00002.00 - Compaq SNMP subagent core dumps 80) Patch 00003.00 - Fixes automount problem 81) Patch 00075.00 - Fix for System Management Station daemon 82) Patch 00167.00 - Fixes incorrect date and time stamp on new directory 83) Patch 00172.00 - Fixes problems with the collect command --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): - Tru64_UNIX_V5.0A / Threads Patches: 84) Patch 00126.00 - Fix for threaded applications problem 85) Patch 00128.00 - Fix for threads created by taso programs - Tru64_UNIX_V5.0A / VM Patches: 86) Patch 00089.00 - Adding swap partition less than 8KB causes problems - Tru64_UNIX_V5.0A / Workstation Patches: 87) Patch 00213.00 - Fixes problem causing diskconfig to issue error msg - Tru64_UNIX_V5.0A / X11 Patches: 88) Patch 00010.00 - Fixes a problem with the svn widget of libDXm.so 89) Patch 00011.00 - Fix for lbxproxy utility 90) Patch 00012.00 - Drawing problems with PowerStorm 4D10T graphics card 91) Patch 00070.00 - Static library fix for libDXm 92) Patch 00132.00 - Fix for tclhelp failure 93) Patch 00150.00 - Fixes a memory leak in Xt --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 94) Patch 00152.00 - Memory leak when creating and destroying widgets 95) Patch 00174.00 - Fix for memory leaks in Xlib 96) Patch 00176.00 - Memory leaks occur when creating widgets 97) Patch 00180.00 - Fixes memory leak in libXm 98) Patch 00182.00 - libXm memory leak when creating widgets Or you may choose one of the following options: 99) ALL of the above B-6 Sample Patch-Kit Installations 100) CANCEL selections and redisplay menus 101) EXIT without installing any patches Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 99999999 You are installing the following optional patches: - Tru64_UNIX_V5.0A / Cluster Kernel Patches: Patch 00090.00 - versw command can core dump during rolling upgrade Patch 00186.00 - Disks can become inaccessible on a cluster node - Tru64_UNIX_V5.0A / Commands, Shells, & Utilities Patches: Patch 00015.00 - Fixes a problem that occurs in multibyte locales Patch 00019.00 - Fixes a problem with the grep command Patch 00035.00 - Fixes a problem with the find command Patch 00041.00 - Corrects problem with the fgrep command Patch 00042.00 - Fixes problem with the restore command Patch 00064.00 - Fixes btcreate and btextract problems Patch 00065.00 - Fixes a hang in the shutdown process Patch 00068.00 - Fix for vrestore problems Patch 00079.00 - Fix for pax and vdump problems Patch 00098.00 - pax opens and truncated pre-existing files - Tru64_UNIX_V5.0A / Commands, Shells, & Utility Patches: Patch 00116.00 - Fixes a problem in uucp Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] Patch 00192.00 - Fix for what command Patch 00205.00 - Corrects problem with mv command deleting files Patch 00211.00 - Fixes cron problems - Tru64_UNIX_V5.0A / Common Desktop Environment (CDE) Patches: Patch 00001.00 - CDE does not recreate list of application groups Patch 00165.00 - dtlogin core dumps from XDMCP clients Patch 00200.00 - Fix for dtmail problem Patch 00209.00 - dtwm hangs on system using multiple displays - Tru64_UNIX_V5.0A / Filesystem Patches: Patch 00027.00 - Changes quotactl prototype to meet POSIX standards Patch 00031.00 - Fix for nfscast error message Patch 00047.00 - UFS disk quotas are not updating automatically Patch 00130.00 - Incorrect warning messages about mounted filesystems Patch 00134.00 - Fixes problems with vdf Patch 00190.00 - b-tree index for directory could become corrupted Patch 00207.00 - Potential hang on booting a cluster Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Hardware Configuration Patches: Patch 00061.00 - Hardware manager inaccurately reports CPU speed Sample Patch-Kit Installations B-7 Patch 00081.00 - Fix for dn_setup core dump Patch 00083.00 - SCSI_MC_GENERIC-READ_ELEMENT_STATUS fails - Tru64_UNIX_V5.0A / I/O Device Handling Patches: Patch 00051.00 - Provides the latest driver for PowerStorm 4D10T Patch 00084.00 - Corrects a hardware probe time hang Patch 00122.00 - Fixes a timeout table overflow system panic Patch 00154.00 - Improper handling of PCI options cards Patch 00159.00 - Fixes AdvFS domain panic Patch 00194.00 - Fixes potential source code computability problem - Tru64_UNIX_V5.0A / I18N Patches: Patch 00014.00 - Updates the Danish (da_DK.ISO8859-1) locale Patch 00124.00 - Adds support for euro character to keymap files - Tru64_UNIX_V5.0A / Kernel Patches: Patch 00036.00 - OS only looks in slot 0 for primary CPU Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] Patch 00057.00 - Fixes panic caused when deleting process group Patch 00062.00 - Cursor displays incorrectly when image plane set to 1 Patch 00141.00 - System hangs when running granularity hints Patch 00178.00 - Incorrect bcache size returned to kernel from HWRPB Patch 00184.00 - Bootlink can fail on AlphaStations 600, 600A, 500/400 - Tru64_UNIX_V5.0A / Library Patches: Patch 00008.00 - Provides missing compose definitions for ISO8859-15 Patch 00022.00 - Fix for EVM problems on some Alpha EV6 systems Patch 00071.00 - Static library fix for libevm Patch 00095.00 - Overlap checking in MKFDMN and NEWFS fails Patch 00097.00 - Fixes a problem with the dlsym routine Patch 00099.00 - MKFDMN NEWFS fails for third party drivers in cluster Patch 00163.00 - Fixes conflicting cuserid declarations - Tru64_UNIX_V5.0A / Memory Channel Patches: Patch 00086.00 - Fix for rm_state_change panic - Tru64_UNIX_V5.0A / Network Patches: Patch 00023.00 - Fixes a kernel memory fault when using ATM Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] Patch 00025.00 - Fix for VMAC functionality when used with NETrain Patch 00032.00 - Kernel panics Classical IP over lfa ATM driver Patch 00033.00 - System panics when running ATM Patch 00037.00 - Fixes a tftpd problem Patch 00069.00 - Updates the lfa ATM device driver to V1.0.17 Patch 00118.00 - Corrects a problem in the lat driver Patch 00148.00 - Performance problem in Cluster File System Patch 00161.00 - Updates emx Fiber Channel driver to revision 1.22 Patch 00170.00 - ATM LAN emulation fails with ATM Meteor 351 board - Tru64_UNIX_V5.0A / Printers Patches: B-8 Sample Patch-Kit Installations Patch 00157.00 - Unnecessary error messages written to lpr log file - Tru64_UNIX_V5.0A / Security Related Patches: Patch 00074.00 - Security (SSRT0636U) Patch 00076.00 - Security (SSRT0656U) Patch 00100.00 - Security (SSRT0656U) Patch 00114.00 - Security (SSRT0636U) Patch 00120.00 - System panic occurs when auditing is enabled Patch 00188.00 - advscan does not display bootable partitions properly Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] Patch 00196.00 - Security (SSRT0683U) Patch 00202.00 - Upgrades sys_check utility to version 119 - Tru64_UNIX_V5.0A / Software Development Environment Patches: Patch 00038.00 - Fixes linker (ld) problems Patch 00053.00 - Fixes errors seen when compiling with the -om switch Patch 00066.00 - Problems with kdbx extensions mount and swap Patch 00067.00 - Fixes a problem with routines in the libst library Patch 00072.00 - Cannot change file permission using libst routines Patch 00073.00 - prof profiling tool causes segmentation fault Patch 00198.00 - Fixes problems in the Compaq C compiler - Tru64_UNIX_V5.0A / System Administration Patches: Patch 00002.00 - Compaq SNMP subagent core dumps Patch 00003.00 - Fixes automount problem Patch 00075.00 - Fix for System Management Station daemon Patch 00167.00 - Fixes incorrect date and time stamp on new directory Patch 00172.00 - Fixes problems with the collect command Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Threads Patches: Patch 00126.00 - Fix for threaded applications problem Patch 00128.00 - Fix for threads created by taso programs - Tru64_UNIX_V5.0A / VM Patches: Patch 00089.00 - Adding swap partition less than 8KB causes problems - Tru64_UNIX_V5.0A / Workstation Patches: Patch 00213.00 - Fixes problem causing diskconfig to issue error msg - Tru64_UNIX_V5.0A / X11 Patches: Patch 00010.00 - Fixes a problem with the svn widget of libDXm.so Patch 00011.00 - Fix for lbxproxy utility Patch 00012.00 - Drawing problems with PowerStorm 4D10T graphics card Patch 00070.00 - Static library fix for libDXm Patch 00132.00 - Fix for tclhelp failure Patch 00150.00 - Fixes a memory leak in Xt Patch 00152.00 - Memory leak when creating and destroying widgets Patch 00174.00 - Fix for memory leaks in Xlib Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] Sample Patch-Kit Installations B-9 Patch 00176.00 - Memory leaks occur when creating widgets Patch 00180.00 - Fixes memory leak in libXm Patch 00182.00 - libXm memory leak when creating widgets Is this correct? (y/n): yyyy Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take awhile) *** You have selected 98 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. *********************************************************************** === Installing "Tru64 UNIX V5.0A" Patches: Checking file system space required to install specified subsets: File system space checked OK. 98 subsets will be installed. Loading subset 1 of 98 ... Patch: Fixes panic caused when deleting process group Copying from /scratch/public/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying Loading subset 2 of 98 ... Patch: Fixes problems with vdf Copying from /scratch/public/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying Loading subset 3 of 98 ... 0000oading subset 97 of 98 ... Patch: Fixes a problem in uucp Copying from /scratch/public/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying Loading subset 98 of 98 ... B-10 Sample Patch-Kit Installations Patch: pax opens and truncated pre-existing files Copying from /scratch/public/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying 98 of 98 subsets installed successfully. Configuring "Patch: Fixes panic caused when deleting process group" (OSFPAT00005700505) Configuring "Patch: Fixes problems with vdf" (OSFPAT00013400505) Configuring "Patch: Upgrades sys_check utility to version 119" (OSFPAT00020200505) 0000onfiguring "Patch: Fixes a problem in uucp" (OSFPAT00011600505) Configuring "Patch: pax opens and truncated pre-existing files" (OSFPAT00009800505) Beginning kernel build... Do you have a pre-existing configuration file?: yyyy *** KERNEL CONFIGURATION AND BUILD PROCEDURE *** Enter a name for the kernel configuration file. [IDIOM2]: [[[[RRRReeeettttuuuurrrrnnnn]]]] A configuration file with the name 'IDIOM2' already exists. Do you want to replace it? (y/n) [n]: yyyy Saving /sys/conf/IDIOM2 as /sys/conf/IDIOM2.bck *** 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 Point-to-Point Protocol (PPP) 6 STREAMS pckt module (PCKT) 7 X/Open Transport Interface (XTISO, TIMOD, TIRDWR) 8 ISO 9660 Compact Disc File System (CDFS) 9 Audit Subsystem 10 ATM UNI 3.0/3.1 ILMI (ATMILMI3X) 11 IP Switching over ATM (ATMIFMP) 12 LAN Emulation over ATM (LANE) 13 Classical IP over ATM (ATMIP) 14 ATM UNI 3.0/3.1 Signalling for SVCs (UNI3X) 15 Asynchronous Transfer Mode (ATM) 16 All of the above 17 None of the above 18 Help 19 Display all options again Sample Patch-Kit Installations B-11 -------------------------------------------------------------- Enter your choices. Choices (for example, 1 2 4-6) [17]: 8888 You selected the following kernel options: ISO 9660 Compact Disc File System (CDFS) Is that correct? (y/n) [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Do you want to edit the configuration file? (y/n) [n]: *** PERFORMING KERNEL BUILD *** A log file listing special device files is located in /dev/MAKEDEV.log Working....Thu Sep 21 12:57:42 EDT 2000 Working....Thu Sep 21 12:59:44 EDT 2000 The new kernel is /sys/IDIOM2/vmunix A reboot is necessary to complete the patch installation. Do you want to reboot now? [y/n] [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Existing kernel copied to /vmunix.PrePatch. New Kernel (/sys/IDIOM2/vmunix) moved to /vmunix. *** successfully installed 98 patches; failed to install 0 pathes *** * A system reboot of the patched system is required for the successfully installed patches. _B._2 _T_r_u_C_l_u_s_t_e_r _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _i_n _R_o_l_l_i_n_g _U_p_g_r_a_d_e The example in this section illustrates the installation of a patch kit during a rolling upgrade. When following this example, note the following conventions: +o The cluster ID of the lead member is 10. +o During the roll stage, you will roll each member. This example shows the roll of only one member, which has the ID of 61. +o The output of booting processes in this sample has been truncated. # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssseeeettttuuuupppp 11110000 B-12 Sample Patch-Kit Installations This is the cluster upgrade program. You have indicated that you want to perform the 'setup' stage of the upgrade. Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Are you running the clu_upgrade command to upgrade to a new version of the base operating system and cluster software? [yes]: nnnnoooo Are you running the clu_upgrade command to apply a rolling patch? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Backing-up member specific data for member: 10 . Creating tagged files. ............................................................................. ............................................................................. ............................................................................. The cluster upgrade 'setup' stage has completed successfully. Reboot all cluster members except member: '10' 0000he 'setup' stage of the upgrade has completed successfully. # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee pppprrrreeeeiiiinnnnssssttttaaaallllllll [[[[RRRReeeettttuuuurrrrnnnn]]]] This is the cluster upgrade program. You have indicated that you want to perform the 'preinstall' stage of the upgrade. Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Checking tagged files. ................................................................... The cluster upgrade 'preinstall' stage has completed successfully. You can now run the dupatch command on the lead member. # ....////dddduuuuppppaaaattttcccchhhh Enter path to the top of the patch distribution, or enter "q" to quit : . * A new version of patch tools required for patch management is now being installed on your system. * Tools updated, invoking the updated Patch Utility... Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion Sample Patch-Kit Installations B-13 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 Checking Cluster State...done Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Installation Menu: ----------------------- 1) Pre-Installation Check ONLY 2) Check & Install patches in Single-User Mode 3) Check and Install in Multi-User mode b) Back to Main Menu q) Quit Enter your choice: 3333 *** Installation Warning *** You have chosen to install patches onto this system while it is running in Multi-User mode. Some patches may directly affect core operating system operations. To insure 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]: yyyy The products listed below are optional: There may be more optional products than can be presented on a single screen. If this is the case, you can choose products 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 products are installed. 1) Patches for Tru64 UNIX V5.0A 2) Patches for TruCluster Server V5.0A Or you may choose one of the following options: B-14 Sample Patch-Kit Installations 3) ALL of the above 4) CANCEL selections and redisplay menus 5) EXIT without installing any products Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 3333 You are installing patches (to be selected) from the following products: Patches for Tru64 UNIX V5.0A Patches for TruCluster Server V5.0A Is this correct? (y/n): yyyy Gathering patch information... (depending upon the size of the patch kit, this may take awhile) *** Start of Special Instructions *** *** There are NO Special Instructions *** Press RETURN to proceed... ------------------------------------------------------------------------ To Make Patches Reversible - PLEASE READ THE FOLLOWING INFORMATION: - You have the option to make the patches reversible so you can revert the system to its state prior to the installation of a patch. - Reversibility is achieved by compressing and saving a copy of the files being replaced by the patches. These files would be restored to the system if you choose to delete a patch. - If you choose to make patches NON-reversible, then the system cannot be restored to the state prior to the installation of a patch; you will not be able to delete the patches later. - This patch kit may force a small set of patches to be reversible to ensure your upgrades to future versions of Tru64 UNIX are successful. The Patch Utility will make those patches reversible automatically. Refer to the Release Notes / Installation Instructions provided with this patch kit. Sample Patch-Kit Installations B-15 Do you want the patches to be reversible? [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] By default, the backup copies of the installed patches will be 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. You must ensure the backup directory is configured the same way during any patch removal operations. Your current setup of "/var/adm/patch/backup" is: * A plain directory (not a mount point or a symbolic link) Do you want to proceed with the installation with this setup? [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Enter any notes about this operation that you would like stored for future reference (To end your input, enter a "."): : IIIInnnnssssttttaaaalllllllliiiinnnngggg IIIIPPPPKKKK ffffoooorrrr 5555....0000aaaa oooonnnn 3333 nnnnooooddddeeeessss : .... The patches listed below are optional: There may be more optional 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 installed. - Tru64_UNIX_V5.0A / Cluster Kernel Patches: 1) Patch 0090.00 - versw command can core dump during rolling upgrade - Tru64_UNIX_V5.0A / Commands, Shells, & Utilities Patches: 2) Patch 0015.00 - Fixes a problem that occurs in multibyte locales 3) Patch 0019.00 - Fixes a problem with the grep command 4) Patch 0035.00 - Fixes a problem with the find command 5) Patch 0041.00 - Corrects problem with the fgrep command 6) Patch 0042.00 - Fixes problem with the restore command 7) Patch 0050.00 - crontab jobs run multiple times in same minute 8) Patch 0064.00 - Fixes btcreate and btextract problems --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 9) Patch 0065.00 - Fixes a hang in the shutdown process 10) Patch 0068.00 - Fix for vrestore problems 11) Patch 0079.00 - Fix for pax and vdump problems 12) Patch 0098.00 - pax opens and truncated pre-existing files B-16 Sample Patch-Kit Installations - Tru64_UNIX_V5.0A / Common Desktop Environment (CDE) Patches: 13) Patch 0001.00 - CDE does not recreate list of application groups - Tru64_UNIX_V5.0A / Filesystem Patches: 14) Patch 0027.00 - Changes quotactl prototype to meet POSIX standards 15) Patch 0031.00 - Fix for nfscast error message 16) Patch 0047.00 - UFS disk quotas are not updating automatically 17) Patch 0077.00 - Fix for AdvFS kernerl memory fault problem 18) Patch 0078.00 - Fix for advscan utility 19) Patch 0096.00 - Fix for sendmsg, nsendmsg, recvmsg, and nrecvmsg - Tru64_UNIX_V5.0A / Hardware Configuration Patches: 20) Patch 0054.00 - Provides PCI Resource Mgmt support for Atalla AXL200 --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 21) Patch 0061.00 - Hardware manager inaccurately reports CPU speed 22) Patch 0081.00 - Fix for dn_setup core dump 23) Patch 0083.00 - SCSI_MC_GENERIC-READ_ELEMENT_STATUS fails 24) Patch 0102.00 - Fixes a panic during a multi-node reboot - Tru64_UNIX_V5.0A / I/O Device Handling Patches: 25) Patch 0051.00 - Provides the latest driver for PowerStorm 4D10T 26) Patch 0059.00 - Updates emx Fiber Channel driver to revision 1.22 27) Patch 0084.00 - Corrects a hardware probe time hang 28) Patch 0103.00 - Fixes CAM disk problems - Tru64_UNIX_V5.0A / I18N Patches: 29) Patch 0014.00 - Updates the Danish (da_DK.ISO8859-1) locale - Tru64_UNIX_V5.0A / Kernel Patches: 30) Patch 0036.00 - OS only looks in slot 0 for primary CPU 31) Patch 0062.00 - Cursor displays incorrectly when image plane set to 1 --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Library Patches: 32) Patch 0008.00 - Provides missing compose definitions for ISO8859-15 33) Patch 0022.00 - Fix for EVM problems on some Alpha EV6 systems 34) Patch 0071.00 - Static library fix for libevm 35) Patch 0095.00 - Overlap checking in MKFDMN and NEWFS fails 36) Patch 0097.00 - Fixes a problem with the dlsym routine 37) Patch 0099.00 - MKFDMN NEWFS fails for third party drivers in cluster - Tru64_UNIX_V5.0A / Memory Channel Patches: 38) Patch 0086.00 - Fix for rm_state_change panic Sample Patch-Kit Installations B-17 - Tru64_UNIX_V5.0A / Network Patches: 39) Patch 0023.00 - Fixes a kernel memory fault when using ATM 40) Patch 0025.00 - Fix for VMAC functionality when used with NETrain 41) Patch 0032.00 - Kernel panics Classical IP over lfa ATM driver 42) Patch 0033.00 - System panics when running ATM 43) Patch 0037.00 - Fixes a tftpd problem --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 44) Patch 0069.00 - Updates the lfa ATM device driver to V1.0.17 45) Patch 0091.00 - Performance problem in Cluster File System - Tru64_UNIX_V5.0A / Printers Patches: 46) Patch 0101.00 - Fixes various printing problems - Tru64_UNIX_V5.0A / Security Related Patches: 47) Patch 0074.00 - Security (SSRT0636U) 48) Patch 0076.00 - Security (SSRT0656U) 49) Patch 0087.00 - Security (SSRT0636U) 50) Patch 0100.00 - Security (SSRT0656U) - Tru64_UNIX_V5.0A / Software Development Environment Patches: 51) Patch 0030.00 - Fixes problems in the Compaq C compiler 52) Patch 0038.00 - Fixes linker (ld) problems 53) Patch 0053.00 - Fixes errors seen when compiling with the -om switch 54) Patch 0066.00 - Problems with kdbx extensions mount and swap 55) Patch 0067.00 - Fixes a problem with routines in the libst library --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 56) Patch 0072.00 - Cannot change file permission using libst routines 57) Patch 0073.00 - prof profiling tool causes segmentation fault - Tru64_UNIX_V5.0A / System Administration Patches: 58) Patch 0002.00 - Compaq SNMP subagent core dumps 59) Patch 0003.00 - Fixes automount problem 60) Patch 0007.00 - Fixes problems with dxaccounts application 61) Patch 0075.00 - Fix for System Management Station daemon - Tru64_UNIX_V5.0A / Threads Patches: 62) Patch 0080.00 - Fix for threaded applications problem - Tru64_UNIX_V5.0A / VM Patches: 63) Patch 0089.00 - Adding swap partition less than 8KB causes problems - Tru64_UNIX_V5.0A / X11 Patches: 64) Patch 0009.00 - Fix for problem with Caps Lock setting 65) Patch 0010.00 - Fixes a problem with the svn widget of libDXm.so B-18 Sample Patch-Kit Installations --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] 66) Patch 0011.00 - Fix for lbxproxy utility 67) Patch 0012.00 - Drawing problems with PowerStorm 4D10T graphics card 68) Patch 0070.00 - Static library fix for libDXm - TruCluster_V5.0A / Cluster Kernel Patches: 69) Patch 0001.00 - mounts that return ESTALE may loop forever 70) Patch 0005.00 - Fixes a kernel memory fault panic 71) Patch 0008.00 - Fix for MC2 vhub cluster panic 72) Patch 0011.00 - Fixes problem on cluster nodes 73) Patch 0012.00 - Corrects problem with cluster member - TruCluster_V5.0A / Cluster Services Patches: 74) Patch 0003.00 - Delivers a new stripped clu_genvmunix --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): Or you may choose one of the following options: 75) ALL of the above 76) CANCEL selections and redisplay menus 77) EXIT without installing any patches Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 77775555 You are installing the following optional patches: - Tru64_UNIX_V5.0A / Cluster Kernel Patches: Patch 0090.00 - versw command can core dump during rolling upgrade - Tru64_UNIX_V5.0A / Commands, Shells, & Utilities Patches: Patch 0015.00 - Fixes a problem that occurs in multibyte locales Patch 0019.00 - Fixes a problem with the grep command Patch 0035.00 - Fixes a problem with the find command Patch 0041.00 - Corrects problem with the fgrep command Patch 0042.00 - Fixes problem with the restore command Patch 0050.00 - crontab jobs run multiple times in same minute Patch 0064.00 - Fixes btcreate and btextract problems Patch 0065.00 - Fixes a hang in the shutdown process Patch 0068.00 - Fix for vrestore problems Patch 0079.00 - Fix for pax and vdump problems Patch 0098.00 - pax opens and truncated pre-existing files Sample Patch-Kit Installations B-19 - Tru64_UNIX_V5.0A / Common Desktop Environment (CDE) Patches: Patch 0001.00 - CDE does not recreate list of application groups Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Filesystem Patches: Patch 0027.00 - Changes quotactl prototype to meet POSIX standards Patch 0031.00 - Fix for nfscast error message Patch 0047.00 - UFS disk quotas are not updating automatically Patch 0077.00 - Fix for AdvFS kernerl memory fault problem Patch 0078.00 - Fix for advscan utility Patch 0096.00 - Fix for sendmsg, nsendmsg, recvmsg, and nrecvmsg - Tru64_UNIX_V5.0A / Hardware Configuration Patches: Patch 0054.00 - Provides PCI Resource Mgmt support for Atalla AXL200 Patch 0061.00 - Hardware manager inaccurately reports CPU speed Patch 0081.00 - Fix for dn_setup core dump Patch 0083.00 - SCSI_MC_GENERIC-READ_ELEMENT_STATUS fails Patch 0102.00 - Fixes a panic during a multi-node reboot - Tru64_UNIX_V5.0A / I/O Device Handling Patches: Patch 0051.00 - Provides the latest driver for PowerStorm 4D10T Patch 0059.00 - Updates emx Fiber Channel driver to revision 1.22 Patch 0084.00 - Corrects a hardware probe time hang Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] Patch 0103.00 - Fixes CAM disk problems - Tru64_UNIX_V5.0A / I18N Patches: Patch 0014.00 - Updates the Danish (da_DK.ISO8859-1) locale - Tru64_UNIX_V5.0A / Kernel Patches: Patch 0036.00 - OS only looks in slot 0 for primary CPU Patch 0062.00 - Cursor displays incorrectly when image plane set to 1 - Tru64_UNIX_V5.0A / Library Patches: Patch 0008.00 - Provides missing compose definitions for ISO8859-15 Patch 0022.00 - Fix for EVM problems on some Alpha EV6 systems Patch 0071.00 - Static library fix for libevm Patch 0095.00 - Overlap checking in MKFDMN and NEWFS fails Patch 0097.00 - Fixes a problem with the dlsym routine Patch 0099.00 - MKFDMN NEWFS fails for third party drivers in cluster - Tru64_UNIX_V5.0A / Memory Channel Patches: Patch 0086.00 - Fix for rm_state_change panic Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Network Patches: Patch 0023.00 - Fixes a kernel memory fault when using ATM Patch 0025.00 - Fix for VMAC functionality when used with NETrain B-20 Sample Patch-Kit Installations Patch 0032.00 - Kernel panics Classical IP over lfa ATM driver Patch 0033.00 - System panics when running ATM Patch 0037.00 - Fixes a tftpd problem Patch 0069.00 - Updates the lfa ATM device driver to V1.0.17 Patch 0091.00 - Performance problem in Cluster File System - Tru64_UNIX_V5.0A / Printers Patches: Patch 0101.00 - Fixes various printing problems - Tru64_UNIX_V5.0A / Security Related Patches: Patch 0074.00 - Security (SSRT0636U) Patch 0076.00 - Security (SSRT0656U) Patch 0087.00 - Security (SSRT0636U) Patch 0100.00 - Security (SSRT0656U) Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / Software Development Environment Patches: Patch 0030.00 - Fixes problems in the Compaq C compiler Patch 0038.00 - Fixes linker (ld) problems Patch 0053.00 - Fixes errors seen when compiling with the -om switch Patch 0066.00 - Problems with kdbx extensions mount and swap Patch 0067.00 - Fixes a problem with routines in the libst library Patch 0072.00 - Cannot change file permission using libst routines Patch 0073.00 - prof profiling tool causes segmentation fault - Tru64_UNIX_V5.0A / System Administration Patches: Patch 0002.00 - Compaq SNMP subagent core dumps Patch 0003.00 - Fixes automount problem Patch 0007.00 - Fixes problems with dxaccounts application Patch 0075.00 - Fix for System Management Station daemon - Tru64_UNIX_V5.0A / Threads Patches: Patch 0080.00 - Fix for threaded applications problem Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0A / VM Patches: Patch 0089.00 - Adding swap partition less than 8KB causes problems - Tru64_UNIX_V5.0A / X11 Patches: Patch 0009.00 - Fix for problem with Caps Lock setting Patch 0010.00 - Fixes a problem with the svn widget of libDXm.so Patch 0011.00 - Fix for lbxproxy utility Patch 0012.00 - Drawing problems with PowerStorm 4D10T graphics card Patch 0070.00 - Static library fix for libDXm - TruCluster_V5.0A / Cluster Kernel Patches: Patch 0001.00 - mounts that return ESTALE may loop forever Patch 0005.00 - Fixes a kernel memory fault panic Patch 0008.00 - Fix for MC2 vhub cluster panic Patch 0011.00 - Fixes problem on cluster nodes Sample Patch-Kit Installations B-21 Patch 0012.00 - Corrects problem with cluster member - TruCluster_V5.0A / Cluster Services Patches: Patch 0003.00 - Delivers a new stripped clu_genvmunix Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] Is this correct? (y/n): yyyy Checking patch prerequisites and patch file applicability... (depending upon the number of patches you select, this may take awhile) ************************** 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. *********************************************************************** === Installing "Tru64 UNIX V5.0A" Patches: 68 subsets will be installed. Loading subset 1 of 68 ... Patch: Corrects problem with the fgrep command Copying from /Patchkits/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying Loading subset 2 of 68 ... Patch: Fixes problem with the restore command Copying from /Patchkits/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying Loading subset 3 of 68 ... Patch: CDE does not recreate list of application groups Copying from /Patchkits/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying 000 Loading subset 67 of 68 ... Patch: prof profiling tool causes segmentation fault Copying from /Patchkits/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying Loading subset 68 of 68 ... B-22 Sample Patch-Kit Installations Patch: Static library fix for libDXm Copying from /Patchkits/patch_kit/Tru64_UNIX_V5.0A/kit (disk) Verifying 68 of 68 subsets installed successfully. *** Starting protofile merges for "Tru64 UNIX V5.0A Patch Distribution" (T64V50AAS0001-20000626OSF505,26-Jun-2000:15:22:42) *** Configuring "Patch: Corrects problem with the fgrep command" (OSFPAT00004100505) on member0 Configuring "Patch: Fixes problem with the restore command" (OSFPAT00004200505) on member0 Configuring "Patch: CDE does not recreate list of application groups" (OSFPAT00000100505) on member0 000 Configuring "Patch: Cannot change file permission using libst routines" (OSFPAT00007200505) on member0 Configuring "Patch: prof profiling tool causes segmentation fault" (OSFPAT00007300505) on member0 Configuring "Patch: Static library fix for libDXm" (OSFPAT00007000505) on member0 *** Finished protofile merges for "Tru64 UNIX V5.0A Patch Distribution" (T64V50AAS0001-20000626OSF505,26-Jun-2000:15:22:42) *** Configuring "Patch: Corrects problem with the fgrep command" (OSFPAT00004100505) on member10 Configuring "Patch: Fixes problem with the restore command" (OSFPAT00004200505) on member10 Configuring "Patch: CDE does not recreate list of application groups" (OSFPAT00000100505) on member10 0000onfiguring "Patch: MKFDMN NEWFS fails for third party drivers in cluster" (OSFPAT00009900505) on member10 Configuring "Patch: Static library fix for libevm" (OSFPAT00007100505) on member10 Configuring "Patch: pax opens and truncated pre-existing files" (OSFPAT00009800505) on member10 === Installing "TruCluster Server V5.0A" Patches: 6 subsets will be installed. Loading subset 1 of 6 ... Sample Patch-Kit Installations B-23 Patch: Fixes a kernel memory fault panic Copying from /Patchkits/patch_kit/TruCluster_V5.0A/kit (disk) Verifying Loading subset 2 of 6 ... Patch: mounts that return ESTALE may loop forever Copying from /Patchkits/patch_kit/TruCluster_V5.0A/kit (disk) Verifying Loading subset 3 of 6 ... Patch: Fix for MC2 vhub cluster panic Copying from /Patchkits/patch_kit/TruCluster_V5.0A/kit (disk) Verifying Loading subset 4 of 6 ... Patch: Delivers a new stripped clu_genvmunix Copying from /Patchkits/patch_kit/TruCluster_V5.0A/kit (disk) Verifying Loading subset 5 of 6 ... Patch: Fixes problem on cluster nodes Copying from /Patchkits/patch_kit/TruCluster_V5.0A/kit (disk) Verifying Loading subset 6 of 6 ... Patch: Corrects problem with cluster member Copying from /Patchkits/patch_kit/TruCluster_V5.0A/kit (disk) Verifying 6 of 6 subsets installed successfully. *** Starting protofile merges for "Tru64 UNIX V5.0A Patch Distribution" (T64V50AAS0001-20000626TCR505,26-Jun-2000:15:25:36) *** Configuring "Patch: Fixes a kernel memory fault panic" (TCRPAT00000500505) on member0 Configuring "Patch: mounts that return ESTALE may loop forever" (TCRPAT00000100505) on member0 Configuring "Patch: Fix for MC2 vhub cluster panic" (TCRPAT00000800505) on member0 Configuring "Patch: Delivers a new stripped clu_genvmunix" (TCRPAT00000300505) on member0 Configuring "Patch: Fixes problem on cluster nodes" (TCRPAT00001100505) on member0 Configuring "Patch: Corrects problem with cluster member" (TCRPAT00001200505) on member0 B-24 Sample Patch-Kit Installations *** Finished protofile merges for "Tru64 UNIX V5.0A Patch Distribution" (T64V50AAS0001-20000626TCR505,26-Jun-2000:15:25:36) *** Configuring "Patch: Fixes a kernel memory fault panic" (TCRPAT00000500505) on member10 Configuring "Patch: mounts that return ESTALE may loop forever" (TCRPAT00000100505) on member10 Configuring "Patch: Fix for MC2 vhub cluster panic" (TCRPAT00000800505) on member10 Configuring "Patch: Delivers a new stripped clu_genvmunix" (TCRPAT00000300505) on member10 Configuring "Patch: Fixes problem on cluster nodes" (TCRPAT00001100505) on member10 Configuring "Patch: Corrects problem with cluster member" (TCRPAT00001200505) on member10 Beginning kernel build... Do you have a pre-existing configuration file?: yyyy Enter the name of the pre-existing configuration file or press RETURN to use : *** KERNEL CONFIGURATION AND BUILD PROCEDURE *** Saving /sys/conf/ as /sys/conf/.bck Do you want to edit the configuration file? (y/n) [n]: [[[[RRRReeeettttuuuurrrrnnnn]]]] *** PERFORMING KERNEL BUILD *** Working....Fri Jun 30 10:44:08 EDT 2000 The new kernel is /sys/_n_o_d_e_n_a_m_e/vmunix The system needs to be rebooted in order to complete the patch installation. Please choose one of the following options. Reboot Menu: ----------- 1) Reboot now 2) Schedule a reboot at a later time 3) Do nothing at this time Enter your choice: 1111 Existing kernel copied to cluster/members/{memb}/boot_partition/vmunix.PrePatch. New Kernel (/sys/_n_o_d_e_n_a_m_e/vmunix) moved to Sample Patch-Kit Installations B-25 cluster/members/{memb}/boot_partition/vmunix. CPU 0 halted halt code = 5 HALT instruction executed PC = fffffc00005b3310 CPU 0 booting 000 LAT started. Printer service started SysMan authentication server started CAA Applications now started Cluster sub-agent started cluster wall daemon started SysMan Station Server (smsd) started The system is ready. Compaq Tru64 UNIX V5.0A (Rev. 1094) (stone.grosys.com) console login: rrrrooooooootttt Password: Last login: Thu Jun 29 14:49:11 EDT 2000 from bensyl.grosys.com Compaq Tru64 UNIX V5.0A (Rev. 1094); Thu Jun 29 13:44:13 EDT 2000 The installation software has successfully installed your system. There are logfiles that contain a record of your installation. These are: /var/adm/smlogs/install.cdf - configuration description file /var/adm/smlogs/install.log - general log file /var/adm/smlogs/install.FS.log - file system creation logs /var/adm/smlogs/setld.log - log for the setld(8) utility /var/adm/smlogs/fverify.log - verification log file # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee ppppoooossssttttiiiinnnnssssttttaaaallllllll This is the cluster upgrade program. You have indicated that you want to perform the 'postinstall' stage of the upgrade. Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] The 'postinstall' stage of the upgrade has completed successfully. The following step involves performing the cccclllluuuusssstttteeeerrrr____uuuuppppggggrrrraaaaddddeeee rrrroooollllllll program on all other members of your cluster: # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee rrrroooollllllll This is the cluster upgrade program. B-26 Sample Patch-Kit Installations You have indicated that you want to perform the 'roll' stage of the upgrade. Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Backing up member-specific data for member: 66661111 . The 'roll' stage has completed successfully. This member must be rebooted in order to run with the newly installed software. Do you want to reboot this member at this time? []: yyyy You indicated that you want to reboot this member at this time. Is that correct? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] # syncing disks... done drd: Clean ShutdowCP - SAVE_TERM routine to be called CP - SAVE_TERM exited with hlt_req = 1, r0 = 00000000.00000000 halted CPU 0 halt code = 5 HALT instruction executed PC = fffffc00005b3320 CPU 0 booting 000 Subsystem hwautoconfig was successfully configured. Jun 30 14:40:03 update: started Checking for Installation Tasks... Executing Installation Tasks... Rolling member specific files on member...CNX QDISK: Successfully claimed quorum disk, adding 1 vote. Configuring "Patch: versw command can core dump during rolling upgrade" (OSFPAT00009000505) on member61 Configuring "Patch: Fixes a problem that occurs in multibyte locales" (OSFPAT00001500505) on member61 Configuring "Patch: Fixes a problem with the grep command" (OSFPAT00001900505) on member61 0000onfiguring "Patch: Fixes problem on cluster nodes" (TCRPAT00001100505) on member61 Configuring "Patch: Corrects problem with cluster member" (TCRPAT00001200505) on member61 Configuring "Patch: Delivers a new stripped clu_genvmunix" (TCRPAT00000300505) on member61 Beginning kernel build... Do you have a pre-existing configuration file?: yyyy Enter the name of the pre-existing configuration file or press RETURN to use : *** KERNEL CONFIGURATION AND BUILD PROCEDURE *** Sample Patch-Kit Installations B-27 Saving /sys/conf/ as /sys/conf/.bck Do you want to edit the configuration file? (y/n) [n]: [[[[RRRReeeettttuuuurrrrnnnn]]]] *** PERFORMING KERNEL BUILD *** Working....Fri Jun 30 14:42:28 EDT 2000 Working....Fri Jun 30 14:44:29 EDT 2000 Working....Fri Jun 30 14:46:29 EDT 2000 The new kernel is /sys/_n_o_d_e_n_a_m_e/vmunix syncing disks... done drd: Clean Shutdown CP - SAVE_TERM routine to be called CP - SAVE_TERM exited with hlt_req = 1, r0 = 00000000.00000000 halted CPU 0 halt code = 5 HALT instruction executed PC = fffffc00005b3320 CPU 0 booting 000 # cccclllluuuu____uuuuppppggggrrrraaaaddddeeee sssswwwwiiiittttcccchhhh This is the cluster upgrade program. You have indicated that you want to perform the 'switch' stage of the upgrade. Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] The cluster upgrade 'switch' stage has completed successfully. # sssshhhhuuuuttttddddoooowwwwnnnn ----hhhh nnnnoooowwww Shutdown at 15:07 (in 0 minutes) [pid 5250134] *** FINAL System shutdown message from root@stone.grosys.com *** System going down IMMEDIATELY ... System shutdown time has arrived CPU 0 halted halt code = 5 HALT instruction executed PC = fffffc00005b3310 CPU 0 booting 000 B-28 Sample Patch-Kit Installations The system is ready. Compaq Tru64 UNIX V5.0A (Rev. 1094) (stone.grosys.com) console login: rrrrooooooootttt Password: Last login: Fri Jun 30 15:15:31 EDT 2000 from bensyl.grosys.com Compaq Tru64 UNIX V5.0A (Rev. 1094); Thu Jun 29 13:44:13 EDT 2000 The installation software has successfully installed your system. There are logfiles that contain a record of your installation. These are: /var/adm/smlogs/install.cdf - configuration description file /var/adm/smlogs/install.log - general log file /var/adm/smlogs/install.FS.log - file system creation logs /var/adm/smlogs/setld.log - log for the setld(8) utility /var/adm/smlogs/fverify.log - verification log file At this point you will reboot each remaining member of the cluster before beginning the clean stage to complete the rolling upgrade procedure. # cccclllluuuu ____uuuuppppggggrrrraaaaddddeeee cccclllleeeeaaaannnn This is the cluster upgrade program. You have indicated that you want to perform the 'clean' stage of the upgrade. Do you want to continue to upgrade the cluster? [yes]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Deleting tagged files. _B._3 _G_a_t_h_e_r_i_n_g _B_a_s_e_l_i_n_e _I_n_f_o_r_m_a_t_i_o_n The example in this section shows how to use dddduuuuppppaaaattttcccchhhh to perform a patch baseline analysis. You can perform this operation in either single-user or multiuser mode. #### dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in //var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion Sample Patch-Kit Installations B-29 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 5555 Patch Baseline Analysis and Adjustment ====================================== This section of the patch management utility does not actually install patches. It is an enabler and need only be used to baseline your system for routine use of setld-based patch kits. It is recommended that you read the release notes accompanying this kit, prior to continuing. It is specifically designed to provide continuity from an environment with manually installed operating system patches to one that can be managed using the standard 'setld' installation technology. This baselining is broken into phases that assess and report the state of your operating system files. It will only make changes to your system with your confirmation. Phase 1 - System Evaluation Where possible, this phase determines the origin of changed operating system files and detects formally released official patches that were ---------------------------------------- Press to continue viewing: ---------------------------------------- manually installed. Phase 2 - Report patches with inter-product inventory conflicts Some layered products ship operating system files or files delivered by other layered products. If you have any of these layered products installed on your system and the patch kit happens to contain those files with inventory conflicts, the Patch Utility will block the installation of the patches containing inventory conflicts since it may corrupt the layered product operation. Phase 3 - Create installation records for manually-installed patches During this phase, you will be shown a list of patches that match the files on your system, but are not marked as 'installed'. You will be offered an opportunity to mark these patches as 'installed'. This involves copying valid 'setld' database information to your system. B-30 Sample Patch-Kit Installations Phase 4 - Report changed system files This phase provides information to help you make choices later in this process. It reports both 'missing' and files whose origin cannot be determined. Some of these files may affect patch installation. You will want to consider this information when you later make decisions in phase 5. Phase 5 - Enable patches with file applicability conflicts This phase allows you to enable subsequent installation of patches whose inventory does not match the installed system. This occurs when: 1) System files changed and the origin of that change cannot be determined, or 2) The changed files can only be traced back to previous manual patches, or 3) The original file to be patched is missing from the system, or 4) Hard links to files about to be patched are broken It is recommended that you do not enable the installation of these patches, if any, until you have tracked down the origin of the files that are in conflict, or you may compromise the integrity of your operating system. ---------------------------------------- Press to continue viewing: ---------------------------------------- To assist you in this effort, the file list for the entire patch with the known information will be displayed. You may run through this phase to get the analysis without enabling the installation of any of the listed patches. It is recommended that you backup your operating system prior to the actual patch installation. Do you want to proceed with the analysis and adjustment? [y/n]:yyyy - This Patch Baseline Analysis/Adjustment session is logged in: //var/adm/patch/log/baseline.log KITNAME> OSF500 Phase 1 - System Evaluation =========================== This evaluation compares the contents of your patch kit to the state of files already installed on your system regardless of their origin. Sample Patch-Kit Installations B-31 The amount of time needed to complete this phase can vary greatly depending on the size of the patch kit, the version of the Operating System, and the performance of the system. * system evaluation completed. --------------------------- Press RETURN to proceed to the next phase... Phase 2 - Report patches with inter-product inventory conflicts =============================================================== Some layered products replace files delivered in the original Operating System inventory or other layered products' inventory. The Patch Utility will block installation of those patches with inventory conflicts since they could compromise the integrity of the layered products. * no inter-product inventory conflicts detected. --------------------------------------------- Press RETURN to proceed to the next phase... Phase 3 - Create installation records for manually installed patches ==================================================================== You can choose to copy valid installation records to your system for the following patches, if any. This will allow future management and reporting for patches to your operating system. Creating installation records is intended to establish a baseline to which future patches might be applied. Future patch removal may only ever occur to this baseline. * no manually installed patches detected. -------------------------------------- Press RETURN to proceed to the next phase... Phase 4 - Report changed system files and missing files ======================================================= This phase provides information to help you make choices later in this process. It reports both 'missing' and files whose origin cannot be determined. Some of these files may affect patch installation. You will want to consider this information when you later make decisions in phase 5. * no changed files detected ------------------------- Press RETURN to proceed to the next phase... Phase 5 - Enable patches with file applicability conflicts ========================================================== B-32 Sample Patch-Kit Installations You will be shown a list of patches, if any, and their files. Patches show up during this phase when: 1) System files changed and the origin of that change cannot be determined, or 2) The changed files can only be traced back to previous manual patches, or 3) The file to be patched is missing from the system, or 4) Hard links to files about to be patched are broken After reviewing this section, you can elect to enable the installation of these patches using a standard selection menu. Enabling a patch means that the checks for patch file applicability, done during patch installation, will be bypassed if you later choose to install that patch through the installation section of dupatch. It is recommended that you understand the origin of the listed files before enabling a patch for installation. * no patches with file applicability conflicts detected. ----------------------------------------------------- * Baseline Analysis/Adjustment process completed. ============================================== Press RETURN to get back to the Main Menu... Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in //var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in //var/adm/patch/log/session.log Patch Installation Menu: Sample Patch-Kit Installations B-33 ----------------------- 1) Pre-Installation Check ONLY 2) Check & Install (requires single-user mode) b) Back to Main Menu q) Quit Enter your choice: 2222 This operation can be performed in single-user mode only. Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in //var/adm/patch/log/session.log Patch Installation Menu: ----------------------- 1) Pre-Installation Check ONLY 2) Check & Install (requires single-user mode) b) Back to Main Menu q) Quit Enter your choice: qqqq _B._4 _R_e_m_o_v_i_n_g _P_a_t_c_h_e_s The example in this section shows how to use dddduuuuppppaaaattttcccchhhh to remove patches from a system. You can perform this operation only from systems running in single- user mode. #### dddduuuuppppaaaattttcccchhhh * Previous session logs saved in session.log.[1-25] Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in //var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking B-34 Sample Patch-Kit Installations 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 2222 *** Start of Special Instructions *** SPECIAL INSTRUCTIONS FOR Tru64 UNIX V5.0 Patch 48.00 Update your /etc/fstab entries to enable the selected mount option ("throttle") on the selected UFS filesystems. For example, change from: /dev/rz12e /mnt/test ufs rw 0 2 TO: /dev/rz12e /mnt/test ufs rw,throttle 0 2 Append to /etc/sysconfigtab any tuning changes. For further information on this patch, refer to the Patch Summary and Release Notes document. The release note for this patch includes a section on TUNING. The TUNING section describes the new io-throttle-shift, io-throttle-maxmzthruput, and io-throttle-static tunables. These tunables are configured in the "vfs" stanza. The following 3 lines make up an example: vfs: ---------------------------------------- Press to continue viewing: ---------------------------------------- io-throttle-shift = 1 io-throttle-maxmzthruput = 1 (Note - if you already have a vfs stanza in your sysconfigtab file, then just add the 2 "io-throttle" entries.) *** End of Special Instructions *** Your name: MMMMiiiikkkkeeee Enter any notes about this operation that you would like stored for Sample Patch-Kit Installations B-35 future reference (To end your input, enter a "."): .... : Deleting Patches : . 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. - Tru64_UNIX_V5.0 / Commands, Shells, & Utility Patches: 1) Patch 0011.00 - ld command inserts incorrect values 2) Patch 0019.00 - C shell incorrectly handles 2-byte characters 3) Patch 0021.00 - Fix for crontab command 4) Patch 0022.00 - Fix for sort command 5) Patch 0023.00 - Fix for ksh core dump problem 6) Patch 0028.00 - Fix for binmail 7) Patch 0032.00 - Fix for tar/pax program 8) Patch 0033.00 - Fix for vdump program dumping core 9) Patch 0035.00 - usermod command does not allow use of commas 10) Patch 0042.00 - rc.config and rc.config.common files may be corrupt --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0 / Common Desktop Environment (CDE) Patches: 11) Patch 0039.00 - Fix for dxaccounts shared library - Tru64_UNIX_V5.0 / Filesystem Patches: 12) Patch 0049.00 - Fix for AdvFS system hang - Tru64_UNIX_V5.0 / Hardware Configuration Patches: 13) Patch 0005.00 - Fix for Compaq AlphaServer problems 14) Patch 0025.00 - Restriction lifted for AlphaServer DS20 and ES40 15) Patch 0046.00 - Fix for simple lock timeout panic 16) Patch 0051.00 - Fix for system hang at boot time - Tru64_UNIX_V5.0 / I/O Device Handling Patches: 17) Patch 0001.00 - Fix for KZPCM and 8952U adapters 18) Patch 0004.00 - Fix for Universal Serial Bus (USB) problems 19) Patch 0036.00 - Powerstorm 4D10T does not draw lines correctly --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0 / Kernel Patches: 20) Patch 0017.00 - Fix for kernel memory fault 21) Patch 0045.00 - Fixes error in the SCSI device probe code B-36 Sample Patch-Kit Installations 22) Patch 0048.00 - Fix for lock hierarchy violation panic - Tru64_UNIX_V5.0 / Network Patches: 23) Patch 0007.00 - Fix for FDDI interface hang 24) Patch 0012.00 - Fix for packetfilter problems 25) Patch 0024.00 - Fix for NFS V3 XDR encoding 26) Patch 0030.00 - NFS server cannot handle greater than 8K I/O reqs - Tru64_UNIX_V5.0 / Security Related Patches: 27) Patch 0040.00 - Security (SSRT0614U) 28) Patch 0041.00 - Security (SSRT0571U) - Tru64_UNIX_V5.0 / Software Development Environment Patches: 29) Patch 0029.00 - Fix for Compaq C compiler --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0 / X11 Patches: 30) Patch 0038.00 - Fix for problem in X Display Manager (xdm) Or you may choose one of the following options: 31) ALL of the above 32) CANCEL selections and redisplay menus 33) EXIT without deleting any patches Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 33331111 You are deleting the following patches: - Tru64_UNIX_V5.0 / Commands, Shells, & Utility Patches: Patch 0011.00 - ld command inserts incorrect values Patch 0019.00 - C shell incorrectly handles 2-byte characters Patch 0021.00 - Fix for crontab command Patch 0022.00 - Fix for sort command Patch 0023.00 - Fix for ksh core dump problem Patch 0028.00 - Fix for binmail Patch 0032.00 - Fix for tar/pax program Patch 0033.00 - Fix for vdump program dumping core Patch 0035.00 - usermod command does not allow use of commas Patch 0042.00 - rc.config and rc.config.common files may be corrupt - Tru64_UNIX_V5.0 / Common Desktop Environment (CDE) Patches: Patch 0039.00 - Fix for dxaccounts shared library - Tru64_UNIX_V5.0 / Filesystem Patches: Patch 0049.00 - Fix for AdvFS system hang Sample Patch-Kit Installations B-37 Press RETURN to display the next screen: [[[[RRRReeeettttuuuurrrrnnnn]]]] - Tru64_UNIX_V5.0 / Hardware Configuration Patches: Patch 0005.00 - Fix for Compaq AlphaServer problems Patch 0025.00 - Restriction lifted for AlphaServer DS20 and ES40 Patch 0046.00 - Fix for simple lock timeout panic Patch 0051.00 - Fix for system hang at boot time - Tru64_UNIX_V5.0 / I/O Device Handling Patches: Patch 0001.00 - Fix for KZPCM and 8952U adapters Patch 0004.00 - Fix for Universal Serial Bus (USB) problems Patch 0036.00 - Powerstorm 4D10T does not draw lines correctly - Tru64_UNIX_V5.0 / Kernel Patches: Patch 0017.00 - Fix for kernel memory fault Patch 0045.00 - Fixes error in the SCSI device probe code Patch 0048.00 - Fix for lock hierarchy violation panic - Tru64_UNIX_V5.0 / Network Patches: Patch 0007.00 - Fix for FDDI interface hang Patch 0012.00 - Fix for packetfilter problems Press RETURN to display the next screen: Patch 0024.00 - Fix for NFS V3 XDR encoding Patch 0030.00 - NFS server cannot handle greater than 8K I/O reqs - Tru64_UNIX_V5.0 / Security Related Patches: Patch 0040.00 - Security (SSRT0614U) Patch 0041.00 - Security (SSRT0571U) - Tru64_UNIX_V5.0 / Software Development Environment Patches: Patch 0029.00 - Fix for Compaq C compiler - Tru64_UNIX_V5.0 / X11 Patches: Patch 0038.00 - Fix for problem in X Display Manager (xdm) Is this correct? (y/n): yyyy Checking patch dependency... (depending upon the number of patches you select, this may take a while) ************************** 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. *********************************************************************** B-38 Sample Patch-Kit Installations === Deleting "Tru64 UNIX V5.0": Deleting "Patch: Fix for problem in X Display Manager (xdm)" (OSFPAT00003800500). Deleting "Patch: Fix for Compaq C compiler" (OSFPAT00002900500). 0000eleting "Patch: Fix for crontab command" (OSFPAT00002100500). Deleting "Patch: C shell incorrectly handles 2-byte characters" (OSFPAT00001900500). Deleting "Patch: ld command inserts incorrect values" (OSFPAT00001100500). *** KERNEL CONFIGURATION AND BUILD PROCEDURE *** Enter a name for the kernel configuration file. [COBB]: [[[[RRRReeeettttuuuurrrrnnnn]]]] A configuration file with the name 'COBB' already exists. Do you want to replace it? (y/n) [n]: yyyy Saving /sys/conf/COBB as /sys/conf/COBB.bck *** 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 Point-to-Point Protocol (PPP) 6 STREAMS pckt module (PCKT) 7 Data Link Bridge (DLPI V2.0 Service Class 1) 8 X/Open Transport Interface (XTISO, TIMOD, TIRDWR) 9 ISO 9660 Compact Disc File System (CDFS) 10 Audit Subsystem 11 All of the above 12 None of the above 13 Help 14 Display all options again -------------------------------------------------------------- Enter your choices. Choices (for example, 1 2 4-6) [12]: [[[[RRRReeeettttuuuurrrrnnnn]]]] You do not want to select any kernel options. Is that correct? (y/n) [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] Do you want to edit the configuration file? (y/n) [n]: [[[[RRRReeeettttuuuurrrrnnnn]]]] *** PERFORMING KERNEL BUILD *** Sample Patch-Kit Installations B-39 A log file listing special device files is located in /dev/MAKEDEV.log Working....Tue Feb 1 14:09:04 EDT 2000 Working....Tue Feb 1 14:11:08 EDT 2000 The new kernel is /sys/COBB/vmunix A reboot is necessary to complete the patch deletion. Do you want to reboot now? [y/n] [y]: [[[[RRRReeeettttuuuurrrrnnnn]]]] _B._5 _I_n_s_t_a_l_l_i_n_g _a_n_d _R_e_m_o_v_i_n_g _C_S_P_s _a_n_d _E_R_P_s The examples in this section show how to use dddduuuuppppaaaattttcccchhhh to install and remove CSPs and ERPs. _E_x_a_m_p_l_e _o_f _I_n_s_t_a_l_l_i_n_g _C_S_P_s _a_n_d _E_R_P_s # ....////dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 Tru64 UNIX Patch Utility (Rev. 40-03) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Installation Menu: ----------------------- B-40 Sample Patch-Kit Installations 1) Pre-Installation Check ONLY 2) Check & Install patches in Single-User Mode b) Back to Main Menu q) Quit Enter your choice: 2222 Checking patch kit for transmission errors during download... Finished Checking patch kit checksums Gathering patch information... (depending upon the size of the patch kit, this may take awhile) *** Start of Special Instructions *** *** There are NO Special Instructions *** Press RETURN to proceed... ------------------------------------------------------------------------ To Make Patches Reversible - PLEASE READ THE FOLLOWING INFORMATION: - You have the option to make the patches reversible so you can revert the system to its state prior to the installation of a patch. - Reversibility is achieved by compressing and saving a copy of the files being replaced by the patches. These files would be restored to the system if you choose to delete a patch. - If you choose to make patches NON-reversible, then the system cannot be restored to the state prior to the installation of a patch; you will not be able to delete the patches later. - This patch kit may force a small set of patches to be reversible to ensure your upgrades to future versions of Tru64 UNIX are successful. The Patch Utility will make those patches reversible automatically. Refer to the Release Notes / Installation Instructions provided with this patch kit. Do you want the patches to be reversible? [y]: yyyy By default, the backup copies of the installed patches will be saved in "/var/adm/patch/backup". Sample Patch-Kit Installations B-41 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. You must ensure the backup directory is configured the same way during any patch removal operations. Your current setup of "/var/adm/patch/backup" is: * A plain directory (not a mount point or a symbolic link) Do you want to proceed with the installation with this setup? [y]: yyyy Your name: MMMMiiiikkkkeeee Enter any notes about this operation that you would like stored for future reference (To end your input, enter a "."): : IIIInnnnssssttttaaaallllllll ccccsssspppp ppppaaaattttcccchhhh kkkkiiiitttt 0000000011114444888811119999 : .... *** Enter patch selections *** The following patches are mandatory and will be installed automatically unless you choose to exit without installing any patches: - Tru64_UNIX_V5.1A / Miscellaneous Patches: * Patch C 00323.00 - Fix inetd dies with "out of memory" or seg fault You may choose one of the following options: 1) ALL of the above 2) CANCEL selections and redisplay menus 3) EXIT without installing any patches Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 1111 You are installing the following mandatory patches: - Tru64_UNIX_V5.1A / Miscellaneous Patches: Patch C 00323.00 - Fix inetd dies with "out of memory" or seg fault You are installing the following optional patches: Is this correct? (y/n): yyyy Checking patch prerequisites and patch file applicability... B-42 Sample Patch-Kit Installations (depending upon the number of patches you select, this may take awhile) *** You have selected 1 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. *********************************************************************** === Installing "Tru64 UNIX V5.1A" Patches: Checking file system space required to install specified subsets: File system space checked OK. 1 subsets will be installed. Loading subset 1 of 1 ... Patch: Fix inetd dies with "out of memory" or seg fault Copying from /var/cluster/members/member0/tmp/pat/tars/0014891/patch_kit/Tru64_UNIX_V5.1A/kit (disk) Verifying 1 of 1 subsets installed successfully. Configuring "Patch: Fix inetd dies with "out of memory" or seg fault" (OSFPATC0032300520) A reboot is necessary to complete the patch installation. Do you want to reboot now? [y/n] [y]: yyyy *** successfully installed 1 patches; failed to install 0 patches *** * A system reboot of the patched system is required for the successfully installed patches. _E_x_a_m_p_l_e _o_f _U_n_i_n_s_t_a_l_l_i_n_g _C_S_P_s _a_n_d _E_R_P_s # ....////dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 40-03) ========================== Sample Patch-Kit Installations B-43 - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 2222 *** Start of Special Instructions *** *** There are NO Special Instructions *** Your name: MMMMiiiikkkkeeee Enter any notes about this operation that you would like stored for future reference (To end your input, enter a "."): : RRRReeeemmmmoooovvvviiiinnnngggg ccccsssspppp ppppaaaattttcccchhhh kkkkiiiitttt 0000000011114444333388881111 : .... 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. - Tru64_UNIX_V5.1A / Miscellaneous Patches: 1) Patch C 00323.00 - Fix inetd dies with "out of memory" or seg fault 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): 1111 B-44 Sample Patch-Kit Installations You are deleting the following patches: - Tru64_UNIX_V5.1A / Miscellaneous Patches: Patch C 00323.00 - Fix inetd dies with "out of memory" or seg fault Is this correct? (y/n): yyyy Checking patch dependency... (depending upon the number of patches you select, this may take awhile) *** You have selected 1 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 "Tru64 UNIX V5.1A" patches: Deleting "Patch: Fix inetd dies with "out of memory" or seg fault" (OSFPATC0032300520). A reboot is necessary to complete the patch deletion. Do you want to reboot now? [y/n] [y]: yyyy *** successfully deleted 1 patches; failed to delete 0 patches *** * A system reboot of the patched system is required for the successfully dele ted patches. Sample Patch-Kit Installations B-45 Using dupatch from the Command Line C The dddduuuuppppaaaattttcccchhhh utility provides a command line interface that allows dddduuuuppppaaaattttcccchhhh to be called by other programs. You can use the command line to invoke all functions except for baselining. The functions have the same operation and definition as the menu-driven interface. For information about using the command-line interface, see the dddduuuuppppaaaattttcccchhhh(8) reference page, which is installed on your system when you install the patch-kit tools and is documented in this appendix. The following example shows the use of the dddduuuuppppaaaattttcccchhhh command and several of its options to install Patch 8.01 from a Version 5.0A kit: ////uuuussssrrrr////ssssbbbbiiiinnnn////dddduuuuppppaaaattttcccchhhh ----iiiinnnnssssttttaaaallllllll ----kkkkiiiitttt ////vvvvaaaarrrr////bbbbllll11115555////ppppaaaattttcccchhhh____kkkkiiiitttt ----nnnnaaaammmmeeee JJJJooooeeee ----nnnnooootttteeee \\\\ """"iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhh"""" ----pppprrrroooodddduuuucccctttt TTTTRRRRUUUU66664444____UUUUNNNNIIIIXXXX____VVVV5555....0000AAAA ----ppppaaaattttcccchhhh 00008888....00001111 The following example shows the use of the dddduuuuppppaaaattttcccchhhh command and several of its options to remove Patch 8.01 from a Version 5.0A kit: ////uuuussssrrrr////ssssbbbbiiiinnnn////dddduuuuppppaaaattttcccchhhh ----ddddeeeelllleeeetttteeee ----nnnnaaaammmmeeee JJJJooooeeee ----nnnnooootttteeee """"ddddeeeelllleeeetttteeee ppppaaaattttcccchhhh"""" \\\\ ----pppprrrroooodddduuuucccctttt TTTTRRRRUUUU66664444____UUUUNNNNIIIIXXXX____VVVV5555....0000AAAA ----ppppaaaattttcccchhhh 00008888....00001111 You must specify all mandatory options on the command line or in a data file. If any mandatory option is missing, the command will fail with an appropriate error message; it will not prompt you for the missing option and information. The rest of this appendix documents the dddduuuuppppaaaattttcccchhhh(8) reference page. dupatch(8) _N_A_M_E dddduuuuppppaaaattttcccchhhh - Installs, deletes and maintains software patch updates to the Tru64 UNIX operating system and TruCluster software products. _S_y_n_o_p_s_i_s ////uuuussssrrrr////ssssbbbbiiiinnnn////dddduuuuppppaaaattttcccchhhh ////uuuussssrrrr////ssssbbbbiiiinnnn////dddduuuuppppaaaattttcccchhhh ----hhhheeeellllpppp [----ddddaaaattttaaaa____ffffiiiilllleeee ] [----kkkkiiiitttt _k_i_t__l_o_c_a_t_i_o_n] [----ppppaaaattttcccchhhh____iiiidddd ] [----rrrreeeevvvv] [----pppprrrroooodddduuuucccctttt____iiiidddd] ////uuuussssrrrr////ssssbbbbiiiinnnn////dddduuuuppppaaaattttcccchhhh ----iiiinnnnssssttttaaaallllllll ----kkkkiiiitttt _k_i_t__l_o_c_a_t_i_o_n ----nnnnaaaammmmeeee _u_s_e_r__n_a_m_e ----nnnnooootttteeee _u_s_e_r__n_o_t_e ----ppppaaaattttcccchhhh aaaallllllll | _p_a_t_c_h__i_d [_p_a_t_c_h__i_d ]... [----ccccffffggggffffiiiilllleeee _c_o_n_f_i_g__f_i_l_e] [----ddddaaaattttaaaa _d_a_t_a__f_i_l_e] [----nnnnooooaaaauuuuttttoooo ] [----nnnnoooobbbbaaaacccckkkkuuuupppp ] [----nnnnoooolllloooogggg ] [----nnnnoooorrrroooollllllll ] [----pppprrrreeeecccchhhheeeecccckkkk____oooonnnnllllyyyy ] [---- pppprrrroooocccceeeeeeeedddd ] [----rrrrooooooootttt _r_o_o_t__p_a_t_h] ----pppprrrroooodddduuuucccctttt [[[[ aaaallllllll | _p_r_o_d_u_c_t__i_d ] [----ssssiiiinnnngggglllleeee____uuuusssseeeerrrr ] ////uuuussssrrrr////ssssbbbbiiiinnnn////dddduuuuppppaaaattttcccchhhh ----ddddeeeelllleeeetttteeee ----nnnnaaaammmmeeee _u_s_e_r__n_a_m_e ----nnnnooootttteeee _u_s_e_r__n_o_t_e ----ppppaaaattttcccchhhh aaaallllllll | _p_a_t_c_h__i_d [_p_a_t_c_h__i_d ]... [----ccccffffggggffffiiiilllleeee _c_o_n_f_i_g__f_i_l_e] [----ddddaaaattttaaaa _d_a_t_a__f_i_l_e] [----nnnnooooaaaauuuuttttoooo] [----nnnnoooolllloooogggg] [----nnnnoooorrrroooollllllll ] [----pppprrrroooocccceeeeeeeedddd ] [----rrrrooooooootttt _r_o_o_t__p_a_t_h ] [----pppprrrroooodddduuuucccctttt aaaallllllll | _p_r_o_d_u_c_t__i_d] [----ssssiiiinnnngggglllleeee____uuuusssseeeerrrr ] ////uuuussssrrrr////ssssbbbbiiiinnnn////dddduuuuppppaaaattttcccchhhh ----ttttrrrraaaacccckkkk ----ttttyyyyppppeeee [[[[ ffffiiiilllleeee | kkkkiiiitttt | ppppaaaattttcccchhhh ] ----kkkkiiiitttt _k_i_t__l_o_c_a_t_i_o_n [----ddddaaaattttaaaa _d_a_t_a__f_i_l_e] [----nnnnoooolllloooogggg ] [----rrrrooooooootttt _r_o_o_t__p_a_t_h ] _C_o_m_m_a_n_d _K_e_y_w_o_r_d_s -install _i_n_s_t_a_l_l-_o_p_t_i_o_n_s Installs a software patch or patch kit. -delete _d_e_l_e_t_e-_o_p_t_i_o_n_s Removes an installed patch or patches from the operating system. Patch deletion requires that the patch was installed as a reversible patch. -track _t_r_a_c_k-_o_p_t_i_o_n_s Constructs a history of patch installations and deletions. Information can be patch-kit specific or patch-file specific. -help _h_e_l_p-_o_p_t_i_o_n_s Requests quick help on dupatch. Supplying an argument will provide help specifically on that argument. _O_p_t_i_o_n_s _R_e_q_u_i_r_e_d -_i_n_s_t_a_l_l _O_p_t_i_o_n_s -kit _k_i_t__l_o_c_a_t_i_o_n Specifies the location of the patch kit from which patches will be installed onto the system. _k_i_t__l_o_c_a_t_i_o_n is a full path to the directory containing the patch kit. -name _u_s_e_r__n_a_m_e Specifies the name to be recorded in eeeevvvveeeennnntttt....lllloooogggg. Enclose the _u_s_e_r__n_a_m_e in quotation marks if it contains space characters. -note _u_s_e_r__n_o_t_e Records user-supplied text in the event log. The _u_s_e_r__n_o_t_e is a text string enclosed in quotation marks. -patch aaaallllllll -patch _p_a_t_c_h__i_d [_p_a_t_c_h__i_d]... Directs dddduuuuppppaaaattttcccchhhh to install all patches (aaaallllllll) patches or specific patches (_p_a_t_c_h__i_d) from the specified patch kit. -patch is optional with -precheck_only. See Specifying a Patch ID. C-2 Using dupatch from the Command Line -product _p_r_o_d_u_c_t__i_d [_p_r_o_d_u_c_t__i_d]... Required when more than one product is available for operation. Specifies the installed operating system and/or TruCluster software product to be patched. Product ID specifications are case insensitive. Wildcards are not permitted. See Specifying a Product ID. _O_p_t_i_o_n_a_l -_i_n_s_t_a_l_l _O_p_t_i_o_n_s -cfgfile _c_o_n_f_i_g__f_i_l_e Specifies a configuration file for rebuilding the kernel. See Specifying a Configuration File. -data _d_a_t_a__f_i_l_e Specifies a file that contains arguments (in the form _a_r_g_u_m_e_n_t = _v_a_l_u_e) to the dddduuuuppppaaaattttcccchhhh command. See Using a Data File. -noauto Directs dddduuuuppppaaaattttcccchhhh to not automatically rebuild the kernel if indicated by the patches installed. In addition, if running dddduuuuppppaaaattttcccchhhh to install the patches in single-user mode, the system will not automatically reboot after the patch process is complete. -nobackup Directs dddduuuuppppaaaattttcccchhhh to not retain backup information during a patch installation. This will remove the ability to back out an installed patch. -nolog Directs dddduuuuppppaaaattttcccchhhh to not record actions in a sssseeeessssssssiiiioooonnnn....lllloooogggg file. -noroll Directs dddduuuuppppaaaattttcccchhhh to install patches on a cluster using the no-roll procedure rather than the default rolling-upgrade procedure. -precheck_only Directs dddduuuuppppaaaattttcccchhhh to perform the preinstallation check but to not proceed with the patch installation. If -precheck_only is omitted, dddduuuuppppaaaattttcccchhhh begins the installation process after the preinstallation check has been completed, as long as no patch failed the preinstallation check. The preinstallation check determines whether new patches that depend on the presence of other patches or software subsets can be installed. It does this by verifying that the required patches or software subsets are already installed onto the system. -proceed Directs dddduuuuppppaaaattttcccchhhh to install any patches that passed the preinstallation check, Using dupatch from the Command Line C-3 even if one or more patches failed the preinstallation check. If -proceed is omitted, dddduuuuppppaaaattttcccchhhh will not install any patches if at least one patch fails the preinstallation check. The preinstallation check determines whether new patches that depend on the presence of other patches or software subsets can be installed. It does this by verifying that the required patches or software subsets are already installed onto the system. -root _r_o_o_t__p_a_t_h Specifies an alternate root location. The default _r_o_o_t__p_a_t_h is //// for all operations. -single_user If the system is presently in multiuser mode, brings the system down to single-user mode prior to installing patches. -rev Prints the current dupatch revision. _R_e_q_u_i_r_e_d -_d_e_l_e_t_e _O_p_t_i_o_n_s -name _u_s_e_r__n_a_m_e Specifies the name to be recorded in eeeevvvveeeennnntttt....lllloooogggg. Enclose the _u_s_e_r__n_a_m_e in quotation marks if it contains space characters. -note _u_s_e_r__n_o_t_e Records user-supplied text in the event log. The _u_s_e_r__n_o_t_e is a text string enclosed in quotation marks. -patch aaaallllllll -patch _p_a_t_c_h__i_d [_p_a_t_c_h__i_d]... Directs dddduuuuppppaaaattttcccchhhh to remove all aaaallllllll patches or specific (_p_a_t_c_h__i_d) patches from the specified patch kit. See Specifying a Patch ID. -product _p_r_o_d_u_c_t__i_d [_p_r_o_d_u_c_t__i_d]... Mandatory when more than one product is installed. Specifies the installed operating system and/or TruCluster software product to be patched. Product ID specifications are case insensitive. Wildcards are not permitted. See Specifying a Product ID. _O_p_t_i_o_n_a_l -_d_e_l_e_t_e _O_p_t_i_o_n_s -data _d_a_t_a__f_i_l_e Specifies a file that contains arguments (in the form _a_r_g_u_m_e_n_t = _v_a_l_u_e) to the dddduuuuppppaaaattttcccchhhh command. See Using a Data File. C-4 Using dupatch from the Command Line -nolog Directs dddduuuuppppaaaattttcccchhhh to not record actions in a sssseeeessssssssiiiioooonnnn....lllloooogggg file. -noroll Directs dddduuuuppppaaaattttcccchhhh to remove patches on a cluster using the no-roll procedure rather than the default rolling-upgrade procedure. -proceed Directs dddduuuuppppaaaattttcccchhhh to delete any patches that passed the predeletion check, even if one or more patches failed the predeletion check. If -proceed is omitted, dddduuuuppppaaaattttcccchhhh will not delete any patches if at least one patch failed the predeletion check. The predeletion check determines whether any installed patches have dependencies on any of the patches listed for removal. If such dependencies exist, dddduuuuppppaaaattttcccchhhh blocks the removal of any required patch. -root _r_o_o_t__p_a_t_h Specifies an alternate root location. The default _r_o_o_t__p_a_t_h is //// for all operations. _R_e_q_u_i_r_e_d -_t_r_a_c_k _O_p_t_i_o_n_s -type _f_i_l_e -type _k_i_t -type _p_a_t_c_h Lists all patched files (-file), installed patch kits (-kit), or installed patches (-patch). _O_p_t_i_o_n_a_l -_t_r_a_c_k _O_p_t_i_o_n_s -data _d_a_t_a__f_i_l_e Specifies a file that contains arguments (in the form _a_r_g_u_m_e_n_t = _v_a_l_u_e) to the dddduuuuppppaaaattttcccchhhh command. See Using a Data File. -kit _k_i_t__l_o_c_a_t_i_o_n Identifies the location of the patch kit for which the reports will cover. _k_i_t__l_o_c_a_t_i_o_n is a full path to the directory containing the patch kit. -nolog Directs dddduuuuppppaaaattttcccchhhh to not record actions in a session.log file. -root _r_o_o_t__p_a_t_h Specifies an alternate root location. The default _r_o_o_t__p_a_t_h is //// for all operations. _D_e_s_c_r_i_p_t_i_o_n Using dupatch from the Command Line C-5 The dddduuuuppppaaaattttcccchhhh utility is an interactive program used to install and delete software patches to the Tru64 UNIX operating system and systems running TruCluster software products. With dddduuuuppppaaaattttcccchhhh you can baseline your system to incorporate any system files that may have been manually installed. You can also use dddduuuuppppaaaattttcccchhhh to obtain a list of installed patches or view the system history of patch installations and deletions. When invoked without arguments, dddduuuuppppaaaattttcccchhhh is run interactively by providing menus that step you through the patching procedure while prompting you for necessary information. Alternatively, you can invoke dddduuuuppppaaaattttcccchhhh from the command line, whereby you supply required arguments to the dddduuuuppppaaaattttcccchhhh command. Although you can install patches in either single-user or multiuser mode, the use of single-user mode is strongly recommended. In multiuser mode, libraries and system files that are in use by active processes may be affected by the new patches. The patching of any active library or system files may result in unexpected consequences. On clustered systems running TruCluster software Version 5.0A or higher, the dddduuuuppppaaaattttcccchhhh utility is run in conjunction with the rolling upgrade procedure. (See the _P_a_t_c_h _K_i_t _I_n_s_t_a_l_l_a_t_i_o_n _I_n_s_t_r_u_c_t_i_o_n_s or the _C_l_u_s_t_e_r _I_n_s_t_a_l_l_a_t_i_o_n manual for information about performing a rolling upgrade.) _U_s_i_n_g _a _D_a_t_a _F_i_l_e The _d_a_t_a__f_i_l_e that you specify with the -data option is a fully qualified file location and a file that contains command-line options with the following format: _o_p_t_i_o_n_1 = _v_a_l_u_e _o_p_t_i_o_n_2 = _v_a_l_u_e 000_0_o_p_t_i_o_n_3 = _n For example: kit = /mnt name = Joe note = Installing April patch kit product = Tru64_UNIX_V5.1 patch = 27.01 63.00 74 83.01 product = TruCluster_V5.1 # multiple patches are separated by space characters patch = 21.01 27.01 40 precheck_only nobackup Blank lines and comments (preceded with #) are allowed. Line continuation ( \ ) is required if a specification spans multiple lines. Only one _d_a_t_a__f_i_l_e is permitted per command line and nested _d_a_t_a__f_i_l_e specifications are not C-6 Using dupatch from the Command Line allowed. _S_p_e_c_i_f_y_i_n_g _a _P_r_o_d_u_c_t _I_D The _p_r_o_d_u_c_t__i_d you specify with the -product option is one of the following: TRU64_UNIX_V5.1 TRU64_UNIX_V5.0A TRU64_UNIX_V5.0 TRU64_UNIX_V4.0G TRU64__UNIX_V4.0F DIGITAL_UNIX_V4.0D TruCluster_V5.1 TruCluster_V5.0A TruCluster_V1.6 TruCluster_V1.5 +o A _p_r_o_d_u_c_t__i_d specification is not necessary when the system being patched has only one product installed; for example, Tru64 UNIX Version 4.0F with no TruCluster software product. +o A _p_r_o_d_u_c_t__i_d specification only applies to the _p_a_t_c_h__i_d specifications that follow it and ends when another _p_r_o_d_u_c_t__i_d is specified. +o Because the purpose of the _p_r_o_d_u_c_t__i_d is to clarify the _p_a_t_c_h__i_d specification, the _p_r_o_d_u_c_t__i_d must precede the _p_a_t_c_h__i_d. +o Product strings are not case sensitive. Wildcards are not permitted. The following example shows a product string: dupatch -install -product DIGITAL_UNIX_V4.0F -patch 1.1 -product TruCluster_V1.6 -patch 35 \ -name Joe -note "installing patch 1.1" -kit _S_p_e_c_i_f_y_i_n_g _a _P_a_t_c_h _I_D The _p_a_t_c_h__i_d you specify with the -patch option has the following format: xxxx[.yy] For example: 15 200.11 10.2 00111.02 +o Both xxxx and yy are numeric values; leading zeros can be omitted. Using dupatch from the Command Line C-7 +o Patch revision (yy), when left unspecified, maps to wildcarded "??" +o Multiple _p_a_t_c_h__i_d specifications are separated by white space. +o The keyword aaaallllllll cannot be combined with other patch IDs. +o If _p_r_o_d_u_c_t__i_d is used, _p_a_t_c_h__i_d must come after it. _S_p_e_c_i_f_y_i_n_g _a _R_o_o_t _P_a_t_h The _r_o_o_t__p_a_t_h you specify with the -root option specifies an alternative root for the specified operation. (The -root option is similar to the -D option of sssseeeettttlllldddd.) The following list describes characteristics of the -root option. +o The root path must be the root of a complete UFS file system or AdvFS domain. +o The default root path is //// for all operations. +o If -root is the only argument on the command line, dddduuuuppppaaaattttcccchhhh will proceed in interactive mode; this is an exception to the command-line rule previously mentioned. +o When performing an alternate root installation, the -noauto flag is set implicitly. _S_p_e_c_i_f_y_i_n_g _a _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e The -cfgfile option to the -install and -delete command options allows you to call in the system configuration file (////uuuussssrrrr////ssssyyyyssss////ccccoooonnnnffff////_c_o_n_f_i_g__f_i_l_e). For information about creating or modifying a ccccoooonnnnffffiiiigggg____ffffiiiilllleeee, see the ddddooooccccoooonnnnffffiiiigggg(8) and ssssiiiizzzzeeeerrrr(8) reference pages. _R_e_s_t_r_i_c_t_i_o_n_s The following restrictions apply to the dddduuuuppppaaaattttcccchhhh utility. You must be logged in as rrrrooooooootttt to run dddduuuuppppaaaattttcccchhhh. The system must be running in single-user mode when removing patches. The -product option must precede the -patch option on the command line. _E_x_i_t _S_t_a_t_u_s 0000 (Zero) Success. >>>>0000 C-8 Using dupatch from the Command Line An error occurred. _E_r_r_o_r_s See the Patch Kit Installation Instructions for a detailed list of dupatch error messages. _E_x_a_m_p_l_e_s 1. The following interactive example shows how to invoke the menu-driven interface of dddduuuuppppaaaattttcccchhhh: # dddduuuuppppaaaattttcccchhhh Tru64 UNIX Patch Utility (Rev. 34-00) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1111 2. The following interactive example shows how to perform a preinstallation check on patch 00183.00 contained in the kit located at /_m_n_t/_p_a_t_c_h__k_i_t. This will verify that the specified patch can be installed onto the system without actually proceeding with the installation: # dddduuuuppppaaaattttcccchhhh ----iiiinnnnssssttttaaaallllllll ----kkkkiiiitttt ////mmmmnnnntttt////ppppaaaattttcccchhhh____kkkkiiiitttt ----nnnnaaaammmmeeee JJJJeeeessssssssiiiiccccaaaa ----nnnnooootttteeee \\\\ """"PPPPrrrreeee----IIIInnnnssssttttaaaallllllllaaaattttiiiioooonnnn cccchhhheeeecccckkkk oooonnnnllllyyyy oooonnnn 111188883333....00000000"""" ----ppppaaaattttcccchhhh 111188883333....00000000 ----pppprrrreeeecccchhhheeeecccckkkk____oooonnnnllllyyyy 3. The following interactive example shows how to install all patches in kit located at /_m_n_t/_p_a_t_c_h__k_i_t: # dddduuuuppppaaaattttcccchhhh ----iiiinnnnssssttttaaaallllllll ----kkkkiiiitttt ////mmmmnnnntttt////ppppaaaattttcccchhhh____kkkkiiiitttt ----nnnnaaaammmmeeee JJJJeeeessssssssiiiiccccaaaa \\\\ ----nnnnooootttteeee """"iiiinnnnssssttttaaaallllllll aaaallllllll ppppaaaattttcccchhhheeeessss"""" ----ppppaaaattttcccchhhh aaaallllllll 4. The following interactive example shows how to identify all patches Using dupatch from the Command Line C-9 installed on system: # dddduuuuppppaaaattttcccchhhh ----ttttrrrraaaacccckkkk ----ttttyyyyppppeeee ppppaaaattttcccchhhh 5. The following interactive example shows how to list all system files updated by installed patches: # dddduuuuppppaaaattttcccchhhh ----ttttrrrraaaacccckkkk ----ttttyyyyppppeeee ffffiiiilllleeee 6. The following interactive example shows how to remove patch 00183.00 from the system. Note that the system will automatically be rebooted upon patch deletion because ----nnnnooooaaaauuuuttttoooo was not specified: # dddduuuuppppaaaattttcccchhhh ----hhhheeeellllpppp ppppaaaattttcccchhhh____iiiidddd 7. The following interactive example shows how to obtain help on specifying _p_a_t_c_h__i_d usage: # dddduuuuppppaaaattttcccchhhh ----ddddeeeelllleeeetttteeee ----ppppaaaattttcccchhhh 111188883333....00000000 ----nnnnaaaammmmeeee JJJJooooeeee \\\\ ----nnnnooootttteeee """"ddddeeeelllleeeetttteeee ppppaaaattttcccchhhh 00000000111188883333....00000000 ffffrrrroooommmm ssssyyyysssstttteeeemmmm"""" _E_n_v_i_r_o_n_m_e_n_t _V_a_r_i_a_b_l_e_s The following environment variables affect the execution of dddduuuuppppaaaattttcccchhhh: MMMMAAAAXXXX____LLLLOOOOGGGGSSSS Specifies the maximum number of session logs to be retained on the system. The default number is 25. If, for example, MMMMAAAAXXXX____LLLLOOOOGGGGSSSS is set to 25, the oldest session log would be named sssseeeessssssssiiiioooonnnn....lllloooogggg....22224444 and the current would be named sssseeeessssssssiiiioooonnnn....lllloooogggg, with no number affixed. ____RRRROOOOOOOOTTTT Overrides the location of the root directory. The default value is /, the system root directory. This value must be the top-level directory of a file system (or an AdvFS domain). PPPPAAAATTTTCCCCHHHHDDDDIIIIRRRR Specifies the path to the patch tools repository. The default value is $$$$____RRRROOOOOOOOTTTT////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh. _F_i_l_e_s ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////sssseeeessssssssiiiioooonnnn....lllloooogggg...._n This file captures dddduuuuppppaaaattttcccchhhh activities. A separate session log is written with C-10 Using dupatch from the Command Line each dddduuuuppppaaaattttcccchhhh session and log files from the previous sessions are saved. The order is first in, first out, with sssseeeessssssssiiiioooonnnn....lllloooogggg....$_M_A_X__L_O_G_S as the oldest file. ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////DDDDuuuuppppaaaattttcccchhhh____llllooooaaaadddd_____D_a_t_e.log This file specifies the date when the patch tools were loaded or updated onto the system. ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////bbbbaaaasssseeeelllliiiinnnneeee....lllloooogggg...._n This file records the screen output from the baselining session. A separate baseline log is written for each baselining session and log files from previous sessions are saved. The order is first in, first out, with sssseeeessssssssiiiioooonnnn....lllloooogggg....$_M_A_X__L_O_G_S as the oldest file. ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////lllloooogggg////eeeevvvveeeennnntttt....lllloooogggg...._n This file captures information regarding patch installation and removal operations. A separate event log is written each time patches are installed or removed. Log files from previous sessions are saved. The order is first in, first out, with sssseeeessssssssiiiioooonnnn....lllloooogggg....$_M_A_X__L_O_G_S as the oldest file. ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////bbbbaaaacccckkkkuuuupppp The files in this directory are used to restore the system to its former state if patches are deleted. ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////ddddoooocccc////OOOOSSSSFFFFPPPPAAAATTTT****_p_a_t_c_h__n_o.abs Provides brief summary of what a patch fixes. ////vvvvaaaarrrr////aaaaddddmmmm////ppppaaaattttcccchhhh////ddddoooocccc////OOOOSSSSFFFFPPPPAAAATTTT****_p_a_t_c_h__n_o.txt Provides detailed discussion of what a patch fixes. _r_o_o_t-_p_a_t_h/usr/.smdb./OSFPAT*.inv Lists the subset inventory files. _r_o_o_t-_p_a_t_h/usr/.smdb./OSFPAT*.ctrl Lists the subset control files. _r_o_o_t-_p_a_t_h/usr/.smdb./OSFPAT*.scp Lists the subset inventory programs. _r_o_o_t-_p_a_t_h/usr/.smdb./OSFPAT*.lk Lists the subset installed lock files. _S_e_e _A_l_s_o Commands: sssseeeettttlllldddd(8), cccclllluuuu____uuuuppppggggrrrraaaaddddeeee(8) Using dupatch from the Command Line C-11 Documents: _P_a_t_c_h _I_n_s_t_a_l_l_a_t_i_o_n _I_n_s_t_r_u_c_t_i_o_n_s _P_a_t_c_h _S_u_m_m_a_r_y _a_n_d _R_e_l_e_a_s_e _N_o_t_e_s supplied with the patch kit to be installed Tru64 UNIX _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e Tru64 UNIX _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual TruCluster Software Products _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n manual for the installed 4.0n or 5.n cluster system TruCluster Software Products _C_l_u_s_t_e_r _A_d_m_i_n_i_s_t_r_a_t_i_o_n manual for the installed 4.0n or 5.n cluster system C-12 Using dupatch from the Command Line Glossary bbbbaaaasssseeeelllliiiinnnniiiinnnngggg A dddduuuuppppaaaattttcccchhhh feature that looks at the files installed on a system, compares them to the files it expects to find, and prevents the installation of any patch files that might cause an incompatibility among system files. CCCCuuuussssttttoooommmmeeeerrrr----SSSSppppeeeecccciiiiffffiiiicccc PPPPaaaattttcccchhhh ((((CCCCSSSSPPPP)))) KKKKiiiitttt A patch kit that is developed and made available to resolve a problem for a specific customer. A Customer-Specific patch is developed with prior knowledge of that customer's unique hardware and software configuration and environment. Customer-Specific patches may not be useful for another customer's system. An Early Release patch is a type of CSP. See also _E_a_r_l_y _R_e_l_e_a_s_e _P_a_t_c_h (_E_R_P) _K_i_t, _R_e_l_e_a_s_e _P_a_t_c_h _K_i_t dddduuuuppppaaaattttcccchhhh A utility included in a patch kit that installs, removes, and manages patches for Tru64 UNIX and TruCluster software products. This utility is installed and left on the system through the successful installation of a patch kit. EEEEaaaarrrrllllyyyy RRRReeeelllleeeeaaaasssseeee PPPPaaaattttcccchhhh ((((EEEERRRRPPPP)))) KKKKiiiitttt A patch kit that contains a patch or patches that will be included in a Release Patch Kit that is still under development. ERPs, which are a type of Customer-Specific patch, are provided by HP to help customers who have an immediate need for some specific functionality that will be included in an upcoming Release Patch Kit. See also _C_u_s_t_o_m_e_r-_S_p_e_c_i_f_i_c _P_a_t_c_h (_C_S_P) _K_i_t, _R_e_l_e_a_s_e _P_a_t_c_h _K_i_t ffffuuuullllllll iiiinnnnssssttttaaaallllllllaaaattttiiiioooonnnn A Tru64 UNIX installation that creates new file systems and loads a full copy of the operating system from the kit onto a system. Any other version of the operating system, any layered products, and any patches that previously existed on the system are overwritten. A full installation does not preserve system customizations (for example, user or data files) because the root (////), ////uuuussssrrrr, and ////vvvvaaaarrrr file systems are re-created during the process. See also _u_p_d_a_t_e _i_n_s_t_a_l_l_a_t_i_o_n iiiinnnnaaaauuuugggguuuurrrraaaallll ppppaaaattttcccchhhh kkkkiiiitttt ((((IIIIPPPPKKKK)))) The first Release Patch Kit for a specific operating system version; for example Patch Kit 0001 for Version 5.1A.. nnnnoooo----rrrroooollllllll ppppaaaattttcccchhhhiiiinnnngggg A process that patches your cluster in one operation and requires only one reboot of the whole cluster to complete the operation. This method was developed for mission-critical environments to provide a way to apply patches quickly, with a minimum amount of down time. The no-roll patch process is a modification of dddduuuuppppaaaattttcccchhhh; that is, all patches are installed or removed entirely using the dddduuuuppppaaaattttcccchhhh utility, as opposed to the cccclllluuuu____uuuuppppggggrrrraaaaddddeeee and dddduuuuppppaaaattttcccchhhh utilities used in the rolling upgrade procedure. The no-roll process conducts significantly fewer operations than the rolling upgrade procedure. See also _r_o_l_l_i_n_g _u_p_g_r_a_d_e ooooffffffffiiiicccciiiiaaaallll ppppaaaattttcccchhhh See _R_e_l_e_a_s_e _P_a_t_c_h _K_i_t ppppaaaattttcccchhhh A file or a collection of files that contain fixes to problems. When possible, patches are merged together into one patch if they have intersecting files or codependencies. A patch may correct one or more problems. Each patch is packaged in its own sssseeeettttlllldddd subset. The subsets are managed by a utility named dddduuuuppppaaaattttcccchhhh. ppppaaaattttcccchhhh aaaapppppppplllliiiiccccaaaabbbbiiiilllliiiittttyyyy A file-by-file check of system files to determine whether a patch might cause a system to be degraded or crash. The installation of a patch is blocked if any system files to be replaced by that patch are not valid predecessors of the patch files. RRRReeeelllleeeeaaaasssseeee PPPPaaaattttcccchhhh KKKKiiiitttt A patch kit that HP provides to modify a specific version of the Tru64 UNIX operating system and TruCluster software. Sometimes referred to as official patch kits, Release Patches Kits are intended for worldwide distribution and can be safely used on any customer's system within the guidelines documented in the kit. The patches in a Release Patch Kit are referred to as Release patches. See also _C_u_s_t_o_m_e_r-_S_p_e_c_i_f_i_c _P_a_t_c_h (_C_S_P) _K_i_t, _E_a_r_l_y _R_e_l_e_a_s_e _P_a_t_c_h (_E_R_P) _K_i_t rrrroooolllllllliiiinnnngggg uuuuppppggggrrrraaaaddddeeee A software upgrade of a cluster that is performed while the cluster is in operation. One member at a time is rolled and returned to operation while the cluster transparently maintains a mixed-version environment for the base 2 Glossary operating system, cluster, and Worldwide Language Support (WLS) software. Clients accessing services are not aware that a rolling upgrade is in progress. On Version 5.0A and higher systems, you use a rolling upgrade to patch a cluster or to update the Tru64 UNIX operating system or TruCluster software on a cluster. The procedure is the same for both types of upgrades — the only difference is the command you run during the install stage of the rolling upgrade procedure. See also _n_o-_r_o_l_l _p_a_t_c_h_i_n_g sssseeeettttlllldddd An interactive program for installing and managing software subsets. Software products are organized into subsets that can be loaded, deleted, inventoried, and configured. The load operation reads software from disk, tape, CD-ROM, or an Internet installation server. The patch installation tool, dddduuuuppppaaaattttcccchhhh, is based on the sssseeeettttlllldddd program. ttttaaaarrrr ffffiiiilllleeee A file created with the ttttaaaarrrr command that saves and restores multiple files in a single file. Tru64 UNIX patch kits are provided as tar files (except for kits included on a Patch CD-ROM). uuuuppppddddaaaatttteeee iiiinnnnssssttttaaaallllllllaaaattttiiiioooonnnn A type of installation that preserves disk partitions, file systems, file customizations, the network, print and mail environments, user accounts, user-created files, and any other system setup you may have done. If software patches had been applied to the operating system, it would not be necessary to remove the patches before beginning the update process, which is designed to update and reinstall any software fixes or features that were supplied in Release patches. See also _f_u_l_l _i_n_s_t_a_l_l_a_t_i_o_n vvvveeeerrrrssssiiiioooonnnn sssswwwwiiiittttcccchhhh During a rolling upgrade, a version switch manages the transition of the active version to the new version of an operating system. The active version is the one that is currently in use. The purpose of a version switch in a cluster is to prevent the introduction of potentially incompatible new features until all members have been updated. See also _r_o_l_l_i_n_g _u_p_g_r_a_d_e Glossary 3