HP Server Automation Release Notes

Software version: 9.12


Original Publication Date: March 22, 2012

Server Automation release notes contain information for users who are familiar with the installation and maintenance of Server Automation, Storage Visibility and Automation, SE Connector, Application Deployment Manager, DMA integration, and SA-OO integration. The notes contain information that is not included in books or online Help.

In addition, these release notes contain a Known Issues table and a Fixed Issues table:

Note: The latest information for 9.12 can be found in the latest version of these release notes, located at: http://support.openview.hp.com/selfsolve/manuals.

 

Table of Contents

This document contains the following information:

What's New in This Release

Installation

Known Issues

Fixed Issues

Deprecated Features

Documentation Information

HP Software Support

Legal Notices

 

What's New In this Release

This section describes new functionality and other relevant release-specific information.

For information about what was new in previous releases, please see the corresponding release notes at:
http://support.openview.hp.com/selfsolve/manuals.

Use SA 9.12 Instead of SA 9.11

Due to regression issues (see Using Pre-9.11 SA Agents with SA 9.12), it is suggested that you use SA 9.12 instead of 9.11.


Using Pre-9.12 SA Agents with SA 9.12

After upgrading to SA 9.11, snapshot and audit regression issues occurred if you used a pre-9.11 SA Agent and an established datacenter. Upgraded (9.11) SA Agents execute snapshots and audits using Python Version 2.4. However, snapshots and audits fail with non-upgraded agents (pre-9.11) because they cannot use that version of Python.

SA 9.12 resolves this regression issue and supports both 9.12 and pre-9.12 SA Agents. However, other functionality might not be available if you do not use the 9.12 SA Agents.


Qualified Managed Platforms


The SA 9.12 release provides qualified managed platform support for the following:

Note: Solaris 8 and 9 are no longer supported.

For more support and compatibility information, download the HP Server Automation Support and Compatibility Matrix for this release from the HP Software Support Online web site at: http://support.openview.hp.com/selfsolve/manuals.

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.

Windows Multibinary Patch Support

You can now import and install most Windows multibinary patches, including those that have been traditionally blocked by SA or required fixit scripts. 

Enabling Windows Multibinary Patch Support

To take advantage of the patch-management enhancements in this release, the following steps are required:

  1. Run the clear_winpatch_prereq_override.pyc script on your core servers to allow import of previously blocked patches.
    (See Windows Server Post-Patch Install and Upgrade Tasks for details.)
  2. Run your patch import process to create the patch entry.
    (See the Windows chapter in the SA User’s Guide: Server Patching.)
  3. Update the SA Agent for 9.12 on all the managed servers in the facility to enable new SA functionality..
    (See Updating SA Agents for details.)

Caution: Do not apply any SA-provided fixit scripts after upgrading to SA 9.12. The fixit scripts are only applicable to previous versions of SA. If you encounter an issue with a patch for which there have been fixit scripts in the past, contact SA Customer Support. Applying fixit scripts after applying SA 9.12 will not resolve the issue and could cause an error.

Tip: If you are installing Windows OS Service Packs (SPs), hotfixes, and update rollups, HP recommends that you remediate the server with the desired SP before installing the hotfixes and update rollups. Hotfixes are usually quickly released refinements that are eventually rolled up into the subsequent SP. Isolating the SP into its own policy before running the remainder of the vendor-recommended policy can prevent errors that might result from installing unnecessary hotfixes that are rolled up into the subsequent SPs. 


Agents


Agent Support

SA Agents were upgraded to Python 2.4.4.

Older SA Agents support a limited feature set. Pre-9.10 agent versions are supported only in upgraded cores.

For more information, see the HP Server Automation Support and Compatibility Matrix for this release from the HP Software Support Online web site at: http://support.openview.hp.com/selfsolve/manuals.

Updating SA Agents

After you upgrade to SA 9.12, you should upgrade the SA Agent on each Managed Server in the facility. The latest version of the SA Agent enables you to use new SA functionality. You can continue to use non-upgraded agents, but you will not be able to take advantage of all SA 9.12 functionality. See the SA User’s Guide: Server Automation for information about the Agent Upgrade Tool.

Faster Agent Installation

For more information on installing the agent and bringing servers under SA management, see the SA User Guide: Server Automation.


Application Deployment Manager


Code Component Base Directory Support

This capability enables you to create separate “sandboxes” for code component deployment. This is useful if you want code-component files to only be installed in controlled filesystem locations.

Global and Release Parameters

There are two new types of variables that you can reference in parameter definitions:

Release parameters are available to all components within a release. They are created and managed by the application owner and can be modified by anyone who has permission to edit the application. The value of a release parameter does not change unless it is explicitly modified. A release parameter has the same value within a specific version of the release.

Global parameters are available to all applications. They are created and managed by the Application Deployment administrator. The value specification of a global parameter does not change unless it is explicitly modified by the administrator. The actual value of a global parameter can vary depending on the environment and target.

Automatically Created Directories

For a Configuration File component, the application designer can now instruct the Application Deployment Manager to create the destination directory if it does not yet exist on the target server.

Partial Import/Export

The admtool utility now supports importing and exporting one or more specific applications. You can specify the list of applications to be imported or exported on the command line, or you can specify a CSV file that contains the list of applications. In both cases, the names of the applications must be separated by semicolons (for example: app1;app2;app3).

New admtool Option

Purpose

--exportAppList <list>

Export a list of applications specified on the command line.

--exportAppListFile <file>

Export a list of applications specified in a CSV file.

--importAppList <list>

Import a list of applications specified on the command line.

--importAppListFile <file>

Import a list of applications specified in a CSV file.

Example 1: Export Three Specific Applications

/opt/opsware/da/bin/admtool.sh -e --exportAppList "app1;app2;app3" --exportFile ADM_export.xml
/opt/opsware/da/bin/admtool.sh -e --exportAppListFile app_list.csv --exportFile ADM_export.xml

Example 2: Import Three Specific Applications

/opt/opsware/da/bin/admtool.sh -i --importAppList "app1;app2;app3" --importFile ADM_import.xml
/opt/opsware/da/bin/admtool.sh -i --importAppListFile app_list.csv --importFile ADM_import.xml

Example 3: Preview the Import of Three Specific Applications
/opt/opsware/da/bin/admtool.sh -p --importAppList "app1;app2;app3" --importFile ADM_import.xml
/opt/opsware/da/bin/admtool.sh -p --importAppListFile app_list.csv --importFile ADM_import.xml

Sample contents of the app_list.csv file:

app1;app2;app3;

HP Operations Orchestration Integration

The Application Deployment Manager now supports enhanced logging for HP Operations Orchestration (HP OO) integration, allowing easier auditing of in-bound and out-bound HP OO interactions.


Database and Middleware Automation (DMA)

Single-Click Navigation for DMA Environments

To reduce confusion on the Environment > Dashboard page in the DMA web interface, single-click navigation is now used exclusively. When you click any item in the Environment hierarchy, that item is highlighted in blue, and the following information is displayed:


Item Clicked
Upper Pane Shows Lower Pane Shows

Organization

List of Servers associated with this Organization

Detailed information about the Organization

Server

List of Instances associated with this Server

Detailed information about the Server

Instance

List of Databases associated with this Instance

Detailed information about the Instance

Database

N/A

Detailed information about the Database

The hierarchy associated with the item clicked is highlighted in gray. For example, if you click an Instance, the Server and Organization to which that Instance belongs are highlighted in gray.


OO-SA Integration

Updates pertaining specifically to the OO-SA integration (Server Automation operations performed within Operations Orchestration) are delivered via the HP Live Network at https://www.www2.hp.com/.


OS Provisioning


New Delivery Method for OS Provisioning Build Plan Content

As of SA 9.10, OS Provisioning Build Plan (OSBP) content is uploaded into the SA Core during installation and/or upgrade.

After installing or upgrading to SA 9.12, you must not download OSBP content from the HP Live Network (HPLN). Any automatic jobs you have created to download OSBP content from HPLN must be disabled. If you download OSBP content from HPLN after installing SA 9.12, you will overwrite the SA 9.10 OSBP content that was uploaded during install/upgrade with older SA 9.10 OSBP content, which will cause errors when you attempt to run OS Build Plan jobs under SA 9.12.

Enabling IBM POWER6 Provisioning with the DHCPD Tool

Due to hardware constraints, IBM POWER6 servers cannot be provisioned using the normal OS Provisioning procedures. However, you can enable provisioning for these servers using the dhcpdtool provided with SA.

This involves using the dhcpdtool to set a parameter in the initial subnet declaration which enables Linux OS provisioning on the IBM POWER6 server's hardware. This workaround also requires that SA be in Full DHCP Management mode.

Note: Setting this parameter prevents Solaris SPARC OS provisioning. You will see a warning message to this effect when you change the parameter.

Perform the following tasks to enable Linux OS Provisioning on IBM POWER6 hardware:

  1. Start the dhcpdtool.

    /opt/opsware/dhcpd/sbin/dhcpdtool

  2. Select “Full DHCP Management”.

  3. Select the network for which the workaround is to be applied. An editing menu is displayed:
    Opsware DHCP Network Configuration Tool
       Editing DHCP information for 192.168.208.160/27 (255.255.255.224)
       1) gateway    : 192.168.208.161
       2) DHCP range : 192.168.208.163 - 192.168.208.190
       3) DNS servers: 192.168.194.4
       4) DNS domain : dev.opsware.com
       5) Power6 provisioning override: No
         !!! WARNING: Option 5) breaks Solaris SPARC OS provisioning !!!
         !!! Make sure to deactivate this option before trying to provision a Solaris SPARC machine !!!
       1..5 to edit option.
       d)elete network and return to main menu.
       k)eep network and return to main menu.
       Choice [1..5, d, k]:

  4. Select option 5 and press ENTER.

  5. The message “Are you sure that you want to toggle POWER6 provisioning although it breaks Solaris SPARC provisioning (Enable/Disable)?” is displayed.

  6. Press E to Enable POWER6 provisioning, D to Disable, then select K to keep the settings then S to save them.

  7. Exit the DHCPD tool. Upon exiting, the DHCPD server is restarted and the new setting takes effect.

    Note: If you are not using the SA-provided DHCPD server, you must add the following line to the subnet in which POWER6 you will perform OS provisioning:
               filename "yaboot";


