The Issue report is included in the HTML report. There
is a section for every analyzer selected, plus an Automatically invoked analyzers section if there
are AUTO issues detected.
The Issue report includes issues SWA does not have recommendations
for (unresolved issues), but does not indicate they are unresolved.
Information on unresolved issues can be found in the Detail report.
Select the Issue report for display to standard output with
the -r issue option to the swa report command or the swa step report command.
Latest Quality Pack Bundle (QPK) |
 |
The Quality Pack analyzer detects
the revision of the current QPK bundle and selects available updates.
If patches in a recommended QPK have warnings, they will
be listed explicitly in the QPK section of the Issue report, as shown
in the following example. When available, the patches that fix these
warnings will be included in the list of actions recommended by SWA.
| 1 | The Quality Pack bundle QPKBASE includes patches with warnings. |
Security Bulletins (SEC) |
|
SWA lists all detected security
bulletins that might apply to your system.
It is possible for more security bulletins to be listed here
than in the Action report, since this list includes bulletins satisfied
by patch and manual actions; the Action report only lists the security
bulletins satisfied by manual actions.
The following example illustrates that although an issue might
generate multiple actions, such as the Security Bulletin 02284r4,
it is listed once in the Issue report. Below, the various identifiers
appearing in the report are explained.
| 1 | The Security Bulletin 02284r4 generates four actions in the
Action report, and a single issue in the Issue report. |
A security bulletin usually has a number of identifiers associated
with it.
The following example explains the identifiers associated with
security bulletin 02284r4.
| 1 | The short form of the external HP security identifier. It is
comprised of the numeric portion of the HPSBUX identifier, 02284, plus the revision number, r4. |
| 2 | The long form of the external HP security identifier, also called
the HPSBUX identifier. |
| 3 | The software security response team number, which is used internally
to HP. |
| 4 | The revision number. A security bulletin revision can be issued
for minor or significant changes. |
|
| |
|
 | NOTE: The Common Vulnerabilities and Exposures (CVE) identifier, if
there is one associated with the bulletin, is available with the detailed
information on the ITRC. Follow the hyperlink in the HTML report to
access this information. |
|
| |
|
Patches that Fix Critical Issues (CRIT) |
|
Problems are categorized as critical
based on the severity of the problem, not how likely the problem might
occur. Critical problems include system panics or hangs, process failures,
data corruption, severe performance degradation, and application-specific
critical issues.
If there is a newer patch in the supersession chain, that patch
might be listed in the Action report, not the patch listed as missing
in this section.
Patches with Warnings (PW) |
|
This section reports patches with warnings
identified by the PW orPCW analyzer. If a newer recommendable patch exists,
it will be selected. Note that in some instances the best course of
action is to retain a patch with a warning.
| 1 | This is the posting date of the most recent patch warning. |
| 2 | Patches with critical warnings are identified here. |
Specific Patch (PATCH) and Patch or Recommended Successor (CHAIN) |
|
Given a user-specified
list, the PATCH and CHAIN analyzers identify user-specified patches
that can be installed. Patches are omitted from the list because the
base product is not present or because the patch or its replacement
is already installed. In an Issue report, these two analyzers are
equivalent; they differ in the recommendations made within the SWA
Action report.
Automatically Invoked Analyzers |
|
You might have a section for Automatically invoked analyzers (AUTO)
in your report, which is an analyzer SWA always runs and cannot be
deselected. Problems in this category include missing dependent patches
and unrecognized patches. An unidentified patch can be a sign of a
special release or site-specific patch. An out-of-date catalog file
might also cause unidentified patches.
| 1 | The Patch PHKL_31500 is a special
patch for HP-UX 11i v2, in that new dependencies may be introduced
after its release. |
Printable version
