In these Release Notes, the term Combined kit refers to the Data Analyzer/Data Server kit. The Release Notes documents additions and changes for version 3.0-2 of the Combined kit and version 3.0-2A of the Data Collector kit. Be sure to read the following sections:
|
The following notes address late-breaking information and known problems for the HP Availability Manager Version 3.0-2. These notes are in the following categories:
The following section discusses new and changed features introduced in Version 3.0-2 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.6.
The Availability Manager uses Transport Layer Security (TLS) for secure WAN communication between the Data Analyzer and Data Server. See the Chapter 2 of HP OpenVMS Availability Manager User's Guide for steps that you must perform in order to set up this security mechanism.
1.2 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.
You need to uninstall the AVAIL_MAN_ANA kit before installing the new AVAIL_MAN_ANA_SRVR kit. |
1.3 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:
1.4 Ability to Install the Combined Kit on a Non-system Disk
In Version 3.0-2, 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.5 New Data Columns in System Overview and Related Event Additions and Changes
Version 3.0-2 introduces three new data columns in the System Overview Window.
| Data Column | Description |
|---|---|
| PFLTS | Total page fault rate and hard fault rate |
| PFW/COM | Number of processes in PFW and COM states |
| DC | Data Collector capability version and Managed Object registration status |
Version 3.0-2 also changed the CPU Qs column. The states summed in this column are now COLPG, COMO, FPG, and MWAIT. The column also displays the individual state counts if the total is greater than zero. The COM and PFW state counts that used to be included in the CPU Qs count have been moved to the new PFW/COM column.
New events in Version 3.0-2 follow. The last three result from the new PFW/COM column and changes to the CPU Qs column.
| Data Column | Description |
|---|---|
| HIALNR | High alignment fault rate |
| HICMOQ | Many processes waiting in COMO |
| HIPFWQ | Many processes waiting in PFW state |
| PRCCMO | Process waiting in COMO |
These events have changed as a result of the column changes.
| Event | Description |
|---|---|
| HICOMQ | Many processes waiting in COM |
| HIPWTQ | Many processes waiting in COLPG or FPG |
| PRCCOM | Process waiting in COM |
1.6 Data Collection for Logical Disk (LDcn:) devices
The Data Analyzer now collects data on Logical Disks. These devices show up in the Disk Status and Disk Volume displays.
1.7 System Memory and Alignment Faults in Mem Column Tooltip
The Mem column in the System Overview Window now shows the total amount of memory on the system, and the number of page faults by mode.
With the advent of WAN support, there is an Event Log for each connection that the Data Analyzer is using, instead of one Event Log for the Data Analyzer session.
The Event Log now contains an entry when a threshold event has been cancelled. This new entry allows you to determine how long a threshold has been exceeded.
Along with the new entry for cancelled threshold events, three new columns have been added to the Event Log. These columns are as follows:
| Event Column | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Status | The value describes the status of the event. Values are as follows:
| ||||||||||||
| EventKey | A hex value identifying an event for a node. For instance, all HINTER events for a node have the same value. Each time the HINTER event is signaled for a node, the value will be the same, making it easy to search for all the HINTER events for a node. | ||||||||||||
| EventID | A hex value identifying an individual event. For instance, if the HICOMQ event on node SAM is signaled, the BEGIN and END/CANCELD/EXPIRED entries that mark when the event was signaled and cancelled will have the same value. The next time the HICOMQ event is signaled on node SAM, the hex value will be different. This value makes it easy to find the entry that signals when the event has been cancelled. |
1.9 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.
To display help on 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.10 New LOG Command Option in SYS$STARTUP:AMDS$STARTUP Command for START and RESTART Procedure
The START and RESTART command options support the LOG option. This option displays the configuration data that is loaded into the Data Collector. This option is useful to confirm the actual data gathered and loaded.
An example of using the LOG option follows:
$ SYS$SYSTARTUP:AMDS$STARTUP START LOG |
1.11 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.12 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.
1.13 Fix to Force a Disk Volume 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.
1.14 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.
1.15 Data Analyzer Supports Change of MAC Address on Data Collector System
The Data Analyzer now supports a change of MAC address from an OpenVMS system. The MAC address of a system may change if certain network protocol stacks are started or modified, and is usually seen if the $ @SYS$STARTUP:AMDS$STARTUP START command is executed early in the system boot sequence. If this occurred in previous releases of the Availability Manager, the usual behavior is to display the system twice in the System Overview window - one entry is color-coded black, and the other is yellow, and no data is collected for the system.
The following events are affected by this change.
| Event | Description |
|---|---|
| CFGDON | Current MAC address from system is added to the event text |
| PTHLST | Last known MAC address from system is added to the event text |
| CHGMAC | New event showing the current MAC address the system is using |
| NEWMAC | New event showing that a new MAC address is recorded for the system |
1.16 Changed Disk Status Filter Mount Count to Display Shadow Set Members
The default mount count in the Disk Status filter has been set from one to zero. This setting allows shadow set members to be displayed in the Disk Status Summary display. This was done in conjunction with the shadow set member fix in Section 1.14.
1.17 Changed I/O Filter Open File Count Default
The default open file count in the I/O filter has been set from three to one. The default setting of three open files is from the DECamds application, but often filters out processes doing I/O simply because only one or two files are open for the process.
1.18 Starting the Data Analyzer or Data Server on OpenVMS Checks for Necessary Logicals
A check for all the necessary logical names has been added to the startup of the Data Analyzer or Data Server. This ensures that the Data Analyzer and Data Server can access various files needed for a correct startup. If an error message appears saying that all the logical names aren't defined, make sure to compare your SYS$MANAGER:AMDS$LOGICALS.COM file with the file SYS$MANAGER:AMDS$LOGICALS.TEMPLATE.
1.19 Data Analyzer Logs Now Incorporate Data and Time in File Name
Data Analyzer and Data Server log files now incorporate the date and time in the file name. This helps to show when the file was created, and on Windows systems where the file system doesn't save versions of a file, the older log files are not deleted when newer versions are created.s are created. File names are now in the for *_YYYYMMDD-HHMM.*.
1.20 Default Hello Multicast Interval Changes
The default and secondary intervals in AMDS$LOGICALS.COM have been changed from 30 and 90 to 10 and 15 seconds respectively. The older defaults were appropriate for older, slower networks of a number of years ago. The change for more modern networks allows the Data Analyzer to discover OpenVMS systems more quickly. This change is made in the file SYS$MANAGER:AMDS$LOGICALS.TEMPLATE. Carry this change into your SYS$MANAGER:AMDS$LOGICALS.COM file to change the Data Collector behavior.
1.21 Option to Increase OpenVMS Data Analyzer Performance When Displayed on a Remote System
The logical AMDS$AM_DISABLE_OFFSCREEN_PIXMAP_SUPPORT controls whether or not the Java Virtual Machine uses offscreen pixmap support. Disabling this support can increase performance, especially when the Data Analyzer display is on a remote system using TCP/IP. If the performance of the OpenVMS Data Analyzer in this situation is slow, you can try setting this logical to TRUE to see if this helps in your situation. This change is made in the file SYS$MANAGER:AMDS$LOGICALS.TEMPLATE. Carry this change into your SYS$MANAGER:AMDS$LOGICALS.COM file to enable use of the AMDS$AM_DISABLE_OFFSCREEN_PIXMAP_SUPPORT logical.
The notes in this section are related to the preinstallation and installation of the Availability Manager software.
2.1 Check Date of AMNDIS50.SYS on Windows Systems After Installing Version 3.0-2
After installing the Version 3.0-2 Windows kit, check the date of the AMNDIS50.SYS file. This file is on the Windows system disk, usually in C:\WINDOWS\system32\drivers. The date should be November 28, 2006. If the date is earlier than this, you need to uninstall the Availability Manager software, and then reinstall it. Make sure to reboot your system when you are prompted to do so. This usually fixes the problem. The problem is being investigated. It is important to have the latest AMNDIS50.SYS file as it has fixes in it to prevent some system crashes when two Data Analyzers are started at the same time.
2.2 Uninstall Data Analyzer Kits Before Installing the Combined Kit for Version 3.0-2
Before installing the Version 3.0-2 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-2; this new name better reflects the Data Analyzer and Data Server combination.)
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-2:
These requirements are explained in the Version 3.0-2 installation instructions.
2.4 Installing from an ODS-5 Disk
If you install the Version 3.0-2 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.5 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 event threshold settings and 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.
The following sections discuss problems corrected in Version 3.0-2 of the Availability Manager.
3.1 Alignment Faults in the Data Collector Have Been Fixed
The remaining alignment faults in the Data Collector (SYS$RMDRIVER.EXE) have been found and fixed.
3.2 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.3 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.4 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.5 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.
3.6 Lock Contention Data Collection Performance Improvements
For systems with large resource hash tables, the data collection for lock contention have been improved, and result in less network traffic.
| Next |