SA-UCMDB Integration

HP Server Automation now integrates with HP UCMDB. You can use the SA-UCMDB Connector to copy data from SA to the HP UCMDB. Whenever the data in SA changes, the SA-UCMDB Connector automatically sends the latest data to the UCMDB.

The HP Universal CMDB is a configuration management database (CMDB) for enterprise IT organizations to document, store, and manage business-service definitions and associated infrastructure relationships. The UCMDB provides a shared single version of truth to support business-service management, IT-service management, change management, and asset management initiatives. These initiatives help align IT efforts with business requirements and run IT operations more efficiently and effectively.

HP Server Automation provides life cycle management for enterprise servers and applications from discovery to provisioning, patching to configuration management, and script execution to compliance assurance. HP Server Automation automates operations and processes across disparate IT teams and systems. HP SA stores a large amount of information about your servers and software in the SA database. You can now leverage this data into the HP UCMDB.

For more information, see the HP SA-UCMDB Integration Guide available at: http://support.openview.hp.com/selfsolve/manuals


Support for Browsers

This table shows browser support information for this release.

  Windows 2003 Windows XP Windows Vista Windows 7 Windows 2008
Chrome

x

x

x

x

x

Firefox 3.0

x

x

x

 

x

Firefox 3.5

x

x

x

x

x

Firefox 3.6

x

x

x

x

x

IE 6.0

x

x

 

 

x

IE 7.0

x

x

x

 

x

IE 8.0

x

x

x

x

x

 

Support for Windows Operating Systems

This section lists the operating-systems supported on the SA Client.


Remediation Scalability Enhancements


In 9.12, remediation performance and scalability have been significantly enhanced. There are two key areas of improvement:

Two new components were introduced to the Slice Component bundle:

To benefit from this enhancement, you must apply the 9.12 patch to each SA Server Agent on each SA Managed Server in the facility.

Note: This enhancement applies only to agents that communicate directly with a Linux-based SA core. You must upgrade your agents to the agent version shipped with the 9.12 patch to benefit from this enhancement. You can continue to use non-upgraded agents, but they will not benefit from this enhancement. See the SA 9.10 User’s Guide: Server Automation for information about the Agent Upgrade Tool. The component services are integrated with the global Start script and are started with the other services. In particular, tsunami and memcached are started with the Slice component bundle components. A new log directory is also created for the tsunami logs:/var/log/opsware/tsunami.

Note: For information about component log files or starting and stopping individual components, see the SA 9.10 Administration Guide.

Performance Considerations

For best results when deploying and using the remediation performance and scalability enhancements in this release, be aware of the following considerations.

Package Locality

When packages are uploaded to an SA core, the packages are associated with the core/facility (locality) in which they were uploaded. When you remediate a software policy against a specific managed host, it attempts to fetch the package from its local software repository or software repository cache.

If the package or packages in question do not reside in the local software repository, the local software repository attempts to fetch the package from the remote software repository where the package is. The package is then served to the managed host by proxy. Depending on the network speeds between cores, this operation can result in a performance penalty that would affect the remediation job.

Recommendation: To achieve the highest levels of performance, you should turn on Software Repository Replication for your mesh. Software Repository Replication was introduced in SA 9.0 and ensures that packages are replicated between cores in the same mesh automatically and frequently, which eliminates the performance overhead associated with proxying remote packages.

Satellite Performance

The initial release of this enhancement includes core-side improvements only. This means that machines reporting to a core via a satellite will not directly benefit from this enhancement. For Satellites that share a local LAN with a core machine (e.g. those used for HA or security boundaries), it is possible to disable the Software Repository Cache component via a customization of your satellite Agent Gateway configurations. 

Recommendation: Contact HP Software Professional Services for more information on customizing Agent Gateway configurations.

Oracle RAC Support

SA supports Oracle Real Application Clusters (RAC).

Note: Oracle RAC support requires a new installation of both Oracle and SA. Therefore, in order to enable Oracle RAC support in SA, you must first install SA and Oracle RAC 10.2.0.4, 11.1.0.7 or 11.2.0.2, configured as described in the following sections.

Prerequisites

This section discusses prerequisites for Oracle RAC.

Database Server Time Requirements

Core servers (either single core or multimaster) and satellite core servers must meet the following requirements. These time requirements do not apply to managed servers.

Linux Time Configuration:

To configure the time zone on a Linux server, perform the following tasks:

  1. Copy or link /usr/share/zoneinfo/UTC to /etc/localtime.
  2. Ensure that the /etc/sysconfig/clock file contains the following lines:
    ZONE="UTC"
    UTC=true

Solaris Time Configuration:

To configure the time zone on a Solaris server, verify that the /etc/TIMEZONE file contains the following line:

TZ=UTC

Supported Oracle Versions

SA support for Oracle RAC includes these Oracle Enterprise Edition versions:

- 10.2.0.4
- 11.1.0.7
- 11.2.0.2

Supported Operating Systems

- Red Hat Enterprise Linux AS 4 x86_64
- Red Hat Enterprise Linux AS 5 x86_64

Set up the Oracle RAC Database/Instances

SA supports any valid Oracle RAC configuration, such as any number of nodes, ASM or regular disks, and so on.

However, SA requires that the Oracle database be configured for use with SA. You will require your Oracle DBA's help to configure the Oracle RAC/instances, the required initialization parameters, the required tablespaces, the opsware_admin database user, and the listener.ora and tnsnames.ora files.

Create the Database with the Required Initialization Parameters

Before installing Oracle, the following scripts must be run and init.ora must have certain parameter values edited or added as shown in Required and Suggested Parameters for init.ora in the SA 9.10 Simple/Advanced Installation Guide, Appendix A.

  1. Create the database.

    Create a database with the UTF8 character set (as required by SA), the data and index files, the default temporary tablespace, the undo tablespace, and the log files.

  2. Create the Required Tablespaces.

    Create the following tablespaces that are required by SA:
    LCREP_DATA
    LCREP_INDX
    TRUTH_DATA
    TRUTH_INDX
    AAA_DATA
    AAA_INDX
    AUDIT_DATA
    AUDIT_INDX
    STRG_DATA
    STRG_INDX

    See “Tablespace Sizes” in the SA Simple/Advanced Installation Guide for additional tablespace sizing information.

  3. Specify the Required and Suggested Parameters for init.ora.

    The file init.ora must be edited as shown in Required and Suggested Parameters for init.ora in the SA 9.10 Simple/Advanced Installation Guide, Appendix A.

  4. Create the User opsware_admin.

    You can use the script, CreateUserOpsware_Admin.sql, to create the opsware_admin database user and grant permissions (privileges) to the user (required by SA) or create the user manually.

Manual Creation of the User Opsware_Admin

If you plan to create the opsware_admin user manually, follow the procedure in this section.

To create the opsware_admin user after a manual Oracle installation, log in to SQL*Plus, and enter the following:

# Su - oracle
# Sqlplus "/ as sysdba"
SQL>create user opsware_admin identified by opsware_admin
default tablespace truth_data
temporary tablespace temp
quota unlimited on truth_data;
grant alter session to opsware_admin with admin option;
grant create procedure to opsware_admin with admin option;
grant create public synonym to opsware_admin with admin option;
grant create sequence to opsware_admin with admin option;
grant create session to opsware_admin with admin option;
grant create table to opsware_admin with admin option;
grant create trigger to opsware_admin with admin option;
grant create type to opsware_admin with admin option;
grant create view to opsware_admin with admin option;
grant delete any table to opsware_admin with admin option;
grant drop public synonym to opsware_admin with admin option;
grant select any table to opsware_admin with admin option;
grant select_catalog_role to opsware_admin with admin option;
grant query rewrite to opsware_admin with admin option;
grant restricted session to opsware_admin with admin option;
grant execute on dbms_utility to opsware_admin with grant option;
grant analyze any to opsware_admin;
grant insert, update, delete, select on sys.aux_stats$ to opsware_admin;
grant gather_system_statistics to opsware_admin;
grant create job to opsware_admin;
grant create any directory to opsware_admin;
grant drop any directory to opsware_admin;
grant alter system to opsware_admin;
grant create role to opsware_admin;
grant create user to opsware_admin;
grant alter user to opsware_admin;
grant drop user to opsware_admin;
grant create profile to opsware_admin;
grant alter profile to opsware_admin;
grant drop profile to opsware_admin;

Installing the Model Repository

In most production environments with Oracle RAC, the Model Repository installation can be done from any SA server. The database server or RAC nodes in this case are considered to be remote.

The examples used in the following sections assume this configuration:

Identity Host Note Name Type Address Address static or dynamic Resolved By
Node 1 Public rac1pub rac1pub (rac1pub.dev.opsware.com) Public 192.168.173.210 Static DNS
Node 1 virtual Selected by Oracle clusterware rac1-vip (rac1-vip.dev.opsware.com) Virtual 192.168.173.212 Static DNS, hosts file, or both
Node 1 private rac1pub rac1prv (rac1prv.dev.opsware.com) Private 172.16.1.100 Static DNS, hosts file, or none
Node 2 Public rac2pub rac2pub (rac2pub.dev.opsware.com) Public 192-168-173-211 Static DNS
Node 2 virtual Selected by Oracle clusterware rac2-vip (rac2-vip.dev.opsware.com) Virtual 192.168.173.213 Static DNS or hosts file
Node 2 private rac2pub rac2prv (rac2prv.dev.opsware.com) Private 172.16.1.101 Static DNS, hosts file, or none
SCAN vip 1 Selected by Oracle clusterware sa_cluster1-scan (sa_cluster1-scan.dev.opsware.com) Virtual 192.168.173.216 Static DNS
SCAN vip 2 Selected by Oracle clusterware sa_cluster1-scan (sa_cluster1-scan.dev.opsware.com) Virtual 192.168.173.217 Static DNS
SCAN vip 3 Selected by Oracle clusterware sa_cluster1-scan (sa_cluster1-scan.dev.opsware.com) Virtual 192.168.173.218 Static DNS

