Release Notes for HP Performance Agent (OVPA) Version 4.0-40 for OpenVMS Copyright © 2010 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 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. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. HP Performance Agent Version 4.0-40 for OpenVMS is primarily released to include OVPA support on OpenVMS Version 8.4. In this release, OVPA is statically linked with SSL Version 1.3 to make it independent of the SSL version installed on the system. This has been qualified with the HP OpenView Performance Manager (OVPM) Version 6.x and 8.x. This document is organized as follows: 1 Problems Fixed 2 Restrictions and Known Issues 1 Problems Fixed ================ 1.1 Issue with starting OVPA with TDC 2.3-x -------------------------------------------- Problem: -------- OVPA would not start with TDC 2.3-x. Solution: --------- The problem is fixed by modifying the TDC version check code appropriately. 1.2 OVPA alarms not reported to OpenVMS HTTPS Agents ----------------------------------------------------- Problem: -------- QXCM1000891741 - OVPA alarms are not reported to the OVO HTTPS management server. Solution: --------- This codebase of OVPA is designed to interoperate with OpenVMS DCE agents seamlessly. However, this codebase has been tweaked to interoperate with OpenVMS HTTPS agents. The next major version release of OVPA would be based on new codebase and would interoperate with OpenVMS HTTPS agents seamlessly. 1.3 Blank template file ------------------------ Problem: -------- QXCM1000869155 -The default template file "reptall" is an empty file. Solution: --------- The "reptall" file is modified. In this file, all the supported OpenVMS metrics are commented. Users need to remove the comments from the required metrics to use it. 1.4 Issue with "EXTRACT" command --------------------------------- Problem: -------- QXCM1000889960 - While exporting data using extract command on OVPA node, it gives the following error: "Unable to read record from file, size returned = 0" Solution: --------- This problem is fixed. 1.5 OVPA$TTD aborts during cluster reboot ------------------------------------------ Problem: -------- QXCM1000894846 - At times OVPA$TTD aborts during cluster reboot. Solution: --------- The code that handles ttd.pid file is modified to fix this problem. 1.6 Increase in file size for thread.out ----------------------------------------- Problem: -------- QXCM1000906031 - Thread.out file keeps on increase in size over the time. Solution: --------- This problem is fixed by modifying the cleanup operation before starting OVPA. 2 Restrictions and Known Issues =============================== The following are the restrictions and known issues in HP Performance Agent (OVPA) Version 4.0-40 for OpenVMS: - Coexistence of OVPA 4.0 with HP OpenVMS HTTPS Operations Manager Agent The default port used by the communication broker of HTTPS Agents is 383. This has to be changed for HTTPS agents to a customized port number, if the HTTPS Agents and OVPA 4.0 are to be used on the same managed node. To change the default port to a customized port, follow these steps: 1. Stop agents. 2. On managed node: ovconfchg -ns bbc.cb -set "SERVER_PORT" 3. On management server: /opt/OV/bin/ovconfchg -ns bbc.cb.ports -set : 4.Restart agents. - OpenView HTTPS Agents and OVPA cannot coexist on the same OpenVMS node when OM and PM coexist on the same management server. NOTE: The coexistence issues described above is not applicable to OpenVMS Version 8.4 as Operations Manager Agents are yet to be qualified on OpenVMS Version 8.4. - The following display fields in OVPM are not supported on OpenVMS: o The Disk ID display shows up blank. Disk ID is a unique ID on UNIX and it is not supported on OpenVMS. However, the device name is a unique ID on OpenVMS and can be used instead of Disk ID. o INODE is not applicable to OpenVMS. HP is investigating an alternative metric for INODE. - If you have installed TDC clusterwide, the OVPA installation might not be aware of the TDC installation. You must install TDC on all the nodes where you are installing OVPA. - Prior to installing an update to the TDC software from the TDC website (http://www.hp.com/products/openvms/tdc), shut down OVPA by executing the @SYS$STARTUP:OVPA$SHUTDOWN command. Failure to do so prevents the newly-installed TDC software from running correctly. The TDC installation installs an updated version of the TDC execlet image into SYS$LOADABLE_IMAGES, and the newly-installed TDC software attempts to load the updated execlet when it starts a collection. This attempt is blocked because the previous version of the execlet image is still in use. The TDC collection operation continues; however, TDC is unable to gather most process- and disk-I/O metrics.