Hitachi MK-96RD617-08 사용자 설명서
Using the Export Tool
7-69
Hitachi Universal Storage Platform V/VM Hitachi Performance Manager User’s Guide
Causes of Invalid Monitoring Data
If the value of monitoring data in CSV files is less than 0 (zero), consider the
following causes:
following causes:
Table 7-25 Causes of Invalid Monitoring Data
Invalid Values of
Monitoring Data
Probable Causes
The monitoring data in the
CSV file includes "-1".
CSV file includes "-1".
The value "-1" indicates that Performance Monitor failed to obtain
monitoring data. Probable reasons are:
monitoring data. Probable reasons are:
Performance Monitor attempted to obtain statistics when an
operation for rebooting the disk array is in progress.
operation for rebooting the disk array is in progress.
Performance Monitor attempted to obtain statistics when a heavy
workload is imposed on the disk array.
workload is imposed on the disk array.
There is no volume in a parity group.
Just after the CUs to be monitored were added, the Export Tool failed
to save files that contain monitoring data for all volumes or journal
volumes used by remote copy software (i.e., TrueCopy, TrueCopy for
z/OS, Universal Replicator, or Universal Replicator for z/OS). For
details about the files, see Table 7-10, Table 7-14, and Table 7-15.
to save files that contain monitoring data for all volumes or journal
volumes used by remote copy software (i.e., TrueCopy, TrueCopy for
z/OS, Universal Replicator, or Universal Replicator for z/OS). For
details about the files, see Table 7-10, Table 7-14, and Table 7-15.
If Disable is selected to stop monitoring in Monitoring Switch on
the Monitoring Options window and longrange is specified as the
gathering interval, the monitoring data for the period when
Performance Monitor stops monitoring is "-1".
the Monitoring Options window and longrange is specified as the
gathering interval, the monitoring data for the period when
Performance Monitor stops monitoring 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.
gathering interval, and collected monitoring data, the value
"-1" is displayed as the monitoring data before the CU was added.
The monitoring data in the
CSV file includes "-3".
CSV file includes "-3".
The value "-3" indicates that Performance Monitor failed to obtain
monitoring data for the following reason:
If IOPS is 0 (zero), the Response Time that is included in the
monitoring data for LUs, LDEVs, ports, WWNs, or external volumes is "-
3". Because IOPS is 0 (zero), the average response time becomes
invalid.
monitoring data for the following reason:
If IOPS is 0 (zero), the Response Time that is included in the
monitoring data for LUs, LDEVs, ports, WWNs, or external volumes is "-
3". Because IOPS is 0 (zero), the average response time becomes
invalid.
The monitoring data in the
CSV file includes "-4".
CSV file includes "-4".
The value "-4" indicates that Performance Monitor failed to obtain
monitoring data for the following reason:
If the period for the monitoring data that is specified with the Export
Tool does not match the collecting period for monitoring data, the
Export Tool cannot collect the monitoring data. If data of SVP is updated
while the monitoring data is being collected, the collected monitoring
data near the collection start time is "-4".
monitoring data for the following reason:
If the period for the monitoring data that is specified with the Export
Tool does not match the collecting period for monitoring data, the
Export Tool cannot collect the monitoring data. If data of SVP is updated
while the monitoring data is being collected, the collected monitoring
data near the collection start time is "-4".