HP Availability Manager - Version V3.0 Release Notes ______________________ IMPORTANT ______________________ In these Release Notes, the term Combined kit refers to the Data Analyzer/Data Server kit. Be sure to read the following notes: o Note 1.3-contains information about new security measures for communication between the Data Analyzer and Data Server. o Notes 1.2 and 1.5. Note 1.2 describes the requirement that the installation disk be an ODS- 5 formatted disk on OpenVMS systems using the Combined kit. Note 1.5 describes how to install the Combined kit on any ODS-5 formatted disk. o Notes 1.4-explains that the AVAIL_MAN_ANA kit has been renamed to AVAIL_MAN_ANA_SRVR. ______________________________________________________ The following notes address late-breaking information and known problems for the HP Availability Manager Version V3.0. These notes are in the following categories: o New and changed features o Installation notes o Problems corrected o Operation notes o Display notes ________________________ Note ________________________ The HP OpenVMS Availability Manager User's Guide has been updated to reflect changes made in Version V3.0 of the Availability Manager software. However, because the System Overview Window is not yet in its final form, the only screen capture that has been updated is in Chapters 1 and 2. 1 When the System Overview Window is in its final form, other screen captures that are based on that window will be updated in the manual. ______________________________________________________ 1 New and Changed Features The following section discusses new and changed features introduced in Version 3.0 of the Availability Manager. 1.1 Data Collection Over a Wide-Area Network (WAN) The Availability Manager can now collect data over a WAN. This possible because a new software component has been added to the Availability Manager software: the Data Server. The Data Server resides on the same local-area network (LAN) as the OpenVMS systems that you want to monitor. The Data Analyzer connects to the Data Server over the WAN. Using the IP protocol suite, data packets are transmitted between the Data Analyzer and the Data Server. This method of transmitting data packets allows the Data Analyzer to reside anywhere on the WAN. Data Server setup and usage details are in the HP OpenVMS Availability Manager User's Guide, Sections 1.1 and 1.2, as well as Sections 2.2 through 2.4. A separate document Setting Up Secure Server Connections contains steps to set up secure connections between the Data Analyzer and Data Server. 1.2 Use of Java Version 5.0 for the Combined Kit The Availability Manager Combined kit uses the 5.0 version of the Java Virtual Machine. (Java Version 5.0 is also known as 1.5.) The following changes are the result of this Java upgrade: o For OpenVMS systems using the Data Analyzer or Data Server, the installation disk must be an ODS-5 disk. o Performance on OpenVMS has improved. 2 1.3 Security Measures for Data Analyzer-Data Server Communications over a Wide Area Network (WAN) In Version V3.0, the Availability Manager uses Transport Layer Security (TLS) for secure WAN communication between the Data Analyzer and Data Server. See the separate document Setting Up Secure Server Connections for steps that you must perform in order to set up this security mechanism. 1.4 Data Analyzer Kit Renamed to AVAIL_MAN_ANA_SRVR The AVAIL_MAN_ANA kit has been renamed to AVAIL_MAN_ANA_ SRVR because the new kit contains both the Data Analyzer and Data Server. ________________________ Note ________________________ You need to uninstall the AVAIL_MAN_ANA kit before installing the new AVAIL_MAN_ANA_SRVR kit. ______________________________________________________ 1.5 Ability to Install the Combined Kit on a Non-system Disk In Version V3.0, you can install the Combined kit, AVAIL_ MAN_ANA_SRVR, on a non-system ODS-5 formatted disk. This kit removes the requirement that the kit be installed on the system disk. To install on a non-system ODS-5 formatted disk, use the /DESTINATION qualifier of the $ PRODUCT INSTALL command to specify the installation disk and directory; for example: $ PRODUCT INSTALL AVAIL_MAN_ANA_SRVR /DESTINATION=DISK$SYS_V83:[SOFTWARE] The manual HP Availability Manager Installation Instructions details how to do the installation. 1.6 New STATUS Command Option in SYS$STARTUP:AMDS$STARTUP Command Procedure The STATUS command option shows the current state of the Data Collector; for example, RMDRIVER STOPPED and RMDRIVER STARTED. 3 To display the output of this new option, enter the following command: $ SYS$SYSTARTUP:AMDS$STARTUP HELP STATUS Examples of a STATUS command and output messages are the following: $ @SYS$STARTUP:AMDS$STARTUP STATUS Current status of AM/DECamds Data Collector device RMA0: RMA0: is started and is ready to accept requests for data and can accept a connection from a Data Analyzer RMA0: is set to log data requests generating security violations to OPCOM (AMDS$RM_OPCOM_READ is set to TRUE) RMA0: is set to log fixes generating security violations to OPCOM (AMDS$RM_OPCOM_WRITE is set to TRUE) RMA0: is using VCI for network communications 1.7 Windows Availability Manager Software Can Use an FDDI Network Adapter You can now use an FDDI network adapter to communicate with the network on a Windows version of the Availability Manager Data Analyzer. (Note that the OpenVMS Availability Manager software can already use an FDDI network adapter.) 1.8 Features not documented in the HP OpenVMS Availability Manager User's Guide Version 3.0 manual The following new features have not been documented in the HP OpenVMS Availability Manager User's Guide Version 3.0. These will be documented in the next release of the Availabililty Manager software. 1.8.1 Lock Contention Filter page now allows entry in hex The Lock Contention Filter page has been enhanced to display any entry in hex and allows entering hex values for an entry. There are 16 hex fields for the first 16 bytes of a resource name. A blank field indicates that there is no value for that byte. The ability to edit all 31 characters of a resource name will be done in a future release. 4 1.8.2 Fix to force a disk vlume out of mount verify state A new fix has been added to take a disk volume that is in a mount verify state and force it into a mount verify timeout state. This fix is available by right-clicking on any disk entry in the Disk Status Summary or Disk Volume Summary of a node pane. If the disk is not mounted or not in a mount verify state, the fix will return an OpenVMS error status. The return statuses are as follows: ___________________________________________________________ Return_Status____Description_______________________________ SS$_NORMAL Disk was successfully taken out of the mount verify state. SS$_DEVNOTMOUNT Disk is not mounted by this node. SS$_VOLINV Disk is a shadow set virtual unit or a shadow set member. SS$ WRONGSTATE Disk is not in the mount verify state. ___________________________________________________________ 1.8.3 Fix to force a shadow set member out of a shadow set A new fix has been added to take a shadow set member in a mount verify state out of a shadow set. This has the same effect as the DCL command $ SET SHADOW/FORCE_REMOVAL ddcu: This fix is available by right-clicking on any shadow set member entry in the Disk Status Summary or Disk Volume Summary of a node pane. Note: To show shadow set members in these two summaries, you need to bring up the Disk Status filter and set the Transaction count to zero. If the shadow set member is not mounted or not in a mount verify state, the fix will return an OpenVMS error status. The return statuses are as follows: ___________________________________________________________ Return_Status____Description_______________________________ SS$_NORMAL Shadow set member was successfully taken out of the mount verify state. 5 ___________________________________________________________ Return_Status____Description_______________________________ SS$_DEVNOTMOUNT Shadow set member is not mounted by this node. SS$_VOLINV Shadow set member is a shadow set virtual unit, a Host Based RAID device or not a shadow set member. SS$_WRONGSTATE Shadow set member is not in the mount verify state. SS$ BADTIME Shadow set is in a failed state. ___________________________________________________________ 2 Installation Notes The notes in this section are related to the preinstallation and installation of the Availability Manager software. 2.1 Uninstall Data Analyzer Kits Before Installing the Combined Kit for Version 3.0 Before installing the V3.0 AVAIL_MAN_ANA_SRVR kit, you must uninstall the old AVAIL_MAN_ANA kit. You cannot install the new kit over the old one because of restrictions in the $ PRODUCT INSTALL command. (Note that the Data Analyzer kit, ANA_MAN_ANA in previous versions, has been renamed to AVAIL_MAN_ANA_SRVR in Version 3.0; this new name better reflects the Data Analyzer and Data Server combination.) 2.2 Uninstall Versions of the Availability Manager Prior to 2.4 Before Installing the V3.0 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 3.0: o On Windows systems, you must first uninstall Versions 2.3 and lower kits. On Versions 2.4 and higher, you can install new kits over prior kits. 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 3.0 directly. 6 - 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.3-1 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 3.0 Combined kit. - 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 3.0 Combined kit. These requirements are explained in the Version 3.0 installation instructions. 2.3 Installing from an ODS-5 Disk If you install the Version 3.0 kit from an ODS-5 disk, the file name for the kit must be in all-capital letters for the kit to be installed correctly. 2.4 Copy Your AVAILMAN.INI File Prior to installation, you might want to make a copy of your AVAILMAN.INI file to save your customizations such as 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 once the new version is installed. 3 Problems Corrected The following sections discuss problems corrected in Version 3.0 of the Availability Manager. 7 3.1 Password Encryption Now Enabled by Default The password encryption feature introduced in Version 2.5 was not enabled as expected. This meant that the password for the Data Collector was passed in plain text. This problem has now been corrected. 3.2 Problem Starting Data Analyzer When DCL Extended Parsing Is On On OpenVMS systems, when the DCL parsing style was set to extended ($ SET PROCESS/PARSE_STYLE=EXTENDED), starting the Data Analyzer resulted in an unrecognized option error: Unrecognized option: -CP Could not create the Java virtual machine. This problem has been corrected. 3.3 Sizing of Displays Corrected The updated Data Analyzer now sizes and displays tables and sections of a window correctly-according to the size of the font. The Lock Contention and Cluster displays are now more readable as well. These changes are especially evident on OpenVMS systems. 3.4 Data Analyzer Performance Improvements The reworking of the Data Analyzer to initiate and use connections to the Data Server also made processing of data more efficient. The result has been improved performance in the Data Analyzer. 4 Operation Notes/Restrictions The following sections contain notes pertaining to the operation of the Availability Manager Version 3.0. The sections are subdivided into field test versions and a final section that contains notes applying to all field test versions. 4.1 Notes for Version 3.0 The following sections contain notes that apply the Availability Manager Version 3.0. 8 4.1.1 Changing the Number of the Port the Data Server Uses The default port number for the Data Server is 9819. If you want to use a different port number, do one of the following: o For Windows systems, modify the Data Server startup shortcut. Right-click the shortcut, and choose Properties. In the "Target:" field, find the number 9819. Change this number to the port you want. o For OpenVMS systems, use the /PORT_NUMBER qualifier to specify a different port number; for example: $ AVAIL/SERVER/PORT_NUMBER=5498 4.1.2 Changing the Network Adapter the Data Server Uses on Windows Systems On Windows systems, the Data Server picks up the first available network adapter for data communications. If it selects an undesirable network adapter-for example, a wireless adapter on a laptop-you can disable this selection by unchecking "HP Availability Manager NDIS 5.0 Protocol Driver" in the Network Properties for the network adapter. 4.1.3 Stopping the Data Server You can stop the Data Server in one of the following ways: o On Windows systems, close the Windows console window where the Data Server is running. o On OpenVMS sysetms, Ctrl/Y stops the Data Server in interactive processes. Stopping the process stops the Data Server for batch processes. 4.1.4 Data Server Uses Only First Network Adapter This version of the Data Server on Windows selects the first network adapter that it discovers when it starts up. The network adapter it chooses is displayed in a log message on the screen. Plans for a future field test release include the ability to select the network adapter of your choice. 9 4.1.5 Starting the Data Server Might Trigger Windows Security Alert On Windows systems, a security alert from the Windows firewall or third-party firewall might be displayed for the Java 2 Platform Standard Edition binary. The Data Server needs to accept connections as part of its normal operation. Tell the firewall to "Unblock" the program. 4.2 Notes for All Versions The following sections contain notes that apply to all versions of the Availability Manager. 4.2.1 Running Reflective Memory by GE Fanuc and Availability Manager The Reflective Memory product by GE Fanuc sets up the device RMA0: as part of its normal operation. Because the Availability Manager Data Collector also creates the device RMA0:, both products cannot run on the same node at the same time. 4.2.2 Administrator Account Required to Run the Availability Manager On Windows 2000 and Windows XP platforms, you must run the Data Analyzer or Data Server from an account in the Administrator group. This restriction will be removed in a future release of the Availability Manager. 4.2.3 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. 10 4.2.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 notes pertaining to the display of Data Analyzer data on all platforms and on OpenVMS systems. 5.1 Problems Using the Data Analyzer on All Platforms The following sections contains subsections pertaining to the display of the Data Analyzer on Windows and on OpenVMS platforms in Version 3.0. 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. 11 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 be corrected in DECwindows Motif Version 1.3-1. 12