HP StorageWorks Command View SDM Installation and User Guide (T1086-96023, February 2005)

Array Logs 221
Array Logs
Performance Logs
In addition to the event logs, array performance data is logged. Performance
data is stored in a log structure similar to the event logs. Performance data is
logged continually while the array is in operation. A new performance log is
created every 24 hours beginning at 12:00 a.m. The array directory structure
is shown below:
../commandview/server/logs/performance/arrayuniquename/
YYYY-MM/dd-perf.log
An example of this directory structure for an array with a unique name of
“W6000123”, for February 28, 2000, would be:
../commandview/server/logs/performance/W600012/2000-02/
28-perf.log
For information on reading performance logs, refer to "armperf" on
page 148.
Port Statistics Log
A separate log file is used to store the port statistics metrics. These metrics
indicate low level port activity and errors. The port statistics logs use a
directory structure similar to that of the performance log, but the file name is
dd-portStatistics.log:
../commandview/server/logs/performance/arrayuniquename/
YYYY-MM/dd-portStatistics.log
Managing the Size of the Performance Log Files
You can configure the operating parameters to automatically limit the
performance log file size. This is done by adding the following parameters to
the PanConfigParams.txt file
PERFORMANCE_DB_MAX_SIZE=nnn
Sets the maximum amount of disk space in Mbytes that performance log
files can consume. Once this limit is reached, the oldest performance log
files are automatically deleted. A value of zero will not delete any logs.
PERFORMANCE_KEEP_MIN_LOGS=nn