Model Repository Installation on a Remote Database (truth) RAC Server

In an Oracle RAC environment, only one of the RAC nodes is used during the SA installation/upgrade process. The SA Installer connects to only one Oracle RAC instance to install/modify the Model Repository. During the regular SA operations, all RAC nodes are used.

Perform the following tasks on the SA server on which you will run the SA Installer, for example rac1sa.dev.opsware.com.

  1. Model Repository Hostname Resolution

    On the server where you will run the SA Installer, ensure that the Model Repository hostname truth resolves to the remote database server, not to the server on which you will be running the SA Installer:

    In /etc/hosts, enter the public IP address of one of the RAC nodes/instances. For example the /etc/hosts file on rac1sa.dev.opsware.com would have the following entry:

    192.168.173.210 truth rac1pub rac1pub.dev.opsware.com

    If you have set up Oracle Clusterware, you should use the Clusterware scan IP address and DNS name rather than a single database node IP address. For example:

    192.168.173.216 truth sa_cluster1-scan sa_cluster1-scan.dev.opsware.com

  2. Install the Oracle 11g Full Client on the SA server

    Note: For Oracle RDBMS 11.2.0.2, use the Oracle Full Client version 11.2.0.2.

    The SA Installer will use the Oracle Full Client to connect to the database server and install the Model Repository. Below are sample commands for installing the Oracle full client.

    1. Create user oracle for the Oracle Full Client installation:

    root@rac1sa ~]# mkdir -p /u01/app/oracle
    root@rac1sa ~]# mkdir -p /u01/app/oraInventory
    root@rac1sa ~]# groupadd oinstall
    root@rac1sa ~]# groupadd dba
    root@rac1sa ~]# useradd -c "Oracle Client software owner" -g oinstall -G
    dba -d /u01/app/oracle -s /bin/bash oracle
    root@rac1sa ~]# chown -R oracle:oinstall /u01/app
    root@rac1sa ~]# chmod -R 775 /u01/app
    root@rac1sa ~]#passwd oracle (change oracle user password )

    2. Create the .bash_profile file

    In /u01/app/oracle create the .bash_profile file.

    Temporarily comment out ORACLE_HOME and ORACLE_PATH. You will uncomment these entries after the Oracle client installation is complete.

    Sample .bash_profile file

    # .bash_profile

    # Get the aliases and functions
    if [ -f ~/.bashrc ]; then
    . ~/.bashrc
    fi

    # User specific environment and startup programs
    PATH=$PATH:$HOME/bin
    export PATH

    #SA-OracleRAC parameters begin
    #unset USERNAME
    export ORACLE_BASE=/u01/app/oracle
    #export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/client_1
    #PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
    export PATH

    if [ -t ]; then
    stty intr ^C
    fi

    umask 022

    #SA-OracleRAC parameters end

    3. Install the Oracle Full Client

    Install the Oracle Full Client as described in your Oracle documentation. You can create a share to access the Oracle Full Client binaries.

    4. Set Up Terminals

    You will need two X window terminals to install the Oracle Full Client:

    Terminal 1: log in as root and enter the commands:

    Terminal 1> xhost +
    Terminal 2: ssh –X oracle@<new_oracle_full_client_host>

    5. Start Oracle Full Client installation

    From Terminal 2 run the Oracle Universal Installer (OUI) installer. The Oracle Full Client is installed in:

    /u01/app/oracle/product/11.2.0/client_1

    6. Run the Oracle Universal Installer to install Oracle Full Client. The directories in this example assume an Oracle 11g Full Client on Linux.

    a. cd /location_of_oracle_full_client
    b. /runInstaller
    c. At the Welcome Screen, click Next.
    d. Specify the Inventory Directory and Credentials (/u01/app/oraInventory and /u01/app/oinstall)
    e. For Select Installation Type, choose Administrator, click Next.
    f. For ORACLE_BASE select: /u01/app/oracle, click Next.
    g. The Oracle Universal Installer performs some checks. If the checks are not successful, fix the issue and re-run this step. If the checks are successful the click on 'Next'
    h. Oracle OUI will list of products that will be installed. Click on 'Install'
    i. OUI will show the progress bar when installing
    j. On the 'Welcome to Oracle Net Configuration Assistant' window click on 'Next'
    k. Click on 'Finish' once the installation is complete.
    l. The following two configuration scripts must be executed as "root" upon installation completion:
    – /u01/app/oraInventory/orainstRoot.sh
    – /u01/app/oracle/product/11.2.0/client_1/root.sh

    7. Verify that the .bash_profile file for user oracle is correct.

    8. Uncomment $ORACLE_HOME and $ORACLE_PATH.

Making changes to tnsnames.ora on an SA server

By default the tnsnames.ora file is located in /var/opt/oracle.

Login as root on the SA Server.

Enter the command:

mkdir -p /var/opt/oracle

Copy tnsnames.ora from the remote database server to the directory you created above.

For the RAC environment, copy tnsnames.ora from RAC Node 1 (for example, rac1pub.dev.opsware.com).

To accommodate the remote Model Repository installation process, two sets of tnsnames.ora are required on the SA server.

- tnsnames.ora-install_upgrade – this copy of tnsnames.ora is used during SA installation/upgrade. The file can be renamed.

- tnsnames.ora-operational– this copy of tnsnames.ora is used during normal SA operation. The file can be renamed.

You can use softlinks to point tnsnames.ora to either tnsnames.ora-install_upgrade or tnsnames.ora-operational. For example:

ln –s tnsnames.ora-install_upgrade tnsnames.ora

Testing the connection from the SA host to the database

Before starting the Model Repository installation/upgrade, you can perform the following tests to verify that your tnsnames.ora file is configured correctly and if the SA Installer can connect to the database in restricted mode.

  1. Verify that the SA server's /var/opt/oracle/tnsnames.ora file is configured correctly as described in Making changes to tnsnames.ora on an SA Server.
  2. On the SA server:

    a. Login as oracle or root or su – twist/spin – if these users exist.
    b. Export ORACLE_HOME=/u01/app/oracle/product/11.2.0/client_1 (or where you installed the Oracle Full Client).
    c. Export LD_LIBRARY_PATH=$ORACLE_HOME/lib.
    d. Export TNS_ADMIN=/var/opt/oracle.
    e. Set $PATH $ORACLE_HOME/bin path.
    f. sqlplus sys/password@RAC1SA_TRUTH as sysdba.
    where RAC1SA_TRUTH is the service_name or entry from the tnsnames.ora file.
    g. Connect opsware_admin/<password>@RAC1SA_TRUTH.

    If you are able to logon to the database, then all files are configured correctly.

SA Installer Response File

You can now start the installation of the SA Model Repository. Ensure that you have the correct parameter values for the installation interview or that you have a previous response file.

- %db.sid: truth1 (Oracle SID of the instance where SA installer is going to connect to.)

- %db.orahome: /u01/app/oracle/product/11.2.0/client_1 (oracle client home)

- %db.port: 1521 (Oracle listener port)

- %truth.tnsdir-/var/opt/oracle (client's tnsnames.ora file)

- %db.host: 192.168.173.210 (server where Oracle RDBMS is installed)

- %truth.servicename: rac1sa_truth (value of service name from tnsnames.ora file)

You can now install the SA core as described in the SA Simple/Advanced Installation Guide.

Post SA installation process

After you install the SA core, perform the following tasks in order to use all the nodes in the Oracle RAC environment.

Making changes to tnsnames.ora on the SA server

After SA install is complete, the tnsnames.ora file should point/link to the tnsnames.ora-operational file.

In an Oracle RAC environment, only one of the RAC nodes or instances is used during the installation/upgrade process. The SA Installer connects to only one Oracle instance to modify the Model Repository. During the normal SA operations, all the RAC nodes are used.

To accommodate the remote truth installation process, two sets of tnsnames.ora are required on
the SA server.

- tnsnames.ora-install_upgrade – this copy of tnsnames.ora is used during SA installation/upgrade. You can rename the file.

- tnsnames.ora-operational – this copy of tnsnames.ora is used during normal SA operation. You can rename the file.

You can use softlinks to point tnsnames.ora to either tnsnames.ora-install_upgrade or
tnsnames.ora-operational:

ln –s tnsnames.ora-operational tnsnames.ora

tnsnames.ora-install_upgrade

# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_2/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.

RAC1SA_TRUTH =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1pub.dev.opsware.com)(PORT = 1521))
(CONNECT_DATA =
(UR=A)
(SERVER = DEDICATED)
(SERVICE_NAME = truth)
)
)

RAC2SA_TRUTH=(DESCRIPTION=(ADDRESS=(HOST=192.168.173.214)(PORT=20002)(PROTOCOL=tcp))(CONNECT_DATA=(SERVICE_NAME=truth)))

 

tnsnames.ora-operational sample file

Note: If you have set up Oracle Clusterware, you should use the Clusterware IP address rather than a single database node IP address.

Make a note of the text that is in BOLD letters. This tnsnames.ora file is used during normal SA operation and contains the RAC parameters.

tnsnames.ora-operational sample file - with Clusterware setup

If you have set up Oracle Clusterware, use the following:

#This entry is for connecting to RAC virtual machines. This entry is used by SA during operation of SA.

RAC1SA_TRUTH =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = sa_cluster1-scan)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = truth)
(FAILOVER_MODE =
(TYPE = SELECT)
(METHOD = Preconnect)
(RETRIES = 180)
(DELAY = 5))

)
)

#This entry is for connecting to node2 via service_name. This is for DBA convenience. This is not used by SA.

TRUTH2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2pub.dev.opsware.com)(PORT = 1521))
(CONNECT_DATA =
(UR=A)
(SERVER = DEDICATED)
(SERVICE_NAME = truth)

)
)

#This entry is for connecting to node1 via service_name. This is for DBA convenience. This is not used by SA.

