HP Server Automation 9.02 Release Notes

for the HP-UX, IBM AIX, Red Hat Enterprise Linux, Solaris,
SUSE Linux Enterprise Server, VMware, and

Windows® operating systems


Software version: 9.02

Original Publication Date: November 2010

This document is an overview of the changes made to Server Automation.
It contains important information that is not included in books or Help.

Table of Contents

You can find information about the following in this document:

What's New in This Release?

Installation

Known Issues

Fixed Issues

Documentation Errata

HP Software Support

Legal Notices

What's New In this Release?

Server Automation release notes contain information for Server Automation, Storage
Visibility and Automation, SE Connector, Application Deployment Manager,
DMA integration, and other changes.

Fixed and Known Issues

Critical fixes and known issues each have their own tables: see Fixed Issues and
Known Issues. Within those tables, defects are conveniently listed alphabetically by
subsystem, and then numerically under each subsystem.

Supported Operating Systems and Platforms

For a list of supported operating systems and platforms for Server Automation Cores,
Agents, clients, and Satellites, see the Server Automation Support and Compatibility Matrix .

For a list of supported operating systems and platforms for Storage Visibility and
Automation Managed Servers, SE Connector, SAN Arrays, Fibre Channel Adapters,
SAN Switches, File System Software, Database Support, and Storage Essentials Compatibility,
see the Storage Visibility and Automation Support and Compatibility Matrix .

To check for updates to these documents, go to:
http://support.openview.hp.com/selfsolve/manuals

The HP Software Product Manuals site requires that you register for an HP Passport and sign in.
To register for an HP Passport, select the New users - please register link on the HP Passport
login page.

Application Deployment Manager

Application Deployment Manager benefits from two significant changes in HP SA 9.02. First,
Application Deployment Manager now integrates with HP Database and Middleware Automation
(DMA – formerly Stratavia Data Palette) through the DMA Flow Component. Second, application
definition has been greatly simplified with the introduction of a deployment debugger.

DMA Flow Component

Starting with SA 9.02, the new “DMA Flow Component” allows developers to leverage the vast
middleware capabilities of DMA to ensure the middleware requirements of their applications are
satisfied. For more information about DMA, see the DMA 1.0 User Guide. For more information
on configuring SA to use DMA, see the HP SA Integration Guide. For more information on DMA
Flow Components, see the Application Deployment Manager User Guide.

Deployment Debugger

The deployment debugger introduced in SA 9.02 allows developers to selectively execute
(or skip) components, include (or exclude) servers, step incrementally through deployments, set
breakpoints and pause on deployment failure. The ability to pause on failure allows developers to
investigate managed server state before rollback restores the systems to their last good state.
The fine-grained deployment job control allows developers to focus on problematic components
and more quickly produce a stable application version for release into production.

Approving Blocked Jobs

Approving Blocked Jobs that Run SA Extensions

Job Approval Integration in SA allows you to block certain SA jobs from running until they
are verified and unblocked. The typical method of unblocking these blocked jobs is by using
HP Operations Orchestration (OO). SA provides a way to unblock jobs that run program
APXs (Automation Platform Extensions) without requiring HP Operations Orchestration.
For more information on Job Approval Integration, see the SA Platform Developer's Guide.

In releases prior to SA 9.02, the only way to unblock blocked jobs was by calling an OO flow.
The OO flow performed the appropriate checks and unblocked the job, allowing it to run.
SA 9.02 added the ability to verify and unblock jobs that run program APXs without requiring
HP Operations Orchestration.

NOTE: This applies only to "Run Program Extension" jobs, which are jobs that run a program APX.
APXs are extensions to SA. For more information on APXs, see "Creating Automation
Platform Extensions (APX)" in the SA Platform Developer's Guide.


With SA 9.02, you can create a specifically named program APX that will run without
blocking. This allows you to write a program APX that can unblock other APX jobs, without
the control APX itself being blocked. To specify an APX to unblock jobs, set the following
system configuration parameters in the SA Web Client.

Table 1 - System Configuration Parameters for an APX to Unblock Jobs

System Configuration Parameter

Script Running Order

approval_integration.apx.enabled

0 (default) disables the ability to unblock jobs
with an APX.
1 enables unblocking jobs with an APX.

 

approval_integration.apx.uniquename

Specifies the name of the program APX that willhandle blocked jobs.

Enabling Job Approval for APXs

You must have the appropriate permissions to make changes to System Configuration
parameters. For more information on permissions, see the SA Administration Guide.

To create this type of APX, perform the following steps:

  1. Write a program APX that checks the blocked jobs and unblocks them using the SA API
    methods approveBlockedJob(), updateBlockedJob(), cancelScheduledJob() and
    findJobRefs(). These methods are the callbacks into SA that enable job approval
    integration. For details on writing APXs see "Creating Automation Platform Extensions
    (APX)" in the SA Platform Developer's Guide.

  2. Log in to the SAS Web Client. For more information on the SAS Web Client, see the SA
    User's Guide: Server Automation
    .

  3. In the navigation pane, select Administration System Configuration. This displays the
    subcomponents of the SA platform.

  4. Under "Select a Product:", select Opsware. This displays the system configurations you
    can modify.

  5. Locate the entry for approval_integration.apx.enabled.

  6. Under the Value column, select the "Use value" button.

  7. In the text box next to the "Use value" button, enter a 1.

  8. Locate the entry for approval_integration.apx.uniquename.

  9. Under the Value column, select the "Use value" button.

  10. In the text box next to the "Use value" button, enter the unique name of your program
    APX that checks and unblocks blocked jobs.

  11. Select the Save button at the bottom of the page.

  12. Set up a mechanism to run this APX. For example, you could schedule this APX to run
    periodically to check for blocked APXs.

Disabling Job Approval for APXs

You must have the appropriate permissions to make changes to System Configuration
parameters. For more information on permissions, see the SA Administration Guide.

To disable the unblocking APX, set the value of approval_integration.apx.enabled to 0.
For details on setting this system configuration value, see Enabling Job Approval for APXs.

 

RPM Folders

Restricting Access to RPM Folders

Starting in SA 9.02, you can ensure that your Linux managed servers only have access
to the set of RPMs in the SA Library that apply to each server. You simply specify in a
custom attribute the folders in the SA Library that the server has access to. All other
folders will be inaccessible to the server. This section describes how to set up these
restrictions.

With this new mechanism, you can mimic the common RedHat systems administration
paradigm of having multiple, distinct yum (Yellowdog Updater, Modified) repositories. This
gives you folder-level control over which versions of RPMs can be applied to a given server,
allowing you to precisely manage platform update versions, for example Red Hat Enterprise
Linux Advanced Platform Version 4 Update 5 versus Update 6.

This is not intended as a user-level access control mechanism, but rather to restrict the
library and folder view of a managed server from access to the full set of RPMs in the SA
Library. For information on user level folder access controls and folder permissions in the SA
Library, see the SA Administration Guide.

How the RPM Folder Restrictions Work

During remediation, if a server has one or more of these custom attributes defined, SA reads
the custom attribute values and only allows the managed server access to the RPMs in the SA
Library folders specified in the custom attributes and their subfolders. Subfolders of all the
specified folders are recursively searched for RPMs. All other folders are not accessible to the
server.


Enabling RPM Folder Restrictions

To restrict a server or group of servers to a subset of RPMs in the SA Library, set a custom
attribute in the format described below on your managed server or at a location that will be
inherited by the server such as a device group, a software policy, a customer, a facility and so
forth.

These custom attributes follow the custom attribute inheritance rules. For example, if you set
a custom attribute at the facility level, the servers in that facility will inherit the custom
attributes.

SA does not validate the SA Library folder paths you specify in these custom attributes so
make sure the folder paths you specify are correct.

For more information about custom attributes, see the SA User's Guide: Application
Automation
.

Custom Attribute Format

The custom attributes that restrict access to RPMs must be in the following format:

repo.restrict.<name>

Where <name> is any user-defined alphanumeric string.
Specify a name that is descriptive and helps you remember the purpose of the
custom attribute. You can define multiple custom attributes as long as each
name is unique.

Examples:

The following defines custom attributes that grant access only to the SA
Library directories:

/Redhat/AS4/en/x86_64/U5 and /Oracle/10/AS4/x86_64:

repo.restrict.as4u5=/Redhat/AS4/en/x86_64/U5
repo.restrict.oracle_updates=/Oracle/10/AS4/x86_64

The custom attribute value can be multiple lines. The following defines custom
attributes that grant access only to the SA Library directories listed:

repo.restrict.as4u5=/Redhat/AS4/en/x86_64/U5 /Redhat/AS4/en/x86_64/U5-extras
repo.restrict.s5u3=/Redhat/5Server/en/x86_64/U3
/Redhat/5Server/en/x86_64/U3-extras
/Redhat/5Server/en/x86_64/U3-VT
/Redhat/5Server/en/x86_64/U3-Cluster

Sun Solaris Moves to Oracle

As of the 9.02 release, Oracle and Sun were in the process of
retiring the SunSolve web site and establishing a new Oracle support web site
for Solaris patches and patch information. Once this transition is complete,
HP will provide information about how to modify your solpatch_import.conf
file to ensure that Solaris patching with SA continues to work correctly.
This information will be posted on the standard HP support channels.
For more information on Solaris patching and the solpatch_import.conf file,
see the SA User Guide: Application Automation.

Back to the Table of Contents

Installation

This section describes the SA 9.02 installation procedure.

As with previous SA releases, all SA Core installations and upgrades must be performed
by HP Professional Services or HP-certified consultants. SA Satellite installations and
upgrades performed by customers continue to be supported.

General Information

Script Running Order

The pre-patch, database update and patch install scripts must be run in the following order:

Table 2 - SA Script Running Order - Upgrade

Upgrade From

To

Script Running Order

9.0

9.02

  1. patch_database.sh
  2. patch_opsware.sh
  3. patch_contents.sh

9.01

9.02

  1. patch_opsware.sh
  2. patch_contents.sh

Table 3 - SA Script Running Order - Rollback

Rollback From

To

Script Running Order

9.02

9.0

  1. patch_opsware.sh
  2. patch_database.sh

 

 

Database Schema Update Procedure

Required only if you have not previously applied the SA 9.01 patch. The script run
during this procedure makes required changes to the Model Repository including adding
required tables and objects. Perform the following tasks to install database updates:

  1. Before running the patch install script, perform steps below to ensure that the script
    20_truth_modify_truth_stats_job_90.sh is run during patch installation.

    This script modifies the TRUTH database users dba_job that collects schema statistics.

    Note: This is an optional script that fixes issues described in QCR1D: 93757.
    This script is run by the patch install script, patch_database.sh , only when
    you have made the following changes.

    1. Create the file:

      /var/opt/opsware/OPSWpatch_sql/optional_updates.conf

      on the server on which you will run the patch install script, patch_database.sh .
    2. Edit optional_updates.conf and add this entry:

      truth_modify_truth_stats_job=1

      When you run the patch install script patch_database.sh , it checks for the
      existence of optional_updates.conf, and if the file exists and contains the entry
      specified in step b, it runs the script 20_truth_modify_truth_stats_job_90.sh
      which then modifies the dba_job that collects schema statistics.

      If optional_updates.conf is not found, or if the
      truth_modify_truth_stats_job=1 entry is not found in the file, then the script
      20_truth_modify_truth_stats_job_90.sh will not be run.
  2. Mount the SA 9.02 distribution. Invoke patch_database.sh on the Model Repository host:

    1. <distro>/opsware_installer/patch_database.sh --verbose -r <response file>

      Where <response file> is the response file last used to install/upgrade the system.

      Usage: patch_database.sh [--verbose] -r <response file>

      patch_database.sh automatically detects if a database update is already
      installed and presents a corresponding menu:

    2. If the database update has not been previously applied, you see
      the following:
      Welcome to the Opsware Installer.
      It appears that you do not have a database update
      installed on this system.
      Press 'i' to proceed with patch installation.
      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: i
    3. Enter i at the prompt to begin the database update.
    4. If the database update has previously been applied, you see
      the following:

      Welcome to the Opsware Installer.
      It appears that you have installed or attempted
      to install a previous version of the database
      update on this system.
      Press 'u' to upgrade the patch to the current version.
      Press 'r' to remove this patch.
      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: u
      You chose to upgrade the patch. Continue? [y/n]: y

      Enter u at the prompt then Y to begin the database update.

  3. After you make your selection, the installer completes the new (or interrupted) installation.
    On completion, you see a screen similar to the following:

    [timestamp] Done with component Opsware SQL patches.

    [timestamp] ########################################################

    [timestamp] Opsware Installer ran successfully.

    [timestamp] ########################################################

