HP Server Automation Release Notes

Software version: 9.14

Original Publication Date: December, 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.

Note: The latest information for 9.14 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:

Supported in This Release

This section lists the platforms, integrations, browsers, and operating systems that SA 9.14 supports.

Qualified Managed Support

The SA 9.14 release provides qualified managed support for the following:

Platforms:

• CentOS 5.8 (x86, x64), 6.3 (x86, x64)
• ESX/ESXi 4.1 U3
• ESXi 5.1
• OES 11, 11 SP1
• OEL 5.8 (X86, X64), 6.3 (X86, X64)
• RHEL 5.8 (IA 64, Power)
• RHEL 6 Client (x86, x64)
• RHEL 6.2 zSeries
• RHEL 6.3 (x86, x64, Power)
• SLES 11 SP2 (Power)
• SLES 11 SP2 zSeries
• Windows Server 2012
• Xen 6.0.2, 6.1.0

Core Platforms:

• Solaris 10U10
• SLES 10 SP4

Integrations

The SA 9.14 release provides support for the following integrations:

• BSAE 9.20

• Live Network Connector (LNc 3.30
• Storage Essentials (SE 9.5.1)
• UCMDB

Browsers

This table shows browser support information for this release.

Windows Operating Systems

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

• Windows Server 2003  
• Windows Server 2008   
• Windows XP
• Windows Vista 
• Windows  7 

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.

New Features 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.

New Installation Preparation Instructions

Make sure you follow these steps before you install SA:

1. Mount the patch ISO file to a directory. 
2. Then copy the entire content of the directory mentioned in step 1 to a writable file system. 
   This file system must have the equivalent free-disk space equal to double the size of the ISO file plus 1 GB. For example, if the ISO file is 4 GB, make sure the file system has at least 9 GB of free-disk space available.
3. Run the patch installation scripts as explained in Script Running Order, but run the scripts from the writable directory, not from the original mount location.

Manage Boot Client Facility Special Attribute Behavior Change

Starting in SA 9.14, the facility special attribute used in Manage-Boot Client Facility (MBC) Comma-Separated Values (CSV) files requires that the Facility ID be specified rather than the Facility Name.

SA Managed Server Peer Content Caching

In previous SA releases, if you had smaller sites without a sufficient number of managed servers to justify installation of a full SA Core, SA provided the Satellite installation. This smaller installation allows you to install only the minimum necessary Core Components on the Satellite host which then accesses the Primary Core's database and other services through an SA Gateway connection.

As of SA 9.14, SA provides Managed Server Peer Content Caching which, for facilities with fewer than 50 Managed Servers, provides caching of the Software Repository without the need for Satellite components.

Some of the benefits of Managed Server Peer Content Caching are:

• Managed Server Peer Content Caching uses existing SA managed servers (no additional hardware infrastructure required)
• Managed Server Peer Content Caching reduces WAN traffic during software staging
• Managed Server Peer Content Caching allows pre-staging of software packages
• An SA Satellite or Gateway is not required at the remote site
• Software can be manually loaded into the cache

Requirements

Managed Server Peer Content Caching requires:

• A managed server running any SA supported operating system to act as the Peer Cache server
• Managed Servers must be configured to use Managed Server Peer Content Caching using custom server attributes

Installing a Peer Cache

1. Decide which managed server(s) will act as peer cache servers.
2. Upgrade the SA Agents on the peer cache servers to SA 9.14 (SA Agents on other managed servers do not need to be upgraded).

Warning: The peer caching feature will be unavailable if you use pre-9.14 SA Agents on the peer cache servers.

Note: You perform the Agent upgrade as described in the Agent Utilities appendix of the User Guide: Server Automation.

Configuring the Peer Cache and SA Servers

1. Create a custom attribute for each managed server in the branch/remote site.
   1. For example, 'peer_cache_dvc_id = 240001' where 240001 is the device id of the server acting as a peer cache.
   2. If the branches/remote sites are modeled as device groups, you can apply the custom attributes at the device group level using a script. Managed servers added to the device group later will automatically inherit this custom attribute.
2. Ensure that all managed servers using the peer cache must belong to the same customer as the peer cache.
3. (Optional) Create the following custom attributes on the managed server(s) acting as a peer cache(s)
   1. 'peer_cache_size' = <value in megabytes>
      default: 1TB (but limited to filesystem size)
   2. 'peer_cache_path' = <location of file store>

   Note: 'sa_cache' is appended to the value you specify for the path.
   For example, the default for Windows is:
   \Program Files\Common Files\Opsware\sa_cache

4. By default, managed servers attempt to connect to the peer cache using the cache's primary IP address. However, you can use a custom attribute to specify a different IP address in the format:

   'peer_cache_ip_field' = <'primary_ip' | 'management_ip' | 'ip:<addr>'>
   where:
   'primary_ip' - (default) the IP address of the management interface. This is the locally-configured IP address (not NAT translated)

   'management_ip' - the IP address SA uses to communicate with the server. This may be a NAT translated address

   
   'ip:<addr>' - to manually set an IP address (e.g. 'ip:192.168.2.1')
   
   See the section in the SA User Guide: Server Automation, 'Communication between Managed Servers and SA' for more information about configuring the primary IP address and NAT for managed servers.

Remediation with Managed Server Peer-Content Caching

You start remediation as described in the User Guide: Software Management.
When using Managed Server Peer Content Caching, remediation performs these steps:

1. During the staging phase, managed servers are given the cache IP address (derived from the 'peer_cache_dvc_id' CA attached to that server).
2. The managed servers stages packages from the branch/remote site peer cache (see Retrieve Objects from Peer Cache below).

Retrieving Objects from the Peer Cache

When retrieving objects from the peer cache, SA/SA components usually perform this sequence of steps:

1. The staging code on the managed server receives the IP address of the configured peer cache.
2. The staging code makes a secure connection to the Agent port of the peer cache server using the Agent's SA security certificate.
3. The peer cache confirms that the connecting client is configured to use the cache, and belongs to the same customer as the peer cache.
4. A request is made to the peer cache to stage a specified unit.
5. The peer cache server responds to the request by sending the unit.
6. During the action phase, the checksum of the object is verified against the checksum of the same object in the Software Repository.

Different Sequence of Events that Can Occur Instead

Instead of the normal sequence of steps (see Retrieve Objects from the Peer Cache), peer-caching issues can occur, causing a different set of actions. This table presents a list of the original actions, along with the alternate actions that could occur, and the subsequent steps that will occur as a result of the alternate actions.

Manually Add Files to the Peer Cache

You can manually add files to the peer cache with the following restrictions:

• The file must be identical to the source file in the Software Repository.
• The path to the file must be identical to the path in the Software Repository.
  

For example, to copy the following file from the Software Repository:

/var/opt/opsware/word/GPC/packages/software_repository/Linux/6SERVER-X86_64/7000001

Note: The Facility name in this example is 'GPC'.

The file should be copied to the peer cache as follows:

/var/opt/opsware/sa_cache/packages/software_repository/Linux/6SERVER-X86_64/7000001

Example: Copy all RHEL 6 X86-64 files to the peer cache.

1. On the core slice, issue the following commands:

   cd /var/opt/opsware/word/GPC
   zip -r rhel6_content packages/software_repository/Linux/6SERVER-X86_64/
   # we don't need the .sig files
   zip -d rhel6_content.zip \*.sig

2. Copy rhel6_content.zip to the peer cache server and unzip it in the sa_cache directory.

Viewing the Peer Cache Status Page

1. Install browser certificate: browser.p12

   browser.p12 is located in: /var/opt/opsware/crypto/spin/
   
   on any Slice Component bundle host. Copy the file to your local machine and import browser.p12 into your browser following your browser import certificate instructions.

2. Using your web browser access:
   https://<peer_cache>:1002/oplets/peer_cache.py

Bandwidth Management of Remote Connections (Bandwidth Throttling Porting)

Bandwidth Management is a measure employed in communication networks to regulate network traffic and minimize network congestion. The SA remote-site management model typically uses a satellite configuration that deploys a remote gateway on every logical location (for example, a branch office) to handle connections to remote servers and to manage the network bandwidth of these connections. However, the cost effectiveness of this configuration is significantly reduced for sites that manage only few servers.

A new SA bandwidth management capability eliminates the need to install a satellite for remote locations with only a few servers. As of SA 9.14, SA provides the Bandwidth Configuration Management tool (BCM) to control the bandwidth used by agent or satellite gateways when communicating with remote servers.

As of this release, you can push bandwidth configurations to a peer group by using the new Bandwidth Configuration Management tool. After the configuration is pushed to the peers, it is saved to a file. During gateway startup, the configuration is loaded from this file and synchronized with the peers. When a client negotiates a connection through the SA Gateway mesh to connect to a remote TCP service, the client then has a TCP connection to the ingress gateway. Also, there is a TCP connection leaving the egress gateway to the remote service.

When the proxy connection through the gateway mesh is established, the peer addresses of ingress/egress connections are classified and a runtime queue is created for each classification. At this point, bandwidth throttling is in effect for these connections. The corresponding queue is updated with the bandwidth usage information as the data flows through the connection. The bandwidth usage information is also shared among the peer group so that the local queue can be updated on each gateway cluster. The data can flow through that connection till the maximum bandwidth allowed is reached. Queue bandwidth usage information is reset at a one-second interval.

Note: All agent gateways in the same REALM must also be running the same SA version (minimum SA 9.14) in order to participate in agent-gateway bandwidth negotiation and communication. Mixed-core configurations (core and satellites running a different SA version) are not supported.

The SA Bandwidth Configuration Management Tool (BCM)

Note: SA Bandwidth Configuration Management (BCM) Tool does not support SA cores/satellites running Solaris or Red Hat Enterprise Linux 3 (x86).

Note:  If you plan to use the Bandwidth Configuration Management tool, your firewall must allow SA network traffic on ports 3001 and 8086. If you plan to use the BCM tool administrative interface, port 8089 must also be open.

This section describes using BCM to create bandwidth-management configurations. These configurations can then be automatically synchronized across peer gateways.

Only administrative users who have root access to the gateway host can perform gateway-configuration push operations with the BCM tool.

Note: Although the BCM tool is installed with a default configuration file /etc/opt/opsware/gateway_name/BWT.conf, you should not modify that file directly. Make a copy of the file and edit it to suit your configuration. You can then push the modified configuration file to all the gateway(s) in the realm using the gwctl –f command. See Invoking the Bandwidth Management Configuration Tool.

Specified bandwidth configurations are saved to a configuration file. The following is an example of a typical Gateway configuration file:

enabled

# Branch offices have only 3M bytes per sec connections, SA should never use 
# more than 512K bytes per sec.
queue branch_office bandwidth 512KB

# Branch offices A and B (non-standard addresses)
class 192.168.1.[1-5,10-15,20,30] for branch_office

# Other branch offices
class 192.168.2.0/24 for branch_office

Invoking the BCM Tool

You invoke the Bandwidth Configuration Management Tool (BCM) as a command-line tool.

On the Satellite whose SA Agent configuration you want to manage, use the following commands:

gwctl: [OPTIONS] ...

Bandwidth Configuration Management Tool Options

This section describes BCM Tool options and sample commands.

This table describes the BCM Tool options.

This table displays sample commands.

Enabling/Disabling Remote Connection Bandwidth Management

You must enable or disable remote-connection bandwidth management in one of the two following ways:

• By pushing a bandwidth configuration file containing the enabled or disabled keyword. Each configuration file must contain enabled or disabled options indicating the status of bandwidth throttling.
• From the command line using gwctl –e to enable bandwidth management or gwctl –d to disable bandwidth management. The bandwidth management state of enabled or disabled persists in the bandwidth management configuration file with no version upgrade.
  

Bandwidth Configuration Grammar

The Context Free Grammar (CFG) of bandwidth configuration in Extended Backus–Naur Form  (EBNF) format is:

config : ((queue | class | version | config_source | config_user | enabled | disabled | comment)? '\n')\*

queue : 'queue' queue_name 'bandwidth' d_number bandwidth_spec ('rtt' d_number)? ('parent' queue_name 'borrow')?

queue_name : "[a-zA-Z0-9_]+"

class : 'class' pattern (',' pattern)* 'for' queue_name

pattern : ipv4 | ipv4_cidr

ipv4 : ipv4_address_pattern_element ('.' ipv4_address_pattern_element)@1:3

ipv4_cidr : d_number ('.' d_number)@1:3 '/' d_number

ipv4_address_pattern_element : single_number | range | range_class | wildcard range_class : '[' (number ('-' number)? ',')+ ']'

wildcard : '*'

range : '[' number '-' number ']'

single_number : d_number

number : d_number

d_number : "[0-9]+"

x_number : "[a-fA-F0-9]+"

bandwidth_spec : "[GMK]?[bB]"

config_source : 'config-source' ':' "[a-zA-Z0-9.:\-]+"

config_user : 'config-user' ':' "[a-zA-Z0-9_!@#$%^&*();.`~\-\\]+"

enabled  : ‘enabled’

disabled : 'disabled'

comment : '#' "[^\n]*"

SA Server Patching

SA Server Patching Enhancements

SA Patching introduces a number of new and changed features for 9.14, listed below.

Documentation: See SA 9.14 Server Patching Updates Whitepaper for a full explanation of these patching updates. Additional whitepapers are available for some features, as listed in the table below. All documentation for SA 9.14 can be found on the HP Software Support Online site at: http://support.openview.hp.com/selfsolve/manuals.

Predictable and Reliable Windows Patching

Other SA Server Patching Enhancements

SA Software Management

Remediate RPM Packages Using the Native YUM

The new Yellowdog Updater Modified (YUM) plugin is an alternative to the old YUM Adapter for the analyze phase of the remediation process. It uses the native YUM available on the managed server and has the following main advantages:

• Accurate results – there have been cases where the old YUM Adapter returned different results than the native YUM
• Better performance – the duration of the analyze phase was significantly reduced by using the native YUM available on the managed server. In order to support this feature the managed server must use native YUM 3.0.1 or later.
  

The YUM version available on the managed server can be identified by running the following command in the command line:

yum --version

When available, the managed server’s native YUM is used to analyze RPM package dependencies. When the managed server does not have a native YUM available, the SA YUM Adapter is used instead. This behavior is based on the default and recommended setting governed by the SA configuration parameter, way.analyze.yum, which has the following available values:

0 - use the YUM adapter (YUM v2.6.1)
1 - use the native YUM when available, otherwise use the YUM adapter. (Default)
2 - use the native YUM

Note: SA configuration parameters are accessible only via the SA Web Client. Only system administrators with the Opsware System Administrators user group permission can change these settings.

Warning: Changes to SA Core configuration parameter values, as listed in this Release Notes document, are verified by HP and you can safely apply them as directed. However, exercise caution when modifying any default SA Core configuration parameter values as modifications can have a negative effect on core functionality and performance.

IMPORTANT—Known issue with legacy YUM: YUM versions prior to 3.2.22 may encounter an installation error if a package is stored in multiple locations. For example, if you import a package to Folder A, run a remediation job, and then import the same package to Folder B and try to install it, the analysis might fail, reporting the package from folder B as missing. This issue does not reproduce on servers using YUM version 3.2.22 or later, where the YUM repository is updated to contain both packages.

SA-UCMDB Integration

SA 9.14 includes fixes to the SA-UCMDB Connector, in addition to the following enhancements:

• Extensibility
• Support for UCMDB Browser integration in the NGUI
• Support for UCMDB server versions 9.05 and 10.01
• Global UCMDB IDs
• Extended Out-Of-The-Box mappings
• Support for SA Custom Attributes
• On-demand sync
• Extensible ETL mapping and data normalizing capabilities
• SSL Connectivity to the UCMDB Server

With the SA-UCMDB Connector enabled in 9.14, the SA Client now provides the ability to launch the UCMDB Browser-Impact widget against an SA managed server.

Documentation: Complete, illustrated instructions for using the new SA-UCMDB functionality are provided in the SA 9.14 SA-UCMDB Integration Guide, which is available via HP's Software Support Online at http://support.openview.hp.com/selfsolve/manuals.

Agents

Upgrading SA Agents

Since 9.11, SA Agents have used Python 2.4.4.

After you upgrade to SA 9.14, you should also upgrade to the 9.14 SA Agents on each Managed Server in the facility.

You can continue to use non-upgraded agents with 9.14, but SA 9.14 features, platforms, and integrations (see Qualified Managed Platforms, Features, Integrations, and SA Agents) will not be supported.

Faster Agent Installation

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

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://hpln.hp.com/.

SA-OO Integration

Integrating the OO SDK Client Certificate

The SA-OO Integration feature is not available until you import the required OO SDK Client Certificate into SA. SA 9.14 is bundled with two OO SDK certificates that apply to different OO versions, as shown in the following table. Before you import the certificate into SA, make sure it is compatible with your OO version.

To integrate the new certificate, you must perform the steps in the procedure detailed below.

Note: If your architecture includes a master core and one or more secondary cores, follow the steps in this section for the master core and for each of the secondary cores. Similarly, if your SA computer has a sliced-core installation with one or more slices, repeat the steps for each slice.

To integrate the certificate:

1. Stop the Web Services Data Access Engine (Twist):

   /etc/init.d/opsware-sas stop twist

2. Transfer the OO Certificate to SA (when you are prompted for a password for the next steps, use: changeit)
   1. Export the OO Central Certificate:
      /opt/opsware/jdk1.6/jre/bin/keytool -exportcert -alias oocert2011 -file /tmp/oocentral.crt -keystore /var/opt/opsware/twist/oocert
      
      Connect to the previous version of OO that still uses the older certificate, which expired May, 2011 (optional):
      /opt/opsware/jdk1.6/jre/bin/keytool -exportcert -alias oocert2007 -file /tmp/oocentral.crt -keystore /var/opt/opsware/twist/oocert
      
      Note: The keystore /var/opt/opsware/twist/oocert contains the following certificates:
      oocert2007 - OO certificate bundled with OO versions 7.5, 7.6, and 9.0, valid until May, 2011
      oocert2011 - OO certificate bundled with OO 9.02.0002 and later, also released as part of the OO hotfix #132914, valid until July, 2016
      pas - OO certificate that is the same as oocert2007, retained for backward compatibility
      
   2. Import the OO Central Certificate to the SA Java Runtime Environment (JRE) keystore:
      /opt/opsware/jdk1.6/jre/bin/keytool -importcert -alias oocert -file /tmp/oocentral.crt -keystore /opt/opsware/jdk1.6/jre/lib/security/cacerts
      
      Note: Any alias can be used when importing the certificate, as long as it is not already used in that keystore. The sample command above uses oocert, but you can use any other name.

Operating System Build-Plan Script Changes

In previous SA versions, if you created OGFS scripts and added them to your build plans, the scripts were executed in the file system in the following directory:

/opsw/.Server.ID/<mid>/files/<user>

Now, the scripts are executed in this new location:

/opsw/.Server.ID/<mid>

As a result of this change, you must add the following line to your build-plan scripts to avoid compatibility issues with user scripts:

cd files/root (Linux)

cd files/Administrator ( Windows)

Oracle RAC Support

This release supports Oracle 11.2.0.2. For more information, see the white paper: Oracle RAC Support, which you can download from the SA 9.14 release section at: http://support.openview.hp.com/selfsolve/manuals.

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.14, 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.14, you will overwrite the SA 9.10 OSBP content that was uploaded during install/upgrade with older SA 9.0 OSBP content, which will cause errors when you attempt to run OS Build Plan jobs under SA 9.14.

Solaris 11

Using OCLI on Solaris 11 Servers

Note: This information applies to all Unix and Linux platforms.

To install the SA Command-line Interface (OCLI) on a Solaris 11 server, issue the following command:

<package_name> -d <installation_directory>

No other steps to setup the environment are necessary.

When using the SA Command-line Interface (OCLI) on a Solaris 11 server, the oupload and odownload scripts are run from the newly created /bin directory:

<installation_directory>/bin/oupload.sh

<installation_directory>/bin/odownload.sh

Solaris 11 Patching Support

Oracle Solaris 11 uses IPS packages to deliver software and software updates. IPS (Image Packaging System) is a network-based package management system that is used for the entire software lifecycle, including package installation, upgrade and removal.

Introduced in SA 9.13 - Server Automation's Solaris 11 platform support for server patching allows you to update your managed servers to the latest versions of existing software without installing new software. This is a powerful way to keep your system up to date in an environment that no longer supports explicit patch units.

Solaris 11 patching support leverages the existing Solaris patching functionality, with a few differences to adapt to the new Solaris IPS package delivery structure. Additionally, there are setup requirements for setting up the initial IPS Package database.

Documentation: The SA 9.14 Solaris 11 Patching Whitepaper provides detailed instructions on setting up and maintaining the IPS Package database. This document also describes the Solaris 11 patch policy and remediation differences. This whitepaper is available via HP's Software Support Online at http://support.openview.hp.com/selfsolve/manuals.

Using Server Modules (SMOs) with Solaris 11

Solaris 11 introduces Role-based Access Control (RBAC), which affects the functionality of SA Server Modules (SMOs). SMOs rely on the root user to get information from the managed servers. In previous versions of Solaris, the root account is created as a user by default, with the option to have it as a role. In Solaris 11, the root account is created as a role by default; not as a user.

In order to enable the SMO functionality, the system administrator must modify the root account (root) to make it a user with regular login capability. The best method for doing this is to run an ad hoc script on the managed server.

To enable root for regular login capability:

1. Navigate to Devices > Servers > All Managed Servers.
2. Right-click on the target server and select Run Script > Select Script… and choose Define Ad hoc Script.
3. In the Script Contents, enter the line ‘rolemod -K type=normal root’ and click Next.
4. Choose Runtime User: root and click Start Job.

   After the job completes the user will be able to run the SMOs on the selected servers.

Note: To change the root account to a role again, complete the same procedure but enter ‘usermod -K type=role root’ in the Script Contents.

Oracle Solaris 11 OS Provisioning

Oracle Solaris 11 provides a service called the Automated Installer to handle OS Provisioning of bare-metal servers. The Oracle Solaris Automated Installer requires a new package type called IPS.

Solaris 11 OS Provisioning is somewhat different than the procedure used to provision Oracle Solaris 10.

The Oracle Solaris 11 Automated Installer no longer uses the Solaris JumpStart mechanism. Instead, SA components have been adapted to use the new Solaris 11 provisioning mechanism.

New Platform-Specific Changes

Installation Media

The installation media represents an IPS repository.

In order to obtain this repository:

1. Go to http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html?ssSourceSiteId=ocomen and download the images under "Oracle Solaris 11 11/11 Repository Image".  There are two ISO images: Part A SPARC, x86 (3.3 GB), and Part B SPARC, x86 (3.1 GB).
2. Follow the instructions on the download page to concatenate the two images into a single full image.
3. Mount the image and copy it to the SA Media server under the directory: /media/opsware/sunos

Performing OS Provisioning on the Same Core

If you need to perform OS Provisioning on the same core for both oracle Solaris x86 and Oracle Sun SPARC, create a link to the repository on the SA Media Server. This link is required because a Media Resource Locator (MRL) cannot be created using the same path for two operating systems.

For example:

# cd /media/opsware/sunos/
# ls -lsa
4 lrwxrwxrwx 1 root root 15 Mar 26 14:39 solaris11_link -> solaris11_repo/
8 drwxr-xr-x 3 root root 4096 Mar 26 14:33 solaris11_repo

Oracle Solaris Automated Installer

The Oracle Solaris Automated Installer uses two response files:

• ai.xml: for the Automated Installer to specify partitioning, locales, source repository and packages to be installed
• sc.xml: for System Configuration to specify hostname, user passwords and specific configurations, services configurations, hostname, network configurations.
  

  Note: Oracle documentation about creating ai.xml and sc.xml files can be found at: http://docs.oracle.com/cd/E23824_01/html/E21798/
  
  Since SA can handle only one response file per operating system and the Solaris Automated Installer requires two files for provisioning Solaris 11, SA provides a script, join_ai_sc.py, located in /opt/opsware/buildscripts/solaris/tools that can join ai.xml and sc.xml into a single file. The output file this script creates is then used as the response file for Oracle Solaris 11 provisioning.

Limitations

• Choosing Between Solaris 10 SPARC and Solaris 11 SPARC

  Because Oracle Sun SPARC provisioning uses the bootp protocol, there is no clear way to choose between Solaris 10 SPARC and Solaris 11 SPARC provisioning. Therefore, you must use the /opt/opsware/boot/jumpstart/tools/switch_solaris_sparc_miniroot command to tell SA which version of Solaris to choose.

• Enabling Oracle Solaris 11 x86 with the Manage Boot Client (MBC)

  By default, the Manage Boot Client (MBC) utility can only automatically provision Solaris 10 X86. To enable Oracle Solaris 11 X86 in MBC, run the tool /opt/opsware/boot/js-x86/tools/switch_solaris_x86_default_pxe and choose the desired default option from the Solaris Preboot Execution Environment (PXE) menu. Once Solaris 11 is set as the default, all machines that will boot into Server Pool will boot the Solaris 11 X86 miniroot. Also all MBC jobs will use the Solaris 11 X86 miniroot, causing MBC jobs for Solaris 10 X86 to fail.
  

Customizations

The new Oracle Solaris 11 OS provisioning mechanism allows the use of custom attributes to simplify system configuration.

These are:

OS Provisioning

OS Build-Plan Support for VMware ESXi5

SA briefly stops the VMware ESXi firewall in order to communicate the VM's IP Address, so that it can be managed by the SA core. SA restarts the firewall immediately afterwards.

If you do not want SA to stop and start the firewall, use static OS Provisioning instead.

HP ProLiant Gen8 Changes

For more information on any of these topics, see the SA UG: OS Provisioning and SA online help.

Support for OS Build Plans

HP ProLiant Gen8 models have two embedded service operating systems available: Linux and Windows Preinstallation Environment (Windows PE). SA can use either the Integrated Lights-Out (iLO) functionality of these embedded systems, or Preboot Execution Environment (PXE) booting.

To use the embedded systems' iLO functionality, you must add your server as an iLO device to the list of unprovisioned servers.

There are two ways to do this:

• Use the Run the OS Build Plan interface. In the second screen, where you select the target servers, you can add iLO devices one by one or through bulk comma-separated value (CSV) input.
• Right-click Devices > Servers > Unprovisioned Servers and select Add ILO Device.

In both these cases, you will need to manually provide iLO credentials and the corresponding SA realm (which is related to the SA Satellite or core available in the target network). This information defines the SA infrastructure to be contacted after the embedded service operating system is booted. When you use PXE booting, this information is provided by the PXE server automatically.

For more information on how to add your server, see" Installing (Provisioning) an Operating System" in the 9.10 UG: OS Provisioning.

Operating System Build-Plan Updates

The following 3 steps have been enhanced, or added, to build plans for HP ProLiant Gen8 support.

• Boot step - Enables SA to use the iLO library to boot the target server into its embedded service operating system. The step is transparent for non-HP ProLiant Gen8 target systems.
• Wait for Agent - Pauses the build plan until the SA Agent registers the target server and reports that it is in MAINTENANCE mode.
• Prepare Disks - Prevents the Windows installer from accidentally using the Virtual Installation Device (VID) as the target disk.

Virtual Installation Device (VID) handling

HP ProLiant Gen8 devices support special Virtual Installation Devices (VIDs).

SA handles VIDs as follows:

• If the BIOS VID setting is Hidden (default), SA detects the setting and handles VIDs automatically.
• If the BIOS VID setting is not Hidden, and you are using iLO with the HP ProLiant Gen8-specific embedded service operating systems (Linux or Windows PE), you must include the step "Prepare Disks on HP ProLiant Gen8" (see the HP ProLiant Gen8 online help) early in the build plan. Adding this step prevents the Windows installer from installing on the VID.

For more information on this topic and for specific use case, see "Prepare Disks on HP ProLiant Gen8" in the SA OS Provisioning README.

Running OS Build Plans on Servers

Build plans can now be run on servers that are in the pre-unprovisioned lifecycle.

SLES 11 SP1 kISO Handling

If you are using SuSE Linux Enterprise Server (SLES) 11 SP1 and above, you must do the following to support the SuSE kernel & driver update method using kISO:

1. Download the kISO & mount the ISO file for access.
2. Create (or reuse) a SLES distribution repository in a directory (for example: /repositories/SLES-11-SP1-x86_64).
3. Create a new directory called addon (the directory name does not have to be case sensitive, you can also use AddOn or ADDON) under your new repository directory (for example: /repositories/SLES-11-SP1-x86_64/addon).
4. Copy the kISO contents to the addon directory.
5. Replace the original installation kernel and initrd files with the kISO files found in the addon directory.
6. Copy the contents of the addon/boot/x86_64/loader/initrd directory to the following directory: boot/x86_64/loader/initrd.
7. Copy the contents of the addon/boot/x86_64/loader/linux directory to the following directory: boot/x86_64/loader/linux.

Note: If you experience driver problems with SLES 11 SP1 and kISO on HP ProLiant Gen8 target machines, see the following technical support documents:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03237879
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03237878

For more information on kISO handling, see the kISO media documentation and the OS Provisioning README.

OS Build-Plan Custom Attributes

Custom attributes set on the build plan will now be resolved and used in parameters and scripts during the execution of the build plan. If a custom attribute with the same name exist anywhere else on or in the servers’ hierarchy, its value will take precedence over the value set on the build plan. This is the priority order from highest to lowest:

1. server
2. device group
3. customer
4. realm
5. facility
6. OS
7. software policy
8. (new) OS build plan
   

Driver Update for HP ProLiant G6/G7 Servers

SA service operating-system drivers have been updated with the latest HP ProLiant SP drivers: SPP 2012.02 b51.

Multipath SAN Support for OS Provisioning

As of this release, SA provides multipath SAN support for the topics listed in this section.

OS Sequences

Red Hat 6 automatically identifies multipathing and enables kernel modules, but Red Hat 5 does not.

For Red Hat 5, before you run the Red Hat Enterprise Linux (REL) 5 OS Sequence, use the following steps to pass 'mpath' as a kernel argument for the server:

1. Define a custom attribute kernel_arguments for the server, and set its value to mpath.
2. Create the OS Installation Profile.
3. Add a custom attribute to the Installation profile, and set its value to mpath.
4. Set the value of the installation profile to mpath.

If you are performing multipath installation, it is also recommended that you add mpath as the kernel argument in the kickstart Red Hat 5 file. You can do this by creating a copy of Configure Default Red Hat 5 ks.cfg and modifying the file for use in your OS build plan.

SUSE Linux Enterprise Server 11

SUSE Linux Enterprise Server 11 does not identify multipathing by default. Use the procedures in this section to install SUSE Linux Enterprise Server on multipath LUNs.

• Updating Multipath Drivers

  You must copy the drivers into the media to enable multipathing. More information about the driver update disk (DUD) and the process of updating the media is available here:

  http://www.novell.com/support/viewContent.do?externalId=7009981&sliceId=1

  To configure SA, you must perform the following tasks:

  1. Download the driver update disk (DUD) from the above link.
  2. Extract the contents of the DUD to the SUSE Linux Enterprise Server 11 media.
  3. Upload the SUSE Linux Enterprise Server 11 media to the SA Media Server using the import_media command.
  4. If you already have the media uploaded into the SA Media Server, extract the contents of the DUD as directed by the SUSE support document.
     
     Note: After you complete these steps, multipathing will be enabled for all subsequent installations. To perform non-multipathed installations, create a separate SUSE media within SA Media Server.
• Defining Kernel Arguments

  To enable multipath installation, pass mpath as a value for the custom attribute kernel_argument by doing one of the following:

  1. When creating the OS Installation Profile, define the custom attribute kernel_argument and set its value to mpath.
  2. Before running the SUSE Linux Enterprise Server 11 OS sequence, define a custom attribute kernel_argument on the server to be provisioned, and set its value to mpath.
• Partitioning Section in AutoYaST

  SUSE Linux Enterprise Server 11 requires that devices be specified in Mapper format during multipath environment installations. SA OS Provisioning verifies the AutoYaST profile and modifies it to suit the multipathing environments, based on the following rules:

  Case	SA Solution
  #1 - AutoYaST does not have the partitioning section.	SA will add the partitioning section with the drive and device.
  #2 - Has a single drive section, but does not have a device section.	SA will insert the boot drive expressed in Mapper format.
  #3 - Has multiple drive sections, but does not have device sections. Has multiple drive sections but no <device> in <drive> section.	SA will not make any changes to AutoYaST. It will just print a warning and continue with the installations. This sort of configuration causes installation failure.  To ensure a successful installation, fill each of the drive sections with devices in Mapper formats.
  #4 - Has devices in the configuration Single _OR_ multiple drive sections and a <device> specified for the <drive>.	SA checks if the drive attributes in AutoYaST are in the correct Mapper format. If they are not, SA prints a warning and will not make any checks for correctness. If the drive attributes are not in the correct format, the installation fails.  To ensure a successful installation, fill each of the drive sections with devices in Mapper formats.

• Friendly Device Name

  The /dev/mapper devices should only be used during the installation. The SLES Storage Administration Guide states that, in the running system, the multipath devices should be accessed through /dev/disk/by-id/.

  SA will set up the scripts to convert the devices from /dev/mapper to /dev/disk/by-id when the user defines the custom attribute friendly_mpath_device to true.

Windows 2008/ Windows 2008 R2

Windows supports installations in multipath environments. Install multipath Device Specific Modules (DSMs) to further improve the capabilities of the target server. Import these DSMs into the SA Software Repository and install them using software policies attached to OS sequences.

You can modify the SAN Policy for the Windows Service OS (Winpe32, winpe64, winpe32-ogfs, winpe64-ogfs) shipped with SA. For more information about available options, see: http://technet.microsoft.com/en-us/library/cc749466(v=ws.10).aspx.

The default SAN Policy registry value in the SA-provided Windows pre-installation environment (WinPE) boot image is 1.

VMWare ESX/ESXi

VMWare ESX and ESXi support multipathing - no additional steps are required.

Use the Inject Multipath AutoYaST step

You must add the Inject Multipath AutoYaST Settings step to the OS build plan.

Perform the following tasks:

1. Create a new OS build plan by copying the default SUSE Linux Enterprise Server 11 Install Build Plan from the SA Client library.
2. Add the Inject Multipath AutoYaST Settings step after the Install And Configure SUSE Build Image step.
3. Add the Embed Files Initrd step after the Inject Multipath AutoYaST Settings step with the following parameters:

-s /tmp/user.autoinst.xml:/

The drive injections in the AutoYaST will be performed based on the criterion defined in the OS sequences (see Partitioning Section in AutoYaST).

Installation

This section describes the SA 9.14 installation procedure.

General Information

• SA 9.14 can be rolled back, but only to the previous full release, SA 9.10.
• The patch_opsware.sh script is used both for installing and for uninstalling SA 9.14.
• There's no need to supply a response file with patch_opsware.sh .
• The patch_database.sh script is used both for installing and rolling back database schema changes required for SA 9.14.
• You must run the patch_database.sh script on the First Core and all Secondary Cores. Note that the Model Repository and Oracle database can exist on a different host than the SA host.
• The response file used to last install/upgrade of the SA Core must be supplied when invoking patch_database.sh.
• This patch includes updated Server Agents that will be uploaded to the Software Repository. However, no agents will be upgraded on core machines (that is, in the Model Repository) or on Managed Servers without manual intervention.
• SA 9.14 can only be installed on systems running the following:
  • SA version 9.10 GA build (Build ID of opsware_45.0.6790.0)
  • SA versions 9.10.01, 9.10.02, 9.11, 9.12, and 9.13

  If any installed SA components (other than a previously installed patch) have a different build ID, you will not be allowed to install SA 9.14.

• To determine the build ID for a core machine, open the file:

/var/opt/opsware/install_opsware/inv/install.inv

and find the section beginning with %basics_ . Under this line, find the build_id .

For example:

%basics_linux

build_id: opsware_45.0.6790.0

When you install an SA patch, the patch installation updates the install.inv file to record the patch installation and the patch build ID.

For example:

%opsware_patch

build_id: opsware_45.0.17090.0

• Before a patch operation (such as install/upgrade/uninstall), all core/satellite services must be up and running. If any services are stopped or dysfunctional (as reported by the /etc/init.d/opsware-sas status command), the patch operation will terminate.
• Upon completion of a patch operation, all services on the core/satellite machine should  be up and running.
• If you are patching a multi-host core/satellite, you must patch each core and satellite host separately, one at a time.
• If you are patching a Multi-master mesh, HP recommends that you patch the primary core first, followed by secondary cores and satellites, thus ensuring that the primary core is at a higher version (such as SA 9.14 or higher) than the secondary cores.

  If you must roll back the SA 9.14 patch in a Multi-master Mesh, HP recommends that you roll back the secondary cores and satellites first, then the primary core.

• Mixed version core environments are not supported. However, during the patch upgrade, a transitory mixed core version environment is supported. For example, while the patch upgrade is in progress, cores at different patch levels can temporarily coexist in a Multimaster Mesh.
• In order to patch and/or roll back Wayscripts, the spog.pkcs8 certificate must exist under /var/opt/opsware/crypto (typically the certificate is installed with the Shell, SAS Web Client, or Build Manager). If the certificate does not exist, the patch operation will fail with the following error:

  Could not find spog.pkcs8 /var/opt/opsware/crypto/occ

  Copy the certificate from another core machine (for example, occ ) to
  
  /var/opt/opsware/crypto/occ
  
  and retry this operation.

  If this error is encountered, simply copy the certificate from another core machine to your core server and retry the operation.

• In order to patch and/or roll back Software Repository ( word ) updates, the spin.srv certificate must exist under /var/opt/opsware/crypto/spin (typically the certificate is installed with the Web Services Data Access Engine ( spin )). If the certificate does not exist, the patch operation will fail with the following error:

  Could not find spin.srv under /var/opt/opsware/crypto/spin.

  Copy the certificate from another core machine (such as occ) to

  /var/opt/opsware/crypto/spin

  and retry this operation.

• The following error may occur during upgrade on cores on which Solaris patching has not yet been set up:

  You don't have permission to update the patch meta database in HP SA.
Please re-run this command with a proper hpsa_user and hpsa_pass.
The hpsa_user needs permission to write the folder
"/Opsware/Tools/Solaris Patching" and the Package Management
Client Feature, "Manage Package" permission set "Read & Write".
There was a problem with running update_supplements.
Please refer to section Patch Management for Solaris of the Users Guide:
Application Automation manual for details on how to set up Solaris
patching on your core.

  You can safely disregard this error.

Script Running Order

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

SA Script Running Order - Upgrade

SA Script Running Order - Rollback

Migrating from SA 7.8 or SA 9.0 to SA 9.14

Migrating Order

When migrating from SA 7.8 to SA 9.1x:

• Upgrade to 7.87 first.
• Migrate all 2008 R2 servers using the script: windows_2008_R2_fix_script.pyc
• Upgrade to 9.1x.

When migrating from SA 9.0 to SA 9.1x:

• Upgrade to 9.04 first.
• Migrate all 2008 R2 servers using the script: windows_2008_R2_fix_script.pyc
• Upgrade to 9.1x.

No Leading Underscores Allowed for Users or Folder Names in 9.14

SA 9.14 does not support the use of leading underscores (_) in folder names; such as: _USER. Some previous versions of SA (7.81 and earlier) did allow these leading underscores in folder names. If you are upgrading to SA 9.14 on an SA Core that contains data created when the leading underscore was allowed, you will not be able to import that data on the Web Services Data Access Engine (twist) using CBT.

A subtle associated issue may occur in cases where a user has a leading underscore in their username, which means that user’s folder will also have a leading underscore. In this case, a user with a leading underscore in their username will also run into this issue.

When this error occurs during a CBT import/export operation on the Web Services Data Access Engine (twist), the following message will appear:

Rename all folders and users that begin with an underscore (_) before performing an export/import operation using CBT. Alternatively, contact HPSA Customer Support.

Adobe Flash Player

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.

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

1. Stop any instances of the SA Client.
2. Using Internet Explorer, access the following site: http://www.adobe.com/software/flash/about/
3. Make sure that the latest version of Adobe Flash Player is installed in Internet Explorer.
4. Restart the SA Client and run the features normally.
   

The error message should not display.

Database Schema Update Procedure

The script run during this procedure makes required changes to the Model Repository including adding required tables and objects.

1. Mount the SA 9.14 distribution. Invoke patch_database.sh on the Model Repository host:
   All SA Core Servers must have their time zone set to Coordinated Universal Time (UTC). In a RAC environment, all RAC nodes must have the exact same time.
   
   

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

1. Mount the SA 9.14 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

• Upgrading software repository content data is similar to using patch_opsware.sh from the upload distribution, but will only update those packages that have changed since the last major version.
• If you are upgrading a core hosted on multiple servers, the Software Repository content patch must be applied to the server hosting the Software Repository
  Store ( word store ).
• If you are upgrading a Multimaster Mesh, the Software Repository content upgrade should only be applied to the First Core (the upgraded content will automatically be propagated to other cores in the mesh).

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 roll back SA 9.14 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 SA 9.14 does not remove the Windows Server 2008 data that was created when the core was upgraded. For example, any Windows Server 2008 patches or policies created will remain. If you try to install these patches or attach the policies, an error will occur.
• Rolling back SA 9.14 does not delete any patches and policies that you have imported or created after the upgrade and these may fail with an error if you attempt to run them.

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.14. Some tasks might not be appropriate for your situation.

Windows Server OCLI Installation

If you plan to install the SA Command-line Interface (OCLI) on a Windows Server after upgrading to SA 9.14, 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.

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:

1. Identify the SA core server by checking the value field of the custom attribute CORD_OPSWwayscripts. To do so, log in to the SA Client as administrator (opsware admin user) and navigate to Administration > Customers. Select the Opsware Customer and view the Custom Attributes.
2. 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
3. Apply any required hotfixes to the wayscripts.

Upgrades

Customized Settings

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

Post-Upgrade Tasks

Patch De-duplication Steps for Windows Patching

Note: These steps should only be performed after upgrading to SA 9.14 from a previous release. If you are installing SA for the first time in 9.14, these instructions do not apply.

Duplicate patches can be inadvertently created in the SA database if you import the Microsoft Patch Supplement (MPS) and then run the SA Patch Import process using the Microsoft Offline Patch Catalog (wsusscn2.cab). These duplicates can cause conflicts during remediation and compliance checks.

How do I know if I have duplicates?

Resolving Duplicates

IMPORTANT: The de-duplication procedure varies based on your version of SA. For this reason, there will be multiple versions of this whitepaper, each providing release-specific instructions.

To find the whitepaper:

1. Go to HP Software Support Online: http://www.hp.com/go/hpsoftwaresupport

1. Click the Self-solve tab.
2. Log in using your HP Passport credentials.
3. Complete the search criteria:
1. All of these words: duplicate patches
2. Product:  Server Automation
3. Version: 9.14
4. Document types: Manuals and White Papers
5. Sort by: Relevance
4. Click Search.
5. Scroll down to see the results.

 Find filename: SA9.14_Windows_PatchingPatch_Supplement_wp.pdf
You can also do the same search directly from the SSO Product Manuals site: http://support.openview.hp.com/selfsolve/manuals

Back to the Table of Contents

Known Issues

This section describes issues from SA versions 9.0, 9.01, 9.02, 9.03, 9.10, 9.11, 9.12, 9.13, and 9.14. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.

Known Issues

Fixed Issues

The Fixed Issues table includes issues that:

• Were found by customers during SA 9.14 and fixed in the 9.14 release period.
• Were in the Known Issues table in previous releases, but are now fixed.

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

Fixed Issues

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.

API Methods (Deprecated)

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

Agent (Deprecated)

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.

Audit and Remediation

The Windows Hyper-V Manager rule type was deprecated from Audit Policies.

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 Manager in SA 9.0 is intended to replace CDR. See Application Deployment Manager in the SA Application Deployment User Guide for more information.

If you upgrade to SA 9.14 and also upgrade to an SA 9.14 agent, you will no longer be able to use CDR because it is only supported if you are using SA 9.01 (or earlier) agents. However, you will be able to use CDR with SA 9.14 if you uninstall the SA 9.14 agent and reinstall an SA 9.01 (or earlier) agent (not recommended, as you will be unable to use other SA 9.14 features).

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

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.

Virtualization

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.

Virtual Server Reports

The following Virtual Server reports were deprecated in 9.14:

• Server Reports/ Virtualization Reports/Virtual Servers by Virtualization Technology
• Server Reports/ Virtualization Reports/All Virtual Servers
• Server Reports/Virtualization Reports/VMware Virtualization Reports/Virtual Servers by Hypervisor (VMware only)
• Server Reports/Virtualization Reports/VMware Virtualization Reports/Resource Allocation by Hypervisor (VMware only)

Deprecated SMOs

The following SMOs were deprecated in 9.14:

• Library > (select by folder) > Opsware > Tools > Server Modules > com.opsware.server.module.hypervmanager_windows
  
• Library > (select by folder) > Opsware > Tools > Virtualization Management Modules > (here are 7 zip files and one software policy)
  
• Package:  vmm-vmware-esx-45.0.2748.0.zip (VMware ESX Server 3)
  
• Package:  vmm-vmware-esx-45.0.2749.0.zip (VMware ESX Server 3.5)
  
• Package:  vmm-vmware-esx-45.0.2749.0.zip (VMware ESX Server 4)
  
• Package:  vmm-vmware-esx-45.0.2749.0.zip (VMware ESX Server 4.1)
  
• Package:  vmm-vmware-esx-45.0.8508.0.5.zip (VMware ESX Server 3)
  
• Package:  vmm-vmware-esx-45.0.8508.0.5.zip (VMware ESX Server 3.5)
  
• Package:  vmm-vmware-esx-45.0.8508.0.5.zip (VMware ESX Server 4)
  
• Package:  vmm-vmware-esx-45.0.8508.0.5.zip (VMware ESX Server 4.1)
  
• Software Policy: VMware ESX VMM

Documentation Information

This section discusses documentation information for this release.

Documents Relevant to This Release

In addition to the SA 9.10 guides on the Self Solve website and the online help, the following white papers and guides are relevant to this release:

• Oracle RAC Support
• SA 9.14 HP-UX OS Provisioning
• SA 9.14 Patch Importer for Oracle Enterprise Linux
• SA 9.14 Resolving Conflicts between SA Patching and the MS Patch Supplement
• SA 9.14 SA-UCMDB Integration Guide
• SA 9.14 Server Patching Updates

• SA 9.14 Solaris 11 Patching
• SA 9.14 Support and Compatibility Matrix
• SA 9.14 Support and Compatibility Matrix for Storage Visibility and Automation
• SA 9.14 Upgrade Guide: Database and Middleware Automation
• SA 9.14: User Guide: Database and Middleware Automation
• SA 9.14 User Guide: Managing HP-UX Virtual Servers Using Server Automation

• Note: Some of these guides and white papers were also released in earlier releases, but are still relevant to SA 9.14.

Documentation Errata

This section contains corrections for existing documentation.

SA 9.10 Administration Guide

• Chapter 2: SA Core and Component Security
  • Page 110, Table 16, Core Recertification Configuration File: Properties, descriptions for agent_recert.using_cdr=<0 |1> and agent_recert.cleanup_old_agent_ca=<0 | 1> should be changed to the following:

    Property Name	Required?	Description	Example
    agent_recert.using_cdr=<0 | 1>	Yes	Specifies that the Agent CA push will be required when the value is set to 1. Also, the old Agent CA cleanup phase will be skipped unless the agent_recert.cleanup_old_agent_ca property is set to 1. Valid values are 1 (true) or 0 (false). Any other value will result in an invalid property error.  Default: 1. Note: CDR refers to Code Deployment and Rollback which has been deprecated but may still be in use.	agent_recert.using_cdr=1
    agent_recert.cleanup _old_agent_ca= <0 | 1>	No	Indicates whether to clean up the old AgentCA after Core Recertification. Cleanup of old Agent CA phase is not necessary and can be disabled. The valid values are 1 (true) or 0 (false). Any other value will result in an invalid property error. This is an optional property. Default: 0.	agent_recert.cleanup_old_agent_ca=0

  
  
• Chapter 5: SA Maintenance (page 193):

  In the Details: Start Order for SA Components list, item 16,  opswgw-lb, should be removed. The opswgw-lb component was incorporated into the Core Gateway (opswgw-cgw) component.

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

On page 25, Network Reports section, disregard the following reports:

• Duplex Compliance (All Servers)
• Duplex Compliance by Customer
• Duplex Compliance by Facility
  

The only reports available in SA are "Connections by Network Device" and "Connections by Server".

SA 9.10 Simple/Advanced Installation Guide

• Page 39:

  Under the heading "Network Requirements", the first bullet:

  • All SA Core Servers must be on the same Local Area Network (LAN or VLAN).

  should be changed to:

  • It is recommended that all SA Core Servers be on the same Local Area Network (LAN or VLAN). If cores are placed in different subnets, be aware that there may be performance issues.
• Page 195

  Under the heading "Required and Suggested Parameters for init.ora, Oracle 11.2.0", the following entry:

  db_file_multiblock_read_count := required to be = 16

  should read:

  db_file_multiblock_read_count := required to be >= 16

  Note: The required change is ">=" before the number "16"

• Page 214:

  As of SA 9.14, under the heading "Check for Sufficient Free Disk Space in the Tablespaces", the following SQL replaces the SQL in this section for checking free tablespace disk space:
  

SELECT
nvl(df.tablespace_name,'UNKOWN') name,
df.mbytes_alloc Mbytes,
df.mbytes_alloc-nvl(fs.mbytes_free,0) used,
nvl(fs.mbytes_free,0) free,
((df.mbytes_alloc-nvl(fs.mbytes_free,0)) / df.mbytes_alloc) * 100 pct_used,
nvl(df.largest,0) largest,
nvl(df.mbytes_max,df.mbytes_alloc) Max_Size,
((df.mbytes_alloc-nvl(fs.mbytes_free,0)) / df.mbytes_max) * 100 pct_max_used
FROM
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_alloc,
max(bytes)/1024/1024 largest,
sum(decode(autoextensible,'YES',greatest(bytes,maxbytes),bytes))/1024/1024 Mbytes_max
FROM
dba_data_files
GROUP BY tablespace_name
) df,
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_free
FROM
dba_free_space
GROUP BY tablespace_name
) fs
WHERE df.tablespace_name = fs.tablespace_name(+)
UNION
SELECT
D.tablespace_name name,
D.mbytes_alloc Mbytes,
((ss.used_blocks * F.block_size) / 1024 / 1024) used,
D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024) free,
((D.mbytes_alloc-nvl((D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024)),0)) / D.mbytes_alloc) * 100 pct_used,
nvl(((G.max_blocks * F.block_size) / 1024 / 1024),0) largest,
Max_Mbytes Max_Size,
((D.mbytes_alloc-nvl((D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024)),0)) / D.Max_Mbytes) * 100 pct_pct_used
FROM
(
SELECT
tablespace_name,
used_blocks,
free_blocks,
max_size
FROM
v$sort_segment
) ss,
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_alloc,
sum(decode(autoextensible,'YES',greatest(bytes,maxbytes),bytes))/1024/1024 Max_Mbytes
FROM
dba_temp_files
GROUP BY tablespace_name
) D,
(
SELECT
B.name,
C.block_size,
SUM (C.bytes) / 1024 / 1024 mb_total
FROM
v$tablespace B,
v$tempfile C
WHERE B.ts#= C.ts#
GROUP BY B.name, C.block_size
) F,
(
SELECT
B.name,
max(blocks) max_blocks,
sum(blocks) total_blocks
FROM
v$tablespace B,
v$tempfile C
WHERE
B.ts#= C.ts#
GROUP BY B.name
) G
WHERE
ss.tablespace_name = D.tablespace_name and
ss.tablespace_name = F.name and
ss.tablespace_name = G.name;

