HP OpenView Smart Plug-in for UNIX Operating Systems

Release Notes

April 2005

This document provides an overview of the changes made to HP OpenView Smart Plug-in for UNIX Operating Systems (OSSPI) software version B.03.15. It contains important information not included in the manuals or in online help.

In This Version
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Verified Environments
Integration with Other OpenView Solutions
Support
Legal Notices

In This Version

This release of the OSSPI supports only HP OpenView Operations for Windows (OVO) version 7.5. Earlier versions of OVO are not supported.

• OSSPI on a clustered OVO Management Server

  OVO 7.5 can be configured to run on a Windows cluster server as a high-availability resource group. Being a high-availability resource group allows OVO to be switched from one system to another by the cluster software. This release of OSSPI supports failover of the OVO Management Server.

• Discovery and monitoring of Sun cluster objects

  The OSSPI discovers and monitors cluster nodes, shared devices, resource groups, quorum devices, NAFO groups, and interconnects, that make up the cluster.

• Enhanced file system monitoring

  With this enhancement, the OSSPI discovers and monitors dynamically mounted file systems.

• Changes to the directory structure

  For the new locations of configuration files, refer to the OSSPI online help.

• Message key correlation

  Message key correlation has been used to reduce duplicate messages appearing on the message browser.

• Regrouping of OSSPI policies

  The Auto-Discovery policy group has been restructured. Also, the high-level policy group for each operating system now contains the Advanced and QuickStart policy groups. The Advanced group has policies to monitor specific applications that may be present on a managed node. The QuickStart group contains basic policies required to monitor a managed node.

• Single instrumentation directory
  With this release of the OSSPI, all the instrumentation files are present in the SPI for Unix OS instrumentation directory. This includes the additional instrumentation files that were present in the SPI for Unix OS Discovery instrumentation directory in earlier versions of the OSSPI.
• Self-Healing Services support
  This release of the OSSPI supports data collection using the Self-Healing Services client in the event of a problem on the managed node. The Self-Healing Info tool has been added in this release to support collection of diagnostic data on specified nodes.