Note: After running the patch_database.sh script, you may see the following error when running
the System Diagnostic test on your core:

Test Name: Model Repository Schema
Description: Verifies that the Data Access Engine's version of the schema matches
the Model Repository's version.
Component device: Data Access Engine (spin)
Test Results: The following tables differ between the Data Access Engine and the
Model Repository: local_data_centers, role_class_bridge.


This error is invalid and you can disregard it.

Patch Installation Procedure

Note: Before performing the tasks in this section ensure that you have completed the
tasks listed in Database Schema Update Procedure.

Perform the following tasks to install SA 9.02:

  1. Mount the SA 9.02 distribution. Invoke patch_opsware.sh on every host in the
    core/satellite facility:

    <distro>/opsware_installer/patch_opsware.sh --verbose

    Usage : patch_opsware.sh [--verbose]

    patch_opsware.sh automatically detects whether or not there is a patch
    already installed and presents a corresponding menu:

    1. Non-upgraded System : If your system has not been upgraded,
      you see the following menu:
      Welcome to the Opsware Installer. It appears that
      you do not have any patches installed on this system.
      Press 'i' to proceed with patch installation.
      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: i

      Enter i at the prompt to begin the installation.

    2. Previously Upgraded System : If an SA patch has already been installed
      successfully, when patch_opsware.sh is invoked from a newer patch
      release, you see the following menu:
      Welcome to the Opsware Installer. It appears that you have
      installed or attempted to install a previous version of
      the patch on this system.
      Press 'u' to upgrade the patch to the current version.
      Press 'r' to remove this patch.

      Press 's' to show patch contents.
      Press 'q' to quit.
      Selection: u

      Enter u at the prompt to begin the upgrade.

  2. After you make your selection, the installer completes the new (or interrupted)
    installation.

The installer displays the following upon completion:

[<timestamp>] Done with component Opsware Patch.

[<timestamp>]

########################################################

[<timestamp>] Opsware Installer ran successfully.

[<timestamp>]

########################################################

Software Repository Content Upgrade

This section details upgrades to the software repository content on the upload
distribution (such as agent packages to be reconciled to managed servers).

General Information

 Note: Unlike core patches, Software Repository content upgrades cannot be rolled back.

Upgrading the First Core Content

  1. On the First Core Software Repository store ( word store ) host, invoke the upgrade
    script:

    <distro>/opsware_installer/patch_contents.sh --verbose -r <response file>

    where <response file> is the response file last used to install/upgrade the SA Core.

    The following menu is displayed:

    Welcome to the Opsware Installer. Please select the components
    to install.
    1 ( ) Software Repository - Content (install once per mesh)
    Enter a component number to toggle ('a' for all, 'n' for none).
    When ready, press 'c' to continue, or 'q' to quit.


    Enter either 1 or a and press c to begin the installation.

  2. If the Software Repository content image is not installed on the server, the following
    message will be displayed:

    [<timestamp>] There are no components to upgrade.
    [<timestamp>] Exiting Opsware Installer.

Rolling Back the Patch

To rollback SA 9.02 to SA 9.0, invoke the script:

<distro>/opsware_installer/patch_opsware.sh --verbose

If this is a patched system, the following will be displayed:

Welcome to the Opsware Installer. It appears that you have previously
completed installation of this patch on this system.
Press 'r' to remove this patch.
Press 's' to show patch contents.
Press 'q' to quit.
Selection:

Enter r at the prompt to remove the patch.

Notes:

Rolling Back the Database Schema Update

Note: If you created the optional file
/var/opt/opsware/OPSWpatch_sql/optional_updates.conf

with the entry truth_modify_truth_stats_job=1 (modifies the TRUTH database
users dba_job that collects schema statistics.) during the install process as described
in Step 1 of the Database Schema Update Procedure, you must ensure that the same
optional_updates.conf
file is available during the rollback process.

To roll back the database schema update, enter this command:

<distro>/opsware_installer/patch_database.sh --verbose -r <response file>

Where <response file> is the response file last used to install/upgrade the system.

If the database has been updated, you see the following:

Welcome to the Opsware Installer. It appears that you have previously
completed the installation of this database update on this system.
Press 'r' to remove this patch.
Press 's' to show patch contents.
Press 'q' to quit.
Selection: r

Enter r at the prompt to begin the database schema update rollback.

Post-Patch Installation Tasks

Windows Server 2008 R2 x64

Required only if you have not set up SA support for Windows Server 2008 R2 x64
when you applied the SA 9.01 patch. SA 9.01 and later provide improved support for
Windows Server 2008 R2 x64. Windows Server 2008 R2 x64 now appears with its own
entries in the SA Client rather than as a subset of Windows Server 2008.

However, there are some tasks you must perform in order to migrate any Software Policies,
Application Configurations, packages (units), Patch Policies and/or OS Provisioning objects
you may already have set up for your server(s).

This section describes how to set up SA support for Windows Server 2008 R2 x64.

Migrating Software Policies, Application Configurations and/or Patch Policies is handled by
running a script, windows_2008_R2_fix_script.pyc , provided with SA 9.02 and later
in the directory:

<distro>/opsware_installer/tools

The script is called windows_2008_R2_fix_script.pyc and is invoked as follows:

/opt/opsware/bin/python2 windows_2008_R2_fix_script.pyc [--mrl=<MRL_ID>|--listmrls|--help

Note: It is very important that you ensure that the MRL(s) specified when you invoke this
migration script are correct. Once the script is invoked, migration begins immediately.
Providing the incorrect information when invoking this script can cause irreversible data
integrity errors.

The script has the following options:

Table 4: Script Options

Options

Description

--listmrls, -l

List all Windows Server 2008 x64 MRLs (ID, Name and Media Path)

--MRL=<MRL ID>

Migrate the MRL with the specified ID to the Windows Server 2008 R2 x64 platform.
Can be specified multiple times.

--help, -h

Display usage and help

Note: Migrated objects other than Patch Policies are not copied, they are attached to the new
Windows Server 2008 R2 x64 configuration.

For Patch Policies, Windows Server 2008 R2 x64 copies are created of Windows Server 2008 x64
Patch Policies containing R2 patches (x64 patch library).

The Windows Server 2008 x64 Patch Policies are then detached from the Windows Server 2008 R2 x64
servers and the equivalent Windows Server 2008 R2 x64 Patch Policy copies are attached to the
Windows Server 2008 R2 x64 servers.

Note: You can run windows_2008_R2_fix_script.pyc multiple times without issue. The changes
made by the script cannot be rolled back.

Requirements

Software Policies

After migration completes, the Software Policy appears in the SA Client Navigation
pane under Library/By Type/Software Policies/Windows/Windows Server 2008 R2 x64
and Windows Server 2008 x64.

During migration, Software Policies are modified only if:

When processing policy items the script looks for the following types of objects:

If the script finds a policy item that has Windows Server 2008 x64 in the platform list it
will migrate that policy item to Windows Server 2008 R2 x64.

The order of items in the Software Policy is retained and remediation status remains
unchanged.

If the script identifies an existing Software Policy as a Windows Server 2008 R2 x64 policy,
it does not modify it during processing.

Packages

The script migrates only the packages that have Windows Server 2008 x64 in the platform
list and are included as policy item inside a Software Policy that is migrated by the script.

After migration, the package will appear in the SA Client under both the
Windows Server 2008 x64 and Windows Server 2008 R2 x64 folders in
Library/By Type/Packages/Windows.

The script does not take into account the package type. It looks for packages included in
migrated Software Policies that are attached to Windows Server 2008 x64. Server Module
Result objects, Windows Registry objects and Windows Services objects cannot be migrated
by the script because their platform associations cannot be changed.

Properties settings (including general, archived scripts, install parameters, install scripts,
uninstall parameters, uninstall scripts) are preserved.

Application Configurations

The migration script migrates an application configuration if:

During migration the script adds Windows Server 2008 R2 x64 to the application
configuration's platform list. The script also inspects all application configurations'
associated templates (CML templates) and if a template has Windows Server 2008 x64
in the platform list it is also migrated.

There is no undo option.

Patch Policies

During migration, the script appends R2 to the Patch Policy name. For example, for a
patch policy named 2008 XYZ Policy, the migration script creates a new
Windows Server 2008 R2 x64 policy named 2008 XYZ Policy R2 if:

Note: If a Windows Server 2008 R2 x64 policy named 2008 XYZ Policy R2 already exists,
the applicable patches will be added to it.

If Windows Server 2008 R2 x64 servers, or device groups containing
Windows Server 2008 R2 x64 servers, are attached to Windows Server 2008 x64 patch
policies, the migration script will detach these policies and attach the newly created or
updated equivalent Windows Server 2008 R2 x64 policies. Applicable Patch Policy
exceptions are also migrated.

If metadata associated with Windows Server 2008 R2 x64 patches has been modified
(for example: install/uninstall flags, pre/post install/uninstall scripts), that metadata will
be migrated.

WindowsImageName Custom Attribute

The specification of the WindowsImageName custom attribute with
Windows Server 2008 R2 x64 is somewhat different from other platforms.

For Windows Server 2008 R2 x64, the expected values are:

Windows Server 2008 R2 SERVERDATACENTER
Windows Server 2008 R2 SERVERDATACENTERCORE
Windows Server 2008 R2 SERVERENTERPRISE
Windows Server 2008 R2 SERVERENTERPRISECORE
Windows Server 2008 R2 SERVERSTANDARD
Windows Server 2008 R2 SERVERSTANDARDCORE
Windows Server 2008 R2 SERVERWEB
Windows Server 2008 R2 SERVERWEBCORE

The populate-opsware-update-library Script

A new option, --no_w2k8r2, is provided for the populate-opsware-update-library
script and is used to specify that Windows Server 2008 R2 x64 patch binaries should
not be uploaded. For more information about the populate-opsware-update-library
script, see the SA User's Guide: Application Automation .

Windows Server CLI Installation

If you plan to install the SA Command-line Interface (OCLI) on a Windows Server after
upgrade to SA 9.02, you must update the Agent on that server to the latest version. Errors
occur during OCLI installation on Windows servers with earlier Agent versions.

Back to the Table of Contents

Known Issues

This section describes known issues for 9.02. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.

Table 5: Known Issues

QCCRID Symptom/Description Platform Subsystem Workaround

Agent

100660 Windows ADT login fails for administrators
that are not user Administrator due to security
controls for Windows UAC.
Windows Server 2008 using UAC Agent Deployment

Turn off UAC:

  1. In the Control Panel, click User Accounts.
  2. In the User Accounts window, click User
    Accounts.
  3. In the User Accounts tasks window, click
    Turn User Account Control on or off.
  4. If UAC is currently configured in Admin
    Approval Mode, the User Account Control
    message appears. Click Continue.
  5. Clear the Use User Account Control (UAC)
    to help protect your computer check box,
    and then click OK.
  6. Click Restart Now to apply the change right
    away, or click Restart Later and close the
    User Accounts tasks window. After the
    workaround is performed, any user belonging
    to the Administrators group will be able to
    deploy agents.
107917 Failed SA agent installation returns
gencache.py
error message in the agent log file (%SystemDrive%\Windows\System32\
opsware-agent-installer- .log
).
Windows Agent Installer

Remove all the files from the following three directories,
if they exist, and reinstall the agent.

%SystemDrive%\Program Files\opsware\agent\lcpython15
\Lib\site-packages\win32c om\gen_py\

%TEMP%\gen_py

%SystemDrive%:\Windows\temp\gen_p

111593 Agent fails to install when there is a gateway problem, but the agent log reports that the installation was successful.

Windows Agent Installer

Make sure the gateway can be reached from the managed server.

110347

Windows servers running a pre-9.0 agent can
perform a scan on an upgraded 9.0 core but not
on a freshly installed 9.0 core because scanning
Windows utilities are retained on the upgraded
core but are absent from the freshly installed core.

Windows Agent

Upgrade the agent on the managed servers that you registered
with SA 9.0.

 

118437

Agent deployment fails several times due to timeout issues when the uudecode utility
is not installed on the machine to which the Agent is deployed.

Red Hat or SUSE Linux s390x Agent Deployment/Upgrade

Install the uudcode utility on the machine(s) to which Agents are to be deployed to facilitate Agent deployment.

 

Application Configuration

50099 Data-manipulation script that includes Japanese
characters in the filename and content fails
with errors.
Windows Application Configuration - Backend Grant Read-Write privileges for Client Features -
Manage Installed Configuration and Backups on Servers.
111765 You are unable to modify Application Configuration
value sets for all scopes (Configuration, Facility,
Customers) even when you have appropriate
permissions.
Independent Application Configuration Grant Read-Write privilege for Client Features - Manage
Installed Configuration and Backups on Servers.

Application Deployment Manager

110220 When using a FileSystem Code Component in a
Delta Release for an Application, the Delta Release
will pick up file modifications and additions, but
not file deletions. In other words, a Delta Release
will not remove stale files.
Independent Application Deployment Manager

None.

You can choose to use a Script component to delete stale files
when deploying a Delta Release.

110637

Package Component file import (using the Import
Package feature) is unreliable for files that are larger
than 100MB.

When creating ADM Package Components, large
files may not upload successfully. You may see
an error message similar to:

Failed to upload installer.msi
(sent 238547 of419232 bytes).
IO Error: #2038

Independent Application Deployment Manager

Increasing the memory available to the SA Client should
allow for files up to 350MB to be uploaded using the
Application Deployment Manager. Larger files can be
uploaded using the Actions > Import Software menu
when editing a package in the Software Library.
To increase memory available to the SA Client, modify
the “max-heap-size”
parameter in /opt/opsware/occclient/jnlp.tmpl.
For example:

<j2se version="1.6" initial-heap-size="128m"
max-heap-size="1350m"/
>

Note that max-heap-size can be adjusted up to ~1350MB
for the 32-bit JVM used by the SA Client.

111106 When you export the ADM Environment to a Device Group
you receive the following error message:
"java.lang.RuntimeException: Unable to update the device
group representing the target '[targe name]': DeviceGroup or Server
deleted during operation, try again."
Independent Applicatikon Deployment Manager

Edit the target specified in the error message and remove all servers
that have been deleted from the inventory. Export the environment again.

111925

A deployment that includes a Configuration File
component fails without any warning or error when
attempting to place a file in a directory that has not
been created in advance.

Independent Application Deployment Manager

Ensure that a Code (or other type of ADM component)
creates the destination directory in preparation for file
placement by the Configuration File component.

 

113202 The Application Deployment Manager fails to launch
when a non-default Oracle System ID is used
(SID is not “truth”). The installer should automatically
add the truth.sid to the da.conf file.
Independent Application Deployment Manager

To resolve the issue, perform the following steps:

  1. Stop the Application Deployment Manager
    using the following command:

    /etc/init.d/opsware-sas stop da
  2. Add the truth.sid configuration parameter
    to the /etc/opt/opsware/da/da.conf file.
    For example:

    truth.sid=<newSIDname>
  3. Restart the ADM service:

    /etc/init.d/opsware-sas start da
115187 The Application Deployment Manager fails to launch
after you upgrade from 7.8 to 9.0 in an Oracle
Real Application Clusters (RAC) environment.
Independent Application Deployment Manager

Perform the following steps after the upgrade :

  1. Run the following command to stop the
    Application Deployment Manager:

    /etc/init.d/opsware-sas stop da
  2. In the /etc/opt/opsware/da/da.conf file,
    remove the truth.sid configuration parameter.
    For example:

    truth.sid= <SIDname>
  3. Edit the following file:

    /opt/opsware/da/webapps/arm/WEB-INF/
    classes/hibernate.cfg.xml
  4. Locate the block that contains the
    connection.driver and
    connection.username
    properties.
  5. Add the following string:

    <property name="connection.url">
    jdbc:oracle:thin:@ (DESCRIPTION =
    (ADDRESS = PROTOCOL = TCP)
    (HOST = host1)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)
    (HOST = host2)(PORT = 1521))
    (LOAD_BALANCE = yes) (CONNECT_DATA =
    (SERVER = DEDICATED) (SERVICE_NAME =
    truth) (FAILOVER_MODE = (TYPE = SELECT)
    (METHOD = Preconnect) (RETRIES = 180)
    (DELAY = 5))))</property>

    Here, host1 and host1 are variables that represent
    the names of your database servers. Include one
    (ADDRESS = (PROTOCOL = TCP)(HOST = hostname)
    (PORT = 1521))
    specification for every database
    server in your environment.
  6. Run the following command to restart the Application
    Deployment Manager:

    /etc/init.d/opsware-sas start da
  7. Re-run the Opsware Installer—or, alternatively, invoke
    the following command to populate the Application
    Deployment Manager baseline data:

    /opt/opsware/da/bin/da_baseline.sh
116762

Deployment into (or undeployment from) a
previously managed but now deactivated server
reports success. It should report a failure.

When a server is deactivated, all Policies are
detached, and all history is discarded.

Independent Application Deployment Manager Delete the server from all of its targets when it is deactivated.
The targets can be seen from the list of device groups to which
the server belongs.
118701

You cannot add a Tier to an Application if the
Tier name contains certain special characters.

Specifically, the Add Tier dialog will appear
completely empty.

Independent Application Deployment Manager

Do not use the following characters in a Tier name:  >
(greater than), < (less than), or & (ampersand)

If you create a Tier using these characters, and you encounter
problems adding tiers, simply delete the problematic new
Tier from the Application Deployment Manager
Administration screen.

118746

After upgrading the Java plug-in for your browser
to version 1.6.0_22, the following error dialog
appears whenever the SA Client or Application
Deployment Manager is launched:

"The new Java Plug-In requires a recent version
of the FireFox browser (Firefox 3 or later)"

Independent Application Deployment Manager

Click OK to close the error dialog.

Alternatively, you can change the following setting in the
greprefs\all.js file (by default, c:\program files\hp bsa\launcher\gre\greprefs\all.js):

pref("security.enable_java", false);

This prevents the error dialog from being displayed but may
have other consequences. Be sure to restart the SA Client
after you make this change.

APX

117680

APX session timeout is not correctly implemented.

 

Independent APX

To increase timeout for Web APX Proxy (Note: this must be
done at all the Slices on all the Cores):

  1. Edit /etc/opt/opsware/apxproxy/apxproxy.conf
    to specify both the session timeout and socket
    timeout. Make sure socket timeout is at least
    equal to session timeout. For example,

    apxproxy.apx.session.timeout=1200000
    apxproxy.apx.socket.timeout=1200000

  2. Edit both /opt/opsware/apxhttpd/conf/httpd.conf.tmpl
    and /var/opt/opsware/ogfs/mnt/root/opt/opsware/
    apxhttpd/conf/httpd.conf.tmpl
    to add a timeout directive.
    Add this property after the "Server" property. For example,

    imeOut 1200

    Remember, unlike apxproxy.conf, the timeout value in
    httpd.conf.tmpl is in seconds, not millisecon

  3. Restart the Core.

Audit and Remediation

102706 After a patch rollback, audits, patches and AppConfig,
software policies are missing from the Select
Compliance Columns dialog on an SA 7.81 Secondary
Core if the First Core is SA 7.80.
Independent Audit and Compliance The pick lists are empty because the search to fill them relies
on a new SA 7.81 search field that is not in the database
because of the rollback. In a Multi-master mesh, HP
recommends that you patch the primary core first, followed by
secondary cores and satellites, thus ensuring that the primary
core is at a higher version (such as SA 7.81 or higher) than the
secondary cores. If you must roll back the SA 7.81 patch in a
Multi-master Mesh, HP recommends that you roll back the
secondary cores and satellites first, then the primary core.
However, if you cannot rollback a secondary core(s), you can
restore the missing data by running the following on the 7.81
secondary core(s):
/opt/opsware/bin/python2 /var/opt/opsware/
OPSWpatch/OPSWspin/scripts/ QC94469_apply.pyc

BSA Essentials Dataminer

112784

In multimaster environments, Application
Deployment data mismatches between SA and
BSA Essention can occurr if the data is replicated
across the Model Repository Multimaster
Component (vault) to where the BSA Essentials
Dataminer is installed within the first few
milliseconds of a minute.

Independent BSA Essentials Dataminer None.

Database Scanner for Oracle

88091 Database Scanner for Oracle binaries, which are
copied to a managed server during each
snapshot process, are not automatically removed.
Independent Database Scanner for Oracle

Remove the binary files:

  1. From the Navigation pane, select Device ->
    Servers -> All Managed Servers
    .
  2. Right-click the managed server and select
    Run Script -> Select Script.
  3. In the Run Server Script window, click Select
    Script to display the Select Script dialog.
  4. In either the Browser Scripts tab or the Browse
    Folders tab, select the "post-uninstall script for
    Database scanner for Oracle [unix|win]" script
    and then click Select.
    To view this script, you must have privileges on
    the /Opsware/Tools/Server Modules
    com.opsware.server.module.storage.
    dbscanner.oracle
    " folder.
  5. In the Run Server Script window, click Next.
  6. Click Start Job in the Options pane. Do not specify
    any additional parameters.
  7. When the job successfully finishes, the files
    related to the Database Scanner for Oracle
    will no longer be on the cleaned managed server.

 

 

91143

The status of an ASM Diskgroup shown in
the Properties view (for one database instance
only) is different than the status shown in the
Database Configuration Assistant (DBCA) view
(a CONNECTED status is displayed instead of a
MOUNTED status).

Independent Database Scanner for Oracle None.
93690

The Server -> Relationships -> SAN Switches
panel on a virtual server is empty/only displays
SAN switches to which the given server is
directly connected.
In some cases, a server may depend on SAN
switches that are not displayed in this panel.
For example, a virtual server may be using
storage allocated from a hypervisor that was
allocated storage from a SAN.

Independent Database Scanner for Oracle None.
Bug ID: 156909 / QCCRID 68263 Free space in the tablespace view does not
match what is displayed in the Oracle
Enterprise Manager (OEM) tablespace.
Independent Database Scanner for Oracle

None.

Note: There is an OEM bug about some tablespaces showing the
incorrect used size. The Database Scanner for Oracle gets the
tablespace used size directly from all of its data files, which
avoid the OEM bug.

Installer

100931

Patch rollback of the SA 7.81 patch displays
a failure error:
(Failed to remove software
policy (8710001) ProtocolError:
<ProtocolError for 192.168.161.22/
cogrpc.py: 404 Not found>
)

and fails to remove Storage Compliance
(which is a new feature and incompabile with
SA 7.80).

After reporting the error, rollback continues to
the next component. The rollback completes
successfully without other errors and cleans
up all patch-related files and folders on the core.