TRUTH1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1pub.dev.opsware.com)(PORT = 1521))
(CONNECT_DATA =
(UR=A)
(SERVER = DEDICATED)

(SERVICE_NAME = truth)
)
)

#This entry is added by SA and is used by SA during regular operation.

RAC2SA_TRUTH=(DESCRIPTION=(ADDRESS=(HOST=192.168.173.214)
(PORT=20002)
(PROTOCOL=tcp))
(CONNECT_DATA=(SERVICE_NAME=truth)))

tnsnames.ora-operational sample file - without Clusterware setup

If you have not set up Oracle Clusterware, use the following:

#This entry is for connecting to RAC virtual machines.

TRUTH =
(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))
)
)
LISTENERS_TRUTH =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.dev.opsware.com)(PORT = 1521))
)


#This entry is for connecting to node2 via service_name. This entry is optional. This is for DBA convenience. This is not used by SA.


TRUTH2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.dev.opsware.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = truth)
(INSTANCE_NAME = truth2)
)
)
LISTENER_TRUTH2 =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.dev.opsware.com)(PORT = 1521))

#This entry is for connecting to node1 using service_name. This entry is optional. This is for DBA convenience. This is not used by SA.


TRUTH1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = truth)
(INSTANCE_NAME = truth1)
)
)
LISTENER_TRUTH1 =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521))

#This entry is added by SA and is used by SA during regular operation.

RAC2SA_TRUTH=(DESCRIPTION=(ADDRESS=(HOST=192.168.173.214)
(PORT=20002) (PROTOCOL=tcp))(CONNECT_DATA=(SERVICE_NAME=truth)))

Use softlinks to link the file to tnsnames.ora file after SA installation is complete and you are ready to start SA in operational mode.

ln –s tnsnames.ora- operational tnsnames.ora

During installation, the SA Installer adds an SA Gateway entry into tnsnames.ora (linked to
tnsnames.ora.install-upgrade) file on the First SA core. When installation is complete, copy that entry into tnsname.ora.operational. If this entry is not present in the tnsname.ora.operational, Multimaster Mesh transactions will not flow. The following is a sample gateway entry from tnsnames.ora:

Rac2sa_truth=(DESCRIPTION=(ADDRESS=(HOST=192.168.173.214)(PORT=20002)(PROTOCO
L=tcp))(CONNECT_DATA=(SERVICE_NAME=truth)))

vault.conf File Changes

Note: If you have set up Oracle Clusterware, you should use the Clusterware IP address rather than a single database node IP address.

In an Oracle RAC environment, the vault.conf file must be modified after SA installation is complete. Modify /etc/opt/opsware/vault/vault.conf to specify the complete tnsname definition instead of the SID. For example:

If you have set up Oracle Clusterware, use the following:

Before:

truth.sid: truth1

After:

#truth.sid: truth1
truth.sid: (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = sa_cluster1-scan)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =(SERVER = DEDICATED)
(SERVICE_NAME = truth)
(FAILOVER_MODE = (TYPE = SELECT)
(METHOD = Preconnect)(RETRIES = 180)(DELAY = 5))))

If Oracle Clusterware is not setup, use the following:

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))))


truth.port: 1521

Also, ensure that these values are correct:

truth.port: 1521
truth.host: 192.168.173.210
(database server IP)
truth.servicename: rac1sa_truth (tnsnames.ora enter)

- Restart the vaultdaemon:

/etc/init.d/opsware-sas restart vaultdaemon


Changing the da.conf Configuration File

In SA 9.10, the Application Deployment Manager reads database connection information from the tnsnames.ora file.

In SA 9.10 and 9.1x, the default was SID =Truth unless changed by the user, for example, in /etc/opt/opsware/da/da.conf:

truth.sid=truth1 (this is the Oracle SID of the instance on RAC node)

Changes to /opt/opsware/oi_util/startup/opsware_start.config

Note: If you have set up Oracle Clusterware, you should use the Clusterware IP address rather than a single database node IP address.

- TRUTH_HOST="192.168.173.210" - If Clusterware is not set up, then set the TRUTH_HOST value to one of the node's hostnames or public IPs.

- TRUTH_HOST="sa_cluster1-scan.dev.opsware.com" - If Clusterware is set up, then set the  TRUTH_HOST value to the Clusterware scan name.

Upgrading the Model Repository

To upgrade the Model Repository in an Oracle RAC environment, follow the same procedure as Installing the Model Repository. If you are doing a remote database installation, ensure that you modify your tnsnames.ora on the server where the SA Installer is run. It is recommended that you test the connection as suggested in section Testing the connection from the SA host to the database.

Back to the Table of Contents


Installation

This section describes the SA 9.12 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.

See the SA installation guides for more installation information.

General Information

Script Running Order

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

SA Script Running Order - Upgrade

Upgrade From

To

Script Running Order

9.10

9.12

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

9.10.02

9.12

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

SA Script Running Order - Rollback

Rollback From

To

Script Running Order

9.12

9.10

  1. patch_opsware.sh
  2. patch_database.sh

 

Adobe Flash Player and HP BSA Launcher Issues

Certain SA Client features (such as Run OS Build Plan or HP UX Provisioning) require the Adobe Flash Player. If you try to run these features, and you have not yet installed Adobe Flash Player, you will get an error. If you subsequently install the Player on a machine where you have already installed HP BSA Launcher, and try to run the same features, the error message will still be displayed, even though you have already installed the Player.

To make sure Adobe Flash Player functions correctly and to avoid the error message, you should:

  1. Make sure that Adobe Flash Player is installed correctly (access the following site: http://www.adobe.com/software/flash/about/).
  2. Stop any instances of the SA Client.
  3. Uninstall HP BSA Launcher.
  4. Reinstall HP BSA Launcher (1.5.0 or later).
  5. Restart the SA Client and run the features normally.

The error message should not be displayed.

 

Database Schema Update Procedure

Required only if you have not previously applied the SA 9.12 patch. The script run during this procedure makes required changes to the Model Repository including adding required tables and objects.

  1. Mount the SA 9.12 distribution. Invoke patch_database.sh on the Model Repository host:

      <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:

    1. 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
    2. Enter i at the prompt to begin the database update.
    3. 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.

  2. 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.

Dual Layer DVD Requirements

All SA installation DVDs require a DVD drive that supports dual layer.

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.12:

  1. Mount the SA 9.12 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 previously patched with a 9.1x patch, 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.12 to SA 9.10, 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

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-Installation Tasks

This section lists the tasks that should be performed after you install SA 9.12. Some tasks might not be appropriate for your situation.

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.12 patch. SA 9.12 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.12 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:

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 upgrading to SA 9.12, you must update the SA Agent on that server to the latest version. Errors occur during OCLI installation on Windows servers with earlier SA Agent versions.


Windows Server Post-Patch Install and Upgrade Tasks

Note: These instructions are for SA 9.12 fresh installs and upgrades.

Use these instructions to import Windows multibinary patches that have been traditionally blocked by SA or fixit scripts (such as MS11-078.pyc).

  1. To allow import of previously blocked patches, run these commands on the SA core server with the Software Repository component after installing or upgrading to SA 9.12:

    # cd /opt/opsware/mm_wordbot/util
    # export PYTHONPATH=/opt/opsware/pylibs2
    # python clear_winpatch_prereq_override.pyc -c -d

    The clear_winpatch_prereq_override.pyc script has the following options:

  2. Option Description
    - c Clears out the blocked patches
    - d

    Displays the current value

    Note: You can run the script with just the –d value to see the current value.
  3. Run the patch-import process based on your network configuration.
    1. Re-download the path metadata.
    2. Import the binary for the newly detected multibinary patches.

    (See the Windows chapter in the SA User's Guide: Server Patching for additional details.)

  4. Update the SA Agent for 9.12 on each managed server in the facility to enable new SA functionality, including support for Windows multibinary patches. (See Updating SA Agents for details.)

Important: The SA Agent must be updated before you scan and remediate the servers.

Back to the Table of Contents

Installing Slices

If you install additional Slice Component bundle instances after patching the SA Core to version 9.1X, wayscript versions are set to version 9.10 rather than to the patch version. Use the following procedure to remedy the situation:

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_OPSWwayscripts.
  3. Log in to the SA Core server you identified in step 1 and execute the following two commands:

    Command #1:
    cd /var/opt/opsware/OPSWpatch/OPSWwayscripts/scripts

    Command #2:
    ./post_after_startup.sh
  4. Apply any required hotfixes to the wayscripts.

Updating Server Agents

After you upgrade to SA 9.12, you should upgrade the Server Agent on each Managed Server in the facility. The latest version of the Server Agent enables you to use new SA features. You can continue to use non-upgraded Agents, you will not be able to take advantage of all SA 9.12 functionality. On any server on which you must run the SA Command Line Interface (OCLI), you must upgrade the server’s Agent to SA 9.12 in order to continue using OCLI. See the SA User’s Guide: Server Automation for information about the Agent Upgrade Tool.

Upgrades

 

Customized Settings

If you have customized such settings as Java heap settings, you must reapply your customizations after you install 9.12, as the settings are set to the SA default during installation or upgrade.

Windows Multibinary Patches

If you plan to import Windows multi-binary patches that have been traditionally blocked by SA or fixit scripts (such as MS11-078.pyc), see Windows Server Post-Patch Upgrade and Install Tasks in the Install section.

Back to the Table of Contents


Known Issues

This section describes cumulative known issues for 9.0, 9.01, 9.02, 9.03, 9.10, 9.11, and 9.12. The table lists issues first alphabetically by subsystem, then numerically within each subsystem.

Known Issues

QCCR1D Symptom/Description Platform Subsystem Workaround

Agent

QCCR1D100660 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.
QCCR1D107917 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

QCCR1D110347

Windows servers running a pre-9.12 agent can perform a scan on an upgraded 9.12 core but not on a freshly installed 9.12 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.12.

 

QCCR1D111593 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.

QCCR1D118437

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 SA Agent deployment.

 

QCCR1D123031

Reprovisioning for Red Hat Enterprise Linux 6 with the ext4 file system is not yet supported.

Linux   None
QCCR1D144308

On servers where there is no locale installed other than POSIX or C, agent installation appears successful but SA still displays the server with an unmanaged status.

AIX 5.3 Agent Install and use a locale (such as en_US) instead of the default locale (POSIX or C).

Application Configuration

QCCR1D50099 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.
QCCR1D111765 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.

APX

QCCR1D116476

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 millisecond.

  3. Restart the SA Core.

Audit and Remediation

QCCR1D81308 An erroneous status is displayed when remediation of registry and COM+ objects fails.
Windows Audit and Remediation - Backend None

BSA Essentials Dataminer

QCCR1D112784

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

Independent BSA Essentials Dataminer None.

Command-Line Interface (CLI)

QCCR1D118249

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

Database Scanner for Oracle

QCCR1D88091 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.

 

 

QCCR1D91143

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.
QCCR1D133226

In order to monitor an Oracle 11G database with the SA Oracle Database Scanner, the XML DB and DBMS_NETWORK_ACL_ADMIN package must exist in the database. 

The SA Oracle DB Scanner needs access to these objects in order to grant privileges and access for itself. If the objects do not exist, then the "pamuserprivilege.sql" will fail and the DB Scanner cannot be run.   An application may or may not install these objects in its Oracle 11G database.

The following error might be displayed under these circumstances:
"PLS-00905: object SYS.DBMS_NETWORK_ACL_ADMIN is invalid". 

Independent

Database Scanner for Oracle

Before executing the SA DB Scanner "pamuserprivilege.sql" in the Oracle database, first perform the following steps to install the XML DB and DBMS_NETWORK_ACL_ADMIN package in the Oracle 11G database.

1) cd $ORACLE_HOME/rdbms/admin
2) sqlplus /nolog
3) SQL> connect <sys_user>/<password> as sysdba
4) SQL> spool install_xml.log
5) SQL> @catqm xdb sysaux temp NO
6) SQL> @dbmsnacl.sql
7) SQL> spool off;