• Page 195
  • Under the heading "Required and Suggested Parameters for init.ora, Oracle 11.2.0", the following entry:
  • db_file_multiblock_read_count := required to be = 16
  • should read:
  • db_file_multiblock_read_count := required to be >= 16
  • Note: the required change is ">=" before the number "16"
• Chapter 2: System Requirements, Table 15

  Add the following required open port:

  • 3003 (SA Gateway)
  
  

• Chapter 7: Multimaster Mesh Installation (page 141):

  Step 4: The following bullet should be removed, as the truth_data.tar.gz is no longer a valid file:

  • The path to the Model Repository content export file, truth_data.tar.gz, must be
    the same for both the First Core's Model Repository server and the Subsequent Core's
    Model Repository server.

• Chapter 8: Satellite Installation

  • Page 146:

    Remove the following bullet:

    • You must know how to edit files using the vi editor. By default, the Gateway Installer launches the vi editor during the installation process, which you will use to edit the Gateway Properties File.
  • Page 157
    • Remove from the parameter list:
      • satellite.host.ip
• Chapter 10: "SA Core Uninstallation" (page 169):

  Under the heading "Uninstall a Single Core in a Multimaster Mesh", remove step 1a. This step is no longer required.

• Appendix A, "Oracle Setup for the Model Repository", page 191, the section titled "Oracle XDB Component Installation Requirements" should be removed or ignored. From SA 9.10 onwards SA uses the Oracle Data Pump utility rather than the Oracle Export utility.
• Appendix A: To reflect support for Oracle 11.2.0.2, replace the section in Appendix A on page 26, "Oracle RAC Support", with the white paper: Oracle RAC Support, which you can download from http://support.openview.hp.com/selfsolve/manuals, SA 9.14 release section.

