Causes of invalid monitoring data – HP XP7 Storage User Manual
Page 137
Causes of Invalid Monitoring Data
If the value of monitoring data in CSV files is less than 0 (zero), consider the following causes:
Probable causes
Invalid values of monitoring
data
The value (-1) indicates that Performance Monitor failed to obtain monitoring data. Probable
reasons are:
The monitoring data in the
CSV file includes (-1).
•
Performance Monitor attempted to obtain statistics when an 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.
•
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
(for example, Continuous Access Synchronous, Continuous Access Synchronous Z,
Continuous Access Journal, or Continuous Access Journal Z). For details about the files,
see
,
, and
•
If Disable is selected to stop monitoring in the Monitoring Switch field on the Monitoring
Options window and longrange is specified as the sampling 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 sampling interval,
and collected monitoring data, the value (-1) is displayed as the monitoring data before
the CU was added.
•
If the CU number is not the monitoring target object, Performance Monitor cannot
obtain monitoring data from the CU. However, when the RemoteCopy,
UniversalReplicator, or URJNL operand is specified for the group subcommand, the
value (-1) is not displayed as the monitoring data even if the CU number is not the
monitoring target object. In that case, data on the monitored CU is added up and
output to the CSV file.
•
If no CU is specified as a monitoring target, the value (-1) is displayed as the monitoring
data.
The value (-3) indicates that Performance Monitor failed to obtain monitoring data for the
following reason:
The monitoring data in the
CSV file includes (-3).
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 value (-4) indicates that Performance Monitor failed to obtain monitoring data for the
following reason:
The monitoring data in the
CSV file includes (-4).
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).
When the CU number is not the monitoring target object, Performance Monitor cannot
obtain monitoring data from the CU.
The monitoring data in the
CSV file includes "-5".
If the PG, LDEV, LU, RCLU, RCLDEV, URLU, or URLDEV operand is specified, the value of
the monitoring data is "-5". To solve this problem, specify the CU as the monitoring target
object by using the Monitoring Options window of Performance Monitor (not by using the
Export Tool).
If the RemoteCopy, UniversalReplicator, or URJNL operand is specified, the value "-5" is
not output in the monitoring data though the CU number is not the monitoring target object.
In this case, data on monitored CUs are summed up and output into the CSV file.
Causes of Invalid Monitoring Data
137