Database and Middleware Automation (DMA)

QCCR1D133378 Workflow cancellation indicates success in the DMA Console, but workflow runs to completion on SA managed server. Independent DMA Use the appropriate process manager for the managed server's Operating System (for example, kill for UNIX and Task Manager for Windows) to manually terminate the process. 

Installer

QCCR1D100931

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 incompatible 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
QCCR1D111215

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
QCCR1D114346 ADT works after third try. Redhat Enterprise Linux 5 S390X , SuSE Enterprise Linux 10 S390X and SuSE Enterprise Linux 11 S390X Installer

Install uudecode utility.

QCCR1D114639

If you install additional Slice Component bundle instances after patching the SA Core to version 9.1X, wayscript versions are set to version 9.10 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_OPSWwayscripts.
  3. Log in to the SA Core server you identified in step 1 and execute the following two commands:
    Command #1:
    cd /var/opt/opsware/OPSWpatch/OPSWwayscripts/scripts

    Command #2:
    ./post_after_startup.sh
  4. Apply any required hotfixes to the wayscripts.
QCCR1D132004 Health check fails with mismatched core component version errors (check_occ_up, lnxisoupload, new_platforms, opswbia_upload) Independent Installer None

ISM Tool

QCCR1D110511

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.

OS Provisioning

QCCR1D90667 BCS imported as multiple platform object is not listed during OS Profile creation. Linux OS Provisioning None
QCCR1D100928

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
QCCR1D102830 Cannot modify or enter a timeout value for pre/post remediate scripts while creating a new OS Sequence. Independent OS Provisioning - SA Client None.
QCCR1D103362

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 - SA Client None.
QCCR1D103602

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 Use the CSV import to generate the pre-unprovisioned devices.
QCCR1D104194

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.

QCCR1D104739 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.
QCCR1D109077

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.
QCCR1D111245

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
QCCR1D111445

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.
QCCR1D111781

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.
QCCR1D114523

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

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

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.

 

Red Hat Linux

 

OS Provisioning - MBC 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.
QCCR1D115063

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.
QCCR1D118372

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.
QCCR1D122908 Multipath IO OS Sequences Failing on Linux RHEL5 (physical system) Red Hat Enterprise Linux 5 OS Provisioning Backend

Modify the server's OS Provisioning configuration files as follows:

1. Add the kernel_arguments custom attribute to the OS Installation Profile and set the value to mpath.

2. Add a %pre script to the kickstart file specified by the OS Installation Profile and add the following:

mkdir -p /opsw
mount CORE_IP:/opt/opsware/boot/kickstart/rhel50 /opsw

cp /opsw/miniagent /tmp
/tmp/miniagent --server CORE_IP 8017

Where CORE_IP is the IP address of the SA Core.

QCCR1D129619 ESXi DHCP-LESS: DNS Search Domain was not set via the DHCP-LESS value VMware ESXi 4.1 OS Provisioning Backend None. Anything entered in the "DNS Search Domain" field is inserted into the custom attribute as domain=. Therefore, the DNS domain will not be inserted to the ESXi 4.1 system.
QCCR1D131265 Manage Boot Client utility: WAPX sometimes fails at the second step with: 503 Service Unavailable Error Independent OS Provisioning Backend In the Global File System (GFS), use the /opsw/apx/bin/osprov/manage_boot_clients_script.
QCCR1D132628 SUSE Linux Enterprise Server provisioning fails on an HP ProLiant server with a CCISS disk. HP-UX OS Provisioning

For post-SUSE Linux Enterprise Server 10 SP2 provisioning on HP ProLiant servers with CCISS disks, ensure that the <code1>autoyast.xml</code1> file has the partitioning configuration specified as shown below:

<partitioning config:type="list">
<drive>
<use>all</use>
<partitions config:type="list">
<partition>
<mount>/boot</mount>
<size>100mb</size>
<partition_type>primary</partition_type>
</partition>
<partition>
<mount>swap</mount>
<size>1gb</size>
<partition_type>primary</partition_type>
</partition>
<partition>
<mount>/</mount>
<size>max</size>
<partition_type>primary</partition_type>
</partition>
</partitions>
</drive>
</partitioning>

QCCR1D132825/130199

During provisioning in a  non-DHCP environment, Red Hat Enterprise Linux 6 provisioning can become interactive if the HPSAlinux_boot_cd.iso remains connected.

Red Hat Enterprise Linux 6 OS Provisioning Backend Eject the boot CD when the server reaches the restart phase or after provisioning becomes interactive.
QCCR1D133102 Reprovisioning using the custom attribute boot_kernel=rhel50 causes reprovisioning issues. Red Hat Enterprise Linux 5

OS Provisioning

For Red Hat Enterprise Linux reprovisioning, do not use the custom attribute boot_kernel or set it to rhel60.
QCCR1D133153 VMware ESX 4.1 OS Sequence with OS firewall enabled fails with a broken pipe exception during the Agent download phase. VMware ESX 4.1

OS Provisioning

The firewall should be disabled during OS Provisioning and re-enabled after.

QCCR1D136144

Running a single OS Sequence job against two servers with the same MAC address in different networks causes an exception.

Independent OS Provisioning - Backend

If you have servers with the same MAC address in different networks, you must provision them sequentially. For example,  complete the Run OS Sequence job on the first server before you power on the second server.

QCCR1D136423

Provisioning dupe-mac Linux servers sequentially into a managed server, then reprovsioned the servers simultaneously should result in a Run OS Sequence job error.

Linux OS Provisioning None
QCCR1D136445

If you attempt to register another server with the same MAC address as a mini agent after a server is in the OS Provisioning lifecycle, the Run OS Sequence job on the first server fails.

Independent OS Provisioning

Follow these instructions:

  1. Shut down the second server.
  2. Reboot the first server.
  3. Re-register the first server as a mini-agent.
  4. Re-run the OS Sequence steps.
QCCR1D136592

After a server is registered with SA as miniagent, if you then attempt to register a second server with the same MAC address (but with a different service operating system than the first server) as a miniagent, the registration fails. Then, if you shut down the second server as instructed, the Run OS Sequence job against the first server fails with an error.

Linux OS Provisioning

When this problem occurs, you must

1. Ensure the second server remains shut down
2. Reboot the first server and  re-register it with SA as miniagent
3. Run the Run OS Sequence job against the first server again

Patch Management for Solaris

QCCR1D100566

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.
QCCR1D111342

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.
QCCR1D114156

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.12, 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.
QCCR1D130601

solpatch_import: Import "Fujitsu Solaris 10 OS Recommended Patch Cluster" fails with 'KeyError: 'patch_order.SS' on a Solaris core. The following error displays when importing a large cluster on an older Solaris core:

bash-3.00# echo Fujitsu Solaris 10 OS Recommended Patch Cluster | ./solpatch_import -a import
Importing patch cluster Fujitsu Solaris 10 OS Recommended Patch Cluster note: didn't find end-of-central-dir signature at end of central dir.
(please check that you have transferred or created the zipfile in the appropriate BINARY mode and that you have compiled UnZip properly)

Solaris Patch Management - Solaris - Backend Import a specific patch on your core. See the article from Oracle at https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1020109.1.
QCCR1D132332 After upgrading to SA 9.12, you must manually run update_supplements to see new clusters, such as Fujitsu clusters. Solaris Patch Management - Solaris

SA 9.12 provides new clusters (Fujitsu clusters for Solaris 10) in the Solaris collection file.

This workaround applies to a mesh that contains different SA cores (such as SA 7.84 or SA 9.12), where the mesh has Solaris patching configured (solpatchdb). After the mesh has been upgraded to SA 9.12, the following command must be manually run on a core server (slice):

/opt/opsware/solpatch_import/bin/solpatch_import -a update_supplements

This command loads the new collection file into solpatchdb.

To see all available clusters, including the new clusters, run the following command:

/opt/opsware/solpatch_import/bin/solpatch_import -a show --available_clusters

QCCR1D138928

Solaris Recommended Clusters cannot be imported into SA when the SA core server has a version of unzip that does not support large Solaris Cluster zip files.

SunOS Solaris server patching

To resolve this issue, update the unzip tool to v.6.0 on the SA core server before importing the recommended Solaris Clusters into SA.

