Causes of invalid monitoring data
If the value of monitoring data in CSV files is less than 0 (zero), consider the following causes:
|
Invalid values of monitoring data |
Probable causes |
|
The monitoring data in the CSV file includes (-1). |
The value (-1) indicates that Performance Monitor failed to obtain monitoring data. Probable reasons are:
|
|
The monitoring data in the 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. |
|
The monitoring data in the 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 Export Tool does not match the collecting period for monitoring data, 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). |
|
The monitoring data in the CSV file includes "-5". |
When the CU number is not the monitoring target object, Performance Monitor cannot obtain monitoring data from the CU. 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 Export Tool). If the RemoteCopy, Universal Replicator, 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. |
