HP UX Patch Management manual $ swlist -l fileset -a supersedes PHSS28681

Page 28

PHSS_27875.X11-RUN-CL PHSS_28681.X11-RUN-CL,fa=HP-UX_B.11.11_32/64 PHSS_27875.X11-TCH-B-MSG PHSS_28681.X11-TCH-B-MSG,fa=HP-UX_B.11.11_32/64

You can also show the filesets that a given patch has superseded. These superseded filesets will be listed whether or not they are installed on a system. This is done by using the swlist command to list the supersedes attribute of the patch. Note that the first patch of any particular patch supersession chain does not have a supersedes attribute. In the following example, patch PHSS_28681 is shown to supersede patches PHSS_27875, PHSS_26498, and PHSS_25201. (The output has been reformatted to improve readability.)

swlist -llevel -aattributepatch_id

For example:

$ swlist -l fileset -a supersedes PHSS_28681

#Initializing...

#Contacting target "some_system"...

#Target: some_system:/

#

# PHSS_28681

PHSS_28681.X11-JPN-S-MSG PHSS_27875.X11-JPN-S-MSG,fr=* PHSS_26498.X11-JPN-S-MSG,fr=* PHSS_28681.X11-RUN-CL PHSS_27875.X11-RUN-CL,fr=* PHSS_26498.X11-RUN-CL,fr=* PHSS_25201.X11-RUN-CL,fr=* PHSS_28681.X11-TCH-B-MSG PHSS_27875.X11-TCH-B-MSG,fr=* PHSS_26498.X11-TCH-B-MSG,fr=*

Advanced topic: supersession and the patch_state attribute

When a superseding patch is applied to a system, the superseded patch (if there was one) remains on the system but is not active. Only the top patch of the chain is in the active (applied) state. For more information about patch state, see “Patch state” (page 19).

You can use the following swlist command to show the patch_state attribute for patch patch_id:

swlist -a patch_state -x show_superseded_patches=true patch_id

It is important to note that the availability of a newer, superseding patch does not preclude the use of the older patch. Depending on the circumstances, a superseded patch might be a better choice than the patch superseding it. Older patches have had more exposure to varied, real-world use. When they have been shown to induce no ill effects, they are generally safer than newer patches that supersede them. Thus, if two patches in a supersession chain solve the problem you are facing, you might find that the older patch is the better choice.

Because HP-UX patches are cumulative, a superseding patch negates the need for the previous patch. As an example, patch PHSS_29377 delivers all the features and fixes of all other patches shown in Figure 3-2:“HP-UX Patch Supersession Chain” (page 29). This patch will also satisfy any dependencies on all patches in the supersession chain.

SD-UX does not allow you to install a patch that has been superseded by another patch already installed on a system. Using Figure 3-2:“HP-UX Patch Supersession Chain” (page 29) as an example, if you have patch PHSS_29377 installed on a system SD-UX will not allow you to install patch PHSS_29323.

Patch supersession chains can be more complex than the one shown in Figure 3-2:“HP-UX Patch Supersession Chain” (page 29).

28 HP-UX patch overview

