Compaq Availability Manager Version 2.2 System Performance & Availability Management Software User's Guide
Below you will find brief information for Compaq Availability Manager Version 2.2. This software is designed to help you detect and correct system availability problems by collecting and analyzing data from OpenVMS Alpha, VAX, Windows 2000, and Windows XP systems. It identifies performance issues and allows for various 'fixes' to improve system stability and performance.
Advertisement
Advertisement
Compaq Availability Manager
User’s Guide
Order Number: AA-RNSJB-TE
June 2002
This guide explains how to use Compaq Availability Manager software to detect and correct system availability problems.
Revision/Update Information:
This guide supersedes the Availability
Manager User’s Guide, Version 1.4 of the printed manual and Version 2.1 of the HTML manual.
Operating System:
Software Version:
Data Analyzer: Windows 2000 SP 2 or higher; Windows XP;
OpenVMS Alpha Version 7.1 or later
Data Collector: OpenVMS Alpha and
VAX Version 6.2 or later
Compaq Availability Manager Version
2.2
Compaq Computer Corporation
Houston, Texas
© 2002 Compaq Information Technologies Group, L.P.
Compaq, the Compaq logo, Alpha, OpenVMS, Tru64, VAX, VMS, and the DIGITAL logo are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.
Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft
Corporation in the U.S. and/or other countries.
Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries.
Motif, OSF/1, and UNIX are trademarks of The Open Group in the U.S. and/or other countries.
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.
All other product names mentioned herein may be trademarks of their respective companies.
Confidential computer software. Valid license from Compaq 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.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
ZK6552
The Compaq OpenVMS documentation set is available on CD-ROM.
This document was prepared using DECdocument, Version 3.3-1b.
Contents
Preface
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Overview
1.1
1.2
1.3
1.3.1
1.3.1.1
1.3.1.2
1.3.1.3
1.3.2
1.3.2.1
1.4
1.4.1
1.4.2
What Is the Availability Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Does the Availability Manager Work? . . . . . . . . . . . . . . . . . . . . . . . .
How Does the Availability Manager Identify Performance Problems? . . . .
Collecting and Analyzing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Events and Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Collection Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Thresholds and Occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Does the Availability Manager Maintain Security? . . . . . . . . . . . . . .
Data Analyzer Password Security . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Data Collector Security Features . . . . . . . . . . . . . . . . . . . .
2 Getting Started
2.1
2.2
2.2.1
2.2.2
2.3
2.3.1
2.3.2
2.3.3
2.4
2.4.1
2.4.2
2.4.3
2.5
Starting the Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the Data Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Start the Data Analyzer on an OpenVMS Alpha Node . . . . . .
How to Start the Data Analyzer on a Windows Node . . . . . . . . . . . . . .
Using the Application Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Window Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding Groups of Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying More Information about Nodes . . . . . . . . . . . . . . . . . . . . . . . . .
Choosing a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying Data to Collect on OpenVMS Nodes . . . . . . . . . . . . . . . . . .
Sorting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Getting Information About Nodes
3.1
3.1.1
3.1.2
3.2
3.2.1
Node Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Node Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Node Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Data Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xi
3–1
3–2
3–2
3–3
3–4
1–1
1–3
1–4
1–5
1–5
1–6
1–6
1–7
1–8
1–8
1–8
1–9
2–1
2–2
2–2
2–2
2–2
2–4
2–5
2–5
2–6
2–6
2–7
2–8
2–9 iii
3.2.5.3
3.2.5.4
3.2.5.5
3.2.6
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.2.2
3.2.2.1
3.2.2.2
3.2.2.3
3.2.2.4
3.2.3
3.2.3.1
3.2.3.2
3.2.3.3
3.2.4
3.2.4.1
3.2.4.2
3.2.5
3.2.5.1
3.2.5.2
CPU Modes and Process Summaries . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows CPU Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS CPU Modes Summary . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS CPU Modes Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS CPU Process Summary . . . . . . . . . . . . . . . . . . . . . . . .
Memory Summaries and Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Memory Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Memory Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Memory Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS I/O Summaries and Page/Swap Files . . . . . . . . . . . . . . . . .
OpenVMS I/O Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS I/O Page/Swap Files . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Status Summary . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Single Disk Summary . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Volume Summary . . . . . . . . . . . . . . . . . . . . . . . .
Windows Logical Disk Summary . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Physical Disk Summary . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Lock Contention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Single Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Execution Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Job Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Displaying OpenVMS Cluster Data
4.1
4.1.1
4.1.2
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3
4.3.1
4.3.2
4.3.2.1
4.3.2.2
4.3.2.3
4.3.2.4
4.3.2.5
4.3.2.6
4.3.2.7
OpenVMS Cluster Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Cluster Summary Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Cluster Members Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary Data in the Cluster Members Pane . . . . . . . . . . . . . . . . . . . . . .
Port Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCA (System Communications Architecture) Summary Data . . . . . . .
SCS (System Communications Services) Connections Summary Data
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Virtual Circuit Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Detailed Data in the Cluster Members Pane . . . . . . . . . . . . . . . . . . . . . . .
Adapter Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Virtual Circuit Details Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Transmit Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Receive Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Congestion Control Data . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Channel Selection Data (Pre-Version 2.0) . . . . . . . . . . . .
LAN VC Channel Selection Data (Version 2.0 and Later) . . . . . . .
LAN VC Closures Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Packets Discarded Data . . . . . . . . . . . . . . . . . . . . . . . . . .
3–19
3–21
3–21
3–22
3–24
3–24
3–25
3–27
3–28
3–29
3–30
3–10
3–11
3–13
3–13
3–15
3–16
3–16
3–18
3–5
3–5
3–6
3–7
3–8
3–8
3–9
4–8
4–11
4–13
4–16
4–16
4–17
4–18
4–19
4–20
4–21
4–22
4–23
4–24
4–2
4–3
4–3
4–5
4–5
4–6 iv
4.3.3
4.3.3.1
4.3.3.2
4.3.3.3
4.3.3.4
4.3.3.5
4.3.4
4.3.4.1
4.3.4.2
4.3.4.3
4.3.4.4
4.3.4.5
LAN Channel Details Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Overview Data Page . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Counters Data Page . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Errors Data Page . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Remote System Data Page . . . . . . . . . . . . . . . . . . .
LAN Channel ECS (Equivalent Channel Set) Criteria Data
Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapters Detail Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Overview Data Page . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Transmit Data Page . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Receive Data Page . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Events Data Page . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Errors Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 Getting Information About Events
5.1
5.1.1
5.1.2
5.2
5.3
Event Information That Is Displayed in the Event Pane . . . . . . . . . . . . . .
Data in the Event Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Pane Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Criteria for Posting and Displaying an Event . . . . . . . . . . . . . . . . . . . . . .
Displaying Additional Event Information . . . . . . . . . . . . . . . . . . . . . . . . . .
6 Performing Fixes on OpenVMS Nodes
6.3.2.2
6.3.3
6.3.3.1
6.3.3.2
6.3.3.3
6.3.3.4
6.3.3.5
6.3.3.6
6.3.3.7
6.3.3.8
6.3.3.9
6.4
6.4.1
6.4.2
6.1
6.2
6.2.1
6.2.2
6.3
6.3.1
6.3.1.1
6.3.1.2
6.3.1.3
6.3.1.4
6.3.1.5
6.3.2
6.3.2.1
Understanding Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Node Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Crash Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjust Quorum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Process Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Process Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Suspend Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resume Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Memory Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purge Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjust Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Limits Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct I/O Count Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Buffered I/O Count Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AST Queue Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open File Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lock Queue Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timer Queue Entry Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subprocess Creation Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pagefile Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Cluster Interconnect Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Adjust Priority Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Circuit Adjust Priority Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6–14
6–15
6–16
6–17
6–18
6–19
6–20
6–21
6–22
6–23
6–24
6–24
6–25
6–25
6–10
6–11
6–12
6–13
6–13
6–1
6–5
6–5
6–6
6–7
6–7
6–8
6–9
4–25
4–26
4–27
4–28
4–29
4–30
4–32
4–32
4–33
4–34
4–35
4–35
5–2
5–3
5–3
5–3
5–6 v
6.4.3
6.4.3.1
6.4.3.2
6.4.3.3
6.4.3.4
6.4.4
6.4.4.1
6.4.4.2
6.4.4.3
6.4.5
6.4.5.1
6.4.5.2
6.4.5.3
6.4.5.4
LAN Virtual Circuit Summary Fixes . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Maximum Transmit Window Size Fix . . . . . . . . . . . . . . .
LAN VC Maximum Receive Window Size Fix . . . . . . . . . . . . . . . .
LAN VC Checksumming Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Compression Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Path Adjust Priority Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Path Hops Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Path Maximum Packet Size Fix . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Adjust Priority Fix . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Set Maximum Buffer Fix . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Start Adapter Fix . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Stop Adapter Fix . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 Customizing the Availability Manager
7.1
7.2
7.2.1
7.2.2
7.3
7.4
7.4.1
7.4.2
7.4.3
7.4.4
7.4.5
7.4.6
7.4.7
7.5
7.5.1
7.5.2
7.5.2.1
7.5.2.2
7.6
7.6.1
7.6.1.1
7.6.1.2
7.6.2
7.6.2.1
7.6.2.2
7.6.2.3
7.6.3
Specifying Groups or Individual Nodes to Monitor . . . . . . . . . . . . . . . . . . .
Changing the Group Membership of a Node . . . . . . . . . . . . . . . . . . . . . . .
Changing the Group of an OpenVMS Node . . . . . . . . . . . . . . . . . . . . .
Changing the Group of a Windows Node . . . . . . . . . . . . . . . . . . . . . . .
Customizing OpenVMS Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing OpenVMS Data Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS CPU Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Status Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Volume Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS I/O Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Lock Contention Filters . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Memory Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Page/Swap File Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing Events and User Notification of Events . . . . . . . . . . . . . . . . .
Customizing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering a User Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Executing a Procedure on an OpenVMS System . . . . . . . . . . . . . .
Executing a Procedure on a Windows System . . . . . . . . . . . . . . . .
Customizing Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Data Analyzer Passwords . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a Data Analyzer Password for an OpenVMS Data
Collector Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a Data Analyzer Password for a Windows Data
Collector Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Security Triplets on OpenVMS Data Collector Nodes . . . . .
Understanding OpenVMS Security Triplets . . . . . . . . . . . . . . . . . .
How to Change a Security Triplet . . . . . . . . . . . . . . . . . . . . . . . . .
How the Availability Manager Ensures Security . . . . . . . . . . . . . .
Changing a Password on a Windows Data Collector . . . . . . . . . . . . . .
6–32
6–33
6–34
6–34
6–35
6–36
6–37
6–26
6–27
6–28
6–29
6–30
6–31
6–31
7–20
7–21
7–21
7–22
7–22
7–24
7–25
7–7
7–7
7–8
7–10
7–11
7–12
7–13
7–14
7–2
7–4
7–4
7–4
7–5
7–15
7–15
7–16
7–17
7–18
7–19
7–20 vi
A CPU Process States
B Tables of Events
C OpenVMS Events by Type of Data Collected
Index
Figures
3–10
3–11
3–12
3–13
3–14
3–15
3–16
3–17
3–18
3–19
3–20
3–21
3–22
3–23
3–24
2–2
2–3
2–4
2–5
3–1
3–2
3–3
3–4
3–5
3–6
3–7
3–8
3–9
1–1
1–2
1–3
1–4
1–5
1–6
1–7
2–1
Application Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Availability Manager Node Configuration . . . . . . . . . . . . . . . . . . . . . .
Requesting and Receiving Information . . . . . . . . . . . . . . . . . . . . . . . .
Data Collection Customization Page . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Node Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Event Customization Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
Availability Manager Password Matching . . . . . . . . . . . . . . . . . . . . . .
Application Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Group Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Node Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Node Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Collection Customization Page . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Node Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Node Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows CPU Modes Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS CPU Modes Summary Pane . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS CPU Modes Detail Pane . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS CPU Process Summary Pane . . . . . . . . . . . . . . . . . . . . . . .
Windows Memory Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Memory Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Memory Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS I/O Summaries Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS I/O Page/Swap Files Pane . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Single Disk Summary Page . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Volume Summary Page . . . . . . . . . . . . . . . . . . . . . . . .
Windows Logical Disk Summary Page . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Physical Disk Summary Page . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Lock Contention Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Information Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Working Set Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Execution Rates Page . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Quotas Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Wait States Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Job Quotas Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–12
3–14
3–16
3–17
3–19
3–20
3–21
3–22
3–23
3–25
3–26
3–27
3–28
3–29
3–30
3–6
3–7
3–8
3–9
3–10
2–5
2–6
2–7
2–8
3–2
3–2
3–4
3–5
1–2
1–3
1–4
1–5
1–6
1–7
1–9
2–3 vii
viii
6–3
6–4
6–5
6–6
6–7
6–8
6–9
6–10
6–11
6–12
6–13
6–14
6–15
6–16
6–17
5–3
5–4
5–5
6–1
6–2
4–20
4–21
4–22
4–23
4–24
4–25
5–1
5–2
4–11
4–12
4–13
4–14
4–15
4–16
4–17
4–18
4–19
4–1
4–2
4–3
4–4
4–5
4–6
4–7
4–8
4–9
4–10
OpenVMS Cluster Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Cluster Members Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCA Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCS Connections Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Virtual Circuit Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adapter Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Transmit Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Receive Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Congestion Control Data Page . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Channel Selection Data Page (Pre-Version 2.0) . . . . . . . . . . .
LAN VC Channel Selection Data Page (Version 2.0 and Later) . . . . . .
LAN VC Closures Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Packets Discarded Data Page . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Overview Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Counters Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Errors Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Remote System Data Page . . . . . . . . . . . . . . . . . . . . . .
LAN Channel ECS Criteria Data Page . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Overview Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Transmit Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Receive Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Events Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Errors Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Event Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Testing for Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Event Customization Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Data Collection Customization Page . . . . . . . . . . . . . . . . . .
OpenVMS Node Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Crash Node Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjust Quorum Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete Process Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit Image Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Suspend Process Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resume Process Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Priority Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purge Working Set Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjust Working Set Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct I/O Count Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Buffered I/O Count Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AST Queue Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open File Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lock Queue Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timer Queue Entry Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subprocess Creation Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6–7
6–9
6–10
6–11
6–12
6–13
6–14
6–15
6–16
6–17
6–18
6–19
6–20
6–21
6–22
4–31
4–32
4–33
4–34
4–35
4–36
5–1
5–2
5–4
5–5
5–5
6–5
6–6
4–20
4–22
4–23
4–24
4–25
4–26
4–27
4–28
4–30
4–2
4–4
4–5
4–7
4–9
4–12
4–14
4–17
4–18
4–19
Tables
1–1
2–1
3–1
3–2
3–3
3–4
3–5
3–6
3–7
3–8
3–9
3–10
3–11
3–12
4–1
6–28
6–29
6–30
6–31
6–32
7–1
7–2
7–3
7–4
6–18
6–19
6–20
6–21
6–22
6–23
6–24
6–25
6–26
6–27
7–5
7–6
7–7
7–8
7–9
7–10
7–11
7–12
7–13
7–14
I/O Byte Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pagefile Quota Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Adjust Priority Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Circuit Adjust Priority Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Maximum Transmit Window Size Page . . . . . . . . . . . . . . . . .
LAN VC Maximum Receive Window Size Page . . . . . . . . . . . . . . . . . .
LAN VC Checksumming Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Compression Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Path Adjust Priority Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Path Hops Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Path Maximum Packet Size Page . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Adjust Priority Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Set Maximum Buffer Size Page . . . . . . . . . . . . . . . . . . .
LAN Adapter Start Adapter Page . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Stop Adapter Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customize Menu in Application Window . . . . . . . . . . . . . . . . . . . . . . .
Customize Menu in Node Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Group/Node Lists Customization Page . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Data Collection Customization Page . . . . . . . . . . . . . . . . . .
OpenVMS CPU Filters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Status Filters Page . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Disk Volume Filters Page . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS I/O Filters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Lock Contention Filters Page . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Memory Filters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Page/Swap File Filters Page . . . . . . . . . . . . . . . . . . . . . . . .
Event Customization Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Security Customization Page . . . . . . . . . . . . . . . . . . . . . . .
Windows Security Customization Page . . . . . . . . . . . . . . . . . . . . . . . .
6–33
6–34
6–35
6–36
6–37
7–1
7–2
7–3
7–5
6–23
6–24
6–25
6–26
6–27
6–28
6–29
6–30
6–31
6–32
7–8
7–9
7–10
7–11
7–12
7–13
7–14
7–15
7–20
7–21
Data Collection Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Information Displayed in Group Pane . . . . . . . . . . . . . . . . . . . . .
OpenVMS Node Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Node Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Data Page Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Memory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single RAD Data Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Data Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Execution Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Process Job Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary Pane Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–7
2–3
3–2
3–3
3–3
3–12
3–13
3–14
3–25
3–26
3–27
3–28
3–29
3–31
4–3 ix
x
4–12
4–13
4–14
4–15
4–16
4–17
4–18
4–19
4–20
4–2
4–3
4–4
4–5
4–6
4–7
4–8
4–9
4–10
4–11
4–21
4–22
4–23
4–24
4–25
5–1
6–1
6–2
7–1
7–2
7–3
A–1
B–1
B–2
C–1
C–2
Cluster Member Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Port Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCA Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCS Connections Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Virtual Circuit Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adapter Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Transmit Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Receive Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Congestion Control Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Channel Selection Data (Pre-Version 2.0) . . . . . . . . . . . . . . .
Channel Selection Data (Version 2.0 and Later) . . . . . . . . . . . . . . . . .
LAN VC Closures Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN VC Packets Discarded Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Overview Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Counters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Errors Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel Remote System Data . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Channel ECS Criteria Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Overview Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Transmit Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Receive Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Events Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Adapter Errors Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Pane Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing Availability Manager Fixes . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of Problems and Matching Fixes . . . . . . . . . . . . . . . . . . . . .
Data Collection Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Collection Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security Triplet Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPU Process States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Threshold Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Nonthreshold Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–22
4–23
4–24
4–25
4–26
4–27
4–28
4–30
4–31
4–4
4–6
4–7
4–9
4–12
4–15
4–17
4–18
4–20
4–21
4–33
4–34
4–34
4–35
4–36
5–3
6–1
6–3
7–6
7–6
7–25
A–1
B–1
B–12
C–1
C–4
Preface
Intended Audience
This guide is intended for system managers who install and use Compaq
Availability Manager software. It is assumed that the system managers who use this product are familiar with Windows terms and functions.
Note
The term Windows as it is used in this manual refers to either Windows
2000 or Windows XP but not to any other Windows product.
Document Structure
This guide contains the following chapters and appendixes:
• Chapter 1 provides an overview of Availability Manager software, including security features.
• Chapter 2 tells how to start the Availability Manager, use the main
Application window, select a group of nodes and individual nodes, and use online help.
• Chapter 3 tells how to select nodes and display node data; it also explains what that data is.
• Chapter 4 tells how to display OpenVMS Cluster summary and detailed data; it also explains what that data is.
• Chapter 5 tells how to display and interpret events.
• Chapter 6 tells how to take a variety of corrective called fixes, to improve system availability.
• Chapter 7 describes the tasks you can perform to filter, select, and customize the display of data and events.
• Appendix A contains a table of CPU process states, which are referred to in
Section 3.2.2.4 and in Section 3.3.1.
• Appendix B contains a table of OpenVMS and Windows events that can be displayed in the Events pane discussed in Chapter 5.
• Appendix C describes the events that can be signaled for each type of
OpenVMS data that is collected.
xi
Related Documents
The following manuals provide additional information:
• OpenVMS System Manager’s Manual describes tasks for managing an OpenVMS system. It also describes installing a product with the
POLYCENTER Software Installation utility.
• OpenVMS System Management Utilities Reference Manual describes utilities you can use to manage an OpenVMS system.
• OpenVMS Programming Concepts Manual explains OpenVMS lock management concepts.
For additional information about Compaq OpenVMS products and services, access the Compaq website at the following location: http://www.openvms.compaq.com/
Reader’s Comments
Compaq welcomes your comments on this manual. Please send comments to either of the following addresses:
Internet
Compaq Computer Corporation
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698
How to Order Additional Documentation
Visit the following World Wide Web address for information about how to order additional documentation: http://www.openvms.compaq.com/
Conventions
The following conventions are used in this guide:
Ctrl/x
PF1 x
Return
A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.
In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)
In the HTML version of this document, this convention appears as brackets, rather than a box.
xii
. . .
.
.
.
( )
[ ]
|
{ }
bold text
italic text
UPPERCASE TEXT
Monospace text
numbers
A horizontal ellipsis in examples indicates one of the following possibilities:
• Additional optional arguments in a statement have been omitted.
• The preceding item or items can be repeated one or more times.
• Additional parameters, values, or other information can be entered.
A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.
In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items.
Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.
This typeface represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.
Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type).
Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace type indicates code examples and interactive screen displays.
In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.
A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes—binary, octal, or hexadecimal—are explicitly indicated.
xiii
1
Overview
This chapter answers the following questions:
• What is the Availability Manager?
• How does the Availability Manager work?
• How does the Availability Manager identify possible performance problems?
• How does the Availability Manager maintain security?
1.1 What Is the Availability Manager?
The Availability Manager is a system management tool that allows you to monitor, from an OpenVMS or Windows node, one or more OpenVMS nodes on an extended local area network (LAN).
The Availability Manager helps system managers and analysts target a specific node or process for detailed analysis. This tool collects system and process data from multiple OpenVMS nodes simultaneously, analyzes the data, and displays the output using a graphical user interface (GUI).
Features and Benefits
The Availability Manager offers many features that can help system managers improve the availability, accessibility, and performance of OpenVMS nodes and clusters.
Feature
Immediate notification of problems
Centralized management
Intuitive interface
Correction capability
Description
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.
Provides centralized management of remote nodes within an extended local area network (LAN).
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.
Allows real-time intervention, including adjustment of node and process parameters, even when remote nodes are hung.
Overview 1–1
Overview
1.1 What Is the Availability Manager?
Feature
Uses its own protocol
Customization
Description
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.
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.
Makes it easier to monitor multiple OpenVMS nodes.
Scalability
Figure 1–1 is an example of the initial Application window of the Availability
Manager.
Figure 1–1 Application Window
1–2 Overview
The Application window is divided into the following sections:
• In the upper left section of the window is a list of user-defined groups of nodes. You can click either the name of a group or the icon in front of it to select a group.
• In the upper right section is a list of the nodes in the group you selected.
Double-click a node name or the icon in front of it to display more detailed data for that node. You can also double-click data items in each row to display more detailed data about a specific item.
Overview
1.1 What Is the Availability Manager?
• In the lower section events are posted, alerting you to possible problems on your system.
1.2 How Does the Availability Manager Work?
The Availability Manager uses two types of nodes to monitor systems:
• One or more OpenVMS Data Collector nodes, which contain the software that collects data.
• An OpenVMS or a Windows Data Analyzer node, which contains the software that analyzes the collected data.
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
Data Analyzer
Node
~
~
Passwords do not match
D A B C
Data Collector
Node
Data Collector
Node
Data Collector
Node
Data Collector
Node
VM-0092A-AI
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.
Overview 1–3
Overview
1.2 How Does the Availability Manager Work?
Requesting and Receiving Information
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
Data Analyzer Node
GUI
1 4
Driver
Network
2
Driver
3
Data Collector Node
VM-0358A-AI
The following steps correspond to the numbers in Figure 1–3.
!
The GUI communicates users’ requests for data to the driver on the Data
Analyzer node.
"
The Data Analyzer driver sends users’ requests across the network to a driver on a Data Collector node.
#
The Data Collector driver transmits the requested information over the network to the driver on the Data Analyzer node.
$
The Data Analyzer driver passes the requested information to the GUI, which displays the data.
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
1–4 Overview
Overview
1.3 How Does the Availability Manager Identify Performance Problems?
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:
• Collecting and analyzing data
• Posting events
1.3.1 Collecting and Analyzing Data
This section explains how the Availability Manager collects and analyzes data. It also defines terms related to data collection and analysis.
1.3.1.1 Types of Data Collection
You can use the Availability Manager to collect data either as a background activity or as a foreground activity.
• Background data collection
When you enable background collection of a specific type of data on a specific node, the Availability Manager collects that data whether or not any windows are currently displaying data for that node.
To enable background data collection, select the check box for a specific type of data on the Data Collection Customization page (Figure 1–4). Note that if the Customize window applies to all OpenVMS nodes, the data collection properties that you set are for all nodes. If the window applies to a specific node, the properties you set apply only to that node.
Chapter 7 contains instructions for customizing data collection properties.
Figure 1–4 Data Collection Customization Page
Overview 1–5
Overview
1.3 How Does the Availability Manager Identify Performance Problems?
• Foreground data collection
Foreground data collection occurs automatically when you open any data page for a specific node. To open a node data page, double-click a node name in the
Node pane of the Application window (Figure 1–1). The Node Summary page is the first page displayed (by default); Figure 1–5 is an example. At the top of the page are tabs that you can select to display other data pages for that node.
Figure 1–5 Sample Node Summary Page
Foreground data collection for all data types begins automatically when any node data page is displayed. Data collection ends when all node data pages have been closed.
Chapter 3 contains instructions for selecting nodes and displaying node data.
1.3.1.2 Events and Data Collection
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 data collection.
1.3.1.3 Data Collection Intervals
Data collection intervals, which are displayed on the Data Collection customization page (Figure 1–4), specify the frequency of data collection.
Table 1–1 describes these intervals.
1–6 Overview
Overview
1.3 How Does the Availability Manager Identify Performance Problems?
Table 1–1 Data Collection Intervals
Interval (in seconds)
Type of Data
Collection Description
NoEvent
Event
Display
Background
Background
Foreground
How often data is collected if no events have been posted for that type of data.
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.
1.3.2 Posting Events
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
Overview 1–7
Overview
1.3 How Does the Availability Manager Identify Performance Problems?
1.3.2.1 Thresholds and Occurrences
Thresholds and occurrences are criteria that the Availability Manager uses for posting events.
A threshold is a value against which data in a data collection is compared. An
occurrence is a value that represents the number of consecutive data collections that meet or exceed the threshold.
Both thresholds and occurrences are customizable values that you can adjust according to the needs of your system. For details about how to change the values for thresholds and occurrences, see Chapter 7.
Relationship between Thresholds and Occurrences
For a particular event, when the data collected meets or exceeds the threshold, the data collection enters a threshold-exceeded state. When the number of consecutive data collections to enter this state meets or exceeds the value in the
Occurrence box (see Figure 1–6), the Availability Manager displays (posts) the event in the Event pane.
A closer look at Figure 1–6 shows the relationship between thresholds and occurrences. For the
1
Rwait
DSKRWT, high disk device RWAIT count
event, a threshold of process has been set. A value of 2 in the Occurrence box indicates that the number of
Rwait
errors during 2 consecutive data collections must meet or exceed the threshold of 1 for the
DSKRWT, high disk device RWAIT count
event to be posted.
1.4 How Does the Availability Manager Maintain Security?
The Availability Manager uses passwords to maintain security. These passwords have somewhat different appearances on Windows Data Analyzer nodes and on
OpenVMS Data Analyzer and Data Collector nodes. On Windows Data Analyzer nodes, passwords are up to 8 characters long. On OpenVMS Data Analyzer and
Data Collector nodes, passwords are part of a three-part security code called a
security triplet.
The following sections explain these security methods further.
1.4.1 Data Analyzer Password Security
For monitoring to take place, the password on a Data Analyzer node must match the password section of the security triplet on each OpenVMS Data
Collector node. (A Windows Data Analyzer checks only the password part of each OpenVMS Data Collector security triplet. OpenVMS Data Collectors impose other security measures, which are explained in Section 1.4.2.)
Figure 1–7 illustrates how you can use passwords to limit access to node information. The Testing Department’s Data Analyzer, whose password is HOMERUNS, can access only OpenVMS Data Collector nodes with the
HOMERUNS password as part of their security triplets. The same is true of the
Accounting Department Data Analyzer, whose password is BATTERUP; it can access only OpenVMS Data Collector nodes with the BATTERUP password as part of their security triplets.
1–8 Overview
Overview
1.4 How Does the Availability Manager Maintain Security?
Figure 1–7 Availability Manager Password Matching
Testing Department
Password:
Homeruns
Data Analyzer
Accounting Department
Data Analyzer
Password:
Batterup
Test A Test B Acct A Acct B
Data Collector
Password:
Homeruns
Data Collector
Password:
Homeruns
Data Collector
Password:
Batterup
Data Collector
Password:
Batterup
VM-0100A-AI
The Availability Manager sets a default password when you install the Data
Analyzer. To change that password, you must use a customization option that is explained in Chapter 7.
1.4.2 OpenVMS Data Collector Security Features
OpenVMS Data Collector nodes have the following security features:
•
Private LAN transport
The Availability Manager protocol is based on the 802.3 Extended Packet
Format (also known as SNAP). The IEEE Availability Manager protocol values are as follows:
Protocol ID: 08-00-2B-80-48
Multicast Address: 09-00-2B-02-01-09
If you filter protocols for bridges or routers in your network, you need to add these values to your network protocols.
•
Availability Manager data-transfer security
Each OpenVMS node running as a Data Collector has a file containing a list of security triplets. For Data Analyzer and Data Collector nodes to exchange data, the passwords on the nodes must match.
In addition, note the following:
– Data Collector nodes that have read access allow Windows Data Analyzer nodes to view system data.
– Data Collector nodes that have write access also allow a matching
Windows Data Analyzer node to perform fixes or modifications to the running system.
Chapter 7 explains security triplets and how to edit them.
Overview 1–9
Overview
1.4 How Does the Availability Manager Maintain Security?
•
OpenVMS file protection and process privileges
When the Availability Manager is installed, it creates a directory
(SYS$COMMON:[AMDS$AM]) and sets directory and file protections on it so that only the SYSTEM account can read the files in that directory. For additional security on these system-level directories and files, you can create access control lists (ACLs) to restrict and set alarms on write access to the security files.
For more information about creating ACLs, see the OpenVMS Guide to
System Security.
1–10 Overview
2
Getting Started
Notes
Before you start this chapter, be sure to read the explanation of data collection, events, thresholds, and occurrences in Chapter 1.
When this manual does not use the terms Windows 2000 or Windows XP, the term ‘‘Windows’’ refers to both Windows 2000 and XP, but not to any other Windows product.
This chapter provides the following information:
• How to start the Availability Manager Data Collector
• How to start the Availability Manager Data Analyzer
• How to use the main Application window
• How to display basic node data
For information about installing the Availability Manager on OpenVMS or
Windows systems, refer to the appropriate installation instructions. You can access these instructions from the Availability Manager web pages at the following URL: http://www.openvms.compaq.com/openvms/products/availman/
The installation instructions for OpenVMS systems also include an explanation of how to install and use both DECamds and the Availability Manager on the same system.
2.1 Starting the Data Collector
Beginning with OpenVMS Version 7.2, the files needed to run the Data Collector on OpenVMS nodes are shipped with the OpenVMS operating system. However, if you want the latest Data Collector software, you need to install it from the
Availability Manager Version 2.2 kit. Once the Data Collector is running on a node, you can monitor that node using DECamds or the Availability Manager.
To use the Data Collector on a particular node, do either of the following:
• Run the following command procedure:
$ @SYS$STARTUP:AMDS$STARTUP START
• Add the following command to the SYSTARTUP_VMS.COM command file in the SYS$MANAGER directory:
@SYS$STARTUP:AMDS$STARTUP START
Getting Started 2–1
Getting Started
2.2 Starting the Data Analyzer
2.2 Starting the Data Analyzer
This section describes what you need to do after the Availability Manager Data
Analyzer is installed. Starting the Data Analyzer is somewhat different on
OpenVMS and on Windows systems. However, on both systems, starting the Data
Analyzer automatically starts the Java graphical user interface (GUI) that allows you to view information that is collected from the Data Collector nodes.
The following sections contain the sequence of steps required to start the Data
Analyzer on an OpenVMS node and a Windows node.
2.2.1 How to Start the Data Analyzer on an OpenVMS Alpha Node
Make sure the Data Analyzer has been installed on the OpenVMS Alpha node from which you want to monitor other nodes. (Installation instructions are at the web site referred to at the beginning of this chapter.)
To start the Data Analyzer, enter the following command:
$ avail/avail
The Availability Manager then displays the main Application window, which is shown in Figure 2–1.
Refer to the Installation Instructions for qualifiers you can use with the
AVAIL/AVAIL command.
2.2.2 How to Start the Data Analyzer on a Windows Node
Make sure the Data Analyzer has been installed on the Windows node from which you want to monitor other nodes. (Installation instructions are at the web site referred to at the beginning of this chapter.)
Starting the Data Analyzer
To start the Data Analyzer, follow these steps:
1.
Choose the following options beginning with the Windows Start menu:
Start —> Programs
2.
Choose Availability Manager.
3.
Choose Data Analyzer Startup.
The Availability Manager then displays the main Application window, which is shown in Figure 2–1.
2.3 Using the Application Window
Once it starts, the Availability Manager watches for notifications from nodes running the Data Collector. After receiving notification from the Data Collector, the Availability Manager attempts to connect to a node. This is called the
attempting collection phase.
If the node passes the security check while the Availability Manager is attempting the connection, the connection succeeds, and data collection starts. This is called the data collection phase. If the node fails the security check, it is in the
connection failed phase.
While collecting data, if a node goes down, or a network connection fails between the graphical user interface and the node, that node is placed in the path lost phase.
2–2 Getting Started
Getting Started
2.3 Using the Application Window
The Availability Manager notifies you of these phases and other states in the
Application window, which is shown in Figure 2–1.
Figure 2–1 Application Window
The Application window is divided into three segments, or panes:
•
Group pane
The Group pane is at the top left of the window. In this pane, you select the group of nodes that you want to monitor. The first number in parentheses after ‘‘OpenVMS’’ is the number of groups that are listed. The second number is the total number of nodes in the listed groups.
The number in parentheses after each group name is the total number of nodes in the group. Preceding the name of each group, you might see as many as five color-coded columns of numbers.
From left to right, the columns display the number of nodes in the group that are in the states described in Table 2–1.
Table 2–1 Node Information Displayed in Group Pane
Column
Number Color Description
1 Brown Number of nodes for which attempts to configure the node have failed—for example, because the node is in a connection failed phase.
(continued on next page)
Getting Started 2–3
Getting Started
2.3 Using the Application Window
2
3
4
Table 2–1 (Cont.) Node Information Displayed in Group Pane
Column
Number Color Description
5
Yellow
Black
Red
Green
Number of nodes that are in the attempting collection phase.
Number of nodes that are in a path lost phase.
Number of nodes that are in the data collection phase but that have exceeded a threshold, thereby causing an event to be posted.
Number of nodes that are in the data collection phase.
•
Node pane
The Node pane occupies most of the top right of the window. In this pane, the
Availability Manager displays a list of the nodes in the group you select in the Group pane, along with summary data for each node. In Figure 2–1, the
Debug cluster group has been selected. Chapter 3 contains more information about using the Node pane.
Figure 2–1 shows the node information that is displayed when you select a group of OpenVMS nodes. Somewhat different information is displayed for a group of Windows nodes. For more information about this, see Chapter 3.
•
Event pane
The Event pane occupies the entire bottom of the window. In this pane, the Availability Manager displays events that occur on all the nodes being monitored on your system. (Events signal potential problems that might require further investigation.)
An event must reach a certain level of severity to be displayed. You can customize the severity levels at which events are displayed (see Chapter 7).
For more information about displaying events, see Chapter 5.
You can change the size of the panes as well as the width of specific fields in the Application window and also the borders between the fields by clicking on a border and dragging it. Scroll bars indicate whether you are displaying all or part of a screen. For example, clicking a right arrow on a scroll bar allows you to view the rightmost portion of a screen.
2.3.1 Other Window Components
In addition to panes, the Application window also includes the following components (see Figure 2–1):
Title bar
The title bar runs across the top of the window and contains the product name.
Menu bar
The menu bar, immediately below the title bar, contains the following menu options:
•
File
The File menu contains the Exit option, which allows you to stop the Data
Analyzer and close the window.
•
Customize
The Customize menu contains options that allow you to customize various aspects of the Availability Manager. These options are explained in Chapter 7.
2–4 Getting Started
Getting Started
2.3 Using the Application Window
•
Help
The Help menu offers different types of online help for the Availability
Manager. These options are explained in Section 2.5.
Status bar
The status bar runs across the bottom of the window. It displays the name of the selected group and the number of nodes in that group.
2.3.2 Displaying More Information
In the initial Application window (Figure 2–1), which is displayed by default, you can do the following at any time:
• Click a field to select it.
• Double-click most fields to display a page containing information specific to that field.
• Right-click a field to display a popup menu.
2.3.3 Understanding Groups of Nodes
When you start the Availability Manager, the Group pane lists groups of nodes that the Data Analyzer has found. If the Data Analyzer finds Windows nodes, those are also displayed.
To monitor specific nodes, you must select the group in the Group pane that contains those nodes (see Figure 2–2).
Figure 2–2 Group Pane
Groups are set up during installation on Data Collector nodes and are user definable. You might define groups by function, type of hardware, or geographical location.
For example, if you were to set up groups of nodes by geographical location, you might assign nodes A and B to a group called Dallas and nodes C, D, and E to a group called Denver. When you select a group, the Availability Manager displays only the nodes in that group, as shown in the following table:
Group Selected
Dallas
Nodes Displayed
Node A
Node B
Getting Started 2–5
Getting Started
2.3 Using the Application Window
Group Selected
Denver
Nodes Displayed
Node C
Node D
Node E
By default, all nodes are members of one group, DECAMDS, when your system is set up. If you want to change the groups being monitored, you need to to use a customization option to make changes. See Section 7.1 for instructions.
Compaq recommends that you define a cluster as its own group.
2.4 Displaying More Information about Nodes
The Node pane of the Application window allows you to focus on resource usage activity at a high level and to display more specific data whenever you want. This section explains the basic use of the Node pane. For more detailed information, see Chapter 3.
Within the group of nodes you select, the Availability Manager displays all the nodes with which that group can communicate. Figure 2–3 shows a list of
OpenVMS nodes.
Figure 2–3 OpenVMS Node Pane
Each node name has an icon next to it. The color of the icon represents a state similar to those described in Table 2–1:
Color
Brown
Yellow
Black
Red
Green
Description
Attempts to configure the node have failed—for example, because it failed the security check.
Node security check is in progress or has failed.
Path to node has been lost.
Security check was successful. However, a threshold has been exceeded, and an event has been posted.
Security check was successful; data is being collected.
2.4.1 Choosing a Node
To choose a node on a Windows or an OpenVMS system, double-click a node name in the Node pane to highlight the name of the node and display the Node
Summary page (Figure 2–4). Alternatively, you can right-click a node name to display a popup menu. To display the Node Summary page, select the Display... option.
2–6 Getting Started
Getting Started
2.4 Displaying More Information about Nodes
Figure 2–4 OpenVMS Node Summary Page
The data displayed on this page is explained in Chapter 3.
At the top of the Node Summary page are tabs that correspond to most of the types of node data displayed in the Node pane. When you click a tab on the
Node Summary page, the Availability Manager displays most of the same pages that are displayed when you double-click a data item in the Node pane (see
Figure 2–3).
2.4.2 Specifying Data to Collect on OpenVMS Nodes
For OpenVMS nodes, if you want background data collection (and the associated event detection), you must turn on data collection for each type of data you want to collect. On Windows nodes, background data collection is always enabled and cannot be turned off.
To turn on various types of data to be collected, follow these steps:
1.
In the Application window, click the Customize menu.
2.
Click Customize OpenVMS....
3.
Click the Data Collection tab.
The Availability Manager displays the Data Collection Customization page
(Figure 2–5).
Background and foreground collections are explained in Chapter 1.
Getting Started 2–7
Getting Started
2.4 Displaying More Information about Nodes
Figure 2–5 Data Collection Customization Page
The following types of data are collected by default:
• Node summary
• Single disk
• Single process
To stop collecting Node Summary data, for example, clear the check box for ‘‘Node summary’’ in the ‘‘Collect’’ column. You cannot, however, turn off the collection of single disk and single process data. These types of data are collected by default when you open a Single Disk Summary page or a Process Information page, respectively.
To turn on a type of data to be collected, select the check box for that type in the
‘‘Collect’’ column. Table 7–1 identifies the page where each type of data that is collected appears.
On the Data Collection Customization page, you can also change the intervals at which data is collected. Collection intervals are explained in Chapter 7.
2.4.3 Sorting Data
You can sort data in many OpenVMS displays, for example:
• Event pane of the Application window (Figure 1–1)
• CPU Process Summary pane (Figure 3–7)
• Memory page (Figure 3–9)
• Bottom pane of I/O Summaries page (Figure 3–11)
• Disk Status Summary page (Figure 3–13)
• Disk Volume Summary page (Figure 3–15)
2–8 Getting Started
Getting Started
2.4 Displaying More Information about Nodes
Depending on the field, you can sort data alphabetically or numerically. An alphabetical sort is performed using ASCII character values; for example, dollar signs ($) precede letters in the sort order.
To sort the values in a field, double-click the corresponding column heading. To reverse the sort order, double-click the column heading again.
2.5 Getting Help
To obtain online help, click the Help menu on the Application window menu bar.
Then choose one of the following options:
Menu Option
Availability Manager
Help
Getting Started
Availability Manager
Release Notes
About Availability
Manager...
Description
Information about using the Availability Manager.
A special online version of help for getting started using this tool.
Last-minute information about the software and how it works.
Information about this Availability Manager release (such as the version number).
Getting Started 2–9
3
Getting Information About Nodes
Note
Before you start this chapter, be sure to read the explanation of data collection, events, thresholds, and occurrences in Chapter 1. Compaq also recommends completing the getting-started steps described in Chapter 2.
Node summary data is the only data that is collected by default. The Availability
Manager looks for events only in data that is being collected.
You can collect additional data in either of the following ways:
• Opening any display page that contains node-specific data (for example,
CPU, memory, I/O) automatically starts foreground data collection and event analysis except for Lock Contention and Cluster Summary information.
(You must select these tabs individually to start foreground data collection.)
Collection and evaluation continue as long as a page with node-specific data is displayed.
• Clicking a check mark on the Data Collection Customization page (which you can select on the Customize OpenVMS menu) enables background collection of that type of data. Data is collected and events are analyzed continuously until you remove the check mark.
Refer to Chapter 1 and Chapter 7 for details.
This chapter describes the node data that the Availability Manager displays by default and more detailed data that you can choose to display. Differences are noted whenever information displayed for OpenVMS nodes differs from that displayed for Windows nodes.
Although Cluster Summary is one of the tabs displayed on the OpenVMS Node
Summary page (see Figure 3–3), see Chapter 4 for a detailed discussion of
OpenVMS Cluster data.
3.1 Node Panes
After you select a group of nodes in the Group pane, the Availability Manager automatically displays data for each node within that group in the Node pane of the Application window (Figure 3–1).
Getting Information About Nodes 3–1
Getting Information About Nodes
3.1 Node Panes
Figure 3–1 OpenVMS Node Pane
The following sections describe the data displayed for OpenVMS and Windows
Node panes.
3.1.1 OpenVMS Node Pane
Node pane data displayed in red on your screen indicates that the amount is above the threshold set for that field. For each OpenVMS node and group it recognizes, the Availability Manager displays the data described in Table 3–1.
The table also lists the abbreviation of the event that is related to each type of data, where applicable.
Refer to Section 7.5 for information about setting event thresholds. Appendix B describes OpenVMS and Windows events.
Table 3–1 OpenVMS Node Data
Data
Node Name
CPU
MEM
BIO
DIO
CPU Qs
OS Version
Hardware Model
Description of Data
Name of the node being monitored.
Percentage of CPU usage of all processes on the node.
Percentage of space in memory that all processes on the node use.
Buffered I/O rate of processes on the node.
Direct I/O usage of processes on the node.
Number of processes in one of the following states: MWAIT, COLPG, PFW, FPG.
Version of the operating system on the node.
Hardware model of the node.
Related
Event
n/a n/a
LOMEMY
HIBIOR
HIDIOR n/a n/a n/a
3.1.2 Windows Node Pane
Figure 3–2 is an example of a Windows Node pane. From the group you select, the Availability Manager displays all the nodes with which it can communicate.
Figure 3–2 Windows Node Pane
3–2 Getting Information About Nodes
Getting Information About Nodes
3.1 Node Panes
For each Windows node in the group, the Availability Manager displays the data shown in Table 3–2.
Table 3–2 Windows Node Data
Data Description
Node Name
CPU
MEM
DIO
Processes
Threads
Events
Semaphores
Mutexes
Sections
OS Version
HW Model
Name of the node being monitored.
Percentage of CPU usage of all the processes on the node.
Percentage of memory that is in use.
Direct I/O usage of processes on the node.
Number of processes on the node.
Number of threads on the node. A thread is a basic executable entity that can execute instructions in a processor.
The number of events on the node. An event is used when two or more threads want to synchronize execution.
The number of semaphores on the node. Threads use semaphores to control access to data structures that they share with other threads.
The number of mutexes on the node. Threads use mutexes to ensure that only one thread executes a section of code at a time.
The number of sections on the node. A section is a portion of virtual memory created by a process for storing data. A process can share sections with other processes.
Version of the operating system on the node.
Hardware model of the node.
3.2 Node Data Pages
The following sections describe node data pages, which you can display in any of the following ways:
• Double-click a data item in the Node pane to display an associated page.
• Double-click a node name on the Node pane to display the Node Summary page (Figure 3–3). You can then click other tabs on the Node Summary page to display the same detailed data that you display by double-clicking a data item in the Node pane.
• Double-click an event in the Event pane.
The menu bar on each node data page contains the options described in
Table 3–3.
Table 3–3 Node Data Page Menu Bar
Menu Option
File
Description
For More
Information
Contains the Close option, which you can choose to exit from the pages.
n/a
(continued on next page)
Getting Information About Nodes 3–3
Getting Information About Nodes
3.2 Node Data Pages
Table 3–3 (Cont.) Node Data Page Menu Bar
Menu Option
View
Fix
Customize
Description
For More
Information
Contains options that allow you to view data from another perspective.
Contains options that allow you to resolve various resource availability problems and improve system performance.
Contains options that allow you to organize data collection and analysis and to display data by filtering and customizing Availability Manager data.
See specific pages.
Chapter 6
Chapter 7
The following sections describe individual node data pages.
3.2.1 Node Summary
When you double-click a node name, operating system (OS) version, or hardware model in an OpenVMS or Windows Node pane, the Availability Manager displays the Node Summary page (Figure 3–3).
Figure 3–3 Node Summary Page
On this page, the following information is displayed for the node selected:
Data
Model
OS Version
Uptime
Memory
CPUs
Description
System hardware model name.
Name and version of the operating system.
Time (in days, hours, minutes, and seconds) since the last reboot.
Total amount of physical memory (in megabytes) found on the system.
Number of active CPUs on the node.
3–4 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
3.2.2 CPU Modes and Process Summaries
By clicking the CPU tab, you can display CPU panes that contain more detailed statistics about CPU mode usage and process summaries than the Node Summary does. You can use the CPU panes to diagnose issues that CPU-intensive users or CPU bottlenecks might cause. For OpenVMS nodes, you can also display information about specific CPU processes.
When you double-click a value under the CPU or CPU Qs heading on either an OpenVMS or a Windows Node pane, or when you click the CPU tab, the
Availability Manager displays the CPU Modes Summary in the top pane and, by default in the bottom pane, CPU Modes Detail. You can use the View menu to select the CPU Process Summary in the bottom pane (see Section 3.2.2.4).
CPU modes summaries and process summary panes are described in the following sections. Note that there are differences between the pages displayed for
OpenVMS and Windows nodes.
3.2.2.1 Windows CPU Modes
Figure 3–4 contains a sample Windows CPU Modes page.
Figure 3–4 Windows CPU Modes Page
The top pane of the Windows CPU Modes page is a summary of Windows CPU usage, listed by type of mode.
On the left, the following CPU modes are listed:
• User
• Privileged
• Null
On the graph, values that exceed thresholds are displayed in red. To the right of the graph are current and extreme amounts for each mode.
Current and extreme amounts are also displayed for the following values:
• Deferred procedure calls (DPCs) queued per second
Getting Information About Nodes 3–5
Getting Information About Nodes
3.2 Node Data Pages
• Interrupts that occurred per second
The bottom pane of the Windows CPU Modes contains modes details. The following data is displayed:
Data
CPU ID
Mode %
DPCs Queued
DPC Rate
DPC Bypasses
APC Bypasses
Description
Decimal value representing the identity of a processor in a multiprocessing system. On a uniprocessor, this value is always
CPU #00.
Graphical representation of the percentage of active modes on that
CPU. The color displayed matches the mode color on the graph on the top pane.
Rate that deferred procedure call (DPC) objects are queued to this processor’s DPC queue.
Average rate that DPC objects are queued to this processor’s DPC queue per clock tick.
Rate that dispatch interrupts were short-circuited.
Rate that kernel asynchronous procedure call (APC) interrupts were short-circuited.
3.2.2.2 OpenVMS CPU Modes Summary
Figure 3–5 shows a sample OpenVMS CPU Modes summary, which is the top pane of the CPU Modes page.
Figure 3–5 OpenVMS CPU Modes Summary Pane
The CPU Modes summary pane shows OpenVMS CPU usage by mode. On symmetric multiprocessing (SMP) nodes, percentages are averaged across all the
CPUs and are displayed as a single value.
To the left of the graph is a list of CPU modes. The bars in the graph represent the percentage of CPU cycles used for each mode. Values that are lower than the thresholds are displayed in green; values that exceed thresholds are displayed in red. To the right of the graph are current and extreme percentages of time spent in each mode.
3–6 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
Below the graph, the Availability Manager displays the COM and WAIT process queues:
• COM: The value displayed is the number of processes in the COM and COMO states.
• WAIT: The value displayed is the number of processes in the miscellaneous
WAIT, COLPG, CEF, PFW, and FPG states.
See Appendix A for explanations of CPU process states.
3.2.2.3 OpenVMS CPU Modes Detail
The bottom pane of the CPU Modes page contains CPU modes details, as shown in Figure 3–6.
Figure 3–6 OpenVMS CPU Modes Detail Pane
In the OpenVMS CPU Modes Detail pane, the following data is displayed:
Data
CPU ID
State
Mode %
PID
Process Name
Capabilities
RAD
Description
Decimal value representing the identity of a processor in a multiprocessing system. On a uniprocessor, this value is always
CPU #00.
One of the following CPU states: Boot, Booted, Init, Rejected,
Reserved, Run, Stopped, Stopping, or Timeout.
Graphical representation of the percentage of active modes on that
CPU. The color displayed coincides with the mode color in the graph in the top pane.
Process identifier (PID) value of the process that is using the CPU.
If the PID is unknown to the console application, the internal PID
(IPID) is listed.
Name of the process active on the CPU. If no active process is found on the CPU, the name is listed as *** None ***.
One or more of the following CPU capabilities: Primary, Quorum,
Run, or Vector.
Number of the RAD where the CPU exists.
Getting Information About Nodes 3–7
Getting Information About Nodes
3.2 Node Data Pages
3.2.2.4 OpenVMS CPU Process Summary
To display the OpenVMS CPU Process Summary pane at the bottom of the CPU page, select CPU Process Summary from the View menu. Figure 3–7 shows a sample OpenVMS CPU Process Summary pane.
Figure 3–7 OpenVMS CPU Process Summary Pane
The OpenVMS CPU Process Summary pane displays the following data:
Data
PID
Process Name
Priority
State
Rate
Wait
Time
Home RAD
Description
Process identifier, a 32-bit value that uniquely identifies a process.
Name of the process active on the CPU.
Computable (xx) and base (yy) process priority in the format xx/yy.
One of the process states listed in Appendix A.
Percentage of CPU time used by this process. This is the ratio of
CPU time to elapsed time. The CPU rate is also displayed in the bar graph.
Percentage of time the process is in the COM or COMO state.
Amount of actual CPU time charged to the process.
Where most of the resources of the process reside.
Displaying Single Process Information
When you double-click a PID on the lower part of an OpenVMS CPU Process
Summary (Figure 3–7), Memory Summary (Figure 3–9), or I/O Summary
(Figure 3–11) page, the Availability Manager displays the first of several
OpenVMS Single Process pages. On these pages, you can click tabs to display specific data about one process.
This data includes a combination of data elements from the CPU Process,
Memory, and I/O pages, as well as data for specific quota utilization, current image, and queue wait time. These pages are described in more detail in
Section 3.3.
3.2.3 Memory Summaries and Details
The Memory Summary and Memory Details pages contain statistics about memory usage on the node you select. The Memory Summary pages displayed for OpenVMS and Windows nodes are somewhat different, as described in the following sections. The Memory Details page exists only for OpenVMS systems.
3–8 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
3.2.3.1 Windows Memory Summary
You can display the Windows Memory Summary page in either of the following ways:
• Double-click a node, and then click the Memory tab.
• Double-click a value under the MEM heading.
The Availability Manager displays the Windows Memory page (Figure 3–8).
Figure 3–8 Windows Memory Page
The Current and Extreme amounts on the page display the data shown in the following table. The table also indicates what the graph amounts represent.
Data
Available
Cache
Paged Pool
Nonpaged Pool
Description
Size (in bytes) of the virtual memory currently on the zeroed, free, and standby lists. Zeroed and free memory are ready for use, with zeroed memory cleared to zeros. Standby memory is removed from a process’s working set but is still available. The graph shows the percentage of physical memory that is available for use.
Number of bytes currently in use by the system cache. The system cache is used to buffer data retrieved from disk or LAN. The system cache uses memory not in use by active processes on the computer. The graph shows the percentage of physical memory devoted to the cache.
Number of bytes in paged pool, a system memory area where operating system components acquire space as they complete their tasks. Paged pool pages can be paged out to the paging file when the system does not access them for long periods of time. The graph shows the percentage of physical memory devoted to paged pool.
Number of bytes in nonpaged pool, a system memory area where operating system components acquire space as they complete their tasks. Nonpaged pool pages cannot be paged out to the paging file; instead, they remain in memory as long as they are allocated. The graph shows the percentage of physical memory devoted to nonpaged pool.
Getting Information About Nodes 3–9
Getting Information About Nodes
3.2 Node Data Pages
Data
Committed
Bytes
Commit Limit
Description
Amount of available virtual memory (the Commit Limit) that is in use.
Note that the commit limit can change if the paging file is extended.
The graph shows the percentage of the Commit Limit used by the
Committed Bytes.
Size (in bytes) of virtual memory that can be committed without having to extend the paging files. If the paging files can be extended, this limit can be raised.
3.2.3.2 OpenVMS Memory Summary
When you double-click a value under the MEM heading in an OpenVMS Node pane, or if you click the Memory tab, the Availability Manager displays the
OpenVMS Memory Summary page (Figure 3–9).
Alternatively, if you click the View menu on the OpenVMS Memory Summary page, the following options are displayed in a popup menu:
• Memory Summary View
• Memory Details View
You can click Memory Summary View to select the Memory Summary page.
Figure 3–9 OpenVMS Memory Summary Page
The graph in the top pane shows memory distribution (Free, Used, and Modified) as absolute values, in megabytes of memory. Current and extreme values are also listed for each type of memory distribution. (Free memory uses the lowest seen value as its extreme.) Bad Pages show the number of pages that the operating system has marked as bad. The thresholds that you see in the graph are the ones
3–10 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
set for the LOMEMY event. (The LOMEMY thresholds are also in the display of values for the Mem field in the OpenVMS Node pane shown in Figure 3–1.)
The bottom pane displays the following data:
Data
PID
Process Name
Count
Size
Extent
Rate
I/O
Description
Process identifier. A 32-bit value that uniquely identifies a process.
Name of the process.
Number of physical pages or pagelets of memory that the process is using for the working set count.
Number of pages or pagelets of memory the process is allowed to use for the working set size. The operating system periodically adjusts this value based on an analysis of page faults relative to CPU time used.
Number of pages or pagelets of memory in the process’s working set extent (WSEXTENT) quota as defined in the user authorization file
(UAF). Number of pages or pagelets cannot exceed the value of the system parameter WSMAX.
Number of page faults per second for the process.
Rate of I/O read attempts necessary to satisfy page faults (also known as page read I/O or the hard fault rate).
When you double-click a PID on the lower part of the Memory Summary page
(Figure 3–9), the Availability Manager displays an OpenVMS Single Process, where you can click tabs to display pages containing specific data about one process. This data includes a combination of data from the CPU Process, Memory, and I/O pages, as well as data for specific quota utilization, current image, and queue wait time. These pages are described in Section 3.3.
3.2.3.3 OpenVMS Memory Details
When you click the View menu on the OpenVMS Memory Summary page (see
Figure 3–9), the following options are displayed in a popup menu:
• Memory Summary View
• Memory Details View
To display memory details, select that option. The Availability Manager displays the OpenVMS Memory Details page (Figure 3–10).
Getting Information About Nodes 3–11
Getting Information About Nodes
3.2 Node Data Pages
Figure 3–10 OpenVMS Memory Details Page
The following data items are in a box at the top left of the page:
Heading Description
Successful Expansions
Failed Expansions
Number of successful nonpaged pool expansions.
Number of failed attempts to expand nonpaged pool.
System space replication Whether system space replication is enabled or disabled.
To the right of the box is a list of system memory data that is displayed in the bar graphs at the bottom of the page. You can toggle these data items on or off
(that is, to display them or not to display them as bar graphs). You can also click a small box to choose between Linear and Logarithmic bar graph displays.
The system memory data items are described in Table 3–4.
Table 3–4 System Memory Data
Data Description
Total memory Total physical memory size, as seen by OpenVMS.
(continued on next page)
3–12 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
Table 3–4 (Cont.) System Memory Data
Data Description
Available process memory
Free list
Modified list
Resident code region
Reserved page count
Galactic shared used
Galactic shared unused
Global read-only
Total nonpaged pool
Total free nonpaged pool
Amount of total physical memory available to processes.
This is the total memory minus memory allocated to
OpenVMS.
Size of the free page list.
Size of the modified page list.
Size of the resident image code region.
Number of reserved memory pages.
Galaxy shared memory pages currently in use.
Galaxy shared memory pages currently not in use.
Read-only pages, which are installed as resident when system space replication is enabled, that will also be replicated for improved performance.
Total size of system nonpaged pool.
Amount of nonpaged pool that is currently free.
To the right of the system memory data is a list of single RAD data items, which are described in Table 3–5. You can toggle these items to display them or not in bar graphs.
Table 3–5 Single RAD Data Items
Data Description
Free list
Modified list
Nonpaged pool
Free nonpaged pool
Size of the free page list.
Size of the modified page list.
Total size of system nonpaged pool.
Amount of nonpaged pool that is currently free.
Below the list of single RAD items is a box where you can toggle between
Percentage and Raw Data to display Current and Extreme values to the right of the bar graphs.
3.2.4 OpenVMS I/O Summaries and Page/Swap Files
By clicking the I/O tab on any OpenVMS node data page, you can display a page that contains summaries of accumulated I/O rates. In the top pane, the summary covers all processes; in the bottom pane, the summary is for one process.
From the View menu, you can also choose to display (in the bottom pane) a list of page and swap files.
3.2.4.1 OpenVMS I/O Summaries
The OpenVMS I/O Summaries page displays the rate, per second, at which I/O transfers take place, including paging write I/O (WIO), direct I/O (DIO), and buffered I/O (BIO). In the top pane, the summary is for all CPUs; in the bottom pane, the summary is for one process.
Getting Information About Nodes 3–13
Getting Information About Nodes
3.2 Node Data Pages
When you double-click a data item under the DIO or BIO heading on the Node pane, or if you click the I/O tab, the Availability Manager displays, by default, the
OpenVMS I/O Summaries (Figure 3–11).
Figure 3–11 OpenVMS I/O Summaries Page
The graph in the top pane represents the percentage of thresholds for the types of I/O shown in Table 3–6. The table also shows the event that is related to each data item. (Refer to Section 7.5 for information about setting event thresholds.)
Table 3–6 I/O Data Displayed
Type of I/O
Paging Write I/O
Rate
Direct I/O Rate
Buffered I/O Rate
Total Page Faults
Hard Page Faults
System Page Faults
I/O Description
Rate of write I/Os to one or more paging files.
Related
Event
HIPWIO
Transfers are from the pages or pagelets containing the process buffer that the system locks in physical memory to the system devices.
HIDIOR
Transfers are for the process buffer from an intermediate buffer from the system buffer pool.
Total of hard and soft page faults on the system, as well as peak values seen during an Availability
Manager session.
Total of hard page faults on the system.
HIBIOR
HITTLP
HIHRDP
Page faults that are taken from kernel processes.
HISYSP
Current and peak values are listed for each type of I/O. Values that exceed thresholds set by the events indicated in the table are displayed in red on the screen. Appendix B describes OpenVMS and Windows events.
3–14 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
To the right of the graph, the following values are listed:
Value
Threshold
Current
Peak
Description
Defined in Event Properties.
Current value or rate.
Highest value or rate seen since start of data collection.
The bottom pane displays summary accumulated I/O rates on a per-process basis.
The following data is displayed:
Data
PID
Process Name
DIO Rate
BIO Rate
PIO Rate
Open Files
DIO Avail
BIO Avail
BYTLM
Files
Description
Process identifier. A 32-bit value that uniquely identifies a process.
Name of the current process.
Direct I/O rate. The rate at which I/O transfers occur between the system devices and the pages or pagelets that contain the process buffer that the system locks in physical memory.
Buffered I/O rate. The rate at which I/O transfers occur between the process buffer and an intermediate buffer from the system buffer pool.
Paging I/O rate. The rate of read attempts necessary to satisfy page faults (also known as page read I/O or the hard fault rate).
Number of open files.
Direct I/O limit remaining. The number of remaining direct I/O limit operations available before the process reaches its quota. DIOLM quota is the maximum number of direct I/O operations a process can have outstanding at one time.
Buffered I/O limit remaining. The number of remaining buffered I/O operations available before the process reaches its quota. BIOLM quota is the maximum number of buffered I/O operations a process can have outstanding at one time.
The number of buffered I/O bytes available before the process reaches its quota. BYTLM is the maximum number of bytes of nonpaged system dynamic memory that a process can claim at one time.
Open file limit remaining. The number of additional files the process can open before reaching its quota. The FILLM quota is the maximum number of files that can be opened simultaneously by the process, including active network logical links.
When you double-click a PID on the lower part of the I/O Summaries page, the
Availability Manager displays an OpenVMS Single Process, where you can click tabs to display specific data about one process. See Section 3.3 for more details.
3.2.4.2 OpenVMS I/O Page/Swap Files
Click I/O Page/Swap Files on the I/O page View menu to select this option. The
Availability Manager displays an OpenVMS I/O Page/Swap Files page. The top pane displays the same information as that in the OpenVMS I/O Summaries page
(Figure 3–11). The bottom pane contains the I/O Page/Swap Files Pane shown in
Figure 3–12.
Getting Information About Nodes 3–15
Getting Information About Nodes
3.2 Node Data Pages
Figure 3–12 OpenVMS I/O Page/Swap Files Pane
The I/O Page/Swap Files Pane displays the following data:
Data
Host Name
File Name
Used
% Used
Total
Reservable
Description
Name of the node on which the page or swap file resides.
Name of the page or swap file. For secondary page or swap files, the file name is obtained by a special AST to the job controller on the remote node. The Availability Manager makes one attempt to retrieve the file name.
Number of used blocks in the file.
Of the available blocks in each file, the percentage that has been used.
Total number of blocks in the file.
The number of reservable blocks in each page or swap file currently installed. Reservable blocks are blocks that might be logially claimed by a process for future physical allocation. A negative value indicates that the file might be overcommitted. Although a negative value is not an immediate concern, it indicates that the file might become overcommitted if physical memory becomes scarce.
3.2.5 Disk Summaries
The Disk tab allows you to display disk pages that contain data about availability, count, and errors of disk devices on the system. OpenVMS disk data displays differ from those for Windows nodes, as described in the following sections.
On OpenVMS pages, the View menu lets you choose the following disk summaries:
• Status Summary
• Volume Summary
Also, on the Disk Status Summary, you can double-click a device name to display a Single Disk Summary page.
3.2.5.1 OpenVMS Disk Status Summary
To display the default disk page, the OpenVMS Disk Status Summary
(Figure 3–13), click the Disk tab on the OpenVMS Node Summary page. The
Disk Status Summary page displays disk device data, including path, volume name, status, and mount, transaction, error, and resource wait counts.
3–16 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
Figure 3–13 OpenVMS Disk Status Summary
This summary displays the following data:
Heading
Device Name
Host Path
Volume Name
Description
Standard OpenVMS device name that indicates where the device is located, as well as a controller or unit designation.
Primary path (node) from which the device receives commands.
Name of the mounted media.
Getting Information About Nodes 3–17
Getting Information About Nodes
3.2 Node Data Pages
Heading
Status
Error
Trans
Mount
Rwait
Description
One or more of the following disk status values:
Alloc Disk is allocated to a specific user.
CluTran Disk status is uncertain because of a cluster state transition in progress.
Dismount
Foreign
Invalid
MntVerify
Mounted
Disk in process of dismounting; may be waiting for a file to close.
Disk is mounted with the /FOREIGN qualifier.
Disk is in an invalid state (most likely Mount
Verify Timeout).
Disk is waiting for a mount verification.
Disk is logically mounted by a MOUNT command.
Offline
Online
Shadow Set
Member
Disk is no longer physically mounted in device drive.
Disk is physically mounted in device drive.
Disk is a member of a shadow set.
Unavailable
Wrong Volume
Disk is set to unavailable.
Disk was mounted with the wrong volume name.
Wrtlck Disk is mounted and write locked.
Number of errors generated by the disk (a quick indicator of device problems).
Number of in-progress file system operations for the disk.
Number of nodes that have the specified disk mounted.
Indicator that a system I/O operation is stalled, usually during normal recovery from a connection failure or during volume processing of host-based shadowing.
3.2.5.2 OpenVMS Single Disk Summary
To collect single disk data and display the data on the Single Disk Summary, double-click a device name on the Disk Status Summary. Figure 3–14 is an example of a Single Disk Summary page. The display interval of the data collected is 5 seconds.
3–18 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
Figure 3–14 OpenVMS Single Disk Summary Page
This summary displays the following data:
Data
Node
Status
Errors
Trans
Rwait
Free
QLen
OpRate
Description
Name of the node.
Status of the disk: mounted, online, offline, and so on.
Number of errors on the disk.
Number of in-progress file system operations on the disk (number of open files on the volume).
Indication of an I/O stalled on the disk.
Number of free disk blocks on the volume.
Average number of operations in the I/O queue for the volume.
Each node’s contribution to the total operation rate (number of I/Os per second) for the disk.
3.2.5.3 OpenVMS Disk Volume Summary
By using the View option on the Disk Status Summary page (Figure 3–13), you can select the Volume Summary option to display the OpenVMS Disk Volume
Summary (Figure 3–15). This page displays disk volume data, including path, volume name, disk block utilization, queue length, and operation rate.
Getting Information About Nodes 3–19
Getting Information About Nodes
3.2 Node Data Pages
Figure 3–15 OpenVMS Disk Volume Summary Page
This summary displays the following data:
Data
Device Name
Host Path
Volume Name
% Used
Free
Queue
OpRate
Description
Standard OpenVMS device name that indicates where the device is located, as well as a controller or unit designation.
Primary path (node) from which the device receives commands.
Name of the mounted media.
Percentage of the number of volume blocks in use in relation to the total volume blocks available.
Number of blocks of volume space available for new data from the perspective of the node that is mounted.
Average number of I/O operations pending for the volume (an indicator of performance; less than 1.00 is optimal).
Operation rate for the most recent sampling interval. The rate measures the amount of activity on a volume. The optimal load is device specific.
Windows Logical and Physical Disk Summaries
On Windows nodes, the View menu lets you choose the following summaries:
• Logical Disk Summary
• Physical Disk Summary
3–20 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
3.2.5.4 Windows Logical Disk Summary
A logical disk is the user-definable set of partitions under a drive letter. The
Windows Logical Disk Summary displays logical disk device data, including path, label, percentage used, free space, and queue statistics.
To display the Logical Disk Summary page, follow these steps:
1.
Double-click a node name in the Node pane to display the Windows Node
Summary.
2.
Click the Disk tab on the Windows Node Summary.
The Availability Manager displays the Windows Logical Disk Summary page
(Figure 3–16).
Figure 3–16 Windows Logical Disk Summary Page
This summary displays the following data:
Data
Disk
Path
Label
Type
% Used
Free
Current Queue
Average Queue
Transfers/Sec
KBytes/Sec
% Busy
Description
Drive letter, for example, c:, or Total, which is the summation of statistics for all the disks.
Primary path (node) from which the device receives commands.
Identifying label of a volume.
File system type; for example, FAT or NTFS.
Percentage of disk space used.
Amount of free space available on the logical disk unit.
Number of requests outstanding on the disk at the time the performance data is collected. It includes requests in progress at the time of data collection.
Average number of both read and write requests that were queued for the selected disk during the sample interval.
Rate of read and write operations on the disk.
Rate data is transferred to or from the disk during write or read operations. The rate is displayed in kilobytes per second.
Percentage of elapsed time that the selected disk drive is busy servicing read and write requests.
3.2.5.5 Windows Physical Disk Summary
A physical disk is hardware used on your computer system. The Windows
Physical Disk Summary displays disk volume data, including path, label, queue statistics, transfers, and bytes per second.
Getting Information About Nodes 3–21
Getting Information About Nodes
3.2 Node Data Pages
To display the Windows Physical Disk Summary, follow these steps:
1.
Click the View menu on the Windows Logical Disk Summary.
2.
Click the Physical Disk Summary menu option.
The Availability Manager displays the Windows Physical Disk Summary page
(Figure 3–17).
Figure 3–17 Windows Physical Disk Summary Page
This page displays the following data:
Data
Disk
Path
Current Queue
Average Queue
Transfers/Sec
KBytes/Sec
% Busy
% Read Busy
% Write Busy
Description
Drive number, for example, 0, 1, 2 or Total, which is the summation of statistics for all the disks.
Primary path (node) from which the device receives commands.
Number of requests outstanding on the disk at the time the performance data is collected; it includes requests in service at the time of data collection.
Average number of read and write requests that were queued for the selected disk during the sample interval.
Rate of read and write operations on the disk. The rate is displayed in kilobytes per second.
Rate bytes are transferred to or from the disk during read or write operations. The rate is displayed in kilobytes per second.
Percentage of elapsed time the selected disk drive is busy servicing read and write requests.
Percentage of elapsed time the selected disk drive is busy servicing read requests.
Percentage of elapsed time the selected disk drive is busy servicing write requests.
3.2.6 OpenVMS Lock Contention
To display the OpenVMS Lock Contention page, select the Lock Contention tab on the OpenVMS Node Summary page. The Lock Contention page (Figure 3–18) displays each resource in the group you have selected for which a potential lock contention problem exists.
3–22 Getting Information About Nodes
Getting Information About Nodes
3.2 Node Data Pages
Figure 3–18 OpenVMS Lock Contention Page
This page displays the following data:
Data Description
Resource Name
Master Node
Resource name associated with the $ENQ system service call. An ellipsis (...) indicates an unprintable character.
Node on which the resource is mastered.
Parent Resource Name of the parent resource. If no name is displayed, the resource listed is the parent resource.
Duration Amount of time elapsed since the Availability Manager first detected the contention situation.
Status Status of the lock. See the $ENQ(W) description in the OpenVMS
System Services Reference Manual.
When you double-click a data item under these headings, the Availability
Manager displays the following data:
Data
Node
Process Name
LKID
Mode
Duration
Description
Node name on which the lock is granted.
Name of the process owning the blocking lock.
Lock ID value (which is useful with SDA).
One of the following modes at which the lock is granted or requested:
EX, CW, CR, PW, PR, NL.
Length of time the lock has been in the current queue (since the console application found the lock).
Flags specified with the $ENQ(W) request.
Flags
Data is displayed in one of three colors:
Color
Green
Yellow
Pink
Meaning
Granted
Converting
Waiting
To interpret the information displayed on the OpenVMS Lock Contention
Summary, you should understand OpenVMS lock management services. For more information, see the OpenVMS System Services Reference Manual.
Getting Information About Nodes 3–23
Getting Information About Nodes
3.2 Node Data Pages
Note
Lock contention data is accurate only if every node in an OpenVMS
Cluster environment is in the same group. Multiple clusters can share a group, but clusters cannot be divided into different groups without losing accuracy.
The Availability Manager detects the following CPU-related events and displays them in the Event pane:
PRCCOM, node process waiting in COM or COMO
PRCCVR, node process has high CPU rate
PRCMWT, node process waiting in MWAIT
PRCPWT, node process waiting in COLPG, PFW, or FPG
where:
• node is replaced by the name of the node to which the event is related.
• process is replaced by the name of the process to which the event is related.
3.3 OpenVMS Single Process
When you double-click a PID on the lower part of an OpenVMS CPU Process
(Figure 3–7), Memory (Figure 3–9), or I/O (Figure 3–11) page, the Availability
Manager displays the first of several OpenVMS Single Process pages. On these pages, you can click tabs to display specific data about one process. The following sections describe these pages.
Note About ENQ Values on Single Process Pages
In versions of Availability Manager prior to Version 2.0, whenever an ENQ value in the Single Process page was above 32,767, the Availability Manager assigned it a large default value (4,294,967,295, for example) and displayed that large value.
This problem has been corrected so that any value up to 32 bits is displayed correctly.
3.3.1 Single Process Information
To display the Single Process Information page (Figure 3–19), click the Process
Information tab. The data on this page is displayed at the default intervals shown for Single Process Data on the Data Collection Customization page.
3–24 Getting Information About Nodes
Getting Information About Nodes
3.3 OpenVMS Single Process
Figure 3–19 Single Process Information Page
Table 3–7 describes the data in Figure 3–19.
Table 3–7 Single Process Information
Data Description
Process name
Username
Account
UIC
PID
Owner ID
PC
PS
Priority
State
CPU Time
Name of the process.
User name of the user who owns the process.
Account string that the system manager assigns to the user.
User identification code (UIC). A pair of numbers or character strings that designate the group and user.
Process identifier. A 32-bit value that uniquely identifies a process.
Process identifier of the process that created the process displayed on the page. If the PID is 0, then the process is a parent process.
Program counter.
On OpenVMS Alpha systems, this value is displayed as 0 because the data is not readily available to the Data Collector node.
Processor status longword (PSL). This value is displayed on VAX systems only.
Computable and base priority of the process. Priority is an integer between 0 and 31. Processes with higher priority are given more
CPU time.
One of the process states listed in Appendix A.
CPU time used by the process.
3.3.2 Single Process Working Set
To display the Single Process Working Set page (Figure 3–20), click the Working
Set tab.
Getting Information About Nodes 3–25
Getting Information About Nodes
3.3 OpenVMS Single Process
Figure 3–20 Single Process Working Set Page
Table 3–8 describes the data in Figure 3–20.
Table 3–8 Single Process Working Set
Data Description
WS Global Pages
WS Private Pages
WS Total Pages
WS Size
WS Default
WS Quota
Shared data or code between processes, listed in pages (measured in pagelets).
Amount of accessible memory, listed in pages (measured in pagelets).
Sum of global and private pages (measured in pagelets).
Working set size. The number of pages (measured in pagelets) of memory the process is allowed to use. This value is periodically adjusted by the operating system based on analysis of page faults relative to CPU time used. Increases in large units indicates that a process is taking many page faults, and its memory allocation is increasing.
Working set default. The initial limit of the number of physical pages (measured in pagelets) of memory the process can use.
This parameter is listed in the user authorization file (UAF); discrepancies between the UAF value and the displayed value are due to page/longword boundary rounding or other adjustments made by the operating system.
Working set quota. The maximum amount of physical pages
(measured in pagelets) of memory the process can lock into its working set. This parameter is listed in the UAF; discrepancies between the UAF value and the displayed value are due to page/longword boundary rounding or other adjustments made by the operating system.
(continued on next page)
3–26 Getting Information About Nodes
Getting Information About Nodes
3.3 OpenVMS Single Process
Table 3–8 (Cont.) Single Process Working Set
Data Description
WS Extent
Images Activated
Mutexes Held
Working set extent. The maximum number of physical pages
(measured in pagelets) of memory the system will allocate for the process. The system provides memory to a process beyond its quota only when it has an excess of free pages and can be recalled if necessary. This parameter is listed in the UAF; any discrepancies between the UAF value and the displayed value are due to page/longword boundary rounding or other adjustments made by the operating system.
Number of times an image is activated.
Number of mutual exclusions (mutexes) held. Persistent values other than zero (0) require analysis. A mutex is similar to a lock but is restricted to one CPU. When a process holds a mutex, its priority is temporarily increased to 16.
3.3.3 Single Process Execution Rates
To display the Single Process Execution Rates page (Figure 3–21), click the
Execution Rates tab.
Figure 3–21 Single Process Execution Rates Page
Table 3–9 describes the data in Figure 3–21.
Table 3–9 Single Process Execution Rates
Data Description
CPU Percent of CPU time used by this process. The ratio of CPU time to elapsed time.
(continued on next page)
Getting Information About Nodes 3–27
Getting Information About Nodes
3.3 OpenVMS Single Process
Table 3–9 (Cont.) Single Process Execution Rates
Data Description
Direct I/O
Buffered I/O
Paging I/O
Page Faults
Rate at which I/O transfers take place from the pages or pagelets containing the process buffer that the system locks in physical memory to the system devices.
Rate at which I/O transfers take place for the process buffer from an intermediate buffer from the system buffer pool.
Rate of read attempts necessary to satisfy page faults. This is also known as page read I/O or the hard fault rate.
Page faults per second for the process.
3.3.4 Single Process Quotas
To display the Single Process Quotas page (Figure 3–22), click the Process Quotas tab.
Figure 3–22 Single Process Quotas Page
Table 3–10 describes the data displayed in Figure 3–22. When you display the
SWAPPER process, however, no values are listed in this section. The SWAPPER process does not have quotas defined in the same way as other system and user processes do.
Table 3–10 Single Process Quotas
Data Description
Direct I/O
Buffered I/O
The current number of direct I/Os used compared with the limit possible.
The current number of buffered I/Os used compared with the possible limit.
(continued on next page)
3–28 Getting Information About Nodes
Getting Information About Nodes
3.3 OpenVMS Single Process
Table 3–10 (Cont.) Single Process Quotas
Data Description
ASTs
CPU Time
Asynchronous system traps. The current number of ASTs used compared with the possible limit.
Amount of time used compared with the possible limit (in ms). "No
Limit" is displayed if the limit is 0.
3.3.5 Single Process Wait States
To display the Single Process Wait States page (Figure 3–23), click the Wait
States tab.
Figure 3–23 Single Process Wait States Page
Table 3–11 describes the data in Figure 3–23. The wait state specifies why a process cannot execute, based on calculations made on collected data. Each value is calculated over a data collection period of approximately 2 minutes.
‘‘Current’’ refers to the percentage of elapsed time each process spends in one of the computed wait states. If a process spends all its time waiting in one state, the total approaches 100%.
Appendix A contains descriptions of process wait states.
Table 3–11 Single Process Wait States
Data Description
Compute
Memory
Relative value indicating that the process is waiting for CPU time.
Possible states are COM, COMO, or RWCAP.
Relative value indicating that the process is waiting for a page fault that requires data to be read from disk; this is common during image activation. Possible states are PFW, COLPG, FPG, RWPAG, RWNPG,
RWMPE, or RWMPB.
(continued on next page)
Getting Information About Nodes 3–29
Getting Information About Nodes
3.3 OpenVMS Single Process
Table 3–11 (Cont.) Single Process Wait States
Data Description
Direct I/O
Buffered I/O
Control
Quotas
Explicit
Relative value indicating that the process is waiting for data to be read from or written to a disk. The possible state is DIO.
Relative value indicating that the process is waiting for data to be read from or written to a slower device such as a terminal, line printer, or mailbox. The possible state is BIO.
Relative value indicating that the process is waiting for another process to release control of some resource. Possible states are CEF, MWAIT,
LEF, LEFO, RWAST, RWMBX, RWSCS, RWCLU, RWCSV, RWUNK, or
LEF waiting for an ENQ.
Relative value indicating that the process is waiting because the process has exceeded some quota. Possible states are QUOTA or
RWAST_QUOTA.
Relative value indicating that the process is waiting because the process asked to wait, such as a hibernate system service. Possible states are HIB, HIBO, SUSP, SUSPO, or LEF waiting for a TQE.
3.3.6 Single Process Job Quotas
To display the Single Process Job Quotas page (Figure 3–24), click the Job Quotas tab.
Figure 3–24 Single Process Job Quotas Page
Table 3–12 describes the data in Figure 3–24.
3–30 Getting Information About Nodes
Getting Information About Nodes
3.3 OpenVMS Single Process
Table 3–12 Single Process Job Quotas
Data Description
File Count
Page File Count
Enqueue Count
TQE Count
Process Count
Byte Count
Current number of open files compared with the possible limit.
Current number of disk blocks in the page file that the process can use compared with the possible limit.
Current number of resources (lock blocks) queued compared with the possible limit.
Current number of timer queue entry (TQE) requests compared with the possible limit.
Current number of subprocesses created compared with the possible limit.
Current number of bytes used for buffered I/O transfers compared with the possible limit.
Getting Information About Nodes 3–31
4
Displaying OpenVMS Cluster Data
The Availability Manager displays a great deal of OpenVMS Cluster data. The amount of cluster information has increased in each successive version of the product and will probably continue to do so. In order to accommodate future growth in this area, beginning with Availability Manager Version 2.2, OpenVMS
Cluster information is documented in a separate chapter of this manual.
By clicking a series of ‘‘handles’’ on the cluster node tree in the Cluster Members pane of the Cluster Summary page, you can open up lines of data to display progressively more detailed cluster data. This chapter describes the data you can display.
Support for Managed Objects
New support has been added to the OpenVMS Data Collector, RMDRIVER, for OpenVMS managed objects. These are operating system components with characteristics that allow the Availability Manager to manage them. Managed objects, which register themselves with the Data Collector at system startup, not only provide data but also implement fixes in response to client requests.
In OpenVMS Version 7.3 and later, cluster data and fixes are available for LAN virtual circuits through the managed object interface. When the Availability
Manager Version 2.2 Data Analyzer connects to a Data Collector node, it retrieves a list of the managed objects on that node, if any. For such a node, the Availability Manager can provide additional details and new data that would otherwise be unavailable.
Note
To enable managed object data collection on nodes running OpenVMS
Version 7.3 and later, the system manager must take steps so that the
Data Collector driver, RMDRIVER, is loaded early in the boot process.
Refer to the postinstallation steps in the Installation Instructions
for OpenVMS Systems for more details on how to enable collection of managed object data.
LAN Displays
When you monitor OpenVMS Version 7.3 and later nodes with managed objects enabled, additional cluster data and fixes are available for LAN virtual circuits.
This includes enhanced LAN virtual circuit summary data in the Cluster
Summary window and the LAN Virtual Circuit Details (NISCA) window. In addition, the Cluster Summary now includes virtual circuit, channel, and adapter fixes. If managed object support is not enabled for a Data Collector node, then only basic virtual circuit data is available.
Displaying OpenVMS Cluster Data 4–1
Displaying OpenVMS Cluster Data
4.1 OpenVMS Cluster Summary Page
4.1 OpenVMS Cluster Summary Page
To display the OpenVMS Cluster Summary page (Figure 4–1), click the Cluster
Summary tab on an OpenVMS Node Summary page.
The Cluster Summary page contains cluster interconnect information for an entire cluster as well as detailed information about each node in the cluster, including System Communications Services (SCS) circuits and connections for individual nodes. You can also display details about PEdriver LAN virtual circuits.
The data items shown on the page correspond to data that the Show
Cluster utility (SHOW CLUSTER) displays for the SYSTEMS, MEMBERS,
CONNECTIONS, and CIRCUITS classes. No SHOW CLUSTER counterpart exists for the PEdriver LAN virtual circuit, channel, and device detail displays.
The data items shown on the page also correspond to data that the SCACP utility displays for SHOW commands that display PORT, CIRCUIT, VC, CHANNEL, and LAN DEVICE information.
Figure 4–1 OpenVMS Cluster Summary
The two panes in the Cluster Summary page display the following information:
• The Summary pane (top) displays summary information about the entire cluster.
• The Cluster Members pane (bottom) displays detailed information about each node in the cluster, including its System Communication Architecture (SCA) connections with other nodes.
4–2 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.1 OpenVMS Cluster Summary Page
Notes About Pane Displays
Following are notes about the display of data in the panes:
The Availability Manager signals the LOVOTE event when cluster votes minus cluster quorum is less than the threshold value for the event:
LOVOTE, ’node’ VOTES count is close to or below QUORUM
The default threshold for the LOVOTE event is 1.
You can change collection intervals by using the Customize menu on the main
Application window. Choose the Customize OpenVMS... option, and then click the Data Collection tab. On the page displayed, you can select the data that you want to collect and also change default collection intervals.
4.1.1 OpenVMS Cluster Summary Pane
Table 4–1 describes the data in the OpenVMS Cluster Summary pane (see
Figure 4–1).
Table 4–1 Summary Pane Data
Data Description
Formed
Last Trans
Votes
Expected Votes
Failover Step
Members In
Members Out
Quorum
1
QD Votes
Failover ID
Date and time the cluster was formed.
Date and time of the most recent cluster state transition.
Total number of quorum votes being contributed by all cluster members and by the quorum disk.
The expected votes contribution by all members of the cluster. This value is calculated from the maximum EXPECTED_VOTES system parameter and the maximized value of the VOTES system parameter.
Current failover step index. Shows which step in the sequence of failover steps the failover is currently executing.
Number of cluster members to which the Availability Manager has a connection.
Number of cluster members to which the Availability Manager either has no connection or has lost its connection.
Number of votes that must be present for the cluster to function and to permit user activity, that is, to ‘‘maintain cluster quorum.’’
Number of votes given to the quorum disk. A value of 65535 means no quorum disk exists.
Failover instance identification. Unique ID of a failover sequence that indicates to system managers whether a failover has occurred since the last time they checked.
1
You can adjust the quorum value by using the Adjust Quorum fix described in Section 6.2.2.
4.1.2 OpenVMS Cluster Members Pane
The Cluster Members pane (the lower pane on the Cluster Summary page shown in Figure 4–1) lists all the nodes in the cluster and provides detailed information about each one. Figure 4–2 shows only the Cluster Members pane.
Displaying OpenVMS Cluster Data 4–3
Displaying OpenVMS Cluster Data
4.1 OpenVMS Cluster Summary Page
Figure 4–2 OpenVMS Cluster Members Pane
The first level of information in the Cluster Members pane contains cluster member data, which is described in Table 4–2.
Table 4–2 Cluster Member Data
Data Description
SCS Name
SCSID
CSID
Votes
Expect
Quorum
LckDirWt
Status
System Communications Services (SCS) name for the node (system parameter SCSNODE).
SCS identification for the node (system parameter SCSYSTEMID).
Cluster system identification.
Number of votes the member contributes.
Member’s expected votes as set by the EXPECTED_VOTES system parameter.
Number of votes that must be present for the cluster to function and permit user activity, that is, to ‘‘maintain cluster quorum’’.
Lock manager distributed directory weight as determined by the
LCKDIRWT system parameter.
Current cluster member status:
Status Value
NEW
BRK_NEW
MEMBER
BRK_MEM
NON
BRK_NON
REMOVED
BRK_REM
Description
New system in cluster.
New system; there has been a break in the connection.
System is a member of the cluster.
Member; there has been a break in the connection.
System is not a member of the cluster.
Nonmember; there has been a break in the connection.
System has been removed from the cluster.
System has been removed from the cluster, and there has also been a break in the connection.
(continued on next page)
4–4 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.1 OpenVMS Cluster Summary Page
Table 4–2 (Cont.) Cluster Member Data
Data Description
Transition Time The time of the system’s last change in cluster membership status.
4.2 Summary Data in the Cluster Members Pane
The following sections contain descriptions of the categories of summary data displayed in the Cluster Members pane shown in Figure 4–2.
When you click the handle in front of an SCS (System Communications Services)
Name, the Availability Manager first displays a Ports heading, if ports are configured on your system.
A port is an OpenVMS device that provide SCA (System Communications
Architecture) services. Port summary data is discussed in Section 4.2.1. Below the Ports heading is the Circuits heading, which precedes a line of SCA headings.
(SCA data are discussed in Section 4.2.2.)
4.2.1 Port Summary Data
When you initially click the handle in front of Ports in the Cluster Members pane
(Figure 4–1), Ports headings are displayed, with information about port interfaces on the local system, as shown in Figure 4–3.
Figure 4–3 Port Summary Data
Displaying OpenVMS Cluster Data 4–5
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
The port summary data shown in Figure 4–3 is described in Table 4–3. Data items in this table are related to the SCACP utility SHOW PORTS display and the SHOW CLUSTER utility LOCAL_PORT CLASS display.
Table 4–3 Local Port Data
Data Description
Local Port:
Name
Number
Mgmt Priority
Load Class
Device name of the port.
The local port’s interconnect address or other interconnect-specific identifier.
Management priority assigned to the port.
Hard-coded capacity value of the port, based on the rate (in megabits/second) of the interconnect of the port.
Messages Sent:
Count
Rate
Messages Received:
Count
Rate
Datagrams Sent:
Count
Rate
Datagrams
Received:
Count
Rate
Kilobytes Mapped
Total number of messages sent since the port was initialized.
Rate at which messages are sent (per second).
Total number of messages sent since the port was initialized.
Rate at which SCS messages are received (per second).
Total number of SCS datagrams sent since the port was initialized.
Rate at which SCS datagrams are sent (per second).
Total number of SCS datagrams sent since the port was initialized.
Rate at which SCS datagrams are sent (per second).
Number of kilobytes mapped for block transfer.
4.2.2 SCA (System Communications Architecture) Summary Data
Below the heading Circuits in Figure 4–4 is a line of SCA summary headings that include information about a node’s SCS circuits between local SCA ports and remote SCA ports on other nodes in the cluster. More than one circuit indicates more than one communications path to the other node.
The data displayed in Figure 4–4 is similar to the information that the Show
Cluster utility (SHOW CLUSTER) displays for the CIRCUITS, CONNECTIONS, and COUNTERS classes and that the SCACP utility’s SHOW CIRCUITS command displays. Note that circuit count is the total number of events since the the state of the circuit changed to OPEN.
Starting with Availability Manager Version 2.2, the circuits display shows circuits to non-OpenVMS nodes, such as storage controllers.
4–6 Displaying OpenVMS Cluster Data
Figure 4–4 SCA Summary Data
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Table 4–4 describes the SCA summary data displayed in Figure 4–4. Each line of data shows either a summary of an SCS connection between a local system connection of an application (or SYSAP) to a remote SYSAP that uses the circuit, or a summary of interconnect-specific information about the operation of the circuit.
Some of the data described in Table 4–4 is not displayed in Figure 4–4 because the screen display is wider than the page. You can scroll to the right on your terminal screen to display the remaining fields described in the table.
Note
Each rate referred to in Figure 4–4 is in messages per second. The
‘‘Message Rates’’ data are rates; the remaining data items are counts.
Table 4–4 SCA Summary Data
Data Description
Remote Node
Local Port
SCS name of the remote node containing the remote port of the circuit.
The device name of the local port associated with the circuit.
(continued on next page)
Displaying OpenVMS Cluster Data 4–7
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Table 4–4 (Cont.) SCA Summary Data
Remote Port:
Type The remote port’s device or interconnect type associated with the circuit (for example, LAN, CIPCA, DSSI).
Number
State
Priority:
The remote port’s interconnect address, or another other interconnect-specific unique identifier.
The state of the virtual circuit connection.
Curr
Mgmt
Load Class
Circuit’s current priority, which is the sum of the management priorities assigned to the circuit and associated local port.
Priority value assigned to the circuit by management action.
The circuit’s current capacity rating, derived from the current
ECS member’s load class values.
Message Rates:
Sent
Received
Block Data
(Kilobytes):
Mapped
Count/rate of SCS messages sent over the circuit.
Count/rate that SCS messages are received on the circuit.
Sent
Requested
Count/rate of kilobytes mapped for block data transfers over the circuit.
Count/rate of kilobytes sent over the circuit using transfers.
Count/rate of kilobytes requested from the remote port over the circuit using request block data transfers.
Block Data (Count):
Sent
Requested
Datagrams:
Sent
Received
Credit Wait
Buff Desc Wait
Count/rate of send block data transfers over the circuit.
Count/rate of block data transfer requests sent over the circuit.
Count/rate of SCS datagrams sent over the circuit.
Count/rate of SCS datagrams received on the circuit.
Count/rate any connection on the circuit had to wait for a send credit.
Count/rate any connection over the circuit had to wait for a buffer descriptor.
4.2.3 SCS (System Communications Services) Connections Summary Data
You can click the handle at the beginning of a Virtual Circuit Data (green) row to display the following headings, when they apply to a particular node:
• SCS Connections
• LAN Virtual Circuit Summary
To display SCS connections summary data, click the handle at the beginning of the SCS Connections data row on the Cluster Summary pane shown in
Figure 4–1. Figure 4–5 displays SCS Connections Data information.
4–8 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Figure 4–5 SCS Connections Data
Table 4–5 describes the SCS connections data shown in Figure 4–5. Some of the data described in Table 4–5 is not displayed in Figure 4–5 because the screen display is wider than the page. You can scroll to the right on your terminal screen to display the remaining fields described in the table.
Note that connection count is the total number of events since the state of the connection changed to OPEN.
Table 4–5 SCS Connections Data
Data Description
SYSAPs:
Local
Remote
Name of the SYSAP (system application) on the local system associated with the connection.
Name of the SYSAP on the remote system associated with the connection.
(continued on next page)
Displaying OpenVMS Cluster Data 4–9
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Table 4–5 (Cont.) SCS Connections Data
Data Description
State The connection’s current state. The possible displays are:
• ACCP_SENT—An accept request has been sent.
• CLOSED—The connection is closed.
• CON_ACK—A connect request has been sent and acknowledged.
• CON_REC— A connect request has been received.
• CON_SENT— A connect request has been sent.
• DISC_ACK—A disconnect is acknowledged.
• DISC_MTCH—A disconnect request has matched.
• DISC_REC— A disconnect request has been received.
• DISC_SENT—A disconnect request has been sent.
• LISTEN— The connection is in the listen state.
• OPEN—The connection is open.
• REJ_SENT— A rejection has been sent.
• VC_FAI—The virtual circuit has failed.
Message Rates:
Sent
Received
Count/rate that SCS messages are sent over the connection.
Count/rate that SCS messages are being received on the connection.
Block Data
(Kilobytes):
Mapped
Sent
Requested
Count/rate of kilobytes mapped for block data transfers by the local SYSAP using the connection. Note: This field is available only in raw data format.
Number of kilobytes sent over the SCS connection by the local
SYSAP using send block data transfers.
Number of kilobytes requested over the SCS connection by the local SYSAP using request block data transfers.
Block Data (Number):
Sent
Requested
Count/Rate of send block data transfers by this node over the
SCS connection.
Count/Rate of request block data transfers sent to the remote port over the SCS connection.
Datagrams:
Sent
Received
Credit Wait
Count/Rate of datagrams sent on the SCS connection.
Count/Rate of datagrams received on the SCS connection.
Count/Rate of times the connection had to wait for a send credit.
(continued on next page)
4–10 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Table 4–5 (Cont.) SCS Connections Data
Data Description
Buff Desc Wait Count/Rate of times the connection had to wait for a buffer descriptor.
4.2.4 LAN Virtual Circuit Summary Data
You can display interconnect-specific virtual circuit summary data by clicking the handle at the beginning of a Virtual Circuit Summary (black) data row. The screen expands to display the interconnect-specific VC summary data shown in
Figure 4–6.
Much of the data in this display corresponds to the information displayed by the
SCACP command SHOW VC. The SHOW CLUSTER command does not provide a corresponding display. Which data items are displayed depends on the type of interconnect the virtual circuit is using. Currently, this feature is available only for LAN virtual circuits. VC Summary displays for other cluster interconnects such as CI might be available in the future. When other interconnects are supported, the interconnect type will be displayed at the beginning of the line— for example, CI Virtual Circuit Summary—and the associated heading will have interconnect-specific data items.
Note that LAN Virtual Circuit counters are initialized when PEDRIVER detects the existence of a PEDRIVER on a remote system. All of a LAN VC’s counters are cumulative from that time.
Some of the data described in Table 4–6 is not displayed in Figure 4–6 because the screen display is wider than the page. You can scroll to the right on your terminal screen to display the remaining fields described in the table.
Displaying OpenVMS Cluster Data 4–11
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Figure 4–6 LAN Virtual Circuit Summary Data
Table 4–6 describes the LAN virtual circuit summary data shown in Figure 4–6.
Table 4–6 LAN Virtual Circuit Summary Data
Data Description
VC State Current internal state of the virtual circuit:
• OPEN—Virtual Circuit is open and usable.
• PATH—At least one open channel has been established, but the
Virtual Circuit has not yet transitioned to OPEN.
• CLOSED—The Virtual Circuit has been closed or has become unusable.
Total Errors
ReXmt Ratio
Number of times the virtual circuit has been closed or has had other errors.
Ratio of total numbers of transmitted to retransmitted packets during the most recent data collection interval.
Channels:
Open Number of currently open channels available to the virtual circuit.
(continued on next page)
4–12 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Table 4–6 (Cont.) LAN Virtual Circuit Summary Data
Data Description
ECS
MaxPktSiz
ECS Priority
Number of equivalent channel set (ECS) channels currently in use by the LAN virtual circuit.
Maximum data buffer size in use by this LAN virtual circuit.
Priority a channel must have in order to be included in the
Equivalent channel set (ECS). It is the highest priority any open and tight channel has.
ReXmt TMO (µsec) Retransmission timeout, in microseconds. The length of time the virtual circuit is currently using to wait for an acknowledgment of the receipt of a packet before retransmitting that packet.
XmtWindow:
Cur Current value of the transmit window (or pipe quota). Maximum number of packets that are sent before stopping to await an acknowledgment. After a timeout, the transmit window is reset to 1 to decrease congestion; it is allowed to increase as acknowledgments are received.
Max
Options
Maximum transmit window size currently allowed for the virtual circuit.
Virtual circuit options enabled:
CKSUM—packet checksumming
CMPR—compression
Packets:
Sent
Received
Most recent:
Number of packets sent over this virtual circuit.
Number of packets received over this virtual circuit.
Time Opened Most recent time the virtual circuit was opened.
Time Closed Most recent time the virtual circuit was closed.
4.2.5 LAN Channel Summary Data
A LAN path or channel is a logical communication path between two LAN adapters. Channels between nodes are determined by a local adapter, a remote adapter, and the connecting network. For example, two nodes, each having two adapters, might establish four channels between the nodes. The packets that a particular LAN virtual circuit carries can be sent over any open channel connecting the two nodes.
The difference between channels and virtual circuits is that channels provide datagram service. Virtual circuits, layered on channels, provide error-free paths between nodes. Multiple channels can exist between nodes in an OpenVMS
Cluster system, but only one LAN-based virtual circuit can exist between any two nodes at a time.
LAN channel counters are initialized when PEdriver detects the existence of a
LAN device on a remote system. All of a LAN channel counters are cumulative from that time. For more information about channels and virtual circuits, refer to the OpenVMS Cluster Systems manual.
Displaying OpenVMS Cluster Data 4–13
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Displaying Data
You can display LAN channel summary data by clicking the handle in front of the data item OPEN, PATH, or CLOSED under ‘‘VC State’’ for LAN virtual circuit summary data (see Figure 4–6), or by right-clicking a data item and choosing the
Channel Summary item from the popup menu. The screen expands to display the
LAN channel summary data shown in Figure 4–7.
The data items displayed depend on the type of virtual circuit. Currently, this feature is available only for LAN virtual circuits.
Figure 4–7 LAN Channel Summary Data
Some of the data described in Table 4–7 is not displayed in Figure 4–7 because the screen display is wider than the page. You can scroll to the right on your terminal screen to display the remaining fields described in the table.
4–14 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Table 4–7 LAN Channel Data
Data Description
Devices:
Local
Remote
Channel State
Local LAN device associated with the channel.
Remote LAN device associated with the channel.
One of the following states:
• OPEN—Channel is usable.
• PATH—Channel handshake has been completed and, if usable, will transition to
OPEN.
• CLOSED—Channel has been shut down or is unusable.
Total Errors
ECS State
Total of various error counters for this channel (see channel details for breakdown).
Channel ECS membership information:
• Y—Member
• N—Nonmember
Losses—one of the following:
• T (tight)—Packet loss history is acceptable.
• L (lossy)—Recent history of packet losses makes channel unusable.
Capacity—one of the following:
• P (peer)—Priority and Buffer size both match the highest corresponding values of the set of tight channels, entitling the channel to be an ECS member.
• I (inferior)—Priority or buffer size does not match the corresponding values of the set of tight channels.
• S (superior)—Priority or buffer size is better than those of the current corresponding values of the set ECS member channels. This is a short-lived, transient state because it exists only while the ECS membership criteria are being re-evaluated.
• U (unevaluated)—Priority or buffer size, or both, have not been evaluated against the ECS criteria, usually because the channel is lossy.
Speed—one of the following:
• F (fast)—Channel delay is among the best for tight and peer channels.
• S (slow)—Channel delay makes channel too slow to be usable because it would limit the virtual circuit’s average delay.
Note: If a channel is lossy, its capacity and speed are not always kept current.
Therefore, displayed values might be those that the channel had at the time it become lossy.
(continued on next page)
Displaying OpenVMS Cluster Data 4–15
Displaying OpenVMS Cluster Data
4.2 Summary Data in the Cluster Members Pane
Table 4–7 (Cont.) LAN Channel Data
Data Description
Priority:
Chan
Hops
Mgmt
BufSiz
Current priority used to evaluate the channel for ECS membership. This is the sum of management priority values assigned to the LAN device.
Dynamic management-assigned priority.
Number of switches or bridges in this channel’s network path to the remote LAN device.
Current maximum amount of SCS data that can be contained in a packet sent over the channel. It is the smallest of the following values:
• Local LAN device buffer sizes
• Remote LAN device buffer sizes
• Local NISCS_MAX_PKTSZ system (SYSGEN) parameter values
• Remote NISCS_MAX_PKTSZ system (SYSGEN) parameter values
• Largest packet size determined by the NISCA Channel Packet Size probing algorithm that the intervening network can deliver
Delay (µsec) Running average of measured round-trip time, in microseconds, for packets sent over the channel.
Load class initialized from local and remote LAN device bit rates.
Load Class
Packets:
Sent Number of packets sent on this channel, including control packets.
Received
Most recent:
Number of packets received by this channel.
Time Opened Last time this channel had a verified usable path to a remote system.
Time Closed Time that this channel was last closed.
4.3 Detailed Data in the Cluster Members Pane
The following sections describe detailed data that appears on lines that you can open in the Cluster Members Pane shown in Figure 4–1.
4.3.1 Adapter Data
You can display adapter data by first right-clicking a node name on the Cluster
Members pane shown in Figure 4–1. On Version 7.3 or later nodes on which managed objects are enabled, the Availability Manager displays a menu with the following choices:
• SCA Summary
• Adapter Summary
• Fix node-name
Click Adapter Summary... to display the Adapter Summary Data page shown in
Figure 4–8.
4–16 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–8 Adapter Summary Data
Table 4–8 describes the adapter summary data displayed in Figure 4–8. This data is also displayed with SCACP command SHOW LAN_DEVICE.
Table 4–8 Adapter Summary Data
Data Description
Adapter
Type
Errors
Name of the LAN device used for cluster communications between local and remote nodes.
Type of LAN adapter used for the cluster.
Number of errors reported by the adapter since cluster communications began using it.
Management:
Priority
BufSize
BufSize
Adapter’s current management-assigned priority.
Adapter’s current management-assigned maximum buffer size.
Smaller of adapter’s interconnect specific buffer size and its current management-assigned buffer size.
Messages:
Sent
Received
Number of LAN packets sent by the adapter.
Number of packets received from remote LAN adapters.
4.3.2 LAN Virtual Circuit Details Data
The Network Interconnect for System Communications Architecture (NISCA) is the transport protocol responsible for carrying packets such as disk I/Os and lock packets across Ethernet and FDDI LANs to other nodes in the cluster.
The LAN virtual circuit details (NISCA) pages show detailed information about the LAN Ethernet or FDDI connection between two nodes. The Availability
Manager displays one window for each LAN virtual circuit. This page is intended primarily to provide real-time aids for diagnosing LAN-related cluster communications problems. OpenVMS Cluster Systems describes the parameters shown on these pages and tells how to diagnose LAN-related cluster problems.
Displaying OpenVMS Cluster Data 4–17
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
The LAN Virtual Circuit Details pages provide the same information as the
SCACP command SHOW VC and as the following OpenVMS System Dump
Analyzer (SDA) commands: PE VC and SHOW PORTS/VC=VC_ remote-node-
name. In these commands, remote-node-name is the SCS name of another node in the cluster.
SDA defines VC_remote-node-name and performs the first SHOW PORTS action after SDA is started. Thus, the /CH and /VC options are valid only with the second and subsequent SHOW PORT commands.
You can display LAN virtual circuit details data by double-clicking OPEN or
CLOSED under ‘‘VC State’’ for LAN Virtual Circuit Summary on the Cluster
Summary page (see Figure 4–7). After a brief delay, a LAN VC Transmit Data page (shown in Figure 4–9) is displayed. The tabs at the top of the page indicate additional pages that you can display.
The data items displayed depend on the type of virtual circuit. Currently, this feature is available only for LAN virtual circuits.
4.3.2.1 LAN VC Transmit Data
Transmit data is information about data packet transmission. Figure 4–9 is an example of a LAN VC Transmit Data page.
Figure 4–9 LAN VC Transmit Data Page
Table 4–9 describes the data displayed in Figure 4–9.
Table 4–9 LAN VC Transmit Data
Data Description
Packets Sent (Raw) count and rate of packets transmitted through the virtual circuit to the remote node, including both sequenced and unsequenced (channel control) packets and lone acknowledgments.
(continued on next page)
4–18 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–9 (Cont.) LAN VC Transmit Data
Data Description
Bytes Sent
Unsequenced (DG)
Sequenced
ReXMT Ratio
Lone ACK
ReXMT Count
ReXMT Timeout
(Raw) count and rate of bytes transmitted through the virtual circuit.
(Raw) count and rate of the number of unsequenced packets that are transmitted.
(Raw) count and rate of sequenced packets transmitted.
Sequenced packets are guaranteed to be delivered.
Ratio of the total number of sequenced packets sent to the current retransmission count.
(Raw) count and rate of packets sent solely for the purpose of acknowledging receipt of one or more packets.
Number of packets retransmitted. Retransmission occurs when the local node does not receive an acknowledgment for a transmitted packet within a predetermined timeout interval.
Number of retransmission timeouts that have occurred.
4.3.2.2 LAN VC Receive Data
Receive data is information about the receipt of data packets. Figure 4–10 is an example of a LAN VC Receive Data page.
Figure 4–10 LAN VC Receive Data Page
Displaying OpenVMS Cluster Data 4–19
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–10 describes the data displayed in Figure 4–10.
Table 4–10 LAN VC Receive Data
Data Description
Packets Received
Bytes Received
Unsequenced (DG)
Sequenced
Lone ACK
Duplicate
Out of Order
Illegal ACK
(Raw) count and rate of packets received on the virtual circuit from the remote node, including both sequenced and unsequenced—that is, datagram packets and lone acknowledgments.
(Raw) count and rate of bytes received in packets over the virtual circuit.
(Raw) count and rate of unsequenced—datagram—packets received.
(Raw) count and rate of sequenced packets received.
(Raw) count and rate of lone acknowledgments received.
Number of duplicated packets received by this system.
Duplicates occur when the sending node retransmits a packet, and both the original and the retransmitted packets are received.
Number of packets received out of order by this system.
Number of illegal acknowledgments received—that is, acknowledgments of an out-of-range sequence number.
4.3.2.3 LAN VC Congestion Control Data
LAN VC congestion control data is information about LAN traffic. The values indicate the number of packets that can be sent to the remote node before receiving an acknowledgment and the retransmission timeout.
Figure 4–11 is an example of a LAN VC Congestion Control Data page.
Figure 4–11 LAN VC Congestion Control Data Page
4–20 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–11 describes the data displayed in Figure 4–11.
Table 4–11 LAN VC Congestion Control Data
Data Description
Transmit Window Current Current value of the transmit window (or pipe quota). After a timeout, the pipe quota is reset to 1 to decrease network path congestion. The pipe quota is allowed to increase as quickly as acknowledgments are received.
Transmit Window Grow
Transmit Window Max
Transmit Window Max
(mgmt)
Transmit Window
Reached
The slow growth threshold. The size at which the increase rate of the window is slowed to avoid congestion on the network again.
Maximum transmit window size currently allowed for the virtual circuit based on channel and remote PEdriver receive cache limitations.
Management override to calculated value for Maximum
Transmit Window size. N/A on systems prior to Version 2.0.
Roundtrip Time
Roundtrip Deviation
Retransmit Timeout
Number of times the entire transmit window was full. If this number is small compared with the number of sequenced packets transmitted, then either the local node is not sending large bursts of data to the remote node, or acknowledging packets are being received so promptly that the window limit is never reached.
Average round-trip time, in microseconds, for a packet to be sent and acknowledged.
Average deviation, in microseconds, of the round-trip time.
UnAcked Packets
CMD Queue Length
Value, in microseconds, used to determine packet retransmission timeout. If a packet does not receive either an acknowledging or a responding packet, the packet is assumed to be lost and will be resent.
Current number of unacknowledged packets.
Current length of the virtual circuit’s command queue.
CMD Queue Max Maximum number of commands in the virtual circuit’s command queue so far.
4.3.2.4 LAN VC Channel Selection Data (Pre-Version 2.0)
Systems running versions prior to Version 2.0 Availability Manager software collect and display information about LAN VC channel selection, but this information does not include managed objects, which were implemented beginning with Version 2.0 (Refer to the introduction to this chapter for more information about managed objects.)
Figure 4–12 is an example of a pre-Version 2.0 LAN VC Channel Selection Data page.
Displaying OpenVMS Cluster Data 4–21
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–12 LAN VC Channel Selection Data Page (Pre-Version 2.0)
Table 4–12 describes the data displayed in Figure 4–12.
Table 4–12 LAN VC Channel Selection Data (Pre-Version 2.0)
Data Description
Buffer Size
Channel Count
Channel Selections
Protocol
Local Device
Local LAN Address
Remote Device
Remote LAN Address
Maximum data buffer size for this virtual circuit.
Number of channels available for use by this virtual circuit.
Number of channel selections performed.
NISCA protocol version.
Name of the local LAN device that the channel uses to send and receive packets.
Address of the local LAN device that performs sends and receives.
Name of the remote LAN device that the channel uses to send and receive packets.
Address of the remote LAN device performing the sends and receives.
4.3.2.5 LAN VC Channel Selection Data (Version 2.0 and Later)
Systems running Availability Manager Version 2.0 or later collect and display the following information about LAN VC Channel Selection. This information includes managed objects, which were implemented beginning with Version 2.0
(Refer to the introduction to this chapter for more information about managed objects.)
Note
An additional requirement for displaying this data page is that managed objects be enabled on your system. Refer to postinstallation tasks described in the Installation Guide for OpenVMS Systems.
4–22 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–13 is an example of a Channel Selection Data page on a Version 2.0 or later system.
Figure 4–13 LAN VC Channel Selection Data Page (Version 2.0 and Later)
Table 4–13 describes the data displayed in Figure 4–13.
Table 4–13 Channel Selection Data (Version 2.0 and Later)
Data Description
ECS Priority
Buffer Size
Hops
Channel Count
Channel Selections
Protocol
Speed Demote
Threshold
Speed Promote
Threshold
Min RTT
Min RTT Threshold
Current minimum priority a tight channel must have in order to be an ECS member.
Maximum data buffer size for this virtual circuit. A channel must have this buffer size in order to be an ECS member.
Current minimum management hops a channel must have in order to be included in the ECS.
Number of channels currently available for use by this virtual circuit.
Number of channel selections performed.
Remote node’s NISCA protocol version.
Current threshold for reclassifying a FAST channel to SLOW.
Current threshold for reclassifying a SLOW channel to FAST.
Current minimum average delay of any current ECS members.
Current threshold for reclassifying a channel as FASTER than the current set of ECS channels.
4.3.2.6 LAN VC Closures Data
LAN VC closures data is information about the number of times a virtual circuit has closed for a particular reason. Figure 4–14 is an example of a LAN VC
Closures Data page.
Displaying OpenVMS Cluster Data 4–23
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–14 LAN VC Closures Data Page
Table 4–14 describes the data displayed in Figure 4–14.
Table 4–14 LAN VC Closures Data
Data Description
No Path
SeqPkt TMO
Topology Change
CC DFQ Empty
LAN XmtTMO
NPAGEDYN Low
Number of times the virtual circuit was closed because no usable
LAN path was available. N/A on systems prior to Version 2.0.
Number of times the VC was closed because a sequenced packet’s retransmit timeout count limit was exceeded.
Number of times the VC was closed because PEdriver performed a failover from a LAN path (or paths) with a large packet size to a LAN path with a smaller packet size.
Number of times the VC was closed because the channel control data-free queue (DFQ) was empty.
Number of times the VC was closed because a sequenced packet was not transmitted by the LAN device within an acceptable amount of time.
Number of times the virtual circuit was lost because of a nonpaged pool allocation failure in the local node.
4.3.2.7 LAN VC Packets Discarded Data
LAN VC packets discarded data is information about the number of times packets were discarded for a particular reason. Figure 4–15 is an example of a LAN VC
Packets Discarded Data page.
4–24 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–15 LAN VC Packets Discarded Data Page
Table 4–15 describes the data displayed in Figure 4–15.
Table 4–15 LAN VC Packets Discarded Data
Data Description
Bad Checksum
No Xmt Chan
Rcv Short Pkt
Ill Seq Pkt
TR DFQ Empty
TR MFQ Empty
CC MFQ Empty
Rcv Window Miss
Number of times there was a checksum failure on a received packet.
Number of times no transmit channel was available.
Number of times an undersized transport packet was received.
Number of times an out-of-range sequence numbered packet was received.
Number of times the transmit data-free queue (DFQ) was empty.
Number of times the TR layer message-free queue (MFQ) was empty.
Number of times the channel control MFQ was empty.
Number of packets that could not be placed in the virtual circuit’s receive cache because the cache was full.
4.3.3 LAN Channel Details Data
To display LAN channel details data, right-click a LAN channel summary data item on the Cluster Summary page (Figure 4–7). The Availability Manager displays a popup menu with the following options:
• Channel Details...
• Adapter Details...
• Fixes...
To display LAN channel details, select the Channel Details... item on the menu.
After a brief delay, a LAN Channel Overview Data Page, shown in Figure 4–16, is displayed. A series of tabs at the top of the Overview Data Page indicate additional channel pages you can display.
Displaying OpenVMS Cluster Data 4–25
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
4.3.3.1 LAN Channel Overview Data Page
The LAN Channel Overview Data page, shown in Figure 4–16, displays general channel data.
Figure 4–16 LAN Channel Overview Data Page
Table 4–16 describes the data displayed in Figure 4–16.
Table 4–16 LAN Channel Overview Data
Data Description
State
Status
Total Errors
Time Opened
Time Closed
Total Time Open
Device Name
Device Type
Average RTT
RSVP Threshold
Remote Ring Size
Remote Device Type
Remote T/R Cache
Channel’s current state: OPEN, PATH, or CLOSED.
Channel status.
Sum of channel’s error counters.
Last time that this channel had a path to a remote system.
Last time that this channel was closed.
Total time that this channel has been open.
Local LAN device name.
Local LAN device type.
Average of measured round-trip time.
Number of packets before requesting that the remote node immediately return an acknowledgment.
Number of entries in the remote LAN device.
Remote LAN device type.
Number of out-of-order packets that the remote transmit/receive resequencing cache can buffer.
(continued on next page)
4–26 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–16 (Cont.) LAN Channel Overview Data
Data Description
LAN H/W Address LAN device’s hardware address.
4.3.3.2 LAN Channel Counters Data Page
The LAN Channel Counters Data page, shown in Figure 4–17, displays path counters data.
Figure 4–17 LAN Channel Counters Data Page
Table 4–17 describes the data displayed in Figure 4–17.
Table 4–17 LAN Channel Counters Data
Data Description
ECS Transitions
Messages Sent
Bytes Sent
Control Messages Sent
Control Msg Bytes Sent
Messages Received
Number of times this channel has been in and out of the equivalent channel set (ECS).
Number of packets sent over this channel, including control packets.
Number of bytes transmitted on this channel, including control packets.
Number of control packets sent, not including multicast packets.
Number of control packet bytes sent, not including multicast packets.
Number of packets received by this channel.
(continued on next page)
Displaying OpenVMS Cluster Data 4–27
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–17 (Cont.) LAN Channel Counters Data
Data Description
Bytes Received
MC Control Messages
Rcvd
MC Control Msg Bytes
Rcvd
Control Messages Rcvd
Control Msg Bytes Rcvd
Number of bytes in packets received by this channel.
Number of multicast control packets received.
Number of multicast control packets bytes received.
Number of control packets received.
Number of control packet bytes received.
4.3.3.3 LAN Channel Errors Data Page
The LAN Channel Errors Data page, shown in Figure 4–18, displays LAN channel errors data.
Figure 4–18 LAN Channel Errors Data Page
Table 4–18 describes the data displayed in Figure 4–18.
Table 4–18 LAN Channel Errors Data
Data Description
Seq Retransmit
LAN Transmit
Failures
Number of times a sequenced VC packet sent on this channel was retransmitted, and the channel was penalized for the lost packet.
Number of times the local LAN device reported a failure to transmit a packet, and channel was penalized for the lost packet.
(continued on next page)
4–28 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–18 (Cont.) LAN Channel Errors Data
Data Description
Restart Channel Close/restart because of channel control packet was received indicating the other end closed the channel and is restarting the channel handshake.
Channel Init Timeouts Channel initialization handshake timeout.
Listen Timeouts No packets of any kind, including HELLOs, were received in
LISTEN_TIMEOUT seconds.
Bad Authorization Msg Received a CC (channel control) packet with a bad authorization field.
Bad ECO CC Msg Received a CC packet with an incompatible NISCA protocol ECO rev. field value.
Bad Multicast Msg Received a bad multicast CC packet.
CC Short Packet
CC Incompatible
Rcv Old Channel
No MSCP Server
Disk Not Served
Buffer Size Change
Received a CC packet that was too short.
Received a CC packet that was incompatible with existing channels for this virtual circuit.
Received a packet from an old instance of a channel.
No MSCP server available to respond to a received channel control solicit service packet asking this node to boot serve another node.
Disk is not served by this system.
Change in buffer size.
4.3.3.4 LAN Channel Remote System Data Page
The LAN Channel Remote System Data page, shown in Figure 4–19, displays
LAN path remote system data.
Displaying OpenVMS Cluster Data 4–29
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–19 LAN Channel Remote System Data Page
Table 4–19 describes the data displayed in Figure 4–19.
Table 4–19 LAN Channel Remote System Data
Data Description
Node Name
Buffer Size
Max Buffer Size
Services
Dev Name
LAN Address
H/W Type
Protocol Version
Node name of remote system.
Buffer size (largest possible buffer size) of remote system.
Current upper bound on buffer size usable on this channel.
NISCA services supported on this channel.
Name of the remote LAN device.
Remote hardware address.
Hardware type of remote node.
NISCA protocol version of remote system.
4.3.3.5 LAN Channel ECS (Equivalent Channel Set) Criteria Data Page
The LAN Channel ECS Criteria Data page, shown in Figure 4–20, displays equivalent channel set criteria data.
4–30 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–20 LAN Channel ECS Criteria Data Page
Table 4–20 describes the data displayed in Figure 4–20.
Table 4–20 LAN Channel ECS Criteria Data
Data Description
ECS Membership
Time Entered ECS
Time Exited ECS
Total Time in ECS
Losses
Capacity
Priority
Management Priority
Buffer Size
Management Buffer Size
Hops
Management Hops
Speed
ECS membership status; that is, Member or Nonmember.
Last time this channel entered the ECS.
Last time this channel exited the ECS.
Total time this channel was in the ECS.
Value representing channel’s recent packet loss history.
Channel’s capacity rating based on evaluating its priority, buffer size, and hops values relative to the current ECS criteria. Values are: Ungraded, Peer, Inferior, Superior.
Channel’s current priority for ECS calculations; it is the sum of the management priorities assigned to the local LAN device and to the channel.
Dynamic management-assigned priority.
Negotiated maximum common buffer size: the smaller of local and remote BUS$ limits on block data field sizes.
Maximum block data field size assigned by dynamic management.
Number of switches or bridges for this channel.
Management-supplied hops or media packet storage equivalent.
Classification of channel’s delay relative to that of the lowest delay of any ECS member.
(continued on next page)
Displaying OpenVMS Cluster Data 4–31
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–20 (Cont.) LAN Channel ECS Criteria Data
Data Description
Average RTT
Load Class
Local Seq Number
Remote Seq Number
Average measured round-trip time.
Lesser of the local and remote LAN device load class values.
Sequence number of the local channel.
Sequence number of the remote channel.
4.3.4 LAN Adapters Detail Data
To display LAN adapters details data, right-click a LAN path (channel) summary data item on the Cluster Summary page (see Figure 4–6). The Availability
Manager then displays a popup menu with the following options:
• Channel Details...
• Adapter Details...
• Fixes...
To display adapter details, select the Adapter Details... item on the menu. After a brief delay, a LAN Adapter Overview Data page (shown in Figure 4–21) is displayed.
A series of tabs at the top of the LAN Adapter Overview Data page indicate additional LAN adapter pages that you can display. Much of the LAN Adapter detail data corresponds to data displayed by the SCACP command SHOW LAN_
DEVICE.
4.3.4.1 LAN Adapter Overview Data Page
The LAN Adapter Overview Data page, shown in Figure 4–21, displays LAN adapters summary data.
Figure 4–21 LAN Adapter Overview Data Page
4–32 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–21 describes the data displayed in Figure 4–21.
Table 4–21 LAN Adapter Overview Data
Data Description
Status
Device Name
Device Type
Total Errors
Priority
Max Buffer Size
Mgmt Buffer Size
Load Class
Receive Ring Size
Default LAN Address
Current LAN Address
Device status: Run, Online, Restart; or Not in use by SCA.
LAN adapter’s device’s name.
OpenVMS device type value.
Total number of errors listed on the Errors page.
Dynamic management-assigned priority.
Maximum data buffer size for this LAN device.
Dynamic management-assigned maximum block data field size.
Load class. The rate in MBs currently being reported by the
LAN device.
Number of packets the LAN device can buffer before it discards incoming packets.
LAN device’s hardware LAN address.
Current LAN address being used by this LAN device.
4.3.4.2 LAN Adapter Transmit Data Page
The LAN Adapter Transmit Data page, shown in Figure 4–22, displays LAN adapter transmit data.
Figure 4–22 LAN Adapter Transmit Data Page
Displaying OpenVMS Cluster Data 4–33
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Table 4–22 describes the data displayed in Figure 4–22.
Table 4–22 LAN Adapter Transmit Data
Data Description
Messages Sent
Bytes Sent
Number of packets sent by this bus, including multicast packets.
Number of bytes in packets sent by this LAN device, including multicast packets.
Number of multicast packets sent by this LAN device.
Multicast Msgs Sent
Multicast Bytes Sent Number of multicast bytes in packets sent by this LAN device.
Outstanding I/O Count Number of transmit requests being processed by LAN driver.
4.3.4.3 LAN Adapter Receive Data Page
The LAN Adapter Receive Data page, shown in Figure 4–23, displays LAN adapter receive data.
Figure 4–23 LAN Adapter Receive Data Page
Table 4–23 describes the data displayed in Figure 4–23.
Table 4–23 LAN Adapter Receive Data
Data Description
Messages Rcvd
Bytes Received
Multicast Msgs Rcvd
Multicast Bytes Rcvd
Number of packets received by this LAN device, including multicast packets.
Number of bytes in packets received by this LAN device, including multicast packets.
Number of multicast NISCA packets received by this LAN device.
Number of multicast bytes received by this LAN device.
4–34 Displaying OpenVMS Cluster Data
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
4.3.4.4 LAN Adapter Events Data Page
The LAN Adapter Events Data page, shown in Figure 4–24, displays LAN adapter events data.
Figure 4–24 LAN Adapter Events Data Page
Table 4–24 describes the data displayed in Figure 4–24.
Table 4–24 LAN Adapter Events Data
Data Description
Port Usable
Port Unusable
Address Change
Restart Failures
Last Event
Time of Last Event
Number of times the LAN device became usable.
Number of times the LAN device became unusable.
Number of times the LAN device’s LAN address changed.
Number of times the LAN device failed to restart.
Event type of the last LAN device event (for example, LAN address change, an error, and so on).
Time the last event occurred.
4.3.4.5 LAN Adapter Errors Data Page
The LAN Adapter Errors Data page, shown in Figure 4–25, displays LAN adapter errors data.
Displaying OpenVMS Cluster Data 4–35
Displaying OpenVMS Cluster Data
4.3 Detailed Data in the Cluster Members Pane
Figure 4–25 LAN Adapter Errors Data Page
Table 4–25 describes the data displayed in Figure 4–25.
Table 4–25 LAN Adapter Errors Data
Data Description
Bad SCSSYSTEM ID
MC Msgs Directed to TR
Layer
Short CC Messages
Received
Short DX Messages
Received
CH Allocation Failures
VC Allocation Failures
Wrong Port
Port Disabled
H/W Transmit Errors
Hello Transmit Errors
Last Transmit Error
Reason
Time of Last Transmit
Error
Received a packet with the wrong SCSSYSTEM ID in it.
Number of multicast packets directed to the NISCA Transport layer.
Number of packets received that were too short to contain a
NISCA channel control header.
Number of packets received that were too short to contain a
NISCA DX header.
Number of times the system failed to allocate memory for use as a channel structure in response to a packet received by this
LAN device.
Number of times the system failed to allocate memory for use as a VC structure in response to a packet received by this LAN device.
Number of packets addressed to the wrong NISCA address.
Number of packets discarded because the LAN device was disabled.
Number of local hardware transmit errors.
Number of transmit errors during HELLOs.
Reason for last transmit error.
Time of last transmit error: date and time.
4–36 Displaying OpenVMS Cluster Data
5
Getting Information About Events
Note
Before you start this chapter, be sure to read the explanations of data collection, events, thresholds, and occurrences in Chapter 1.
The Availability Manager indicates resource availability problems in the Event pane Figure 5–1 of the main Application window (see Figure 1–1).
Figure 5–1 OpenVMS Event Pane
The Event pane helps you identify system problems. In many cases, you can apply fixes to correct these problems as well, as explained in Chapter 6.
The Availability Manager displays a warning message in the Event pane whenever it detects a resource availability problem. If logging is enabled (the default), the Availability Manager also logs each event in the Event Log file, which you can display or print. (See Section 5.2 for the location of this file and a cautionary note about it.)
Occurrence Counters
During data collection, any time data meets or exceeds the threshold for an event, an occurrence counter is incremented. When the incremented value matches the value in the Occurrence box on the Event Customization page (Figure 1–6), the event is posted in the Event pane of the Application window (see Figure 1–1).
Note that some events are triggered when data is lower than the threshold; other events are triggered when data is higher than the threshold.
If, at any time during data collection, the data does not meet or exceed the threshold, the occurrence counter is set to 0, and the event is removed from the
Event pane. Figure 5–2 depicts this sequence.
Getting Information About Events 5–1
Getting Information About Events
Figure 5–2 Testing for Events
Start
Does any data need testing
?
No
Yes
Does data exceed a threshold
?
Yes
No
Increment occurrence counter
End
Set occurrence counter to 0
Is event posted
?
Yes
No
Remove event from Event pane
No
Does occurrence counter equal occurrence value
?
Yes
Post event
VM-0480A-AI
5.1 Event Information That Is Displayed in the Event Pane
The Availability Manager can display events for all nodes that are currently in communication with the Data Analyzer. When an event of a certain severity occurs, the Availability Manager adds the event to a list in the Event pane.
The length of time an event is displayed depends on the severity of the event.
Less severe events are displayed for a short period of time (30 seconds); more severe events are displayed until you explicitly remove the event from the Event pane (explained in Section 5.1.2).
5–2 Getting Information About Events
Getting Information About Events
5.1 Event Information That Is Displayed in the Event Pane
5.1.1 Data in the Event Pane
Table 5–1 identifies the data items displayed in the Event pane.
Table 5–1 Event Pane Data
Data Item Description
Node
Group
Date
Time
Sev
Event
Description
Name of the node causing the event
Group of the node causing the event
Date the event occurred
Time that an event was detected
Severity: a value from 0 to 100
Alphanumeric identifier of the type of event
Short description of the resource availability problem
Appendix B contains tables of events that are displayed in the Event pane. In addition, these tables contain an explanation of each event and the recommended remedial action.
5.1.2 Event Pane Menu Options
When you right-click a node name or data item in the Event pane, the Availability
Manager displays a popup menu with the following options:
Menu Option
Display
Remove
Freeze/Unfreeze
Customize
Description
Displays the Node Summary page associated with that event.
Removes an event from the display.
Freezes a value in the display until you ‘‘unfreeze’’ it; a snowflake icon is displayed to the left of an event that is frozen.
Allows you to customize events.
5.2 Criteria for Posting and Displaying an Event
The Availability Manager uses the following criteria to determine whether to post an event and display it in the Event pane:
• Data collection posts an event if the event condition exists for the number of data collections specified in the Occurrence value on the Event Customization page (Figure 5–3).
Getting Information About Events 5–3
Getting Information About Events
5.2 Criteria for Posting and Displaying an Event
Figure 5–3 Sample Event Customization Page
The sample Event Customization page indicates an Occurrence value of 2.
This means that if the DSKERR event exceeds its threshold of 15 for two consecutive data collections, the DSKERR event is posted in the Event pane.
• When an event is posted, data is collected at the Event interval shown on the
Data Collection Customization page (Figure 5–4).
5–4 Getting Information About Events
Getting Information About Events
5.2 Criteria for Posting and Displaying an Event
Figure 5–4 OpenVMS Data Collection Customization Page
On the Data Collection Customization page, for example, the Event interval for Disk Status is every 15 seconds.
• The data value displayed in the Node pane that is associated with the event turns red when an event is posted (see Figure 5–5).
Figure 5–5 OpenVMS Node Pane
• When an event is posted, it is added to the Events Log file by default:
On OpenVMS systems, the Events Log file is:
AMDS$AM_LOG:ANALYZEREVENTS.LOG
A new version of this file is created each time you access the Availability
Manager.
On Windows systems, the Events Log file is:
AnalyzerEvents.log
This file, which is in the installation directory, is overwritten each time you access the Availability Manager.
Getting Information About Events 5–5
Getting Information About Events
5.2 Criteria for Posting and Displaying an Event
The following example shows a partial event log file:
VAXJET 01-22-2001 11:24:50.67 0 CFGDON VAXJET configuration done
DBGAVC 01-22-2001 11:25:12.41 0 CFGDON DBGAVC configuration done
AFFS5 01-22-2001 11:25:13.23 0 CFGDON AFFS5 configuration done
DBGAVC 01-22-2001 11:25:18.31 80 LCKCNT DBGAVC possible contention for resource REG$MASTER_LOCK
VAXJET 01-22-2001 11:25:27.47 40 LOBIOQ VAXJET LES$ACP_V30 has used most of its BIOLM process quota
PEROIT 01-22-2001 11:25:27.16 0 CFGDON PEROIT configuration done
KOINE 01-22-2001 11:25:33.05 99 NOSWFL KOINE has no swap file
MAWK 01-22-2001 11:26:20.15 99 FXTIMO MAWK Fix timeout for FID to Filename Fix
MAWK 01-22-2001 11:26:24.48 60 HIDIOR MAWK direct I/O rate is high
REDSQL 01-22-2001 11:26:30.61 10 PRPGFL REDSQL _FTA2: high page fault rate
REDSQL 01-22-2001 11:26:31.18 60 PRPIOR REDSQL _FTA7: paging I/O rate is high
MAWK 01-22-2001 11:26:24.48 60 HIDIOR MAWK direct I/O rate is high
AFFS52 01-22-2001 11:25:33.64 60 DSKMNV AFFS52 $4$DUA320(OMTV4) disk mount verify in progress
VAXJET 01-22-2001 11:38:46.23 90 DPGERR VAXJET error executing driver program, ...
REDSQL 01-22-2001 11:39:18.73 60 PRCPWT REDSQL _FTA2: waiting in PWAIT
REDSQL 01-22-2001 11:44:37.19 75 PRCCUR REDSQL _FTA7: has a high CPU rate
Caution About Event Logs
If you collect data on many nodes, running the Availability Manager for a long period of time can result in a large event log. For example, in a run that monitors more than 50 nodes with most of the background data collection enabled, the event log can grow by up to 30 MB per day. At this rate, systems with small disks might fill up the disk on which the event log resides.
Closing the Availability Manager application will enable you to access the event log for tasks such as archiving. Starting the Availability Manager starts a new event log.
5.3 Displaying Additional Event Information
For more detailed information about a specific event, double-click any event data item in the Event pane. The Availability Manager first displays a data page that most closely corresponds to the cause of the event. You can choose other tabs for additional detailed information.
For a description of data pages and the information they contain, see Chapter 3.
5–6 Getting Information About Events
6
Performing Fixes on OpenVMS Nodes
You can perform fixes on OpenVMS nodes to resolve resource availability problems and improve system availability.
This chapter discusses the following topics:
• Understanding fixes
• Performing fixes
Caution
Performing certain fixes can have serious repercussions, including possible system failure. Therefore, only experienced system managers should perform fixes.
6.1 Understanding Fixes
When you suspect or detect a resource availability problem, in many cases you can use the Availability Manager to analyze the problem and to perform a fix to improve the situation.
Availability Manager fixes fall into these categories:
• Node fixes
• Process fixes
• Cluster interconnect fixes
You can access fixes, by category, from the pages listed in Table 6–1.
Table 6–1 Accessing Availability Manager Fixes
Fix Category and Name Available from This Page
Node fixes:
Crash Node
Adjust Quorum
Node Summary
CPU
Memory
I/O
(continued on next page)
Performing Fixes on OpenVMS Nodes 6–1
Performing Fixes on OpenVMS Nodes
6.1 Understanding Fixes
Table 6–1 (Cont.) Accessing Availability Manager Fixes
Fix Category and Name Available from This Page
Process fixes:
General process fixes:
Delete Process
Exit Image
Suspend Process
Resume Process
Process Priority
All of the process fixes are available from the following pages:
Memory
I/O
CPU Process
Single Process
Process memory fixes:
Purge Working Set (WS)
Adjust Working Set (WS)
Process limits fixes:
Direct I/O
Buffered I/O
AST
Open file
Lock
Timer
Subprocess
I/O Byte
Pagefile Quota
Cluster interconnect fixes:
– Port Adjust Priority
– Circuit Adjust Priority
These fixes are available from the following lines of data on the Cluster Summary page
(Figure 4–7):
Right-click a data item on the local port data display line to display a menu containing the
Adjust Priority option.
Right-click a data item on the circuits data display line to display a menu containing the
Adjust Priority option.
Right-click a data item in the LAN Virtual
Circuit Summary category to display a menu.
Then click the Fixes... menu item.
LAN Virtual Circuit summary:
Maximum Transmit Window Size
Maximum Receive Window Size
Checksumming
Compression
LAN Path (Channel) Summary:
Adjust Priority
Hops
Maximum Packet Size
Right-click a data item in the LAN Path
(Channel) Summary category to display a menu. Then click the VC LAN Fix... menu item.
(continued on next page)
6–2 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.1 Understanding Fixes
Table 6–1 (Cont.) Accessing Availability Manager Fixes
Fix Category and Name Available from This Page
LAN Adapter Details:
Adjust Priority
Maximum Buffer Size
Start Adapter
Stop Adapter
Right-click a data item in the LAN Path
(Channel) Summary category to display a menu. Then click the Adapter Details menu item to display pages containing Fix options.
Table 6–2 summarizes various problems, recommended fixes, and the expected results of fixes.
Table 6–2 Summary of Problems and Matching Fixes
Problem Fix Result
Node resource hanging cluster
Cluster hung
Process looping, intruder
Endless process loop in same PC range
Runaway process, unwelcome intruder
Process previously suspended
Runaway process or process that is overconsuming
Low node memory
Crash Node
Adjust Quorum
Delete Process
Exit Image
Suspend Process
Resume Process
Process Priority
Node fails with operator-requested shutdown.
Quorum for cluster is adjusted.
Process no longer exists.
Exits from current image.
Process is suspended from execution.
Process starts from point it was suspended.
Base priority changes to selected setting.
Working set too high or low
Process quota has reached its limit and has entered RWAIT state
Process has exhausted its pagefile quota
Purge Working Set
(WS)
Adjust Working Set
(WS)
Adjust Process
Limits
Adjust Pagefile
Quota
Frees memory on node; page faulting might occur for process affected.
Removes unused pages from working set; page faulting might occur.
Process limit is increased, which in many cases frees the process to continue execution.
Pagefile quota limit of the process is adjusted.
Most process fixes correspond to an OpenVMS system service call, as shown in the following table:
Process Fix
Delete Process
Exit Image
Suspend Process
Resume Process
Process Priority
Purge Working Set (WS)
Adjust Working Set (WS)
System Service Call
$DELPRC
$FORCEX
$SUSPND
$RESUME
$SETPRI
$PURGWS
$ADJWSL
Performing Fixes on OpenVMS Nodes 6–3
Performing Fixes on OpenVMS Nodes
6.1 Understanding Fixes
Process Fix
Adjust process limits of the following:
Direct I/O (DIO)
Buffered I/O (BIO)
Asynchronous system trap (AST)
Open file (FIL)
Lock queue (ENQ)
Timer queue entry (TQE)
Subprocess (PRC)
I/O byte (BYT)
System Service Call
None
Note
Each fix that uses a system service call requires that the process execute the system service. A hung process will have the fix queued to it, where the fix will remain until the process is operational again.
Be aware of the following facts before you perform a fix:
• You must have write access to perform a fix. To perform LAN fixes, you must have control access.
• You cannot undo many fixes. For example, after using the Crash Node fix, the node must be rebooted (either by the node if the node reboots automatically, or by a person performing a manual boot).
• Do not apply the Exit Image, Delete Process, or Suspend Process fix to system processes. Doing so might require you to reboot the node.
• Whenever you exit an image, you cannot return to that image.
• You cannot delete processes that have exceeded their job or process quota.
• The Availability Manager ignores fixes applied to the SWAPPER process.
How to Perform Fixes
Standard OpenVMS privileges restrict users’ write access. When you run the
Data Analyzer, you must have the CMKRNL privilege to send a write (fix) instruction to a node with a problem.
The following options are displayed at the bottom of all fix pages:
Option
OK
Cancel
Apply
Description
Applies the fix and then exits the page. Any message associated with the fix is displayed in the Event pane.
Cancels the fix.
Applies the fix and does not exit the page. Any message associated with the fix is displayed in the Return Status section of the page and in the Event pane.
The following sections explain how to perform node fixes and process fixes.
6–4 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.2 Performing Node Fixes
6.2 Performing Node Fixes
The Availability Manager node fixes allow you to deliberately fail (crash) a node or to adjust cluster quorum.
To perform a node fix, follow these steps:
1.
On the Node Summary, CPU, Memory, or I/O page, click the Fix menu.
2.
Click Fix Options.
6.2.1 Crash Node
Caution
The crash node fix is an operator-requested bugcheck from the driver. It takes place as soon as you click OK in the Crash Node page. After you perform this fix, the node cannot be restored to its previous state. After a crash, the node must be rebooted.
When you select the Crash Node option, the Availability Manager displays the
Crash Node page, shown in Figure 6–1.
Figure 6–1 Crash Node Page
Note
Because the node cannot report a confirmation when a node crash fix is successful, the crash success message is displayed after the timeout period for the fix confirmation has expired.
Performing Fixes on OpenVMS Nodes 6–5
Performing Fixes on OpenVMS Nodes
6.2 Performing Node Fixes
Recognizing a System Failure Forced by the Availability Manager
Because a user with suitable privileges can force a node to fail from the Data
Analyzer by using the ‘‘Crash Node’’ fix, system managers have requested a method for recognizing these particular failure footprints so that they can distinguish them from other failures. These failures all have identical footprints: they are operator-induced system failures in kernel mode at IPL 8. The top of the kernel stack is similar the following display:
SP => Quadword system address
Quadword data
1BE0DEAD.00000000
00000000.00000000
Quadword data
Quadword data
TRAP$CRASH
SYS$RMDRIVER + offset
6.2.2 Adjust Quorum
The Adjust Quorum fix forces the node to refigure the quorum value. This fix is the equivalent of the Interrupt Priority C (IPC) mechanism used at system consoles for the same purpose. The fix forces the adjustment for the entire cluster so that each node in the cluster will have the same new quorum value.
The Adjust Quorum fix is useful when the number of votes in a cluster falls below the quorum set for that cluster. This fix allows you to readjust the quorum so that it corresponds to the current number of votes in the cluster.
When you select the Adjust Quorum option, the Availability Manager displays the page shown in Figure 6–2.
Figure 6–2 Adjust Quorum Page
6–6 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3 Performing Process Fixes
To perform a process fix, follow these steps:
1.
On the Memory or I/O page, right-click a process name.
2.
Click Fix Options.
The Availability Manager displays these Process tabs:
Process General
Process Memory
Process Limits
3.
Click one of these tabs to bring it to the front.
4.
Click the down arrow to display the process fixes in this group, as shown in
Figure 6–3, where the Process General tab has been chosen.
Figure 6–3 Process General Options
5.
Select a process fix (for example, Process Priority, as shown in Figure 6–3,) to display a fix page.
Some of the fixes, such as Process Priority, require you to use a slider to change the default value. When you finish setting a new process priority, click Apply at the bottom of the page to apply that fix.
6.3.1 General Process Fixes
The following sections describe Availability Manager general process fixes.
Performing Fixes on OpenVMS Nodes 6–7
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.1.1 Delete Process
In most cases, a Delete Process fix deletes a process. However, if a process is waiting for disk I/O or is in a resource wait state (RWAST), this fix might not delete the process. In this situation, it is useless to repeat the fix. Instead, depending on the resource the process is waiting for, a Process Limit fix might free the process. As a last resort, reboot the node to delete the process.
Caution
Deleting a system process could cause the system to hang or become unstable.
6–8 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
When you select the Delete Process option, the Availability Manager displays the page shown in Figure 6–4.
Figure 6–4 Delete Process Page
After reading the explanation, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.3.1.2 Exit Image
Exiting an image on a node can stop an application that a user requires. Check the Single Process page first to determine which image is running on the node.
Caution
Exiting an image on a system process could cause the system to hang or become unstable.
Performing Fixes on OpenVMS Nodes 6–9
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
When you select the Exit Image option, the Availability Manager displays the page shown in Figure 6–5.
Figure 6–5 Exit Image Page
After reading the explanation in the page, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.3.1.3 Suspend Process
Suspending a process that is consuming excess CPU time can improve perceived
CPU performance on the node by freeing the CPU for other processes to use.
(Conversely, resuming a process that was using excess CPU time while running might reduce perceived CPU performance on the node.)
Caution
Do not suspend system processes, especially JOB_CONTROL, because this might make your system unusable. (See the OpenVMS Programming
Concepts Manual, Volume I for more information.)
6–10 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
When you select the Suspend Process option, the Availability Manager displays the page shown in Figure 6–6.
Figure 6–6 Suspend Process Page
After reading the explanation, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.3.1.4 Resume Process
Resuming a process that was using excess CPU time while running might reduce perceived CPU performance on the node. (Conversely, suspending a process that is consuming excess CPU time can improve perceived CPU performance by freeing the CPU for other processes to use.)
Performing Fixes on OpenVMS Nodes 6–11
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
When you select the Resume Process option, the Availability Manager displays the page shown in Figure 6–7.
Figure 6–7 Resume Process Page
After reading the explanation, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.3.1.5 Process Priority
If the priority of a compute-bound process is too high, the process can consume all the CPU cycles on the node, affecting performance dramatically. On the other hand, if the priority of a process is too low, the process might not obtain enough
CPU cycles to do its job, also affecting performance.
6–12 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
When you select the Process Priority option, the Availability Manager displays the page shown in Figure 6–8.
Figure 6–8 Process Priority Page
To change the base priority for a process, drag the slider on the scale to the number you want. The current priority number is displayed in a small box above the slider. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new base priority, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.3.2 Process Memory Fixes
The following sections describe the Availability Manager fixes you can use to correct process memory problems:
• Purge Working Set
• Adjust Working Set
6.3.2.1 Purge Working Set
This fix purges the working set to a minimal size. You can use this fix to reclaim a process’s pages that are not in active use. If the process is in a wait state, the working set remains at a minimal size, and the purged pages become available for other uses. If the process becomes active, pages the process needs are pagefaulted back into memory, and the unneeded pages are available for other uses.
Be careful not to repeat this fix too often: a process that continually reclaims needed pages can cause excessive page faulting, which can affect system performance.
Performing Fixes on OpenVMS Nodes 6–13
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
When you select the Purge Working Set option, the Availability Manager displays the page shown in Figure 6–9.
Figure 6–9 Purge Working Set Page
After reading the explanation on the page, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.3.2.2 Adjust Working Set
Adjusting the working set of a process might prove to be useful in situations similar to the following ones:
• If a process is page-faulting because of insufficient memory, you can reclaim unused memory from other processes by decreasing the working set of one or more of them.
• If a process is page-faulting too frequently because its working set is too small, you can increase its working set.
Caution
If the automatic working set adjustment is enabled for the system, a fix to adjust the working set size disables the automatic adjustment for the process. For more information, refer to OpenVMS online help for SET
WORKING_SET/ADJUST, which includes /NOADJUST.
When you select the Adjust Working Set fix, the Availability Manager displays the page shown in Figure 6–10.
6–14 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
Figure 6–10 Adjust Working Set Page
To perform this fix, use the slider to adjust the working set to the limit you want.
You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new working set limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.3.3 Process Limits Fixes
If a process is waiting for a resource, you can use a Process Limits fix to increase the resource limit so that the process can continue. The increased limit is in effect only for the life of the process, however; any new process is assigned the quota that was set in the UAF.
When you click the Process Limits tab, you can select any of the following options:
Direct I/O
Buffered I/O
AST
Open File
Lock
Timer
Subprocess
I/O Byte
Pagefile Quota
These fix options are described in the following sections.
Performing Fixes on OpenVMS Nodes 6–15
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.1 Direct I/O Count Limit
You can use this fix to adjust the direct I/O count limit of a process. When you select the Direct I/O option, the Availability Manager displays the page shown in
Figure 6–11.
Figure 6–11 Direct I/O Count Limit Page
To perform this fix, use the slider to adjust the direct I/O count to the limit you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new direct I/O count limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6–16 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.2 Buffered I/O Count Limit
You can use this fix to adjust the buffered I/O count limit of a process. When you select the Buffered I/O option, the Availability Manager displays the page shown in Figure 6–12.
Figure 6–12 Buffered I/O Count Limit Page
To perform this fix, use the slider to adjust the buffered I/O count to the limit you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new buffered I/O count limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
Performing Fixes on OpenVMS Nodes 6–17
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.3 AST Queue Limit
You can use this fix to adjust the AST queue limit of a process. When you select the AST option, the Availability Manager displays the page shown in Figure 6–13.
Figure 6–13 AST Queue Limit Page
To perform this fix, use the slider to adjust the AST queue limit to the number you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new AST queue limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6–18 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.4 Open File Limit
You can use this fix to adjust the open file limit of a process. When you select the Open File option, the Availability Manager displays the page shown in
Figure 6–14.
Figure 6–14 Open File Limit Page
To perform this fix, use the slider to adjust the open file limit to the number you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new open file limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
Performing Fixes on OpenVMS Nodes 6–19
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.5 Lock Queue Limit
You can use this fix to adjust the lock queue limit of a process. When you select the Lock option, the Availability Manager displays the page shown in
Figure 6–15.
Figure 6–15 Lock Queue Limit Page
To perform this fix, use the slider to adjust the lock queue limit to the number you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new lock queue limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6–20 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.6 Timer Queue Entry Limit
You can use this fix to adjust the timer queue entry limit of a process. When you select the Timer option, the Availability Manager displays the page shown in
Figure 6–16.
Figure 6–16 Timer Queue Entry Limit Page
To perform this fix, use the slider to adjust the timer queue entry limit to the number you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new timer queue entry limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
Performing Fixes on OpenVMS Nodes 6–21
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.7 Subprocess Creation Limit
You can use this fix to adjust the creation limit of the subprocess of a process.
When you select the Subprocess option, the Availability Manager displays the page shown in Figure 6–17.
Figure 6–17 Subprocess Creation Limit Page
To perform this fix, use the slider to adjust the subprocess creation limit of a process to the number you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new subprocess creation limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6–22 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.8 I/O Byte
You can use this fix to adjust the I/O byte limit of a process. When you select the
I/O Byte option, the Availability Manager displays the page shown in Figure 6–18.
Figure 6–18 I/O Byte Page
To perform this fix, use the slider to adjust the I/O byte limit to the number you want. You can also click the line above or below the slider to adjust the number by 1.
When you are satisfied with the new I/O byte limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
Performing Fixes on OpenVMS Nodes 6–23
Performing Fixes on OpenVMS Nodes
6.3 Performing Process Fixes
6.3.3.9 Pagefile Quota
You can use this fix to adjust the pagefile quota limit of a process. This quota is share among all the processes in a job. When you select the Pagefile Quota option, the Availability Manager displays the page shown in Figure 6–19.
Figure 6–19 Pagefile Quota Page
To perform this fix, use the slider to adjust the pagefile quota limit to the number you want. You can also click above or below the slider to adjust the fix value by 1.
When you are satisfied with the new pagefile quota limit, click Apply at the bottom of the page to apply the fix. A message displayed on the page indicates that the fix has been successful.
6.4 Performing Cluster Interconnect Fixes
Cluster interconnect fixes have been added to the Availability Manager beginning in Version 2.0. The following are categories of cluster interconnect fixes:
• Port adjust priority fix
• Circuit adjust priority fix
• LAN virtual circuit (VC) summary fixes
• LAN channel (path) fixes
• LAN adapter fixes
The following sections describe these types of fixes and tell how to access them and how to perform them. The descriptions also indicate whether or not the fix is currently available.
6–24 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.1 Port Adjust Priority Fix
To access the Port Adjust Priority fix, right-click a data item in the local port data display line (see Figure 4–3). The Availability Manager displays a popup menu with the Port Fix option.
This page (Figure 6–20) allows you to change the cost associated with this port, which, in turn, affects the routing of cluster traffic.
Figure 6–20 Port Adjust Priority Page
6.4.2 Circuit Adjust Priority Fix
To access the Circuit Adjust Priority fix, right-click a data item in the local port data display line (see Figure 4–4). The Availability Manager displays a popup menu with the Circuit Fix option.
This page (Figure 6–21) allows you to change the cost associated with this circuit, which, in turn, affects the routing of cluster traffic.
Performing Fixes on OpenVMS Nodes 6–25
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
Figure 6–21 Circuit Adjust Priority Page
6.4.3 LAN Virtual Circuit Summary Fixes
To access LAN virtual circuit summary fixes, right-click a data item in the LAN
Virtual Circuit Summary category (see Figure 4–6). The Availability Manager displays a popup menu with the following options:
• Channel Summary
• VC LAN Details...
• VC LAN Fix...
When you select VC LAN Fix..., the Availability Manager displays the first of several fix pages, the Maximum Transmit Window Size. By clicking Maximum
Transmit Window Size, you can display a list of all the LAN VC summary fixes:
• Maximum Transmit Window Size
• Maximum Receive Window Size
• Checksumming
• Compression
These fixes are described in the following sections.
6–26 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.3.1 LAN VC Maximum Transmit Window Size Fix
This page (Figure 6–22) allows you to adjust the maximum transmit window size for the virtual circuit.
Note
This fix is not currently implemented.
Figure 6–22 LAN VC Maximum Transmit Window Size Page
Performing Fixes on OpenVMS Nodes 6–27
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.3.2 LAN VC Maximum Receive Window Size Fix
This page, (Figure 6–23) allows you to adjust the maximum receive window size for the virtual circuit.
Note
This fix is not currently implemented.
Figure 6–23 LAN VC Maximum Receive Window Size Page
6–28 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.3.3 LAN VC Checksumming Fix
This page (Figure 6–24) allows you to turn checksumming on or off for the virtual circuit.
Note
This fix is not currently implemented.
Figure 6–24 LAN VC Checksumming Page
Performing Fixes on OpenVMS Nodes 6–29
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.3.4 LAN VC Compression Fix
This page (Figure 6–24) allows you to turn compression on or off for the virtual circuit.
Note
This fix is not currently implemented.
Figure 6–25 LAN VC Compression Page
6–30 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.4 LAN Channel Fixes
To access LAN path fixes, right-click an item in the LAN Channel Summary category (see Figure 4–7). The Availability Manager displays a popup menu with the following options:
• Channel Details...
• Adapter Details...
• Fixes...
Click the Fixes... menu item to display this list of available fixes:
• Adjust Priority
• Hops
• Maximum Packet Size
These fixes are described in the following sections.
6.4.4.1 LAN Path Adjust Priority Fix
This page (Figure 6–26) allows you to change the cost associated with this channel. This, in turn, affects the routing of cluster traffic.
Figure 6–26 LAN Path Adjust Priority Page
Performing Fixes on OpenVMS Nodes 6–31
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.4.2 LAN Path Hops Fix
This page (Figure 6–27) allows you to change the hops for the channel. This fix changes the hops value associated with this channel. This, in turn, affects the routing of cluster traffic.
Figure 6–27 LAN Path Hops Page
6–32 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.4.3 LAN Path Maximum Packet Size Fix
This page (Figure 6–28) allows you to set the maximum packet size associated with this channel. This, in turn, affects the routing of cluster traffic.
Note
This fix is not currently implemented.
Figure 6–28 LAN Path Maximum Packet Size Page
Performing Fixes on OpenVMS Nodes 6–33
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.5 LAN Adapter Fixes
To access LAN adapter fixes, right-click an item in the LAN Path (Channel)
Summary category (see Figure 4–7). The Availability Manager displays a popup menu with the following options:
• Channel Details...
• Adapter Details...
• Fixes...
Select the Adapter Details menu item to display the Adapter Details window.
From the Adapter Details window, select Fix... from the Fix menu. The
Availability Manager displays the first of several pages, each of which contains a fix option:
Adjust Priority
Set Max Buffer Size
Start Adapter
Stop Adapter
These fixes are described in the following sections.
6.4.5.1 LAN Adapter Adjust Priority Fix
This page (Figure 6–29) allows you to adjust the management priority for the adapter. This fix changes the cost associated with this adapter. This, in turn, affects the routing of cluster traffic.
Figure 6–29 LAN Adapter Adjust Priority Page
6–34 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.5.2 LAN Adapter Set Maximum Buffer Fix
This page (Figure 6–30) allows you to set the maximum packet size for the adapter. This fix changes the maximum packet size associate with this channel.
This, in turn, affects the routing of cluster traffic.
Figure 6–30 LAN Adapter Set Maximum Buffer Size Page
Performing Fixes on OpenVMS Nodes 6–35
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.5.3 LAN Adapter Start Adapter Fix
This page (Figure 6–31) starts the use of this adapter. This fix enables the use of this adapter for cluster traffic.
Figure 6–31 LAN Adapter Start Adapter Page
6–36 Performing Fixes on OpenVMS Nodes
Performing Fixes on OpenVMS Nodes
6.4 Performing Cluster Interconnect Fixes
6.4.5.4 LAN Adapter Stop Adapter Fix
This page (Figure 6–32) stops the use of this adapter. This fix disables the use of this adapter for cluster traffic.
Caution
This fix could result in interruption of cluster communications for this node. The node may exit the cluster (CLUEXIT crash).
Figure 6–32 LAN Adapter Stop Adapter Page
Performing Fixes on OpenVMS Nodes 6–37
7
Customizing the Availability Manager
This chapter explains how to customize the following features of the Availability
Manager:
Feature Description
Nodes or groups of nodes
You can select one or more groups or individual nodes to monitor.
Group membership You can change a node’s default group membership.
Types of data collection
For OpenVMS nodes, you can select the types of data you want to collect as well as several types of collection intervals. (On Windows nodes, specific types of data are collected by default.)
Data filters
Event filters
Security features
For OpenVMS nodes, you can specify a number of parameters and values that limit the amount of data that is collected.
You can specify the severity of events that are displayed as well as several other filtering settings.
On Data Analyzer and Data Collector nodes, you can change passwords. On OpenVMS Data Collector nodes, you can edit a file that contains security triplets.
How to Specify Which Nodes to Customize
In the Application window, you can select the Customize option in either of the following ways:
• To customize groups of nodes, on the Application window menu bar, click the
Customize menu. The Availability Manager displays the popup menu shown in Figure 7–1.
Figure 7–1 Customize Menu in Application Window
• To customize a specific node, right-click a node name in the Node pane of the
Application window (see Figure 1–1). The Availability Manager displays the popup menu shown in Figure 7–2.
Customizing the Availability Manager 7–1
Customizing the Availability Manager
Figure 7–2 Customize Menu in Node Pane
Depending on which Customize menu you use and your choice of menu items, in a group of nodes,your customizations can affect one or more nodes, as indicated in the following table.
Nodes Affected
All nodes
All Windows nodes
All OpenVMS nodes
One node
Action
Click Customize Application... on the menu shown in
Figure 7–1.
Click Customize Windows NT... on the menu shown in
Figure 7–1.
Click Customize OpenVMS... on the menu shown in
Figure 7–1.
Click Customize... on the popup menu shown in Figure 7–2.
The customization options you choose will affect only the node you have selected.
7.1 Specifying Groups or Individual Nodes to Monitor
When you select Customize Application on the Application window Customize menu (Figure 7–1), the Availability Manager displays a Group/Node Lists tab
(Figure 7–3).
7–2 Customizing the Availability Manager
Customizing the Availability Manager
7.1 Specifying Groups or Individual Nodes to Monitor
Figure 7–3 Group/Node Lists Customization Page
You can select either of the following lists of nodes to monitor:
•
Use Group List
Using the correct case, enter the names of the groups of nodes you want to monitor.
•
Use Node List
Using the correct case, enter the names of individual nodes you want to monitor.
If you decide to return to the default (monitor all nodes) or to enter names again, click Use default values.
After you enter a list of groups or individual nodes, click one of the following choices:
Option
OK
Cancel
Apply
Description
Accepts the choice of names you have entered and exits the page.
Cancels the choice of names and does not exit the page.
Accepts the choice of names you have entered but does not exit the page.
To put the list into effect, exit the Availability Manager and restart it.
Customizing the Availability Manager 7–3
Customizing the Availability Manager
7.2 Changing the Group Membership of a Node
7.2 Changing the Group Membership of a Node
Each Availability Manager Data Collector node is assigned to the DECAMDS group by default. The following sections explain how to change the group membership of nodes.
Note
You need to place nodes belonging to the same cluster in the same group.
If such nodes are placed in different groups, some of the data collected might be misleading.
7.2.1 Changing the Group of an OpenVMS Node
You need to edit a logical on each Data Collector node to change the group for that node. To do this, follow these steps:
1.
Assign a unique name of up to 15 alphanumeric characters to the AMDS$GROUP_NAME logical name in the AMDS$AM_
SYSTEM:AMDS$AM_LOGICALS.COM file. For example:
$ AMDS$DEF AMDS$GROUP_NAME FINANCE ! Group FINANCE; OpenVMS Cluster alias
2.
Apply the logical name by restarting the Data Collector:
$ @SYS$STARTUP:AMDS$AM_STARTUP RESTART
Note
The configuration files for DECamds and the Availability Manager are separate; only one set is used, depending on which startup command procedure you use to start the driver.
Refer to the Compaq Availability Manager Installation Instructions for
OpenVMS Alpha Systems for further explanation of the configuration files set up for both DECamds and the Availability Manager.
7.2.2 Changing the Group of a Windows Node
You need to edit the Registry to change the group of a Windows node. To edit the
Registry, follow these steps:
1.
Click the Windows Start button. On the lists displayed, first click Programs and then Command Prompt.
2.
Type REGEDIT after the angle prompt (>).
The system displays a screen for the Registry Editor, with a list of entries under My Computer.
3.
On the list displayed, click HKEY_LOCAL_MACHINE .
4.
Click SYSTEM.
5.
Click CurrentControlSet.
6.
Click damdrvr.
7.
Click Parameters.
7–4 Customizing the Availability Manager
Customizing the Availability Manager
7.2 Changing the Group Membership of a Node
8.
Double-click Group Name. Then type a new group name of 15 alphanumeric characters or fewer, and click OK to make the change.
9.
On the Control Panel, click Services, and then click Stop for ‘‘PerfServ.’’
10.
Again on the Control Panel, click Devices, and then click Stop for ‘‘damdrvr.’’
11.
First restart damdrvr under ‘‘Devices,’’ and then restart PerfServ under
‘‘Services.’’
This step completes the change of groups for this node.
7.3 Customizing OpenVMS Data Collection
Note
Before you start this section, be sure to read the explanation of data collection, events, thresholds, and occurrences in Chapter 1.
When you click the Customize OpenVMS... menu option in the Application window and then click the Data Collection tab, the Availability Manager displays the OpenVMS Data Collection Customization page, where you can choose types of data you want to collect. You can also change the default
Availability Manager intervals at which data is collected or updated.
Figure 7–4 shows the OpenVMS Data Collection page.
Figure 7–4 OpenVMS Data Collection Customization Page
Customizing the Availability Manager 7–5
Customizing the Availability Manager
7.3 Customizing OpenVMS Data Collection
Table 7–1 identifies the page where each type of data collected appears and indicates whether or not that type of data collection is a default.
Table 7–1 Data Collection Choices
Data Collected Default Page Where Data Is Displayed
Cluster summary data
CPU mode data
CPU summary data
Disk status data
Disk volume data
I/O data
Lock contention data
Memory data
Node summary data
Page/Swap file data
Single disk data
Single process data
No
No
No
Yes
No
No
No
No
No
No
Yes
1
Yes
2
Cluster Summary page
CPU Modes Summary page
CPU Process States page
Disk Status Summary page
Disk Volume Summary page
I/O Summaries page
Lock Contention page
Memory Summary page
Node pane, Node Summary page, and the top pane of the CPU, Memory, and I/O pages
I/O Page Faults page
Single Disk Summary page
Data collection for the Process Information page
1
Data is collected by default when you open a Single Disk Summary page.
2
Data is collected by default when you open a Single Process page.
You can choose additional types of data to collect by selecting the Collect check box on the Data Collection Customization page of the Customize OpenVMS... menu (Figure 7–4). A check mark indicates that data will be collected at the intervals described in Table 7–2.
Table 7–2 Data Collection Intervals
Interval (in seconds) Description
Display
Event
NoEvent
How often the data display is refreshed.
If events occur related to the screen, how often data is collected.
If no events occur related to the screen, how often data is collected.
You can enter a different collection interval by double-clicking the value; then delete the old value and enter a new one. If you change your mind and decide to return to the default collection interval, select one or more rows of data items: then click Use default values. The system displays the default values for all the collection intervals.
When you finish customizing your data collection, select one of the following options at the bottom of the page:
7–6 Customizing the Availability Manager
Customizing the Availability Manager
7.3 Customizing OpenVMS Data Collection
Option
OK
Cancel
Apply
Description
To confirm any changes you have made and exit the page.
To cancel any changes you have made and exit the page.
To confirm and apply any changes you have made and not exit the page.
7.4 Customizing OpenVMS Data Filters
When you select the Customize OpenVMS... menu option and click the Filter tab, the Availability Manager displays a page that allows you to display specific kinds of data by selecting check boxes. The types of data filters available are as follows:
• CPU Filters
• Disk Status
• Disk Volume
• I/O
• Lock Contention
• Memory Filters
• Page/Swap File
Filters can vary depending on the type of data collected. For example, filters might be process states or a variety of rates and counts. The following sections describe data filters that are available for various types of data collection.
Each filter page contains the following note: ‘‘Changes to these settings will override the program default settings.’’ This means that settings that are changed on the node level override settings made at the application and program
(or GUI) level.
You can display the default values for the data items on the page at any time. To do this, select the item and click Use default values.
When you finish modifying a filters page, click one of the following options at the bottom of the page:
Option
OK
Cancel
Apply
Description
To confirm any changes you have made and exit the page.
To cancel any changes you have made and exit the page.
To confirm and apply any changes you have made and continue to display the page.
7.4.1 OpenVMS CPU Filters
When you click CPU Filters on the Filter page, the Availability Manager displays the OpenVMS CPU Filters page (Figure 7–5).
Customizing the Availability Manager 7–7
Customizing the Availability Manager
7.4 Customizing OpenVMS Data Filters
Figure 7–5 OpenVMS CPU Filters Page
This page allows you to change and select values that are displayed on the
OpenVMS CPU Process States page (Figure 3–7).
You can change the current priority and rate of a process. By default, a process is displayed only if it has a Current Priority of 4 or more. Click the up or down arrow to increase or decrease the priority value by one. The default CPU rate is
0.0, which means that processes with any CPU rate used will be displayed. To limit the number of processes displayed, you can click the up or down arrow to increase or decrease the CPU rate by .5 each time you click.
The OpenVMS CPU Filters page also allows you to select the states of the processes that you want to display on the CPU Process States page. Select the check box for each state you want to display. (Process states are described in
Appendix B.)
7.4.2 OpenVMS Disk Status Filters
When you click Disk Status on the Filter page, the Availability Manager displays the OpenVMS Disk Status Filters page (Figure 7–6).
7–8 Customizing the Availability Manager
Customizing the Availability Manager
7.4 Customizing OpenVMS Data Filters
Figure 7–6 OpenVMS Disk Status Filters Page
The OpenVMS Disk Status Summary page (Figure 3–13) displays the values you set on this filters page.
This filters page lets you change the following default values:
Data
Error Count
Transaction
Mount Count
RWAIT Count
Description
The number of errors generated by the disk (a quick indicator of device problems).
The number of in-progress file system operations for the disk.
The number of nodes that have the specified disk mounted.
An indicator that a system I/O operation is stalled, usually during normal connection failure recovery or volume processing of hostbased shadowing.
This filters page also lets you check the states of the disks you want to display, as described in the following table:
Disk State
Invalid
Shadow Member
Unavailable
Wrong Vol
Mounted
Mount Verify
Offline
Online
Description
Disk is in an invalid state (Mount Verify Timeout is likely).
Disk is a member of a shadow set.
Disk is set to unavailable.
Disk was mounted with the wrong volume name.
Disk is logically mounted by a MOUNT command or a service call.
Disk is waiting for a mount verification.
Disk is no longer physically mounted in device drive.
Disk is physically mounted in device drive.
Customizing the Availability Manager 7–9
Customizing the Availability Manager
7.4 Customizing OpenVMS Data Filters
7.4.3 OpenVMS Disk Volume Filters
When you click Disk Volume on the Filter page, the Availability Manager displays the OpenVMS Disk Volume Filters page (Figure 7–7).
Figure 7–7 OpenVMS Disk Volume Filters Page
The OpenVMS Disk Volume Filters page allows you to change the values for the following data:
Data
Used Blocks
Disk % Used
Free Blocks
Queue Length
Operations Rate
Description
The number of volume blocks in use.
The percentage of the number of volume blocks in use in relation to the total volume blocks available.
The number of blocks of volume space available for new data.
Current length of all queues.
The rate at which the operations count to the volume has changed since the last sampling. The rate measures the amount of activity on a volume. The optimal load is device-specific.
You can also change options for the following to be on (checked) or off (unchecked):
• RAMdisks (MDxn:): Show devices
• Wrtlocked Volumes: Show devices
• Sec. Page/Swap: Show devices
• Filtered Volumes: Use filter
7–10 Customizing the Availability Manager
Customizing the Availability Manager
7.4 Customizing OpenVMS Data Filters
7.4.4 OpenVMS I/O Filters
When you click I/O on the Filter page, the Availability Manager displays the
OpenVMS I/O Filters page (Figure 7–8).
Figure 7–8 OpenVMS I/O Filters Page
The OpenVMS I/O Summaries page (Figure 3–11) displays the values you set on this filters page.
This filters page allows you to change values for the following data:
Data Description
Direct I/O Rate
Buffered I/O Rate
Paging I/O Rate
The rate at which I/O transfers occur between the system devices and the pages or pagelets that contain the process buffer that the system locks in physical memory.
The rate at which I/O transfers occur between the process buffer and an intermediate buffer from the system buffer pool.
The rate of read attempts necessary to satisfy page faults (also known as Page Read I/O or the Hard Fault Rate).
The number of open files.
Open File Count
BIO lim Remaining The number of remaining buffered I/O operations available before the process reaches its quota. BIOLM quota is the maximum number of buffered I/O operations a process can have outstanding at one time.
DIO lim Remaining The number of remaining direct I/O limit operations available before the process reaches its quota. DIOLM quota is the maximum number of direct I/O operations a process can have outstanding at one time.
Customizing the Availability Manager 7–11
Customizing the Availability Manager
7.4 Customizing OpenVMS Data Filters
Data Description
BYTLM Remaining The number of buffered I/O bytes available before the process reaches its quota. BYTLM is the maximum number of bytes of nonpaged system dynamic memory that a process can claim at one time.
Open File limit The number of additional files the process can open before reaching its quota. FILLM quota is the maximum number of files that can be opened simultaneously by the process, including active network logical links.
7.4.5 OpenVMS Lock Contention Filters
The OpenVMS Lock Contention Filters page allows you to remove (filter out) resource names from the Lock Contention page (Figure 3–18).
When you click Lock Contention on the Filter page, the Availability Manager displays the OpenVMS Lock Contention Filters page (Figure 7–9).
Figure 7–9 OpenVMS Lock Contention Filters Page
Each entry on the Lock Contention Filters page is a resource name or part of a resource name that you want to filter out. For example, the STRIPE$ entry filters out any value that starts with the characters STRIPE$. To redisplay original entries, click Use default values.
7–12 Customizing the Availability Manager
Customizing the Availability Manager
7.4 Customizing OpenVMS Data Filters
7.4.6 OpenVMS Memory Filters
When you click Memory Filters on the Filter page, the Availability Manager displays the OpenVMS Memory Filters page (Figure 7–10).
Figure 7–10 OpenVMS Memory Filters Page
The OpenVMS Memory page (Figure 3–9) displays the values on this filters page.
The OpenVMS Memory Filters page allows you to change values for the following data:
Data Description
Working Set Count The number of physical pages or pagelets of memory that the process is using.
Working Set Size The number of pages or pagelets of memory the process is allowed to use. The operating system periodically adjusts this value based on an analysis of page faults relative to CPU time used. An increase in this value in large units indicates a process is receiving a lot of page faults and its memory allocation is increasing.
Working Set Extent The number of pages or pagelets of memory in the process’s
WSEXTENT quota as defined in the user authorization file (UAF).
The number of pages or pagelets will not exceed the value of the system parameter WSMAX.
Page Fault Rate The number of page faults per second for the process.
Page I/O Rate The rate of read attempts necessary to satisfy page faults (also known as page read I/O or the hard fault rate).
Customizing the Availability Manager 7–13
Customizing the Availability Manager
7.4 Customizing OpenVMS Data Filters
7.4.7 OpenVMS Page/Swap File Filters
When you click Page/Swap File on the Filter page, the Availability Manager displays the OpenVMS Page/Swap File Filters page (Figure 7–11).
Figure 7–11 OpenVMS Page/Swap File Filters Page
The OpenVMS I/O Summaries page (Figure 3–11) displays the values that you set on this filters page.
This filters page allows you to change values for the following data:
Data
Used Blocks
Page File % Used
Swap File % Used
Total Blocks
Reservable Blocks
Description
The number of used blocks within the file.
The percentage of the blocks from the page file that have been used.
The percentage of the blocks from the swap file that have been used.
The total number of blocks in paging and swapping files.
Number of reservable blocks in each paging and swapping file currently installed. Reservable blocks can be logically claimed by a process for a future physical allocation. A negative value indicates that the file might be overcommitted. Note that a negative value is not an immediate concern but indicates that the file might become overcommitted if physical memory becomes scarce.
You can also select (turn on) or clear (turn off) the following options:
• Show page files
• Show swap files
7–14 Customizing the Availability Manager
Customizing the Availability Manager
7.5 Customizing Events and User Notification of Events
7.5 Customizing Events and User Notification of Events
You can customize a number of characteristics of the events that are displayed in the Event pane of the Application window (Figure 1–1). You can also use customization options to notify users when specific events occur.
When you select the Customize OpenVMS... or Customize Windows NT... option from the Application window’s Customize menu, the Availability Manager displays a tabbed page similar to the one shown in Figure 7–12.
Figure 7–12 Event Customization Page
7.5.1 Customizing Events
You can change the values for any data that is available (not dimmed) on this page.
The following table describes the data you can change:
Data
Severity
Description
Controls the severity level at which events are displayed in the Event pane. By default, all events are displayed. Increasing this value reduces the number of event messages in the Event pane and can improve perceived response time.
Customizing the Availability Manager 7–15
Customizing the Availability Manager
7.5 Customizing Events and User Notification of Events
Data
Occurrence
Threshold
Description
Each Availability Manager event is assigned an occurrence value, that is, the number of consecutive data samples that must exceed the event threshold before the event is signaled. By default, events have low occurrence values. However, you might find that a certain event indicates a problem only when it occurs repeatedly over an extended period. You can change the occurrence value assigned to that event so that the Availability Manager signals it only when necessary.
For example, suppose page fault spikes are common in your environment, and the Availability Manager frequently signals intermittent HITTLP, total page fault rate is high events. You could change the event’s occurrence value to 3, so that the total page fault rate must exceed the threshold for three consecutive collection intervals before being signaled to the event log.
To avoid displaying insignificant events, you can customize an event so that the Availability Manager signals it only when it occurs continuously.
Most events are checked against only one threshold; however, some events have dual thresholds, where the event is triggered if either one is true. For example, for the LOVLSP, node disk volume free space
is low event, the Availability Manager checks both of the following thresholds:
• Number of blocks remaining (LowDiskFreeSpace.BlkRem)
• Percentage of total blocks remaining (LowDiskFreeSpace.Percent)
Event escalation action
You can enter one of the following values:
• None: Take no action if this event occurs.
• Opcom: Not yet implemented.
• User: If the event occurs, the Availability Manager refers to the
‘‘User Action’’ field to determine what action to take.
User Action When the ‘‘Event escalation action’’ field is set to User, User Action is no longer dimmed. You can enter the name of a procedure to be executed if the event displayed at the top of the page occurs. To use this field, refer to the instructions in Section 7.5.2.
The ‘‘Event explanation and investigation hints’’ section of the Event
Customization page, which is not customizable, includes a description of the event displayed and a suggestion for how to correct any problems that the event signals.
7.5.2 Entering a User Action
Note
OpenVMS and Windows execute the User Action procedure somewhat differently, as explained in the following paragraphs.
The following notes pertain to writing and executing User Action commands or command procedures. These notes apply to User Actions on both OpenVMS and
Windows systems.
7–16 Customizing the Availability Manager
Customizing the Availability Manager
7.5 Customizing Events and User Notification of Events
• The procedure that you specify as the User Action will be executed in the following manner:
It will be issued to the operating system that is running the Availability
Manager Data Analyzer.
It will be issued as a process separate from the one running the
Availability Manager to avoid affecting its operation.
It will be run under the same account as the one running the Availability
Manager Data Analyzer.
• User Actions are intended to execute procedures that do not require interactive displays or user input.
• You can enter User Actions for events on either a systemwide basis or a per-node basis:
On a systemwide basis, the User Action is issued for an event that occurs on any node.
On a per-node basis, the User Action is issued for an event that occurs only on a specific node.
• If event logging is enabled, the Availability Manager writes events to the event log file (called AnalyzerEvents.log by default on OpenVMS systems and
AvailManEvents.log by default on Windows systems). A status line matching the original line indicates whether the User Action was successfully issued.
For example:
AMGR/KOINE -- 13-Apr-2001 15:33:02.531 --<0,CFGDON>KOINE configuration done
AMGR/KOINE -- 13-Apr-2001 15:33:02.531 --<0,CFGDON>KOINE configuration done
(User Action issued for this event on the client O/S)
Other events might appear between the first logging and the status line. The log file does not indicate whether the User Action executed successfully. You must obtain the execution status from the operating system, for example, the
OpenVMS batch procedure log.
• The User Action functionality might be enhanced in a future release of the
Availability Manager, but backward compatibility is not guaranteed for the format of User Action procedure strings or for the method of executing the procedures on a particular operating system.
7.5.2.1 Executing a Procedure on an OpenVMS System
The User Action procedure and arguments are passed as string values to the DCL command interpreter as follows:
$ SUBMIT/NOPRINTER/LOG user_action_procedure arg_1 arg_2 arg_3 arg_4 where:
• The first command is the DCL command SUBMIT with associated qualifiers.
• user_action_procedure is a valid OpenVMS file name.
Enter the name of the procedure you want OpenVMS to execute using the following format:
disk:[directory]filename.COM
where:
disk is the name of the disk where the procedure resides.
Customizing the Availability Manager 7–17
Customizing the Availability Manager
7.5 Customizing Events and User Notification of Events
directory is the name of the directory where the procedure resides.
filename.COM is the file name of the command procedure you want
OpenVMS to execute. The file name must follow OpenVMS file-naming conventions.
The file you submit must contain one or more DCL command statements that form a valid OpenVMS command procedure.
• The arguments correspond to the following data:
Argument
arg_1 arg_2 arg_3 arg_4
Description
Node name of the node that generated the event.
Date and time that the event was generated.
Name of the event.
Description of the event.
The Availability Manager does not interpret the string contents. You can supply any content in the User Action procedure that DCL accepts in the OpenVMS environment for the user account running the Data Analyzer. However, if you include arguments in the User Action procedure, they might displace or overwrite arguments supplied by the Availability Manager.
A suitable batch queue must be available on the Data Analyzer computer to be the target of the SUBMIT command. Refer to the OpenVMS DCL Dictionary for the SUBMIT, INITIALIZE/QUEUE, and START/QUEUE commands for use of batch queues and the queue manager.
The following is an example of a DCL command procedure:
$ if (p3.eqs."DSKOFF").and.(p1.eqs."PAYROL")
$ then
$ mail/subject="’’p2’ ’’p3’ ’’p4’ "urgent_instructions.txt
call_center,finance,adams
$ else
$ mail/subject="’’p2’ ’’p3’ ’’p4’ "instructions.txt call_center
$ endif
The pn numbers in the DCL procedure correspond in type, number, and position to the arguments in the preceding table.
You might use a procedure like this one to notify several groups if the payroll disk goes off line, or to notify the call center if any other event occurs.
7.5.2.2 Executing a Procedure on a Windows System
The user action procedure and arguments are passed as string values to the
Windows command interpreter as follows:
"AT time CMD/C user_action_procedure arg_1 arg_2 arg_3 arg_4" where:
• AT is the Windows command that schedules commands and programs at a specified time and date.
• The time substring is a short period of time— aproximately 2 minutes—in the future so that the AT utility processes the user action procedure today rather than tomorrow. This is necessary because the AT utility cannot execute a procedure ‘‘now’’ rather than at an explicitly stated time.
7–18 Customizing the Availability Manager
Customizing the Availability Manager
7.5 Customizing Events and User Notification of Events
• user_action_procedure is a Windows command or valid file name. The file must contain one or more Windows command statements to form a valid command procedure. (See the example in this section.)
Enter the name of the procedure you want Windows to execute using the following format:
device:\ (directory\ filename.BAT
where:
device is the disk on which the procedure is located.
directory is the folder in which the procedure is located.
filename.BAT is the name of the command file to be executed. The file name must follow Windows file-naming conventions.
• The arguments are listed in the table in Section 7.5.2.1.
The Availability Manager does not interpret the string contents. You can supply any content in the string that the Windows command-line interpreter accepts for the user account running the Data Analyzer. However, if you include arguments in the User Action procedure, they might displace or overwrite arguments supplied by the Availability Manager.
You cannot specify positional command-line switches or arguments to the AT command, although you can include switches in the User Action procedure substring as qualifiers to the user-supplied command. This is a limitation of both the Windows command-line interpreter and the way the entire string is passed from the Availability Manager to Windows.
The Schedule service must be running on the Data Analyzer computer in order to use the AT command. However, the Schedule service does not run by default. To start the Schedule service, refer to the Windows documentation for instructions in the use of the CONTROL PANEL/SERVICES/SCHEDULE/[startup button].
Windows Examples
The following are examples of a Windows command procedure and a direct command invocation:
• Command procedure: notify.bat
net send/domain:openvms %1 %2 %3 %4
The numbers preceded by a percent sign (%) correspond to the arguments in the table in Section 7.5.2.1.
• Direct command invocation net send/domain:openvms
When executed, both of these User Actions display a message containing the contents of the command-line arguments in the OpenVMS domain.
7.6 Customizing Security Features
The following sections explain how to change these security features:
• Data Analyzer passwords for OpenVMS and Windows Data Collector nodes
• OpenVMS Data Collector security triplets
Customizing the Availability Manager 7–19
Customizing the Availability Manager
7.6 Customizing Security Features
• A Windows Data Collector password
Note
OpenVMS Data Collector nodes can have more than one password: each password is part of a security triplet. (Windows nodes allow you to have only one password per node.)
7.6.1 Changing Data Analyzer Passwords
You can change the passwords that the Windows Data Analyzer uses for
OpenVMS Data Collector nodes and for Windows Data Collector nodes. The following sections explain how to perform both actions.
7.6.1.1 Changing a Data Analyzer Password for an OpenVMS Data Collector Node
When you click Customize OpenVMS... on the Customize menu of the
Application window, the Availability Manager displays a Security page
(Figure 7–13).
Figure 7–13 OpenVMS Security Customization Page
To change the default password for the Data Analyzer to use to access OpenVMS
Data Collector nodes, enter a password of exactly 8 uppercase alphanumeric characters. The Availability Manager will use this password to access OpenVMS
Data Collector nodes. This password must match the password that is part of the
OpenVMS Data Collector security triplet (see Section 1.4).
When you are satisfied with your password, click OK. Exit the Availability
Manager, and restart the application for the password to take effect.
7–20 Customizing the Availability Manager
Customizing the Availability Manager
7.6 Customizing Security Features
7.6.1.2 Changing a Data Analyzer Password for a Windows Data Collector Node
When you click Customize Windows NT... on the Customize menu of the Application window, the Availability Manager displays a Security page
(Figure 7–14).
Figure 7–14 Windows Security Customization Page
To change the default password for the Data Analyzer to use to access Windows
Data Collector nodes, enter a password of exactly 8 alphanumeric characters.
Note that this password is case sensitive; any time you type it, you must use the original capitalization.
This password must also match the password for the Windows Data Collector node that you want to access. (See Section 7.6.3 for instructions for changing that password.)
When you are satisfied with your password, click OK. Exit and restart the
Availability Manager for the password to take effect.
7.6.2 Changing Security Triplets on OpenVMS Data Collector Nodes
To change security triplets on an OpenVMS Data Collector node, you must edit the AMDS$DRIVER_ACCESS.DAT file, which is installed on all Data
Collector nodes. The following sections explain what a security triplet is, how the
Availability Manager uses it, and how to change it.
Customizing the Availability Manager 7–21
Customizing the Availability Manager
7.6 Customizing Security Features
7.6.2.1 Understanding OpenVMS Security Triplets
A security triplet determines which nodes can access system data from an
OpenVMS Data Collector node. The AMDS$DRIVER_ACCESS.DAT file on
OpenVMS Data Collector nodes lists security triplets.
On OpenVMS Data Collector nodes, the AMDS$AM_CONFIG logical translates to the location of the default security file, AMDS$DRIVER_ACCESS.DAT. This file is installed on all OpenVMS Data Collector nodes.
A security triplet is a three-part record whose fields are separated by backslashes
( \ ). A triplet consists of the following fields:
• A network address (hardware address or wildcard character)
• An 8-character alphanumeric password
The password is not case sensitive (so the passwords ‘‘testtest’’ and
‘‘TESTTEST’’ are considered to be the same).
• A read, write, or control (R, W, or C) access verification code
The exclamation point ( ! ) is a comment delimiter; any characters to the right of the comment delimiter are ignored.
Example
All Data Collector nodes in group FINANCE have the following AMDS$DRIVER_
ACCESS.DAT file:
*\FINGROUP\R ! Let anyone with FINGROUP password read
!
2.1\DEVGROUP\W ! Let only DECnet node 2.1 with
! DEVGROUP password perform fixes (writes)
7.6.2.2 How to Change a Security Triplet
Note
The configuration files for DECamds and the Availability Manager are separate; only one set is used, depending on which startup command procedure you use to start the driver.
See Installing the Availability Manager on OpenVMS Alpha Systems
and Running DECamds and the Availability Manager Concurrently for a further explanation of the configuration file setup for both DECamds and the Availability Manager.
On each Data Collector node on which you want to change security, you must edit the AMDS$DRIVER_ACCESS.DAT file. The data in the AMDS$DRIVER_
ACCESS.DAT file is set up as follows:
Network address\password\access
Use a backslash character (\ ) to separate the three fields.
To edit the AMDS$DRIVER_ACCESS.DAT file, follow these steps:
1.
Edit the network address.
The network address can be either of the following:
• Hardware address
7–22 Customizing the Availability Manager
Customizing the Availability Manager
7.6 Customizing Security Features
The hardware address field is the physical hardware address in the
LAN adapter chip. It is used if you have multiple LAN adapters or are running the Compaq DECnet-Plus for OpenVMS networking software on the system (not the Compaq DECnet Phase IV for OpenVMS networking software).
For adapters provided by Compaq, the hardware address is in the form
08-00-2B-xx-xx-xx, where the 08-00-2B portion is Compaq’s valid range of
LAN addresses as defined by the IEEE 802 standards, and the xx-xx-xx portion is chip specific.
To determine the value of the hardware address on a node, use the
OpenVMS System Dump Analyzer (SDA) as follows:
$ ANALYZE/SYSTEM
SDA> SHOW LAN
These commands display a list of available devices. Choose the template device of the LAN adapter you will be using, and then enter the following command:
SDA> SHOW LAN/DEVICE=xxA0
• Wildcard address
The wildcard character (*) allows any incoming triplet with a matching password field to access the Data Collector node. Use the wildcard character to allow read access and to run the console application from any node in your network.
Because the Data Analyzer does not use this field, you should use the wildcard character in this field in the AMDS$CONSOLE_ACCESS.DAT
file.
Caution: Use of the wildcard character for write-access security triplets enables any person using that node to perform system-altering fixes.
2.
Edit the password field.
The password field must be an 8-byte alphanumeric field. The Availability
Manager forces upper-case on the password, so "aaaaaaaa" and "AAAAAAAA" are essentially the same password to the Data Collector.
The password field gives you a second level of protection when you want to use the wildcard address denotation to allow multiple modes of access to your monitored system.
3.
Enter R, W, or C as an access code:
• R means READONLY allowance for the Data Analyzer.
• W means READ/WRITE allowance for the Data Analyzer. (WRITE implies READ.)
• C means CONTROL allowance for the Data Analyzer. CONTROL allows you to manipulate objects from which data are derived. (CONTROL implies both WRITE and READ.)
The following security triplets are all valid; an explanation follows the exclamation point (!).
Customizing the Availability Manager 7–23
Customizing the Availability Manager
7.6 Customizing Security Features
*\1decamds\r ! Anyone with password "1decamds" can monitor
*\1decamds\w ! Anyone with password "1decamds" can monitor or write
2.1\1decamds\r ! Only node 2.1 with password "1decamds" can monitor
2.1\1decamds\w ! Only node 2.1 with password "1decamds" can monitor and write
08-00-2b-03-23-cd\1decamds\w ! Allows a particular hardware address to write
08-00-2b-03-23-cd\1decamds\r ! Allows a particular hardware address to read node
OpenVMS Data Collector nodes accept more than one password. Therefore, you might have several security triplets in an AMDS$DRIVER_ACCESS.DAT file for one Data Collector node. For example:
*\1DECAMDS\R
*\KOINECLS\R
*\KOINEFIX\W
*\AVAILMAN\C
In this example, Data Analyzer nodes with the passwords 1DECAMDS and
KOINECLS would be able to see the Data Collector data, but only the Data
Analyzer node with the KOINEFIX password would be able to write or change information, including performing fixes, on the Data Collector node. The Data
Analyzer node with the AVAILMAN password would be able to perform switched
LAN fixes.
If you want, you can set up your AMDS$DRIVER_ACCESS.DAT file to allow anyone in the world to read from your system but allow only certain nodes to write or change process or device characteristics on your system.
Note
After editing the AMDS$DRIVER_ACCESS.DAT file, you must stop and then restart the Data Collector. This action loads the new data into the driver.
7.6.2.3 How the Availability Manager Ensures Security
The Availability Manager performs these steps when using security triplets to ensure security among Data Analyzer and Data Collector nodes:
1.
A message is broadcast at regular intervals to all nodes within the LAN indicating the availability of a Data Collector node to communicate with a
Data Analyzer node.
2.
The node running the Data Analyzer receives the availability message and returns a security triplet that identifies it to the Data Collector, and requests system data from the Data Collector.
3.
The Data Collector examines the security triplet to determine whether the
Data Analyzer is listed in the AMDS$DRIVER_ACCESS.DAT file to permit access to the system.
• If the AMDS$DRIVER_ACCESS.DAT file lists Data Analyzer access information, then the Data Provider and the Data Analyzer can exchange information.
• If the Data Analyzer is not listed in the AMDS$DRIVER_ACCESS.DAT
file or does not have appropriate access information, then access is denied and a message is logged to OPCOM. The Data Analyzer receives a message stating that access to that node is not permitted.
7–24 Customizing the Availability Manager
Customizing the Availability Manager
7.6 Customizing Security Features
Table 7–3 describes how the Data Collector node interprets a security triplet match.
Table 7–3 Security Triplet Verification
Security Triplet Interpretation
08-00-2B-12-34-56\ HOMETOWN\ W
2.1\ HOMETOWN\ R
*\ HOMETOWN\ R
The Data Analyzer has write access to the node only when the Data Analyzer is run from a node with this hardware address (multiadapter or
DECnet-Plus system) and with the password
HOMETOWN.
The Data Analyzer has read access to the node when run from a node with DECnet for OpenVMS Phase IV address 2.1 and the password HOMETOWN.
Any Data Analyzer with the password
HOMETOWN has read access to the node.
7.6.3 Changing a Password on a Windows Data Collector
To change the Data Collector password in the Registry, follow these steps:
1.
Click the Windows Start button. First click Programs and then Command
Prompt.
2.
Type
regedit
after the angle prompt (>).
The system displays a screen for the Registry Editor, with a list of entries under My Computer.
3.
On the list displayed, click HKEY_LOCAL_MACHINE .
4.
Click SYSTEM.
5.
Click CurrentControlSet.
6.
Click Services.
7.
Click damdrvr.
8.
Click Parameters.
9.
Double-click Read Password. Then type a new 8-character alphanumeric password, and click OK to make the change.
10.
To store the new password, click Exit under File on the main menu bar.
11.
On the Control Panel, click Services and then Stop for ‘‘PerfServ.’’
12.
Again on the Control Panel, click Devices and then Stop for ‘‘damdrvr.’’
13.
First restart damdrvr under ‘‘Devices’’ and then restart PerfServ under
‘‘Services.’’
This step completes the change of your Data Collector password.
Customizing the Availability Manager 7–25
A
CPU Process States
The CPU process states shown in the following table are displayed in the
OpenVMS CPU Process States page (see Figure 3–7) and in the OpenVMS
Process Information page (see Figure 3–19).
Table A–1 CPU Process States
Process
State Description
CEF
COLPG
COM
COMO
CUR
FPW
LEF
LEFO
HIB
HIBO
Common Event Flag, waiting for a common event flag
Collided Page Wait, involuntary wait state; likely to indicate a memory shortage, waiting for hard page faults
Computable; ready to execute
Computable Outswapped, COM, but swapped out
Current, currently executing in a CPU
Free Page Wait, involuntary wait state; most likely indicates a memory shortage
Local Event Flag, waiting for a Local Event Flag
Local Event Flag Outswapped; LEF, but outswapped
Hibernate, voluntary wait state requested by the process; it is inactive
Hibernate Outswapped, hibernating but swapped out
(continued on next page)
CPU Process States A–1
CPU Process States
Table A–1 (Cont.) CPU Process States
Process
State Description
MWAIT Miscellaneous Resource Wait, involuntary wait state, possibly caused by a shortage of a systemwide resource, such as no page or swap file capacity or no synchronizations for single-threaded code.
Types of MWAIT states are shown in the following table:
MWAIT State
BYTLM Wait
JIB Wait
TQELM Wait
EXH
INNER_MODE
PSXFR
RWAST
RWMBX
RWNBX
RWPFF
RWPAG
RWMPE
RWMPB
RWSCS
RWCLU
RWCAP
RWCSV
Definition
Process waiting for buffered I/O byte count quota.
Process in either BYTLM Wait or TQELM Wait state.
Process waiting for timer queue entry quota.
Kernel thread in exit handler (not currently used).
Kernel thread waiting to acquire inner-mode semaphore.
Process waiting during a POSIX fork operation.
Process waiting for system or special kernel mode AST.
Process waiting because mailbox is full.
Process waiting for nonpaged dynamic memory.
Process waiting because page file is full.
Process waiting for paged dynamic memory.
Process waiting because modified page list is empty.
Process waiting because modified page writer is busy.
Process waiting for distributed lock manager.
Process waiting because OpenVMS Cluster is in transition.
Process waiting for CPU that has its capability set.
Kernel thread waiting for request completion by
OpenVMS Cluster server process.
PFW
RWAST
RWBRK
RWCAP
RWCLU
RWCSV
Page Fault Wait, involuntary wait state; possibly indicates a memory shortage, waiting for hard page faults.
Resource Wait State, waiting for delivery of an asynchronous system trap
(AST) that signals a resource availability; usually an I/O is outstanding or a process quota is exhausted.
Resource Wait for BROADCAST to finish
Resource Wait for CPU Capability
Resource Wait for Cluster Transition
Resource Wait for Cluster Server Process
(continued on next page)
A–2 CPU Process States
CPU Process States
RWMPB
RWMPE
RWNPG
RWPAG
RWPFF
RWQUO
RWSCS
RWSWP
SUSP
Table A–1 (Cont.) CPU Process States
Process
State Description
RWIMG
RWLCK
RWMBX
SUSPO
Resource Wait for Image Activation Lock
Resource Wait for Lock ID data base
Resource Wait on MailBox, either waiting for data in mailbox (to read) or waiting to place data (write) into a full mailbox (some other process has not read from it; mailbox is full so this process cannot write).
Resource Wait for Modified Page writer Busy
Resource Wait for Modified Page list Empty
Resource Wait for Non Paged Pool
Resource Wait for Paged Pool
Resource Wait for Page File Full
Resource Wait for Pooled Quota
Resource Wait for System Communications Services
Resource Wait for Swap File space
Suspended, wait state process placed into suspension; it can be resumed at the request of an external process
Suspended Outswapped, suspended but swapped out
CPU Process States A–3
B
Tables of Events
This appendix contains the following tables of events:
• OpenVMS Events
• Windows Events
Each table provides the following information:
• Alphabetical list of the events that the Availability Manager signals in the
Event pane of the Application window (see Figure 1–1)
• Abbreviation and brief description of each event (also displayed in the Event pane)
• Explanation of the event and a suggestion for remedial action, if applicable
Table B–1 OpenVMS Events
Event Description Explanation
CFGDON Configuration done
DPGERR Error executing driver program
DSKERR High disk error count
DSKINV Disk is invalid
The server application has made a connection to the node and will start collecting the data according to the Customize Data Collection options.
The Data Collector has detected a program error while executing the data collection program.
The error count for the disk device exceeds the threshold.
The valid bit in the disk device status field is not set. The disk device is not considered valid by the operating system.
Recommended Action
This informational event indicates that the node is recognized. No further investigation is required.
This event can occur if you have a bad driver program library, or there is a bug in the driver program. Make sure you have the program library that shipped with the kit; if it is correct, contact your customer support representative with the full text of the event.
Check error log entries for device errors.
A disk device with a high error count could indicate a problem with the disk or with the connection between the disk and the system.
Make sure that the disk device is valid and is known to the operating system.
(continued on next page)
Tables of Events B–1
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event Description Explanation
DSKMNV Disk in mount verify state
The disk device is performing a mount verification.
Recommended Action
The system is performing a mount verification for the disk device. This could be caused by:
• A removable disk on a local or remote node was removed.
• A disk on a local or remote node has gone offline due to errors.
• The node that serves the disk is down.
• The connection to a remote disk is down.
DSKOFF
DSKQLN High disk queue length
DSKRWT
DSKUNA Disk device is unavailable
DSKWRV Wrong volume mounted
ELIBCR
ELIBNP
ELIBUR
Disk device is off line
High disk
RWAIT count
Bad CRC for exportable program library
No privilege to access exportable program library
Unable to read exportable program library
The disk device has been placed in the off line state.
The average number of pending
I/Os to the disk device exceeds the threshold.
The RWAIT count on the disk device exceeds the threshold.
The disk device has been placed in the Unavailable state.
The disk device has been mounted with the wrong volume label.
The CRC calculation for the exportable program library does not match the CRC value in the library.
Unable to access the exportable program library.
Check whether the disk device should be off line. This event is also signalled when the same device name is used for two different physical disks. The volume name in the event is the second node to use the same device name.
More I/O requests are being queued to the disk device than the device can service. Reasons include a slow disk or too much work being done on the disk.
RWAIT is an indicator that an I/O operation has stalled, usually during normal connection failure recovery or volume processing of host-based shadowing. A node has probably failed and shadowing is recovering data.
The disk device state has been set to
/NOAVAILABLE. See DCL help for the
SET DEVICE/AVAILABLE command.
Set the correct volume name by entering the DCL command SET
VOLUME/LABEL on the node.
The exportable program library may be corrupt. Restore the exportable program library from its original source.
Check to make sure that the Availability
Manager has the proper security access to the exportable program library file.
Unable to read the exportable program library for the combination of hardware architecture and OpenVMS version.
The exportable program library may be corrupt. Restore the exportable program library from its original source.
(continued on next page)
B–2 Tables of Events
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event Description Explanation
FXCPKT Received a corrupt fix response packet from node
FXCRSH Crash node fix
The Availability Manager tried to perform a fix, but the fix acknowledgment from the node was corrupt.
FXDCPR Decrement process priority fix
FXDCWS Decrement process working set size fix
FXDLPR Delete process fix
FXEXIT
FXINPR
Exit image fix
Increment process priority fix
FXINQU Increment process quota limits fix
FXINWS Increment process working set size fix
FXNOPR No-change process priority fix
Recommended Action
This event could occur if there is network congestion or some problem with the node. Confirm the connection to the node, and reapply the fix if necessary.
The Availability Manager has successfully performed a Crash
Node fix on the node.
The Availability Manager has successfully performed a
Decrement Process Priority fix on the process.
The Availability Manager has successfully decreased the working set size of the process on the node by performing an Adjust Working
Set fix.
The Availability Manager has successfully performed a Delete
Process fix on the process.
This informational message indicates a successful fix. Expect to see a Path Lost event for the node.
This informational message indicates a successful fix. Setting a process priority too low takes CPU time away from the process.
This informational message indicates a successful fix. This fix disables the automatic working set adjustment for the process.
The Availability Manager has successfully performed an Exit
Image fix on the process.
The Availability Manager has successfully performed an
Increment Process Priority fix on the process.
The Availability Manager has successfully increased the quota limit of the process on the node by placing a new limit value in the limit field of the quota.
The Availability Manager has successfully increased the working set size of the process on the node by performing an Adjust Working
Set fix.
The Availability Manager has successfully performed a Process
Priority fix on the process that resulted in no change to the process priority.
This informational message indicates a successful fix. If the process is in RWAST state, this fix does not work. This fix also does not work on processes created with the no delete option.
This informational message indicates a successful fix. Forcing a system process to exit its current image can corrupt the kernel.
This informational message indicates a successful fix. Setting a process priority too high takes CPU time away from other processes. Set the priority above
15 only for ‘‘real-time’’ processing.
This informational message indicates a successful fix. This fix is only for the life of the process. If the problem continues, change the limit for the account in the
UAF file.
This informational message indicates a successful fix. This fix disables the automatic working set adjustment for the process. The adjusted working set value cannot exceed WSQUOTA for the process or WSMAX for the system.
This informational message indicates a successful fix. The Fix Value slider was set to the current priority of the process.
(continued on next page)
Tables of Events B–3
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event
FXNOQU No-change process quota limits fix
FXNOWS No-change process working set size fix
FXPGWS Purge working set fix
FXPRIV No privilege to attempt fix
FXQUOR Adjust quorum fix
FXRESM Resume process fix
FXSUSP
FXTIMO
FXUERR Unknown error code for fix
HIBIOR
Description
Suspend process fix
Fix timeout
High buffered
I/O rate
HICOMQ Many processes waiting in
COM or
COMO
Explanation
The Availability Manager has successfully performed a quota limit fix for the process that resulted in no change to the quota limit.
The Availability Manager has successfully performed Adjust
Working Set fix on the process.
The Availability Manager has successfully performed a Purge
Working Set fix on the process.
Recommended Action
This informational message indicates a successful fix. The Fix Value slider was set to the current quota of the process.
This informational message indicates a successful fix. The Fix Value slider was set to the current working set size of the process.
This informational message indicates a successful fix. The purged process might page fault to retrieve memory it needs for current processing.
See Chapter 6 for details about setting up security.
The Availability Manager cannot perform a fix on the node due either to no CMKRNL privilege or to unmatched security triplets.
The Availability Manager has successfully performed an Adjust
Quorum fix on the node.
The Availability Manager has successfully performed a Resume
Process fix on the process.
The Availability Manager has successfully performed a Suspend
Process fix on the process.
The Availability Manager tried to perform a fix, but no acknowledgment for the fix was received from the node within the timeout period.
The Availability Manager tried to perform a fix, but the fix failed for an unexpected reason.
The node’s average buffered I/O rate exceeds the threshold.
The average number of processes on the node in the COM or COMO queues exceeds the threshold.
This informational message indicates a successful fix. Use this fix when you find many processes in RWCAP state on a cluster node.
This informational message indicates a successful fix. If the process goes back into suspend state, check the AUDIT_
SERVER process for problems.
This informational message indicates a successful fix. Do not suspend system processes.
This event can occur if there is network congestion, if some problem is causing the node not to respond, or if the fix request failed to reach the node. Confirm the connection to the node, and reapply the fix if necessary.
Please contact your Compaq customer support representative with the text of this event. The event text is also recorded in the event log.
A high buffered I/O rate can cause high system overhead. If this is affecting overall system performance, use the I/O
Summary to determine the high buffered
I/O processes, and adjust their priorities or suspend them as needed.
Use the CPU Mode Summary to determine which processes are competing for CPU resources. Possible adjustments include changing process priorities and suspending processes.
(continued on next page)
B–4 Tables of Events
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event Description Explanation Recommended Action
HIDIOR High direct
I/O rate
HIHRDP High hard page fault rate
HIMWTQ Many processes
HINTER
HIPWIO waiting in
MWAIT
High interrupt mode time
High paging write I/O rate
HIPWTQ Many processes waiting in
COLPG,
PFW, or FPG
HISYSP
HITTLP
High system page fault rate
High total page fault rate
HMPSYN High multiprocessor
(MP) synchronization mode time
KTHIMD Kernel thread waiting for inner-mode semaphore
The average direct I/O rate on the node exceeds the threshold.
The average hard page fault rate on the node exceeds the threshold.
The average number of processes on the node in the Miscellaneous
Resource Wait (MWAIT) queues exceeds the threshold.
The average percentage of time the node spends in interrupt mode exceeds the threshold.
The average paging write I/O rate on the node exceeds the threshold.
The average number of processes on the node that are waiting for page file space exceeds the threshold.
The node’s average page fault rate for pageable system areas exceeds the threshold.
The average total page fault rate on the node exceeds the threshold.
The average percentage of time the node handles multiprocessor
(MP) synchronization exceeds the threshold.
The average percentage of time that the kernel thread waits for the inner-mode semaphore exceeds the threshold.
A high direct I/O rate can cause high system overhead. If this is affecting overall system performance, use the I/O
Summary to determine the high direct
I/O processes, and adjust their priorities or suspend them as needed.
A high hard page fault indicates that the free or modified page list is too small.
Check Chapter 6 for possible actions.
Use the CPU and Single Process pages to determine which resource is awaited.
See Chapter 6 for more information about wait states.
Consistently high interrupt time prohibits processes from obtaining CPU time. Determine which device or devices are overusing this mode.
Use the Process I/O and Memory
Summary pages to determine which processes are writing to the page file excessively, and decide whether their working sets need adjustment.
Use the CPU Process States and Memory
Summary to determine which processes are in the COLPG, PFW, or FPG state.
COLPG and PFW processes might be constrained by too little physical memory, too restrictive working set quotas, or lack of available page file space. FPG processes indicate too little physical memory is available.
These are page faults from pageable sections in loadable executive images, page pool, and the global page table. The system parameter SYSMWCNT might be set too low. Use AUTOGEN to adjust this parameter.
Use the Memory Summary to find the page faulting processes, and make sure that their working sets are set properly.
High synchronization time prevents other devices and processes from obtaining CPU time. Determine which device is overusing this mode.
Use SDA to determine which kernel thread of the process has the semaphore.
(continued on next page)
Tables of Events B–5
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event Description Explanation Recommended Action
LCKBLK
LCKCNT
LOBIOQ
LOBYTQ
LODIOQ
LOENQU
Lock blocking
Lock contention
The process holds the highest priority lock in the resource’s granted lock queue. This lock is blocking all other locks from gaining access to the resource.
The resource has a contention situation, with multiple locks competing for the same resource.
The competing locks are the currently granted lock and those that are waiting in the conversion queue or in the waiting queue.
LCKWAT Lock waiting The process that has access to the resource is blocking the process that is waiting for it. Once the blocking process releases its access, the next highest lock request acquires the blocking lock.
LOASTQ Process has used most of ASTLM quota
Process has used most of BIOLM quota
Process has used most of BYTLM quota
Process has used most of DIOLM quota
Process has used most of ENQLM quota
Either the remaining number of asynchronous system traps
(ASTs) the process can request is below the threshold, or the percentage of ASTs used compared to the allowed quota is above the threshold.
Either the remaining number of
Buffered I/Os (BIO) the process can request is below the threshold, or the percentage of BIOs used is above the threshold.
Either the remaining number of bytes for the buffered I/O byte count (BYTCNT) that the process can request is below the threshold, or the percentage of bytes used is above the threshold.
Either the remaining number of
Direct I/Os (DIOs) the process can request is below the threshold, or the percentage of DIOs used is above the threshold.
Either the remaining number of lock enqueues (ENQ) the process can request is below the threshold, or the percentage of ENQs used is above the threshold.
Use the Single Process Windows to determine what the process is doing. If the process is in an RWxxx state, try exiting the image or deleting the process.
If this fails, crashing the blocking node might be the only other fix option.
Use Lock Contention to investigate a potential lock contention situation. Locks for the same resource might have the
NODLCKWT wait flag enabled and be on every member of the cluster. Usually this is not a lock contention situation, and these locks can be filtered out.
If the blocking process holds the resource too long, check to see whether the process is working correctly; if not, one of the fixes might solve the problem.
If the amount used reaches the quota, the process enters RWAST state. If the process requires a higher quota, you can increase the ASTLM quota for the process in the UAF file. ASTLM is only a count; system resources are not compromised by increasing this count.
If the amount used reaches the quota, the process enters RWAST state. If the process requires a higher quota, you can increasing the BIOLM quota for the process in the UAF file. BIOLM is only a count; system resources are not compromised by increasing this count.
If the amount used reaches the quota, the process enters RWAST state. If the process requires a higher quota, you can raise the BYTLM quota for the process in the UAF file. BYTLM is the number of bytes in nonpaged pool used for buffered
I/O.
If the amount used reaches the quota, the process enters RWAST state. If the process requires a higher quota, you can increase the DIOLM quota for the process in the UAF file. DIOLM is only a count; system resources are not compromised by increasing this count.
If the limit reaches the quota, the process is not able to make further lock queue requests. If the process requires a higher quota, you can increase the ENQLM quota for the process in the UAF file.
(continued on next page)
B–6 Tables of Events
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event Description Explanation Recommended Action
LOFILQ
LOMEMY
Process has used most of FILLM quota
Free memory is low
LOPGFQ Process has used most of
PGFLQUOTA quota
LOPGSP
LOPRCQ
LOSTVC
LOSWSP
LOTQEQ
LOVLSP
Low page file space
Process has used most of PRCLM quota
Lost virtual circuit to node
Low swap file space
Process has used most of TQELM quota
Low disk volume free space
Either the remaining number of files the process can open is below the threshold, or the percentage of files open is above the threshold.
For the node, the percentage of free memory compared to total memory is below the threshold.
Either the remaining number of pages the process can allocate from the system page file is below the threshold, or the percentage of pages allocated is above the threshold.
Either the remaining number of pages in the system page file is below the threshold, or the percentage of page file space remaining is below the threshold.
Either the remaining number of subprocesses the current process is allowed to create is below the threshold, or the percentage of created subprocesses is above the threshold.
The virtual circuit between the listed nodes has been lost.
Either the remaining number of pages in the system page file is below the threshold, or the percentage of page file space remaining is below the threshold.
Either the remaining number of
Timer Queue Entries (TQEs) the process can request is below the threshold, or the percentage of
TQEs used to the allowed quota is above the threshold.
Either the remaining number of blocks on the volume is below the threshold, or the percentage of free blocks remaining on the volume is below the threshold.
If the amount used reaches the quota, the process must first close some files before being allowed to open new ones. If the process requires a higher quota, you can increase the FILLM quota for the process in the UAF file.
Use the automatic Purge Working Set fix, or use the Memory and CPU Summary to select processes that that are either not currently executing or not page faulting, and purge their working sets.
If the process requires a higher quota, you can raise the PGFLQUOTA quota for the process in the UAF file. This value limits the number of pages in the system page file that the account’s processes can use.
Either extend the size of this page file or create a new page file to allow new processes to use the new page file.
If the amount used reaches the quota, the process is not allowed to create more subprocesses. If the process requires a higher quota, you can increase the
PRCLM quota for the process in the UAF file.
Check to see whether the second node listed has failed or whether the connection between the nodes is broken.
The VC name listed in parentheses is the communication link between the nodes.
Either increase the size of this page file, or create a new page file to allow new processes to use the new page file.
If the amount used reaches the quota, the process enters RWAST state. If the process requires a higher quota, you can raise the TQELM quota for the process in the UAF file. TQELM is only a count; system resources are not compromised by raising it.
You must free up some disk volume space. If part of the purpose of the volume is to be filled, such as a page/swap device, then you can filter the volume from the display.
(continued on next page)
Tables of Events B–7
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event
LOWSQU
Description
LOVOTE Low cluster votes
LOWEXT Low process working set extent
Low process working set quota
Explanation
The difference between the number of VOTES and the
QUORUM in the cluster is below the threshold.
The process page fault rate exceeds the threshold, and the percentage of working set size compared to working set extent exceeds the threshold.
The process page fault rate exceeds the threshold, and the percentage of working set size exceeds the threshold.
Recommended Action
Check to see whether voting members have failed. To avoid the hang that results if VOTES goes below QUORUM, use the Adjust Quorum fix.
This event indicates that the
WSEXTENT value in the UAF file might be too low. The process needs more physical memory but cannot obtain it; therefore, the process page faults excessively.
This event indicates the process needs more memory but might not be able to obtain it because one of the following is true:
• The WSQUOTA value in the UAF file is set too low for the size of memory allocation requests or
• The system is memory constrained.
LRGHSH
NOPGFL
NOPLIB
NOPRIV
NOPROC Specific process not found
NOSWFL
PKTFER
Remote lock hash table too large to collect data on
No page file
No program library
Not allowed to monitor node
No swap file
Packet format error
The Availability Manager cannot investigate the node’s resource hash table (RESHASHTBL). It is either too sparse or too dense to investigate efficiently.
The Availability Manager cannot find a page file on the node.
The program library for the combination of hardware architecture and OpenVMS version was not found.
The Availability Manager cannot monitor the node due to unmatched security triplets.
The Availability Manager cannot find the process name selected in the Process Name Search dialog box on the Node Summary page.
The Availability Manager cannot find a swap file on the node.
The data packet sent to the remote node was not in the correct format for the remote node to process.
This event indicates that the Availability
Manager will take too many collection iterations to analyze lock contention situations efficiently. Make sure that the
SYSGEN parameter RESHASHTBL is set properly for the node.
Use SYSGEN to create and connect a page file on the node.
Check to see that all the program library files exist in the program library directory.
See Chapter 6 for details on setting up security.
This event can occur because the listed process no longer exists, or the process name is listed incorrectly in the dialog box.
If you do not use swap files, you can ignore this event. Otherwise, use
SYSGEN to create and connect a swap file for the node.
Please contact your Compaq customer support representative with the full text of the event, the version of the
Availability Manager, the configuration of the node running the Availability
Manager, and the configuration of the nodes being monitored.
(continued on next page)
B–8 Tables of Events
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event
PLIBNP
PLIBUR
PRBIOR
PRBIOW
PRCCOM
PRCCUR
PRCMWT
PRCPSX
Description
No privilege to access program library
Unable to read program library
High process buffered I/O rate
Process waiting for buffered I/O
Process waiting in
COM or
COMO
Process has a high CPU rate
PRCMUT Process waiting for a mutex
Process waiting in
MWAIT
Process waiting in
PSXFR
PRCPUL Most of
CPULIM process quota used
PRCPWT Process waiting in
COLPG,
PFW or FPG
Explanation
Unable to access the program library.
Recommended Action
Check to see that the Availability
Manager has the proper security access to the program library file.
Unable to read the program library for the combination of hardware architecture and
OpenVMS version.
The average buffered I/O rate of the process exceeds the threshold.
The average percentage of time the process is waiting for a buffered I/O to complete exceeds the threshold.
The average number of processes on the node in the COM or COMO queues exceeds the threshold.
The average percentage of time the process is currently executing in the CPU exceeds the threshold.
The program library is either corrupt or from a different version of the
Availability Manager. Restore the program library from the last installation.
If the buffered I/O rate is affecting overall system performance, lowering the process priority or suspending the process would allow other processes to obtain access to the CPU.
Use SDA on the node to ensure that the device to which the process is performing buffered I/Os is still available and is not being overused.
Use the CPU Summary to determine which processes should be given more
CPU time, and adjust process priorities and states accordingly.
Make sure that the listed process is not looping or preventing other processes from gaining access to the CPU. Adjust process priority or state as needed.
Use SDA to help determine which mutex the process is waiting for and to help determine the owner of the mutex.
The average percentage of time the process is waiting for a particular system mutex exceeds the threshold.
The average percentage of time the process is in a Miscellaneous
Resource Wait (MWAIT) state exceeds the threshold.
Various resource wait states are part of the collective wait state called MWAIT.
See Appendix A for a list of these states.
The CPU Process page and the Single
Process page display which state the process is in. Check the Single Process page to determine which resource the process is waiting for and whether the resource is still available for the process.
The average percentage of time the process waits during a
POSIX fork operation exceeds the threshold.
The remaining CPU time available for the process is below the threshold.
The average percentage of time the process is waiting to access the system page file database exceeds the threshold.
Make sure the CPU time allowed for the process is sufficient for its processing needs. If not, increase the CPU quota in the UAF file of the node.
Check to make sure the system page file is large enough for all the resource requests being made.
(continued on next page)
Tables of Events B–9
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event
PRCRWA
PRCRWC
PRCRWM
PRCRWP
PRCRWS
PRDIOW
Description
PRCQUO Process waiting for a quota
Process waiting in
RWAST
Process waiting in
RWCAP
Process waiting in
RWMBX
Process waiting in
RWPAG,
RWNPG,
RWMPE, or
RWMPB
Process waiting in
RWSCS,
RWCLU, or
RWCSV
PRCUNK Process waiting for a system resource
PRDIOR High process direct I/O rate
Process waiting for direct I/O
Explanation Recommended Action
The average percentage of time the process is waiting for a particular quota exceeds the threshold.
The average percentage of time the process is waiting in the RWAST state exceeds the threshold. RWAST indicates the process is waiting for an asynchronous system trap to complete.
The average percentage of time the process is waiting in the RWCAP state exceeds the threshold. RWCAP indicates that the process is waiting for CPU capability.
The average percentage of time the process is waiting in the
RWMBX state exceeds the threshold. RWMBX indicates the process is waiting for a full mailbox to be empty.
The average percentage of time the process is waiting in the
RWPAG, RWNPG, RWMPE, or RWMPB state exceeds the threshold. RWPAG and RWNPG are for paged or nonpaged pool;
RWMPE and RWMPB are for the modified page list.
The average percentage of time the process is waiting in the
RWSCS, RWCLU, or RWCSV state exceeds the threshold. RWCSV is for the cluster server; RWCLU is for the cluster transition; RWSCS is for cluster communications. The process is waiting for a cluster event to complete.
The average percentage of time the process is waiting for an undetermined system resource exceeds the threshold.
The average direct I/O rate of the process exceeds the threshold.
The average percentage of time the process is waiting for a direct I/O to complete exceeds the threshold.
Use the Single Process pages to determine which quota is too low. Then adjust the quotas of the account in the
UAF file.
Use the Single Process pages to determine if RWAST is due to the process quota being set too low. If not, use
SDA to determine if RWAST is due to a problem between the process and a physical device.
When many processes are in this state, the system might be hung because not enough nodes are running in the cluster to maintain the cluster quorum. Use the Adjust Quorum fix to correct the problem.
Use SDA to help determine which mailbox the process is waiting for.
Processes in the RWPAG or RWNPG state can indicate you need to increase the size of paged or nonpaged pool, respectively. Processes in the RWMPB state indicate that the modified page writer cannot handle all the modified pages being generated. Refer to Chapter
6 for suggestions.
Use the Show Cluster utility to help investigate.
The state in which the process is waiting is unknown to the Availability Manager.
If the I/O rate is affecting overall system performance, lowering the process priority might allow other processes to obtain access to the CPU.
Use SDA on the node to ensure that the device to which the process is performing direct I/Os is still available and is not being overused.
(continued on next page)
B–10 Tables of Events
Tables of Events
Table B–1 (Cont.) OpenVMS Events
Event Description Explanation Recommended Action
PRLCKW
PRPGFL
PRPIOR
PTHLST
RESDNS
RESPRS
Process waiting for a lock
High process page fault rate
High process paging I/O rate
Path lost
Resource hash table dense
Resource hash table sparse
UEXPLB Using
OpenVMS program export library
UNSUPP Unsupported node
The average percentage of time the process is waiting in the control wait state exceeds the threshold.
The average page fault rate of the process exceeds the threshold.
The average page read I/O rate of the process exceeds the threshold.
The connection between the server and collection node has been lost.
The percentage of occupied entries in the hash table exceeds the threshold.
The percentage of occupied entries in the hash table is less than the threshold.
The program library for the combination of hardware architecture and OpenVMS version was not found.
The Availability Manager does not support this combination of hardware architecture and
OpenVMS version.
The control wait state indicates that a process is waiting for a lock. Although no locks might appear in Lock Contention, the awaited lock might be filtered out of the display.
The process is memory constrained; it needs an increased number of pages to perform well. Make sure that the working set quotas and extents are set correctly. To increase the working set quota temporarily, use the Adjust
Working Set fix.
The process needs an increased number of pages to perform well. Make sure that the working set quotas and extents are set correctly. To increase the working set quota temporarily, use the Adjust
Working Set fix.
Check to see whether the node failed or whether the LAN segment to the node is having problems. This event occurs when the server no longer receives data from the node on which data is being collected.
A densely populated table can result in a performance degradation. Use the system parameter RESHASHTBL to adjust the total number of entries.
A sparsely populated table wastes memory resources. Use the system parameter RESHASHTBL to adjust the total number of entries.
Check to see that all the program library files exist in the program library directory.
Check the product SPD for supported system configurations.
Tables of Events B–11
Tables of Events
Table B–2 Windows Events
Event Description Explanation
CFGDON Configuration done
NODATA
NOPRIV
PTHLST
Unable to collect performance data
Not allowed to monitor node
Path lost
The server application has made a connection to the node and will start collecting the data according to the Customize Data Collection options.
The Availability Manager is unable to collect performance data from the node.
The Availability Manager cannot monitor the node due to a password mismatch between the Data Collector and the Data
Analyzer.
The connection between the Data
Analyzer and the Data Collector has been lost.
PVRMIS Packet version mismatch
This version of the Availability
Manager is unable to collect performance data from the node because of a data packet version mismatch.
Recommended Action
An informational event to indicate that the node is recognized. No further investigation is required.
The performance data is collected by the
PerfServ service on the remote node.
Check to see that the service is up and running properly.
See Chapter 6 for details on setting up security.
Check if the node crashed or if the LAN segment to the node is having problems.
This event occurs when the server no longer receives data from the node on which data is being collected.
The version of the Availability Manager
Data Collector is more recent than the
Data Analyzer. To process data from the node, upgrade the Data Analyzer to correspond to the Data Collector.
B–12 Tables of Events
C
OpenVMS Events by Type of Data Collected
This appendix shows the events that can be signaled for each type of OpenVMS data collected. The events are categorized as follows:
• Threshold events (Table C–1)
• Nonthreshold events (Table C–2)
Appendix B describes these events in detail and provides recommended actions.
Table C–1 OpenVMS Threshold Events
Type of Data
Collected Event Description
Disk status DSKERR
DSKINV
DSKMNV
DSKOFF
DSKRWT
DSKUNA
DSKWRV
High disk error count
Disk is invalid
Disk in mount verify state
Disk device is off line
High disk RWAIT count
Disk device is unavailable
Wrong volume mounted
Disk volume DSKQLN
LOVLSP
High disk queue length
Low disk volume free space
Node summary HIBIOR
HICOMQ
HIDIOR
HIHRDP
HIMWTQ
HINTER
HIPWIO
HIPWTQ
HISYSP
HITTLP
HMPSYN
LOMEMY
High buffered I/O rate
Many processes waiting in COM or COMO
High direct I/O rate
High hard page fault rate
Many processes waiting in MWAIT
High interrupt mode time
High paging write I/O rate
Many processes waiting in COLPG, PFW, or FPG
High system page fault rate
High total page fault rate
High multiprocessor (MP) synchronization mode time
Free memory is low
(continued on next page)
OpenVMS Events by Type of Data Collected C–1
OpenVMS Events by Type of Data Collected
Table C–1 (Cont.) OpenVMS Threshold Events
Type of Data
Collected Event Description
Lock contention LCKCNT
LRGHSH
RESDNS
RESPRS
Single lock LCKBLK
LCKWAT
Single process KTHIMD
LOASTQ
LOBIOQ
LOBYTQ
LODIOQ
LOENQU
LOFILQ
LOPGFQ
LOPRCQ
LOTQEQ
LOWEXT
LOWSQU
PRBIOR
PRBIOW
PRCCOM
PRCCUR
PRCMUT
PRCPSX
PRCPUL
PRCPWT
PRCQUO
PRCRWA
PRCRWC
PRCRWM
PRCRWP
PRCRWS
PRCUNK
PRDIOR
Lock contention
Remote lock hash table too large to collect data
Resource hash table dense
Resource hash table sparse
Lock blocking
Lock waiting
Kernel thread waiting for inner-mode semaphore
Process has used most of ASTLM quota
Process has used most of BIOLM quota
Process has used most of BYTLM quota
Process has used most of DIOLM quota
Process has used most of ENQLM quota
Process has used most of FILLM quota
Process has used most of PGFLQUOTA quota
Process has used most of PRCLM quota
Process has used most of TQELM quota
Low process working set extent
Low process working set quota
High process buffered I/O rate
Process waiting for buffered I/O
Process waiting in COM or COMO
Process has a high CPU rate
Process waiting for a mutex
POSIX process waiting during fork operation
Most of CPULIM process quota used
Process waiting in COLPG, PFW, or FPG
Process waiting for a quota
Process waiting in RWAST
Process waiting in RWCAP
Process waiting in RWMBX
Process waiting in RWPAG, RWNPG, RWMPE, or
RWMPB
Process waiting in RWSCS, RWCLU, or RWCSV
Process waiting for a system resource
High process direct I/O rate
(continued on next page)
C–2 OpenVMS Events by Type of Data Collected
OpenVMS Events by Type of Data Collected
Table C–1 (Cont.) OpenVMS Threshold Events
Type of Data
Collected Event Description
PRDIOW
PRLCKW
PRPGFL
PRPIOR
Process waiting for direct I/O
Process waiting for a lock
High process page fault rate
High process paging I/O rate
Process I/O
Page/swap file
LOBIOQ
LOBYTQ
LODIOQ
LOFILQ
PRBIOR
PRDIOR
PRPIOR
LOPGSP
LOSWSP
NOPGFL
NOSWFL
LOVOTE
Process has used most of BIOLM quota
Process has used most of BYTLM quota
Process has used most of DIOLM quota
Process has used most of FILLM quota
High process buffered I/O rate
High process direct I/O rate
High process paging I/O rate
Low page file space
Low swap file space
No page file
No swap file
Low cluster votes Cluster summary
Memory
CPU process
LOWEXT
LOWSQU
PRPGFL
PRPIOR
PRCCOM
PRCCUR
PRCMWT
PRCPWT
Low process working set extent
Low process working set quota
High process page fault rate
High process paging I/O rate
Process waiting in COM or COMO
Process has a high CPU rate
Process waiting in MWAIT (See Appendix A for a breakdown of MWAIT state.)
Process waiting in COLPG, PFW, or FPG
OpenVMS Events by Type of Data Collected C–3
OpenVMS Events by Type of Data Collected
Table C–2 OpenVMS Nonthreshold Events
Type of Data Collected Event Description
Node-level event CFGDON
DPGERR
NOPRIV
PKTFER
Configuration done
Error executing driver program
Not allowed to monitor node
Packet format error
Program library error
Events generated by fixes
ELIBCR
ELIBNP
ELIBUR
NOPLIB
PLIBNP
PLIBUR
UEXPLB
UNSUPP
FXCPKT
FXCRSH
FXDCPR
FXDCWS
FXDLPR
FXEXIT
FXINPR
FXINQU
FXINWS
FXPGWS
FXPRIV
FXQUOR
FXRESM
FXSUSP
FXTIMO
FXUERR
Bad CRC for exportable program library
No privilege to access exportable program library
Unable to read exportable program library
No program library
No privilege to access program library
Unable to read program library
Using exportable program library
Unsupported node
Received a corrupt fix response packet from node
Crash node fix
Decrement process priority fix
Decrement process working set size fix
Delete process fix
Exit image fix
Increment process priority fix
Increment process quota limits fix
Increment process working set size fix
Purge working set fix
No privilege to attempt fix
Adjust quorum fix
Resume process fix
Suspend process fix
Fix timeout
Unknown error code for fix
C–4 OpenVMS Events by Type of Data Collected
A
Access control lists (ACLs), 1–9
Adapters
See LAN adapters
Adjust AST Queue Limit fix, 6–18
Adjust Quorum fix, 6–6
Adjust Working Set fix, 6–14
AMDS$AM_CONFIG logical name, 7–22
AMDS$AM_LOG:ANALYZEREVENTS.LOG file on OpenVMS systems, 5–5
AMDS$AM_LOGICALS.COM file, 7–4
AMDS$CONSOLE_ACCESS.DAT file, 7–23
AMDS$DRIVER_ACCESS.DAT file, 7–22
AMDS$GROUP_NAME logical name, 7–4
AMDS$SYSTARTUP_VMS.COM file, 2–1
AnalyzerEvents.log file on Windows systems, 5–5
APCs (asynchronous procedure calls), 3–6
Application window components, 2–4 how to display data, 2–5 how to use, 2–2 menu bar, 2–4 panes, 1–3
ASTLM (AST limit) quota, B–6
Asynchronous procedure calls (APCs), 3–6
Asynchronous system traps (ASTs)
Adjust AST Queue Limit fix, 6–18
Attempting collection phase, 2–2
Automatic data collection, 1–6
AVAIL/AVAIL command to start Availability Manager, 2–2
Availability Manager
URL, 2–1
Availability messages sent to Data Analyzer, 7–24
B
Background data collection, 1–5
Blocks in use, remaining, 7–10
Buffered I/O byte limit (BYTLM), 3–15 limit, 3–15
Index
Buffered I/O (cont’d) rate, 3–14, 7–11, B–4
Buffered I/O (BIO) fix, 6–17
Byte limit remaining for process I/O, 3–15
C
Channels definition, 4–13 details, 4–25
LAN virtual circuit, 4–21, 4–22 summary data, 4–14
Circuits with individual nodes, 4–2
Cluster interconnects fixes, 6–25
Clusters
See OpenVMS Clusters
Collecting data
See Data collection
Collection intervals, 1–4, 3–1
Command procedures user action, 7–16
Commands user action, 7–16
Configuration, 1–3
Congestion control transmitting data, 4–20
Connection failed phase, 2–2
CPU modes
OpenVMS, 3–6, 3–7
Windows, 3–5
CPU process states, A–1
CPUs (central processing units) improving performance by suspending, 6–11 modes, 3–5 summary information, 3–5 number active on a node, 3–4 process states, A–1 process summary, 3–8 setting process priorities, 6–13 usage, 3–5 wait state, 3–8
Crash Node fix, 6–5
Customizing access codes, 7–23 events, 5–1
Index–1
Customizing (cont’d) node selection, 7–1
OpenVMS data collection, 7–5 data filters, 7–7 events, 7–15 group membership, 7–4 security features, 7–20 specifying nodes to monitor, 7–2 security features, 7–20 security triplets, 7–22
Windows events, 7–15 group membership, 7–4 security features, 7–20 specifying nodes to monitor, 7–2
D
Data Analyzer description, 1–3 event log files, 5–5 nodes, 1–3 passwords, 1–8 security, 1–8 starting on OpenVMS Alpha, 2–2 starting on Windows, 2–2
Data collection automatic, 1–6 background, 1–5 changing collection intervals, 7–6 customization selecting data to collect, 2–7 customizing settings, 7–5 default, 2–8 definition of one, 1–6 events associated with, 1–6 foreground, 1–6 frequency of, 1–6 intervals, 1–6 phase, 2–2 specifying types, 2–7
Data Collector for DECamds and Availability Manager, 2–1 installing from latest kit, 2–1 nodes, 1–3 restarting, 7–4
RMDRIVER, 4–1 security private LAN transport, 1–9 read and write access, 1–9 security triplets, 1–8
Data filters changing values, 7–7
Data packets receipt, 4–19 transmission, 4–18
DECamds, 1–1 changes and enhancements no installation of server, 2–1
Deferred procedure calls (DPCs), 3–5
Delete Process fix, 6–8
DIOLM (Direct I/O limit), 3–15
Direct I/O fix, 6–16
Direct I/O rate, 3–14
Disk status filtering data, 7–8
Disks
OpenVMS single disk summary, 3–18 status summary, 3–16 summaries, 3–16 volume summary, 3–19
Windows logical summary, 3–20, 3–21 physical summary, 3–21
Display data collection interval, 1–7
E
ECS criteria, 4–30
Equivalent Channel Set
See ECS
Error messages
CPU, 3–24
Escalation of events, 7–16
Event data collection interval, 1–7
Event pane, 2–4, 5–1
Events definition, 1–6 displaying information, 5–2, 5–6 escalation, 7–16 log files, 5–5 occurrence value, 7–16
OpenVMS, B–1 posting, 1–7 severity, 5–2, 7–15 signaling performance problems, 1–5 testing for, 5–1 threshold defaults, 4–3 thresholds, 7–16 thresholds for posting, 1–8 user actions, 7–16
Windows, B–12
Exit Image fix, 6–9
Extended LAN communication between Data Collector and
Data Analyzer, 1–3
Index–2
F
File protection for security, 1–9
Filtering data methods, 7–1
Filters
OpenVMS CPU, 7–7
OpenVMS disk status, 7–8
OpenVMS disk volume, 7–10
OpenVMS I/O, 7–11
OpenVMS lock contention, 7–12
OpenVMS memory, 7–13
OpenVMS page/swap file, 7–14 specifying types of data to collect, 7–7
Fixes adjusting AST queue limit, 6–18 adjusting buffered I/O count limit, 6–17 adjusting creation limit of subprocess, 6–22 adjusting direct I/O count limit, 6–16 adjusting I/O byte limit, 6–23 adjusting lock queue limit, 6–20 adjusting open file limit, 6–19 adjusting pagefile quota limit, 6–24 adjusting quorum, 6–6 adjusting resource limits, 6–15 adjusting time queue entry limit, 6–21 adjusting working set size, 6–14 changing process priority, 6–12
CMKRNL privilege required, 6–4 crashing a node, 6–5 deleting a process, 6–8 description, 6–1 exiting an image, 6–9
LAN adapter adjusting priority, 6–34 setting maximum buffer, 6–35 starting adapter, 6–36 stopping adapter, 6–37
LAN checksumming, 6–29
LAN path adjusting priority, 6–31 changing hops, 6–32 setting maximum packet size, 6–33
LAN virtual circuit adjusting maximum receive window size,
6–28 adjusting maximum transmit window size,
6–27 compression, 6–30 list of available, 6–1 memory usage, 6–2, 6–3 problems and recommended fixes, 6–3 purging a working set, 6–13, 6–14 results, 6–4 resuming a process, 6–11 suspending a process, 6–10
Fixes (cont’d) system service calls associated with, 6–1, 6–3 types, 6–1
Foreground data collection, 1–6
G
Graphical user interface
See GUI
Group pane, 2–3
See also Groups, Panes selecting a group, 2–5
Groups
See also Group pane, Panes changing, 7–4 selecting for monitoring, 2–5, 7–2 setting up, 2–5 user-definable, 2–6
GUI (graphical user interface), 1–1
H
Hardware security triplet address, 7–22
Hardware model, 3–4
Help
See Online help
Hung cluster fix, 6–3
I
I/O (input/output) adjusting AST limits fix, 6–16 current, threshold, and peak values, 3–14 default data collection, 7–6 page fault rate, 3–11 page/swap files, 3–15 process quotas, 3–28 rates per process, 3–15 summaries, 3–13
I/O byte fix, 6–23
IEEE 802.3 Extended Packet format protocol, 1–3
Increasing resource limits fix, 6–15
Interrupts per second, 3–6
Intruder fix, 6–3
IPID (internal PID), 3–7
J
Java GUI, 1–1
Job quotas in use single process, 3–30
JOB_CONTROL process, 6–14
Index–3
L
LAN
See LAN adapters, LAN fixes, LAN paths displays, 4–1
LAN adapters details, 4–32 errors data, 4–35 events data, 4–35 overview data, 4–32 receive data, 4–34 transmit data, 4–33 fixes, 6–34
LAN channels, 4–2 details counters data, 4–27
ECS criteria data, 4–30 errors data, 4–28 overview data, 4–26 remote system data, 4–29 details data, 4–25 fixes, 6–31 summary data, 4–13
LAN fixes, 6–24 adjusting adapter priority, 6–34 adjusting priority, 6–31 changing channel hops, 6–32 setting maximum packet size, 6–33, 6–35 starting adapter, 6–36 stopping adapter, 6–37
VC checksumming, 6–29
VC compression, 6–30
VC maximum receive window size, 6–28
VC maximum transmit window size, 6–27
LAN paths, 4–2
LAN virtual circuits, 4–2 detailed data, 4–17 fixes, 6–26
PEdriver, 4–2 summary data, 4–11
LAVC
See NISCA and SCS
Local area networks (LANs), 1–1
Lock contention
OpenVMS, 3–22, 7–6
Lock queue limit fix, 6–20
Locks contention for, 3–22
Logical disks
Windows, 3–21
Low node memory fix, 6–3
M
Managed objects support for, 4–1
Memory, 3–4 count, 3–11 data, 7–13 default data collection, 7–6 low memory fix, 6–3
OpenVMS summary, 3–10 summaries, 3–8 total for a node, 3–4
Windows summary, 3–8
Memory usage displaying, 3–10 fixes, 6–3
Menu bar in Application window, 2–4
Modes
See CPU modes
Monitoring nodes selecting nodes, 7–2
Mutexes held, 3–27 number in node, 3–3
MWAIT state resource wait table, A–2
N
Network address security triplet, 7–22
Network Interconnect for the System
Communications Architecture
See NISCA
Network protocol, 1–2
NISCA
LAN adapters, 4–2
LAN channels, 4–2
LAN paths, 4–2
LAN virtual circuits, 4–2
NISCA transport protocol, 4–17
Node data
OpenVMS, 3–2 summary, 3–4
Windows, 3–3
Node pane, 2–4
See also Nodes data in OpenVMS display, 3–2 data in Windows display, 3–3 displaying additional information, 2–6
Windows, 3–2
Nodes
See also Node pane adjusting quorum, 6–6 crashing a node, 6–5
Index–4
Nodes (cont’d) displaying data, 3–1 displaying in Node pane, 2–6 fixes, 6–1, 6–5 memory usage, 3–10
OpenVMS, 3–2 specifying data to collect, 2–7 summary information, 3–4
NoEvent data collection interval, 1–7
Nonpaged pool displaying size, 3–9
O
Occurrence counters definition, 5–1
Occurrences criterion for posting an event, 1–8 event, 1–8 low values, 7–16
Online help, 2–9
Open file limit fix, 6–19
OpenVMS Clusters hung, 6–3 interconnect summary, 4–2 members data, 4–2, 4–3 running Availability Manager in, 1–3 summary data, 4–2, 4–3
OS (operating system) version, 3–4
P
Packets discarded
LAN virtual circuit, 4–24
Page faults, 3–14
Adjust Working Set fix, 6–14
Purging Working Set fix, 6–14 rate, 3–11
Page files data collection, 7–6
Page/swap files, 3–15
Paged pool displaying size, 3–9
Pagefile quota fix, 6–24
Paging write I/O rate, 3–14
Panes
Application window, 1–3, 2–3 changing sizes, 2–4
Event, 2–4
Group, 2–3
Node, 2–4
Passwords, 1–8 changing, 7–20, 7–22, 7–25 default, 1–9 security triplets, 1–8
Path lost phase, 2–2
Performance identifying problems, 1–5
Physical disks
Windows, 3–21
PID (process identifier), 3–7, 3–11, 3–15
PIO (paging I/O) rate, 3–15
Pipe quota for transmitted data, 4–21
PRCCOM error message, 3–24
PRCCVR error message, 3–24
PRCLM process limit, B–7
PRCMWT error message, 3–24
PRCPWT error message, 3–24
Private LAN transport security, 1–9
Process limits fixes, 6–15
Process memory fixes, 6–2
Process Priority fix, 6–2, 6–3, 6–12
Process quotas adjusting, 6–3 displaying data, 3–28
Processes adjusting limits, 6–2 execution rates, 3–27 filtering data, 7–7 fixes, 6–1 information about, 3–24 job quotas, 3–30 looping process fix, 6–3 privileges, 1–9
Process Priority fix, 6–12 quotas displaying, 3–28
Resume Process fix, 6–11 runaway process fix, 6–3 single process data, 3–24
Suspend Process fix, 6–10 wait states, 3–29 working sets, 3–25
Purge Working Set fix, 6–13, 6–14
Q
Quotas adjusting, 6–3 job, 3–30 process I/O, 3–28 working set, B–5
R
Receiving information, 1–4
Requesting information, 1–4
Resource availability displaying, 5–1 fixes, 6–1
Restarting the Data Collector, 7–4
Index–5
Resume Process fix, 6–11
Runaway process
Process Priority fix, 6–3
Suspend Process fix, 6–3
S
SCA
LAN virtual circuits detailed data, 4–17
SCA (System Communications Architecture) summary data, 4–6
SCS
System Communications Services circuits data, 4–2
LAN channel data, 4–2
LAN path data, 4–2
LAN virtual circuit data, 4–2
LAN virtual circuits detailed data, 4–17
SCS (System Communications Services) connections data, 4–2, 4–8
Security, 1–8 access control lists (ACLs), 1–9 changing groups, 7–4 changing passwords, 7–20, 7–22, 7–25 data transfer, 1–9 file protection, 1–9 private LAN transport, 1–9 process privileges, 1–9 triplets, 1–8, 7–22
Security triplets access verification code, 7–22 changing, 7–22 description, 7–22 files, 1–9 format, 7–22 hardware address, 7–22 network address, 7–22 operation, 7–24 password, 7–22 verifying, 7–25 wildcard address, 7–23
Semaphores, 3–3
Single disks, 3–18
Single process data, 3–24
OpenVMS execution rates, 3–27 job quotas, 3–30 process I/O quotas, 3–28 process information, 3–25 wait states, 3–29 working set, 3–25
SMP (symmetric multiprocessing), 3–6
Sorting data, 2–8
Starting the Availability Manager, 2–2
Status bar in Application window, 2–5
Index–6
Subprocess adjusting creation limit, 6–22
Subprocess creation limit fix, 6–22
Suspend Process fix, 6–3, 6–10
Swap files data collection, 7–6
SWAPPER process displaying, 3–28 fixes ignored, 6–4
SYS$STARTUP directory, 2–1
SYSAPs (system applications)
See System applications (SYSAPs)
System applications (SYSAPs), 4–7
System cache displaying size in use, 3–9
System service calls associated with fixes, 6–3
T
Threads, 3–3
Thresholds criteria for posting an event, 1–8 events, 7–16
Timer Queue Entry Limit fix, 6–21
Title bar in Application window, 2–4
U
Uptime, 3–4
User action events, 7–16
User actions executing on OpenVMS system, 7–17 executing on Windows system, 7–18
V
Virtual circuits
LAN channel selection data, 4–21, 4–22 closures data, 4–23 congestion control data, 4–20 detailed data, 4–17 for individual nodes, 4–2 packets discarded data, 4–24 receive data, 4–19 summary data, 4–11 transmit data packets, 4–18
SCS connections data, 4–8
Virtual memory displaying size, 3–9
Volume default data collection, 7–6
W
Wait states
CPU, 3–8 process, 3–29
Wildcard address security triplet, 7–23
Working set extent, 3–11
Working sets data, 3–25 pages, 3–26 purging, 6–13 size, 3–11 size fix, 6–14 too high or too low, 6–3
Index–7
Download
Advertisement
Key features
Detects and corrects system availability problems
Collects and analyzes system data from OpenVMS and Windows environments
Identifies performance problems through data analysis
Posts events based on customizable thresholds and occurrences
Enables performance of corrective 'fixes' on nodes and processes
Offers customizable data collection and event notification
Maintains security for data analyzer and collector passwords
Monitors CPU modes, process summaries, memory, I/O, disk status, and lock contention
Frequently asked questions
Compaq Availability Manager software is used to detect and correct system availability problems.
The Data Analyzer supports Windows 2000 SP 2 or higher, Windows XP, and OpenVMS Alpha Version 7.1 or later.
The Availability Manager identifies performance problems by collecting and analyzing system data and posting events when specific thresholds or occurrences are met.
The Availability Manager can collect data on CPU modes, process summaries, memory, I/O, disk status, page/swap files, lock contention, and cluster interconnects for OpenVMS and Windows systems.
'Fixes' are corrective actions that can be performed through the Availability Manager to improve system availability, such as adjusting process priorities, managing memory, or resolving cluster interconnect issues.
The Availability Manager maintains security through password protection for the Data Analyzer and security triplet verification on OpenVMS Data Collector nodes to ensure authorized data collection and management.