Technical Documentation

Tracing BSG Operations

You can trace the following BSG components and record trace results in a log file:

  • datastore
  • framework
  • session trace
  • SBC utilities
  • signaling
  • SIP stack

All log files are placed in the /var/log directory. When a trace file reaches its maximum size, a .0 is appended to the filename, 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 BSG operations:

  1. Access the traceoptions configuration.
    [edit]user@host# edit services border-signaling-gateway gateway bsg1 traceoptions[edit services border-signaling-gateway traceoptions]
  2. Access the traceoptions trace file configuration.
    [edit services border-signaling-gateway gateway bsg1 traceoptions]user@host# edit file[edit services border-signaling-gateway gateway bsg1 traceoptions file]
  3. Specify a name for the trace file.
    [edit services border-signaling-gateway gateway bsg1 traceoptions file]user@host# set filename bsg1
  4. Set the maximum number of trace files.
    [edit services border-signaling-gateway gateway bsg1 traceoptions file]user@host# set files 10
  5. 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-reabable to allow any user to read the log file.
    [edit services pgcp traceoptions file]user@host# set no-world-readable
  6. Access the traceoptions flag configuration to define trace level options.
    [edit services border-signaling-gateway gateway bsg1 traceoptions file]user@host# up[edit services border-signaling-gateway traceoptions]user@host# edit flag
  7. Set trace level options for any other components for which you do not want the default level, error. For example:
    [edit services border-signaling-gateway gateway bsg1 traceoptions flag]user@host# set datastore debug[edit services border-signaling-gateway gateway bsg1 traceoptions flag]user@host# set signaling policy warning[edit services border-signaling-gateway gateway bsg1 traceoptions flag]user@host# set sbc-utils memory-management debug[edit services border-signaling-gateway gateway bsg1 traceoptions flag]user@host# set sip-stack event-tracing[edit services border-signaling-gateway gateway bsg1 traceoptions flag]user@host# set sip-stack pd-log-level audit[edit services border-signaling-gateway traceoptions flag]

Related Topics

  • Summary of PGCP Configuration Statements in Junos Services Interfaces Configuration Guide

Published: 2010-08-03

Help
|
My Account
|
Log Out