Independent

SA Installer

Manually remove Storage Compliance by running the following
command on one of the core servers:
/opt/opsware/bin/smtool --username=detuser
--password=<detuserpwd> --remove=com.opsware.server.
module.storage.compliance
114639 If you install additional Slice Component
bundle instances after patching the SA Core
to version 9.XX, wayscript versions are set to
version 9.0 rather than to the patch version.
Independent

SA Installer

In the SA Web Client:

  1. Log in as administrator (opsware admin user) and
    navigate to Environment -> Customer -> Opsware ->
    Custom Attributes -> CORD_OPSWwayscripts
    .
  2. Identify the SA core server by checking the value field
    of the custom attribute CORD_OPSWway scripts.
  3. Log in to the SA Core server you identified in step 1
    and execute the following commands:
    cd /var/opt/opsware/OPSWpatch/OPSWwayscripts
    /scripts./post_after_startup.sh
  4. Apply any required hotfixes to the wayscripts.

ISM Tool

110511

ISM tool fails to upload ISM into a software
policy because the tool mistakenly detects
the registry key HKLM\Software\
Wow6432Nodeidentified
, causing it to
identify a Windows Server 2008 server as a
Windows Server 2008 x64 server.

Windows Server 2008 ISM Tool

If you are developing an ISM on a server that has this
registry key, temporarily rename the registry during
ISM development so that ISMtool will correctly identify
the server as a Windows Server 2008 server.

Model Repository

83813 Attempting to synchronize a Multimaster
Mesh conflict on a ServiceInstance fails
with the following type of error:
ERROR -- Unable to perform UPDATE!
spin.genericDatabase error:
'ORA-02291: integrity constraint (.)
violated - parent key not found
ORA-06512: at ........
(srvc_inst_id = :p3)' with args
'('20-OCT-2008 23:40:21',
'124970002', '3230002')'

Independent Model Repository
(Truth)

Run the patch script patch_database.sh ensuring
that the file optional_updates.conf is configured as
described in Database Schema Update Procedure
in the Installation section of these release notes.

 

OCC Client Framework

118068

User’s  preferred  datetime format is:
“星期五 十月 22, 2010 15:16 CST”, but in
the SA Web client, all dates and times are
displayed as “Fri Oct 22,2010 14:04 CST”

Win2008 Win2008 R2 OCC Client Framework None

OCC Web

118067

Chinese Date format: Commonly used date
formats, like yyyy ’year’ mm ‘month’ dd ‘date’
and ‘yyyy-mm-dd’ are not listed in the user
profile setting, so users cannot select a
favorite date format.

Win2008 Win2008 R2 OCC Web None

OCLI

118249

When we upload a package like this
C:\Program Files\Opsware\ocli\scripts>
oupload -O "Windows 2008" -e gb2312
--pkgtype ZIP -d "/"  c:\download\testpkg中文.zip

we get an error
SUMMARY:
Name: exceptions.UnicodeEncodeError
Description: 'ascii' codec can't encode characters
in position 7-8: ordinal not
in range(128)

Win2008 Win2008 R2 OCLI None

OS Provisioning

100928

RAID deployment fails when the RAID
configuration is captured using ACU
version 8.35.7.0 (linux5 boot image) for valid
RAID configurations on machines with SCSI
drives because the "pretty printing" of SCSI
drive bus values uses 0-based index instead
of 1-based index.

Red Hat Enterprise Server 5 OS Provisioning
  1. Perform captures with ACU Version 8.25.5.0
    (using boot images other than linux5) and deploy
    those.
  2. Modify the raid.hpacu.script custom attribute value for
    RAID Array Configuration on ACU Version:
    8.35.7.0-captured RAID policies to use the correct drive
    indexes.
    For example, modify this captured configuration:
    ; Array Specifications
    Array= A
    ; Array Drive Type is Parallel SCSI
    ; 1:0 (36.4 GB), 1:1 (36.4 GB), 1:2 (36.4 GB),
    1:3 (36.4 GB),
    1:4 (36.4 GB), 1:5 (36.4 GB)
    Drive= 1:0, 1:1, 1:2, 1:3, 1:4, 1:5
    to the following:
    ; Array Specifications
    Array= A
    ; Array Drive Type is Parallel SCSI
    ; 2:0 (36.4 GB), 2:1 (36.4 GB), 2:2 (36.4 GB),
    2:3 (36.4 GB),
    2:4 (36.4 GB), 2:5 (36.4 GB)
    Drive= 2:0, 2:1, 2:2, 2:3, 2:4, 2:5
102830 Cannot modify or enter a timeout value
for pre/post remediate scripts while creating
a new OS Sequence.
Independent OS Provisioning - OCC - Client None.
103362

After a server is provisioned using a RedHat
DHCP-LESS image in the VLAN, attempting to
reprovision the server causes the server to reboot,
after which the reprovision process fails at the
Anaconda Configure TCP/IP window, prompting
for network information.

Independent OS Provisioning - OCC - Client None.
103394

When booting a target server using the Linux
boot CD in a DHCPless network, specifying
an IP address already in use by another host
will prevent the target server from successfully
registering with the SA core. No network
check/warning error is displayed.

Red Hat Linux OS Provisioning - OCC - Client Make sure the IP address you specify is available.
103602

After you choose Windows as the OS Family, you
cannot use the Manage Boot Client (MBC) to create
winpexx-ogfs server records in the MBC Single
Form because winpe32-ogfs and winpe64-ogfs
image
types are not displayed in the PXE image
drop-down box.

Windows OS Provisioning - Backend None.
104194

When RAID deployment fails after the RAID
controller configuration has been cleared,
subsequent RAID captures or deployments
will fail unless RAID is first configured manually.

The following error displays:
Exit status: 1280

Error message from ACU: ERROR: (2821)
No controllers detected.

Independent OS Provisioning - Backend

Manually set the RAID controller configuration:

  1. Restart the server and press F8 when prompted.
  2. Create logical drive(s).
  3. Assign physical disks and RAID level.

 

After the RAID controller has been manually configured,
SA can be used to capture and deploy RAID configurations on
the machine.

104739 During a network boot of the server, the following
error displays:
"No driver found" screen appears:
"Unable to find any devices of the type
needed for this installation type.
Would you like to manually select your
driver or use a driver disk? [Select driver]
[Use a driver disk] [Back]
"
Red Hat Enterprise Server IA64 OS Provisioning The missing driver is not required. Press F12 to bypass the driver.
109044

If an OS Build Plan job fails due to a timeout, the target server is left in the Installing OS lifecycle instead of the expected Build Failed lifecycle state.

Windows OS Provisioning Backend

Reset the lifecycle by rebooting the target server into WinPE again.

109077

Assign Customer OS Build Plan content script fails if
customer names contain quote characters.

Windows OS Provisioning Backend Specify the customer ID instead of the actual customer name.
110563

Under some circumstances, when writing I18N content to
files from OGFS to WinPE, data and files containing
non-ASCII characters may be corrupted.

Windows OS Provisioning Backend Use only ASCII characters if possible.
111245

When you upgrade, unless you have customized the bm.reprovision_attributes_to_preserve system
configuration value, your custom values will not be
replaced by the new values required for this SA release -
instead, old values are retained.

Independent OS Provisioning Re-enter your values by appending them to this setting
on the SA Web Client
111337

The Cannot access target server over OGFS
error occurs randomly on a server while running an
OS Build Plan on multiple servers.

Solaris OS Provisioning None.
111445

Run OS Sequence does not escalate device group
privilege. Run an OS Sequence that has an attached
device group results in an exception and the job
is not created.

Independent OS Provisioning Enable the Manage Public Device Group privilege for the user
group on either the Client Features tab or Other tab.
114523

When performing OS provisioning using
Application Deployment Automation, if the SA OS
Sequence in use includes a device group and
multiple servers are provisioned simultaneously,
some of those server provisioning jobs will fail with
the following error:
Unexpected general exception: com.opsware.device.DeviceGroupVO.modifiedDate
is set to the illegal value.

Linux, Solaris, Windows OS Provisioning Do not include any device groups in your OS Sequence.
111781

When provisioning Windows Server 2003 or 2008
using an OS Sequence to a non-C drive using a
WIM image:

  • Provisioning works for Windows Server
    2003 OS Media.
  • Provisioning fails for Windows Server
    2003 WIM and Windows Server 2008
    OS Media and WIM.
    When provisioning Windows Server 2003
    or 2008 using OS Build Plans to
    non-C drives, Windows 2003 & 2008 OS
    Media installs are supported, but Windows
    2003 & 2008 WIM installs are not supported.

 

OS Provisioning Backend

Windows Server 2003

None.
111845

Provisioned machines using MBC may continually reboot
into the un-provisioned server pool after initial provisioning
because the sequence_id and MAC link were not removed.

 

OS Provisioning - MBC Red Hat Linux After Solaris x86 provisioning is completed, manually:
  1. Delete the link file (the filename is equal to the target server
    MAC address) from the core's DHCP server's /opt/opsware/boot/tftpboot/pxelinux.cfg directory.
  2. If set, remove the sequence_id custom attribute
    from the server.
115063

After migration, Windows Server 2008 R2 x64 servers
are listed incorrectly as Windows Server 2008 x64 in the
SA Web Client, but correctly as Windows Server 2008
R2 x64 in the SA Client.

Windows Server 2008 R2 x64 OS Provisioning None.
118372

SA fails to complete OS provisioning if the net or subnet from
which the machine obtains its IP address does not have PTR records
associated with the IP address.

Red Hat Linux 4 and 5 Power OS Provisioning Make sure that there are PTR records associated with the IP address or
specified in /etc/hosts on the OS provisioning DHCP server.

Patch Management for Solaris

98409

Sometimes, when importing a patch cluster into the
SA Library, the vendor documentation for the cluster
is not imported, although a link is provided.

Solaris Patch Management - Solaris Select the link to the vendor documentation and log in to the Sun web
site to download the cluster documentation.
100566

Although the reboot is performed correctly, when you
preview remediating a patch policy on a server, or view
the job status for a patch policy that is already
remediated, the reboot setting might incorrectly
display “Install and Reboot Later” when it should
display “Install and Reboot”.

Solaris Patch Management - Solaris A workaround is not required because the reboot is performed correctly,
even though the display may be incorrect.
109142/
115536

If you modify the default Solaris patch configuration
file (located at /etc/opt/opsware/solpatch_import/
solpatch_import.conf
) and then upgrade to
SA 9.xx, your changes to the configuration file will be
overwritten.

Solaris Patch Management - Solaris - Backend

Save your modified Solaris patch configuration file before
performing the upgrade to SA 9.xx. After the upgrade, update
your Solaris patch configuration file and run
./solpatch_import -a update_supplements
.

Note that Solaris patch bundles are not supported on SA 9.0.
For more information, see QCCRID 109359.

109359

If you use Solaris patch bundles on SA 7.82 and you
upgrade to SA 9.0.x, SA will return errors when attempting
to access the Solaris patch bundles.

