HP XP P9500 Storage - Manual (Page 102)

Probable causes Invalid values of monitoring
data
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.
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.
Troubleshooting the Export Tool
The following table explains possible problems with the Export Tool and probable solutions to the
problems.
Probable causes and recommended action Possible problems
The path to the Java Virtual Machine (Java.exe) might not be defined in the PATH
environment variable. If this is true, you must add that path to the PATH environment You cannot run the batch file.
variable. For information about how to add a path to the environment variable, see
the documentation for your operating system.
An incorrect version of Java Runtime Environment (JRE) might be installed on your
computer. To check the JRE version, enter the following command at the Windows
command prompt or the UNIX console window:Java -version If the version is
incorrect, install the correct version of JRE.
The Export Tool stops and the
processing does not continue. • The command prompt window might be in pause mode. The command prompt
window will be in pause mode if you click the command prompt window when
the Export Tool is running. To cancel pause mode, activate the command prompt
The command prompt window
was displaying progress of the
window and then press the <ESC> key. If a timeout of RMI occurs during pause
mode, the login will be canceled and an error will occur when you cancel pause
mode after the timeout. The error message ID will be (0001 4011).
export processing, but the
window stopped displaying
• If a memory size is not specified in a batch file, the Out Of Memory Error occurs
in JRE, the Export Tool might stop and the processing might not continue. Confirm
whether the specified memory size is correct or not. progress before the processing
stopped. The progress
information does not seem to be
updated anymore.
If the error message ID is (0001 4011), the user is forcibly logged off and the
processing stops because the Export Tool did not issue any request to SVP. The An error occurs and the
processing stops.
102 Export Tool