• New Policies
  • OSSPI-MCSG_Syslog
  • OSSPI-VCS-Hashadow
  • OSSPI-VCS-had
  • OSSPI-cpuutil
  • OSSPI-diskutil
  • OSSPI-procutil
  • OSSPI-sc-gdmsg
  • OSSPI-sc-nafomsg
  • OSSPI-sc-rgmsg
  • OSSPI-sc-transportmsg
  • OSSPI-scmon
  • OSSPI-scmsg
  • OSSPI-scproc
  • OSSPI-sdsmon
  • OSSPI-vmsa-server
  • OSSPI-vxconfigd

  Changed policies
  The policy groups listed in the drop-down list contain the policies that were changed for this release. Select a policy group for additional information about the policies that were changed in that group:

  Select a policy group Monitor file policies Log file policies OpCmsg policies

  Monitor file policies

  Policy	Change
  OSSPI-CD_Mem_Load	Metric name is modified from GBL_MEM_PAGEOUT_RATE to GBL_MEM_UTIL
  OSSPI-defect_long	Polling interval is changed to 28d. The automatic message correlation feature is added to this policy.
  OSSPI-defect_short	The automatic message correlation feature is added to this policy.
  OSSPI-GP_Filesystem	Default Service ID is changed from OSSPI:fs:<OBJ>@@<$MSG_NODE_ID> to OSSPI:fs@@<$MSG_NODE_ID>
  OSSPI-GP_Msg_Tbl	The text in the following conditions were changed as follows: OSSPI-GP_Msg_Tbl.1 MESSAGE QUEUE TABLE utilization, reached limit of $$%. to MESSAGE QUEUE TABLE utilization, $$%. OSSPI-GP_Msg_Tbl.2 MESSAGE QUEUE TABLE utilization, reached limit of $$%. to MESSAGE QUEUE TABLE utilization, $$%. OSSPI-GP_Msg_Tbl.3 MESSAGE QUEUE TABLE utilization, reached critical limit of $$%. to MESSAGE QUEUE TABLE utilization, $$%. OSSPI-GP_Msg_Tbl.4 MESSAGE QUEUE TABLE utilization, situation back to normal. to MESSAGE QUEUE TABLE utilization, situation normal.
  OSSPI-GP_Nfs_Client_Badcall	The text in the following conditions were changed as follows: OSSPI-GP_Nfs_Client_Badcall.1 NFS client RPC error, problem situation (Probability: $$%). to NFS client RPC error, (Probability: $$%). OSSPI-GP_Nfs_Client_Badcall.2 NFS client RPC error, problem situation (Probability: $$%). to NFS client RPC error, (Probability: $$%). OSSPI-GP_Nfs_Client_Badcall.3 NFS client RPC error, problem situation (Probability: $$%). to NFS client RPC error, (Probability: $$%). OSSPI-GP_Nfs_Client_Badcall.4 NFS client RPC error, situation back to normal. to NFS client RPC error, situation normal.
  OSSPI-GP_Nfs_Server_Badcall	The text in the following conditions were changed as follows: OSSPI-GP_Nfs_Server_Badcall.1 NFS server RPC error, problem situation (Probability: $$%). to NFS server RPC error, (Probability: $$%). OSSPI-GP_Nfs_Server_Badcall.2 NFS server RPC error, problem situation (Probability: $$%). to NFS server RPC error, (Probability: $$%). OSSPI-GP_Nfs_Server_Badcall.3 NFS server RPC error, problem situation (Probability: $$%). to NFS server RPC error, (Probability: $$%). OSSPI-GP_Nfs_Server_Badcall.4 NFS server RPC error, situation back to normal. to NFS server RPC error, situation normal.
  OSSPI-GP_Proc_Tbl	Default service id has been changed from OSSPI:os:kernel:tables:procs@@<$MSG_NODE_ID> to OSSPI:os:kernel:tables@@<$MSG_NODE_ID> The text in the following conditions were changed as follows: OSSPI-GP_Proc_Tbl.1 PROCESS TABLE utilization, reached limit of $$%. to PROCESS TABLE utilization, $$%. OSSPI-GP_Proc_Tbl.2 PROCESS TABLE utilization, reached limit of $$%. to PROCESS TABLE utilization, $$%. OSSPI-GP_Proc_Tbl.3 PROCESS TABLE utilization, reached critical limit of $$%. to PROCESS TABLE utilization, $$%. OSSPI-GP_Proc_Tbl.4 PROCESS TABLE utilization, situation back to normal. to PROCESS TABLE utilization, situation normal.
  OSSPI-GP_Sema_Tbl	The text in the following conditions were changed as follows: OSSPI-GP_Sema_Tbl.1 SEMAPHORE TABLE utilization, reached limit of $$%. to SEMAPHORE TABLE utilization, $$%. OSSPI-GP_Sema_Tbl.2 SEMAPHORE TABLE utilization, reached limit of $$%. to SEMAPHORE TABLE utilization, $$%. OSSPI-GP_Sema_Tbl.3 SEMAPHORE TABLE utilization, reached critical limit of $$%. to SEMAPHORE TABLE utilization, $$%. OSSPI-GP_Sema_Tbl.4 SEMAPHORE TABLE utilization, situation back to normal. to SEMAPHORE TABLE utilization, situation normal.
  OSSPI-GP_Shmem_Tbl	The text in the following conditions were changed as follows: OSSPI-GP_Shmem_Tbl.1 SHARED MEMORY TABLE utilization, reached limit of $$%. to SHARED MEMORY TABLE utilization, $$%. OSSPI-GP_Shmem_Tbl.2 SHARED MEMORY TABLE utilization, reached limit of $$%. to SHARED MEMORY TABLE utilization, $$%. OSSPI-GP_Shmem_Tbl.3 SHARED MEMORY TABLE utilization, reached critical limit of $$%. to SHARED MEMORY TABLE utilization, $$%. OSSPI-GP_Shmem_Tbl.4 SHARED MEMORY TABLE utilization, situation back to normal. to SHARED MEMORY TABLE utilization, situation normal.
  OSSPI-GP_Swap_Res	The text in the condition OSSPI-GP_Swap_Res.3 is changed from SWAP reservation, reached critical limit of $$%. to SWAP reservation, reached limit of $$%.
  OSSPI-kmon	Service ID for all conditions is changed to OSSPI:kernel@@<$MSG_NODE_ID>
  OSSPI-mailperm	The default application setting is changed from Sendmail to HP OSSPI. The automatic message correlation feature is added to this policy.
  OSSPI-mailqueue	The default application setting is changed from Sendmail to HP OSSPI. The automatic message correlation feature is added to this policy.
  OSSPI-mount	The polling interval is changed from 1 hour to 20 minutes. The automatic message correlation feature is added to this policy.
  OSSPI-MWA_Filesystem	The default Service ID has been changed from OSSPI:fs:<OBJ>@@<$MSG_NODE_ID> to OSSPI:fs@@<$MSG_NODE_ID>
  OSSPI-NetInterfaces	The action under the Network Interface down [OSSPI-NetInterfaces.2]condition is changed from automatic action to operator-initiated action. This change is as follows: AUTOACTION ifconfig <$MSG_OBJECT> inet up ANNOTATE to OPACTION ifconfig <$MSG_OBJECT> inet up ANNOTATE ACK The automatic message correlation feature is added to this policy.
  OSSPI-NP-Filesystem	The monitor program call is changed from osspi_fsmon.pl OSSPI-NP-Filesystem_2 to osspi_perl.sh osspi_fsmon.pl -m OSSPI-NP-Filesystem The polling interval is changed from 10 minutes to 30 minutes. The automatic message correlation feature is added to this policy.
  OSSPI-printenable	The monitor policy type is changed from MINTHRESHOLD to MAXTHRESHOLD The default application setting is changed from lp to HP OSSPI
  OSSPI-veritas	The polling interval is changed from 1hour to 10 minutes. In the Check for Failed Disk which is not discovered in hardisk.cfg condition, the Service ID is changed from OSSPI:veritas:<dg>@@<$MSG_NODE_ID> to OSSPI:<dg>:<dm>@@<$MSG_NODE_ID> In the Check for Bad Sub Disks condition, the object pattern is changed from Badsd:<*.dg>:<*.sd>:<*.volume> to Badsd:<*.dg>:<*.sd> In the Check for Bad Plexs condition, the Service ID is changed from OSSPI:veritas:<dg>:<volume>@@<$MSG_NODE_ID> to OSSPI:<dg>:<plex>@@<$MSG_NODE_ID> In the Monitor if plex is on volatile disk condition, the Service ID is changed from OSSPI:veritas:<dg>:<volume>@@<$MSG_NODE_ID> to OSSPI:<dg>:<volume>@@<$MSG_NODE_ID>
  OSSPI-vg	Swapped the order of PE very low [OSSPI-vg.1] and PE low [OSSPI-vg.2] conditions.

  Log file policies

  NOTE: All the log file policies are updated to include the Send message if log file does not exist condition. The following table lists the additional changes specific to each log file policy.

  Policy	Change
  OSSPI-AIX-AuditLog	The default service name (OSSPI:os:svc@@<$MSG_NODE_ID>) is added to this policy.
  OSSPI-AIX-KernelLogs	The polling interval is changed from 61 seconds to 1 minute and 1 second. The default service name (OSSPI:os:kernel@@<$MSG_NODE_ID>) is added to this policy.
  OSSPI-AIX-Logins	The default service name (OSSPI:os:users@@<$MSG_NODE_ID>) is added to this policy.
  OSSPI-HPUX-Boot	The default service name (OSSPI:os:svc@@<$MSG_NODE_ID>) is added to this policy.
  OSSPI-Linux-Boot	The default service name (OSSPI:os:svc@@<$MSG_NODE_ID>) is added to this policy.
  OSSPI-SOL-syslog	The default service name (OSSPI:os:svc:syslog@@<$MSG_NODE_ID>) is added to this policy.
  OSSPI-Tru64-cronlog	The default service name (OSSPI:os:svc:cron@@<$MSG_NODE_ID>) is added to this policy.
  OSSPI-Veritas_log	The default service name (OSSPI:veritas@@<$MSG_NODE_NAME>) is added to this policy.
  OSSPI-dnsstat	The default service name (OSSPI:os:svc:dns@@<$MSG_NODE_ID>) is added to this policy. The suppression time interval is changed to 24 hours.

  OpCmsg policies

  Policy	Change
  OSSPI-alarmwriteMsg	The default message group for all conditions is changed to OSSPI-Internal The operator action in Glance processes not running [OSSPI-alarmwriteMsg.9] condition is changed from OPACTION export UNIX95=1; ps -eo pid,args | awk '$1 == <pid> {print;} ANNOTATE to OPACTION . osspi_platdef; ${PS} -eo pid,args ANNOTATE
  OSSPI-opcmsg	The default suppression interval for duplicate messages is changed to 6 hours. The text in the process pid not running [OSSPI-procmonMsg.2] condition has been changed from \\[<*.section>\\]: No such PID <*.pid> to Invalid pid <pid> in service <section>. Process with pid <pid> does not exist. The Trace level change alert [OSSPI-opcmsg.25] condition is added to this policy.
  OSSPI-procmonMsg	The instruction text for the following conditions are modified: procmon more than [OSSPI-procmonMsg_4.6] procmon less than [OSSPI-procmonMsg.6]

  NOTE: The numeric suffixes of all OSSPI policies have been removed. For example, the OSSPI-AIX_HACMP_1 policy is now OSSPI-AIX_HACMP.