Solaris Patch Management - Solaris - Backend If you are using Solaris patch bundles on SA 7.82, you can
wait for a release following SA 9.0 for support for
Solaris patch bundles. Or you can upgrade to SA 9.0
without support for Solaris patch bundles, as follows.
  1. Remove all Solaris patch bundles from the
    SA Library. Use either one of the following
    two methods.
    Method 1 - Remove Solaris bundles using the
    SA Client.
    a. In the SA Client, select the Library tab and
    then the By Type tab.
    b. Open the Patches node.
    c. Open the Solaris node.
    d. Locate all the Solaris patch bundles under
    each Solaris operating system version.
    e. Select each patch bundle and select the
    Actions -> Delete menu.
    Method 2 - Remove Solaris bundles using the
    solpatch_import command.
    a. Put all bundle names in a text file, one bundle
    name per line. To get a list of existing bundles in
    the SA Library, run the solpatch_import command
    with the show action and the -q option to display only
    the bundle names and save the output to a file.
    The following example command places the bundle
    names in the file bundles.txt:

    /opt/opsware/solpatch_import/bin/
    solpatch_import -a show \ --all_bundles
    -q >bundles.txt


    Delete the bundles by running the solpatch_import
    command with the delete action and specifying the
    text file you created in the previous step. For example: /opt/opsware/solpatch_import/bin/
    solpatch_import -a delete bundles.txt

  2. Remove the Solaris patch database by removing the
    following files, if they are present:
    /Opsware/Tools/Solaris Patching/solpatchdb.zip
    /Opsware/Tools/Solaris Patching/solpatchdb-old.zip
    /Opsware/Tools/Solaris Patching/
    solpatchdb_supplement.zip
  1. Complete the upgrade to SA 9.0.
  2. Create a new Solaris patch database using the following
    command:
    /opt/opsware/solpatch_import/bin/
    solpatch_import -a create_db


    For complete information on the
    solpatch_import command and Solaris patching,
    see the SA User’s Guide: Application Automation.
111342

Importing clusters with old names using
the solpatch_import command will fail because
Sun has renamed their Solaris patch clusters -
the clusters in your SALibrary may not match the
cluster names from Sun on Sunsolve.

SunOS 5.6 - 5.10 and SunOS 5.10 x86 Patch Management - Solaris Download the latest supplement file from HP LNc. For complete
instructions, see “Obtaining the Solaris Patch Supplementary
Data File” in the SA User Guide: Application Automation.
114156

The solpatch_import –filter option does
not display recommended and/or security
patches if they had previously been marked
obsolete. This became an issue on June 4,
2010 when Oracle changed the criteria for
recommended and security patches
(described here: http://blogs.sun.com/patch/
entry/merging_the_solaris_
recommended_and
).

Solaris Patch Management - Solaris Users with an existing metadata database (solpatchdb) must
delete the solpatchdb.zip, solpatchdb-old.zip and
solpatchdb_supplement.zip
files and run create_db
to have support for recommended obsolete patches.

You must recreate the Solaris patch metadata database
(solpatchdb) if the following are true:
  1. You use the solpatch_import –filter option.
  2. You have run solpatch_import –update_db on
    June 4, 2010 or later.


After you have installed SA 9.01, perform these tasks to recreate
the metadata database (solpatchdb):
  1. Log in to the SA Client.
  2. Select Library in the Navigation pane.
  3. Select By Folder.
  4. Navigate to /Opsware/Tools/Solaris Patching.
  5. Delete the following files:
    • solpatchdb.zip
    • solpatchdb-old.zip
    • solpatchdb_supplement.zip


Follow the steps to create a new metadata database (solpatchdb)
as described in the SA User Guide: Application Automation,
Patch Management for Solaris.

Patch Management for Windows

102713

If a patch policy contains one or
more superseded patches, the
number of total rules counted after
remediating or patch installation
is incorrect. Note that the
compliance state of the server is
accurate before and after remediating.

Windows Patch Management - Windows - Backend None.
108451

Windows Patch 944036 (installer for
IE 8) reports install failure (and returns
a non-zero exit code) on Windows Server
2008 x64 managed servers, even though
the patch is installed correctly.
Subsequent patch and compliance
scans will indicate the patch is installed
and compliant.

Windows Server 2008 x64 Patch Management - Windows - Backend A workaround is not required because the patch job succeeded,
even though an error displayed.
105098

Automatically installing recommended
Microsoft patches Q934041 (2000) and
Q924883 (MS07-014) fails. Manually
installing the patches results in a
Non-Compliant server status and a
dialog that is displayed:

Update has already been applied or is
included in an update that has already
been applied.

Windows Patch Management - Windows - Backend Since the patch is not required, set a “never install” exception on
the patches.
110257

If you try to install the March 2010
(or later) MBSA patch database, and
then attempt to install MS10-015
(KB977165) and MS10-021 (KB979683)
on to a Windows Server 2008 x86 using
a Windows Patch policy, the Patch install
job results will incorrectly indicate success.
After a patch compliance scan, SA will still
report the patches as recommended for
the server, and the server will be listed
as non-compliant.

Windows Server 2008 x86 Patch Management - Windows - Backend
  1. To install these patches, import the April 2010 (or later)
    version of the BSA Essentials Network patch supplement
    from the BSA Essentials Network on to your SA core server.
  2. Visit http://support.microsoft.com/kb/980966/ to download
    KernelSystemStateCheck.exe to determine whether the
    patch can be installed on your Windows Server 2008 (x86)
    managed servers.
  3. Contact HP Server Automation Support in order to get this file
    qc110257.pyc”. (The Quality Center bug report number is
    QCCRID 110257.)
  4. On the SA core, copy qc110257.pyc to the SA core’s Data
    Access Engine (spin) server.
  5. As root on the SA Data Access Engine (spin) server, execute
    the following command:

    # /opt/opsware/bin/python2 qc110257.pyc

  6. Assuming Microsoft's KernelSystemStateCheck.exe utility reports a pass result, use the ad-hoc Install Patch task window to install the version of MS10-015 (KB977165) that has a file name of
    Windows6.0-KB977165-x86.msu, and the version of MS10-021
    (KB979683) that has a file name of Windows
    6.0-KB979683-x86.msu.
Note: The Install Patch job progress may show “Was Not Installed” or
“side effect” messages. These progress messages may not be accurate.
The true indicator of whether these patches installed or not is when after the
Install Patch job completes (with reboot), MS10-015 (KB977165) and
MS10-021 (KB979683) are no longer recommended, and the compliance
indicators for these patches no longer show a red X.

Note: The SA Client will show the mpsyschk.exe version of these patches as
recommended or installed.
110471

Attempts to install the patch for
KB944036 (Installer for IE8) using SA will fail.

 

Patch Management - Windows - Backend Windows Server 2008 x86 Log on to the managed server and install the patch for KB944036 manually.
111397

After remediating the vendor recommended
policy on a Windows managed server,
the server's recommended patch list shows
additional patches that need to be installed,
requiring the vendor recommended policy
to be remediated again. This sometimes
occurs when older patches introduce
problems that newer patches already fixed.

Windows Patch Management - Windows - Backend None.

SA Client (Framework)

105671

The SA Client cannot be installed under
a localized (I18N) directory if the directory
path contains non-ascii characters.
Windows SA Client Framework Install the SA Client Launcher in a path containing only ascii characters.

SA Client (Search)

66448 Some discovery dates for SAN arrays,
NAS filers, and switches will not display
as expected, although they are
technically correct, if the user profile is
set to a non-UTC timezone for Storage
System Discovery Date.
Independent SA Client (Search) None.

SA/NA Integration

90653

SA 7.8x and SA 9.x with NA7.5x integration
fails.

Independent SA/NA Integration

Perform the following actions:

  1. In the jboss_wrapper.conf file, comment out the
    following lines: #wrapper.java.additional.6=-Dorg.omg.
    CORBA.ORBClass=com.sun.corba.se.internal
    .Interceptors.PIORB

    #wrapper.java.additional.7=-
    Dorg.omg.CORBA.ORBSingletonClass=
    com.sun.corba.se.internal.corba.ORBSingleton

    #wrapper.java.additional.8=-
    Xbootclasspath/p:/opt/NA/server/ext/wrapper/lib/
    CORBA_1.4.2_13.jar

  2. Restart truecontrol.

SA/OO Integration

102614

The SA/OO Integration feature is not
available until after you import the required
OO SDK Client Certificate.

Note: OO SDK Client certificates support
different versions of OO. SA 9.01 contains
an OO SDK Client Certificate for OO versions
7.51, 7.6, and 9.0. Make sure you have a
certificate that is compatible with
your SA version.

Independent SA/OO Integration If you have a mesh core containing one master core and one or
more slave cores, complete the following steps for the Web
Services Data Access Engine (twist) component on the master
core and on all slave cores.

If you have a sliced core installation containing one or more slices,
complete the following steps for the Web Services Data Access
Engine (twist) for each slice. Use the following procedure to
import the certificate:
  1. Enter the following command to stop the twist
    component:
    /etc/init.d/opsware-sas stop twist
  2. Enter the following command to export the OO
    Central Certificate:

    /opt/opsware/jdk1.6/jre/bin/keytool
    -exportcert -alias pascert -file
    /tmp/oocentral.crt -keystore
    /var/opt/opsware/twist/oocert

  3. Import the OO Central Certificate to the SA JRE Keystore.
    The JRE keystore default password is changeit.

    /opt/opsware/jdk1.6/jre/bin/keytool
    -importcert -alias pas -file
    /tmp/oocentral.crt -keystore /opt/opsware/jdk1.6/jre/lib/security/cacerts

  4. Make sure there are no errors when you entered the
    previous commands.
  5. Enter the following command to make sure the
    certificate was imported successfully:
    /opt/opsware/jdk1.6/jre/bin/keytool
    –list –alias pas –keystore
    /opt/opsware/jdk1.6/jre/lib/
    security/cacerts


    Example output:
    pas, Feb 3, 2010, trustedCertEntry,
    Certificate fingerprint (MD5):
    DF:DD:22:1B:A2:1E:A9:9C:1C:AF:8F:
    E0:14:1F:B5:E0
  6. Enter the following command to start the twist:
    /etc/init.d/opsware-sas start twist

SA/SAR Reports

105234

In the SA Client in an NA-enabeld core,
if you run the Connections by Network
Device report and set the parameter to
Device Name Equals [Any Value], the search
returns no results.

Independent SA Client Reporting Run the report using the following parameters:

Device Contains
107293 Scheduled reports exported to .xls do
not display charts or graphs
(“Unsupported Image error” is displayed
instead). However, tables are sent correctly.
Graphs are not visible in the .xls file, but the
report should not display empty image blocks.
Independent SA Client Reporting None.
112434

The “Application Deployment” and “Patch”
folders and their reports in the BSA
Essentials/SAR Client 2.0/2.01 installation
patch are missing. These folder definitions
are required to view the Application
Deployment and Windows patch reports.

Independent SA Client Reporting After you complete the installation process for BSA Essentials
2.0/2.01 patch and download content from the BSA Essentials
Network for the product/stream you subscribe to, complete
the following steps:

Log in to a BSA Essentials core server.

  1. Change your user to become the BSA Essentials
    super user on the server:
    su - ombd
  2. Enter the following commands:

    cd /opt/opsware/omdb/deploy/birt.war
    cp report_def.xml report_def_org.xml
    vi report_def.xml
  3. Add the following two lines in the section of the
    report_def.xml
    file:

    application_deployment_reports

    top_level_patch_reports

    Example: <folder name="reports">

    <display_name>Reports</display_name>

    <folder_reports></folder_reports>

    <subfolders>

    <subfolder_name>
    application_deployment_reports< /
    subfolder_name>

    <subfolder_name>top_level_patch_reports
    </subfolder_name>

    .....

    .....

    /subfolders>

    <parent>none< /parent>

    < /folder>

  4. Save the report_def.xml file.
  5. Launch the BSA Essentials Java Client.
  6. Click on the Reports folder to see the
    “Application Deployment” folder and
    “Patch” folders.

SA Web Client

109000

Internet Explorer enhanced with Security
Configuration (IE ESC) that is enabled to
access the SA Web Client blocks some features
of SA Web, such as the search function.

 