SA 9.10 User Guide: Application Configuration

• Page 116:

  typo in table 10, row 1. "... where the value will be stored in the value wet."  It should say, "... where the value will be stored in the value set.”

• Page 117 and Page 130:

  For the RejectResponseUrl tag the range is wrong:

  r'
  (HTTP_URLSCAN_STATUS_HEADER)|(
  HTTP_URLSCAN_ORIGINAL_VERB)|(H
  TTP_URLSCAN_ORIGINAL_URL)';optional@
  It should use double quotes instead of single:
  r"
  (HTTP_URLSCAN_STATUS_HEADER)|(
  HTTP_URLSCAN_ORIGINAL_VERB)|(H

  TTP_URLSCAN_ORIGINAL_URL)”;optional@

• Page 119, row 2, cell 1 in the table:

  Delete [Options] and replace with [AllowExtensions]

• Page 122:

  Replace the sentence:

  "The field delimiter used here will be an end of line element which instructs the parser stop reading an entry when it encounters the end of a line."

  With the following sentence:

  "The field delimiter used here will be an end of line element which instructs the parser to stop reading an entry when it encounters the end of a line."

• Page 123, Table 14, CML Tag : @*deny_url_sequence;unordered-string-set;;field-delimiter-is-eol@

  Replace this in the Description column:

  "sequence-delimiter=":"
  Instructs the parser to read a colon ( : ) as part of the string and the point at which to move on to the next entry."

  With the following:

  "field-delimiter-is-eol
  Instructs the parser to read the next entry up to the end of the line. "

