Causes Of Invalid Monitoring Data; Causes Of Invalid Monitoring Data - HP XP20000 User Manual

-Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log
sanproject.getmondat.RJMdMain
In the following example, a log file named export.log will be created in the log directory below
the current directory when the Export Tool executes:
Java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServer.jar"
-Xmx536870912 -Dmd.command=command.txt
-Dmd.logfile=export.log -Dmd.logpath=log sanproject.getmondat.RJMdMain
The symbol indicates the end of a command line.

Causes of Invalid Monitoring Data

If the value of monitoring data in CSV files is less than 0 (zero), consider the following causes:
Table 32 Causes of invalid monitoring data
Invalid Values of Monit-
oring Data
The monitoring data in
the CSV file includes "-1".
The monitoring data in
the CSV file includes "-3".
158 Using the Export Tool
Probable Causes
Cause — The value "-1" indicates that Performance Monitor failed to obtain
monitoring data for some reasons.
Reasons:
Performance Monitor attempted to obtain statistics when an operation for re-
booting the disk array is in progress.
A heavy workload is imposed on the disk array.
There is no volume in a parity group.
Just after the CUs to be monitored were added, Performance Monitor failed to
save files that contain monitoring data for all volumes or journal volumes used
by remote copy software (for example, XP Continuous Access, TrueCopy for
Mainframe, XP Continuous Access Journal, or Universal Replicator for Main-
frame). For details about the files, see
20 on page 113, and Table 21
If monitoring is stopped and longrange is specified as the gathering interval,
the monitoring data for the period is "-1".
If you added the CU during monitoring, specified longrange as the gathering
interval, and collected monitoring data. The value "-1" is displayed as the
monitoring data before the CU was added.
Cause — The value "-3" indicates that Performance Monitor failed to obtain
monitoring data.
Reason — If IOPS is 0 (zero), the Response Time of the monitoring data for: LUs,
LDEVs, ports, WWNs, or external volumes is -3. This happens because IOPS is 0
(zero) causing the average response time to become invalid.
Table 16 on page 108,
on page 114.
Table