Independent SA Web Client There are two solutions to this issue:
1. Add the SAS Web core URL to IE's trusted sites list.
When using IE with ESC enabled to access the
SAS Web Client core login page, you will be asked
whether or not to trust the core web site. You must
click the Add button in order to add the core web site
to the list of trusted sites.
To Manually add the core URL to the trusted sites list,
in IE select Tools -> Security -> Trusted Sites.
Enter the entire URL (for example, https://192.168.181.130)
and then click Add. Restart your browser to ensure all new
settings are accepted.
2. Disable IE ESC altogether.
Go to the Server Manager (the first icon near the
Start Menu on most systems, or the top left hand side
icon on all configurations). The Server Manager view
should be automatically selected on the left side panel.
On the right side panel, there is a Group label named
Security Information. On the right hand side of the pane,
in Security Information, click the link named Configure
IE ESC. For both Administrator and Users, select Off
and then click OK. Restart your browser. IE ESC is
now disabled.

Satellites

97659

Network scans to a satellite realm fail for
hosts with the error:
XML document structures must start
and end within the same entity
.

Windows Satellites In the SA Client Options select Tools -> Options
-> Unmanaged Servers -> Advanced
and remove
the argument -S %GATEWAY_IP% from the NMAP
parameters. The network scan should complete
successfully.
91097

In some cases, in the SA Web Client Manage
Gateway page, changes to bandwidth throttling
values between two gateways do not persist.

Independent Satellites

You must apply any bandwidth changes between
gateways on the Core
Gateways only. Changes made on other gateways
will not take effect.

Script Execution

79545

Exporting a Run Server Script Job output
containing multi-byte characters
(Japanese/Korean) to .csv results in question
marks in place of the multi-byte characters.

Windows Script Execution Export the job results in .txt format to eliminate the
garbled text.

SE Connector

88755

There is no Target and Target Volume
information displayed in the storage volume
access path view for a LUN

Independent SE Connector None
91582

When you perform a provisioning operation
for an HP EVA array (such as create, delete,
or modify a volume or pool), the changes for
the volume or pool might not be immediately
available in the corresponding Inventory view
in SA after running the "Update from Storage
Essentials" process.

Independent SE Connector After 30 minutes has lapsed, run the "Update from
Storage Essentials" process again. See the Storage
Essentials SRM Software User Guide
for information
about provisioning EVA arrays.
105778

When a server on which SE Connector is
running is directly deactivated and deleted,
selecting Administration -> Storage Scanners ->
<The names of the SE Scanner on "Host">

shows stale entries of Storage scanners in the
Scanner panel. The stale entries count will
increase, depending on how many times the
server is deactivated and deleted from the core.

Independent SE Connector Manually delete the inactive Storage Scanner entries
from the Storage Scanner panel by using the Remove
menu option provided for each entry.

Server Automation Installer

111215

Restoring OS Provisioning Stage 2 images
fails on SUSE Enterprise Linux 9, which is a
deprecated platform.

SUSE Enterprise Linux 9 Installer You can restore the OS Provisioning Stage 2 images by
manually running the restore_stage2.pyc script. This
script is located in:
<distro>/opsware_installer/tools/
restore_stage2.pyc

Software Management

100754

You cannot set the timeout value for the time
it takes to install or remove software or execute
scripts to anything other than the default value
of 5 hours - the job times out at 5 hours.
This timeout value is specified by
"way.remediate.action_timeout" in the
SAS Web Client.

The job fails with the message "The request
to retrieve information from the Agent failed
because it timed out. If the problem persists,
please contact your HP Server Automation
Administrator."

Independent Software Management None
101517

After performing a software remediation, the
compliance status might incorrectly show servers
as being out of compliance, because there is a
caching delay in the Web Services Data Access
Engine (twist).

Independent Software Management Run a Software Policy Compliance scan. This will show
the correct compliance status. For more information,
see "Software Compliance" and "The Software Policy
Compliance Scan" in the SA User Guide: Application
Automation
.
102564

Software Compliance scan status displays a Scan
Failed status after attaching and remediating a
software policy if the file solpatchdb.zip (the solaris
metadata database) is missing.

Solaris Software Management - API Compliance Use solpatch_import to create the metadata database.
See the Patch Management for Solaris in the
SA User Guide: Application Automation
for more
information about solpatch_import.
102934

If you run a large remediate job (for example,
500 servers), you might encounter a Web
Services Data Access Engine (twist) cache
full exception while running compliance
across the servers.

Independent Software Management - API Compliance Increase the cache size.
111356

When using WebService API to invoke
SoftwarePolicyService.create(), if you set the
RPM package in the installable item list by using setInstallableItemData(), the install list is
not created.

Independent Software Management - API Software Policy Use UAPI or webServiceAPI by calling
setSoftwarePolicyItems().
115665

Migrating a Windows Server 2008 R2 x64 server,
attached to a dynamic device group with the rule
Operating System=Windows Server 2008 x64
specified, prevents all Application Configurations,
remediated using a Software Policy, from being
detached from the server.

Windows Server 2008 R2 x64 Software Management None

Storage Host Agent Extension

93630

LUNs that are multipathed by EMC PowerPath
are shown as both "ROOT" and "LUN" in the
Inventory -> Storage -> Volumes Panel
alongside LUNs that are correctly displayed.
The SCSI Bus number provided by PowerPath
(using the powermt command) does not match
the bus number of the disks (LUNs).

Windows Storage Host Agent Extension None
105382

When you run the storage snapshot specification,
the disk capacity information is changed in the
Inventory -> Storage -> Disk panel. This occurs
if there is a mismatch in the disk names, as
reported by the hardware registration script
and the storage snapshot specification.

Windows 2008 Storage Host Agent Extension Reboot the server after changing disk information
(such as installing or uninstalling multipathing software,
presenting new LUNs, deleting LUNs, and so on),
and run the hardware registration before running
the storage snapshot specification.
105953

An EMC Symmetrix array that is discovered
through SE Connector can report more than
one storage volume with the same LUN number
presented to a managed server. Running the
storage snapshot specification on the managed
server will succeed; however, the Inventory
-> Storage -> File Systems
and Inventory
-> Storage -> Managed Software
panels
will be empty. In addition, some host volumes
with a LUN service type will not be displayed
in the Storage -> Inventory -> Volumes panel.

Independent Storage Host Agent Extension None
106400

The right-hand panel under
Inventory -> Storage -> Volumes does not
display the supply chain and composition
information properly (or the information is
missing altogether) for some volumes that
were created out of LUNs

AIX Storage Host Agent Extension Delete the stale volumes on the AIX managed server and
run the storage inventory snapshot specification.
106699

For managed servers with mirrored volumes,
if one of the disks that is part of a mirrored
volume fails or is removed, the state of the
volume is shown as "Failed Redundancy"
in the Disks Management panel. However,
in the Inventory -> Storage -> Volumes panel
for the managed server, the status of this
volume is shown as "OK", even after running
storage snapshot specifications.

Windows 2008 Storage Host Agent Extension None
107944

Running a storage snapshot specification on
unsupported ESX 3.0.x servers returns an error
message that indicates unsupported namespace
in content of SOAP body. Storage related
information for ESX 3.0.x is not stored and displayed
in the SA Client.

VMware ESX 3.0.x Storage Host Agent Extension None
109306

The supply chain breaks when users create
multilevel LVM RAID volumes, such as RAID10
or RAID50, and the Inventory -> Storage -> Volumes
panel does not display supply chains for
multilevel-RAID volumes.

Linux Storage Host Agent Extension None
111724
/111727

Host Storage Inventory does not support VMware
servers that have VMDK on NFS datastore. Therefore,
no storage information will be collected on VMWare
servers with this configuration.

All VMware servers Storage Host Agent Extension None
Bug ID: 149406 / QCCRID 60760

Solaris LVM RAID on Soft Partition on slices stops
responding, resulting in a defective storage supply
chain.

Independent Storage Host Agent Extension None
Bug ID: 149707 / QCCRID 61061

The SNIA v1 HBAAPI Extension reports two single
port cards when a single dual port card is present
in a multi-port card.

Independent Storage Host Agent Extension None
Bug ID: 151921 / QCCRID 63275

When you add a mirror to concatenated or stripe,
there is no distinction between the volume types
"Mirror Concatenated" and "Mirror Striped" in the
Volume Manager labels. Note that
"Mirrored Concatenated" and "Mirror Striped" are
distinct on the volume manager on the host, such
as on the Veritas Volume Manager.

Independent Storage Host Agent Extension None. The type of volume manager might not match the
native tool, such as the Veritas Volume Manager.
The STORAGE_TYPE value is the immediate node
in the supply graph, which is the storage type of the
most decendent volume.
Bug ID: 152016 / QCCRID 63370

The value stored in
STORAGE_COMPONENTS.STORAGE_DRIVE is a
different format on Solaris 5.10 than on Solaris 5.8
and 5.9. The different format for 5.10 causes a
broken storage supply chain on affected servers.

Unix Storage Host Agent Extension Check the version number in the /etc/format.dat file on
the server. If it is less than 1.28, update the file.
Bug ID: 152942 / QCCRID 64296

On a Windows 2003 server with the SNIA library
from QLogic 9.1.4.15 HBAAPI, Fibre Channel
Adapter and storage volume information might
not be discovered by the Storage Host Agent
Extension, causing fibreproxy.exe to stop
responding.

Windows Storage Host Agent Extension For Windows Server 2003 and Microsoft Windows 2000
operating systems, use the native Microsoft SNIA library
instead of the SNIA that is provided by the QLogic driver.
Download the Fibre Channel Information Tool to add the
Microsoft HBAAPI support to the operating system.
For Windows 2003 SP1 or later, the Microsoft HBAAPI
support is built in. If the SNIA's version of hbaapi.dll is
installed on the operating system, remove it.
Bug ID: 154418 / QCCRID 65772

When you snapshot a Unix server that has a
QLogic driver installed, there is no:
FC adapter information in the Hardware view.
Composition and connectivity information for any
SAN volume in the Volumes pane.

Independent Storage Host Agent Extension Install patches 108434 and 108435 on Solaris 8 SPARC
servers. The Storage Host Agent Extension on Solaris
5.8 SPARC requires these patches.
Note: There is no known workaround for Red Hat 3 or
Red Hat 4 servers using QLogic controllers.
Bug ID: 154971 / QCCRID 66325

Veritas Storage Foundation 4.3 with QLogic
9.1.4.15 results in invalid fibre proxy SCSI
addresses. The SAN storage volume displays
both LUN and Root as the Service Type. There
are two lines for the physical drives: One line
displays LUN and the other displays Root.

Independent Storage Host Agent Extension None
Bug ID: 155476 / QCCRID 66830 The file system is not displayed on the server
storage file system panel when the partition and
format on the Windows server is mounted to an
empty NTFS folder. There is no support for mounting
Windows 32 file systems on non-drive letter locations.
Windows Storage Host Agent Extension

None

Note: The Storage Host Agent Extension does not report file
systems that have non-drive letter mount points.
The Storage Host Agent Extension does not report file systems
that have multiple mount points.

Bug ID: 157044 / QCCRID 68398

Fibreproxy is broken on Windows 2000 SP4 server
with a QLA2310 HBA and vendor driver version
9.1.4.10. A storage inventory snapshot does not
gather and supply complete data, including storage
volume and FCA information.

Windows Storage Host Agent Extension None
Bug ID: 157579 / QCCRID 68933

When you run take a Storage Host Agent Extension
snapshot by running fibreproxy on a Windows server
where Emulex LP850, LP952, LP9002, or LP9402 is
installed, three FibreChannelTargetMappings are
returned, two of which are duplicates. This symptom
does not occur with Emulex driver 1.30a9.

Windows Storage Host Agent Extension None
Bug ID: 158923 / QCCRID 70277

If you run the chpath command as shown below to
take a Storage Host Agent Extension snapshot for
each available path to the device, all the MPIO paths
to a logical device become disabled. In this state,
the system calls used by the diskproxy and mpioproxy
will stop responding.
chpath -l hdisk2 -p fscsi0 -s disable xx

AIX Storage Host Agent Extension None
Bug ID: 159156 / QCCRID 70510

After you update a LUN mapping (and remove the
initiator ports) from a mounted SAN volume on a
server, the old LUN mapping information still
displays in the SAN array volume view and in the
server storage volume view. An additional access
path is displayed in the SAN array volume view
(Access Path subview) for the volume for which
LUN mapping was removed. The access path
that shows no initiator device and/or initiator port
information is the correct one. The incorrect access
path is removed from the display when the next
Storage Host Agent Extension snapshot is run.

independent Storage Host Agent Extension Take a snapshot of the server to which the volume was
mapped or partitioned.
Bug ID: 159580 / QCCRID 70934

The SAV displays incorrect information after adding
a zone to a fabric. The zone is not associated to the
correct server/port/WWN.

independent Storage Host Agent Extension None
Bug ID: 164951 / QCCRID 76305

The multipath information is not reported correctly
for a server that has HP-UX 11iv2 OS installed and
Veritas DMP managing the multipathing in the
SA Client. The SNIA library does not support HBA_GetFcpTargetMappingsV2r.

HP-UX 11iv2 Storage Host Agent Extension None
Bug ID: 168716 / QCCRID 80070

On servers running AIX 5.2 with PCI-X Fibre
Channel Adapters, the supply chain does not
display after taking an inventory snapshot.

Independent Storage Host Agent Extension None
Bug ID:168889 / QCCRID 80243

If you disable a volume in Veritas DMP and
subsequently take a new Storage Host Agent
Extension snapshot, it appears as if the the
updated volume is still managed by Veritas DMP.

Independent Storage Host Agent Extension When constructing LVM modules on the HP-UX 11.31 platform,
use agile DSF devices. There is no workaround for other platforms.
Bug ID: 167103 / QCCRID 78457 If you perform a core upgrade to SA 7.50 and
ASAS 7.50 and then run the customer extension
to upgrade a Storage Host Agent Extension on
the host, the host disappears from the INTERFACE
table and the host's STORAGE_DRIVE does not
appear in the STORAGE_COMPONENT table.
Independent Storage Host Agent Extension It may take one to two hours for the host and drives to repopulate
their tables. Verify that the host is present in the INTERFACE
table and that the STORAGE_DRIVE element is present in the
STORAGE_COMPONENT table.

Virtualization

90019 If a system has more than one virtual network
with the same name, even if those networks
are managed by different hypervisors,
scanning for virtual servers fails due to
a violation of unique name constraints.
Windows Server 2008/Hyper-V Vritualization Do not use duplicate virtual network names.
106085 If your Hyper-V server has more than one IP
address, SA might change the Management
IP address from the one you registered to one
of the other IP addresses.
Windows Server 2008 pre-R2 server Vritualization - Hyper-V To prevent this problem, you need to manage your
Windows 2008 pre-R2 server from a Windows 2008
R2 server and make sure the option to allow the
management operating system to share the network
adapter is not selected. The following gives the basic
steps to accomplish this, however, see your Microsoft
Hyper-V documentation for complete details. More
information may also be available by searching the internet
for "New in Hyper-V Windows Server 2008 R2" and
"Hyper-V Remote Management: You do not have the required
privileges to complete this task."
Make sure the administrators on the pre-R2 and R2 servers
have the same password.
Log on to the R2 server and start the Hyper-V Manager applet.
Right-click on the Hyper-V Manager and select Connect to Server.
In the Select Computer window, select the "Another Computer"
radio button and enter the name of the pre-R2 server.
An icon for the pre-R2 server will appear in Hyper-V Manager.
Select the icon for the pre-R2 server and open the Virtual
Network Manager.
Highlight the NIC whose configuration you need to change.
Under the Connection type, unselect "Allow management
operating system to share this network adapter."
Click OK.
104418 The reported OS property text for ESX servers
is inconsistent between direct (SA Agent) and
indirect managed (vCenter) cases.
VMware ESX (all versions) Vritualization - Backend (VMware) None
105999 After cloning an SA-managed virtual machine, when
the clone starts up for the first time but cannot obtain
network connectivity, agent revival will fail to create a
new server record for the cloned MVM.
Independent Virtualization - Backend (VMWare) Restart the agent on the cloned machine after network
issues are resolved and the agent will correctly register
as a cloned MVM.
106909 Clone Virtual Machine job will fail the Registering
Server step if the Windows Shutdown Event Tracker
is enabled on the source virtual machine. This is
because the Shutdown Event Tracker waits for user
input before it completes rebooting, so the SA Agent
registration cannot complete.
Windows Vritualization Disable the Shutdown Event Tracker on the clone
source virtual server. Windows 2003 x64 cloning
requires a manual reset to resume virtual machine
images customization.
109887 The snapshot view is not available on an ESX server
that is managed by vCenter.
Red Hat Linux Vritualization Manage ESX directly snapshot view.
110035 When a hypervisor that is dual-managed (through
Virtualization Service and SA Agent) loses one of its
management paths (such as when. the Virtualization
Manager or VCenter is removed from SA), the Login
Credentials panel does not display in the server
browser panel and the hypervisor credentials do not
display in the Properties view.
VMWare ESXi Vritualization Right-click on the hypervisor, select "Refresh Server",
and then press F5 (Refresh) to refresh the client so that
the Login Credentials panel displays in the server browser.
111307 If you add an ESXi server with larger hardware
configuration data, the add operation suspends
processing.
ESXi Virtualization - Backend (VMWare) Reconfigure the server with fewer CPU counts in hardware
information.
111780 Hypervisors are not loading. Windows Virtual Center Check that the hypervisor version you are using is supported.
Or check to see if the hypervisor is in a NOT RESPONDING state.
111789 Adding two vCenters concurrently results in
one of the automatically triggered reload data
to suspend processing.
Independent Virtualization - Backend (VMWare) Add the vCenters separately.
111922 The Create Virtual Machine operation on an
SA managed ESX 3.5 server fails with an
error message of com.vmware.vim25.
VirtualMachineConfigSpec.
ESX 3.5 Virtualization - Backend (VMWare)

After the SA 7.5 release, one of the VMM library jar files
was changed from OPSWvmm-vmware.jar to
vmm-vmware.jar. When an upgrade is performed from
SA 7.5 directly to SA 9.0, or from SA 7.5 to SA 7.8 to SA 9.0,
and any virtualization operation is invoked on the ESX
hypervisors, the VMM package gets remediated first with
the new package but the OPSWvmm-vmware.jar file is
left untouched. This causes the consecutive virtual
machine create operations to fail.
The following workaround is intended for any ESX hypervisor
that is managed by an Agent in SA and whose virtualization
aspect will still be handled through the same route (not via VS)
in SA 9.0.

    1. Create a script.
      1. From the Navigation pane, select Library -> By Type -> Scripts ->
        Unix.
      2. From the Actions menu, select New and then enter the following
        information:
        Name: Clean VMM on ESX
        Location: Select Package Repository -> All VMWare Linux ->
        VMWARE ESX Server <any version>
        Script Content:
        1. unlink /opt/opsware/vmm/lib/OPSWvmm-vmware.jar >
        /dev/null 2>&1
      3. Description: Enter a brief description, as necessary.
      4. Leave the defaults for the remaining fields and then select
        File -> Save to save and close the window.<
    2. Create a dynamic device group and add the target servers
      to this device group.
    3. Run the script on the servers in the device group created above.

    Note: This script can be used on all ESX versions.
    There is no need to duplicate it in different packages
    or to create a separate device group for each hypervis
    or version.

111972 Create Virtual Machine fails on a directly
managed ESX hypervisor if the virtual
machine's datastore name contains
special characters.
ESX Virtualization - Backend (VMWare) Change the datastore name so that it does not contain
special characters.
116276 After an SA Agent is installed and before
hardware registration has completed,
you can create or modify a virtual machine
with a memory value that is larger than the
hypervisor's physical memory. The job
completes successfully.
Windows 2008, Windows 2008 R2 Vritualization -
Hyper-V
Run a full hardware registration on the Windows server.
After hardware registration is completed,
SA will not allow you to use memory that is
greater than the maximum memory allowed on a
virtual machine for the actions to create and modify a
virtual machine.

Web Services Data Access Engine

111039 An out-of-memory error is encountered in
the Web Services Data Access Engine
Red Hat Linux/Solaris Web Services Data Access Engine (twist) The default maximum heap size for Web Services
Data Access Engine has been increased to
2560MB from 1280MB.
112222

The Web Services Data Access Engine
does not start and records the error:

Could not reserve enough space for object
heap in:
/var/log/opsware/twist/boot.log

The default maximum JVM heap size has
been increased to 2560 MB, and as a result,
the Web Services Data Access Engine (twist)
does not start properly on Linux AS3 32-bit
systems due to a two-gigabyte memory limit
for a single process running on JVM on 32-bit
systems.

Platform: Red Hat Enterprise
Linux AS3
32-bit
Web Services Data Access Engine (twist)

Before upgrading, edit the file:

/etc/opt/opsware/twist/twistOverrides.conf
and add the following entry:
twist.mxMem=<memory size in Megabytes>
The value must be 2000 megabytes or less.
Example: twist.mxMem=1960m


Back to the Table of Contents

Fixed Issues

This section describes fixed issues for 9.02.
The table lists issues first by subsystem, then numerically within each subsystem.

Table 6: Fixed Issues

QCCRID Symptom/Description Platform Subsystem

AAA

116940

Cannot specify multiple LDAP servers for redundancy.

Support needed for external authentication redundancy for LDAP servers in twistOverrides.conf file.

Independent AAA

Agent

113031 Control Panel of the agent installer displays 0 bytes. Windows Agent Installer
115710 C runtime library runtime error displayed by Opsware agent. Windows 2008 x64 and Windows 2008 R2 Agent Installer
115849 When no options are given on the agent-installer command line, the -h option is not displayed in an error message. Independent Agent Installer
117436 Requested support for passwordless SSH for agent deployment tool (ADT) during agent deployment. Independent Agent Tools
117535 Agent reports the OS version as Linux Unknown instead of the correct OS version. OEL 4.4 i386 and OEL 4.4 x 86_64 Agent
117828 Requested agent installer support for filesystems larger than 2 Terrabytes. Unix Agent Installer
118171 Agent Deployment (including staging the Agent binary to the server through the WAN using SA push) is very slow.
Independent Agent Deployment Tool

APX

117680

APX session timeout is not correctly implemented.

To increase timeout for Web APX Proxy (Note: this must be done at all the Slices on all the Cores):

1. Edit /etc/opt/opsware/apxproxy/apxproxy.conf to specify both the session timeout and socket timeout. Make sure socket timeout is at least equal to session timeout. For example,

apxproxy.apx.session.timeout=1200000
apxproxy.apx.socket.timeout=1200000

2) Edit both /opt/opsware/apxhttpd/conf/httpd.conf.tmpl and /var/opt/opsware/ogfs/mnt/root/opt/opsware/apxhttpd/conf/httpd.conf.tmpl to add a timeout directive. Add this property after the "Server" property. For example,

