HP StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide (December 2005)

Command View XP AE Device Manager Server Properties 122
The Windows
®
event log is located in the event viewer.
7-4-1 logger.loglevel
This property determines the verbosity level of operational (trace) and error logging. The values
accepted in this field are (in decreasing order of detail): DEBUG, INFO, WARN, ERROR, and FATAL.
The default logging level for production systems is INFO, which means that debugging or
informational entries as well as warnings and error messages are written into the trace and error logs.
Default: INFO
7-4-2 logger.MaxBackupIndex
This property sets the number of rolling backups to keep of each log file before the oldest is deleted. If
this property is set to zero, no rolling backups are created, and log files are simply truncated when
their maximum file size is reached. When a log file reaches its maximum length its filename is
modified by appending a counter, for example, access.log.1. As more backup log files are created,
their counter or version suffix is incremented (for example, access.log.1 becomes access.log.2), until
the specified number of rolling backups have been created. After that, the oldest backup log file is
deleted each time a new backup is created. You can specify a range of 1 to 20.
Default: 10
7-4-3 logger.MaxFileSize
This property allows you to specify the maximum size for each log file. Unless KB is specified for
kilobytes or MB for megabytes, bytes is assumed. In this property, the term KB is interpreted as 1024
bytes, and MB as 1024 kilobytes.
Specifiable range: from 512 KB to 32 MB
Default: 1 MB
7-4-4 logger.hicommandbase.loglevel
This property determines the verbosity level of operational (trace) and error logging which writes into
HDvMtrace1.log by Common Component. 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 into the HDvMtrace1.log, but
messages for logging event level 30 are not.
Default: 20
7-4-5 logger.hicommandbase.sysloglevel
This property determines the verbosity level of operational (trace) and error logging which writes into
the EventLog (Windows
®
) by Common Component. 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 0, which means
that messages for only the logging event leveled 0 are written into the EventLog (Windows
®
), but
messages for the logging event leveled 30, 20, and 10 are not. The default value is recommended.
Default: 0
7-4-6 logger.hicommandbase.MaxBackupIndex
This property sets the maximum number of files to keep of the HDvMtrace1 log file before the oldest is
deleted. Valid values are between 1 and 16. When a log file reaches its maximum length, its filename
is modified by increasing a counter (e.g., for example, HDvMtrace2). As more backup log files are
created, their counter or version suffix is incremented (e.g., HDvMtrace2.log becomes
HDvMtrace3.log), until the specified number of rolling backups have been created. After that, the
oldest backup log file is deleted each time a new backup is created.
Default: 10