Chapter 2 Managing Solaris Software Updates
Sun Update Connection – Enterprise offers new features for Solaris update management. This chapter
covers the following topics:
Overriding Sun Recommendations
The default behavior of Sun Update Connection – Enterprise is to deploy Solaris updates according to Sun
recommendations. Deploying updates through Sun Update Connection – Enterprise could necessitate numerous restarts, restart and reconfigure,
or manual deployments during the process of the job.
You have the option to override the recommendations to restart, restart and reconfigure,
or deploy manually, during a job. You can set Sun Update Connection – Enterprise to ignore these recommendations
and force the job to finish deployments before you restart (or otherwise manually
apply the update management).
Caution –
It is not recommended that
you override the default update deploy and apply actions set up by Sun. If you follow this procedure,
realize that you take responsibility for the results.
Overriding Sun Update Policy Recommendations
You override specific recommendations for each Solaris host in the Preferences window,
in the Update Policy
category. If your Host Preferences do not include Update Policy on the left side, contact technical
support.
Note –
When you select a host in the Preferences window, you have the
option to select from any of the managed hosts in the system. However, this procedure
is relevant only for Solaris hosts.
To Override Sun Update Policy Recommendations
-
Open the Preferences window.
You
can open the preferences window using one of the following options:
-
From the tool bar, click the Preferences button.
-
From the Tools menu, choose Preferences.
-
Select a single Solaris host, then click OK.
Wait
while the Preference values of the selected agent are uploaded to the console.
Note –
Preference values can be uploaded only if the agent is not busy with
another command.
-
In the Preferences window left-panel, click Update Policy.
-
If you want to set the override preferences for multiple hosts,
click Select target hosts and then select the hosts.
-
Select the check boxes of the Sun recommendations that you want
to override:
-
To deploy an update that has a recommendation for manual intervention,
select Auto Deploy to deploy updates automatically in the job.
-
To deploy one or more updates that recommend that the host be
restarted after the update is deployed, select the Override Restart option
of the specific notification. By selecting the Override Restart option, you
can complete all deployments before restarting the host. To apply the updates,
restart the host after all updates are deployed.
Note –
If an update requires reconfiguration or single-user deployment,
perform the necessary management tasks after the job has been completed.
-
Click Submit.
The Preferences Confirmation window
opens.
-
Check that the changes are appropriate, select the Restart Agent check box, then click
Submit.
Handling Jobs With Override Settings
After you turn on the overrides, the next update management job that
you run in Sun Update Connection – Enterprise on the affected hosts will use the override settings.
Note that the overrides do not affect the Restart or Restart and Reconfigure profiles; they
affect only the Sun update management
recommendations.
While the job is running, you can monitor the progress of the update deployments. Notice
that the restart and manual
intervention actions are listed in the Host Progress window, and that they
are marked as successfully done, although your overrides ensure that these
actions are not actually done.
To Monitor an Update Management Job
-
To view the Jobs list, select View, then select Jobs.
-
From the Jobs list, select an update management job.
The
tasks of the job appear in the Tasks list.
-
From the Tasks list, select a task.
The hosts running
this task appear in the Hosts list of the Jobs panel.
-
Select a Solaris host.
-
From the Jobs menu, choose Hosts, then choose Show Progress.
The Host Progress window opens.
-
The
To Do list might include Performing <action> items, such as Performing Restart, or Performing Restart and Reconfigure.
These items are
marked with a green check, but they are not actually done.
You
might see Attention! <action>, with an action that you
would normally have to perform before the job continues. With the relevant override
turned on, these items are
also marked with a green check and the job continues.
At the end
of the job, be sure that you complete the actions that are required for
each update.
To View the Job Log
From the Jobs
menu, choose Hosts,
then choose Show Log.
The Job Log window opens.
The Job Log shows the status
of both complete and incomplete deployment updates. It shows the actions
that should have been done, according to the Sun recommendations, as well as actions that were not done. For
example, if an action was not done, you might see the following message: Overridden by User Request.
When the update management is done, be sure to do the appropriate actions.
Caution –
Remember that the overrides are set by agent, not by job. If you
want another job to run according to Sun recommendations (restarting and otherwise
managing the host in the midst of a job), deselect the Update Policy preferences.
Supporting Solaris Update Clusters
Sun publishes Update Clusters, which are bundles of updates, provided for a single installation.
Without Sun Update Connection – Enterprise, most UNIX administrators plan for downtime to install Update Clusters, because some of the updates require single-user
mode. Some administrators research the contents of a cluster, and install only those updates that are not already
installed.
With Sun Update Connection – Enterprise, you can install Update Clusters while the hosts are still
up, and you can let Sun Update Connection – Enterprise do the research and decide what needs to be installed.
The previous
section
explained how to set overrides to Sun recommendations for restarting, which includes
single-user installations and reconfigurations. In general, do not
use the overrides unless you are prepared to take responsibility for the results. However,
when deploying Update Clusters, the most efficient method is to turn on all of the overrides.
Sun releases Update Clusters, as required,
to add updates to the cluster. Theconsole includes a Clusters category, which contains the latest Update Clusters.
You can create a profile which deploys the relevant Update Clusters and checks
them for new updates on a schedule. See the Sun Update Connection – Enterprise 1.0 User's Guide for
instructions on creating profiles and on scheduling profiles.
If you schedule a profile for the installation of an Update Cluster, the deployment
is not actually done unless it is needed. Sun Update Connection – Enterprise determines if the selected
hosts already have the most recent
cluster updates. If so, the profile job ends successfully, with nothing done.
If one or more updates are
added to the cluster, Sun Update Connection – Enterprise installs them on your hosts. All of this takes
place in the background
with no down-time.
Withdrawn Updates in Clusters
When Sun publishes an Update Cluster on http://www.sun.com, only the latest version is published. This
is the recommended cluster to install.
If a job to install an updatecluster is marked as failed, the job might include a withdrawn
update. To troubleshoot the job, determine if the cluster includes updates that Sun withdrew.
Withdrawn updates cannot be maintained by Sun Update Connection – Enterprise, because they are not maintained by Sun. If a cluster includes a
withdrawn update, the cluster
cannot be installed.
In some cases,
an update is withdrawn just minutes after a cluster is published.
For this reason, check the cluster for withdrawn updates before attempting
to install the cluster.
If the
latest cluster published by Sun has a withdrawn update, wait for the next
publication.
To Check a Cluster for Withdrawn Updates
Before You Begin
Ensure that the Inventory panel of the main window is available by selecting View, then selecting Inventory.
-
From the Components list, right-click a cluster and choose Details.
The Details window opens.
-
Open the Rules tab and expand the list of updates of the cluster.
If even one of the updates is marked with WITHDRAWN, the cluster cannot be installed.
Dieses Buch im PDF-Format herunterladen (632 KB)