• Page 124

  Replace this sentence:

  "Next type the following CML replace tags to define the three kay value."

  With this sentence:

  "Next type the following CML replace tags to define the three-key value."

• Page 135:

Replace this sentence:

"The filename-key value is a pathname. It must start with a slash."

With this sentence:

"The filename-key value is a pathname. It does not have to begin with a slash."

• Pages 138, 139, 152, 160:

  Replace this range:

  1024<=,<=2048

  With this range:

  1024<=&<=2048

• Page 140, end of Use Case 1:

  Replace this sequence:

  "/examples/namespace/ip"

  With this one:

  "/example/namespace/ipaddress = 192.168.0.1"

• Pages 151, 155, 157, 159:

  Replace this sentence:

  "Source: The source attribute is the database key"

  With this sentence:

  "Source: The source attribute is the key."  

• Page 155:

  Replace this sentence:

  "The only required element in a replace tag is the source"

  With this one:

  "The only required element in a loop tag is the source"

• Page 168

  Replace this sentence:

  "The filename-key value is a pathname. It must start with a slash."

  With this sentence:

  "The filename-key value is a pathname. It can be written as a relative path and does not need to begin with a slash (/)."

• Page 177:
  • Replace this word:

    "sequence-delimiter-iswhitespace"

    With this one:

    "sequence-delimiter-is-whitespace"

  • Replace this word:

    " sequence-delimiter-issemicolon "

    With this one:

    "sequence-delimiter-is-semicolon "

  • Add the following instructions to the delimeter attribute section:

    The delimiter Attribute
         whitespace-delimited
      comma-delimited
      semicolon-delimited
      tab-delimited
      quote-delimited
      delimiter

    Instruction Tag Syntax
         @!whitespace-delimited@
      @!comma-delimited@
      @!semicolon-delimited@
      @!tab-delimited@
      @!quote-delimited@
      @!delimiter={string}@
                   
     whitespace-delimited is the default behavior

    Option Attribute Syntax
          @[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;whitespace-delimited[;{option}]...]]]]@
          @[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;comma-delimited[;{option}]...]]]]@
          @[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;semicolon-delimited[;{option}]...]]]]@
          @[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;tab-delimited[;{option}]...]]]]@
          @[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;quote-delimited[;{option}]...]]]]@
          @[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;delimiter={string}[;{option}]...]]]]@

    whitespace-delimited is the default behavior.

    Description
                    delimiter sets the default delimiter character. If not explicitly specified, sequence-delimiter and field-delimiter will inherit this value.
     Valid for replace and sequence tags.

