HP UX Patch Management Viewing depots, Choosing depot type and depot location, Swlist -l depot

Page 67

Application depot — contains patches specific to a given application. This type of depot might actually be a specific version of a periodic patch depot.

After you have identified the need that a specific depot will address, you should determine whether a directory depot or a tape directory best suits your needs. Most often, directory depots will be more useful for patch management. You must also select a location for the depot.

Choosing depot type and depot location

You should review the following considerations before creating and using depots:

Do you require the depot to be available remotely for use by SD-UX commands such as the swinstall command?

If you are creating a depot for remote access, you need a directory depot. You must place the depot on a networked system that is accessible by all of the intended users, and you must register the depot. See “Registering and unregistering directory depots” (page 71).

Will the depot be heavily used?

You should ensure that both the system and the network are capable of meeting performance needs based on the intended use. If multiple users will access the depot simultaneously, you need a directory depot.

What amount of disk space and what level of disk performance are required?

You should ensure that both the disk space and level of disk performance are capable of meeting these needs. Depots can be large, and depot operations can involve a significant amount of disk activity.

Is the availability of the depot critical?

If the answer to this question is yes, you should consider high-availability storage solutions such as disk arrays or mirroring.

Does your organization need a heightened level of security?

If the answer to this question is yes, you should give additional consideration to safeguarding the depot. Access Control Lists (ACLs) can play a role in depot security. See “Advanced topic: access control lists” (page 72). In many cases, users of depots install software from the depot as the root user. Therefore, any compromise of software in a depot could lead to a security breach.

Although overlooked at times, a well-conceived depot-naming scheme can be very helpful. This is especially true if you have multiple depots, and is even more important if multiple users will access the depots.

You should combine all the patches needed for a given purpose into a single depot.

The depot should include all products (including patches) necessary to meet the dependencies of patches in the depot.

You can help limit risk by making only the necessary changes to the depot.

You can reduce the size of a depot by removing superseded patches. See “Advanced topic: removing superseded patches from a depot” (page 76).

Viewing depots

Use the swlist command to list the registered directory or tape depots on a local or remote system. You can also use the swlist command to view the contents of a directory or tape depot. This section provides examples of how to use the swlist command to view depots.

Examples of the swlist command

To view a list of registered depots on the local system, use this command:

swlist -l depot

Viewing depots

67

Image 67
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 107 104Patch management strategies HP-UX patches and patch managementWhere to start How to get patchesShould you use standard HP-UX patch bundles? Quick start guide for patching HP-UX systemsOverview Before you beginStandard HP-UX patch bundles Acquiring and installing standard HP-UX patch bundlesAcquiring the bundles As root, run the createdepothp-ux11script Installing the bundlesSwlist Advanced topic using Dynamic Root Disk DRDAcquiring the patches Acquiring and installing individual patchesQuick start guide for patching HP-UX systems Swverify -d \* @ /tmp/somepatchdirectory/depot Installing the patchesAdvanced topic using Dynamic Root Disk DRD HP-UX software structure HP-UX patch overviewPatch-related concepts Patch identificationSoftware depots and patch depots Patch bundlesPatch state Patch statusCategory tags StateSwlist -l fileset -a state grep patchid Swlist -l product -a categorytag patchid Which patches are on a system?For example Examples of the swlist command$ swlist -l product *,c=patch $ swlist -l bundle @ somesystem $ swlist -l product *,c=manualdependenciesAncestors Ancestors and supersession$ swlist -l fileset -a ancestor PHSS29183 Swlist -a appliedpatches filesetname Supersession$ swlist -a appliedpatches Xserver.AGRM Showpatches -s Swlist -l patch -x showsupersededpatches=trueSwlist -a patchstate -x showsupersededpatches=true patchid $ swlist -l fileset -a supersedes PHSS28681HP-UX Patch Supersession Chain Patch-related attributesSee 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 Rating details HP patch rating$ swlist -l product -a categorytag PHSS30011 Critical and noncritical patchesFinding information for a specific patch Patch documentationSubset of fields in patch text file and patch details Swlist -l product -a readme patchid more Obtaining information using the ItrcPatch warnings Advanced topic the readme attributeCritical and noncritical warnings Questions to ask How to handle patch warningsAdvanced topic finding patches with warnings Considerations Backup and recoveryPatch management life cycle Patch management overviewPatch management life cycle Patch management overview Restrictive Conservative Innovative Establishing a software change management strategyOperational factor and patch management strategy matrix Recommendations for software change managementPatch management and software depots Consideration of HP patch ratingAcquiring patches for proactive patching Proactive patching strategyAdvanced topic HP-UX Software Assistant Reactive patching strategyAcquiring patches for reactive patching Advanced topic security patching strategyAdvanced topic scanning for security patches Testing the patches to be installedWhat are standard HP-UX patch bundles? Key featuresStandard HP-UX patch bundles Standard HP-UX patch bundle use and release dates Obtaining standard HP-UX patch bundlesQuick start guide for patching HP-UX systems Find individual patches Using the IT Resource CenterObtaining an Itrc user account Useful pages on the ItrcAccessing the patch database and finding an individual patch Key featuresClick the add to selected patch list button Using the IT Resource Center Check for patches with dependencies Advanced topic checking for all patch dependenciesUsing the IT Resource Center Click the add to selected patch list button Ask your peers in the forums Standard patch bundlesCustom patch bundles run a patch assessment Support information digestsSearch knowledge base Common software distributor commands for patching Using software depots for patch managementDirectory depots Depot typesTape depots Using 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 Depot/patches/11.11 Copying patches to depotsAdvanced topic HP-UX Software Assistant Registering and unregistering directory depotsCopying products with patch dependencies to depots $ swreg -u -l depot /depot/patches/2003-07periodicdepot Advanced topic access control listsExamples of registering and unregistering depots $ swreg -l depot /depot/patches/2003-07periodicdepotExamples of verifying directory depots Verifying directory depots$ swverify -d \* @ /mydepots/newdirectorydepot $ swverify -d \* @ /mydepots/PHSS30278depot Verification had errorsRemoving software from a directory depot Verification succeededExecution succeeded Advanced topic removing superseded patches from a depot $ /usr/sbin/cleanup -d /mydepots/patchdepot$ swlist -l product -d @ /mydepots/patchdepot $ swreg -u -l depot /mydepots/PHCO27780depot Installing patches from a depotRemoving a directory depot $ swlist -l product @ /mydepots/patchdepotReboots the system when required Analysis succeeded Examples of installing patches from a depotCustom patch bundles Installing products with patch dependencies from a depotAnalysis and Execution succeeded Rev Patch description Examples of listing patches and bundlesRev Bundle Description $ swlist -d @ /mydepots/temporarydepot Creating a custom bundleAnalysis succeeded Finally, remove the temporary depot For more information Using HP-UX Software Assistant for patch managementUsing 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 Components in test Image Then production Patch usage model 1 hardware/application software changeDRD 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 Create clone Patch usage model 5 proactive patchPassed? System Patch usage model 6 reactive patchAncestor GlossaryIPD SWA Index Index See also HWE Index