HP StorageWorks P9000 Command View Advanced Edition Suite Software 7.1.1 Administrator Guide (web) (TB581-96065, September 2011)

The n in the file name indicates the backup generation number of the file. When a log file reaches
its maximum length, its filename is modified by appending a counter, as in access.log.1, for
example. As more backup log files are created, their counters or version suffixes are incremented (for
example, access.log.1 becomes access.log.2), until the specified number of backups have
been created. After that, the oldest backup log file is deleted each time a new backup is created.
Specifiable values are from 1 to 20.
Default: 10
logger.MaxFileSize
In this property, you can specify the maximum size for the access.log.n, cim_access.log.n,
error.log.n, service.log.n, stdout.log.n, stderr.log.n, statuscheck.log.n,
trace.log.n, CIMOMTracen.log, and SMISClientTracen.log (the n in the file name indicates
the backup generation number of the file). If the maximum size is exceeded, a new log file is created.
Unless KB is specified for kilobytes or MB for megabytes, the specified size is interpreted to mean
bytes.
Specifiable range: from 512 KB to 32 MB
Default: 1 MB
logger.hbase.loglevel
In this property, you can specify the verbosity level for each operation (trace) log file and error log
file written by Common Component. The log files are HDvMtracen.log, HDvMGuiTracen.log,
and HDvMGuiMessagen.log, where n is an integer that represents the backup number for the file.
Each logging event has its own importance level independent from its type (error, warning, and
information). The levels, in increasing order of importance, are: 30, 20, 10, and 0. The default logging
level for production systems is 20, which means that messages for logging event levels 20, 10, and
0 are written to HDvMtrace1.log, but messages for logging event level 30 are not.
Default: 20
logger.hbase.sysloglevel
In this property, you can specify the verbosity level for the operation (trace) log data and error log
data written to the event log (in Windows) or to syslog (in Linux) by Common Component. Each logged
event has its own importance level independent from its type (error, warning, and information). The
levels, in increasing order of importance, are: 30, 20, 10 and 0. The default logging level for
production systems is 0, which means that only messages for the logging event level 0 are written to
the event log (in Windows) or to syslog (in Linux), but messages for the logging event level 30, 20,
and 10 are not. The default value is recommended.
Default: 0
logger.hbase.MaxBackupIndex
In this property, you can specify the maximum number of backups for each trace and error log file
that is written by Common Component. The log files are HDvMtracen.log, HDvMGuiTracen.log,
and HDvMGuiMessagen.log (the n in the file name indicates the backup generation number of the
file). Valid values are from 1 to 16.
When a log file reaches its maximum length, its filename is modified by increasing a counter (for
example, HDvMtrace2). As more backup log files are created, their counters or version suffixes are
Administrator Guide (Web Version) 321