• Pages 177 and 178:
  • Both the sequence-delimiter and the field-delimiter are missing a way to specify the value for the delimiter. The extra way is " sequence-delimiter-is-quote " (and " field-delimiter-is-quote " respectively). The syntax is like the existing documented ways.
  • It is repeatedly stated that " ...delimiter-is-whitespace " is the default behavior. This is false; those lines should be replaced by: "By default, field-delimiter uses the value of delimiter (the default for the latter is whitespace-delimited)" and "By default, sequence-delimiter uses the value of delimiter (the default for the latter is whitespace-delimited)," respectively.

SA 9.10 User Guide: OS Provisioning

• The DHCP setup step should be removed from the HP-UX OS Provisioning section of the SA 9.10 User Guide: OS Provisioning. As of SA 9.05 and 9.11, DHCP is enabled by default and the OS Provisioning menu now includes HP-UX.
  

  Complete HP-UX OS Provisioning instructions are provided in the SA HP-UX OS Provisioning Whitepaper, which can be downloaded for any relevant SA 9.x release from the HP Support Self-Solve website: http://support.openview.hp.com/selfsolve/manuals or http://support.openview.hp.com/selfsolve/documents

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

SA 9.10 User Guide: Server Automation

• ‘Agent Uninstaller Options’ section, after ‘Table 47 Agent Uninstallation Unix Options’ add the following paragraphs:

  When Agent uninstall is attempted on a core machine and the --force uninstall option is not provided, the following warning is prompted:
  
  WARNING: The server is owned by the OPSWARE account. Probably it is a core machine.
  

  Are you sure you want to uninstall the Opsware Agent? [y/n]:

  If the 'n' option is selected, the Agent uninstall is aborted. Otherwise, the uninstall proceeds.

