|
|
United States-English | |
|
|
 |
|
 HP OpenVMS Systems Documentation |
|
The notes in this section are related to the preinstallation and
installation of the Availability Manager software.
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.6:
These requirements are explained in the Version 2.6 installation
instructions.
If you install the Version 2.5 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.
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 with the new version.
The following sections discuss new and changed features introduced in
Version 2.6 of the Availability Manager.
The DECamds System Overview window format has been very popular and useful in the past. In this release of the Availability Manager, the System Overview window has been redesigned to match this format.
This format allows you to view nodes in multiple groups at the same
time.
In addition to the redesigned System Overview window, this version of the Availability Manager has two new windows to help you monitor sites with many groups and nodes:
2.3 New Single-Process DisplaysThe DECamds Single Process window has been very popular and useful in the past. In this release of the Availability Manager, there are two new views of the Single Process window:
2.4 Support for OpenVMS Version 8.3
This version of the Availability Manager supports monitoring of OpenVMS
Version 8.3 nodes, including Alpha and I64 systems.
The data collections that involve collecting data from the CPU
databases (Node Summary and CPU Modes) have been updated to report data
on up to and including 64 CPUs.
Several new flags have been added to the "Capabilities and CPU Flags" column in the CPU Modes view, CPU page, and Group/Node pane. The new flags and the systems to which they apply are in the following table:
2.7 Events AddedThe following events have been added:
These events set thresholds for interrupt and MP synchronization mode time. The Primary CPU on OpenVMS has several tasks assigned to it, such as updating the system clock.
If the system overhead on this CPU approaches 100%, performance
problems might result such as degradation in I/O and lock manager
performance.
The following sections discuss problems that have been corrected in
Version 2.6 of the Availability Manager.
The accounting for the number of COMO processes in the Node Summary
data collection was incorrect and was usually underreported. This
problem has been corrected.
Several filter options in the Disk Status and Disk Volume Filtering did not work. For instance, in the Disk Status page, the offline checkbox might not be checked, but nevertheless the offline disks were listed.
Other checkboxes also did not operate correctly. In the Disk Volume
page, the RAMdisks checkbox did not detect all RAMdisks, and the
Exclude Devices list did not work correctly. All of these problems have
been corrected.
The disk free space in the Volume Summary view, Disk tab, Node Summary page at times reported a stale value for a disk in an OpenVMS Cluster. This problem has been corrected.
Note, however, that the free space is stored on the node that masters
the disk's resources. To obtain an accurate reading of the disk free
space for a disk in an OpenVMS Cluster, check the "Collect"
checkbox for disk volume in the Data Collection customization at the
Group level. This enables background data collection for disk volume
data over the cluster.
The following fixes have been made for the collection of single process data:
3.5 Bad Memory Page Collection Fixed
On I64 systems, the data collection to gather the bad memory pages on
the system operated incorrectly. This problem has been corrected.
Many alignment faults generated by SYS$RMDRIVER have been eliminated.
Work continues to eliminate these faults altogether and is expected to
be completed in a future release.
For large memory machines in the multigigabyte range, memory values are
now reported in gigabytes.
The thresholds in the following table have been changed to reflect the increase performance of machines in general:
3.9 CPU Qs Column Documentation and Tooltip ChangesThis column is the total of COM, COMO, MWAIT, COLPG, PFW and FPG states. (COM and COMO have always been included.)
The tooltips for this column in several displays and the documentation
have been updated. (DECamds documentation has remained the same.)
The following sections contain notes pertaining to the operation of the
Availability Manager Version 2.6, including restrictions on operation.
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.
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.
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.
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.
The following sections contain notes pertaining to the display of Data
Analyzer data on all platforms and on OpenVMS systems.
The following sections contain notes about the display of the Data
Analyzer on Windows and OpenVMS platforms in Version 2.5.
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.
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:
This problem was corrected in the OpenVMS Version 7.3-1 PEDRIVER.
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:
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.
|
| ** About PDF files: The PDF files on this Web site can be read online or printed using Adobe® Acrobat® Reader. If you do not have this software installed on your system, you may download it from the Adobe Web site. | ||
|
|
|
|||||||||||||||
|
|||||||||||||||