• Obsolete policies
  • OSSPI-Discovery_1
  • OSSPI-Linux-printlog_1
  • OSSPI-Linux-snmplog_1
  • OSSPI-ServiceDeletion_1
  • OSSPI-Veritaslog_1
  • OSSPI-AIX-KernelLogs_2
  • OSSPI-alarmwriteMsg_1
  • OSSPI-AutoDeploy_Glance_1
  • OSSPI-AutoDeploy_Coda_1
  • OSSPI-AutoDeploy_NoPerf_1
  • OSSPI-AutoDeploy_MeasureWare_1
  • OSSPI-AutoDiscovery_2
  • OSSPI-CD_AIX_Disk_2
  • OSSPI-CD_HPUX_Disk_2
  • OSSPI-CD_SOL_Disk_2
  • OSSPI-FilesystemMsg_3
  • OSSPI-FilesystemMsg_2
  • OSSPI-xterm_1
  • OSSPI-HPUX-Dmesg_1
  • OSSPI-MWA_Filesystem_1
  • OSSPI-NFSClientProc_1
  • OSSPI-NFSClientProc_2
  • OSSPI-NFSServerProc_1
  • OSSPI-NFSServerProc_2
  • OSSPI-opcmsg_2
  • OSSPI-procmonMsg_2
  • OSSPI-procmonMsg_3
  • OSSPI-SOL-Dmesg_1
  • OSSPI-SOL-syslog_1
  • OSSPI-veritasmon_1
  • OSSPI-veritaslog_1
  • OSSPI-veritasproc_1
  • OSSPI-ntpproc_i
  • OSSPI-printproc_1
  • OSSPI-snmpproc_1
  • OSSPI-syslogproc_1
  • OSSPI-vg_1
  • OSSPI_sdsmon_1
  • OSSPI_veritasproc_1
  • OSSPI-cronproc_1
  • OSSPI-dnsproc_1
  • OSSPI-inetdproc_1
  • OSSPI-mailproc_1
  • OSSPI-FSMonConfigfile_1
  • OSSPI-AIX-BadLogs_1
  • OSSPI-Linux-BadLogins_1
  • OSSPI-NP-Filesystem_1
