Opsware Instructions for patching in Solaris:
Quarterly Release Schedule:
The quarterly schedule for the bundles has been defined as:
February 15
May 15
August 15
November 15
Quarterly Release Information:
The HP ES Server Automation team will release the following information on a quarterly basis:
Synopsis files listing and describing each patch contained in the patch bundle for each supported
platform
Any special instructions necessary to patch servers for that quarter for each supported platform
PCAmetadata location: /var/opt/PCAmetadata check for the latest metadata available on the server
To install the quarterly PCA metadata:
A new feature of the PCAtool solution is the advent of quarterly PCA metadata patch policies. These
policies will have to be installed - the analysis phase will no longer download and extract the quarterly
metadata for you. It will simply analyze the server with the already installed metadata from this step.
However, the fact that this metadata will be an installed software policy on your server means you and
your clients will have much better line of sight as to which servers have applied which quarterly
metadata which will lead to better auditing and reporting of solaris quarterly patch application. Always
install only the latest version of the metadata. These versions contain fixes to previously released
metadata.
1. Login to the SAS Java Client ([Link]
2. Select the Library tree on the left pane and then select the By Folder tab
3. Browse to Unix System Admin/Software Policies/HP Enterprise Services
4. At this point you wil need to select the quarterly PCA metadata policy you want to install. PCA
metadata policies will always be named with this format: PCA metadata <quarter>-<version>-SunOS
(An example is PCA metadata 3q2009-v1-SunOS)
5. Right-click on the policy you want to install, select Open and then select Server Usage - you will now
see a list of all servers that have this poilcy attached
6. On the top of the screen select Action and then Attach Server
7. Click on All Managed Servers and then browse for the server(s) on to which you want to install the
new patchtool policy
8. Select the server(s) (using the ctrl key to select multiple servers)
9. Make sure the "Remediate servers immediately" box is checked and click on Attach
10. Click Yes to the save changes prompt and then Select Next followed by Continuous - Run all phases
as an uninterrupted operation (the default)
11. Select Suppress all reboots
12. Select either Run immediately or schedule the install to occur in the future
13. Add any email notifcations as needed and then select Next
14. Select Preview if you would like to run a preview of the installation else just Start Job
15. Click the plus sign to the left of the server name if you would like to view status of each phase of the
installation
16. Click on the output and error tabs to see installation and error output respectively
17. When the job has completed, select Close
Opsware patching instruction in GUI mode – follow the below link
[Link]
Opsware patching instruction in CLI mode:
Quick view for analyzing, staging & installation
Analysing - /opt/PCAtool/bin/patchtool -a -d /var/tmp/patchtool
Staging - /opt/PCAtool/bin/patchtool -s -d /var/tmp/patchtool
Installation - /opt/PCAtool/bin/patchtool -il -d /var/tmp/patchtool
Clearing earlier staged patches - /opt/PCAtool/bin/patchtool –c
Note: The PCATool should normally be run from the OCC via the Solaris Patch Wizard (PCA) Custom
Extension, using the instructions in this document. However, it may also be run on the server itself. See
the “CLI Instructions” section in each step of this document for more information.
Usage: patchtool { -a | -s | -i | -c | -p } [ -d staging_directory ] [ -b list of patches ] [ -R alternate root path
] [-l] [-f] [-h]
-a analyze system and determine which patches should be installed.
-s stage (download) patches from Opsware Software Repository to
staging_directory.
-i install previously staged patches.
-c cleanup (remove) local data (patches in staging_directory,
cached meta-data directory, persistent local values).
-p progressive. like -sic, except that patches are staged,
installed, and removed from the staging directory one at
a time. generally useful only when there is not sufficient
disk space to stage all the patches before installing.
-l store/retrieve persistent values locally only.
-d <staging_directory>
specify staging directory. value is set persistently when
used with -a. option is ignored in all other phases (the
stored persistent value is used instead.)
-b <list of patches>
backout comma or blank separated list of patches. If “all” is specified backout all patches listed in
the
patchtool_patch_order custom attribute in inverse order
-R <alternate root path> specify an alternate root path under which to apply the patches.
-f force. override diskspace check during patch application.
*** patches will be applied without saving backout data. ***
-h this help.
Options may be combined and will do what you expect (hopefully).
Examples:
-as will analyze and stage. -s by itself will just stage, but will
fail is a previous analysis has not been done. -s will skip over
patches that have already been staged.
-asi will analyzie, stage, and install. -i by itself will fail
if the patches have not been staged. -si will fail if a previous
analysis has not been done, etc.
-ic will install and cleanup patches as they are succesfully
installed. -c by itself will cleanup all patches and local values
regardless of whether any patches have installed succesfully.
-I -R /a will install patches but under the alternate root mounted path of /a
-asic will do everything in one shot.
-ap will analyze and then per-patch progressively stage, install
and clean each patch as described under the -p option.
Persistent values are stored both as device custom attributes and
locally unless -l is used. If the Opsware core cannot be reached,
the script will terminate, unless -l is used. Obviously patches
cannot be staged if the core is not reachable, so using -l with
-s causes undefined behavior.
Persistent values are stored locally under:
/var/opt/PCAtool/params
Where To Go For Opsware Support
Central Opsware Support Team (24x7 Support):
Telephone:
Toll-free: 866-319-1568
International: +55 11 4196 0387
International Dialing Instructions
[Link]