TimeOut 1200

Remember, unlike apxproxy.conf, the timeout value in httpd.conf.tmpl is in seconds, not milliseconds.

3) Restart the Core.

Independent APX

Audit and Compliance

55463 Hardware audit of CPU should include stepping to allow for CPU comparisons.. Independent Audit and Compliance-
Backend

Application Configuration

111359 Comments and new lines in XML file are not displayed in XML preview even when the preserve format option is active. Independent Application Configuration UI

Application Deployment Manager

111106

When exporting an ADM environment to a device group with targets that contain servers that have been deleted, you received the following error message:

“java.lang.RuntimeException: Unable to update the device group representing the target '[target name]': DeviceGroup or Server deleted during operation, try again.”

Independent Application Deployment Manager
112151

The Application Deployment Manager should warn users in the Job Step output when a Script component times out. There is no indication in the Output area of the job Step details window that a timeout had occurred. This is the window that is displayed when you double-click a job step on the Jobs screen (or in the Debugger) or when you drill-down from the Job details window.

( The Output area in the job Step details window now indicates the reason that a Script component fails.)

Independent Application Deployment Manager
116465

When you create or modify a lifecycle, the list of Available Environments is not sorted, causing problems if numerous environments are listed.

(The list is now sorted alphabetically by name.)

