Manually restart the Operations for Windows (OVO-W) agent as follows:
- Change directory to <OV_INSTALL_DIR>\bin.
-
Run the following command:
opcagt -start
This document provides an overview of the changes made to the HP OpenView Self-Healing Services client version 2.60. It contains important information not included in the manuals or in online help.
In
This Version
Installation
Notes
Known
Problems, Limitations, and Workarounds
Verified
Environments
Local
Language Support
Integration
with Other HP OpenView Solutions
Support
Legal
Notices
The Chai virtual machine was replaced by Java.
The OvTomcat container was replaced by Jetty (6.0.1).
Memory utilization has improved.
The naming conventions are changed as follows:
| Earlier versions | Version 2.60 | |
| Managed Node | Managed Client | |
| Deployment Node | Configuration Center | |
| Gateway Node | Communication Gateway |
The Self-Healing Services client, including a full-featured GUI, is available for download.
The packaging mechanism changed from a native installer to the standard HP OpenView installer. Specific details for installation are available in the HP OpenView Self-Healing Services Installation Guide.
The current release, version 2.60.094, is I18N (internationalization) compliant but not L10N (localization) compliant.
The communication protocol between Self-Healing Services clients has changed from SOAP to HTTPS.
The trigger configuration page has been enhanced with improved functionality and better usability features.
Ease of installation - options to configure Self-Healing Services as a Configuration Center, a Communication Gateway, or both after installation.
Multiple modes of execution:
| Connected Mode | The Self-Healing Services client is fully functional in Connected Mode. It has active connections with a Configuration Center and one or more Communication Gateways. | |
| Disconnected Mode | The Self-Healing Services client is not connected to HP through a Communication Gateway. It can detect problems, collect data, and notify you by email. If this client is connected to a Configuration Center, any changes made at the Configuration Center are applied to this client. | |
| Silent Mode | The Self-Healing Services client runs without a Configuration Center or Communication Gateway. It can still detect faults, collect data, and notify you by email about the faults detected. Email server parameters, however, must be configured. |
In Connected mode, when a monitored event is recognized by the Self-Healing Services client, the client configuration is consulted to determine the action that should be taken for that event. If appropriate, a data collector is launched, and the fault data is sent to HP via the ISEE client. Once the data is received at HP, the support contract entitlement handle is validated, and an incident analysis report is created for the fault.
Installation requirements, as well as instructions for installing Self-Healing Services, are documented in the HP OpenView Self-Healing Services Installation Guide provided in Adobe Acrobat (.pdf) format. The document file can be found at:
http://support.openview.hp.com/pdf/selfhealing-installguide.pdf
Before installing Self-Healing Services, make sure that your system meets the following minimum requirements:
Supported Browsers
Microsoft® Internet Explorer 6.0 (or later), or Netscape 7.0 (or later) or must exist on the system from which you will access your Self-Healing Services client. This can be either the HP OpenView management server itself or another machine on your network. While Self-Healing Services is officially supported only on these versions, other browser combinations and versions are likely to produce acceptable results.
ISEE Client
To run in connected mode, Self-Healing Services requires that the HP Instant Support Enterprise Edition (ISEE) client is installed and properly configured on at least one communication gateway system within the Self-Healing Services managed environment. This system may be the HP OpenView management server or a completely different system as long as that system has access to the Internet (either directly or through a proxy).
For Predictive Support Users:
Predictive Support will be disabled by the installation of the entire ISEE
platform depot. Self-Healing Services requires only a subset of the ISEE
platform and does not utilize the features that interfere with predictive
support. To avoid any interference with Predictive Support, you MUST install
the ISEE client using the setup.exe command, as specified in the
HP OpenView Self-Healing Services Installation Guide.
ISEE Support Handle:
The ISEE client requires a system handle to be specified when the client is first configured. If you are an existing ISEE customer, no change is required if you intend to use an existing ISEE client system as your Self-Healing Services communication gateway. Otherwise, you must specify OVSUPPORT as your ISEE system handle.
For HP-UX Installations:
Make sure that all the operating system patches required by the ISEE client are installed. For additional information about patches required for ISEE, see the following web page:
http://www.hp.com/support/isee_support
Select the "A.03.00 and A.03.50 HP-UX Baseline Patches" link. At a minimum, install the patches listed under the Conservative/Restrictive Patch Methodology for the version that you are running. Comprehensive information about HP-UX patches is available at the HP IT Resources Center (ITRC) located at the following URL:
For Solaris Installations:
Ensure that the March 19, 2003 patch cluster has been installed. A user named "nobody" or "install" must be present on the system for a successful installation.
Windows Scripting Host (WSH)
Version 5.6 or greater of the Windows Scripting Host is required for the HP OpenView Self-Healing Services installation. Windows XP and 2003 Server include WSH 5.6 by default, to check the version of WSH on Windows 2000 Professional:
Open Windows Explorer.
Navigate to C:\Windows\System32 (or
%SystemRoot%\system32).
Right-click the cscript.exe file, and click
Properties.
Select the Version tab. The version of WSH is located in the File Version field.
To upgrade the version of Windows Scripting Host to version 5.6 or greater go to the Microsoft Download Center and follow the instructions.
Host Name Resolution
Configuration center, communication gateway node names must be resolvable by both forward and reverse IP lookups. In other words, Self-Healing Services obtains the system's IP address and performs a reverse IP lookup to get the fully qualified hostname.
Windows XP Firewall Configuration
Beginning with Windows XP SP2, the Windows firewall is enabled by default. Configuration centers and communication gateways will not be reachable by Self-Healing Services clients unless the firewall functionality is either configured to allow traffic on TCP port 5814, or the firewall feature is disabled. You can change the firewall configuration as follows:
Open the Control Panel.
Select Network and Internet Connections.
Select Network Connections.
Right-click the Local Area Connection icon, and click Properties.
Select the Advanced tab.
Choose one of the following two options:
Option 1: Clear the Enable Windows Firewall box to disable the Windows firewall.
OR
Option 2: Follow these steps to configure the Windows firewall to allow the Self-Healing Services client to access your network:
Select the Enable Windows Firewall box.
Click the Add button.
In the Name box, type Self-Healing
Services.
In the Address box, type the IP address (or range of IP addresses) that Self-Healing Services will be able to access.
In both the Internal Port and External Port boxes, type the port number for the Self-Healing Services client. By default, this is TCP 5814.
Click OK to close the Windows Firewall dialog box.
Click OK to close the Local Area Connection Properties dialog box.
Firewalls and Proxies
In order to run Self-Healing Services across firewalls, the firewalls must be configured to allow network traffic between the Self-Healing Services clients, configuration center, and communication gateway. The current release of the HP OpenView Self-Healing Services client is not designed to communicate with the configuration center or the communication gateway through Internet/Intranet proxies. The ISEE client, however, has been designed to run in a proxy enabled environment.
HP OpenView Self-Healing Services does not require you to purchase a separate license. However, you must specify a valid support ID (system handle or service agreement identifier(SAID)) for a product monitored by Self-Healing Services. This support ID will be used for entitlement verification during incident submittals.
To start the Self-Healing Services user interface, specify the name of the Self-Healing Services client and port number in the Address box in a browser window. For example, https://myhost:5814/SAM
NOTE: Self-Healing Services utilizes Secure HTTP. You must specify "https" in the address.
The Self-Healing Services client process may take several minutes to initiate, during which time you cannot access the Self-Healing Services user interface. After all the client processes are fully initialized, the UI is available.
Always click the Sign-out link to log out of the Self-Healing Services client user interface before you close the web browser window. If you do not do this, you will have to wait for the existing session to time out before you can log on again. The existing session will time out according to the idle timeout period setting (default is 10 minutes) on the Username and Password page.
Self-Healing configuration center nodes are used to administer and transmit configuration information to communication gateways and other managed clients. Each communication gateway can be assigned to one and only one configuration center.
Use the HP OpenView installer utility to uninstall the Self-Healing Services client. By default, the OpenView installer utility is located here:
Windows: <InstallationDrive>:/Program Files/HP OpenView/Uninstall/HPOvShs/setup.exe
HP-UX or Solaris: /opt/OV/Uninstall/HPOvShs/setup.binITO Agent service stopped for Operations for Windows (OVO-W) 7.5 during the installation of Self-Healing Services.
Manually restart the Operations for Windows (OVO-W) agent as follows:
Run the following command:
opcagt -start
There is a known limitation using Windows 2000 communication gateways. Incidents generating collections with a large number of files may fail to correctly submit to HP (via ISEE). These incidents will appear to submit correctly but will not generate a response from the HP server. This typically affects Network Node Manager 7.51 advanced edition but may also affect other Network Node Manager versions.
Do not use Windows 2000 systems as communication gateways when using Self-Healing Services with Network Node Manager.
There is a known problem if Self-Healing Services is actively processing incidents and is stopped during incident processing. When Self-Healing is restarted, incidents that were being processed are no longer visible in the user interface.
Data collection will fail for any incident that is being processed and is, therefore, in the Received state when Self-Healing Services is stopped. This is a nonrecoverable error, and Self-Healing Services will not be able to retrieve or reprocess this incident.
Un-installation of Operations for UNIX (OVO) may stop Self-Healing Services.
Manually restart Self-Healing Services after uninstalling Operations for UNIX (OVO)
Un-installation of Operations for Windows (OVO-W) may corrupt Self-Healing Services. This problem typically occurs when OVO-W is the only OpenView software, apart from Self-Healing Services, on the Windows system. Errors may occur in Self-Healing Services after OVO-W is uninstalled. This behavior is confirmed in OVO-W 7.5 but may affect other versions. It affects all versions of Windows.
Self-Healing Services should be immediately shut down and un-installed. It will need to be re-installed to continue use.
Self-Healing Services does not correctly detect Network Node Manager consolidated patches installed on Solaris operating systems. The incident analysis report may recommend a Network Node Manager patch even though the patch is already installed as part of a consolidated patch.
Manually place the patch text document for the Network Node Manager consolidated patches into the directory /opt/OV/ReleaseNotes/patches. Self-Healing Services will report that the patch is installed.
Currently, for products with an agent/server architecture, Self-Healing Services patch analysis recommendations are not filtered by the type of product installation reporting the incident. For instance, if an incident is generated by an operations for Unix agent, then Self-Healing Services patch analysis will provide patch recommendations for both agent and server installations. The same applies if the incident was generated for an operations for Unix server.
Please check the patch description under the Self-Healing Services recommended patches table to determine if the patch applies to an agent or server. In addition, please refer to the patch document's install instructions and special install instructions to determine patch applicability.
For Operations for Windows, data collected by OvSuptInfo.exe during a FAULT incident is not sent to HP.
If a support case is opened for Operations for Windows, manually submit the files located in the %TEMP%/OvSuptInfoOut directory to your support engineer.
Installation of Network Node Manager on Solaris displays an error installing Perl 5.6 message.
Install Network Node Manager before installing Self-Healing Services.
After restarting the machine Self-Healing Services is not running until a user logs in for first time .
A user must login to the system at least one time before Self-Healing Services will be running. After a user logs into the machine they are able to log out and Self-Healing Services will continue running.
A manual submission might report that a product is uninstalled while upgrading or downgrading an OpenView product.
The following platforms have been tested:
Windows 2000 SP-4, Windows XP Professional, Windows 2003 Server
HPUX: HPUX 11.11, HPUX 11.23 PA, and Itanium
Solaris: Solaris 7, Solaris 8, Solaris 9 and Solaris 10
This version of Self-Healing Services does not support local languages, though it is localization-ready.
The Self Healing Services client can send fault notifications to the HP OpenView Operations (OVO) message browser, the HP OpenView Network Node Manager (NNM) incident browser, or both, as specified by the user in the settings.
Please visit the HP OpenView support web site at:
http://www.hp.com/managementsoftware/support
This web site provides contact information and details about the products, services, and support that HP OpenView offers.
HP OpenView 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:
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 2003-2006 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.
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® and Windows® are U.S. registered trademarks of Microsoft
Corporation.
UNIX® is a registered trademark of the Open Group.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).