To update the unzip tool on the SA core server:

  1. Rename the current unzip tool in /usr/bin/ to unzip_OLD.
  2. Copy the unzip file that is shipped with SA under /opt/opsware/bin/.
  3. Paste the new unzip into the /usr/bin directory.

Patch Management - Windows

QCCR1D102713

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.
QCCR1D105098

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.
QCCR1D108451

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.
QCCR1D110257

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
    QCCR1D 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.
QCCR1D108451

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

 

Windows Server 2008 x86

Patch Management - Windows - Backend Log on to the managed server and install the patch for KB944036 manually.
QCCR1D111397

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.
QCCR1D136373

Windows systems that use .cab files for remediation time out during the installation process for a vendor recommended policy. When installing multiple .cab files without reboot, calls to the Windows API UpdateSearcher.Search do not return in a timely manner, causing the timeout.

Windows Patch Management - Windows - Backend After the remediation job fails (due to the timeout), reboot the server to complete the timed out job and then run the remediation job again.
QCCR1D130284 Install patch Q979309 failed on a Windows 2008 R2 server with exit code 4. Windows Patch Management - Windows - Backend Install KB978601 and KB979309.
QCCR1D131240 If you do not have the SA 9.10 Agent installed on a managed server, the Reboot Server option will not change the server's Reboot Required state from "Yes" to "No". Windows Patch Management - Windows - Backend Upgrade the Agent on your managed server to the SA 9.10 Agent and then reboot the server. The server's Reboot Required state will then accurately display the state as "No".
QCCR1D140751

Attempts to install the Windows KB929300 multi-binary patch without including all the binaries in the SA patch policy remediation job will fail with the following error and stack trace:

The operation to install or uninstall software failed.Execution error: Traceback (most recent call last):
File ".\base\wayfuncs.py", line 136, in evaluator
File "", line 7177, in ?
File "", line 7171, in main
File "", line 6872, in action
File "", line 6346, in actionImpl
File "", line 0, in ?
File "", line 5044, in install
File "", line 4987, in getResult
TypeError: int() argument must be a string or a number

Note: In this example for KB929300, at least 4 binaries were missing from the job.
Windows Patch Management - Windows To resolve this issue, include ALL binaries from the multi-binary patch in the SA patch policy remediation job.

SA Client (Framework)

QCCR1D105671

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.
QCCR1D115211 Launching the SA Client under Windows Vista or Windows 7 causes flickering/redrawing of the screen. Windows Vista, Windows 7 SA Client Framework Disable the Windows Aero graphical user interface and/or use the Windows Classic display.
QCCR1D115403 The SA Client freezes when any of the following items is launched for the first time: Application Deployment, Web Automation Platform Extension (APX) processes (including OS Build Plans and HP Virtualization), and reports. Windows SA Client Framework

Use the Applications tab in the Windows Task Manager to stop the SA Client. Restart the SA Client.

SA Client (Search)

QCCR1D66448 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

QCCR1D90653

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

QCCR1D102614

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.0 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 Web Services Data Access Engine (twist):
    /etc/init.d/opsware-sas start twist
QCCR1D133085

OO servers use a certificate that is bundled with SA 9.10 and that is used to connect SA to OO. This certificate expires May 21, 2011. As of today, a newer OO certificate is not available to bundle in SA.

The certificate will be updated when you apply the next OO patch, but, as a consequence, the SA OO integration will fail. If this happens, you must manually import the certificate into SA.

Note: If you do not update OO, the integration will continue to work.

 


Independent SA-OO

To manually install the certificate:

  1. Stop the Web Services Data Access Engine.
  2. Transfer the OO certificate to SA:
    1. /opt/opsware/jdk1.6/jre/bin/keytool -exportcert -alias pascert -file /tmp/oocentral.crt -keystore /var/opt/opsware/twist/oocert
    2. /opt/opsware/jdk1.6/jre/bin/keytool -importcert -alias pas -file /tmp/oocentral.crt -keystore /opt/opsware/jdk1.6/jre/lib/security/cacerts
  3. Check that the OO Central Certificate was imported successfully:
    1. /opt/opsware/jdk1.6/jre/bin/keytool -list -alias pas -keystore /opt/opsware/jdk1.6/jre/lib/security/cacerts
  4. Start the Web Services Data Access Engine.

When a new OO certificate becomes available, use the following process to install it:

  1. Stop the Web Services Data Access Engine.
  2. Transfer the OO certificate to SA:
    1. Manually obtain the new OO certificate.
    2. Save it in: /tmp/oocentral.crt
    3. Enter the following command:

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

  3. Check that the OO Central Certificate was imported successfully:
    /opt/opsware/jdk1.6/jre/bin/keytool -list -alias oocentral -keystore /opt/opsware/jdk1.6/jre/lib/security/cacerts
  4. Start the Web Services Data Access Engine.

If you follow this second process, the new and old certificates can coexist on the server. Co-existence might be useful if SA integration with an older OO is required.

If you want to use the same alias name (pas alias), you must delete the older certificate first:

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

SA/SAR Reports

QCCR1D82108

In the SA Client in an NA-enabled 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
QCCR1D107293 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.
QCCR1D110658

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-UCMDB Integration

141512

If you are running HP DDMA, and both SA and DDMA are reporting data to the HP UCMDB, some duplicate Configuration Items may be created in the UCMDB.
These duplicate CIs may include Node, Hypervisor and Installed Software.

HP DDMA (HP Discovery and Dependency Mapping Advanced Edition) automates discovery and dependency mapping of services, applications, and underlying
infrastructure.

Independent SA-UCMDB Integration None

SA Web Client

QCCR1D118067

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 SA Web Client None
QCCR1D118068

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 SA Web Client Framework None
QCCR1D131019 After locales are enabled, the SA Web Client fails to start. Windows SA Web Client None

Satellites

QCCR1D91097

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.

QCCR1D97659

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.

Script Execution

QCCR1D79545

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

QCCR1D88755

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

Independent SE Connector None
QCCR1D91582

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.
QCCR1D105778

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.

Software Management

QCCR1D100754

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 SA 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
QCCR1D101517

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.
QCCR1D102564

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.

QCCR1D115665

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
QCCR1D118747 The install/uninstall software status is Failed for all packages, even for packages that were successfully installed. Linux Software Management - Backend

Set the way.remediate.yum=0 in the SA Command Center system configuration.

 

QCCR1D132577

When you remediate a software policy that contains patches, you see a red cross on the software-policy icon in the Management Policies -> Software Policies window.

The following message is displayed:

"There is nothing to be done on this job."

Solaris, HPUX, and Windows Software Management None

QCCR1D133097

Running a compliance scan using a software policy that contains a large number of software policy items might generate errors if the following conditions exist:

  • The software compliance scan runs before the previous scan finishes.
  • An attempt is made to recalculate device groups when device membership has changed.
  • A software policy is detached.

                                                                                          
There is no exact number of items in the software policy that will cause this issue; the higher the number, the higher the probability of an error. 

  Software Management None
QCCR1D133123 Script permissions are not updated correctly in the SA Client. Windows Software Management

Reset the Manage Server Script feature permission to restore the permissions as follows:

  1. Set the Manage Server Script = None.
  2. Save the changes.
  3. Reset it to the value you require.
  4. Save the changes.
QCCR1D133403

When scanning software compliance of a device group or multiple servers, the scan fails on Solaris servers with the following exception:

"SEVERE Exception in polling scan compliance status: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: " ....


Solaris Software Management, Backend

Scan the servers one at a time.

Software Repository

QCCR1D131751

HP Server Automation 9.10 configurations that use a Solaris machine as the Network File System (NFS) server may encounter unexpected behavior and unreliable performance. Due to known instability issues with Solaris NFS, this configuration should be avoided. The recommended configuration is a Linux NFS server, which works reliably with either Solaris or Linux clients.

Solaris Software Repository The recommended configuration is a Linux server as the NFS, which works with either Solaris or Linux machines as clients.

Storage Host Agent Extension

QCCR1D93630

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
QCCR1D93690

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.
QCCR1D105382

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.
QCCR1D105953

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
QCCR1D106400

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.
QCCR1D106699

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
QCCR1D107944

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
QCCR1D111724
/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 / QCCR1D 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 / QCCR1D 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 / QCCR1D 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 / QCCR1D 63370

The format of the value stored in STORAGE_COMPONENTS.STORAGE_DRIVE is different on Solaris 10 than on previous versions of Solaris. The format for Solaris 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 / QCCR1D 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 operating system, 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/
QCCR1D142884

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 None
Bug ID: 154971 / QCCR1D 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 / QCCR1D 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: 157579 / QCCR1D 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 / QCCR1D 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 / QCCR1D 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 / QCCR1D 70934

The SVA 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 / QCCR1D 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: 167103 / QCCR1D 78457 If you perform a core upgrade to SA 7.50 and  SVA 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.
Bug ID:168889 / QCCR1D 80243

If you disable a volume in Veritas DMP and subsequently take a new Storage Host Agent Extension snapshot, it appears as if 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.

Virtualization

QCCR1D90019 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 Virtualization Do not use duplicate virtual network names.
QCCR1D104418 The reported OS property text for ESX servers is inconsistent between direct (SA Agent) and indirect managed (vCenter) cases. VMware ESX (all versions) Virtualization - Backend (VMware) None
QCCR1D105999 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.
QCCR1D106085 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 Virtualization - 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."

  1. Make sure the administrators on the pre-R2 and R2 servers
    have the same password.
  2. Log on to the R2 server and start the Hyper-V Manager applet.
  3. Right-click on the Hyper-V Manager and select Connect to Server.
  4. In the Select Computer window, select the "Another Computer"
    radio button and enter the name of the pre-R2 server.
  5. An icon for the pre-R2 server will appear in Hyper-V Manager.
  6. Select the icon for the pre-R2 server and open the Virtual
    Network Manager.
  7. Highlight the NIC whose configuration you need to change.
  8. Under the Connection type, unselect "Allow management
    operating system to share this network adapter."
  9. Click OK.
