This document provides an overview of the Smart Plug-ins DVD for HP Operations Manager for Windows. It contains important information not included in the Installation and Upgrade Guide.
In
This Version
Documentation
Updates
Installation
Notes
Known
Problems, Limitations, and Workarounds
Support
Legal
Notices
The October 2008 HP Operations Smart Plug-ins DVD runs with HP OpenView for Windows version 7.50 and HP Operations Manager for Windows version 8.10. It contains the following SPIs and SPIs components:
Note: Click here to see the list of SPI documents available with this release. You can also see the documentation for the installed SPIs under the %OvInstallDir%/paperdocs\en\SPI_Documentation folder on the management server.
The first page of this release notes document contains the publish date, which changes each time the document is updated.
To check for recent updates or to verify that you are using the most recent
edition, go to the following web site:
http://h20230.www2.hp.com/selfsolve/manuals
Prerequisite: Before you install Smart Plug-ins, you must have OVO for Windows 7.50 or HPOM for Windows 8.10 installed on a management server.
To ensure a successful Smart Plug-in installation, follow one of the procedures below:
1. Installing OVO/HPOM for Windows, then the Smart Plug-ins:
2. Installing Smart Plug-ins on a system already running OVO/HPOM for Windows:
Before installing the HP Operations Smart Plug-ins, make sure that your system meets the following minimum requirements:
This release contains certain unresolved problems, some limitations, and there are workaround to help solve certain problems.
Problem: After uninstalling the SPIs by using SPI DVD, Generic JMX components do not get uninstalled.
Workaround: Manually remove the Generic JMX components by double-clicking Generic_JMX_Component.msi.
Problem: After upgrading the windows DCE agent on an existing node to an HTTPS agent, SPI specific data does not get logged into CODA.
Workaround: Before upgrading the windows DCE agent on an existing node to an HTTPS agent, you must apply the necessary hotfix on the node. To obtain the hotfix necessary for DCE-to-HTTPS agent migration, contact HP Software Support. You can go to the HP Software Support web site and submit a support case to obtain the hotfix.
Problem: SPIs fail to monitor cluster nodes with 64-bit HTTPS agents. All the policies remain disabled on 64-bit HTTPS-managed cluster nodes.
Workaround: To resolve this limitation, follow these steps:
Problem: If a failover takes place in a cluster environment where 64-bit HTTPS agents are deployed, the service hierarchy and map view of the discovered services display duplicate entries of active and passive cluster nodes.
Workaround: To resolve this limitation, follow these steps:
You must perform these steps before deploying Service Auto-Discovery policies on nodes.
Problem: The checkboxes for installing SPI, SPI Graphs and
SPI Reports are not by default selected when HPOM for Windows, with HP Reporter
or HP Performance Manager, is installed in a clustered
environment.
Workaround: Select the checkboxes manually.
Problem: When uninstalling a SPI, sometimes policies are not
deleted from the Agent Policies grouped by type folder.
Workaround: Delete the policies manually.
Problem: A system can become corrupted if installing SPIs on
an HPOM 8.10 cluster when the cluster node is passive.
Workaround: Make sure the node is active before installing
the SPIs. This can be done through the "Cluster Administration" mmc snap-in. If
the node is not active, and the SPIDVD continues with the installation, the
system might become corrupted.
You can visit the HP Software Support web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP offers.
HP Software online 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 do the following:
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 the following
URL:
http://www.hp.com/managementsoftware/access_level
To
register for an HP Passport ID, go to the following URL:
http://www.managementsoftware.hp.com/passport-registration.html
©Copyright 2008 Hewlett-Packard Development Company, L.P.
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.
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.
For information about third-party license agreements, see the spi-thirdparty-license-agreements\xerces directory on the product installation DVD-ROM.
Adobe® is a trademark of Adobe Systems Incorporated.
HP-UX Release 10.20 and later, and HP-UX Release 11.00 and later (in both 32- and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95-branded products.
Java™ is a U.S. trademark of Sun Microsystems, Inc.
Microsoft® is a U.S. registered trademark of Microsoft Corporation.
Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood City, California.
Oracle Reports™, Oracle7™, and Oracle7 Server™ are trademarks of Oracle Corporation, Redwood City, California.
Windows NT® is a U.S. registered trademark of Microsoft Corporation.
Windows® and MS Windows® are U.S. registered trademarks of Microsoft Corporation.
All other product names are the property of their respective trademark or service mark holders and are hereby acknowledged.