• Renamed Cluster Management Group policies

  The following table lists the policies (in the Cluster Management policy group for OVO) that were renamed in this version of the OSSPI.

  Policy Name in OVO	New Policy Name in OSSPI
  Engine Log (VCS)	OSSPI-VCS-EngineLog
  Engine Notify Log (VCS)	OSSPI-VCS-EngineNotifyLog
  Engine Log (SC)	OSSPI-SC-EngineLog
  Syslog (ServiceGuard)	OSSPI-MCSG-Syslog

   

  NOTE: The policies listed in the table can be used after updating them to version 7.0.

  All policies that ship with this release of the OSSPI have the version number 4.0, except for the following policies:

  • OSSPI-VCS-EngineLog
  • OSSPI-VCS-EngineNotifyLog
  • OSSPI-SC-EngineLog
  • OSSPI-MCSG-Syslog

• Installation Notes

  Installation requirements, as well as instructions for installing the OSSPI are documented in the following guides provided in Adobe Acrobat (.pdf) format:

• HP OpenView Operations for Windows Installation Guide
• HP OpenView Operations for Windows Upgrade Guide
• Smart Plug-ins CD for OpenView Operations Installation/Upgrade Guide

NOTE: The OSSPI-AutoDeploy policy is automatically deployed to the Management Server by default after the installation of the OSSPI. You can set the registry value of
HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\AutoDeployment\Disable to 1 to disable this autodeployment. This configuration ignores any other autodeployment settings specified.