Image 28
Contents Patch Management User Guide for HP-UX 11.x Systems Revision history Table of Contents What are standard HP-UX patch bundles? Using Dynamic Root Disk for patch management 104 107HP-UX patches and patch management Patch management strategiesHow to get patches Where to startQuick start guide for patching HP-UX systems OverviewBefore you begin Should you use standard HP-UX patch bundles?Standard HP-UX patch bundles Acquiring and installing standard HP-UX patch bundlesAcquiring the bundles Installing the bundles As root, run the createdepothp-ux11scriptAdvanced topic using Dynamic Root Disk DRD SwlistAcquiring and installing individual patches Acquiring the patchesQuick start guide for patching HP-UX systems Installing the patches Swverify -d \* @ /tmp/somepatchdirectory/depotAdvanced topic using Dynamic Root Disk DRD HP-UX patch overview Patch-related conceptsPatch identification HP-UX software structurePatch bundles Software depots and patch depotsPatch status Patch stateCategory tags StateSwlist -l fileset -a state grep patchid Which patches are on a system? Swlist -l product -a categorytag patchidExamples of the swlist command For example$ swlist -l product *,c=patch $ swlist -l product *,c=manualdependencies $ swlist -l bundle @ somesystemAncestors Ancestors and supersession$ swlist -l fileset -a ancestor PHSS29183 Swlist -a appliedpatches filesetname Supersession$ swlist -a appliedpatches Xserver.AGRM Swlist -l patch -x showsupersededpatches=true Showpatches -s$ swlist -l fileset -a supersedes PHSS28681 Swlist -a patchstate -x showsupersededpatches=true patchidPatch-related attributes HP-UX Patch Supersession ChainSee Category tags Types of dependencies Patch dependenciesCorequisites and prerequisites Impact of dependencies on acquiring patches Enforced and unenforced manual dependenciesSwlist -vl fileset -a dependencytype fileset Patch rollback Patch rollback and commitmentPatch commitment Cleanup -p -c number Advanced topic patch cleanup utilityHP-UX patch ratings HP patch rating Rating detailsCritical and noncritical patches Finding information for a specific patchPatch documentation $ swlist -l product -a categorytag PHSS30011Subset of fields in patch text file and patch details Obtaining information using the Itrc Patch warningsAdvanced topic the readme attribute Swlist -l product -a readme patchid moreCritical and noncritical warnings Questions to ask How to handle patch warningsAdvanced topic finding patches with warnings Backup and recovery ConsiderationsPatch management overview Patch management life cyclePatch management life cycle Patch management overview Establishing a software change management strategy Restrictive Conservative InnovativeRecommendations for software change management Operational factor and patch management strategy matrixConsideration of HP patch rating Patch management and software depotsProactive patching strategy Acquiring patches for proactive patchingReactive patching strategy Advanced topic HP-UX Software AssistantAdvanced topic security patching strategy Acquiring patches for reactive patchingTesting the patches to be installed Advanced topic scanning for security patchesWhat are standard HP-UX patch bundles? Key featuresStandard HP-UX patch bundles Obtaining standard HP-UX patch bundles Standard HP-UX patch bundle use and release datesQuick start guide for patching HP-UX systems Using the IT Resource Center Obtaining an Itrc user accountUseful pages on the Itrc Find individual patchesKey features Accessing the patch database and finding an individual patchClick the add to selected patch list button Using the IT Resource Center Advanced topic checking for all patch dependencies Check for patches with dependenciesUsing the IT Resource Center Click the add to selected patch list button Standard patch bundles Custom patch bundles run a patch assessmentSupport information digests Ask your peers in the forumsSearch knowledge base Using software depots for patch management Common software distributor commands for patchingDepot types Directory depotsUsing depots Tape depotsChoosing depot type and depot location Viewing depotsSwlist -l depot Swlist -l depot @ remotesystem $ swlist -l depot$ swlist -l depot @ swdepot.xyz.com Creating and adding to a directory depot Copying patches to depots Depot/patches/11.11Advanced topic HP-UX Software Assistant Registering and unregistering directory depotsCopying products with patch dependencies to depots Advanced topic access control lists Examples of registering and unregistering depots$ swreg -l depot /depot/patches/2003-07periodicdepot $ swreg -u -l depot /depot/patches/2003-07periodicdepotExamples of verifying directory depots Verifying directory depots$ swverify -d \* @ /mydepots/newdirectorydepot Verification had errors Removing software from a directory depotVerification succeeded $ swverify -d \* @ /mydepots/PHSS30278depotExecution succeeded Advanced topic removing superseded patches from a depot $ /usr/sbin/cleanup -d /mydepots/patchdepot$ swlist -l product -d @ /mydepots/patchdepot Installing patches from a depot Removing a directory depot$ swlist -l product @ /mydepots/patchdepot $ swreg -u -l depot /mydepots/PHCO27780depotReboots the system when required Examples of installing patches from a depot Analysis succeededCustom patch bundles Installing products with patch dependencies from a depotAnalysis and Execution succeeded Rev Patch description Examples of listing patches and bundlesRev Bundle Description Creating a custom bundle $ swlist -d @ /mydepots/temporarydepotAnalysis succeeded Finally, remove the temporary depot Using HP-UX Software Assistant for patch management For more informationUsing Dynamic Root Disk for patch management Drd1m Patch Assessment Tool Using the Patch Assessment ToolBenefits of the Patch Assessment Tool Example of running the Patch Assessment Tool Select upload new system information Contacting HP Support and other resourcesRelated information HP websites Typographic conventionsNon-HP websites Times Patch usage models Patch usage model 1 hardware/application software change Components in test Image Then productionDRD Begi n Product needs to be certified on HP-UX 11i v2/v3 Patch usage model 3 operating environment cold install Patch usage model 3 operating environment cold install Patch usage model 4 operating environment update Patch usage model 4 operating environment update Patch usage model 5 proactive patch Create clonePatch usage model 6 reactive patch Passed? SystemGlossary AncestorIPD SWA Index Index See also HWE Index