Cisco Model D-PCG1000 PowerKEY CAS Gateway User Guide
4012159 Rev B
Enabling Tracing on the SARA Server
7-3
Enable Tracing,
Continued
Syntax For the trace.cfg File
You must enter the trace.cfg entries using the following syntax:
tracename programcontext tracelevel
The following table explains each component of the trace.cfg entry. Use the
tracename programcontext tracelevel
The following table explains each component of the trace.cfg entry. Use the
components to build entries for the trace.cfg file.
Part
Description
tracename
Identifies the subset of code within an executable file that you
want to trace. The tracename component can be the trace
name that was registered in the executable code, or it can be
the library file name without the lib and .* extensions.
The tracename component is optional. You can include
The tracename component is optional. You can include
tracename to turn on tracing for a given subset of code, such as
a library. If it is omitted, tracing is turned on in all contexts for
the tracename.
programcontext Identifies the process that you want to trace. The
programcontext component can be the name of the executable
file or the trace name that was registered in the executable
code.
tracelevel
Identifies the level of detail that you want to capture for this
process.
Examples:
_ipgui 2
_ipgui 2
The programcontext is _ipgui, and the tracelevel is 2. This entry
starts a level 2 trace on the _ipgui process.
gui _ipgui 1 The tracename is gui, the programcontext is _ipgui, and the
tracelevel is 1. This entry starts a level 1 trace on code labeled gui in
the _ipgui process. (This code may be in the gui library)
All _ipgui 1 The tracename is all, the programcontext is _ipgui, and the
tracelevel is 1. This entry starts a level 1 trace on all code in the
_ipgui process.
Important: To enable the tracing function, go to Enabling the Tracing Function,
next in this section.