 |
HP OpenVMS System Management Utilities Reference
Manual
MONITOR CLUSTER
The MONITOR CLUSTER command initiates monitoring of the CLUSTER
statistics class, which shows clusterwide CPU, memory, disk, and
locking activity.
Format
MONITOR CLUSTER
Command Qualifiers
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier
Descriptions section.
Classname Qualifiers
/ALL
Specifies that a table of all available statistics (current, average,
minimum, and maximum) is to be included in the display and summary
output. For summary output, this qualifier is the default for all
classes; otherwise, it is the default for all classes except CLUSTER,
MODES, PROCESSES, STATES, SYSTEM, and VECTOR.
/AVERAGE
Specifies that a bar graph of average statistics is to be included in
the display and summary outputs.
/CURRENT
Specifies that a bar graph of current statistics is to be included in
the display and summary outputs. The /CURRENT qualifier is the default
for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.
/MAXIMUM
Specifies that a bar graph of maximum statistics is to be included in
the display and summary outputs.
/MINIMUM
Specifies that a bar graph of minimum statistics is to be included in
the display and summary outputs.
Description
For the CLUSTER class, MONITOR collects data items for up to 48 nodes
in a cluster. Because this class combines the most significant
clusterwide performance statistics in a single display, it is
particularly useful to cluster managers and other users seeking an
overview of cluster activity.
MONITOR does not recognize nodes that enter the cluster while a request
is active. MONITOR, therefore, does not collect data for these nodes.
You cannot specify the CLUSTER class in the same request with any other
class.
In a multifile summary request, the classes CLUSTER and PROCESSES are
ignored. If these classes are the only classes specified on the command
line, MONITOR does not recognize them and displays a "no classes
specified" error message. MONITOR does not recognize these classes
if they are the only classes specified on the command line, and
displays a "no classes specified" error message.
The CLUSTER class includes the following data items:
| Data Item |
Description |
|
CPU Busy
|
Percentage of CPU in use; includes activity in all processor modes
(except Idle Time) for each node.
|
|
Percent Memory In Use
|
Memory in use on each node; calculated by dividing the Free List Size
by total available memory and subtracting the result from 100%.
|
|
I/O Operation Rate
|
Total rate of disk I/O operations on each disk by all nodes currently
active in the request.
In cluster configurations, the MSCP server software makes locally
attached and HSC disks available to other nodes. A node uses
remote access to a disk when it accesses the disk through
another VAX node (using the MSCP server). A node uses
direct access to a disk when it directly accesses a locally
attached or HSC disk.
An "R" following the device name indicates that the
displayed statistics represent I/O operations requested by nodes using
remote access.
If an "R" does not appear after the device name, the
displayed statistics represent I/O operations issued by nodes with
direct access. These I/O operations might include those issued by the
MSCP server on behalf of remote requests.
|
|
Total ENQ/DEQ Rate
|
Sum of all local, incoming, and outgoing ENQs, DEQs, and conversions.
|
Two display formats are provided, depending on the classname qualifier
specified:
- A tabular style format for the /ALL qualifier
- A bar graph style format for the /AVERAGE, /CURRENT, /MAXIMUM, and
/MINIMUM qualifiers
Beginning in OpenVMS Version 7.3, the range of rate fields has been
increased in the MONITOR CLUSTER screen display as follows:
| Rate Name |
Old Rate |
New Rate |
|
I/O Operation
|
0 - 25 - 50 - 75 - 100
|
0 - 125 - 250 - 375 - 500
|
|
Lock
|
Scale from 0 to 500
|
Scale from 0 to 1000
|
Note to Cluster Managers on MONITOR_SERVER Process
When users enter the MONITOR CLUSTER command, MONITOR activates the
image SYS$SYSTEM:VPM.EXE, which creates a process called
MONITOR_SERVER on each remote cluster node. (If users
specify the /NODE qualifier with the MONITOR CLUSTER command or with
any command of the form MONITOR class name, MONITOR creates the process
only on the specified nodes.) The server process gathers data from
remote nodes for live display or to record on the local node. To ensure
accurate and timely data collection, the process is started at priority
15. Because server processes consume minimal resources, they have no
significant effect on system performance.
By default, MONITOR_SERVER processes are started in the system DECnet
account, which is created when the NETCONFIG.COM command procedure
executes at bootstrap time. If this account is not present on your
system, you must either create it by executing NETCONFIG.COM, or
specify another account in which the server processes can be started.
If you want to start the processes in another account, use the
following sequence of commands to define VPM as known object 51 in the
DECnet database and associate the object with the desired account:
$ SET PROCESS/PRIVILEGE=SYSPRV
$ RUN SYS$SYSTEM:NCP
NCP> DEFINE OBJECT VPM NUMBER 51 -
_ FILE SYS$SYSTEM:VPM.EXE -
_ PROXY NONE -
_ ACCOUNT account -
_ USER user-id -
_ PASSWORD password
NCP> SET OBJECT VPM NUMBER 51 -
_ FILE SYS$SYSTEM:VPM.EXE -
_ PROXY NONE -
_ ACCOUNT account -
_ USERNAME user-id -
_ PASSWORD password
NCP> EXIT
$ SET PROCESS/PRIVILEGE=NOSYSPRV
|
For each server process, MONITOR creates a log file on the local node
to which information about server connection activity, including error
messages, is written. Note that error messages are written to the file
only when errors occur. A single version is maintained for the life of
the system. The default file specification has the form
SYS$COMMON:[SYSMGR]VPM$nodename.LOG. The node name portion of the
specification identifies the node on which the MONITOR_SERVER process
has been started.
If you want to change the default specification, you can redefine the
executive-mode logical name VPM$LOG_FILE in the system logical name
table on the appropriate nodes. For example, if you wanted to write
server error logging data to the file WRKD:[MONSERVER]VPM_ERRORS.LOG,
you would define VPM$LOG_FILE as follows:
$ DEFINE/SYSTEM/EXECUTIVE_MODE VPM$LOG_FILE -
_$ WRKD:[MONSERVER]VPM_ERRORS.LOG
|
To direct to a single file data for all MONITOR_SERVER processes on the
cluster, you could assign the logical name the same value on each
member system. Note that because the log files are created as shared
sequential files, multiple server processes can access them
simultaneously.
If you routinely monitor your cluster, you can reduce server startup
time significantly by creating MONITOR_SERVER processes on each member
node at bootstrap time and maintaining the processes for the life of
the system. To do so, add the following lines to the appropriate
site-independent startup command files:
$ DEFINE/SYSTEM/EXECUTIVE_MODE VPM$SERVER_LIVE TRUE
$ RUN/DETACH/PAGE_FILE=10000 SYS$SYSTEM:VPM.EXE
|
You can enter these commands interactively at any time if you have the
following privileges: ALTPRI, NETMBX, PSWAPM, SYSNAM, SYSPRV, and
TMPMBX.
Example
|
MONITOR> MONITOR CLUSTER/ALL
OpenVMS Monitor Utility
CLUSTER STATISTICS
on node CURLEY
29-APR-2003 12:25:13
CPU Busy CUR AVE MIN MAX
LARRY 100.00 100.00 100.00 100.00
CURLEY 100.00 99.83 100.00 100.00
MOE 8.52 8.50 8.52 8.52
OpenVMS Monitor Utility
CLUSTER STATISTICS
on node CURLEY
29-APR-2003 12:25:19
%Memory In Use CUR AVE MIN MAX
MOE 88.00 88.00 88.00 88.00
LARRY 78.00 78.00 77.00 78.00
CURLEY 72.00 72.50 72.00 72.00
OpenVMS Monitor Utility
CLUSTER STATISTICS
on node CURLEY
29-APR-2003 12:25:25
I/O Operation Rate CUR AVE MIN MAX
$111$DUA7: (DECEIT) SQMCLUSTERV4 0.48 6.53 0.48 10.41
$111$DUA6: (DECEIT) QUALD 1.93 1.07 0.00 1.93
$111$DUA4: (DECEIT) PAGESWAPDISK 1.44 0.96 0.00 1.44
$111$DUA2: (DECEIT) TSDPERF 0.32 0.53 0.16 1.12
LARRY$DRA3: QUALQUEST 0.00 0.21 0.00 0.64
MOE$DMA1: UVMSQAR 0.00 0.00 0.00 0.00
MOE$DRA5: USER01 0.00 0.00 0.00 0.00
LARRY$DRA4: TIMEDEV 0.00 0.00 0.00 0.00
LARRY$DBB3: REGLIB 0.00 0.00 0.00 0.00
$111$DUA3: (DECEIT) DUMPDISK 0.00 0.00 0.00 0.00
$111$DUA5: (DECEIT) BPMDISK 0.00 0.00 0.00 0.00
$111$DJA8: (DECEIT) ORLEAN 0.00 0.00 0.00 0.00
$111$DJA10: (DECEIT) QMISDATABASE 0.00 0.00 0.00 0.00
$111$DJA9: (DECEIT) MPI$DATA 0.00 0.00 0.00 0.00
|
OpenVMS Monitor Utility
CLUSTER STATISTICS
on node CURLEY
29-APR-2003 12:25:56
Tot ENQ/DEQ Rate CUR AVE MIN MAX
MOE 7.90 14.92 0.00 43.12
LARRY 20.48 14.64 0.00 46.92
CURLEY 1.93 13.29 0.00 57.30
|
|
The preceding example shows the tabular style format for the CLUSTER
display.
|
MONITOR> MONITOR CLUSTER/CURRENT
Statistic: CURRENT OpenVMS Monitor Utility 5-JUN-2003
10:46:53
CLUSTER STATISTICS
CPU | MEMORY
|
CPU Busy 0 25 50 75 100|%Memory In Use 0 25 50 75 100
+----+----+----+----+| +----+----+----+----+
BRS004 100 |********************|BRS004 37 |*******
| | |
| | |
| | |
| | |
| | |
-----------------------------------------+--------------------------------------
DISK | LOCK
|
I/O Operation Rate 0 125 250 375 500|Tot ENQ/DEQ Rate 0 250 500 750 1000
+----+----+----+----+| +----+----+----+----+
$1$DIA1: 52 |** |BRS004 183 |***
| | |
| | |
| | |
| | |
| | |
|
|
The preceding example shows the bar graph style format for a
CLUSTER/CURRENT display.
MONITOR DECNET
The MONITOR DECNET command initiates monitoring of the DECNET class,
which includes information about DECnet for OpenVMS network activity.
Format
MONITOR DECNET
Command Qualifiers
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier
Descriptions section.
Classname Qualifiers
/ALL
Specifies that a table of all available statistics (current, average,
minimum, and maximum) is to be included in the display and summary
output. For summary output, this qualifier is the default for all
classes; otherwise, it is the default for all classes except CLUSTER,
MODES, PROCESSES, STATES, SYSTEM, and VECTOR.
/AVERAGE
Specifies that a bar graph of average statistics is to be included in
the display and summary outputs.
/CURRENT
Specifies that a bar graph of current statistics is to be included in
the display and summary outputs. The /CURRENT qualifier is the default
for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.
/MAXIMUM
Specifies that a bar graph of maximum statistics is to be included in
the display and summary outputs.
/MINIMUM
Specifies that a bar graph of minimum statistics is to be included in
the display and summary outputs.
Description
The DECNET class consists of the following data items:
| Data Item |
Description |
|
Arriving Local Packet Rate
|
Rate at which local packets are being received.
|
|
Departing Local Packet Rate
|
Rate at which local packets are being sent.
|
|
Arriving Transit Packet Rate
|
Rate at which transit packets are arriving.
|
|
Transit Congestion Loss Rate
|
Rate of transit congestion loss.
|
|
Receiver Buffer Failure Rate
|
Rate of receiver buffer failures.
|
Example
|
MONITOR> MONITOR DECNET
OpenVMS Monitor Utility
DECNET STATISTICS
on node SAMPLE
29-APR-2003 22:22:44
CUR AVE MIN MAX
Arriving Local Packet Rate 9.54 5.08 0.00 11.25
Departing Local Packet Rate 9.22 4.66 0.00 10.92
Arriving Trans Packet Rate 0.00 0.00 0.00 0.00
Trans Congestion Loss Rate 0.00 0.00 0.00 0.00
Receiver Buff Failure Rate 0.00 0.00 0.00 0.00
|
|
This example shows that arriving and departing network packet rates
(including control packets) are roughly equivalent, and that network
activity is currently at a level higher than the average since
monitoring began, but not at its highest point.
MONITOR DISK
The MONITOR DISK command initiates monitoring of the DISK statistics
class. The maximum number of disks that can be monitored for record
output is 909, and for display and summary output is 1817.
Format
MONITOR DISK
Command Qualifiers
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier
Descriptions section.
Classname Qualifiers
/ALL
Specifies that a table of all available statistics (current, average,
minimum, and maximum) is to be included in the display and summary
output. For summary output, this qualifier is the default for all
classes; otherwise, it is the default for all classes except CLUSTER,
MODES, PROCESSES, STATES, SYSTEM, and VECTOR.
/AVERAGE
Specifies that a bar graph of average statistics is to be included in
the display and summary outputs.
/CURRENT
Specifies that a bar graph of current statistics is to be included in
the display and summary outputs. The /CURRENT qualifier is the default
for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.
/ITEM=(keyword[,...])
Selects one or more data items for inclusion in display and summary
outputs. If you specify two or more keywords, enclose them in
parentheses, and separate them with commas. When the /ITEM qualifier is
omitted, the default is /ITEM=OPERATION_RATE.
The following table describes /ITEM qualifier keywords:
| Keyword |
Description |
|
ALL
|
Specifies that statistics on all data items collected for the disks are
displayed on successive screens.
|
|
OPERATION_RATE
|
Specifies that I/O operation rate statistics are displayed for each
disk.
|
|
QUEUE_LENGTH
|
Specifies that the number of I/O request packets being serviced
(current or waiting) is displayed for each disk.
|
/MAXIMUM
Specifies that a bar graph of maximum statistics is to be included in
the display and summary outputs.
/MINIMUM
Specifies that a bar graph of minimum statistics is to be included in
the display and summary outputs.
/PERCENT
/NOPERCENT (default)
Controls whether statistics are expressed as percent values in display
and summary outputs. The /PERCENT qualifier is applicable only to the
DISK, MODES, SCS, and STATES classes.
Description
The DISK class is a component class. Data items for this class are
collected for each mounted disk device in a single-node or cluster
system. The DISK class consists of the following data items:
| Data Item |
Description |
|
I/O Operation Rate
|
Rate at which I/O operations occur on each disk. By comparing operation
rates for all disks in the system, you can tell which disks are busy
and which are idle. However, because this statistic does not provide
information about the time required for individual operations, use
discretion in interpreting it.
|
|
I/O Request Queue Length
|
Number of outstanding I/O request packets. Includes the request
currently being serviced and those awaiting service. Note that, for
greater precision, this item is always sampled at a 1-second interval,
regardless of the value specified with the /INTERVAL command qualifier.
The maximum number of disks that can be monitored is 909 for record
output and 1817 for display or summary output. In previous versions,
the limit was 799 disks for both types of output.
|
In the following example, typical of a cluster environment, note that
each disk is identified by three elements:
- Disk name ending in a colon.
- Name of the cluster node through which the disk is accessed. This
field appears only in the multiple-statistic display; it is not
included in single-statistic displays or multifile summaries.
- Volume label.
In cluster configurations, the MSCP server software makes locally
attached and HSC disks available to other nodes. A node uses
remote access to a disk when it accesses the disk through
another VAX node (using the MSCP server). A node uses direct
access to a disk when it directly accesses a locally attached or HSC
disk.
An "R" following the device name indicates that the displayed
statistics represent I/O operations requested by nodes using remote
access.
If an "R" does not appear after the device name, the
displayed statistics represent I/O operations issued by nodes with
direct access. These I/O operations might include those issued by the
MSCP server on behalf of remote requests.
Example
|
MONITOR> MONITOR DISK/ITEM=QUEUE_LENGTH
OpenVMS Monitor Utility
DISK I/O STATISTICS
on node SAMPLE
29-APR-2003 14:19:56
I/O Request Queue Length CUR AVE MIN MAX
SAMPLE$DBA0: SAMPLE09APR 0.00 0.00 0.00 0.00
SAMPLE$DRA2: SAMPLEPAGE 2.00 1.43 0.00 4.00
SAMPLE$DRB1: ACCREG 0.00 0.00 0.00 0.00
$1$DRA5: (MOE) MOE$$PAGE 0.00 0.00 0.00 0.00
$1$DBA3: (CURLEY) UMASTER 0.00 0.00 0.00 0.00
$1$DBA5: (CURLEY) MIDNITE 0.00 0.00 0.00 0.00
$2$DRA7: (LARRY) RES26APR 0.00 0.00 0.00 0.00
$2$DRB6: (LARRY) CLUSTERDUMP1 0.00 0.00 0.00 0.00
$255$DUA4: (SHEMP) RES06AUG 0.00 0.00 0.00 0.00
$255$DUA5: (SHEMP) VMSDOCLIB 0.00 0.00 0.00 0.00
|
|
This example, typical of a cluster environment, shows the number of I/O
packets awaiting service or in service for each disk. Note that the
device SAMPLE$DRA2 is the only device with a nonzero queue length.
Because MONITOR samples queue lengths every second, regardless of the
collection interval value, the precision of the data does not depend on
the collection interval.
|
