Cisco TMSXE Administrator Guide 2.2
Page 40 of 60
Value
Meaning
-2
Off
-1
Errors Only
0
Errors and Info (default)
1023
Full debugging
LogMode
The LogMode value defines where the information for a particular component is logged to. Logging
can be to file or to OutputDebugString. When logging to OutputDebugString, you can use the freely
downloadable DebugView utility from Microsoft to capture and view the information in real-time.
DebugView can be found at
http://www.microsoft.com/technet/sysinternals/Miscellaneous/DebugView.mspx
To set the LogMode for a particular component, create a new String Value in the Cisco TMSXE
registry key whose name is
LogMode ComponentName
replacing ComponentName with one of the
valid Component names
.
When created, modify the string by double-clicking it and set the value to
the desired level from the list below
.
Value
Meaning
1
Log to file (default)
2
Log to OutputDebugString
Example:
Setting component ‗TANDBERG Configuration‘ to Debug Level Logging to file
Managing Log Files
All log files are written to the same directory. This directory is normally defined using the Configuration
tool, and can be seen in the registry key as string
Log directory
. When a component is set to log to
file, each component creates a separate log file named
ComponentName.log
in the log directory.
To prevent the logs from getting too big and taking up too much disc space, an administrator can
control the maximum file size and rotation of the log files. This is done globally, so all logs share the
same rotation and sizing rules. The size of files is controlled by the string value
Log Size
Log Size
This registry setting is used to control size. The log size is a string whose value is the maximum size
of a log files in bytes. To set the
Log Size
, create a new String Value in the Cisco TMSXE registry key
whose name is
Log Size .
When created, modify the string by double-clicking it and set the value to
the desired size in bytes. For e
xample setting the value to ‗10485760‘ for 10MB. This is also the
default value used if Log Size is not defined.
The log files will be rotated when a log hits its maximum size as defined by
Log Size
. When that
happens, the log file is renamed
ComponentName.bak
and a new
ComponentName.log
file is
created. If an existing
ComponentName.bak
file already exists, it is replaced by the newly rotated
log.