HP StorageWorks P9000 Command View Advanced Edition Suite Software 7.1 Administrator Guide (web) (TB581-96050, May 2011)

The properties logger.hbase.loglevel, logger.hbase.MaxBackupIndex, and
logger.hbase.MaxFileSize are applied to the following files: HDvMtracen.log,
HDvMGuiTracen.log, and HDvMGuiMessagen.log.
The n in the file name indicates the backup generation number of the file.
The Windows event log is viewable in the Event Viewer. The default syslog is specified in /etc/
syslog.conf
logger.loglevel
In this property, you can specify the verbosity level for the trace.log.n, error.log.n,
CIMOMTracen.log, and SMISClientTracen.log (the n in the file name indicates the backup
generation number of the file). The values accepted in this field are (in decreasing order of detail):
DEBUG, INFO, WARN, ERROR, and FATAL. If this property is set to the default, entries whose verbosity
level is either INFO, WARN, ERROR, or FATAL are written into the trace.log.n. In this case, entries
whose verbosity level is DEBUG are not written into the logs.
Default: INFO
logger.MaxBackupIndex
In this property, you can specify the maximum number of backups 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. 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
Specifying Device Manager server properties312