Software version: 10.02
Original Publication Date: August 15, 2014
This document provides an overview of the HP Server Automation Virtual Appliance (SAVA) 10.02 release. It contains important information not included in the manuals or in the online help. In addition, see the Server Automation 10.02 release notes.
All the documentation is available from the new SA 10.x Documentation Library. See the section Documentation Information for instructions on how to use the Documentation Library to access the guides and whitepapers relevant to this release.
SA release notes contain information for users who are familiar with the installation and maintenance of SA, Storage Visibility and Automation, SE Connector, Application Deployment Manager, and DMA integration. The notes contain information that is not included in books or online Help.
What's New in This Release |
Post-Installation / Upgrade Tasks |
Documentation Information |
Installation |
Known Issues |
HP Software Support |
Fixed Issues |
Legal Notices |
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/.
Important: SA 10.02 uses OpenSSL 1.0.1h and, as a result, is not susceptible to the Heartbleed or Man in the Middle vulnerabilities.
This section lists the operating-systems supported on the SA Client.
For complete SA support and compatibility information, see the HP Server Automation Support and Compatibility Matrix for this release at: http://support.openview.hp.com/sc/support_matrices.jsp.
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 at the same link.All SA and Storage guides are available at: http://support.openview.hp.com/selfsolve/manuals.
For more information about supported configurations, see SA 10.0 Installation Guide, chapter 2: “SA Core Configurations Supported For Customer Installation”.
See Post-Installation/Upgrade Tasks for the SA Agent upgrade requirement.
For information on the Agent Upgrade tool, on installing the agent, and on bringing servers under SA management, see the SA User Guide: Server Automation.
SA 10.02 requires that the following ports be open:
8084/8086 - For bandwidth management, if enabled
These, and other ports, are configurable at install/upgrade time through installer parameters.
Note: In addition, other ports are required to be open for previous releases of SA. See the corresponding release notes at:
http://support.openview.hp.com/selfsolve/manuals.
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/.
Two non-supported features (Code Deployment and Rollback (CDR), and Configuration Tracking) were removed from the SA Client interface.
CDR was replaced by ADM. Configuration Tracking was replaced by A&R.
Note: For more information about installation, see the Server Automation Virtual Appliance (SAVA) Installation and Administration Guide.
There is a new patch-installation procedure.
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.
Upon completion of the patch operation, the version tag in Overview in the Settings screen should display: 7.2.0-52580.
This section discusses how to install this patch on the core SA server.
Prerequisites
Before you upgrade your cores to the SAVA 10.02 SAVA patch:
Contents
SAVA 10.02 consists of two .bin files: a pre-upgrade file (prepatch_10.02.bin) and an upgrade file (hpsacordpatch_10.02.bin). The two files are described in the following table:
| File Name | Description |
|---|---|
hpsa_prepatch_10.02_52580.bin |
This pre-upgrade file:
|
| hpsa_cordpatch_10.02_52580.bin | Upgrades SAVA 10.0 to SAVA 10.02. After this file runs, the system reboots itself.. |
Upgrade Procedure
Note: Review the prerequisites section before starting the upgrade procedure.
Note: Do not press any other buttons until you see the file name and version displayed in the Appliance Update dialog box. The dialog box also displays the expected file-installation time, and tells you whether you will need to restart the system.
The Remove link allows you to remove the uploaded file. If you upload a file and then close the browser without installing the patch, the uploaded file persists. When you return to the Update Appliance dialog box, you will be able to pick up where you left off (post-upload and pre-install).
Note: If you cancel an upload or remove an uploaded file, you must clear your browser cache and restart your browser before you attempt another upload.
The Remove link allows you to remove the uploaded file. If you upload a file and then close the browser without installing the patch, the uploaded file persists. When you return to the Update Appliance dialog box, you will be able to pick up where you left off (post-upload and pre-install).
Note: If you cancel an upload or remove an uploaded file, you must clear your browser cache and restart your browser before you attempt another upload.
If the system does not come back up after the upgrade, or if a retry of the update procedure does not succeed:
Error occurred while verifying image file: hpsa_cordpatch_10.02_52580.bin is corrupted. Please download image file and try again.
If this error message is displayed:You cannot roll back SAVA 10.02 to SAVA 10.0. You can only revert to the previous version by using a snapshot. See the Prerequisites section.
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:This section lists the tasks that should be performed after you install or upgrade to SA 10.02. Some tasks might not be appropriate for your situation.
This section lists the tasks that should be performed after you upgrade to SA 10.02.
After you upgrade to SA 10.02, you should also upgrade to the 10.02 SA Agents on each Managed Server in the facility. If you do not upgrade your agents, the new functionality will not be available.
See the SA 10.0 Upgrade Guide for instructions on upgrading your SA Agents.
If you have customized such settings as Java heap settings, you must reapply your customizations after you install SA 10.02, as the settings are set to the SA default during installation or upgrade.
If you plan to install the SA Command-line Interface (OCLI) on a Windows Server after upgrading to SA 10.02, 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.
In a number of places, the SAVA appliance user interface (UI) displays options or choices that are greyed-out. These choices or options are unsupported.
Note: The Server Automation-Executive Scorecard (SA-XS) integration does not support a configuration with XS 9.5 and SA 10.1. See XS documentation for details.
| QCCR1D | Symptom/Description | Platform | Workaround |
|---|---|---|---|
| Agent | |||
| QCCR1D166492 | If you change the IP address of the SAVA Appliance, you must reinstall all the agents on the existing managed servers. |
Independent | None |
| Appliance | |||
| QCCR1D164077/ QCCR1D 164151 /QCCR1D164143 |
.bin file names cannot includes spaces or special non-English characters.
When the file name does include these, the files might not be uploaded, the appliance will malfunction, and, if the characters were non-English characters, the file name will be changed to nonsensical characters.. |
VMware ESXi. Linux | Do not use spaces or special characters in .bin file names.
|
| QCCR1D164966 | Multiple SA jobs fail after Appliance and SA network information is changed through the Appliance interface. |
SAVA/VMware | There is no workaround once the change is made through the Appliance interface. NOTE: Do not change Appliance and SA network information from the Appliance interface after the Appliance FTS (First Time Setup) has been completed. |
| HP Live Network Connector from SAVA Command-Line Utilities APXs | |||
| QCCR1D175236 | Content import from HP Live Network for SAVA fails in an air-gapped setup (that is, importing without network connectivity). |
Independent | Make sure you have network connectivity before you import. |
| Interface | |||
| QCCR1D162957 | In the SAVA User Interface (UI), when you click the HP icon in the upper-right corner, nothing happens. This icon has no function. |
Independent | N/A. |
| QCCR1D | Symptom/Description | Platform | Workaround |
| Installer | |||
| QCCR1D162830 | The SAVA appliance might not reboot automatically during initial appliance setup. Specifically, the appliance becomes unresponsive after you enter network information on the console and the Applying network settings screen is displayed. | Independent | If the appliance does not reboot within 10 minutes, use the VMware tools to reboot the server manually, and then log in again with your new Administrator password. The network setting screen displays the information you already entered. Click OK to accept the settings and to initiate the reboot. |
| QCCR1D162574 | After you enter network information on the console and the Applying network settings screen is displayed, you sometimes see the following error message:
An error was encountered while retrieving OS Deployment settings. Ignore this message.
|
Independent | The appliance will reboot on its own in a few minutes. |
| QCCR1D174973 | SAVA 10.02 patch upload fails when using Internet Explorer. | Independent | Use one of the following browsers instead of Internet Explorer when you upload the SAVA 10.02 patch:
|
| ISM Tool | |||
| QCCR1D163521 | After the ISM Tool is installed, if commands (such as ismtool.cmd, ismusertool.cmd) are issued, they fail with the following error:
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail. |
Windows | Install Microsoft Visual C++ 2005 Redistributable (x86). |
| Software Management | |||
| QCCR1D163167 | If configured to import packages for unsupported platforms (such as RHEL 5 i386), rhn_import will not filter out those packages. Instead, the packages will be imported and the corresponding software policies will be created for the unsupported platforms. All these will be visible in the By Folder view of the Library. |
Independent | None |
| QCCR1D163518 | Server remediation is completed but the job is still in progress, and the end job button is enabled. | Independent | None |
| QCCR1D163868 | When remediating two different versions of the same rpm package with the install flag set, the older version of the package will be overridden by the newest one, instead of having two different versions of the same package installed on the managed server. |
AIX, Linux, Solaris | None |
| QCCR1D166144 | When trying to remediate a Linux software policy with a large number of rpms on a SAVA core against a managed server, a PostgresSQL error might be thrown. | Independent | Try splitting the policy into smaller policies, or contact HP Support. |
| User Interface | |||
| QCCR1D162015 | When setting the SAVA appliance hostname, the managed server instance that represents the core still shows the hostname in the format ci-<mac address>. | Independent | The SA agent on the SA core instance in the appliance always picks up the internal hostname. This has no adverse effects on SA. |
The complete list of 10.0x known issues reported by customers can be found on the SSO Portal at: http://support.openview.hp.com/selfsolve/. For more information on how to access and use this site, see How to Find Information Resources.
Note: Search for Product: Server Automation, Version: 10.00, Document Types: Known problems.
For a list of fixed issues please seethe SA 10.02 Releases Notes.
The complete list of 10.0x fixed issues reported by customers can be found on the SSO Portal at: http://support.openview.hp.com/selfsolve/. For more information on how to access and use this site, see How to Find Information Resources.
Note: Search for Product: Server Automation, Version: 10.00, Document Types: Fixed problems.
This section discusses documentation information for this release.
In addition to the 10.0 guides on the Self Solve website, the following white papers and guides are relevant to this release:
Note: Some of these guides and white papers were released in earlier patches, but are still relevant to SA 10.02.
This section contains corrections for existing documentation.
* Chapter 2: SA Core and Component Security
Page 104, Recertifying SA Cores section - replace the entire section/steps with the following:
Recertifying SA Cores
Note: You must clear all backlogs and conflicts on your Multimaster Mesh before you start a core
recertification.To recertify SA Cores, perform the following tasks:
1. Ensure that you are classified as a Core Recertification User. If not, see your SA System
Administrator.2. Log on to an SA Core host.
3. Change directory to /opt/opsware/oi_util/OpswareCertTool/recert_utils/.
4. Edit corerecert.conf to ensure that the information is correct for your environment.
5. Run: corerecert --status to ensure Core Recertification is not currently in progress.
6. Run: discover_mesh -p to make sure the Core Recertification Tool can correctly detect your Mesh setup.
7. Run: corerecert --phase 1 from the command line to initialize Core Recertification.
8. Monitor the progress on screen by running: corerecert --status until it has indicated Phase 4 is in progress.
9. Run: corerecert --phase 4 from the command line to start Phase 4, which appends a new Agent CA to all the Agents.
10. Monitor the progress on screen by running: corerecert --status until all the Agents have successfully had a new agent CA appended.
Note: This step could take days depending on your maintenance windows and the Agent availability. There can be only one scheduled or active Agent Recertification job per facility at any given time. If you encounter any errors during this stage, resolve the errors and go back to step 9 on page 105. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recert job for the successful facilities.
11. Run: corerecert --phase 6 --doit from the command line to start Phase 6 of the core recertification.
12. Monitor the progress on screen by running: corerecert --status until it has indicated mesh_restart_pending. At this point, you must work with the SA System Administrator to restart the mesh.
Note: This step could take days depending on your maintenance window. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 11.
13. After the mesh has successfully restarted, run: corerecert --phase 6 from the command line to continue phase 6.
14. Monitor the progress on screen by running: corerecert --status until phase 7 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 13 on page 106.
15. Run: corerecert --phase 7 from the command line to start phase 7.
16. Monitor the progress on screen by running: corerecert --status until phase 8 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 15.
17. Run: corerecert --phase 8 from the command line to start Phase 8, which recertifies all the Agents.
18. Monitor the progress on screen by running: corerecert --status until all Agents have successfully been recertified.
Note: This step could take days depending on a customer’s maintenance windows and the agent availability. There can be only one scheduled or active Agent Recertification job per facility at any given time. If you encounter any errors during this stage, resolve the errors and go back to step 17. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.
19. Run: corerecert --phase 9 from the command line to start phase 9. The Core Recertification Tool prompts you to confirm that you want to begin phase 9. Press y to continue.
20. Monitor the progress on screen by running: corerecert --status until it has indicated mesh_restart_pending. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 19. At this point, you must work with your SA System Administrator to restart the mesh.
Note: This step could take days depending on the customer’s maintenance window. If you encounter any errors during this stage, resolve the errors and go back to step 19 on page 106. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.
21. On the base Slice core server:
a) Issue the following commands:
touch /var/opt/opsware/crypto/twist/upgradeInProgress
/etc/init.d/opsware-sas restartb) Wait till the restart successfully finishes, then
c) Restart the rest of the mesh.
22. After the mesh has successfully restarted, the Recertification User must run: corerecert --phase 9 from the command line to continue phase 9.
23. Monitor the progress on screen by running: corerecert --status until Phase 12 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 22
24. If you do not intend to remove the Agent CA, skip to step 26. Otherwise, run: corerecert --phase 12 from the command line to start phase 12, which removes the old Agent CA from all the Agents.
25. Monitor the progress on screen by running: corerecert --status until the old Agent CA has removed from all the Agents.
Note: This step could take days depending on customer’s maintenance windows and the agent availability. If you encounter any errors during this stage, resolve the errors and go back to step 24. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.
26. Run: corerecert --phase 13 --doit from the command line to start phase 13. If you do not want to remove the old CAs, a Mesh restart is not required in this phase.
27. Monitor the progress on screen by running: corerecert --status until it indicates mesh_restart_pend. At this point, you must work with the SA System Administrator to restart the mesh.
Note: This step could take days depending on the customer’s maintenance window. If you encounter any errors during this stage, resolve the errors and go back to step 26.
28. After the mesh has successfully restarted, run: corerecert --phase 13 from the command line to continue phase 13.
29. Monitor the progress on screen by running: corerecert --status until it indicates that Core Recertification has completed successfully.
* Chapter 4: "Pre-Installation System Requirement Checks", Item #6: Check the Free Disk Space Requirements (page 49), Table 9: SA Disk Space Requirements: the disk space requirements have changed to reflect changes for the CORD patches and hotfix installations.
Several directories are created under the /var/opt/opsware and the /opt/opsware directory to facilitate the patching. The diskspace requirements listed below have been increased to handle the patch media requirements:
/opt/opsware 25 GB
/var/opt/opsware 20 GB
* Chapter 5, "Special Attributes for the CLI and CSV Input Form", Table 12, page 127:
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.
* Appendix A, "Crypto Match (CRP) Test, page 314-315:
The section "CRP – Agent certificate mismatch" should read:
This result indicates that the SSL certificate that the Agent is using (cogbot.srv) does not
match the SSL certificate that is registered with HP Server Automation for that Agent. Also,
a server hosting a Slice Component bundle with the wrong time zone specified could cause a
large number of servers with a CRP error during a communications test.What Can I Do If I Get a Certificate CN Mismatch During a CRP Test?
If the mismatch is determined to be due to a time zone mismatch, synchronize the time zone
specifications for the servers. If the error is due to a certificate mismatch, use the Recert
Agent Custom Extension to issue a new certificate to the Agent.
SA 10.0 does not support Oracle 10g.
Ignore the following information in the Upgrade Guide:
* SA 10.0 Upgrade Overview, Page 12, Changes to Oracle Initialization Parameters.
* SA 10.0 Upgrade Prerequisites, Page 31, open_cursors Value section.
Footnote 5 under the Core and Satellite Server Support table was incomplete.
Original:
5 For RHEL5 U9, the latest update version kernel 2.6.18-348.16.1.el5 or above is required.
Changed to:
5 IMPORTANT Note about Red Hat 5.9, 6.3 and 6.4: If you are running a default RedHat 5.9, 6.3, 6.4 kernel, you must upgrade the kernel to a version that no longer has an issue with the SO_REUSEADDR socket semantics. This can be accomplished by installing the latest kernel from the RedHat errata advisory, or installing the next release of RedHat Linux, as described below:
- use the latest version kernel, 2.6.18-348.16.1 or above. See Red Hat errata: http://rhn.redhat.com/errata/RHSA-2013-1166.html
- or upgrade to RHEL 5.10
- use the latest version kernel, 2.6.32-358.18.1 or above. See Red Hat errata: http://rhn.redhat.com/errata/RHSA-2013-1173.html
- or upgrade to RHEL 6.5.
Back to the Table of Contents
All the latest Server Automation documentation for this release is available from the *new* SA 10.x Documentation Library:
http://support.openview.hp.com/selfsolve/document/KM00417675/binary/SA_10_docLibrary.html
Use the SA Documentation Library to access any of the guides, release notes, support matrices, and whitepapers relevant to this release or to download the full documentation set as a bundle. The SA Documentation Library is updated in each release and whenever the release notes are updated or a new whitepaper is introduced.
A direct link to the SA Documentation Library is also provided on the SA Client Help Welcome Page. From the SA Client menu, select Help > Help Contents, Index and Search.
This section includes a list of technical information resources for each product.
To access the information resources for the included products, use any of the following methods:
Note: Some of guides and white papers, although released in earlier patches, are still relevant to this release. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. Note the Document Release Date on the title page of your guide and see the Documentation Change Notes on page 3 of most documents for a list of any revisions. The release-notes change table is at the bottom of this document.
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.
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.
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 2000-2014 Hewlett-Packard Development Company, L.P.
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.
| 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.