QCCR1D106909 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 Virtualization 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.
QCCR1D109887 The snapshot view is not available on an ESX server that is managed by vCenter. Red Hat Linux Virtualization Manage ESX directly snapshot view.
QCCR1D110035 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 Virtualization 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.
QCCR1D111307 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.
QCCR1D111780 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.
QCCR1D111789 Adding two vCenters concurrently results in one of the automatically triggered reload data to suspend processing. Independent Virtualization - Backend (VMWare) Add the vCenters separately.
QCCR1D111922 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:
      unlink /opt/opsware/vmm/lib/OPSWvmm-vmware.jar > /dev/null 2>&1

      Description: Enter a brief description, as necessary.
    3. 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 hypervisor version.

QCCR1D111972 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.
QCCR1D116276 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 Virtualization -
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

QCCR1D111039 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.
QCCR1D112222

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 In This Release

The following fixed Issues table includes issues that:

The table lists issues first by subsystem, then numerically within each subsystem.

Fixed Issues for This Release

QCCR1D Symptom/Description Platform

Agent

QCCR1D130405  Agent registration fails and returns a Python error message if certain network errors occur during the registration process.
Independent
QCCR1D132944
Inventory data does not show Linux bonding interfaces for SuSE Linux Enterprise Server (SLES) 11 x64. Linux
QCCR1D133426  Deployment sets can include servers without open-protocol ports. Independent
QCCR1D133618  Agent registration fails if you run the bs_hardware script on a server with multiple disks. AIX;HP-UX
QCCR1D135192  Agents that have been dormant for 12 hours cannot be registered. Independent
QCCR1D135716 Open Global File System (OGFS) file access does not function  correctly for non-administrator users. Windows
QCCR1D135996 The Solaris system does not display hard disks correctly. Solaris
QCCR1D136362 

Agents have a constantly increasing process-handle count. The agent logs and the OPSWshadowbotservice.out file display the following type of errors:

Registering full software inventory information...
Contacting core for delta with SpinWrapper to httWin32 exception occurred releasing IUnknown at 0x01c06620
Win32 exception occurred releasing IUnknown at 0x01c0e140

Windows
QCCR1D137345 The Open Global File System (OGFS) cannot reach non-Pluggable Authentication Modules (PAM) agents.
Unix

Application Deployment Manager

QCCR1D134220 The Application Deployment Manager did not install successfully when the Oracle TNS entry was defined using a multi-line format. Independent
QCCR1D134461 The instructions for obtaining and installing Adobe Flash Player were shown when the Application Deployment Manager was launched from a web browser. Flash Player is only needed when the Application Deployment Manager is launched from the Server Automation client. Independent
QCCR1D134763 The Application Deployment Manager did not notify users of unsaved changes before leaving the Administration Settings page. Independent
QCCR1D137629 Target groups were not displayed correctly in the Application Deployment Manager. Independent

Audit and Compliance

QCCR1D137342

Audits run successfully but fail all compliance checks with the following error: "Unable to execute on target server."
By default, SA applies a memory limit of 256 KB for scripts executed on the managed servers, resulting in this audit error. The memory limit has been removed.

All Linux
QCCR1D143613

Snapshot and audit regression issues occur after upgrading if you are using an established datacenter and your SA Agent was not also upgraded to 9.12.

AIX, ESX, HP-UX, Linux, Solaris, VMware

Authentication, Authorization, and Accounting (AAA)

QCCR1D112477  When you change the user distinguished name (DN) in the Lightweight Directory Access Protocol (LDAP), you must reimport the user. Independent
QCCR1D131580  Public device-group permission is required to create a private dynamic device group. Linux

APX FRAMEWORK

QCCR1D137903  A web Managed Boot Client (MBC) Dynamic Host Configuration Protocol (DHCP) cleanup APX error is displayed if the parenthesis in a facilities name is removed, making the long and short name different.
Independent

Command Center

QCCR1D133496 Problem exporting audits to a comma-separated value (CSV) file. Windows

Command-Line Interface

QCCR1D104854 Overwriting a file with the Command-Line Interface fails if it is done from a managed server. Independent

Custom Extensions

QCCR1D112879  When you run the Change_Password extension, a defunct password process is sometimes left on the server.   Linux

Data Center Markup Language (DCML) Export Tool (DET)

QCCR1D138384 The Data Center Markup Language (DCML) Export Tool fails to import packages that are larger than two gigabytes (GB). Independent

Database and Middleware Automation (DMA)

