text:
This action might not be possible to undo. Are you sure you want to continue?
A guide to patching HP-UX 11.X systems
5967-3578 June 2001 © 2001 Hewlett-Packard Company
The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty. A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. Restricted Rights Legend. Use, duplication, or disclosure by the U.S. Government Department is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies. HEWLETT-PACKARD COMPANY 3000 Hanover Street Palo Alto, California 94304 U.S.A. Copyright Notices. © 2001 Hewlett-Packard Company, all rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws. Trademark Notices.
HP-UX is a registered trademark of the Hewlett-Packard Company. Motif, OSF/1, UNIX, the "X" device and The Open Group are registered trademarks of The Open Group in the US and other countries. Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Revision History.
January 2000, Preliminary Edition. December 2000, Edition 1, part no. B3782-90829. June 2001, Edition 1, new part number.
This guide's printing date and part number indicate the current edition. The printing date changes when a new edition is printed. Minor corrections and updates incorporated at reprint do not cause the date to change. The part number changes when extensive technical changes are incorporated. New editions of this manual will incorporate all material updated since the previous edition. For the latest version, see the Patch Management sections of: http://docs.hp.com/os/11.00/ or http://docs.hp.com/os/11i/ For additional help with patching HP-UX systems, see: http://itrc.hp.com/ or http://software.hp.com/SUPPORT_PLUS/
Please direct comments regarding this guide to: Hewlett-Packard Company HP-UX Learning Products, MS 11 3404 East Harmony Road Fort Collins, Colorado, 80528-9599 You can also send your questions and comments to firstname.lastname@example.com. If appropriate, include page numbers and document revision with your comments.
HP-UX Patch Management
CHAPTER 1 Introduction 1 Overview 1 Getting Help 3 Other Sources of Information 3 HP-UX Technical Documentation 3 HP Software Depot 3 Interex 3 HP-UX Administrators Mailing List 4 Other Web Resources 4 CHAPTER 2 Planning for Recovery 5 Recovery Planning and Patching The Root Volume Group 5 5 Separating Volatile Data from Stable System Data 6 Preserving Configuration via NIS or DHCP 6 File System Guidelines 7 Ignite-UX 7 Plan for Reinstallation Have a Wish List 8 8 CHAPTER 3 Acquiring Patches 9 The Patch Database 10 Searching for HP-UX Patches by Keywords 11 Searching by Patch IDs 13 Dependency Analysis and the Patch Database 14 HP Patch Bundles 15 Obtaining Patch Bundles from Software Depot 15 Support Plus Media 15 Custom Patch Manager 18 About CPM 18 Using CPM 18 Step 1: Collect Configuration Informations 18 Step 2: Perform Patch Analysis 20 Step 3: Conflict Analysis 22 Step 4: Package and Download Your Patches 23 Custom Patch Notification 23 The Fulfillment Server 25 Accessing the Fulfillment Server via ftp 25 Web Access to FFS 25 The FFS Directories 27 Downloading the patch 27 Patch Recommendation Ratings About Patch Notes 29 Resolving Patch Conflicts 30 28 HP-UX Patch Management 5 .
CHAPTER 4 Depot Management 31 Custom Depots 31 Benefits of Creating Depots 31 Types of Depots 32 HP-UX 10.00 35 Dependency Analysis for HP-UX 11i 36 Depot Access 36 36 Depot Registration 36 Access Control Lists (swacls) CHAPTER 5 Patch Installation System Preparation 37 37 Back-ups Back-ups! 37 A Note on Change Management 37 System Activity 38 Patch Committal Prior to Depot Installation 38 Committed Patch Removal 39 Planning for System Reboot When is a Reboot Needed? Timing of the Reboot 41 41 41 Installation 41 Using the SD-UX Matching Operations 41 Installing to a Committed Patch State 43 Installing Support Plus Patch Bundles 43 Step 1: Mount the CD 43 Step 2: Check for Last-Minute Information 43 Step 3 (Optional): Set Up Sharing for Remote Systems Step 4 (Optional): Set Up Hard Disk Access 44 Step 5: Install the Selected Bundles 45 Usage Tip 46 44 Finishing Touches 46 The swverify command 46 Checking the Logs 46 6 .X vs.X Depots 32 Patch Depots 32 Periodic Patch Depot 32 Critical Fix Patch Depot 32 Patch Hubs 33 Creating a Patch Depot 34 Preparation Tasks 34 Copying Existing Depots 34 Combining Patch Depots 34 Removing Superseded Patches 35 Dependency Analysis for HP-UX 11. 11.
Appendix A Basic Patch Concepts 47 Patch Mechanics 47 Ancestors and Patches 47 Patch Supersession 48 Patch Rollback 48 Patch Commitment 49 Patch Dependencies 49 Dependency Types 50 Enforced Patch Dependencies 50 Viewing Dependency Information 51 The HP-UX Patch 51 Patch Status 51 The Critical Patch 52 Patch Identification 52 The Patch Shar File 53 Appendix B SD-UX Tools & Objects The Basic SD-UX Object Types 55 The Fileset 55 The Product 56 The Bundle 56 The Depot 56 55 Patch Related Object Attributes 56 ancestor 56 applied_patches 56 applied_to 56 category_tag 57 is_patch 57 is_sparse 57 is_reboot 57 patch_state 57 readme 58 software_spec 58 state 58 supersedes 58 superseded_by 58 Introduction to the SD-UX Commands The swinstall Command 59 59 Synopsis 59 Patch Related Command Line Arguments 59 Patch-Related Options 60 Examples 62 The swcopy Command 62 62 Synopsis 62 Patch Related Command Line Arguments Patch Related Options 63 Examples 64 The swremove Command 64 Synopsis 64 Patch Related Command Line Arguments 65 HP-UX Patch Management 7 .
Patch Related Options 65 Examples 66 The swlist Command 66 66 Synopsis 66 Patch Related Command Line Arguments Patch Related Options 68 Examples 68 The swreg Command 69 69 Synopsis 69 Patch Related Command Line Arguments Patch Related Options 69 Examples 69 The swmodify command 69 70 Synopsis 69 Patch Related Command Line Arguments Patch Related Options 70 Examples 70 The swpackage command 71 Synopsis 71 Patch Related Command Line Arguments 71 Patch Related Options 71 Examples 72 The cleanup Command 72 Synopsis 72 Patch Related Command Line Arguments 72 The show_patches Command 72 72 Synopsis 72 Patch Related Command Line Argument: Other Options and Aids to Using the SD-UX Commands Software Specifications 73 Session Files 73 Setting Default Values for Command Options 74 73 Appendix C The Patch Text File 75 8 .
Patching has its own terminology and tools. The current set of chapters and appendices are: • Chapter 2: Planning for Recovery The first rule of system management should be to expect the best.CHAPTER 1 Introduction HP-UX system patching is one of the most confusing areas for new system administrators. Overview This document is built around the concept of the patch depot.00 and 11i. it is usually found piecemeal in the back sections of various manuals. • Chapter 4: Depot Management However patches are acquired. the types of patch depots and their use are covered. each with different abilities. while supporting information is provided in the appendices. The 11. Planning for recovery can create a virtual "Undo" button that allows a system to return to a previous state. its contents must be installed on the target systems. Not only does it protect systems from the unexpected. The chapters provide information regarding the steps required to create and use patch depots. This chapter discusses the basic requirements and some options for system recovery. Some sources may require certain levels of support while others are free. but plan for the worst. but by limiting risk it can also provide the confidence needed to support a proactive patching methodology. and patch management has its own motivations and methods. HP-UX Patch Management 1 . • Chapter 5: Patch Installation Once a depot has been created. This chapter describes the recommended steps to execute and verify patch installation. a patch depot should be created to use them efficiently. While some documentation exists. In this chapter. The first 11i release was introduced in December of 2000. This document is intended to pull together all the technical information required to understand HP-UX 11. this is the tag that you will see whenever you access the online resources and the patch text files addressed in this document.11. This release has a uname -r value of 11.X patching. Patch depots are a mechanism through which systems can be managed as groups rather than as individual systems. • Chapter 3: Acquiring Patches Patches are available from a wide variety of sources. This chapter describes an array of patch sources and how they may be used to acquire patches.X operating systems include 11.
Typographical Conventions This guide uses the following typographical conventions: Boldface Computer User input Important concepts defined for the first time appear in boldface. Computer font indicates literal items displayed by the computer. This appendix provides a basic understanding of patch concepts. but remains the core documentation of each patch. For example. the sections that are of specific interest to patching are not always readily apparent. enter: cd Italics Manual titles. This appendix provides SD information related only to patching. sans-serif font denotes keyboard keys and on-screen menu items. The vertical bar | separates syntax items in a list of choices. you can enter any of these three items in this syntax: ls [-u | -x] Enter Text in this bold. Patches have a terminology and operations all their own. • Appendix B: SD-UX Tools & Objects While Software Distributor (SD) has a wealth of documentation available. • Appendix C: The Patch Text File The patch text file can be found in a variety of locations. For example.text file with a brief description. 2 Introduction . This appendix lists all of the fields within the . you would substitute an actual directory name for directory_name in this command: cd directory_name [ ] and | Brackets [] enclose optional items in command syntax.Overview • Appendix A: Basic Patch Concepts Patches are different from other types of HP-UX software. For example: file not found Bold. computer text indicates literal items that you type. A notation of Ctrl-Q indicates that you should hold the Ctrl key down and press Q. variables in commands and emphasized words appear in italics. For example: To change to your account's home directory.
Review the main page (http://www. maintains this list of technical resources for HP-UX systems.hp.com This source provides online access to HP-UX manuals.com The HP Software Depot. many products (such as Ignite-UX and the Support Plus patch bundles) are free. which is not a part of HP. HP-UX Patch Management 3 . and electronic patch management services. download. Interex.Getting Help Getting Help For technical support. HP-UX releases. or purchase. Interex http://www.org/tech/9000/index.hp. HP Software Depot http://software. Design and Implementation—guidance to manage changes to your IT environment Other Sources of Information HP-UX Technical Documentation All HP-UX technical documentation is available at: http://docs.org) to learn about the benefits of membership.com Use the ITRC to: • Quickly access customized support tools • Make informed decisions with proactive information • Access a rich knowledge database to quickly self-solve problems • Submit hardware and software calls online • Identify and download patches quickly and accurately • Get one-stop access to software updates for your entitlements • Take advantage of ITRC resources across the IT life-cycle: — Forums—a community where you can collaborate and tackle IT questions with peers — Training—including online seminars and self-paced web-based training — Planning. and white papers. which provides a variety of HP-UX software. known as Interex. Information on particular hardware platforms.html The International Association of Hewlett-Packard Computing Professionals. guides. software management. is also noted for the yearly Interworks and HPWorld trade shows and for regional users groups.interex.hp. contact HP's IT Resource Center (ITRC): http://itrc.interex. While some require purchase. and software products is available for browsing.
com/hpux/os/11. send email to email@example.com. Japan.Other Sources of Information HP-UX Administrators Mailing List http://www.hp. To join the list itself.com/SD_AT_HP/ • European information: http://itrc. including STM and EMS Hardware Monitors: http://docs.hp.com/hpux/diag/ • Latest HP-UX 11.hp. Italy.edu/ or http://hpux.wisc. France.0/ http://docs.com/products/IUX/ • Software Distributor (SD): http://software. and the UK.hp. This URL provides an interface to the list archives dating back to 1995.hp.dutchworks. Netherlands. South Africa.edu/ Mirrored sites are available for Canada.X manuals and white papers: http://docs.com/ Select the link to the European site. 4 Introduction .cae.cs. Other Web Resources Additional help with HP-UX patching and related resources is available on the Web: • Support Plus information: http://software.hp.nl and include the following command in the body of the message: subscribe hpux-admin-digest See also the Software Archive and Porting Centre for HP-UX at this URL: http://hpux.hp.com/SUPPORT_PLUS/ • Latest hardware support tools (diagnostics) information.nl/htbin/hpsysadmin Another resource outside of HP is the HP-UX Administrators Mailing List. Germany.hp.com/operating/ • Latest Ignite-UX information: http://software.com/hpux/os/11i/ • HP-UX 11i features and news: http://unix.
• • • The Root Volume Group The Logical Volume Manager (LVM) lets you subdivide a single disk or treat a group of disks as a single unit. Recovery Planning and Patching • Establish a recovery plan and do all necessary pre-work. selecting a recovery technique. and change carries potential risk. To enable the recovery options discussed in this chapter. Use more than one recovery technique to protect yourself from events such as a bad tapes or network failures. usually named vg00).CHAPTER 2 Planning for Recovery A patch introduces change into a system. These concepts also apply to users of whole-disk HFS root disks. A prudent system administrator manages risk by planning for system recovery. The documentation for each patch lists all of the defects or enhancements that the patch addresses. planning for system re-installation. HP-UX Patch Management 5 . but volume groups are usually named as follows: • /dev/vg00 • /dev/vg01 • /dev/vg02. A volume group is a group of one or more physical volumes or disks. The physical volumes in a volume group form a pool of disk space which may be allocated to one or more logical volumes. and so on. This includes setting up the root volume group. This chapter presents an overview of recovery planning and techniques. Proactive maintenance—fixing known problems before they appear on a system—can reduce the cost of a system failure. Use patches as a form of proactive maintenance. You can weigh the known cost of returning to an original system state against the documented conditions of a patch. you must properly set up the volume group that contains the core system (also known as the root volume group. and keeping a "wish list" of changes you want to make to a system when it is down. You can use any naming convention that you wish.
see Installing and Administering NFS Services • For more information on DHCP. An NIS client gets configuration information from the master server or a slave server instead of from its local configuration files. For example. These and related documents are available on http://docs. and other user and application data. or maps. You may have other volume groups on your system for applications. you must place some restrictions on the root volume group: • Limit the size of the root volume group — Reduces the size of recovery images — Reduces the cost of disk mirroring • Do not place volatile data on the root volume group — Avoids loss of data when you restore the root volume image — Saves an additional recovery step • Keep all system data within the root volume group — Avoids unexpected recovery problems.hp.The Root Volume Group By default. see the Ignite-UX Administration Guide and Installing and Administering Internet Services. NIS allows centralized management of common configuration files. /etc/hosts. Preserving Configuration via NIS or DHCP Network Information Services (NIS) and Dynamic Host Configuration Protocol (DHCP) let you maintain data off of your system. The master server may distribute copies of the maps to NIS slave servers to provide load balancing and reliability. like /etc/passwd. Ignite-UX may not be able to save critical data if you have relocated parts of the directory structure. and /etc/services.com/ 6 Planning for Recovery . Separating Volatile Data from Stable System Data You can preserve a known system state by creating an image of the root volume group. This off-system storage of system information that changes frequently (such as networking configuration and password files). • For more information on NFS. You can then return to that image after a failure. make sure you have some kind of alternate recovery methods. To preserve the root volume group as a whole. can simplify restoration. If you do break these rules. See also "File System Guidelines" on page 7 for more information TIP: Do not break these rules of data separation except to meet a specific need. An NIS master server holds master copies of the configuration files. vg00 is a special volume group known as the "root volume group" which typically contains the default boot disk and the majority of the HP-UX operating system.
and duplication. /stand. They must exist completely within the root volume group. While not required to be included within the root volume group. and /etc These directories contain the critical parts of the Core System required for booting. time can be saved by including all of the backup and recovery software (such as Omniback) within the system image.hp. is expected to hold dynamic user data and should be isolated from both the root volume group and /usr.hp. (The Ignite-UX recovery tools will preserve the full contents of the volume group that includes the /usr directories.) • /home This directory. • • • Chapter 2 tells you how to install and administer an Ignite-UX server.Ignite-UX File System Guidelines To best support recovery. including: — make_tape_recovery(1M) — make_net_recovery(4) — Expert (manual) recovery procedure using Core media tools The Ignite-UX Administration Guide is also available on the Instant Information CD and at http://docs.com/products/IUX The Ignite-UX Administration Guide provides complete information about using Ignite-UX. To download the latest version and to browse Ignite-UX documentation. • backup & recovery tool In the event that additional data will need to be restored from backup media. recovery. • /usr The /usr directory tree contains those elements of the Core System that support the post-boot system functionality. This is often accomplished via NIS and the NFS automounter.) • /opt and /var Only certain parts of /opt and /var (such as /var/adm/sw) can be considered to be part of the Core System. Chapter 11 tells you how to use the Ignite-UX system recovery tools. Chapter 3 tells you how to use configuration files to set up system recovery information. /sbin. Ignite-UX HP's Ignite-UX is a set of tools for system installation. (Ignite-UX will preserve these areas regardless of the parent volume group. Ignite-UX is available free of charge. go to http://software. /dev. it should not be placed within a volume group that includes volatile data. use these guidelines to organize your file system: • /.com HP-UX Patch Management 7 . normally used to hold the login or home directory for each user.
For example. • Hardware Modifications Time will limit the extent of the hardware changes you can make during a system outage. while media works best for single systems at a time. see the HP Software Depot (http://software. For example: • File System Layout If your recovery method requires you to recreate the root volume group. Have a Wish List When you are forced to perform a system recovery. but sometimes you have no other options. use performance tools such as HPs GlancePlus.hp. 8 Planning for Recovery . you may want to use the opportunity to make some system changes that you can't make at any other time. use the opportunity to change the number and size of logical volumes. can you identify the person currently using the media that you need? — Do you have an index that lists which systems require a given set of media? (Remember to account for systems and peripherals that require a specific patch level!) • Network Depots: Are your installation media too slow to quickly recover your critical systems quickly? A network depot has faster performance. Do you need to reinstall multiple systems? Network depots let multiple systems share installation information. For more information. • Kernel Tuning Consider tuning any kernel parameters that you can alter only by rebooting the system. • Ignite-UX: Can you use Ignite-UX to reinstall? Ignite-UX lets you use multiple network depots and archives of system "golden" images together as a part of a single installation.com) and HP OpenView (http://openview. you can accomplish some performance optimizations—such as adding another SCSI controller or replacing an older root disk with a larger. faster model—at a relatively small incremental cost. Keep a "wish list" of desired changes so you can take advantage of a failure. HPs GlancePlus can help identify opportunities for kernel tuning.Plan for Reinstallation Plan for Reinstallation Complete reinstallation of a system should not be your preferred method for system recovery. Consider these questions when creating a plan: • Your most critical systems: — Can you reinstall those systems right now? — How long would reinstallation take? • Media Library: — Where are the tapes and CDs required to rebuild the system? — If your media is kept in a central library.com/products/). you may want to adjust partitions if any filesystems such as /var are too small.hp. To identify performance bottlenecks caused by slow hardware.
others are available only if you have an HP support agreement. To sign up for additional services: a. c. HP-UX Patch Management 9 .com 2. Follow the screen instructions. 3. Click on the register now! link. • HP patch bundles from Support Plus media or Software Depot (page 15) • Custom selection from the ITRC (page 18) • The ITRC Patch Fulfillment Server (FFS) (page 25) HP's ITRC is a web-based support environment. HP provides proactive patch analysis in which HP monitors and selects the correct patches for your systems. To sign up to use the ITRC: 1. Some services are available at no cost. Click on the my profile link. Click on the link a support agreement to your user id link. Please consult your local HP sales representative for more information about additional services.hp. Go to the ITRC web site at: http://itrc.CHAPTER 3 Acquiring Patches These are the primary sources for acquiring patches: • The patch database from the ITRC (ITRC) (page 10). b. (Optional) For those with the higher levels of system support.
10 Acquiring Patches . 6. 5.hp. Click on the individual patches link. The log-in screen appears. 2. 3. Click on the hp-ux link. Enter your user name and password.The Patch Database The Patch Database Use the patch database as your primary mechanism for searching for and acquiring individual patches. 7. Go to the ITRC web site: http://itrc. The main ITRC page appears. Click on the log-in link. The patch database main page appears (Figure 1). To access the database: 1. This document discusses two ways of finding HP-UX patches from the search page: • Searching by keyword • Entering specific patch names Patch Database Main Screen FIGURE 1.com Click on the log in link. Click on the maintenance and support link. The patch database search page appears (Figure 2). 4.
Select an OS from the pop-up menu (for example. Expressions inside parentheses ( ) b.The Patch Database Searching for HP-UX Patches by Keywords To conduct a keyword search: FIGURE 2. 5. 4. 10. Select Search by Keyword from the pop-up menu. Series 700). — The precedence of boolean operators in a search are: a. NOT. OR — Expressions are processed from left to right. Select a search criteria: • all words • any word • exact phrase • boolean — Boolean search results are limited to 200 results. Patch Database HP-UX Search Screen (search by keyword) 1. HP-UX Patch Management 11 . AND c.20). — An all UPPERCASE or all lowercase search string yields a case-insensitive search. 2. 3. Select the hardware by clicking on a radio button (for example. — A mixed case search string yields a case-sensitive search. Enter one or more keywords in the text field. Expressions inside parentheses are evaluated following the same order of precedence.
" Listed are the patch name. Figure 3 shows the results of a keyword search on "LVM" and "mirrored. Click SEARCH. Each patch name is a clickable hyperlink to the patch text file. "The Patch Text File. which documents the patch.The Patch Database 6. Selected Patch List Automatically selected dependencies 12 Acquiring Patches .") FIGURE 3. and a one line description of each patch. size in bytes. (See Appendix C . Patch Search Results--The Candidate Patch List FIGURE 4.
HP-UX Patch Management 13 . 6. Searching by Patch IDs To search by patch ID from the patch database search screen (Figure 2): 1.The Patch Database To download a patch from the search results: 1. 10. Click on the DOWNLOAD button beside each listed patch to save it to your system. 4. 2. Click on the check box next to the patch to select it. A list of all your selected patches appears along with any dependent patches (Figure 4). Select the hardware by clicking on a radio button (for example. See also "Dependency Analysis and the Patch Database" on page 14. 3. Series 700). 3. Click SEARCH. Click Add to Selected Patch List when you have made all your selections. Enter one or more patch ID numbers in the text field. (You can also use the Select All or Deselect All buttons. 2. A list of all your selected patches appears along with any dependent patches (see "Dependency Analysis and the Patch Database" on page 14). Select an OS from the pop-up menu (for example. Click on the DOWNLOAD button beside each listed patch to save it to your system.20). Select Search by Patch IDs from the pop-up menu. 5.
(This is because a patch may support more than one architecture and HP-UX release. Patch Description (PHSS_21980) 14 Acquiring Patches . This automatic dependency analysis does not occur when you search for a single patch. the patch database automatically analyzes their dependencies and lists any other patch that you require. Select the dependencies link. (Previously.) To find out about dependencies for an individual patch: 1.) This analysis takes superseding and recalled patches into account. 2. Display the patch description (Figure 5). FIGURE 5.The Patch Database Dependency Analysis and the Patch Database When you select a group of patches. you had to manually check each patch text file for dependency information.
For more information on Support Plus see "Support Plus Media" on page 15 and: http://www.software. which support both workstations and servers. reliability. (Although you can download the software for free.com/SUPPORT_PLUS • Additional Core Enhancements (ACE) An ACE bundle is a collection of enhancements to the HP-UX Operating System.com/ACE • Hardware Enablement (HWE) for 11. HP unified the ACE and HWE bundles to form the HWEnable11i bundle.com) is an online store that provides you with instant access to HP software for free trial or purchase.HP Patch Bundles HP Patch Bundles HP provides pre-packaged bundles of patches designed to be installed as a unit. or functionality. • Product Updates Some HP-UX products release a new version rather than a patch.software. The contents of each Support Plus release is freely available from Software Depot. See: http://www. This patch software enables new hardware and fixes known defects. Each ACE release extends HPUX to support new hardware and software features for HP workstations. For more information.hp. These can be downloaded from Software Depot. Some products available at this time include Ignite-UX and Software Distributor.hp. you may have to register with Software Depot first. Support Plus Media HP-UX Support Plus CDs deliver diagnostics and HP-UX system patches to you on a quarterly basis.software. see: http://www. As an added benefit. Obtaining Patch Bundles from Software Depot The HP Software Depot (http://www. Y2K defects or support for the European currency). but physical media is only available to customers with an HP-UX Software Support contract.hp. You can obtain HP patch bundles from the HP Software Depot on the web or (if included in your support contract) from the quarterly Support Plus media. special needs dictate the creation of a unique patch bundle (for example. These patch products are generally available at no charge and are found in the enhancement releases area of Software Depot. The support contract restrictions related to the actual media do not apply to electronic access. ACE software also corrects any critical or serious defects discovered since the original system release.) • Support Plus Bundles The patch bundles and diagnostic utilities of the Support Plus CDs are also provided for free download from Software Depot. Software Depot provides a number of patch products.com/products/HWE • Unified ACE/Hardware Extensions (HWE) For HP-UX 11i.hp. • Specialty Patch Bundles Occasionally. the bundles are available within Software Depot earlier than on media. HP-UX Patch Management 15 .00 HWE bundles enable new hardware or enhance OS performance.software. These bundles are subjected to stringent levels of testing to assure a high level of reliability and are periodically updated.
Networking driver products). — Gold Applications patch bundle. including hardware enablement and critical patches. EMS Kernel Resource Monitor. • Quality Pack (QPK) bundle for workstations.) General Release (GR) bundle: Bring all Core OS software to current patch level without custom XSWGR1100 patch selection Install critical patches or enable new add-on hardware Prepare your server to use new iCOD functionality Support Plus Patch Bundles for 11i: Hardware/Critical (HWCR) bundle: XSWHWCR1100 iCOD Client Product (from the OnlineDiag depot.g. HP application groups. Use this table to determine which bundle you need to install. which contains defect fixes for the Operating Environment applications.HP Patch Bundles Requesting Support Plus CD-ROMs HP notifies these customers when each Support Plus release becomes available. including current patches for all Core Operating System (OS) software. Support Plus Patch Bundles for 11. ODE (off-line diagnostics). If you want to: Update or install all the latest diagnostic tools. The notification letter includes a request form for physical media. EMS Kernel Resource Monitor. including all recommended. stable. GR and QPK bundles) and after installation of applications (e. and the Instant Capacity on Demand (iCOD) client product. These patches may match or supersede patches found in other HP-UX patch bundles. Predictive Support. • General Release (GR) patches. including Support Tool Manager (STM) for online diagnostics. including hardware monitors You should install: Diagnostic bundle: OnlineDiag Updated: Quarterly Install selected defect-fix patches Quality Pack (QPK) bundle: QPK1100 for the Core OS. You should install this bundle after other patch bundles (e. required for new systems and add-on hardware. 16 Acquiring Patches . • Hardware enablement patch bundle. Bundles in this depot are subjected to stringent levels of testing to assure a high level of reliability and are updated every six months. which contains defect fixes for core OS files. or (HP strongly recommends that you important third party applications include the latest Quality Pack as part of the OS environment for end-user systems. and the Instant Capacity on Demand (iCOD) client product. and key third-party application providers. and third-party defect-fix patches for selected Core OS and other products. • Hardware/critical (HWCR) patches. EMS hardware monitors. B9073AA bundle) As needed Quarterly Quarterly As needed • Diagnostics. HP products.00: • Diagnostics (OnlineDiag). which contains: — Gold Base patch bundle. The Gold Quality Pack depot contain those patches recommended by HP Support. and successful completion of tests by the HP Enterprise Patch Test Center.g. The GR bundles have recommended HP-UX patches with the highest confidence ratings based on patch distribution and age. including Support Tool Manager (STM) for online diagnostics. ODE (off-line diagnostics). • Gold Quality Pack depot. EMS hardware monitors.
HP Patch Bundles
(If you have used Support Plus on HP-UX 10.20 or 11.00: the Gold bundles replace the Quality Pack and GR bundles, combining the best features of both.) Use the following table to determine which bundle you need to install. If you want to: Update or install diagnostics and hardware monitors required for supported hardware You should install: Diagnostic bundle: OnlineDiag Updated: Quarterly
Install defect fixes for the core OS Gold Base bundle: or the network or graphics drivers GOLDBASE11i included on the OE Install defect fixes for HP-UX OE application software Enable new hardware or add-on hardware Prepare your server to use new iCOD functionality
Every six months
Gold Applications bundle: GOLDAPPS11i Every six months Hardware Enablement bundle: HWEnable11i iCOD Client Product (from the OnlineDiag depot, B9073AA bundle) Quarterly As needed
(The GOLDQPK11i depot contains the GOLDAPPS11i and GOLDBASE11i bundles.) Getting More Information For detailed information about Support Plus bundles and installation instructions, see the Support Plus User's Guide. You can obtain this guide from these sources: • The HP documentation web site: http://docs.hp.com/hpux/os/10.x/ • • The HP Instant Information CD The Support Plus CD in the file: /cdrom/USRGUIDE.PDF
HP-UX Patch Management
Custom Patch Manager
Custom Patch Manager
The HP ITRC offers custom solutions for getting patches or informing you about them: Custom Patch Manager (CPM) and Custom Patch Notification. Both services require the phone-in level of support agreement or above and may not be available in all geographic locations. (You can also use CPM on a pay-per-use basis. Consult the ITRC for details.)
About CPM
Custom Patch Manager (CPM) is a tool for selecting and downloading patches that are appropriate for a target system. • CPM patches and patch information are updated daily.This lets you update the collection script and perform an analysis on a regular schedule. For example, you can perform a monthly check for new critical patches, which could help identify a system risk before it is seen in production machines. Automatic dependency and conflict analysis, which reduces the need for lengthy review of the patch documentation.
Using CPM
To access CPM:
1. 2. 3.
Go to the ITRC web site (http://itrc.hp.com) and log in. Click on the maintenance/support link. This takes you to the maintenance and support page. Click on the customized patch bundles (custom patch manager) link. This takes you to the custom patch manager main page (Figure 6). (If your profile indicates you do not have the appropriate support agreement, a pay-per-use notice appears. Click on BUY NOW and fill out the payment form to continue.)
Step 1: Collect Configuration Informations
This step requires that you download the cpm_collect.sh script. This shell script collects the names and revisions of all the products installed on your system. HP recommends that you download the script on a regular basis to ensure you have the latest version of the script. To use the script: 1. Click on the Collect Configurations link on the main CPM page. This displays the system information collection page. 2. Follow the instructions in the "collect system configuration" section to download and execute the script on the system you want to patch (Figure 7). The script requires no special privileges and creates a data file using the name of the system followed by a .fs suffix. 3. Follow the instructions in the "upload results to IT resource center" section to return the data file to the ITRC via ftp: • • The ftp system to use is identified on the same ITRC page used to download the collection script. Use your ITRC user name and password to log in.
• Once connected, place the data file in the incoming subdirectory on the ftp server. (This directory is subject to space limitations.)
Acquiring Patches
Custom Patch Manager
CPM main page
Executing the cpm_collect.sh script
patchsvr> ./cpm_collect.sh Copyright (c) Hewlett-Packard 1995-1998. cpm_collect.sh version: A.03.04 This script will collect information about filesets and installed patches from your system in the file /tmp/patchsvr.fs for subsequent transfer to Hewlett-Packard. Do you wish to continue, [Y] or N ?y removing /tmp/patchsvr.fs Creating list of patches in /tmp/patchsvr.fs... Creating list of products and filesets in /tmp/patchsvr.fs... The file /tmp/patchsvr.fs has been created. All Rights Reserved.
HP-UX Patch Management
Custom Patch Manager
Step 2: Perform Patch Analysis
In this step, you analyze your system configuration information to determine what patches you need.
1. 2. 3. 4.
After you have uploaded the configuration information (Step 1), return to the custom patch manager main page. Click on the Perform Patch Analysis link. This displays a list of the current configuration files found within the incoming directory. Click on the radio button beside the appropriate configuration file in the list. (Optional) Use the search and filter options at the bottom of the page to reduce the number of patches displayed. Options include: • • • • • • • • Descriptive search Boolean search Critical patches only Fileset filtering Command patches Kernel patches Network patches Subsystem patches
Click on the tips for setting filters and searching link for more information about using these search options. Click on the DISPLAY CANDIDATE PATCHES button. This displays the candidate patch list (Figure 8). (The search and filter options appear above list. Using these options regenerates the display to show only the patches that match the filter or search criteria.)
Candidate Patch List
Acquiring Patches
— Always use the recommended patch unless the latest patch explicitly fixes a problem on your system. Click the ADD TO SELECTED PATCH LIST button to display the selected patch list (Figure 10). This list includes additional information on reboot requirements. You can also use the select all recommended or select all latest buttons at the bottom of the list. deselect the check box beside the patch and click the REMOVE button.) FIGURE 9.Custom Patch Manager The candidate patch list displays: • • • • A brief description of the patch The date it was installed on your system A link to a full description of an installed patch A link to the description of the corresponding HP-recommended patch. (Click the Add button to add the patch to your list and go to the selected patch list. 7. size. dependencies. This patch may have a lower patch rating than the recommended patch. • 6. — If the recommended column is blank. HP does not have a patch that is better than the patch (if any) that is already on your system. and patch age. Individual Patch Details (PHCO_21040) 8.) HP-UX Patch Management 21 . (To remove a patch from the list. (Optional) Click on the patch name to display detailed information on the patch (Figure 8). A link to the description of the corresponding latest patch. Select one or more patches from the candidate list by clicking on the check box next to the patch listing.
You can add or remove patches from your list if necessary. 2. This examines your list of patches for conflicts and displays the results (Figure 11). Click on the Analyze button below the selected patch list. Selected Patch List Step 3: Conflict Analysis In this step.) 1. CPM analyzes the selected patches for conflicts. Results of Conflict Analysis 22 Acquiring Patches . (This step is optional but highly recommended. (Optional) Follow the links from the conflicts display to get more information about how to resolve the conflict or to view other patches. See "Resolving Patch Conflicts" on page 30 for additional information. FIGURE 11.Custom Patch Manager FIGURE 10.
One of the scripts delivered in the shell archive is used to place all of these patches into a common depot for future installation. (CPM directs you to the appropriate server. •To use a current configuration file.sh script and uploading the results as described in "Custom Patch Manager" on page 18. go to the Custom Patch Manager main page. Preferences. Follow the instructions delivered with your script to run the script on your HP-UX system. Custom Patch Notification Custom Patch Notification is a an optional feature of Custom Patch Manager that provides you with weekly or monthly e-mail notification of newly posted patches that apply to your system. and view the full reports on the Custom Patch Notification main screen. Profiles specify the kinds of reports you want to receive. After you have selected all patches. or for different patch categories. Profiles. You may create up to 10 notification profiles Profile names may only contain alphanumeric characters (a-z. The selected patches are transferred individually to your system. The first character of name must be a letter. • • • • • • A profile may be based off either a Custom Patch Manager configuration file or a platform and OS revision. You receive an e-mail if the ITRC has posted new patches that apply to any of your profiles. and the underscore). Monthly reports are generated on the last day of each month. You can also specify what patch text fields are displayed when you view your on-line report.Custom Patch Manager Step 4: Package and Download Your Patches 1. simply select the radio button next to the configuration file on which you want your notifications to be based. These fields can be changed and the report re-loaded if you want to view the same report with different filters set. • You can add new configuration files by downloading the cpm_collect. by keywords. NOTE: Custom Patch Notification does not work with depot configuration files. Configuration Files. Weekly reports are sent out on Sundays. (This tool differs from the ITRC Support Information Digests by using configuration files and filters to narrow down the list of patches about which you are notified and by customizing the report contents. Reports. select the User Info link at the top of the screen. so changing it affects all e-mails you receive from the ITRC. such as filtering for critical patches. 2. HP-UX Patch Management 23 .) The script is a shell script that extract scripts and provides instructions for downloading your selected patches. Profiles are processed weekly or monthly. You may also select one or more filters for your notification list. • • • Reports are not cumulative from week to week or month to month. A-Z. • You can have only one ITRC e-mail address. log in to the ITRC. select the custom patch notification link from the custom patch manager main page (Figure 6 on page 19). The preference screen lets you verify the e-mail address to which your notifications are sent. click the Package button. You have the ability to specify which fields are displayed in the report by selecting the Patch Report Fields.) To set up Custom Patch Notification. To get more information about a new patch. 0-9. This notification includes applicable patch names and one-line descriptions. This generates a script and places it in the outgoing subdirectory for your account on one of the FTP servers. You can specify whether you want to receive your reports on a weekly or monthly basis. • To modify this address.
Use the uname(1) command on your system to determine what values to enter in these fields: To determine the platform. Selecting more than one category acts as a logical OR operation. type: uname -r (If you go from a configuration based profile to a profile based on platform and OS revision. Kernel.20) for a profile. type: uname -m To determine the OS revision. 9000/855) and OS revision (e. if you pick the Command and Kernel options. For example. you are notified of all Command patches or all Kernel patches that fit your profile. B. 24 Acquiring Patches . Selecting a category options and the Critical filter acts as a logical AND operator.g. Kernel and Command filters.. Subsystem). 9000/735. •Custom Patch Notification can filter patch notification lists based on these categories: — Critical: Lists all patches tagged as critical by the HP (independent of the actual patch categories listed below) — Command — Kernel — Network — Subsystem • • • • All HP-UX patches are included in one of the four patch categories (Command. Network. you need to click the Reset button to clear the configuration file table so only the platform and revision fields are filled in.10. CPM notifies you of all patches tagged as Critical AND all Command patches OR all Kernel patches that fit your profile.g. For example.Custom Patch Manager • You can also specify configuration by platform (e..) Filters. CPM does not let you deselect all categories. if you pick the Critical.
You do not need an ITRC account. Accessing the Fulfillment Server via ftp Figure 12 shows how to use the /usr/bin/ftp command on an HP-UX system to connect to the Americas/Asia/Pacific FFS system.hp. Disadvantages: • Does not work well for finding groups of related patches.external. Two FFS systems are currently available: • ftp://us-ffs. Note that the response supplied for the name prompt is anonymous.The Fulfillment Server The Fulfillment Server The fulfillment server (FFS) is the patch repository used by the patch database.com into your browser creates an anonymous ftp connection to the Americas/Asia/Pacific FFS system. direct ftp access has an advantage over web ftp access. The password used is the user's e-mail address. and you web browser must re-establish the connection each time you change directories or download files. You may have to make several attempts if the server is busy. (No web server is required. although you can also use FFS via the web. • Disadvantage: FFS limits the total number of simultaneous ftp connections. Web Access to FFS You can also access the FFS from your web browser. HP-UX Patch Management 25 . For example.) • Access is anonymous.com (Americas and Asia/Pacific) • ftp://europe-ffs. Because the FFS server limits the total number of simultaneous ftp connections.external. Simply enter an ftp address as you would a URL (Figure 13). You can perform multiple downloads without having to re-establish a connection each time. the FFS offers these advantages • You can access patches from any system that supports the ftp command and has direct access to the Internet.hp.external. • Works well for finding and downloading a known patch.com (Europe) HP recommends that you use the other techniques discussed in this chapter as your primary patch acquisition method. However. entering ftp://us-ffs. • The FFS server limits the total number of simultaneous ftp connections.hp. • Advantage: you can browse the FFS directories graphically. You can use ftp to directly access all patches on the FFS.
Remote system type is UNIX. w/CNS fixes (277) Wed Jun 24 18:02:04 PDT 1998) ready.com. send email to: 220220support_feedback@us-ffs. Name (us-ffs. 220220-If you have questions. and other platforms. Password:username@hp. Establishing an anonymous FTP session patchsvr(103)-> ftp us-ffs.4. 220220-Log in as user "anonymous" (using your e-mail address as your password) 220-to retrieve available patches for HP-UX. Using binary mode to transfer files.external.com 230 Guest login ok.hp.external. access restrictions apply.The Fulfillment Server FIGURE 12.com Connected to hpcc933. log in with your 220-HP ESC User ID and password to deposit or retrieve your files.external.com 220220 hpcc933 FTP server (Version wu-2. MPE/iX. send your complete e-mail address as password.external.com:username): anonymous 331 Guest login ok. 220220-If you are a user of other HP ESC services.hp. 220220-Welcome to the HP Electronic Support Center ftp server 220------------------------------------------------------220220-You are user 0.hp. HP ASL. Connecting to the Fulfillment Server via Netscape 26 Acquiring Patches . ftp> FIGURE 13. and there is a limit of 200 simultaneous accesses.hp.
3. The text file contains the patch location within the FFS hierarchy as the Path Name field. Patches common to both architectures are found under s700_800.. • /firmware_patches/hp (Firmware patches for HP Hardware) This directory contains patches that supply firmware updates to HP hardware. For example." on page 132 for more information on the text file. 2. When files of this type are transferred through other systems such as personal computers they may be treated as text and undergo a translation step. graphics cards. "Patch Text File Fields. Subdirectories exist for firmware specifically for CPUs. for Netscape. including: — hp-ux_obs_patch_list. Unpack the shar file by typing sh filename HP-UX Patch Management 27 . — hp-ux_patch_matrix. Copy to Folder. but is encoded to contain only 7-bit characters. in which patch_name is the file you wish to download.20 are found in the /hp-ux_patches/s700/10. Fibre Channel.The Fulfillment Server The FFS Directories These are some of the more useful FFS directories for HP-UX patching: • /hp-ux_patches/ARCHITECTURE/OS_RELEASE/ (HP-UX patches) All active HP-UX patches are grouped by architecture (s700.) 2. patches for Series 700 workstations on HP-UX 10.. Right-click on the patch link and select the appropriate save option from the pop-up menu (Save Link As. Downloading the patch • To download by ftp: 1. which contains a full list of every patch that has been superseded with the name of the active superseding patch. and s700_800) and the version of HP-UX supported (10. for Internet Explorer). • /superseded_patches/ (Patches that have been superseded by newer patches) This directory contains patches that have been replaced by newer patches. which contains the checksum for the . s800. (Use mget for downloading multiple files.. (Optional) Enter bi to specify a binary transfer.depot file of all HP-UX patches. which lists all patches that address known security issues for each release. Patch directories contain the full shar(1) archive and the patch text file.. but provides useful data files.X). This downloads the shar file of the patch to your system or displays a dialog to select a location to which to download. • /export/patches (data files) This directory does not deliver any patches. Use the get patch_name command to download specific files.) • To download by your web browser: 1. Use them only if you must revert to an earlier version of a patch to resolve a specific problem.X. 11. Click on the file you want to download.X subdirectory. (The shar archive may deliver 8-bit binary data. — hp-ux_patch_sums. and I/O cards. See Appendix .
) 2 3 R In the interest of timeliness.Patch Recommendation Ratings Patch Recommendation Ratings The "best" of the currently available patches covers a broad spectrum. Patch has been installed in a certain number of customer environments with no problems reported. HP releases a patch after it meets HP's minimum patch quality standards. only defer installing the patch if the problem is not critical or in the case that you can not tolerate any risk to your system. re-check it after one of the quarterly dates below to determine if it has passed further testing and the status has changed. the lower the risk of side-effects and the more suitable the patch is for mission critical environments. Also. HP recommends that you defer fixing the problem until more is known about the risk of the patch. The patches displayed in the candidate patch list (Figure 3 on page 12) are the best available patches. The higher the rating. 28 Acquiring Patches .and performance-tested by HP in simulated customer missioncritical environments using common application stacks. If you defer installing a patch because it is "Not yet HP Recommended". No unwanted side effects were discovered. February 1. If the patch has a rating of 1. and November 1. patches undergo testing both in customer environments and within HP. The HP Rating of a qualifying patch is upgraded to 3 on or shortly after. HP has verified that the patch will install and de-install in its target environments. May 1. It is no longer recommended by HP. Subsequently. Table 1: HP Rating HP rating Description 1 Functional testing by HP to verify that a patch fixes the problem that it purports to fix. August 1. Read the patch description to determine why it was recalled. Patch is known to introduce another problem and has been recalled. Patches are assigned a rating of 1 upon initial release. The Rating of a patch may be updated from 1 to 2 on a daily basis. (Not every recalled patch causes problems for every customer. Patches undergo testing for promotion to an HP Rating of 3 on a quarterly basis. HP rates patches along a three-point scale as shown below. Patch has been stress. The patch's HP Rating is then updated accordingly as HP's confidence in the patch increases. Not all patches undergo this testing. These are the most recently released patches having the highest HP Rating. Having said that.
Patches are assigned an HP Rating of 1.About Patch Notes About Patch Notes Patches may include descriptive notes to help you determine the status or risk of a patch. As a matter of course. or 3 based on how many quality standards they meet. Whenever the patch database suggests a patch that is not yet recommended by HP. Other notes include: • Not yet HP recommended All patches adhere to certain HP quality standards. the higher the rating becomes. However. These patches may fix the problem. If you are not facing a critical problem. patches are assigned an HP Rating of 1 and are labeled "Not yet HP Recommended". HP-UX Patch Management 29 . Click on the one line patch description to view the patch details to determine why it was recalled. it purposely takes time to meet the higher standards. and any impact to your environment. • Recalled A patch may be labeled as recalled when it is known to introduce another problem. "Fixes critical problem" or "Reboot required after installation"). These are displayed in the Notes section of patch lists. Patches with ratings of 2 or 3 are denoted by the term "HP Recommended" in the Notes field. • Patch not available A patch might be unavailable if. Most notes are self-explanatory (such as. but also may contain some element of risk. Upon their initial release. HP recommends waiting for a patch to gain a higher HP Rating. The patch database recommends a replacement patch when you search by patch ID and find a recalled patch. for instance. it has a dependency that requires the installation of a product that needs to be purchased separately. you must make an informed assessment of these trade-offs based on your own situation. As patches advance on the patch confidence scale. not every recalled patch causes problems for every customer. 2. These patches are available to give you the option of obtaining a fix sooner if you can tolerate some risk to fix a critical problem.
Resolving Patch Conflicts Resolving Patch Conflicts These are the possible conflicts that can come up during an analysis and how to resolve them: • Behavioral conflict: A behavioral conflicts generally means a selected patch should not be installed with a patch installed on your system. 2. Click on the patch name to view its details. Analyze for conflicts again to verify that the conflict is resolved. remove the conflicting patch from your selected patch list and perform another analysis. Add the recommended alternate patch. This is a rare occurrence that when encountered can lead to unexpected behavior when a patch is effectively partially superseded. • Recalled A Recalled patch has been removed from distribution. For example. but it will generally imply special handling. usually explained in the Warning/Description field or the final patch listed under Predecessor patches. Review its description and any superseded patches listed. view the details for each patch and decide between them. If you don't want the patch. • Dependency Conflict: A selected patch or a patch already on your system requires another patch to be installed with it. Analyze for conflicts again to verify that the conflict is resolved. 30 Acquiring Patches . 4. A structural conflict may not exclude the selected patch. To find an alternate patch: 1. View the details for each patch to decide which you want. add the patch to your selected patch list. 3. you may select critical patches that have dependencies on noncritical patches. If you choose to leave the existing patch installed. de-select and remove it from your selected patch list. If appropriate. you should verify the revisions and install one or both of the patches as needed. Generally. Click on the dependent patch. If two selected patches conflict. Continue checking the ITRC to check for updates. 2. You must choose between the new patch and the existing one. it might still be in development. 3. 5. This kind of conflict may be common. To resolve dependency conflicts with selected patches: 1. Look for a recommended alternate patch. • Structural Conflict: A structural conflict indicates that both patches will replace the same software file on your system. If you do not find information about an alternate patch. Check the revision numbers descriptions When two patches have structural conflicts. you should select the patch with the highest rating unless a newer patch fixes a specific problem.
Adding the overhead of patch management to system administrators limits the number of systems that each can control. CD-ROM. HP-UX Patch Management 31 .CHAPTER 4 Depot Management Depot management is a method used to simplify systems management by defining a common reservoir of software to be shared by a group of systems. the work of defining and testing a new configuration of software can be centrally managed. Benefits of Creating Depots There are many reasons to create customized depots. • Streamlined Installation When software is acquired as multiple depots and/or media. • Remote Administration It may be that the system is in a remote location. By defining a depot. and are a powerful tool for managing software. installations can take place without the need to mount media. • Separation of Patch Management From System Management Patch management requires a number of unique skills and is an ongoing task. combining all software into a single depot allows for a single installation session to load everything. Custom Depots A depot is a software container present on disk. a centralized team can define and support a standardized configuration to be used by many administrators. For more information on registering depots. While the mechanics of system administration remain. By creating registered depots. or maybe it is just far enough away to be annoying. see "The swreg Command" on page 69. tape. or network that is used as a software source for the swinstall installation utility. the combined depot would result in a single reboot regardless of the number of patches installed. Custom depots can be constructed in a number of different ways. For patches that cause kernel rebuilds. It is not uncommon to want to administer a system without ever seeing it.
Patch Depots Patch selection.X depots identified by the value 0. The format is specifically designed to support software delivery on tape media but it can be stored on other types of media as well. and it is recommended for HP-UX 11. Also known as a network depot. and monitoring are some of the more difficult administrative tasks required for HP-UX systems.X depots marked by 1. It is possible to use depots of layout_version=0. Periodic depots are generated on a regular basis that will vary according to the needs of a user.8 depot.X Depots Beginning with HP-UX 11.X systems. Several different kinds of patch depots are valuable: Periodic Patch Depot A periodic patch depot is created to define the current recommended patch level.X vs.0. When the term depot is used in this document. While this format is not readily transferable like the tape depot.8 and 11. Several problems related to serving depots for HP-UX 10. A directory depot contains each packaged file. patching was significantly enhanced by extending the abilities of the SD-UX tools. Tape media is also a convenient method to allow a depot to be transferred over a network without using the swcopy command." on page 9). but it is also true that there is always the possibility that a system will encounter a problem requiring a new patch. Once created. data will be lost and the depot corrupted. The critical aspects of such a depot are that they have been tested on the target configuration. Both styles are common and while the basic function of each is identical there are advantages to each in certain situations. HP-UX 10. 32 Depot Management . as distinct files in a directory hierarchy. There are many arguments against changing such a depot after it has been released.depot file delivered within any patch shell archive from the Patch Database or Fulfillment Server (see Chapter 3. it is much better suited to parallel access. this type of depot is recommended when creating a depot to be accessed from remote systems. as well as infrastructure. analysis. it can be assumed that a directory depot is implied unless specified otherwise. or just in advance of any scheduled system downtime to take advantage of the opportunity.Patch Depots Types of Depots There are two types of depots: directory and tape. monthly to ensure a more timely inclusion of critical fixes. and no dependencies are missing.00 that you install patch PHCO_20078 (or current replacement) before creating the depots. with 10. A tape depot is a single data file that is accessed in a serial manner. If an HP-UX 11. It may be done quarterly to match the availability of the Support Plus media.0. production systems need only install with an matching operation to load the required patches. "Acquiring Patches.X depot is copied to an HP-UX 10. The best example of this is the .X from HP-UX 11. 11.X have been identified. The price of these new abilities was to introduce several new attributes to the objects. The layout_version attribute is used to differentiate between the old and new. Critical Fix Patch Depot When a periodic patch depot has been created.X system or layout_version=0. Creating dedicated patch depots is a great way to avoid duplicating this effort.8 on an HP-UX 11. it often represents a significant investment in testing and analysis.X system to provide software for use on HP-UX 10.
Patch Depots In these environments. For example. • Patch Bundles Patch bundles may be acquired from HP directly. alternate mechanisms may be used to define subsets of the full patch hub. it may be useful to create a depot that contains fixes to known problems in the current environment. For more information. see"The swinstall Command" on page 59 and the"The swcopy Command" on page 62. Depending on the severity or probability of a given failure. Creating Custom Patch Bundles by Dominguez & Scott in the Interworks 1998 proceedings or at http://www. For 11. Both a software file (specified with the -f option) and a session file (specified with the -C option) provide a mechanism to explicitly select a set of software.00 the user still has the responsibility of including all dependencies. as well as a starting point for the next version of the periodic depot. Session files provide the additional ability to specify options in addition to the software list. but numerous issues exist. swinstall -s /hub -x patch_match_target=true -x patch_filter=*. This can be particularly useful when working with bundle wrappers.c=P2000_Q1 selects all of the patches in the /hub depot that include the category tag P2000_Q1. If the risks are understood and are acceptable. The swmodify command is used to create new category tags. • Software/Session Files Software and session files can be used to select patches for installation (with swinstall) or to copy (with swcopy) from a patch hub. This depot can be used to update any system that encounters a known failure. This problem was corrected with patch PHC)_22526. HP-UX Patch Management 33 .org). or created using the Ignite-UX make_bundles command or externally available tools such as those available through the Interex Users Group (see the paper. it is not uncommon to desire a "kitchen sink" depot that contains every patch that may ever be needed. As with the periodic depots. The advantage of category tags over patch bundles or software/session files is that they may be used with the patch_filter and a matching operation to avoid the problems of explicit selection. it may be advisable to place a newer patch in both the periodic and the critical fix depot. It is recommended that a patch hub is unregistered or be given restricted access (see "Depot Access" on page 36). but provides the system administrator with a variety of ways to perform an incorrect operation that could leave a system in an unknown state. Such a patch hub is no longer suitable for general use and the result of an matching operation does not produce a defined or necessarily tested environment. It may be used as a method to conserve disk space. Such a bundle can be explicitly selected for installation. See Chapter 6.list issue the command: swmodify -a category_tag=P2000_Q1 -f P2000_Q1. This responsibility is handled by the SD-UX tools in 11i. Patch Hubs While not recommended for general use. such as the lack of a working mechanism to delete them.00. To define the P2000_Q1 category used above.list @ /hub Category tags had some initial problems. The swmodify command can be used to add an arbitrary category tag to existing patches. after listing all selected patch filesets in the file P2000_Q1. or as a local resource to ensure local access to any needed patch.*. Providing direct access to a patch hub can be done. • Category Tags Introduced to patches in HP-UX 11.interex. "Patch Installation" for more on this topic. category tags are attributes that can be used to mark a patch. dependencies of the patches in the depot should also be included.
\* @ /depots/testdepot The swcopy command is described in more detail within the swcopy(1m) man page or in "The swcopy Command" on page 62. When multiple patch depots are combined. • Compression Depots are created in an uncompressed state by default. Disk space must be available. • Naming a depot One of the features of the interactive user interfaces is the ability to select from a list of available depots on a system. high availability storage solutions such as disk arrays or mirroring should be considered. If groups of remote systems are accessible only via a congested or expensive link. creating mirror depots may be a valuable option. The following example shows how a depot on the default tape drive could be copied as /depots/testdepot to the current system while ensuring that all files are compressed: swcopy -s /dev/rmt/0m -x compress_files=true \*. or to a tape depot via the swpackage command.Creating a Patch Depot Creating a Patch Depot Once the decision has been made to create a patch depot and the patches have been selected and acquired. systems. The more individuals. This may result in the depot containing patches and their replacements together. creating the right environment today can help support any changes the future may bring. Preparation Tasks There are a number of issues to consider before a depot is put into production. Both disk space and network bandwidth can be conserved by setting the swcopy option compress_files to true. For example. Even if you are the only person that will use the depots. /depots/order_db/Y2000Q1 might contain the periodic patch bundle for the first quarter of the year 2000 to be used on systems hosting the order entry database. it is automatically registered. the depot should be made inaccessible during the creation process. As this document will not address the creation of a patch. While an installation using such a depot should be successful. Copying Existing Depots All packaged software exists in a depot. 34 Depot Management . This can be done by setting the option register_new_depot to false during the initial swcopy session. each is simply copied in turn. it is time to create a depot to house them. and depots involved. • Depot Access When a depot is created using swcopy. A depot can be copied to a directory depot using the swcopy command. the superseded patches will never be used and are a waste of disk space. it can be assumed that an initial depot is always available. Both the performance of the server and the impact on others are to be addressed. and if the depot usage is expected to be high the performance of the disk devices and interface cards must be taken into account. • Disk Considerations Depot operations can involve a significant amount of disk activity. location within the network should be considered. It is particularly useful to specify a depot path that identifies the contents if several different depots and/or depot revisions are present. If the availability of the depot is critical. If the final form of the depot will require more than a single swcopy. the more time and energy should be devoted to preparation. • Network Considerations Not only should the performance of the networking interfaces be taken into account. Combining Patch Depots You may want to combine patch depots so that you can perform a single install and reboot for a given session.
cleanup will remove any superseded patches within the depot.00 Although the patch database and the SD-UX tools perform automatic dependency analysis. but it has been superseded by PHNE_19899. Search the patch database for any dependent patches. For example. In Figure 14. When given the -d option and the full path to a depot. HP-UX Patch Management 35 . Read the PHNE_17051 text file. searching for PHNE_17017 shows that the patch is recalled and is not available.Creating a Patch Depot Removing Superseded Patches For HP-UX 11. The supersession chains are each in a vertical column. two supersession chains are shown that have a mutual dependency. with the older patches on the bottom. the PHNE_17051 file lists a dependency on PHNE_17017. suppose that you need a critical fix found in patch PHNE_17051. For testdepot created above. 2. See "The cleanup Command" on page 72 for more information. you may occasionally have to perform the analysis manually. Example of Inter-Patch Dependencies PHNE_18972 PHNE_19899 Patch Dependency Supersession Chain PHNE_17662 PHNE_17051 PHNE_17017 For example. FIGURE 14. and you are prompted before the command removes them.00 systems. they are listed. This section describes how to analyze dependencies. Dependency Analysis for HP-UX 11. this would be done via: /usr/sbin/cleanup -d /depots/testdepot If any superseded patches are found. 1. For example. superseded patches can be removed from a depot via the cleanup utility (delivered by patch PHCO_19550 or current replacement). A patch dependency is indicated by a dashed arrow pointing from a patch to the patch it is dependent on.
com/. which you already selected. 3. a depot remains accessible on its own system without being visible to remote systems. the . Dependency Analysis for HP-UX 11i The 10. Access rights can be specified for individual products within a depot and given to individual users on specific systems. (This capability results from the requirement that every patch with a dependency enforces or records that dependency in its product specification file.hp. depot registration and access control lists. This means that the SD-UX commands for installing and copying patches automatically include patch dependencies.text file or the patch database) shows that PHNE_18972 has replaced PHNE_17051.00" above.) For example. the swacl command provides the ability to restrict access to a high level of granularity. This could be due to entitlements. When unregistered.Depot Access 3. 36 Depot Management . For patch depots. You must go through the dependency analysis as outlined above. geography. training. PHNE_17662 itself has been replaced by PHNE_19899. For this reason. You copy or install a patch from a depot that does not contain the dependent patches. Depot Access It may be desirable to restrict access to depots. no unresolved dependencies remain.20 and 11. The patch contains a manual_dependency tag.text file for PHNE_19899 shows a dependency on PHNE_18972. the cumulative nature of HPUX patches ensures that the replacement patches include the needed functionality. and you can install patches PHNE_18972 and PHNE_19899 onto the system. At this point. See "Enforced Patch Dependencies" on page 50 for more information. For a full description of swacl. suppose that you need a critical fix found in patch PHNE_17051. swinstall or swcopy detect the patch dependency on another patch and automatically include the dependent patch in the install or copy operation. this is usually sufficient for most needs. HP enabled "enforced dependency" functionality for the HP-UX 11i release. swcopy or swinstall would automatically copy or install PHNE_18972 and PHNE_19899 together. if all the patches in Figure 14 are in the same depot. Registration tasks are done using the swreg command (see "The swreg Command" on page 69). Chapter 3. Check the dependency information for any superseding patches. or the depot not being prepared for production. Depot Registration A registered depot is visible and accessible to remote systems. Even though you did not install the original patch (PHNE_17051). For example. Access Control Lists (swacls) If complex access control is required. consult the swacl(1m) man page or the SD-UX documentation available from http://docs. "Acquiring Patches" has more information about using the patch database and dependency analysis. even if you only selected one of them. The Supersedes field (in the patch . These are the possible scenarios for 11i patch analysis: 1. Two mechanisms exist to restrict access. The rights can be further divided by the type of access granted. The patch and all of its dependencies are in the depot from which you are installing or copying your patch. PHNE 18972 also has a dependency on PHNE_17662. 2. This tag indicates that the patch has one or more dependencies that cannot be resolved by SD-UX.00 process of manually analyzing patch dependencies is time-consuming and cumbersome. You then need to follow the analysis outlined in "Dependency Analysis for HP-UX 11. or example.
A Note on Change Management When working with multiple systems and system administrators. In a large environment it may be beneficial to create a formal change control process for critical systems. Computer systems are complex environments and system administrators are often driven by constant and critical interruptions. Some of the aspects of such a process include: HP-UX Patch Management 37 . It is assumed that prior to installation the following tasks have been completed: • A current system recovery image has been completed • Patches have been selected and acquired • The installation depot contains all dependencies System Preparation Even when the depot is ready. there is more to be done to prepare for any system modification. While the risks may be small. the costs can be huge.CHAPTER 5 Patch Installation This chapter describes a basic process for performing the installation of patches onto an HP-UX system. While not the only method available. software failures and operator error are not hindered in their destructive ability. If there is any question regarding the stability or reproducibility of the user data it must be resolved before proceeding. While disk arrays and mirroring provide terrific protection from hardware failures. it provides a general checklist of tasks that can be used as a starting point for a local process. it can be easy for confusion to lead to mistakes and/or complicate analysis of system failures. Back-ups Back-ups! While this document only addresses issues involving system software. this is not meant to infer that data is not important.
This image can be used to return to the uncommitted state. most documentation has recommended that the system be in run-level (init) 2 or higher. • Centralized Change Database By keeping change records on a central system. For example. The committed patches cannot be removed. senior administrators and management can provide guidance and ensure that business needs are not controlled by technical decisions. Remember that the risk is not only to the failure of an application. and the current patch level becomes a low-water mark. such as a Support Plus patch bundle. For this reason. and no new processing should be started. the individual responsible for executing the change can quickly be identified. system files. Patch Committal Prior to Depot Installation When installing a large number of patches. to commit all patches on your system: swmodify -x patch_commit=true \* Before you commit patches. If this is the case. it becomes necessary to return to the initial state by removing the new patches. These are multi-user states that are usually associated with active systems. HP strongly recommends that you create a recovery image. System Activity The Software Distributor tools rely on the Distributed Computing Environment (DCE) and networking support for even the most basic functions. While less valuable in smaller operations. but to the system being left in a partially installed and corrupted state. Scripts may kill and restart daemons. This can result in the removal of a patch that fulfills a dependency. An attempt to remove all active patches can only delete those that are newly delivered. However. The installation of large numbers of patches might create unwanted side effects on your system. Patches should also never be committed without an immediate need such as reclaim- 38 Patch Installation . The recommended method for performing a system-wide patch committal is to use the SD-UX swmodify command. a growing data center should consider implementing a change control process before it is needed. This causes the initial patched state to become the minimum system environment. One method that can be used to avoid these issues is to perform a system-wide commitment of all patches prior to the installation of the new set. • Change Review and Approval By requiring a period of review and authorization. This is not meant to indicate that updates should take place on active systems from beginning to end. However if you don't perform a committal before the installation of the new patches. Experience and recovery planning should be your guide. By requiring a formal handoff to any new owners. during the installation process. The system will be between supportable configurations.System Preparation • Clear Ownership of each Change The submitter of a change request becomes the initial owner of a task. The database can be constructed to provide access to the experience of other administrators as well as visibility of upcoming changes to system users. they are not lost when a system failure is encountered. Both the initial state prior to the installation and the final state upon completion should be supported and stable environments. Commands and libraries may not match the currently running kernel. and commands are gradually changed. you may inadvertently remove patches that were installed on the system before the bundle installation. it is not uncommon for some of the patches to already be present or superseded on the target system. Applications that are not critical should be halted. libraries.
) Reload the ancestor patches.KERN2-RUN OS-Core.SPT2-DVRSCSI-Passthru. For example.CORE2-KRN.00.2) installed with all patches committed and that you need to remove PHKL_22759.00" on page 35 or "Dependency Analysis for HP-UX 11i" on page 36 for more information. 3.CORE2-KRN OS-Core. "Planning for Recovery". The depot should include all patches desired for the final system.) Create a recovery depot that contains the original products as well as all required patches.There are also disadvantages. Removing any patch might cause another patch to lose a required dependency. The remaining patches are those delivered in the XSWGR1100 bundle.52. ProgSupport. such as an Ignite-UX recovery tape or network image.fr=B. # # Target: phsvr703:/ # # PHKL_22759 PHKL_22759.. this would mean copying PHKL_21989 into the recovery depot and removing PHKL_22759.v=HP From the swlist output. 4. Therefore.11.fr=B.00. Perform a dependency analysis.System Preparation ing disk space or preparing for the installation of a new bundle. can fix the problem. See "Committed Patch Removal" and "Patch Commitment" on page 49 for more information.C-INC.00.SPT2-DVR.11.11. You must re-install the patched products to provide the older versions of files or manage your patch depots in such a way that you can re-install a committed patch's ancestor patches.fr=B. you determine that you need to reload the OS-Core. (See "Dependency Analysis for HP-UX 11. and SCSIPassthru products. PHKL_21989..v=HP PHKL_22759.00.C-INC ProgSupport. # Contacting target "phsvr703". All are confirmed to be in the depot.KERN2-RUN... suppose that a system has the XSWGR1100 bundle (revision 11.00. To remove the committed patch and reinstall PHKL_21989: 1. you must perform an analysis to ensure that the final set of patches will function correctly. 5. To ensure that you can return your system to its current state. using the swinstall preview mode: swinstall -p -s /var/tmp/REBUILD_DEPOT -x autoreboot=true \ -x autoselect_patches=true -x reinstall=true \ -x reinstall_files=true OS-Core ProgSupport SCSI-Passthru HP-UX Patch Management 39 . Committed Patch Removal The primary disadvantage of system-wide patch committal is that you cannot as easily roll back the committed patches. In the example.11.fr=B. staying as close as possible to the patches already on the system. Use the swlist command to determine all ancestors of patches to be changed (because you need to reload all of the filesets modified by the patch): swlist -l fileset -a ancestor PHKL_22759 # Initializing.v=HP PHKL_22759. Failure to perform this analysis for all patches to be removed may cause unpredictable results.v=HP PHKL_22759. No newer patches are acceptable. create a recovery image. but an older patch. The best way to do this is to manage your patch depots in such a way that you can re-install a committed patch's ancestor patches. Selected re-installation and IPD modification can be a complex and risky operation. 2. (See Chapter 2.
or the command "/etc/sdsadmin" indicates that there is a multiple disk software disk striping (SDS) array on the system (or cluster). Theses messages tell you that you need to include the LVM product. use the swinstall program's preview mode (include a -p in the command line) to analyze the install before trying to perform it.00" has previous analysis errors. Preview the installation again.CORE-KRN" gave a global error return (exit code "11").11. (If necessary) check the log files if errors occur. this time with the addition of the LVM product: swinstall -p -s /var/tmp/REBUILD_DEPOT -x autoreboot=true \ -x autoselect_patches=true -x reinstall=true \ -x reinstall_files=true OS-Core ProgSupport SCSI-Passthru LVM Run the same command without the -p option to perform the actual installation. TIP: Reloading of products and patches may cause SD-UX to issue a disk space analysis (DSA) error.CORE2-KRN. Because the disk space used by the reloaded products and patches merely replaces existing disk space.00" for fileset "OS-Core. the actual usage of /var/adm/sw may increase and cause swinstall to fail. 40 Patch Installation .LVM-KRN and LVM.11. Use this option with extreme caution.r=B. but this requires that you change the default behavior of additional SD-UX options including autoselect_dependencies and enforce_dependencies. Unless you are installing patches into a committed state. For the example. You can replace individual filesets to remove committed patches and restore ancestors level. but the actual increase never exceeds of 10 Mbytes. The corequisite "OS. * The software "OS-Core. ERROR: The "checkinstall" script for "OS-Core. This is because there is either an "/etc/lvmtab" file which contains lvm configuration information on the system. Whenever possible. Installing the example products causes swinstall to expect the size of /usr to increase by more than 100 Mbytes. In either case. which turns off automatic dependency checking and increases the risk of error. 7.System Preparation 6. the following error is listed: ERROR: The filesets LVM.r=B.CORE-KRN.r=B.Core. most of which is transient use only.00" cannot be successfully resolved. TIP: Whenever possible. TIP: Patches may include checkinstall scripts that do not support dependency checking and other patch management features. use a test system to verify impacts and changes before you change any production environment systems. data will be lost without LVM.LVM-RUN must be selected in order to ensure that all disks will be accessible after the new kernel is put into place. You can avoid this error setting the enforce_dsa option to false. TIP: SD-UX affords you a greater level of safety and error checking when you work at the product level.11.CORE-KRN. 8.
• SD-UX had no way to determine whether some patches in a depot were superseded by other patches. patches were generally selected and installed using the match_target option of swinstall. the autoreboot option instructs swinstall to reboot the system whenever it is required. the fact that the system is in an unknown state until the installation process completes is discussed.c=patch @ /MyDepot | grep true Timing of the Reboot In "System Preparation" on page 37. The goal is to have all systems at a common level with the least amount of overhead. This also made it impossible to install both the product and its patch(es) in a single step. Not only is a reboot often required. the interactive versions of the swinstall command will display a dialog that announces the required reboot. Patches that were superseded had to be manually removed from a depot. While solutions for the future are under investigation.*. This was an improvement over manual selection of patches but there were several problems: • The match_target option applied to both patches and non-patch software in the same depot and there was no way to ensure that the patches and non-patch software would be installed in the correct order. Installation The previous work outlined in this document was concentrated in creating the depots and with the preparation complete the installation should be simple and quick. but it should also not be unecessarily delayed. It should now be made clear that this ambiguous condition exists until any required system reboot and configuration steps are completed. the only method currently available to restart an HP-UX kernel is to shut down and restart the system. This complicated the process of software updates and required that patches be kept in a separate depot. If specified. The CLI will not allow an installation that will require a system reboot to begin unless an override option (-x autoreboot=true) is specified. This becomes an issue when the swinstall command line interface (CLI) is used. Using the SD-UX Matching Operations In the HP-UX 10. In addition. There was no way to filter them according to their type or level of severity. Unless a special need exists. There are complex methods of patch installation.Planning for System Reboot Planning for System Reboot The core of the HP-UX operating system is known as the kernel. but how can you tell? A flag is recorded both within the patch documentation as well as a fileset attribute within the patch itself. • All patches in the source depot that corresponded to software on the target system were selected. Most kernel (PHKL) and many networking (PHNE) patches require that the kernel be rebuilt and restarted. While useful for automated and unattended installations. Any filesets with this attribute set to true will reboot the system if loaded. avoid using these complex methods unnecessarily. When is a Reboot Needed? Each patch "knows" if it will require a system reboot to install on a system. A depot can be checked for patches requiring a reboot by using the swlist command to display the is_reboot attribute of the patch filesets. The patches in a local depot (/MyDepot) can be checked with the following: swlist -d -l fileset -a is_reboot *. it does not allow any time or warning before the system is halted. it is certain that at times users and applications will remain active during an install and need to be prepared before a reboot can occur. HP-UX Patch Management 41 . and some are mentioned in this document.X releases. Despite this and the cautions regarding system activity.
always check for the manual_dependencies tag which indicates that although the patch has one or more dependencies. This simplifies the process and protects the system from careless activity. the match_target option has been modified so that it applies only to non-patch software. they will be selected and installed with the software. The following command installs patches from a depot which correspond to currently installed software products: swinstall -s /mydepot -x patch_match_target=true -x autoreboot=true Finally. Most patches contain dependency information within their PSF in the form of corequisites or prerequisites. The benefit to the user is that a separate swinstall session is not required to install patches to a product. it does not select the dependencies for those patches. they will not be handled by SD-UX. patch_filter automatically selects the patches which contain myTag as a category tag in addition to their dependencies.*") The autoselect_patches option is used when installing software. 42 Patch Installation . the patch_match_target option can be used to select those patches which correspond to any product installed on the system. If you want to install from a depot of patches. Note that in HP-UX 11. you have additional control over patches selected when using either autoselect_patches or patch_match_target through the use of the patch_filter option. the match_target option was changed to select only non-patch software.Installation With HP-UX 11. For example. This is most often used to install the proper set of patches from a patch bundle. Three new selection options were added to improve management of patches: -x autoselect_patches=true|false -x patch_match_target=true|false -x patch_filter=<selection> (default=true) (default=false) (default="*. In other words. any subset generated through a patch_filter operation in 11.00 must not have external dependencies. It must be emphasized that as with depots. Non-patch software can be identified through the is_patch attribute described in "Patch Related Object Attributes" on page 56. See "Enforced Patch Dependencies" on page 50 for detailed information on the manual_dependencies tag. you must go through and do a manual dependency analysis.c=myTag" The patch_filter option can also be applied in conjunction with the autoselect_patches option to control which patches are selected when software is initially installed. This functionality has been enabled in 11i through the use of requisite tags. For 11i. When installing from a depot.*. there are exceptions to this enforcement. the command: swinstall -s /mydepot MYPRODUCT by default also selects and installs any patches applying to MYPRODUCT that also exist in the source depot. it only selects those patches which have that tag so if the dependency does not contain it. For example. to install only patches with a category_tag of myTag that apply to a system: swinstall -s /mydepot -x patch_match_target=true -x autoreboot=true \ -x patch_filter="*. Each patch contains tags (the category_tag attribute) which characterize the patch. However.X. they can be applied during the initial installation or update of the software.00. If patches that apply to the software selected (by a swinstall or swcopy command) are present in the source depot.00" on page 35 for a detailed explanation of analysis. when patch_filter is used to select patches which contain the myTag category tag. See "Dependency Analysis for HP-UX 11.
the swinstall option -x patch_save_files=false may be used.) Step 1: Mount the CD 1. (From the GUI. Open a terminal window and become root on your system. 4. identify the drive device file: ioscan -fnC disk This command lists all recognized CD drives and their associated device files. they are not all at the top level of the CD. HP-UX Patch Management 43 .hp. and the swmodify command allows the patch commitment to be managed down to the fileset level with the patch_commit=true option. You can now access the CD via the mount-point directory. Step 2: Check for Last-Minute Information Support Plus often contains last-minute information.hp. switch it on. enter: mkdir /cdrom 5. If it is desired that the patches be installed directly into a committed state. then select the appropriate patching tools. (Note that the Support Plus CD has depots contained in subdirectories. For complete information on Support Plus. see "HP Patch Bundles" on page 31 and the Support Plus User's Guide. The cleanup command is discussed in more detail in "The cleanup Command" on page 72. Put the appropriate Support Plus CD into the drive. the cleanup utility (delivered via patch PHCO_22044 or current replacement) provides a simple interface consistent with the version provided on HP-UX 10. Before proceeding. 2. The file name will be something similar to /dev/dsk/c1t2d0. use the name you found using ioscan in Step 5 above.) There are two different methods that may be used to commit patches after they have been installed. If the CD drive is external. For example. to define /cdrom as the mount point. or after the fact. 3.00.com. available on the Support Plus CD and at http://docs. deselect the Actions-->Save files replaced by patch for later rollback.com/ Select the Maintenance and Support page. 7. Mount the CD drive to the mount-point directory: mount -r /dev/dsk/c1t2d0 /cdrom If the CD drive's device-file name is not c1t2d0. There are several important sources of information: • Check the HP IT Resource Center for information about recommended patches: http://itrc. Installing Support Plus Patch Bundles Follow this procedure to install patch bundles from the Support Plus CD. define a new directory as the mount point for the CD drive.Installing Support Plus Patch Bundles Installing to a Committed Patch State Patch commitment may take place during patch installation. If necessary. For example: ls /cdrom 6. For 11.X releases. If necessary. HP strongly recommends that you read the documentation for each bundle or patch you wish to load. Wait for the busy light to stop blinking.
readme (for 11i) • Each patch has an accompanying text file in the /cdrom/TEXT_FILES directory. proceed to "Step 5: Install the Selected Bundles" on page 45.x depots from HP-UX 10.hp. This file contains additional installation instructions. You can print or view these files directly from the CD.adobe. Step 3 (Optional): Set Up Sharing for Remote Systems To enable direct access from one or two other systems. or if you cannot dedicate the CD drive to the Support Plus CD. you must register a depot on the Support Plus CD using the swreg command. Register the depot: swreg -l depot /cdrom/HWEnable11i 2. assuming the Support Plus CD is mounted to /cdrom: 1. and a listing of disk space usage. The hyperlinks from the HTML bundle readme files to the patch text files will work as long as the HTML files reside in the same directory as the TEXT_FILES subdirectory.20 systems. These files contain hyperlinks to the patch text files.readme. (Patch text files are also included with individual patches that you retrieve from HP. changes since the last release. notes about problems in current and previous releases. If you mounted the CD on the system that is the target for the patch or diagnostic installation. to register the HWEnable11i depot. This file provides detailed information about the patch. Install the bundles (see "Step 5: Install the Selected Bundles" on page 45). For example: more /cdrom/TEXT_FILES/PHSS_22540.Installing Support Plus Patch Bundles • Refer to the Support Plus web site for additional information: http://software.html (for 11i) • Diagnostic products have readme files and additional information in the /cdrom/DIAGNOSTICS directory. Some information is in Adobe® Portable Document Format (PDF) files.) You can print or view these directly from the CD. Disable remote access by unregistering the depot before unmounting the CD: swreg -u -l depot /cdrom/HWEnable11i NOTE: You cannot access or register 11. A free version of the Adobe Acrobat® Reader is available at: http://www. Step 4 (Optional): Set Up Hard Disk Access If more than two systems must access the depot.com TIP To simplify sharing of patch information. For example. HP recommends that you copy the patch depots to a hard disk using the swcopy command. Each patch bundle has its own readme file. with the CD mounted at /cdrom. a list of patches (and their dependencies) in the bundle. For example: file:/cdrom/HWEnable11i. you may wish to copy the documentation files onto your own system.com/SUPPORT_PLUS/ • • Refer to the Read Before Installing document that accompanies the Support Plus CD. use: swcopy -s /cdrom/HWEnable11i \* @ /var/tmp/MyDepot Patch Installation 44 . 3. For example: more /cdrom/HWEnable11i.txt • Each bundle readme file is also available in HTML format. For example. This short document contains up-to-date information about known problems with patches in recent Support Plus releases. You can enter a URL into a web browser to view these files directly from the CD.
4. an unexpected condition was encountered. To ensure greatest reliability. Notes • • HP recommends that you do not merge depots created on different versions of HP-UX. and intended for use as a unit. Step 5: Install the Selected Bundles The bundles on the Support Plus CD are built. Create a system backup. HP-UX Patch Management 45 . 3. The bundle readme files may contain additional installation instructions and other important information. HP recommends the following tasks for all systems: 1. you should plan the installation for an appropriate time and announce a system outage to the users ahead of time. an unexpected condition was encountered and you may need to enter additional information or take other action. HP recommends that both the host system and depot should have the same major HP-UX version (for example. HP recommends that after you have selected a bundle for installation (see "HP Patch Bundles" on page 15). Support Plus bundles commonly include patches that require a system reboot. 2. Therefore. Plan for system down time. For example: swinstall -p -s grendel:/cdrom/HWEnable11i \ -x patch_match_target=true -x autoreboot=true NOTE: If the swinstall interactive user interface appears. Even though the swinstall command used for installing the bundles requires that the system has networking enabled. See "Step 2: Check for Last-Minute Information" on page 43. Although you can select individual patches from the bundles. Install the patch bundles. Also. you install the bundle using the matching operations of the swinstall command. Review the documentation. tested. 11. The new depot is automatically registered for use by remote systems.x). to install from a CD mounted and registered on the system grendel: swinstall -s grendel:/cdrom/HWEnable11i \ -x patch_match_target=true -x autoreboot=true You can use the swinstall command's preview mode (-p option) to get an idea of what to expect for the bundle you want to install. it is prudent to limit system activity during any installation. One recovery technique is to use HP's Ignite-UX tools (provided on HP-UX 11i Operating Environment CD1) to create recovery images. Some amount of risk is involved in any system modification. this requires additional analysis of the readme files to ensure you do not overlook software dependencies. If the swcopy interactive user interface appears. You should implement a recovery plan as an insurance policy against a system failure. You may need to enter additional information or take other action.Installing Support Plus Patch Bundles This command copies the contents of the HWEnable11i depot to the local system under the /var/tmp/MyDepot directory. Also. Although you should already have reviewed the patch documentation. it is wise to recheck the readme files before installing. For example.
The cleanup command can also help you manage SD-UX log files. and swremove. These verify the actions taken and begin the preparations as the next cycle begins. WARNING: Ignoring unknown keyword "hp_mfg" at line 229. The swverify command can be used to verify a patch bundle or even a single patch. The swverify command Software Distributor maintains a database of software that it controls known as the Installed Products Database or IPD. See the SD-UX manual for more information. the swagent log is a good place to look for more information.. it includes the output from installation scripts. WARNING: Ignoring unknown keyword "hp_mfg" at line 64.log.Finishing Touches Usage Tip Using the swlist command on an HP-UX 11. swcopy. WARNING: Ignoring unknown keyword "hp_mfg" at line 142. dependency relationships. where task is the name of the command. For depot operations. See "Cleanup Command" on page 22 or "The cleanup Command" on page 72. including swinstall. This can be done using: swverify \* Checking the Logs Each SD-UX command logs messages to /var/adm/sw/sw<task>. The swverify command is provided as a method to compare the data within the IPD with the actual system directories and files. /var/spool/sw/swagent.00 system to list bundles on an HP-UX 11i system may generate warnings. (You can specify a different logfile by modifying the logfile option.) A swagent process performs the actual operations for each of the many SD-UX commands. which would not be in the command log file for swinstall. swagent logs messages to the file swagent. # Contacting target "hpfclc1".. file existence and integrity. For example: swlist -d -l bundle @ 11isys:/cdrom/HWEnable11i/GOLDAPPS11i # Initializing. For example. This log is located at /var/adm/sw/swagent. If you experience problems with one of the SD-UX commands. Finishing Touches Once the installation has completed. This log file is much more complete. but it is recommended that a wildcard be used to verify all products and patches on the system.. This contains a terse summary of command activity.log).log beneath the depot directory (for example. When verifying installed software.. swverify checks software states. a few final steps are required.log. 46 Patch Installation .
or to proactively avoid encountering a known problem in the future. it is possible for several patches to modify a single product or for a single patch to modify several products. When PHCO_0100 is installed. the patch can be installed again.FSD fileset actually being processed.FSD. While it is possible to create a support solution without an understanding of these concepts. the system will determine that fileset Prod. For a patch that delivers a new version of a single file. the ancestor delivered the original version of that file. performance enhancements.FSD is loaded at a later date. For HP-UX 11. The importance of this can be seen through a simple thought experiment of loading PHCO_0100 onto a system that has Prod installed without fileset FSD. "SD-UX Tools & Objects"). The specific details regarding execution are left to the following chapters. and will not load PHCO_0100. with only the PHCO_0100. A patch is an incremental change to the released software. It may deliver defect fixes. If Prod. in practice ancestors are managed between grouping of files known as filesets (see Appendix B. it would rely on external tools or people that do have an understanding. A patch may be loaded in reaction to a system failure. This appendix defines the basic patch terminology and concepts.X patches. This fileset is given the same name as that ancestor.FSD is not present. Certain terms and actions exist solely within the patch space. and in some cases new functionality. This indicates that the FSD fileset was not needed by that system. HP-UX Patch Management 47 . Figure 15 provides a simple example of the four filesets of product Prod being modified by the patch PHCO_0100. While the concept of ancestry can be applied to a single file. Patch Mechanics Ancestors and Patches Ancestry is one of the basic concepts of patch operations. a fileset is created for each ancestor fileset.Appendix A Basic Patch Concepts Patch management differs in many ways from standard forms of software management. The ancestor of a patch is defined as the preexisting software that is being modified or replaced. Working with groups of files.
both having a of revision 1. Since patches are designed to be cumulative. the version delivered with the original product (v1.FS fileset contains the relocatable object files foo. If this were not the case. This patch is superseded by PHCO_2000 which is superseded in turn by PHCO_3000. the presence of a superseding patch will prevent the installation of any preceding patch.o.FSD Patch Supersession Patches for HP-UX products are required to be cumulative. but as each superseded patch returns to the active state it becomes a candidate for removal in future sessions. it remains on the system. A series of patches. is initially patched by PHCO_1000. HP-UX 11. it delivers a new version of foo.FSC Prod. it is not required to have all patches in a supersession chain installed. This means that any individual patch supplied by HP must completely contain all aspects of any preceding patch. an earlier patch could replace files with earlier or outdated versions.Patch Mechanics FIGURE 15. the default behavior is to save copies of all files patched prior to loading the new versions.FS supersession chain of Figure 16. One of the key differences is the ability to perform patch rollback to restore the pre-patched behavior. The Prod.FS PHCO_1000 PHCO_2000 PHCO_3000 The SD-UX-packaged product Prod. In fact. When this happens. In general. Figure 17 shows the save areas for the Prod. Only the active member of a supersession chain can be removed. FIGURE 16.FSB Prod. When PHCO_1000 is loaded. Only the top patch of the chain is in the active (applied) state.X Patch and Ancestors Patch PHCO_0100 PHCO_0100. each replacing the previous patch. The newer patch is said to supersede all earlier patches.o. When a patch is loaded onto a system. If the patch is removed.FSA PHCO_0100.FSD PHCO_0100.0. these saved files are restored. forms a supersession chain (Figure 16). Patch Supersession Chain PROD.FSC PHCO_0100.0) is stored in a save area associated with PHCO_1000. When a patch is superseded.FSB One Patch Multiple Filesets Product Prod Prod.o and bar. the patch numbers increase along a patch supersession chain.FSA Prod. Patch Rollback The installation of a patch differs from the installation of a product in several ways. but is not active. 48 .
The product remains patched until updated to a new version or removed from the system. Patch Rollback PHCO_1000 PHCO_2000 foo. reinstalling the committed patch will not restore the rollback ability.Patch Dependencies FIGURE 17.r=1. it delivers a new version of bar. "The Patch Text File" for more information.o.r=1.2 PROD.o.o. even though it did not change.r=1.1 bar. How? Because the information lost is of the state prior to the installation of the patch.o.o.2 bar. Finally. The versions of foo. it must also deliver the version of foo. and the save area disk space for those patches is also reclaimed. The disk space used to support patch rollback may be reclaimed through patch commitment.o.1 When PHCO_2000 is loaded.r=1.o and bar. if any patch in a supersession chain is committed. any prior patches lose the ability to be restored. cumulative patching ensures that the amount of change delivered by a patch will increase during the life of a supersession chain. The.0 foo.o.r=1.) HP-UX Patch Management 49 .o.FS foo. Each patch could be removed in turn. a patch may document a dependency against patches responsible for these other areas. Patch Dependencies To become fully active.r=1.1 foo. In these cases. the associated save area is deleted and the patch cannot be directly removed. it is important that the areas affected by a single patch are limited.text file field(s) used will be noted as appropriate for each type. Because patches are cumulative.1 bar. (See Appendix C.r=1. a patch may require changes in other areas of the system. As can be seen in the diagram.1 bar.0 Patch Save Area foo.o that was delivered by PHCO_1000.o that are on the system before loading PHCO_2000 are then stored in the save area.r=1.r=1. Patch Commitment The rollback mechanism is not without cost. patch PHCO_3000 delivers new version of both files.o. It requires disk space that may be needed for other applications or data. The different types of dependencies are documented in the text file or readme attribute of each patch.o. and patch PHCO_2000 again becomes the active patch.r=1.1 PHCO_3000 foo.o. If patch PHCO_3000 is removed from the system. As a cumulative patch. Also.0 foo. the files found within its save area are restored to the system.o.FS to the original state.o.r=1. eventually returning Prod.r=1.0 bar. and the existing files on the system are preserved in a save area associated with PHCO_3000. and in some cases multiple copies of the same file will be preserved. When a patch is committed to the system.
Standard dependencies are documented in the Patch Dependencies field. if a patch has a dependency on a superseded patch. These include optional dependencies that are required under specific circumstances or hardware dependencies below the system level. • Ordered Dependency An ordered dependency is an installation-time software dependency without any exceptions or conditions. These system-level dependencies are documented in the Hardware Dependencies field. This is why SD-UX can resolve static dependencies: they don't run the risk of being superseded. their supersessions and their dependencies and then install the appropriate patches. otherwise known as a line-in-the-sand patch. SD-UX can register and automatically manage required patch levels. This analysis is done by the SD-UX tools through some additional attributes within patches and by enforcing the registration of patch dependencies within each patch. but the dependency must be loaded first for the requirement to be satisfied. An example would be that the commands in PHCO_1000 cannot be used without the kernel support of patch PHKL_1234. These are documented in the Patch Dependencies field and/or the Special Installation Instructions field. A dependency that is not directly enforceable by SD-UX (although patch scripts can provide indirect enforcement). swinstall and swcopy will analyze the patches.00.Patch Dependencies Dependency Types While the dependencies of a patch are generally quite simple. • Standard Dependency The standard dependency is an execution-time software dependency without any exceptions or conditions. Static dependencies are those which involve a consolidated patch. there are some cases where special types of dependencies may be encountered. SD-UX tools acquired the ability to manage patches natively (without scripts) and thus static dependencies. • Other Dependencies There are dependencies that cannot be described in a simple manner. (See "Viewing Dependency Information" on page 51. Manual dependencies are indicated by the manual_dependency category tag and are listed in the PDep or Other Dependency field of the patch text file or readme attribute. All such miscellaneous dependencies are explained in the Other Dependencies field.00. However in 11i. Enforced Patch Dependencies The ability to manage patch dependencies was not included in the original design of the SD-UX. The contents of these patches may be modified by subsequent patches but they are not meant to be superseded. Three types of dependencies are used in HP-UX 11i: Table 2: HP-UX 11i Dependency Handling Dependency Type Description Corequisite Prerequisite Manual dependency A standard dependency listed in the PDep field of the patch text file and automatically enforced by SD-UX.) As long as the desired patch and its dependencies are loaded on the depot. In 11. The ability to automatically resolve superseded dependencies for patches was not implemented because of time constraints. 50 . there is no way for SD-UX to recognize that the latest patch in the supersession chain has to be loaded. • Hardware Dependency Certain patches are only applicable to specific system models. An ordered dependency listed in the PDep field of the patch text file and automatically enforced by SD-UX. In 11.
known as the patch status. You should check for this tag every time that you want to install from a bundle or depot to make sure that there are no external dependencies. The ITRC data. This section examines some of these properties. As the newest available patch. the patch will contain a category tag which states that the user must manually resolve any dependencies. if the dependency relationship is more complex than the grammar for requisites can support. then for each of those patches.text file is described in detail in Appendix C.00 cannot handle the new functionality) the patch will not register its dependencies. Any value other than those listed here denotes a patch that should be restricted and used only with full understanding and great caution. • General Release A status of General Release indicates a patch that is approved for widespread use and is the active member of the supersession chain. "The Patch Text File". provide the current patch state. Patch Status Almost every patch created is intended for general release to all customers. If not then proceed with the copy or installation. it will contain all known fixes to date for the target software. and in particular the Patch Database itself.text file and is also displayed when viewing patches within the ITRC. When this happens. The data within the . If the patch is multi-release then (since 11. you must perform a manual dependency analysis such as the one outlined in "Dependency Analysis for HP-UX 11. you must consult the following fields in the patch text file: • Pdep—patches listed in this field are not enforceable but can be detected and listed by the patch database. Viewing Dependency Information To review patches with manual dependencies. the. but the patch may transition into different release states.X patches include internal readme files that you can view with the swlist command. HP-UX Patch Management 51 . • Other Dependencies—patches listed in this field are conditional dependencies but are not detected by the patch database. 11. The following command checks for this tag in the patches within depot /MyDepot: swlist -d -l product *. The following patch states are used by all patches that should be available to customers. For example: swlist -d -l product -a readme PHKL_23400 @ /MyDepot The HP-UX Patch An HP-UX patch is a partial delivery of software that fixes defects found in the original. This is the manual_dependencies tag.The HP-UX Patch Two situations may result in unregistered dependencies. In addition. the requirement of requisite registration is waived.c=manual_dependencies @ /MyDepot If this command yields some patch names. Also.00" on page 35. can be found within the . The current release state. Each patch includes a set of properties that are documented in an associated text file.text file reflects the initial state of the patch due to the static nature of the file. or in some cases extends the original functionality. • Special Installation Instructions—this field often includes explanatory text for patches listed in the Other Dependencies field.
The HP-UX Patch • Special Release A special release patch is an active patch that was not intended for use by all customers. a patch may be recalled and removed from general distribution. Patch Identification An HP-UX patch name consists of a four-character type identifier followed by an underscore followed by a four or five digit numeric field. While there may still be compelling reasons to install such a patch (such as a performance enhancement). The numeric field. data corruption. A patch can be classified into one of three categories: • Not critical No part of the patch addresses a critical failure. it enters the superseded state. • Critical The patch delivers a new fix for a critical failure. Applicable to both General and Special Release patches. certain patches address issues of the highest priority and are considered critical. patch supersession should not be considered in a negative manner. system panic. Patches cannot be partially recalled. and not the probability that it will be encountered. Even if you take a very conservative approach to changing your system. but supersedes a critical patch The patch does not contain critical fixes. • Not critical. The known qualities of an older patch may have greater value than the non-critical improvements. The severity of the defect is such that the patch should be evaluated for applicability to local systems and environments. The Critical Patch While each patch is created to improve upon the original version of the ancestor software. there is no reason to take any immediate action. called the patch number. each system administrator should review the issues documented in the recall notice with the value of the current patch fixes and cost of system change. • General/Special Superseded When an active patch is replaced by a newer version. the correct action for a specific system may vary. or system hang. Examples of conditions that cause a patch to be marked critical include data loss. • General/Special Recalled Under certain conditions. you may choose to proactively load a critical patch to avoid a possible failure. Patches may be created as special release if a set of customers require nonstandard behavior or configuration-specific change that would cause problems for others. but delivers critical content that was introduced within a patch that has been superseded within the same patch chain. While the newer patch should contain additional fixes. they may not be critical. is unique for a patch regardless of patch type. As with superseded patches. The currently defined patch types are: PHCO PHKL PHNE PHSS Commands and libraries Kernel Networking All other HP-UX subsystems 52 . and while the generic recommendation will be to remove and replace the patch. Patches are marked as being critical in response to the severity of a failure.
text file is the complete documentation for the patch. special installation instructions (if any). When exercised by the shell. For more information on these and other attributes. Shell archives are a useful and portable method to package groups of files for transfer between Unix-based systems.X patches are also marked through the is_patch and is_sparse attributes and the patch category tag. and the list of files contained within the patch. the patch shell archive will recreate two files within the current working directory. These sources are described in more detail in chapter 3.depot file is an SD-UX tape-style depot containing the actual patch.The HP-UX Patch This naming convention is not recognized by the SD-UX software management tools.text files. see "Patch Related Object Attributes" on page 56. The . HP-UX Patch Management 53 . The Patch Shar File The shar(1) utility is used to produce a shell archive file. When a patch is acquired individually from the Patch Database within the ITRC or from the Fulfillment Server (FFS). it is packaged as a shell archive. The . These are the .depot and . HP-UX 11. "Acquiring Patches". including descriptions of the symptoms and defects repaired by the patch. dependencies.
The HP-UX Patch 54 .
This section gives you a simplified view of the object types that relate to patches. patches are created and managed at the product level. but you need only a small subset of SD-UX functionality for patching operations. Many patch operations involve some aspects of the SD-UX tools. consult the SD-UX manuals: • Managing HP-UX Software with SD-UX (for 11. This appendix does not discuss SD-UX remote operations or installations involving alternate roots. SD-UX functionality that is not appropriate for patching is not discussed. and patch filesets are delivered only within a patch product.hp. you should avoid selecting patches at the fileset level. Therefore. The Basic SD-UX Object Types Software Distributor uses a variety of object types. HP-UX Patch Management 55 .00) • Software Distributor Administration Guide (for 11i) These manuals are available at http://docs. Consult the SD-UX manual for more information.Appendix B SD-UX Tools & Objects This appendix provides an overview of Software Distributor commands for HP-UX (SD-UX-UX) commands and concepts as they apply to patching. You can find formal definitions in the SD-UX manual or the sd(4) man page. SD-UX is included with the HP-UX Operating System and by default manages software on the local host only. In general. You can also enable SD-UX to install and manage software simultaneously on multiple remote hosts from a central controller.com. The Fileset A fileset is one or more related files. A fileset may include scripts that control installation and removal. Selecting patches by fileset level may cause a fix to be only partially applied. This appendix does not present a comprehensive view of SD-UX. even though SD-UX permits this kind of selection. For in-depth information. It describes a unique subset of the files that make up a product. grouped into a manageable unit.
HP provides several types of standard patch bundles. See "The swlist Command" on page 66 for more information.VXFS-PRG ProgSupport. You can view SD-UX object attributes with the swlist command. A bundle can be thought of as a virtual "configuration" of software. • Lists all of the patch filesets that have modified this fileset.00 release.VXFS-BASE-KRN.11. More than one bundle can contain the same software objects.g. You can change the contents of a depot. The Depot A depot is a directory that contains software products or bundles that are available for direct or remote installation.v=HP JournalFS.VXFS-PRG. each modifying a different fileset found on the HP-UX 11.fr=B.00. which contains three filesets.11.VXFS-BASE-KRN PHKL_18543. Bundles provide a convenient way to group software objects together for easy selection. • Contains the software_spec of the ancestor fileset that this patch fileset modified when it was installed. Patch Related Object Attributes Each of the objects described in "The Basic SD-UX Object Types" has a set of properties known as attributes. Attributes control aspects of patch behavior and define patch properties and relationships.X patches that require customization include SD-UX control scripts at the product level.00. (See "Software Specifications" on page 73 for more information on software_spec.fr=B. ancestor • Applies to filesets. See "HP Patch Bundles" on page 15 for more information. CD or tape) or a single. A depot can also be a distribution media (e.00.. The Bundle A bundle encapsulates products and filesets into a single software object.11.) 56 .v=HP JournalFS.fr=B. serial file that contains products or bundles. applied_to • Applies to patch filesets.Patch Related Object Attributes The Product An HP-UX patch is structured as a single SD-UX product that contains one or more filesets.C-INC PHKL_18543. • The following example shows patch PHKL_18543. The patch-related attributes are described below. swlist -l fileset -a ancestor PHKL_18543 # PHKL_18543 PHKL_18543. • Indicates the fileset that this fileset modifies. HP-UX 11.C-INC.v=HP applied_patches • Applies to base (non-patch) filesets.
committed: A committed patch cannot be directly removed from the system. superseded: Has been replaced by a newer member of its supersession chain. committed: A committed patch cannot be removed from the system. is_patch • Applies to both patch products and filesets. In HP-UX 11. A patch in the applied state has not been committed or superseded. install patch PHCO_22526. • When set to true. In 11i. HP-UX Patch Management 57 . the patch_state attribute records the condition of patches. • In addition to the state attribute (also described in this section). is_patch indicates that the object is a patch.00. superseded: A patch in the superseded state has been replaced by a newer member of its supersession chain. The is_patch attribute is required for patches to be managed via the autoselect_patches or patch_match_target options of swinstall and swcopy. and others may be created by customers with the swmodify command. A category_tag can be used as a selection mechanism (see "Patch Hubs" on page 33). To obtain this state in 11. is_reboot • Applies to filesets. depending on the order of the patch operation: applied: An applied patch contains the software that is currently active on the system and is the most recent member of its supersession chain (of one or more patches) to have been loaded. is_sparse • Applies to patch filesets. Several tags are defined during patch creation. This ensures that a patch fileset cannot be explicitly selected when not appropriate. patch_state • Applies to patch filesets. which records the installation states of software. • When set to true. • When set to true. You may install PHCO_22526 to obtain the committed/superseded state described below. Not committed.00 systems. This attribute gets rid of the ambiguity created by the committed attribute above.Patch Related Object Attributes category_tag • Applies to filesets or products. patch filesets exist in one of three conditions. patch filesets exist in one of four conditions: applied: Same as above. A committed patch is applied but not superseded. A patch in the superseded state may or may not have been committed. is_sparse indicates that the current fileset is incomplete and cannot be loaded in the absence of the fileset's ancestor. is_reboot indicates that installation of the fileset will cause the system to reboot. • Provides a label for a fileset or product. committed/superseded: A committed/superseded patch is committed and superseded. A committed fileset is also in either the applied or superseded state (which state applies cannot be determined from the patch_state field).
The swconfig command is not discussed in this tutorial. superseded_by • Applies to patch filesets. state • Applies to filesets. configured (IPD only): The product was successfully installed AND configured. transient: Indicates that swinstall or swcopy was killed or aborted during the execution phase leaving the software in an unknown and incomplete state. available (depot only): The software is ready for access. No further operations are required. supersedes • Applies to patch filesets. Note that all superseded filesets are included. (Note that 11. corrupt: Indicates that errors detected in the execution phase of a swcopy or swinstall process left the software in an unknown state and that the software should not be used. • The software_spec attribute (short for software specification) contains the fully qualified identifier for the bundle. and never in software depots. consult the swconfig(1m) man page or the SD-UX manual for more information. An SD-UX operation leaves a fileset in one of the following states and records it in the fileset's state attribute.Patch Related Object Attributes readme • Applied to products. 58 . • A fileset's state attribute (also used for non-patch software) provides useful information about the installation state of software. • The readme attribute of an HP-UX patch contains the text file. It can be used by a swinstall or swcopy session using the depot as the source. product. SD-UX commands automatically keep track of software management operations by creating an Installed Products Database (IPD) and various catalog files that contain information about the software on the system. The software_spec contains the object name and any version or architecture information. software_spec • Applies to bundles.X SD-UX-UX commands automatically keep track of software management operations by creating an Installed Products Database (IPD) and various catalog files that contain information about the software on the system. The transient state differs from the corrupt state in that SD-UX did not detect the failure when it initially occurred. but the ordering of the superseded filesets may not match the order of the supersession chain itself. or filesets. See "Software Specifications" on page 73 for more information. HP recommends that you move all patches left in the installed state to the configured state with the swconfig command. or fileset. Although not every patch requires configuration. products. • Records the software specification of the fileset that superseded the fileset on a given system. This attribute is only set for installed patch filesets. Some attributes are stored in the IPD only): installed (IPD only): The software was successfully installed but not configured. • Lists all prior filesets that a patch fileset supersedes.
swremove. [software_selections] Patch Related Command Line Arguments -i Use an interactive user interface. and swlist have an optional GUI mode.unconfigures and removes software products. HP recommends that you use only the options discussed below. swreg .registers or unregisters depots or roots.modifies software product information in a target root or depot. swinstall. swpackage . swcopy .. • swinstall has numerous options that you should not use for patching because they lack dependency support.. Additional concepts for using the SD-UX commands are discussed in "Other Options and Aids to Using the SD-UX Commands" on page 73. Otherwise a terminal user interface (TUI) designed for use on ASCII terminals is invoked. -p -v HP-UX Patch Management 59 . Preview mode is not enabled by default. patch_match_target) should be the preferred method for installing patches. swmodify . swlist . This option affects only standard output and not the log files. swremove . The swinstall Command The swinstall command is used to load patch software from a source depot and onto a target system.displays information about software products. the automatic matching options(autoselect_patches. ordered by those most commonly used: • • • • • • • swinstall . TIPS: • Because many patches aren't designed for individual installation.Introduction to the SD-UX Commands Introduction to the SD-UX Commands This appendix discusses the SD-UX commands that relate to patching.installs and configures software products. swcopy. a graphical user interface is invoked.copies software products for subsequent installation or distribution. Synopsis swinstall [-i] [-p] [-v] [-s source] [-x option=value]. If the environment variable DISPLAY is set to a valid X windows display. Previews the install operation without performing the actual installation. All SD-UX commands run from the command line.packages software products into a depot (directory or tape). The following list shows the commands. The GUI starts by default if you enter swinstall without any software_selections. Requests verbose mode.
those that do employ them are enforcing critical requirements of content and load order. default values are shown. enforce_dependencies=true Options→Change Options→Enforce dependency analysis errors in agent Enforces software dependencies. (when marking software) When software is selected for installation with an SD-UX-enforced dependency. This option should not be set to false unless directed by an HP Support Engineer. that software will automatically be selected for installation if present in the source depot and autoselect_dependencies is set to true. See "Software Specifications" on page 73 for more information software_selections Patch-Related Options The following options have the most relevance to patching (see "Setting Default Values for Command Options" on page 73). this option becomes even more important and helpful. option=default value Description autoreboot=false autoselect_dependencies=true Menu Path in Interactive Interface None (GUI waits for permission to reboot) Actions→→Autoselect dependencies Enables an automatic reboot upon completion of the software installation. Since all 11i patch dependencies will be enforced by SDUX. those that do employ them to enforce critical requirements of content and load order. While few 11. autoselect_patches=true Actions→Manage Patch Selection→Automatically select patches for software to be installed When loading a software product. any bundle wrappers within the source depot that contain software selected for installation will be automatically selected if the is_reference attribute is set to true. if the dependency is not present on the target system and is not selected for installation from the source depot. Patch related command options are specified below. 60 . it is especially important that this option is taken advantage of in selecting patches and avoiding unwanted configurations. Sets the specified command option to the value given. autoselect_reference_bundles=true None When set to true. Note that this does not mean all of the software listed in the wrapper will be selected. All 11i patches will contain enforced dependencies except for those that meet strict exception rules. any patches within the same depot for that product will automatically be selected for installation. As a result. installation will only proceed if enforce_dependencies is set to false. consult the swinstall(1m) man page or refer to the SD-UX manual. For the full set of available options. When software is selected for installation with an SD-UX-enforced dependency. While few 11. This option should not be set to false unless directed by an HP Support Engineer. See "Setting Default Values for Command Options" on page 74 for more information.The swinstall Command -s source -x option=value Specifies the depot (source) containing the software to be installed. Where appropriate. manual patch dependency analysis. eliminating lengthy. One or more software specifications. only the bundle wrapper itself.00 patches exist with dependencies enforced by the SD-UX tools.0 patches exist with dependencies enforced by the SD-UX tools. overriding any other values for that option.
patches are loaded directly to the committed state and cannot be rolled back. patch_save_files=true Options→Change Options→Save files replaced by patch for later rollback If set to false.X systems this option was used to select patches within a depot that applied to the target system. "Planning for Recovery." on page 5 for notes on other options. Specify the device file of the tape drive to be used as the default. This option is not yet recommended for general use in 11. reinstall=false Options→Change Options→Reinstall filesets even if the same revision exists Prevents SD-UX from re-installing (overwriting) an existing revision of a fileset. When set to true and superuser has write permission on the remote file system. Setting this option to false removes this restriction. filesets will be reinstalled. See Chapter 2. patch_filter=software_specification Actions→Manage Patch Selection→Filter The patch_filter option can be used to specify a subset of software available to load. This option should not be used unless directed by an HP Support Engineer. swinstall skips files that would be installed to a remote (NFS) file system (or that are already there). It is also an especially powerful tool for depot management in 11i since dependencies are dealt with correctly. If set to true.X releases to provide this functionality. Prevents installation of files to a target that exists on a remote (NFS) file system. patch_match_target=false Actions→Manage Patch Selection→Automatically select patches for software installed on the target Select all patches within the source depot that modify the existing system software. the patch_match_target option is the preferred method for HP-UX 11. HP-UX Patch Management 61 . this option is not recommended unless alternative recovery mechanisms are available. match_target=false Actions→Match What Target Has Selects all software within the source depot with an ancestor attribute that matches a fileset currently on the target system. mount_all_filesystems=true Options→Change Options→Mount filesystems in /etc/fstab or /etc/checklist By default. While on HP-UX 10.0 as no provision is made for dependencies. While a convenient way to control disk usage. swinstall requires that all filesystems listed in the systems /etc/fstab file are mounted prior to installation. this option can be used for 11. source_cdrom=/SD-UX_CDROM source_tape=/dev/rmt/0m write_remote_files=false None (default cannot be changed within GUI) None (default cannot be changed within GUI) None Specify the device file of the CD-ROM to be used as the default. These scripts may issue errors to protect the system from incorrect patch usage. the remote files are installed. By default.The swinstall Command enforce_scripts=true Options→Change Options→Enforce script failures Each patch may have several installation scripts associated with it. This is the recommended method to install patches from a managed depot (such as those provided by HP). However.00 patch selection when combined with user-defined category tags.
-p -v -s source -x option=value software_selections target_selections 62 . For example. This option affects only standard output and not the log files. the syntax is host:/directory where the host name can be a name. Preview mode is not enabled by default. Note that the swcopy command automatically registers (enables remote access to) any depot that it creates. See "Software Specifications" on page 73 for more information The absolute path name (directory location) to which you want the software_selections to be copied.The swcopy Command Examples • Install from a CD mounted and registered on the system grendel: swinstall -s grendel:/cdrom/XSWGR1100 \ -x patch_match_target=true -x autoreboot=true • Use the swinstall command's preview mode (-p option) to get an idea of what to expect for the bundle you want to install.) Synopsis swcopy [-i] [-p] [-v] [-s source] [-x option=value] [software_selections] [@ target_selection] Patch Related Command Line Arguments -i Use an interactive user interface. If you specify a host with the directory. you can copy all of the contents of individual patches into a single depot from which the group can be loaded in a single session and with a single reboot (if needed). Requests verbose mode. or internet address. Patch related options are specified below. domain name. If the environment variable DISPLAY is set to a valid X windows display. Previews the copy operation without performing the actual copy. One or more software specifications. For example: swinstall -p -s grendel:/cdrom/XSWGR1100 \ -x patch_match_target=true -x autoreboot=true The swcopy Command The swcopy command copies software from one depot to another. overriding any other values for that option. See "Setting Default Values for Command Options" on page 74 for more information. a graphical user interface is invoked. This can be particularly useful if software exists in several depots. Sets the specified option to the value given. (See "The swreg Command" on page 69 for more information. You do not need to use the swreg command on depots created by swcopy. The GUI starts by default if you enter swcopy without any software_selections. Otherwise a terminal user interface (TUI) designed for use on ASCII terminals is invoked. Specifies the depot (source) containing the software to be copied.
00 patches currently exist with dependencies enforced by the SD-UX tools. . This will conserve disk space and can enhance performance on slower networks (50 Kilobytes/second or less). reinstall=false Options→Change Options→Recopy filesets even if the same revision exists Prevents SD-UX from overwriting an existing revision of a fileset. When software to be copied has an SD-UX-enforced dependency. filesets will be recopied. autoselect_reference_bundles=true None (default cannot be changed within GUI) When set to true. Where appropriate. Setting this option to false removes this restriction. making this option very useful. mount_all_filesystems=true Options→Change Options→Mount filesystems in /etc/fstab or /etc/checklist By default. See also the compress_files option.The swcopy Command Patch Related Options The following options have the most relevance to patching (see "Setting Default Values for Command Options" on page 73). swcopy requires that all filesystems listed in the systems /etc/fstab file are mounted prior to installation. This option should not be set to false unless directed by an HP Support Engineer. source_tape=/dev/rmt/0m uncompress_files=false None (default cannot be changed within GUI) Options→Change Options→Uncompress files after transfer Specifies the device file of the tape drive to be used as the default. compress_files=false Options→Change Options→Compress files during transfer Setting this option to true causes swcopy to compress file before transfer to the target depot. For the full set of available options. consult the swcopy(1m) man page or refer to the SD-UX manual. that other software will automatically be selected to be copied if present in the source depot and autoselect_dependencies is set to true. any bundle wrappers within the source depot that contain software selected for copying will be automatically selected if the is_reference attribute set to true. The majority of 11i patches have SD-UX-enforced dependencies. files are uncompressed before swcopy puts them into the target depot. default values are shown. When set to true. HP-UX Patch Management 63 . If set to true. if that dependency is not present on the target system and is not marked for copying from the source depot the copy will only proceed if enforce_dependencies is set to false. While few 11. those that do employ them to enforce critical requirements of content and load order. enforce_dependencies=true Options→Change Options→Enforce dependency analysis errors in agent Enforces software dependencies. Note that this does not mean all of the software listed in the wrapper will be selected. only the bundle wrapper itself. although it may not improve fast networks. option=default value Description autoselect_dependencies=true Menu Path in Interactive Interface Actions→Autoselect dependencies (when marking software) When software is selected for copying with a registered dependency on other software.
• swremove may not always be your first and best solution for error recovery. files are copied to remote systems. swcopy skips files that would be copied to an NFS file system (or that are already there). When set to true and superuser has write permission on the remote file system. Synopsis swremove [-i] [-d] [-p] [-v] [-x option=value] [software_selections] [ @ target] 64 . • Removal of a patch bundle does not automatically return you to the patch state prior to loading that bundle. It also removes software from depots. using the default depot at hostX as the source: swcopy -i -s hostX • Copy all patches in current directory to the depot /hub/patches (assuming root shell is /sbin/sh): for PATCHDEPOT in *.8 \* @ /depots/oldsys The swremove Command The swremove command deletes software that has been installed on your system.The swremove Command write_remote_files=false None Prevents copying of files to a target that exists on a remote (NFS) file system.depot do swcopy -s $PATCHDEPOT \* @ /hub/patches done • Copy a HP-UX 10.X system. Make sure your other recovery methods are not more appropriate before you use this command. If the patch was needed to fulfill a documented dependency then patches to satisfy the dependency must be activated via rollback or installation. swcopy -s oldsys:/depot -x layout_version=0.X style depot from the system oldsys to an HP-UX 11. • You should not use swremove to remove patch information that remains in the IPD after installing a new version of HP-UX. copy the contents of the XSWGR1100 depot to the local system under the /var/tmp/MyDepot directory.00 system and you use swremove to remove a patch. Note that swremove has several limitations when used for patch operations: • You cannot use swremove to remove committed patches. see "The cleanup Command" on page 72. In HP-UX 11i you cannot remove a patch that is required by another patch. Examples • With the CD mounted at /cdrom. swcopy -s /cdrom/XSWGR1100 \* @ /var/tmp/MyDepot • Invoke an interactive session. The swremove command will fail if the unwanted patch fulfills a dependency. By default. you must make sure you didn't "break" any software dependencies. • If you are on an 11.
enforce_scripts=true Options→Change Options→Enforce script failures Each patch may have several removal scripts associated with it. One or more software specifications. the target is assumed to be the system itself. While few 11. enforce_dependencies=true Options→Change Options→Enforce dependency analysis errors in agent Enforces software dependencies. These scripts may issue errors to protect the system from incorrect patch usage. Preview mode is not enabled by default. Verbose mode is enabled by default. Previews the remove operation without performing the actual removal. default values are shown. This option affects only standard output and not the log files. Requests verbose mode. those that do employ them to enforce critical requirements of content and removal order. Where appropriate. Do not set this option to false unless directed to do so by an HP Support Engineer. overriding any other values for that option. consult the swremove(1m) man page or refer to the SD-UX manual. option=default value Description autoselect_reference_bundles=true Menu Path in Interactive Interface None If true. Sets the specified command option to the value given. since all 11i patches enforce dependencies. a graphical user interface is invoked. HP-UX Patch Management 65 . If false. -d -p -v -x option=value software_selections target Patch Related Options The following options have the most relevance to patching (see "Setting Default Values for Command Options" on page 73). If the environment variable DISPLAY is set to a valid X windows display. Otherwise a terminal user interface (TUI) designed for use on ASCII terminals is invoked. bundles that have the is_reference attribute set to true will be automatically removed when the last of its contents is removed. When software selected for removal has a registered dependency. See "Setting Default Values for Command Options" on page 74 for more information. However. If not specified. this option is very useful in maintaining patch integrity and system stability. . removal only proceeds if enforce_dependencies is set to false. See "Software Specifications" on page 73 for more information The depot from which software is to be removed. Patch related command options are specified below. if the dependency is not present on the target system or also selected for removal from the source depot. The GUI starts by default if you enter swremove without any software_selections. the bundles will not be automatically removed.The swremove Command Patch Related Command Line Arguments -i Use an interactive user interface.00 patches currently exist with dependencies enforced by the SD-UX tools. This option should not be used unless directed by an HP Support Engineer. Operate on a depot rather than installed software. For the full set of available options.
You must specify -i to invoke the GUI. it never starts by default.The swlist Command mount_all_filesystems=true Options→Change Options→Mount filesystems in /etc/fstab or /etc/checklist By default. SD-UX requires that all filesystems listed in the systems /etc/fstab file are mounted prior to removal. More specifically: • • • • • See what's installed on a system. Browse the patch documentation. /depots/MyDepot: swremove -d \* @ /depots/MyDepot The swlist Command The swlist command provides information on software installed on a system or located in a depot. If the environment variable DISPLAY is set to a valid X windows display. a graphical user interface is invoked. swremove skips files that would be removed from an NFS file system. Examples • Remove only the bundle wrapper XSWHWCR1100 from the system. See what software is in a depot. one attribute per line. then list the selected attributes in the above format. leaving any contents present (Note that the trailing period (. Synopsis swlist [-i] [-d] [-v] [-a attribute] [-l level] [-s source] [software_selections] [ @ target] Patch Related Command Line Arguments -i Invokes a GUI interface that lets you perform interactive software selections. Lists software depots instead of software currently installed on the target system. files are removed from remote systems. If no -a options are specified. • Remove all contents of the depot. By default. 66 .) is essential to removing the wrapper only): swremove XSWHWCR1100. then list all the attributes for an object. Check attributes of software. The attributes are listed in the format: -d -v keyword value If one or more -a options are specified. See what depots are available on remote systems. When set to true and superuser has write permission on the remote file system. write_remote_files=false None (default cannot be changed within GUI) Prevents removal of files from a target that exists on a remote (NFS) file system. Setting this option to false removes this restriction. Otherwise a terminal user interface (TUI) designed for use on ASCII terminals is invoked.
the target is assumed to be the system itself. revision. and description of the product. See "Software Specifications" on page 73 for more information The depot to be listed. You can also specify the sources as target depots and list them using the -d option. and description of the product or fileset to be listed. • default (no level specified) When no level is specified. and all products and filesets are listed as a comment showing revision and description before any patch fileset that apply to it. the ordering of the arguments does not control the format of the list. Each file is preceded by the product and fileset that is the registered owner of that file. • product List all products with revision and description for each. As is the case with their respective levels. The listing is sorted by ancestor. The listing may be limited in scope by the software_selections specification. If not specified. This is an alternative way to list a source depot. The values used include: -s source software_selections target -l level • file List all files recorded in the IPD. • bundle List all bundles with revision and description for each. A comment (marked by a leading # character) precedes each block giving the name. revision.fileset format) with the associated revision and description. the bundles and products are listed with revision and one-line description. Specifies the detail of the swlist output. One or more software specifications. A comment (marked by a leading # character) precedes each block giving the name. While this option may be specified multiple times. HP-UX Patch Management 67 . • fileset List all filesets recorded in the IPD (in product. swlist displays all bundles within the depot followed by any products not contained within a bundle.The swlist Command -a attribute The named attribute is included in the listing when defined at the specified level. followed by the associated description and current patch_state. • category List all category tags currently defined within the target depot. • patch List all patch filesets using the full software specification. • depot List all registered depots on the target system. Specifies the software source to list.
00 swlist functionality can be turned on in an 11i system (all patches in the IPD are listed).c=patch @ grendel:/var/MyDepot • List the filesets modified by installed patch PHSS_8675 swlist -a ancestor PHSS_8675 • List all of the files delivered within patch PHCO_12140 after downloading from the ITRC: swlist -d -l file @ /tmp/PHCO_12140. However. swlist only lists those patches which are active on the system. show_superseded_patches=false Examples • List all patches in the depot /var/MyDepot on the system grendel: swlist -d -l product *.depot • List all patches that have modified the LVM product swlist -l patch LVM • Display the documentation for all patches containing critical functionality swlist -a readme -l product *. In 11.show_superseded_patches=false must be added to the /var/adm/sw/ defaults file. swlist lists all patches in the IPD.c=critical • List all category tags defined in the depot /var/MyDepot on the system grendel swlist -d -l category @ grendel:/var/MyDepot Also see "Software Specifications" on page 73 for more examples. Where appropriate.00 systems. option=default value Menu Path in Interactive Interface The swlist command lists the contents of the IPD. consult the swlist(1m) man page or refer to the SD-UX manual. By setting this option to true the 11. For the full set of available options. default values are shown. whether or not they are superseded. to get the 11i functionality on an 11. In 11i.The swlist Command Patch Related Options The following options have the most relevance to patching (see "Setting Default Values for Command Options" on page 73). 68 .00 system. patch PHCO_22526 must be installed and swlist.
Synopsis swmodify [-d] [-p] [-v] ]-a attribute[=value]] [-x option=value] [software_selections] [ @ target] HP-UX Patch Management 69 . Examples • Register the patch depot XSWGR1100: swreg -l depot /cdrom/XSWGR1100 • Disable remote access by unregistering the depot XSWGR1100 (local access is still enabled): swreg -u -l depot /cdrom/XSWGR1100 The swmodify command SD-UX commands automatically keep track of software management operations by creating an Installed Products Database (IPD) and various catalog files that contain information about the software on the system.) Synopsis swreg -l depot [-u] [-v] [objects] Patch Related Command Line Arguments -l depot Perform operations on depots. -u -v objects Patch Related Options None. WARNING: With the exception of committing patches and creating category tags. Specifies the path to the object[s] to be registered or unregistered. Improper alteration of the information in the IPD could cause unexpected behavior during subsequent patching or system updates and leave your system in an unsupportable state. Although you cannot edit the IPD or catalog files directly. they are not within the scope of this tutorial.The swreg Command The swreg Command The swreg command registers or unregisters an existing depot. (For the full set of available options. Requests verbose mode. the swmodify command lets you change the contents of these files via the command line. When a depot is registered. This option affects only standard output and not the log files. the swmodify command is not recommended for general usage. While other levels of SD-UX objects may be modified by swreg. Unregistration of a depot can be a convenient way to limit access during development. (Note that unregistered depots are still available locally. consult the swreg(1m) man page or the SD-UX manual. Causes swreg to unregister the specified objects instead of registering them. it can be accessed from remote systems.
Sets the specified command option to the value given. modify. consult the swmodify(1m) man page or refer to the SD-UX manual Menu Path in Interactive Interface Commits a patch by removing files saved for patch rollback. See "Software Specifications" on page 73 for more information The depot to be modified. If the -u option is specified. Previews the modify operation without modifying anything. For the full set of available options. then delete the attribute from the given software_selections (or delete the value from the set of values currently defined for the attribute). The given target must be a depot. Preview mode is not enabled by default. or delete the value of the given attribute.The swmodify command Patch Related Command Line Arguments -a attribute[=value] Add. When set to true. overriding any other values for that option. software_selections target Patch Related Options The following options have the most relevance to patching (see "Setting Default Values for Command Options" on page 73). If not specified. Otherwise add/modify the attribute for each software_selection by setting it to the given value. Requests verbose mode. this option removes the saved files for the patches specified in the software selections for the command. Where appropriate. -d -p -v -x option=value Perform modifications on a depot. The default value is false. Once you have run this option on a patch. See "Setting Default Values for Command Options" on page 74 for more information. Multiple -a options can be specified. One or more software specifications. Patch related command options are specified below. Each attribute modification will be applied to every software_selection. you cannot remove the patch unless you remove the associated base software that the patch modified. This option affects only standard output and not the log files. option=default value patch_commit=false Examples • Commit the patch PHKL_1234 and remove its corresponding rollback files: swmodify -x patch_commit=true PHKL_1234 • Mark all patches in the depot /depots/newpatches with a new category tag to indicate that they have been approved: swmodify -a category=approved \* @ /depots/newpatches 70 . default values are shown. the target is assumed to be the system itself.
/var/spool/sw is used as the default depot directory. Without this operand. target_type=directory HP-UX Patch Management 71 . this command allows the transfer of software onto a tape or into a tape depot which can then be used as a software source. This creates smaller depots. Synopsis swpackage [-p] [-v] [-s directory] [-x option=value] [software_selections] [@ target] Patch Related Command Line Arguments -p -v -s directory -x option=value Previews the package operation without performing the actual packaging. Without this operand. The recognized types are directory and tape.8. This option affects only standard output and not the log files. swpackage uses the device file /dev/swtape. Specifies the POSIX layout version to which the SD-UX commands conform when writing distributions. If you are creating a distribution tape. Refer to the swpackage(1m) manpage or the SD-UX manual for more information. Patch related command options are specified below. default values are shown. An existing directory depot (which already contains products) to be used as the source. overriding any other values for that option. The tape can be used in the absence of networking support. software_selections target Patch Related Options The following options have the most relevance to patching (see "Setting Default Values for Command Options" on page 73). this operand defines the location of the directory. Supported values are 1. See "Software Specifications" on page 73 for more information If you are creating a distribution depot (directory). option=default value compress_files=false layout_version=1. The device file must exist so that swpackage can determine if the media is a DDS tape or a disk file. For the full set of available options. and the tape depot could be provided via ftp(1). Requests verbose mode. Where appropriate.0 Menu Path in Interactive Interface Setting this option to true causes swpackage to compress files before packaging them. Sets the specified command option to the value given. One or more software specifications. Preview mode is not enabled by default. See "Setting Default Values for Command Options" on page 74 for more information. Either method can be used to transport the contents of a depot to another system for local access. Defines the type of distribution to create. this operand names the device file on which to write the tar archive. consult the swpackage(1m) man page or refer to the SD-UX manual.The swpackage command The swpackage command While primarily used to create depots from source files.0 (default) and 0.
show_patches displays the active patches at the SD-UX product level.X patches that are remnants from an upgrade to HP-UX 11. Determine which patches that are included in the Installed Product Database are 10. Currently available as patch PHCO_19550. which may be easier to interpret than the output of the swlist command. Display the active patches on the system. Synopsis cleanup [-n|-p] -i cleanup [-n|-p] -d <depot> Patch Related Command Line Arguments -p -n -i Preview the cleanup task but do not actually remove any patch information. Active patches are those which have not been superseded by newer patches on the system.The cleanup Command Examples • Re-package the entire contents of the depot /var/spool/sw onto the tape at /dev/rmt/0m: swpackage -s /var/spool/sw -x target_type=tape @ /dev/rmt/0m The cleanup Command The cleanup command provides functions useful when dealing with HP-UX patches. The cleanup command logs all information to /var/adm/cleanup. The utility uses the SD-UX patch attributes patch_state and superseded_by to determine which patches are active and which are superseded. These patches are removed from the IPD so that they are no longer displayed in the output of the swlist command. Notify the user of cleanup tasks and request confirmation before actually removing any patch information. but as a patch. Display the patch information at the SD-UX product or fileset level. 72 . The cleanup utility also allows patches to be committed across the entire system. Superseded patches are those that have been replaced by newer patches on the system. It is also used to remove patches from a software depot if they have been superseded by patches also available in the same depot.X. It is used to remove any patches for earlier releases from the Installed Product Database after updating to a newer version of HP-UX. The cleanup command is not delivered with HP-UX. Determine which patches in the software depot have been superseded by patches also available from the depot.log. These superseded patches will be removed from the software depot. -d The show_patches Command The show_patches utility displays active and superseded patches in a formatted output. Display the superseded patches on the system. Synopsis show_patches [-a] [-s] [-l product|fileset] Patch Related Command Line Argument: default -a -s -l level If no options are specified.
00_32 PHKL_18543.) The software_spec attribute contains the full software specification for any bundle. you usually only need to refer to a patch or bundle name.v=HP.00_32/64 PHKL_18543.11.00_32/64.0. From an interactive session. # swlist -l fileset -a software_spec PHKL_18543 # PHKL_18543 PHKL_18543. You can use the swlist command to display this information.a=HP-UX_B.00_32/64 PHKL_18543.11. Each invocation of an SD-UX command defines a session.Other Options and Aids to Using the SD-UX Commands Other Options and Aids to Using the SD-UX Commands Software Specifications When an SD-UX command can be supplied a software selection.00_32/64 Session Files Session files let you save your work from a command session.KERN2-RUN.v=vendor][.sw/sessions/.VXFS-ADV-KRN PHKL_18543.11. and target hosts are saved before command execution actually commences. source information.11.0. From a command-line session. A session file uses the same syntax as the defaults files (see "Setting Default Values for Command Options" on page 74).v=HP.v=HP.11.a=arch][.r=1.0.CORE2-KRN PHKL_18543.r=1.sw/sessions/{command}.0.a=HP-UX_B. The following example shows how swlist can create a list of the software specifications for a patch at the fileset level.fileset][.00_32/64. or patch (see "Patch Related Object Attributes" on page 56).11.r=1.r=1. For patch operations. You can specify an absolute path for a session file.fa=HP-UX_B.VXFS-BASE-KRN.00_32/64.00_32/64.version] where the version has the form: [r=revision][.fa=HP-UX_B.00_32 PHKL_18543.VXFS-ADV-KRN. all products within the bundle are also selected.11. the selection is comprised of one or more software specifications.VXFS-PRG PHKL_18543.0.c=category] (The version may also have a l=location component that applies only to installed software and refers to software installed to a location other than the default product directory.a=HP-UX_B.a=HP-UX_B.VXFS-BASE-KRN PHKL_18543.0.0.00_32/64.a=HP-UX_B.r=1.l=/.KERN2-RUN PHKL_18543.fa=HP-UX_B.11.v=HP.11.C-INC.00_32/64.l=/. you can save session information into a file at any time by selecting the Save Session or Save Session As option from the File menu. save session information by executing swinstall or swcopy with the -C session__file option.00_32/64. The software specification for the patch product appears in the output as a comment.a=HP-UX_B.v=HP PHKL_18543.product[.last. A software specification is a unique identifier for an SD-UX software object. HP-UX Patch Management 73 . The invocation options. A software specification must name either a product or a bundle.l=/.fileset]][.l=/. The software specification takes one of the following formats: product[.00_32 PHKL_18543.11.C-INC PHKL_18543.CORE-KRN.r=1.l=/.0. If you select a product. This file is overwritten on each invocation.11.00_32 PHKL_18543.l=/.VXFS-PRG.fa=HP-UX_B. You can also save session information from interactive or command-line sessions.CORE-KRN PHKL_18543. the default location for a session file is $HOME/. and filesets can be specified only within a product.CORE2-KRN.11. product.l=/.r=1. software selections. If you do not specify a directory.l=/.a=HP-UX_B.execute the command even if the session ends before proper completion.fa=HP-UX_B.11. all filesets within that product are also selected.11.00_32/64. This lets you re.version] bundle[.v=HP. If you explicitly select a bundle. Each session is saved to the file $HOME/.v=HP.r=1.v=HP.11.fa=HP-UX_B.a=HP-UX_B.fa=HP-UX_B.
Values in these option files are specified using this syntax: [command. or command line changes. Option values in /var/adm/sw/defaults file affect all users in a system. 4. specify the session file as the argument for the -S session__file option of swinstall or swcopy. Keep in mind. Setting Default Values for Command Options SD-UX commands have extensive options that alter command behavior.]option=value These rules govern the way the defaults work: 1. Because the daemon is already running.defaults is only usable as a template for copying to other option files. after changing daemon options. the daemon must be restarted for these options to be recognized.sw/defaults file. any command line options or parameters that you specify when you invoke swinstall or swcopy take precedence over the values in the session file. Likewise. all other allowable values. These values can also be overridden by specifying an options file with the -X option_file command-line option or with one or more -x option=value options directly on the command line. 5. default values. the values in the session file take precedence over values in the system defaults file. 2. however. Options in the defaults file are read as part of command initialization.sw/defaults file affect only you and not the entire system. that individual users may override these values with their own $HOME/. type: /usr/sbin/swagentd -r 74 .Other Options and Aids to Using the SD-UX Commands To re-execute a saved session from an interactive session. use the /var/adm/sw/defaults file. Option values changed on the command line affect only that activity.sw. The /usr/lib/sw/sys. These options are listed as comments that you can copy into the system defaults file (/var/adm/sw/defaults) or your personal defaults file ($HOME/.defaults file is a template that lists and explains each option. Option values in /usr/lib/sw/sys. Note that when you re-execute a session file.defaults). They can also be changed using the GUI Options Editor. To restart the daemon. Option values in your personal $HOME/. session files. Altering option values and storing them in a defaults file can help when you want the SD-UX command to behave the same way each time the command is invoked. For system-wide policy setting. To re-execute a session from a command-line. and the resulting system behavior for each. 3. Option values in a session file affect activities only for that session and revert when that session is completed. use the Recall Session option from the File menu. NOTE: Use of session files is not recommended with swremove because the session file could include software selections that you do not want included in the removal operation.
SS . HP-UX Patch Management 75 . yyyyy = a unique number Example: PHSS_14014 .an HP-UX subsystem patch name. and depot files as well as the patch product and (in HP-UX 10. Patch Description A one-line description that describes this cumulative patch. Format is: PHxx_yyyy where: PH = Patch HP-UX.network specific patches.Appendix C The Patch Text File The Patch Text File Fields Patch Name The name of the patch. xx = area patched: CO . This identifier is used for the patch shar. NE .kernel patches.all other subsystems: X11.X releases) the patch fileset.general HP-UX commands. KL . text. etc. Starbase. Creation Date The date that the patch was created.
Causes a major application to fail such that the system's operation is severely impacted. either GR or SP.hp. Critical Yes/No followed by text. Automatic Reboot? Yes/No (whether or not this patch requires a reboot after installation).external. Causes data loss or corruption. A problem is critical if it: • • • • Causes the system (OS/kernel) to fail/crash/panic. Products This field lists the product name and all product revisions to which this patch applies if it is a patch for an optional product.OS Releases The hardware platforms and HP-UX OS releases on which this patch can be installed. Hardware Platforms . If the patch is for the core operating system. Filesets This is a list of all the filesets which contain one or more files included in this patch. A patch is considered critical if it fixes a critical problem or it supersedes a patch fixing a critical problem. • SP = Special Release site-specific patches for installation at one specific customer or set of customers. Path Name The path name is the patch's storage location on the HP Electronic Support Center ftp server (ftp://us-ffs. the value in this field is N/A. and other non-GR patches. and dependency requirements. where: • GR = General Release patch should be installed on all systems meeting the OS. product.e.com).X/PHxx_yyyy 76 . Delivers a fix related to processing dates in the year 2000 and beyond. a non-core operating system product. The current choices for supported releases are: /hp-ux_patches/s700_800/11. Status This is the support status of the patch. This flags the Critical status of this patch and all superseded patches. i.The Patch Text File Fields Post Date The date that the patch was posted for general distribution.
Hardware Dependencies Specific system models to which this patch is limited. specifically what a user would experience. The what string is a way to identify the software version.o in the library /usr/conf/lib/libhp-ux. Also include methods to verify if the patch needs to be installed.a(vers.o). HP-UX Patch Management 77 . Supersedes A list of all patches replaced by this patch. both on a file basis as well as on a behavioral basis. verify that the patch is installed. the full path of the library is listed with the object module following in parentheses. Other Dependencies Any non-patch and non-hardware dependencies that may exist. Defect Description A detailed description of the defect that specifically addresses the explicit conditions which caused the problem (if known).13 $ Patch Conflicts All known patch conflicts. Patch Files The full installed path name of all files in this patch. if a patch replaces the object module vers. For example. and how to reproduce the problem (if known). SR All Service Request (SR) numbers addressed by this patch and all its predecessors.The Patch Text File Fields Symptoms The external symptoms of the problem. Patch Dependencies All patches that must be installed to insure proper operation of this patch. If the patch replaces an object module in a library.a the path listed would be /usr/conf/lib/libhp-ux. and thereby. An SR is a formal request from a customer to have a defect resolved or a feature added to HP software. what(1) Output The output from what(1) for each file or library object file listed in the Patch Files field. Example: $Revision: 1.
Installation Instructions The standard installation instructions common to all patches. Special Installation Instructions Any special instructions not included in those mentioned above.The Patch Text File Fields Equivalent Patches All equivalent patches for other hardware platforms and OS releases not including this patch. 78 . Patch Package Size The SD depot size in Kilobytes. These instructions have been included in this tutorial.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.