• 'Agent Installer Options’ section, after ‘Table 46 Agent Installer Options’ add the following paragraphs:

  When installing the Agent on a core machine that already has the Agent installed and the --coreinstall installer option is not provided, the installation is aborted with the following error message:
  

  You are trying to install the agent on a core machine without passing the --coreinstall argument.

• Appendix B:
  • Page 470, "Prerequisites for Using the Agent Upgrade Tool", the first bullet, second paragraph should read:
    

    Installing the opsh RPM places the OGFS shell and the Agent Upgrade Tool in the directory /opt/opsware/opsh/bin.

  • Page 475, "Example: Commands and Output for Agent Upgrade Tool", the first line should read:

    # cd /opt/opsware/opsh/bin

SA 9.10 User Guide: OS Provisioning: Support for Linux PowerPC 64-based Network Booting

From an Open Firmware prompt, enter:

0 > boot net:,yaboot,,

This retrieves the yaboot boot loader and the boot menu is displayed:

"Choose a boot image by entering the appropriate label at the 'boot:' prompt.

linux5    - Linux Build Agent (RHEL 5.8-based)
linux6    - Linux Build Agent (RHEL 6.3-based)

Welcome to yaboot version 1.3.17
Enter "help" to get some basic usage information
boot:"

Support Matrix

