Administration
A31003-O1010-M100-17-76A9, 09/09/2010
3-190
OpenScape Voice - OpenStage Family, Administration Manual
administration.fm
Diagnostics
3.24.6
Fault Trace Configuration
Error tracing and logging can be configured separately for all components, i. e. the services and
applications running on the OpenStage phone. The resulting files can be viewed in the WBM
web pages over the
Download
links.
The
File size (bytes)
parameter sets the maximum file size. When it is reached, the data is
saved as old file, and a new file is generated. From then on, the trace data is written to the new
file. When the maximum file size is reached again, the data is saved as old file once more,
thereby overwriting the previous old file. The default value is 65536.
The
Trace timeout (minutes)
determines when to stop tracing. When the timeout is reached,
the trace settings for all components are set to OFF, but ERROR and STATUS messages are
still written to the trace file ad infinitum. When the trace file has reached its maximum size, the
data is saved, and a new file is created (for more information, see
File size (bytes)
above). If
the value is 0, the trace data will be written without time limit.
If
Automatic clear before start
is checked, the existing trace file will be deleted on pressing
the
Submit
button, and a new, empty trace file will be generated. By default, it is unchecked.
You can read the log files by clicking on the appropriate hyperlinks (the hyperlinks work only if
the file in question has been created). The following logs can be viewed:
•
Download trace file
The trace data according to the settings specified for the services.
•
Download boot file
(not present with V2)
The system messages of the booting process. With firmware version V2, these messages
will be incorparated in the syslog file (see
Download syslog file
underneath).
•
Download saved trace file
Normally, the trace file is saved only in the phone RAM. When the phone restarts in a con-
trolled manner, the trace file will be saved in permanent memory.
•
Download saved boot file
(not present with V2)
Normally, the boot file is saved only in the phone RAM. When the phone restarts in a con-
trolled manner, the boot file will be saved in permanent memory. With firmware version V2,
these messages will be incorparated in the syslog file (see
Download syslog file
under-
neath).
•
Download upgrade trace file
The trace log created during a software upgrade.
•
Download upgrade error file
The error messages created during a software upgrade. With firmware version V2, these
messages will be incorparated in the syslog file (see
Download syslog file
underneath).
>
The absolute maximum file size is 6 290 000 bytes. However, on OpenStage 15/20/
40 phones, a maximum size no greater than 500 000 bytes is recommended due to
the amount of available memory.