QCCR1D129625 The Dashboard page did not display a message indicating that Adobe Flash Player must be installed and enabled. Independent
QCCR1D131426 When a step was copied, the step history for the copy did not indicate which step it was copied from. Independent
QCCR1D131491 On the Solutions > Installed page, text wrapped incorrectly in the Details pane . Independent
QCCR1D131503 The Available targets search on the Deployment page was not reversible, and at least 3 characters were required to enable the Search button. Independent
QCCR1D131775 The Roles preview list displayed was sometimes larger than Preview pane. Independent
QCCR1D132525 Running a deployment by using the "Run Workflow" step failed. Independent
QCCR1D132917 New group members did not appear in the Preview pane on the Roles page. Independent
QCCR1D133252 After the DMA Agent Support Policy was uninstalled, certain files remained on the managed server. All pertinent files are now removed. Independent
QCCR1D133411 The deployment parameter drop-down list did not preserve consecutive white space characters in the selected choice. Independent
QCCR1D133568 During the creation of a new deployment, parameters were lost if a target was not specified. Independent
QCCR1D134392 An inaccurate error message was displayed when a solution pack import failed. Independent
QCCR1D134582 The "Run Workflow" step failed if the target server had been deleted and then re-added in Server Automation. Independent
QCCR1D134885 If a step in a workflow hung, the workflow did not finish – it had to be manually cancelled. Independent
QCCR1D135009 Invoking a workflow with multiple database targets on the same server caused the workflow to fail with a "text busy" error message. Independent
QCCR1D135012 In rare cases, it was possible for a workflow step to be executed even if the parent step were not executed. Independent
QCCR1D135051 Workflows that wrote large amounts of output or error messages executed slowly. Independent
QCCR1D135108 When a parameter was removed from a step, some references to that parameter were not deleted. Independent
QCCR1D135406 On the Console page, the workflow Output was not formatted for readability (as it is on the History page). Independent
QCCR1D135543 In Internet Explorer versions 7 and 8, the Browse button on the Solutions and Workflows pages were smaller in size than the other buttons. Independent
QCCR1D135549 If backslashes (\) were used in the filter string, filtering was disabled. Independent
QCCR1D135678 Workflow execution sometimes resulted in unexpected import failures. When this happened with Windows managed servers, cryptic error messages were displayed in the DMA console. Independent
QCCR1D136008 In Internet Explorer versions 7 and 8, a Javascript warning appeared on most pages. Independent
QCCR1D136545 When a step with an invalid or duplicate parameter name was saved, an inaccurate error message was displayed. Independent
QCCR1D136902 When you clicked "Run workflow" on the Run page, no message indicating that the workflow was, indeed, running was displayed. Independent
QCCR1D137401 If a workflow name contained a trailing backslash (for example: "myWorkflow\"), the Workflows, Steps, Policies, and Organization tabs on the Setup > Permissions details page could not be viewed. Independent
QCCR1D137632 Solution pack rollback sometimes failed if a parameter were removed from a step. Independent
QCCR1D137822 Workflow documentation was lost when a solution pack was rolled back. Independent
QCCR1D138204 The code sections on the Step and Function pages did not have line-numbering or syntax highlighting. Independent
QCCR1D138398 The solution pack history filter did not include the User or Date fields. Independent
QCCR1D138995 You could not create a PDF file containing the contents of the workflow Documentation pane if the workflow name contained special characters (&, <, >, etc.). Independent
QCCR1D139234 Function names were not sorted alphabetically in the Insert Function dialog. Independent
QCCR1D139406 On the Environment page, it was easy to inadvertently delete an organization, server, instance, or database because of the non-intuitive way that DMA responded to single-clicks and double-clicks. Now, only single-click navigation is used. Independent
QCCR1D139888 A problem on the Automation > Deployments page was fixed. Independent
QCCR1D139918 In the Smart Group criteria, some characters (<, >, &, ', ", etc.) incorrectly showed HTML entities instead of the actual character. Independent
QCCR1D140254 Server.OS was not available as a criteria field when creating a Smart Group. Independent
QCCR1D140422

Windows PowerShell was not supported as a call wrapper. To use PowerShell, specify the call wrapper parameter value as follows: powershell -File

IMPORTANT:  If you install PowerShell on a managed server and want to use it as a DMA call wrapper, you must restart the SA agent on that server. To do this, restart the Opsware Agent service.

Independent
QCCR1D140423 Copying an instance or database level deployment as a non-administrator user caused an error. Independent
QCCR1D140536 Drop-down list for parameters on the Deployment page does not show all the available values Independent

Device Groups

QCCR1D134718  The Filter rules for a dynamic device group are displayed in an inconsistent order. Independent
QCCR1D135045 Event-based changes in dynamic device groups are not shown in the SA Client, but they do appear on the SA Web Client. Independent
QCCR1D135855 Device groups are not calculated correctly. Linux

Gateway

QCCR1D90563 The core gateway fails with no errors when it fails to open port 8085 for listening. Independent

Global Filesystem

QCCR1D133602 The getResult global shell command fails when a job fails. Linux;Solaris
QCCR1D137569 When the snapshot cache level is near 31998 subdirectories (the ext3 filesystem limit), snapshot jobs start to fail and the following type of error is displayed:

2011-09-16 21:10:45,404 SEVERE Thread-3725 [com.opsware.compliance.server.cache.SpokeSnapshotResultsCacheManager] [renameTo] rename from /var/opt/opsware/compliancecache/stempcache/13162074452178601229522788817166.tmp to /var/opt/opsware/compliancecache/scache/184380002 failed
Linux

OS Provisioning

QCCR1D130556 Duplicate Media Access Control (MAC) addresses are created during mini-agent registration. Independent
QCCR1D133706 Unable to import Red Hat Enterprise Linux Server. Independent
QCCR1D136035 SA does not provide an Emulex NC553i HBA driver (for EVA8100) Windows PE-64 Windows Imaging Format (WIM) boot image. WinPE X64
QCCR1D137524
The following timeout message is displayed when you try to provision SUSE Linux Enterprise Server 11.1:
"First state to second stage reboot transition timed out."
SLES 11

Patch Management

QCCR1D114071 When you import the Windows 2008 patches using the populate-opsware script, some of the patches are also uploaded into the software repository. Windows
QCCR1D119830 Duplicate patches are displayed after you import the patch database. Windows 2008
QCCR1D133701 SA only supports the .zip archive format for solpatch_import. Linux

QCCR1D138895

AIX software policies that have service pack file sets with multiple dependencies can now be installed on AIX. Previously, this caused errors in the installation. To resolve this issue, the reboot options for installing an AIX software policy were changed. Now, the first two reboot options function as the third: Hold all server reboots until all actions are completed.

  • Reboot servers as specified by the individual software items  [Not valid for AIX; same as Hold]
  • Reboot servers after each installation or uninstallation  [Not valid for AIX; same as Hold]
  • Hold all server reboots until all actions are completed
  • Suppress all server reboots
Now, when you install software using an AIX software policy, the server will not reboot until after all the installation tasks are complete. The option to Suppress all server reboots is unchanged; it still prevents the server from rebooting when the installation is complete.
AIX

QCCR1D139209

You can now uninstall Windows multi-binary patches that have non-installing components. For example, a Windows multi-binary patch may contain a non-installing component, such as an MSIPatchRegFix script. This script is not installed or uninstalled. It just amends the registry when the patch is installed, and it cannot be undone. Previously, SA prevented these types of multi-binary patches from being uninstalled.

Now, you can uninstall these multi-binary patches using SA, and it will remove all of the uninstallable binaries. In this scenario, a benign error message may indicate that one or more of the uninstallers could not be found. For instance, if one component in the patch succeeds and another has an error message saying that the file cannot be found, there is a chance that the error is false and that the patch actually did uninstall. To verify that the multi-binary patch uninstalled correctly, run a patch compliance scan on the server.

Remember: if you uninstall a patch, you must remove it from the patch policy or it will get reinstalled the next time you remediate the server.

Note: In order for multi-binary patching and compliance to work on any Windows Managed Server, you must upgrade the server’s SA Agent to 9.12.
Windows

Scripting (DSE)

QCCR1D117075 Cannot copy and paste a script to a different folder using the SA Client user interface. Independent
QCCR1D134084 Unable to pull job history for recurring extensible-discovery jobs when servers were deleted prior to running the job. Independent
QCCR1D136850 The Global File System (GFS) script cannot run if the Output options are changed. Independent

Server Management

QCCR1D121098 The Java client is not registering the server's rename actions. Independent

Server Module

QCCR1D132608 Incorrect server i18n encoding setting causes the Users/Group server module (SMO) to fail with a bad-error message. Linux

Software Management

QCCR1D115563 If you remediate  a device group using a pytwist library, then navigate to the job logs and open the specified job, the following warning message is displayed:
"The action can't be performed on one or more of the selected items.
The action will continue only for the applicable selected items."
Independent
QCCR1D115899 If package staging fails during remediation, the process should stop further staging. Independent
QCCR1D120682 Unable to remediate software in the compliance view when the software policy attached is inherited through a Device Group. Independent
QCCR1D121198 Software policy scripts run on the wrong platform. Independent
QCCR1D122573 A corrupt-zip message is displayed when a 3 gigabyte (GB) zip installation fails. Independent
QCCR1D129781 When updating software packages, the Java client progressively uses an excessive amount of local PC resources (memory and CPU) and eventually stops working. No errors are generated. Independent
QCCR1D131520 The remediation process has been enhanced to improve both performance and scalability. You can now remediate a large number of managed servers or devices against a large channel-based RPM software policy in a single job. Previously, this action could make SA become unresponsive.   Red Hat Linux
QCCR1D132413 The rhn_import utility should support Secure Hash Algorithm 256 (SHA256) checksum verification. Linux
QCCR1D134695 When you load a remediation job using the SA Client, there is an approximate 90-second lag time. If you load the same job using JobService.getResults(), there is no lag time.
Independent
QCCR1D134415 RPM Package Manager (RPM) packages are included in software policies. If a package has dependencies that do not also belong to its policy, and the policy is remediated twice, the package is removed. Linux
QCCR1D134769 The Web Services Data Access Engine incurs an excessive load while searching for custom attributes for large remediations. Linux;Solaris
QCCR1D134795 When you remove a package from an attached and remediated software policy, then remediate again, the package is not uninstalled. Independent
QCCR1D135416 SA does not support AIX 7.1 as a managed platform. AIX
QCCR1D137055 Remediation of RPM Package Manager fails and displays the following message: "The remediate operation cannot be performed because of unsatisfied dependencies." Linux
QCCR1D137153 When you successfully install a Solaris package that contains "-R" as part of the package name, SA reports that the installation has failed. Solaris
QCCR1D137154

The usability of the Server and Group selections should be improved in the SA job window.

Independent
QCCR1D138714 The units removed from a policy are not uninstalled when you remediate the policy. You must uninstall them manually. Linux

Software Repository

QCCR1D81181 The yum_metadata cache throws an error if the "*.sig" file is not present.
Independent
QCCR1D113849 Some AIX packages failing to import due to an invalid lpp_name structure. The following error is displayed:

[root@core ~]# export PYTHONPATH=/opt/opsware/pylibs2
[root@core ~]# LD_LIBRARY_PATH=/opt/opsware/lib
[root@core ~]# /opt/opsware/bin/python2 /opt/opsware/mm_wordbot/util/lppname.pyc DLManager.mpio.6.2.0.0.I
Traceback (most recent call last):
  File "./util/lppname.py", line 119, in ?
  File "./util/lppname.py", line 56, in __init__
ValueError: invalid lpp_name data

Linux

Virtualization

QCCR1D138026 Secure Shell (SSH) keys are not generated on Solaris Zones. Solaris

Back to the table of contents


Deprecated Features

When a feature or platform is identified as deprecated for a release, it means that you (the SA customer) are notified of its future removal. Deprecated features are still fully supported in the release they are deprecated in, unless specified otherwise. The intent is that deprecated features or platforms will have support removed in the next major or minor SA release; however, eventual removal is at the discretion of HP.

The following sections list features that were deprecated in the SA 7.80 release. Current and future availability of these features is also described here.

Deprecated API Methods

In SA 9.0, moving application configurations and configuration templates into folders changed the behavior of the associated classes and services.

Attributes folder and lifecycle of the VO-s are required for the following API calls:

com.opsware.acm.ConfigurationService#create
com.opsware.acm.ConfigurationService#update
com.opsware.acm.CMLService#create
com.opsware.acm.CMLService#update
The following methods have been deprecated, but they still perform as expected. Method
com.opsware.folder.FolderVO#getCustomers should be used instead.
com.opsware.acm.ConfigurationVO#getCustomers
com.opsware.acm.CMLVO#getCustomers
The following methods have been deprecated and they have a void implementation. Method
com.opsware.folder.FolderVO#setCustomers must be used instead.
com.opsware.acm.ConfigurationVO#setCustomers
com.opsware.acm.CMLVO#setCustomers

Code Deployment and Rollback (CDR) and Configuration Tracking

Code Deployment and Rollback (CDR) was deprecated in the SA 7.80 release, but is still supported in SA 9.0. In a future release, this feature will not be supported. The new Application Deployment tool in SA 9.0 is intended to replace CDR. See New Application Deployment Manager on page 13 and the SA Application Deployment User Guide for more information.

For more information about the deprecation of CDR, contact your HP Technical Support representative.

Agent Deprecation

In SA 9.0, HP announced the deprecation of the Server Automation Agent for the following versions:

• Server Automation 7.01
• Server Automation 7.00
• Server Automation 6.xx
• Server Automation 5.xx

Although releases of HP Server Automation prior to 9.0 will continue to support these versions of the Agent, it is recommended that customers migrate to newer versions of the Agent on their managed platforms.

HP SA will stop supporting these versions of the Agent in an upcoming major or minor release. Agents from Server Automation 4.xx and earlier are not supported in this release.

DOS-Based OS Provisioning

DOS-based OS Provisioning was deprecated in the SA 7.80 release and is not supported in SA 9.0 or later. For more information, contact your HP Technical Support representative.

start_opsware.sh and stop_opsware.sh scripts

As of SA 7.80, the following scripts are no longer supported:

start_opsware.sh
stop_opsware.sh

In SA 9.0 and later you must use the unified start script:

/etc/init.d/opsware-sas

If you have any applications or scripts that depend on this script, you must rewrite them to use the unified start script.

Virtual Server Management Actions

The Open Console action (for VMware virtual machines of ESX agent-managed hypervisor) was removed in the SA 9.0 release.

The Open Web Access action (for ESX agent-managed hypervisors) was removed in the SA 9.0 release.

As of SA 9.0, virtualization actions for agent-managed ESX 3.0 hypervisors are no longer supported, unless the ESX 3.0 hypervisor is managed by a Virtualization Service. It cannot be directly added to the Virtual Servers view (through Add Hypervisor); it needs to be vCenter managed.


Documentation Information

This section discusses documentation information for this release.

New Guides

The following guide was added for 9.11:

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.

 

Documentation Errata

This section describes documentation errata.

SA 9.10 Administration Guide


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.10 Simple/Advanced Installation Guide


SA 9.10 User Guide: Server Patching

In chapter 4: Patch Management for Solaris, page 108, Fujitsu Clusters, SA Commands, replace the following statement:

Use the following command to display additional information about cluster commands:
/opt/opsware/solpatch_import -manual

With this statement:

Use the following command to display additional information about cluster commands:
/opt/opsware/solpatch_import/bin/solpatch_import --manual

 

Support Matrix

Please note the following documentation errors:

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-2012 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.

Release-Notes Updates


New Publication Date Change
   

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