• The OSSPI versions supported for upgrade or migration are as follows:

  • B.01.53
  • B.02.01
  • B.02.53

  If you are upgrading the OSSPI from version B.01.53, the OSSPI must be uninstalled manually before installing this version of the OSSPI.

  Policies affected during Side-by-Side Migration or In-place Upgrade

  During a side-by-side migration or an in-place upgrade:

  • The policies listed in the obsolete policies section are removed from the managed nodes
    If a managed node is not accessible from the Management Server during an upgrade or migration, you can remove the obsolete policies from the managed node after the managed node becomes accessible. This stops reception of messages from obsolete policies.
  • The policy assignments in the Management Server are updated

Services updated after Side-by-Side Migration or In-place Upgrade

The service instances discovered by the OSSPI are removed from the Management Server during a side-by-side migration or an in-place upgrade. After the service discovery process is run on the UNIX and Linux managed nodes, the new service instances are created automatically based on the new OSSPI service model.

If autodeployment is disabled on the Management Server, you must deploy the following on existing UNIX and Linux managed nodes after the migration or upgrade is complete. This updates the service model of the managed nodes:

• SPI for Unix OS instrumentation
• SPI for Unix OS > Auto-Discovery > OS SPI Discovery policy group

To enable or disable autodeployment, set the following registry value to 0 or 1 respectively.
HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\AutoDeployment\Disable

Enhancements and Fixes

The following items (identified by error tracking number) are fixed in the current software release.
• QXCR1000113535: ER for discovery of auto mounted file systems by OSSPI
• QXCR1000113730: Default threshold of policy"OSSPI-CD_mem_load_2" is wrong
• QXCR1000114084: OS SPI Support for RHEL 2.1 and 3.0
• QXCR1000194918: Unix OSSPI Service discovery fails with SNVP on OVO 7
• QXCR1000199441: osspi_procmon.pl - pb with algorithm of process monitoring (for QXCM1000198798)
• QXCR1000215050: OSSPI-NP-Filesystem_1 not sending Normal message when monitored file systems ret
• QXCR1000215092: OSSPI should not add vxiod entry in procmon.cfg file during discovery
• QXCR1000219203: osspi_procmon.pl sends proc down messages for HA processes running in package
• QXCR1000110202: Include the -M option in swap_mon.sh monitor for IT/O
• QXCR1000111163: LOGFILE "Logins (Solaris)" should display day/time for "System Reboot"
• QXCR1000112689: ENH: Alarms not being generated for MC/SG shared file systems
• QXCR1000112822: OSSPI_Linux_NetInterfaces_1 template auto action should be modified
• QXCR1000113134: Request for support of veritas clustered file systems
• QXCR1000113409: Error in parse_softpartition function of osspi_sds_common script
• QXCR1000113774: osspi_quotamon.sh script can cause problems with large sizes
• QXCR1000114025: Support request for Redhat AS 2.1 and 3
• QXCR1000114052: Unexpected exception executing printer discovery on solaris nodes
• QXCR1000190489: OSSPI 02.50 binaries that fail on HP-UX 10.20/PA 1.1 arch
• QXCR1000192584: Unix OSSPI service discovery does not generate correct icon
• QXCR1000193421: [Reboot] and [Shutdown] tools do not return result in the mgmt console
• QXCR1000193810: RedHat: Unmount appl. doesn't show 'nfs' type FSs
• QXCR1000196574: OSSPI should not discovery logical network if to netif.cfg file
• QXCR1000199135: syntax_gp not getting created in AIX
• QXCR1000200757: osspi_discmod.volgrp.sh script skips MC/SG filesystems
• QXCR1000210568: OSSPI/MWA alarmdef generation fails because of non-active disks for HPUX
• QXCR1000214498: Can not monitor the procmon and fsmon for FQDN node

Known Problems, Limitations, and Workarounds

