Tracing BGF Operations
You can trace the following BGF components and record trace results in a log file:
- BGF core
- H.248 stack
- SBC utilities
All log files are placed in the /var/log directory. When a trace file reaches its maximum size, a .0 is appended to the file name, then a new file is created with a .1 appended, and so on. When the maximum number of trace files is reached, the oldest trace file is overwritten.
To configure tracing of BGF operations:
- Access the traceoptions file configuration.[edit]user@host# edit services pgcp traceoptions file
- Specify a name for the trace file. [edit services pgcp traceoptions file]user@host# set filename bgf1
- Set the maximum number of trace files.
If you specify a maximum number of files, you also must specify a
maximum file size.[edit services pgcp traceoptions file]user@host# set files 10
- Set user access to the trace log file.
Use set no-world-readable to prevent users from accessing
the log file, or use set world-readable to all any user to
read the log file.[edit services pgcp traceoptions file]user@host# set no-world-readable
- Access the traceoptions flag configuration
to define trace level options.[edit services pgcp traceoptions file]user@host# up[edit services pgcp traceoptions]user@host# edit flag
- Specify the operations that you want
to include in the log file. For example:[edit services pgcp traceoptions flag]user@host# set bgf-core firewall warninguser@host# set bgf-core pic-broker warninguser@host# set h248-stack control-association warninguser@host# set sbc-utils memory-management debug
