HP OpenView Service Navigator Value Pack

This document contains the HP OpenView Service Navigator Value Pack Release Notes. It includes last-minute information that could not be included in the documentation and describes known problems and limitations.

In This Version

Welcome to the HP OpenView Service Navigator Value Pack 9.0 software! The Service Navigator Value Pack enhances HP OpenView Operations for UNIX by providing Service Configuration, a graphical user interface for Service Navigator, designed for maximum efficiency and ease-of-use. This version includes the following new features and enhancements:

Web Console integration type (Service Desk integration only) This new Web Console integration type lets you launch Service Desk
Web Console from within Service Navigator.
Single step installation The Service Configuration installation procedure is now simplified by introducing a single step installation using HP OpenView Installer.
Command line tools Two new command line tools are introduced: cadm_DumpConfiguration (for SNVP 8.0 only) and cadm_LoadConfiguration. The following command line tools changed their names: cadmactivate to OvSnvpActivate, cadmexport to OvSnvpExport, cadmstart to OvSnvpStart, and cadmunlock to OvSnvpUnlock.
Upgrading procedure New procedure for upgrading Service Configuration from version 8.0 to 9.0 is available.
Inventory for the OVO/UNIX management server When selecting an OVO/UNIX management server, service hierarchies that were last deployed to that management server are now selected by default.
Copy and paste within the service hierarchy Now you can copy objects (parent objects as well as child
objects) within the same service hierarchy in tree and map views. The copied object is pasted under another object as a child.
Zooming a map view of services You can now instantly magnify or reduce your map view of services using the 'zoom' drop-down list from the toolbar.
User profile to store user relevant data A new user profile CADMUserProfile.conf is introduced. This file contains settings specified in the Service Configuration console. Login dialog options are stored in the OvObsClient.conf file.
URL support for service icons and backgrounds In addition to the file names for graphic files for icons and backgrounds, Service Configuration now supports also URLs to graphics.
New paths for icons and backgrounds and the installation directory All Service Configuration graphic files changed their location on the Service Configuration client system. Also, a new default installation directory is introduced.
Support for some command line tools on OVO/UNIX management server and the SNVP application server Some command line tools are now supported on the OVO/UNIX management server and the SNVP application server as well. These tools are cadm_ApplyHierarchyRules.bat, cadm_chpwd.bat, cadm_Deploy.bat, cadm_DumpHierarchy.bat and cadm_LoadHierarchy.bat.
New logging and tracing This version of the Service Configuration software brings new logging and tracing.
Service Desk 5.0 integration support This version of the software is built for use with Service Desk version 5, patch level SD SP1.
HP Serviceguard cluster SNVP 9.0 now supports HP Serviceguard cluster environment. Installation and configuration details are described in the SNVP Installation Guide version 9.0 October 2006.
HP-UX Itanium support This version of the software supports installation on HP-UX 11.23 OS on the Itanium hardware.
The following conditions apply:
- Installation package for HP-UX Itanium is not available on CD-ROM and is only available for download from: http://support.openview.hp.com/patches/snvp/snvp.jsp
- The installation of SNVP on HP-UX Itanium follows the same process as for HP-UX on PA-RISC which is described in the SNVP 9 installation guide.
Service Desk 5.1
- SD 5.1 is supported with SNVP 09.00.160
- SD 5.1 should be installed before SNVP 9.0
- Installation packages are not available on CD-ROM and are only available for download from: http://support.openview.hp.com/patches/snvp/snvp.jsp
Microsoft SQL 2000 DB Server
- Microsoft SQL 2000 DB Server is supported with SNVP 09.00.160
- Installation packages are not available on CD-ROM and are only available for download from: http://support.openview.hp.com/patches/snvp/snvp.jsp

Not Supported With This Version

This version of the Service Navigator Value Pack software has the following limitations:

Non-English languages The software is only available in the English language. Localized versions, for example for the Japanese language, are planned for future releases.
Supported platforms The software is exclusively supported on the platforms listed in the Supported Platforms document, which is accessible through the following URLs: http://partners.openview.hp.com/ovcw/pricing/config_matrix.jsp and http://support.openview.hp.com/sc/support_matrices.jsp. To access these URLs you need an HP Passport.
Two service reports The software causes two service reports to display incorrect data. The reports Message Trend by Service and Top Active Messages by Service are available with HP OpenView Reporter and should not be used in conjunction with the Service Navigator Value Pack software.
Sun Cluster Installation of the Service Navigator Value Pack software in Sun Cluster environments is not supported. The supported high-availability solutions are VERITAS Cluster and HP Serviceguard. The only component of the Service Navigator Value Pack software that can be installed in a cluster environment is the connector (running on the OVO/UNIX management server).
OVO/UNIX and SNVP application server coexistence A Service Navigator Value Pack application server and OVO/UNIX management server installation on the same system is not supported.
User profile The user_settings.xml file is no longer used for storing the user relevant data.

Installation Notes

To install the Service Navigator Value Pack software:

Installation overview Before you start the installation, thoroughly read chapter 1 of the Service Navigator Value Pack Installation Guide. To ensure a smooth and successful installation, it is essential that you are familiar with the components and architecture of the Service Navigator Value Pack software and that you understand where and how the installation packages must be installed.
Hardware and software requirements Make sure the systems where you plan to install the Service Navigator Value Pack software meet the hardware and software requirements listed in the Supported Platforms document.
The latest version of the Supported Platforms document is accessible through the following URLs: http://partners.openview.hp.com/ovcw/pricing/config_matrix.jsp and http://support.openview.hp.com/sc/support_matrices.jsp. To access these URLs you need an HP Passport.
Installation Install and configure the Service Navigator Value Pack software as described in the Service Navigator Value Pack Installation Guide.
Licensing The HP OpenView Operations for UNIX management server license to use (LTU) entitles you to use the Service Navigator Value Pack. An additional LTU is not required.
Installation log files If you installed the management server, check the log file snvp_HPOvInstaller.txt.
The component log files are located in %OVDATADIR%, in the HPOvInstaller directory. The paths and file names are as follows:

Windows
1. %TEMP%\HPOvInstaller\snvp_<build_number>, where <build_number> is the version and build number, such as 09.00.152.
2. package_msi_<component>_install.log, where <component> is the name of the component.
UNIX
1. /var/tmp/HPOvInstaller/snvp_<build_number>, where <build_number> is the version and build number, such as 09.00.152.
2. package_depot_<component>_install.log, where <component> is the name of the component.
These log files contain information about the native installation of the component.

On a Windows platform, search the log file for Return Value 3, which usually indicates there was an error.
On HP-UX, check the swagent.log file located in /var/adm/sw/swagent.log.

Check the Object Server log file for the reason for the installation failure.
The Object Server log file is located in the following directory:

%OVDATADIR%/log/system0.0_enUS

This file contains the information from Object Server and its tools. Look at the bottom of the file for any exceptions or other error messages that may explain the failure.

Troubleshooting

Known General Problems

Problem:	Problem when the software CD-ROM is mounted on HP-UX
Symptom:	There are wrong filenames and file access permissions when software CD-ROM is mounted on HP-UX.
Solution:	Perform the following procedure: Make sure the directory which contains the PFS utilities (/usr/sbin) is in your PATH. Edit (or create) the /etc/pfs_fstab file to contain a line similar to the following: <device> <mount_dir> pfs-rrip xlat=rrip 0 0 Where: <device> is the path to your CD-ROM reader (for example, /dev/dsk/c1t2d0) <mount_dir> is the path to an existing directory where the CD-ROM will be mounted (for example, /rr_cdrom) Use the following commands to mount the CD-ROM on an HP-UX system: nohup pfs_mountd & nohup pfsd 4 & pfs_mount <device> \| <mount_dir>

Known Usability Related Problems

Problem:	After installation on UNIX systems, server does not start
Symptom:	Because of an inadequate OVControl process timeout, the server on UNIX systems does not start automatically. The startup should be performed manually with ovc -start after the installation process is completed.
Solution:	Enter the following commands: ovc -stop ovc -start

Problem:

After installation on UNIX systems, server does not start

Symptom:

Because of an inadequate OVControl process timeout, the server on UNIX systems does not start automatically. The startup should be performed manually with ovc -start after the installation process is completed.

Solution:

Enter the following commands:

ovc -stop
ovc -start

Problem:	QXCR1000370735: Automatic deployment from SNVP UI fails
Symptom:	On Solaris 10 platforms automatic deployment from SNVP GUI is not working. The ‘Connection refused’ error message is displayed.
Solution:	After successful installation and activation of SEAdapter on Solaris 10 platform perform the following steps: Enter the following command: svcs \| grep cadm If there is no output, enter the following command: inetconv –i /etc/inet/inetd.conf If the output states that SEAdapter is in a maintenance mode, enter the following command: svcadm clear /network/cadmsnd/tcp

Problem:

QXCR1000370735: Automatic deployment from SNVP UI fails

Symptom:

On Solaris 10 platforms automatic deployment from SNVP GUI is not working. The ‘Connection refused’ error message is displayed.

Solution:

After successful installation and activation of SEAdapter on Solaris 10 platform perform the following steps:

Enter the following command: svcs | grep cadm
If there is no output, enter the following command: inetconv –i /etc/inet/inetd.conf
If the output states that SEAdapter is in a maintenance mode, enter the following command:
svcadm clear /network/cadmsnd/tcp

Problem:

Problem starting server on slow UNIX systems

Symptom:

On slow UNIX systems, the ovobs server startup sometimes fails.
The following is an example of the status after an unsuccessful startup:

Ovcd	OV	Control	CORE	(2434)	Running
ovbbccb	OV	Communication Broker	CORE	(2435)	Running
ovloginsv	OV	Login Server	JAVA		Stopped
ovobs	OV	Object Server	OBS		Aborted

This problem is linked to the value of the timeout of the OV Control process, which is too small for the slow UNIX systems.

Solution:

Enter the following commands:

ovc -kill
ovconfchg -ns ctrl.ovcd -set ACTION_TIMEOUT 120
ovc -start

Problem:	QXCR1000304079 (OV Control)
Symptom:	ovapacheA and ovobs processes abort after a reboot.
Solution:	After rebooting your system, restart the processes manually. Enter the following: ovc -start

Known Problems with the Installation

NOTE:

If the installation fails for some reason, it is recommended to check the installation log files. For more information about the log files, see the section Installation Notes of this document.

Problem:	QXCR1000359530: Upgrade installation of SDSP1 fails
Symptom:	Installation of SD5.0 SP1 on HP-UX platforms fails if it is installed over SNVP 9.0.
Solution:	SD5.0 SP1 should be installed before SNVP 9.0.

Known Problems with the Console

Problem:	QXCR1000233802
Symptom:	In Windows XP Professional with SP2, after switching theme from Windows XP to Windows classic view, buttons in dialogs and toolbar are not properly displayed (frames are missing).
Solution:	Restart the SNVP GUI.

Problem:	QXCR1000288555
Symptom:	When copying a service from one hierarchy to another, there is a problem with refreshing the presentation icon if the service appears on multiple locations in destination hierarchy and has a different presentation icon from the copied one.
Solution:	Collapse and expand the parents of the service for which the presentation icons have not been refreshed.

Problem:	QXCR1000293899
Symptom:	When adding new children to the map area that is smaller than screen size, the scrollbars are not instantiated, but they should be.
Solution:	Collapse and expand the parent service.

Problem:	QXCR1000319263
Symptom:	When conflicting Parent-and-Child rules are defined, for example rules which would result in cycles in service dependencies, an incorrect error message (AttributeInfo[0]is null) is sometimes displayed during the Apply hierarchy rules operation.
Solution:	Review and correct the assigned Child- and Parent-and-child object rules in order to make it possible to apply them successfully.

Problem:	QXCR1000322581
Symptom:	When a new icon is assigned to an object, the image is not refreshed in the tree view but only in the graph. This mostly happens to the icons with .16.gif and .24.gif file extensions. Only icons with *.32.gif file extension are used correctly with no exceptions.
Solution:	Use only 32x32 pixel size icons with SNVP. Other sizes are not supported and may result also in incorrect display in Service Navigator.

Known Problems with the Service Desk Integration

Problem:	Object Server Cache
Symptom:	The Object Server cache can cause problems.
Solution:	If you encounter a problem when you start the Object Server using ovc -start, try to delete the Object Server cache files by deleting all of the files in the following directory: Windows: C:\Program Files\HP OpenView\data\datafiles\obs UNIX: /var/opt/OV/datafiles/obs

Different Output Format of opcsvcterm

The format of results returned by the opcsvcterm interface is different with Service Navigator Value Pack SE Adapter installed and activated. There are two major differences:

Element content opcsvcterm does not immediately return a line feed after an end-tag. Instead, it waits until the service engine returns the complete content part of an element before displaying the content with the line feed. Without Service Navigator Value Pack SE Adapter installed and activated, opcsvcterm returns line feeds immediately.
Empty elements opcsvcterm returns a start-tag immediately followed by an end-tag to represent an empty element. Without Service Navigator Value Pack SE Adapter installed and activated, opcsvcterm returns empty-element tags.

The following table gives example output for opcsvcterm without and with Service Navigator Value Pack SE Adapter installed:

Service Navigator	<Results>'\n'	[space][space]<OK/>'\n'				</Results>'\n'
Service Navigator Value Pack SE Adapter	<Results>	'\n'[space][space]	<OK>	</OK>	'\n'	</Results>	'\n'

NOTE:

Hewlett-Packard reserves the right to change the output and the output format of Service Navigator interfaces with product releases. Check the Service Navigator DTDs for changes to the XML definitions. The DTDs can be found on the OVO/UNIX management server in the /etc/opt/OV/share/conf/OpC/mgmt_sv/dtds directory. In general, it is recommended to use an XML parser to interpret the service engine output rather than your own pattern-matching algorithms.

IMPORTANT: In the SNVP Reference Guide, section "Deleting the Content of the Service Engine" on page 89, the following is stated:

"If you want to delete all Service Configuration content in the service engine, type the following on the OVO management server:

echo "\

<Operations>\
<Remove>\
<All/>\
</Remove>\
</Operations>" | /opt/OV/bin/OpC/cadmsnd

The system should reply as follows to indicate successful completion of the command:

<?xml version='1.0' ?>
<Results>
<OK/>
</Results>

See also “Preventing Problems” on page 86."

The text marked with red is not correct. Consider the following instead:

echo "\
<Operations>\
<Remove>\
<ServiceRefs>
<ServiceRef>69970093-C777-494C-BE61-\
E9CDBFF99582</ServiceRef>\
</ServiceRefs>\
</Remove>\
</Operations>" | /opt/OV/bin/OpC/cadmsnd
The SNVP Installation Guide version 9.0 October 2006 is updated with the installation and configuration details for HP Serviceguard cluster environment, which is now supported with SNVP 9.0.