Independent Application Deployment Manager
116612

The following misleading message appears in a pop-up dialog box after the job started when the“Show Jobs screen when deployment starts” option is not selected:

“One or more deployments have been scheduled. View results in the Jobs tab.”

This message is incorrect. At this point, the job is actually running and is no longer in the Scheduled state.

(The message now reads: “One or more deployments have been started.”)

Independent Application Deployment Manager
116707

RPM and MSI packages were imported as type ZIP. The name of the “Import Package” tool used when specifying a Package component is confusing, particularly in the following scenario:

  • If an RPM or MSI file is added to a Package component using the the “Add Package” tool, that RPM or MSI file is copied to the “Default Installation Path” on the target server during deployment.
  • If an RPM or MSI file is added to a Package component using the “Import Package” tool, however, the ZIP file containing the RPM or MSI file is copied to the “Default Installation Path” on the target machine during deployment.

(The name of the button was changed to “Create ZIP Package from Files.”)

Independent Application Deployment Manager
116759

On the Deployment screen, you should not be able to select a Target in an Environment that is not part of the Lifecycle associated with the specified Version.

( Now, only those Targets that belong to Environments that are part of the Lifecycle associated with the specified Version are available.)

Independent Application Deployment Manager
116854

Symptom: Occasionally, the following refresh error message is displayed when the Step details dialog is open while a job is running, and the job failed:
“A data refresh failure has occurred. No further refreshes will occur.”

(The Step details window is now dynamically refreshed to reflect any status changes that occur until the job runs to completion.)

Independent Application Deployment Manager
116867

When a non-superuser with View All Jobs permission, but no Create Applications or Manage Application Deployment permission, views a job that they do not own, the Job Steps and Parameters tables were empty.

(Both the Job Steps and Parameters tables now show the correct information for the job.)

Independent Application Deployment Manager
116880

Automatic backup steps for some components are failing due to timeout errors.

( The timeout for backup steps was increased from 5 to 60 minutes.)

Independent Application Deployment Manager
116883, 117774

In the case where an Environment contained some targets that were suitable for the specified Version and some that were not suitable, the Environment name was “grayed out” in the Select Targets dialog in the Deployment screen. This made it appear that no Targets in that Environment were available when, in fact, some were available.

(All Environments that contain suitable targets are now shown as available.)

Independent Application Deployment Manager
117848

When you create a new deployment on the Deployment screen, the Stage selection should be “Now,” and the Cut Over time should be “Immediately” by default. Instead, the values from the previous deployment are selected - they are not reset.

(The correct default values are now selected.)

Independent Application Deployment Manager
118052

Scripts were not consistently updated during a Patch Upgrade. Some “out of the box” backup and rollback scripts were not properly updated after an SA patch was installed.

(All scripts are now updated when a patch is applied.)

Independent Application Deployment Manager

Core

116991 Debugging files are unusable. Solaris Core - Other
117105 At least two Python C modules fail to compile for reentrancy. Solaris Core - Other

Global File System/ Shell Backend

116994 Core becomes unusable when you attempt to access long file names in the Global Shell (OGSH). ogsh. Linux Global File System/
Shell Backend

Jobs and Session

117956 Custom Range filter not working correctly .in the Jobs and Sessions and History pages of managed servers. Independent Jobs and Sessions

Patch Management

91986 Exception (not error) generated when editing the name of a Windows Patch Policy if the name already exists. Windows Patch Management - UI
116919 RPM remediation fails for some remediations that include a mix of install-only and upgrade RPMs. Linux Patch Management
117667 Text for a patch-installation message that is scheduled for a specific time is truncated. Windows Patch Management - UI

OCC Web - Other

117501 When performing an OS profile edit and uploading a kickstart configuration or an unattend.txt file, the second upload remains in the initializing state, even if the entire upload is completed. Independent OCC Web - Other

OS Provisioning

114962 Requested removal of DOS Boot Install Type for New Windows OS profiles and Modify OS profiles. Windows OS Provisioning - OCC - Web
115542 No network adapters are displayed in ipconfig file when provisioning a DL580G7 server with a CN1000E card that uses the integrated Windows PE 64-bit boot image.
Support for HP StorageWorks CN 1000E (10Gb Ethernet) network cards requested.
Windows OS Provisioning - OCC - Web
117508 Changes to Script Timeout are not saved if you reopen the OS Sequence. Independent OS Provisioning - OCC - Client
117509 Script output to export is limited to 10K for pre- and post-remediate scripts that are attached to an OS sequence. Requested: allow textbox in UI for flexible output size. Independent OS Provisioning - OCC - Client
117604 Gain control over options in the Remediate Policies job spawned by an OS Sequence. Independent OS Provisioning - OCC - Client
117669 When you select servers in the job-progress section during an OS sequence run, the Details pane window closes. The correct behavior is a selection change. Independent OS Provisioning - OCC - Client
117873
/117885
During Windows provisioning, if a driver is not present, the WinPE image does not recognize the NIC card. Windows OS Provisioning - Backend
Windows OS Provisioning - Backend

Search

117830 Search error (" The query was malformed or incomplete.") is received when you run two advanced searches in two different user interfaces, when one of those searches was opened from within the first user interface. Independent Search

Server Groups UI

105997 For the following details panes, the title of the details pane should be the name of the selected View, but instead is the name of the selected Device group: Archived Audit Results, Device Groups, Hardware, Network, Installed Packages
Independent Server Groups UI

Server Management - Managed Servers

106017

Panel title for the Inventory -> Disks view displays incorrect title - it displays the server name.

Independent Server Management - Managed Servers
115884 UI issue: The Servers and Device Groups section of the Reboot Server task window incorrectly displays all reachable Windows servers, instead of displaying only the selected Windows server on a scheduled or completed job. Independent Server Management - Managed Servers
117952

Improper display of multibyte characters when using IIS and COM+ on Korean servers

Windows Server Management - Managed Servers

Spin

116939 Installing satellites on Linux boxes fail if the boxes contain slices that are running SunOS 5.10. Spin fails to link against the libiconv_plug. Solaris Spin

UI

117600 Severe java-console error occurs when you run a server script on a Device Group. Independent UI (DSE)

Back to the Table of Contents

Documentation Errata


This section describes documentation errata.

Application Deployment Manager Context-Sensitive (F1) Help

In the Application Deployment Manager, context-sensitive online help is provided for numerous dialogs, including the Manage Applications and Manage Targets dialogs.

To view a context-sensitive help topic, click the question mark icon in the dialog. Note that the F1 key does not open online help for the Application Deployment Manager.

To view the portion of the SA online help that pertains to application deployment, select Help -> Help in the Application Deployment Manager.

Refer to the HP Server Automation Application Deployment Manager User Guide for additional information.

SA 9.0 Single-Host Installation Guide

Create a User Account with Administrator Privileges (Page 15)

All occurrences of the user Administrator should be replaced with the user System Administrator.
Step 5 should read:
5. Under User Privileges: Group Membership, select the System Administrators user group.

SA 9.0 Simple/Advanced Installation Guide

The following changes affect the version 9.0 SA Simple/Advanced Installation Guide, Chapter 2: System Requirements.

Source Destination Open
Port (s)
Note
Management Desktops Slice Component bundle hosts 80, 443, 8080 Required
Direct access to Oracle database (reports, troubleshooting, management) Model repository (truth) host 1521 Strongly recommended to allow Oracle management
Management Desktops Slice Component bundle hosts 1004, 1018, 1032, 2222 [Optional] Useful for troubleshooting; ports represent spin, way, twist, and ogsh (ssh).
SA Core (Management Gateway) SA Core (Management Gateway) 2001 Required
SA Core (Management Gateway) SA Core in a different Multimaster Mesh (management gateway) 22, 2003 [Optional] For scp (default word replication, can be forwarded over 2001 connection), backup for 2001 if it is busy.
Slice Component bundles SA Agents (in same network) 1002 Required (only for the Agent Gateway managing the Agent).
SA Core (Management Gateway) Satellite/Gateway 3001 Required
SA Core hosts Mail server 25 Required for email notifications
SA Core hosts LDAP server 636 Required for secure LDAP access; port can change if you use unsecure LDAP.
SA Agents SA Core servers and Satellites managing the agent 3001 Required
SA Satellite/Gateway SA Core 2001 Required
SA Satellite/Gateway Managed Agents 1002 Required
BSAe Core Mail Server 25 Required for email notifications
BSAe Core SA Core 1032 Required
BSAe Core BSAe database 1521 Required
BSAe Desktop SA Core 443 Required
BSAe Desktop BSAe Core 8080,8443, 14445 Required
Data Miner (SA Core) BSAe Core 8443, 8873 Required

 

9.0 Simple/Advanced Installation Guide and Oracle Setup for the Model Repository

The following changes have been made to the SA Simple/Advanced Installation Guide and to the Oracle Setup for the Model Repository document, Vault.conf File Changes section (page 196):

The content that reads (note that the first entry truth.sid= is changed to truth.sid:):

truth.sid=(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
rac1-vip.dev.opsware.com)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)
(HOST = rac2-vip.dev.opsware.com)(PORT = 1521)) (LOAD_BALANCE = yes)
(CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = truth)
(FAILOVER_MODE = (TYPE = SELECT) (METHOD = Preconnect) (RETRIES = 180)
(DELAY = 5))))

is changed to read:

truth.sid: (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
rac1-vip.dev.opsware.com)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)
(HOST = rac2-vip.dev.opsware.com)(PORT = 1521)) (LOAD_BALANCE = yes)
(CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = truth)
(FAILOVER_MODE = (TYPE = SELECT) (METHOD = Preconnect) (RETRIES = 180)
(DELAY = 5))))

The following supplements the information about installing the Oracle Client on page 187 of the SA Simple/Advanced Installation Guide and page 183 of the Oracle Setup for the Model Repository document:
The version 11 Oracle Client is not yet compatible with SA, you should use version 10.2.x Oracle Client.

Storage Visibility and Automation User Guide

The following new default values apply to Chapter 2, Asset Discovery:

com.creekpath.agent.common.devices.scheduled.full.sync.max.wait.minutes=10080
com.creekpath.agent.common.devices.full.data.collection.minutes=720
com.creekpath.agent.common.devices.manual.full.sync.max.wait.minutes=10080

Storage Visibility and Automation Installation & Administration Guide

The following new default values apply to Chapter 5, SE Connector:

com.creekpath.agent.common.devices.scheduled.full.sync.max.wait.minutes=10080
com.creekpath.agent.common.devices.manual.full.sync.max.wait.minutes=10080
com.creekpath.agent.common.devices.full.data.collection.minutes=720

Back to the Table of Contents

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

To access the Self-Solve knowledge base, visit the Self-Solve knowledge search home page.

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein
should be construed as constituting an additional warranty. HP shall not be
liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government
under vendor's standard commercial license.

Copyright Notices

© Copyright 2000-2010 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.
Intel® and Itanium® are trademarks of Intel Corporation in the U.S. and other countries.
Microsoft®, Windows®‚ Windows® XP are U.S. registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

Documentation Updates

Latest publication date for this document: September 2011

To check for recent updates or to verify that you are using the most recent edition of a document, go to:
http://support.openview.hp.com/selfsolve/manuals
This site requires that you register for an HP Passport and sign in.
Or click the New users - please register link on the HP Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service.
Contact your HP sales representative for details.

Back to the Table of Contents