HP OpenVMS Systems Documentation
HP Availability Manager User's Guide
Order Number: AA-RNSJD-TE
This guide explains how to use HP Availability Manager software to detect and correct system availability problems.
Revision/Update Information: This guide supersedes the HP OpenVMS Availability Manager User's Guide, Version 2.3-1.
Data Analyzer: Windows 2000 SP 4 or higher; Windows XP
Software Version: HP Availability Manager Version 2.4-1
© 2005 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.
Printed in the US
The HP OpenVMS documentation set is available on CD-ROM.
This guide is intended for system managers who install and use HP Availability Manager software. It is assumed that the system managers who use this product are familiar with Windows terms and functions.
This guide contains the following chapters and appendixes:
The following manuals provide additional information:
For additional information about HP OpenVMS products and services, visit the following World Wide Web address:
HP welcomes your comments on this manual. Please send comments to either of the following addresses:
How to Order Additional Documentation
For information about how to order additional documentation, visit the following World Wide Web address:
The following conventions are used in this guide:
|Immediate notification of problems||Based on its analysis of data, the Availability Manager notifies you immediately if any node you are monitoring is experiencing a performance problem, especially one that affects the node's accessibility to users. At a glance, you can see whether a problem is a persistent one that warrants further investigation and correction.|
|Centralized management||Provides centralized management of remote nodes within an extended local area network (LAN).|
|Intuitive interface||Provides an easy-to-learn and easy-to-use graphical user interface (GUI). An earlier version of the tool, DECamds, uses a Motif GUI to display information about OpenVMS nodes. The Availability Manager uses a Java GUI to display information about OpenVMS nodes on an OpenVMS or a Windows node.|
|Correction capability||Allows real-time intervention, including adjustment of node and process parameters, even when remote nodes are hung.|
|Uses its own protocol||An important advantage of the Availability Manager is that it uses its own network protocol. Unlike most performance monitors, the Availability Manager does not rely on TCP/IP or any other standard protocol. Therefore, even if a standard protocol is unavailable, the Availability Manager can continue to operate.|
|Customization||Using a wide range of customization options, you can customize the Availability Manager to meet the requirements of your particular site. For example, you can change the severity levels of the events that are displayed and escalate their importance.|
|Scalability||Makes it easier to monitor multiple OpenVMS nodes.|
Figure 1-1 is an example of the initial Application window of the Availability Manager.
Figure 1-1 Application Window
The Application window is divided into the following sections:
The Data Analyzer and Data Collector nodes communicate over an extended LAN using an IEEE 802.3 Extended Packet format protocol. Once a connection is established, the Data Analyzer instructs the Data Collector to gather specific system and process data.
Although you can run the Data Analyzer as a member of a monitored cluster, it is typically run on a system that is not a member of a monitored cluster. In this way, the Data Analyzer will not hang if the cluster hangs.
Only one Data Analyzer at a time should be running on each node; however, more than one can be running in the LAN at any given time.
Figure 1-2 shows a possible configuration of Data Analyzer and Data Collector nodes.
Figure 1-2 Availability Manager Node Configuration
In Figure 1-2, the Data Analyzer can monitor nodes A, B, and C across the network. The password on node D does not match the password of the Data Analyzer; therefore, the Data Analyzer cannot monitor node D.
For information about password security, see Section 1.4.
After installing the Availability Manager software, you can begin to request information from one or more Data Collector nodes.
Requesting and receiving information requires the Availability Manager to perform a number of steps, which are shown in Figure 1-3 and explained after the figure.
Figure 1-3 Requesting and Receiving Information
The following steps correspond to the numbers in Figure 1-3.
In step 4, the Availability Manager also checks the data for any events that
should be posted. The following section explains in more detail how
data analysis and event detection work.
1.3 How Does the Availability Manager Identify Performance Problems?
When the Availability Manager detects problems on your system, it uses a combination of methods to bring these problems to the attention of the system manager. If no data display is open for a particular node, the Availability Manager reduces the data collection interval so that data can be analyzed more closely. Performance events are also posted in the Event pane, which is in the lower portion of the Application window (Figure 1-1).
The following topics are related to detecting problems and posting events:
This section explains how the Availability Manager collects and analyzes data.
It also defines terms related to data collection and analysis.
126.96.36.199 Types of Data Collection
Figure 1-4 Data Collection Customization Page
Figure 1-5 Sample Node Summary Page
An event is a problem or potential problem associated with resource availability. Users can customize criteria for events. Events are associated with types of data collected. For example, collection of CPU data is associated with the PRCCUR, PRCMWT, and PRCPWT events. (Appendix B describes events, and Appendix C describes the events that each type of data can signal.)
When the GUI requests one type of data from the Data Collector (for
example, CPU data for all the processes on the system), a snapshot is
taken of that type of data. This snapshot is considered one
188.8.131.52 Data Collection Intervals
|Interval (in seconds)||Type of Data Collection||Description|
How often data is collected if no events have been posted for that type
The Availability Manager starts background data collection at the NoEvent interval (for example, every 75 seconds). If no events have been posted for that type of data, the Availability Manager starts a new collection cycle every 75 seconds.
How often data is collected if any events have been posted for that
type of data.
The Availability Manager continues background data collection at the Event interval until all events for that type of data have been removed from the Event pane. Data collection then resumes at the NoEvent interval.
How often data is collected when the page for a specific node is open.
The Availability Manager starts foreground data collection at the Display interval and continues this rate of collection until the display is closed. Data collection then resumes as a background activity.
The Availability Manager evaluates each data collection for events. The Availability Manager posts events when data values in a data collection meet or exceed user-defined thresholds and occurrences. Values for thresholds and occurrences are displayed on Event Customization pages similar to the one shown in Figure 1-6. Thresholds and occurrences are described in the next section.
Figure 1-6 Sample Event Customization Page