The known problems, limitations, and workarounds for OSSPI B.03.15 are listed below.

OSSPI manages Sun Cluster 3.0 only

The OSSPI supports management of Sun Cluster version 3.0 only.

Sun Cluster policies are not autodeployed

Except for the OSSPI-SunClusterDiscovery autodiscovery policy, the other Sun Cluster policies are not automatically deployed.

NAFO group removal from the Sun Cluster setup stops alerts

If you remove the NAFO group from the Sun Cluster setup and then re-create it, alerts from the NAFO group are not received.

Solaris 10 service discovery

On Solaris version 10, the services (such as cron, snmp, sendmail and so on) that are managed by the Service Management Facility (SMF) are not discovered or monitored. These services are not displayed on the service map.

Verified Environments

• Supported OVO Management Server Version

  OVO 7.5

• Supported OVO Managed Node Operating Systems (To display supported versions, click the operating system name. To hide details, click again.)
  • AIX

    Version	Power
    4.3.1	X
    4.3.2	X
    4.3.3	X
    5.1	X
    5.2	X

  • HP-UX

    Version	PA-RISC	Itanium
    11.00	X
    11.11	X
    11.22		X
    11.23		X
    11.23PI	X	X

  • RedHat Linux

    Version	x86
    6.2	X
    7.0	X
    7.1	X
    7.2	X
    7.3	X
    7.4	X
    8	X
    9	X
    EL 2.1	X
    EL 3.0	X

  • SUSE Linux

    Version	x86	Itanium
    6.4	X
    7.0	X
    7.1	X
    7.2	X
    7.3	X
    8.0	X
    8.1	X
    9	X
    ES 8	X	X

  • Debian Linux

    Version	x86
    3.0 r0	X
    3.0 r1	X

    
    

  • Turbo Linux

    Version	x86
    6.5	X
    7.0	X

  • Solaris

    Version	32 bit	64 bit
    2.6	X	X
    7	X	X
    8	X	X
    9	X	X
    10	X	X

    
    The Veritas Volume Manager, Solaris Volume Manager (SDS), Sun Cluster, HP OpenView Performance Agent and HP OpenView GlancePlus are not supported by OSSPI on Solaris version 10.
    
    

  • Tru64 UNIX

    Version	Alpha
    4.0F	X
    4.0G	X
    5.0A	X
    5.1	X
    5.1A	X
    5.1B	X

Integration With Other OpenView Solutions

Supported OV Performance Tools:

OS	Coda	MW	GP	NP
AIX	X	X	X	X
HP-UX	X	X	X	X
Linux	X	X	X	X
Solaris	X	X	X	X
Tru64 UNIX	X	X		X

Key:

	Coda:	OVO Embedded Performance Component
	GP:	HP OpenView GlancePlus
	MW:	HP OpenView Performance Agent (OVPA, earlier MeasureWare)
	NP:	No Performance Tool

Supported versions of OVPA (MWA) and GP:

Operating System	OVPA and GP version
AIX	C.03.80.00 and later
HP-UX	C.03.70.00 and later
Linux	C.04.00.00 and later
Solaris	C.03.75.00 and later
Tru64 UNIX (GP not available)	C.03.60.00 and later

Support

Please visit the HP OpenView web site at: http://www.managementsoftware.hp.com/This web site provides contact information and details about the products, services, and support that HP OpenView offers. You can also go directly to the support web site at: http://support.openview.hp.com/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 valuable support customer, you can benefit by being able to:
• Search for knowledge documents of interest
• Submit and track progress on support cases
• 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

NOTE: Most of the support areas require that you register as an HP Passport user and log in. Many also require an active support contract. To find more information about support access levels, go to the following URL:

http://support.openview.hp.com/access_level.jsp

To register for an HP Passport ID, go to the following URL:

https://passport.hp.com/hpp2/newuser.do

To view release notes and other documentation:
1. Click using hp software--> product manuals.
   
   

   The product manuals search window opens. It is located at:

   http://ovweb.external.hp.com/lpe/doc_serv/

2. In the select product list, click Smart Plug-ins for UNIX.
3. In the select version list, click b.03.15.
4. In the OS list, click Windows.
5. To start the search, click Open or Download.

NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following URL:

http://www.adobe.com

Legal Notices

©Copyright 2005 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice.

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.