HP Availability Manager Version 2.4-1 Release Notes The following notes address late-breaking information and known problems for the HP Availability Manager Version 2.4-1. These notes fall into the following categories: o Installation note o New and changed features o Problems corrected o Operation notes o Display notes 1 Installation Note: Uninstall Prior Versions Before Installing the New Kit On both Windows and OpenVMS systems, check the following list to see if any item applies to you. If so, follow the instructions in the appropriate section before installing Version 2.4-1: o On Windows systems, you must uninstall Versions 2.3 and lower. o On OpenVMS systems, perform one of the following steps: - If you have never installed the Availability Manager on your system, you can install Version 2.4-1 directly. - If you have installed a version of the Availability Manager prior to Version 2.4 and you are running OpenVMS Version 6.2 through Version 7.2-2 or its variants, you must perform the following steps: a. Uninstall the previous version of the Availability Manager. b. Install the Availability Manager Data Collector Version 2.4 kit. c. Install the Version 2.4-1 kit. 1 - If you have installed a version of the Availability Manager prior to Version 2.4 and you are running OpenVMS Version 7.3 or higher, you must perform the following steps: a. Uninstall the previous version of the Availability Manager. b. Install the Version 2.4-1 kit. These requirements are explained in the Version 2.4-1 installation instructions. Prior to installation, you might want to make a copy of your AVAILMAN.INI file as a reminder of the names of the groups you usually monitor. On Windows systems, also delete any desktop shortcuts for previous versions of the Availability Manager because they will be invalid with the new version. 2 New and Changed Features The following sections discuss new and changed features introduced in Version 2.4-1 of the Availability Manager. 2.1 Support for OpenVMS Version 8.2 on I64 and Alpha The Availability Manager Version 2.4-1 supports data collection from OpenVMS Version 8.2 on I64 and Alpha nodes. It also supports the Data Analyzer on OpenVMS Version 8.2 Alpha nodes. 2.2 Node Tooltips When you hold the cursor over a node in the Node pane, the Availability Manager displays a tool tip in one of several colors. Each color has a specific meaning attached to it regarding the health of the node. The colors and their meanings are in Table 1. 2 Table 1 Colors of Tooltips in the Node Pane ___________________________________________________________ Color Meaning ___________________________________________________________ Brown Indicates why the configuration of the node failed. Yellow Shows number of RM Driver broadcasts ("Hello") and the number of attempts to configure the node ("Configuration packets sent"). Nodes that remain in this state more than a few seconds indicate network connectivity problems with the Data Analyzer. Black Can show one of the following: o If the node was successfully configured and then lost, - When the connection to the node was lost ("Path lost at time"). - When that node was booted ("Boot time: time"). - What the uptime of the node was ("Uptime: time"). o If the node was never configured, - When the connection to the node was lost ("Path lost at time"). - The reason the node was not configured. Red Events signalled for the node. Green Node uptime. ___________________________________________________________ 3 Problems Corrected The following sections discuss problems corrected in Version 2.4-1 of the Availability Manager. 3.1 Correction in Total CPU Count The total CPU count in Active CPUs Column in the Node Pane can increase by the number of CPUs when a node goes down and then comes back up. For example, if a node has 3 CPUs, the total CPU count is 3. Previously, when a node went down and then came back up, the total CPU count was 6. This error has been corrected so that the total CPU count is 3. 3 3.2 Update Problem in Cluster Displays Corrected A problem was introduced in Version 2.4 whereby several of the cluster displays for a given node would stop updating after a period of time. Affected data included adapter, virtual circuit, channel, and port data. This problem has been corrected in Version 2.4-1. 3.3 LAN Adapter Displays Corrected In the LAN Adapter Summary and Details displays, the list of adapter types has been updated so that newer adapters are no longer shown as "unknown". Note also that the "type" displayed represents the underlying communications chip used rather than the HP model number of the device. 4 Operation Notes The following sections contain notes pertaining to the operation of the Availability Manager Version 2.4-1. 4.1 Administrator Account Required On Windows 2000 and Windows XP platforms, the Data Analyzer must be run from an account in the Administrator group. This restriction will be removed in a future release of the Availability Manager. 4.2 Problem Displaying Large Numbers of Processes or Disks Very busy networks can sometimes interfere with the transfer of data between the Data Analyzer and the Data Collector. This problem is noticeable when you display large numbers of disks or processes. The number of disks or processes might change temporarily because of a lost data message. This problem will be corrected in a future release. 4.3 Event Reporting Problem Version 2.4-1 of the Availability Manager does not implement the threshold event LOSTVC. 4 4.4 Local Administrator Account Required for Windows Installation To install the Availability Manager on a Windows system, you must use the local Administrator account. Some users have had problems when they use a Windows domain account that has Administrator privileges instead. For example, a failure message might appear saying "Failure to install AMNDIS50" after most of the installation is complete. This problem will be corrected in a future release. 5 Display Notes The following sections contain display notes pertaining to the Data Analyzer. 5.1 Problems Using the Data Analyzer on All Platforms The following sections contain notes about the display of the Data Analyzer on Windows and OpenVMS platforms in Version 2.4-1. 5.1.1 Events Sometimes Displayed After Background Collection Stops The Data Analyzer sometimes displays events after users customize their systems to stop collecting a particular kind of data. This is most likely to occur when the Data Analyzer is monitoring many nodes. Under these conditions, a data handler sometimes clears events before all pending packets have been processed. The events based on the data in these packets are displayed even though users have requested that this data not be collected. 5.1.2 Truncated LAN Channel Summary Display On versions of OpenVMS prior to Version 7.3-1, the LAN Channel Summary display might be disabled for some OpenVMS nodes if there are more than seven channels for that virtual circuit. This problem results from a restriction in the OpenVMS Version 7.3 PEDRIVER. For this condition, the following error message is displayed: Error retrieving ChSumLAN data, error code=0x85 (Continuation data disallowed for request) This problem was corrected in the OpenVMS Version 7.3-1 PEDRIVER. 5 5.2 Problem Using the Data Analyzer on OpenVMS Systems: Long Runs Exhaust XLIB Resource ID On older versions of DECwindows Motif, a resource ID allocation scheme works poorly with the Motif support in Java for OpenVMS. As a result, long-running Availability Manager sessions might stop updating the display at a time that depends on the speed of the OpenVMS machine. For example, a session running on a dual-processor 275 MHz system reported the following after 14 hours: Xlib: resource ID allocation space exhausted! On faster machines, this message was reported after only 8 hours. This problem appears to have been corrected in DECwindows Motif Version 1.3-1. 6