Please note the following documentation errors:

• French locale support for the following platforms was not listed in the 9.10.01 and 9.10.02 matrices. French locales have been supported on these platforms since 9.10:
  
  Managed Servers:
  HP-UX 11iv3 (11.31) IA_64              
  SuSE Linux Enterprise Server 11 GA-SP1,  x86_32/x86_64      
  SuSE Linux Enterprise Server 10 GA-SP3,  x86_32/x86_64
  
  Core Servers and Satellites:
  SLES 10 SP2-SP3, x86_64

• SA 9.1x support for BSAE 2.0, 2.01, and 9.12 was misstated in previous versions of the SA 9.1x Support and Compatibility Matrix.

  In the HP BSA Essentials column in the Cross-Product Compatibility section, remove all references to the following: 2.0, 2.01, 9.12.

Documentation Additions

This section contains additions to existing documentation.

SA 9.10 Simple/Advanced Installation Guide

• Chapter 6: First Core Post-Installation Tasks, page 115, SA DHCP Network Configuration Tool (dhcpdtool) section, add the following procedure:

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


    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, 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";

• Chapter 8: Satellite Installation

  • Pages 153 to 155, Table 8:
    • Add the following entries:

      - word_tmp_dir: directory where Package Repository will temporarily  place content during uploads

      - word.store.host: the host name of the server where Software Repository content is stored.

      - media_server.windows_share_name: the share name to use for the Windows media sharing server (note: share names that are longer than 8 characters may give errors while browsing or may not be accessible to some older clients.)

      - media_server.windows_share_password: the password to write-protect the Windows media share. Import_media tool will prompt for this password each time it is run.

  • Page 157
    • Add to the parameter list:
      cast.admin.pwd: the password for the SA admin user - Simple and Advanced
  • Page 146
  • Add the following under the heading "Satellite Installation Requirements"

    Satellite Free Disk Space Requirements

    This section describes the free disk space (in addition to the operating files system) requirements for any SA Satellite.

  Satellite Component Directory	Recommended Free Disk Space
  /opt/opsware	15 GB
  /var/log/opsware	10 GB
  /var/opt/opsware	20 GB (dependent on caching plans and the core cache size)
  /osmedia	15 GB (dependent on OS Provisioning needs)

• Appendix A: Oracle Setup for the Model Repository, page 197 tnsnames.ora Requirements:

  The first bullet should read:

  " The tnsnames.ora file must reside in the following locations:

  • /var/opt/oracle/tnsnames.ora
  • $ORACLE_HOME/network/admin

SA 9.10 Administration Guide

• Chapter 7: Notification Configuration, Setting Email Alert Addresses for an SA Core (page 229):
  • Add the following bullet to Step 4: In the field, CronbotMailAlertsEnabled, specify the value 1 to enable cronbot email alerts. To disable cronbot email alerts, specify the value 0.

SA 9.10 User Guide: OS Provisioning

• Chapter 4 (page 86), Table 9: "Linux or VMware ESX Custom Attributes"

  Add the following custom attribute to Table 9:

  Timeout

  Values: the number of minutes to wait for Linux provisioning to complete before timing out.

  Default: 30 minutes

  If Linux provisioning fails because the job takes too long to complete, you can specify a longer timeout period.

• Chapter 5, "Special Attributes for the CLI and CSV Input Form",  Table 12:

  The table entry for the "facility" special attribute should be changed to note that it is the Facility ID that is required, not the Facility Name.

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:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

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

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