[an error occurred while processing this directive][an error occurred while processing this directive]

Tracing Packet-Triggered Subscriber Operations

Packet-triggered subscriber tracing operations track packet-triggered subscriber operations and record them in a log file. The error descriptions captured in the log file provide detailed information to help you solve problems.

All log files are located in the /var/log directory. You cannot change the directory (/var/log) in which trace files are located. When the trace file reaches its maximum size, a .0 is appended to the filename, then a new file is created with a .1, and so on. When the maximum number of trace files is reached, the oldest trace file is overwritten.

To configure packet-triggered subscriber tracing operations:

  1. Specify that you want to configure tracing options.
    [edit system services packet-triggered-subscribers]user@host# edit traceoptions
  2. (Optional) Configure the name for the file used for the trace output.
  3. (Optional) Configure the number and size of the log files.
  4. (Optional) Configure flags to filter the operations to be logged.

The packet-triggered subscriber traceoptions operations are described in the following sections:

Configuring the Packet-Triggered Subscribers Trace Log Filename

By default, the name of the file that records trace output for packet-triggered subscribers is jptspd. You can specify a different name with the file option.

To configure the filename for packet-triggered subscribers tracing operations:

  • Specify the name of the file used for the trace output.
    [edit system services packet-triggered-subscribers traceoptions]user@host# set file ptsp-subs_1

Configuring the Size of Packet-Triggered Subscribers Log Files

By default, when the trace file reaches 128 kilobytes (KB) in size, it is renamed filename.0, then filename.1, and so on, until there are three trace files. Then the oldest trace file (filename.2) is overwritten.

You can optionally configure the maximum file size to be from 10 KB through 1 gigabyte (GB).

For example, you can set the maximum file size to 2 MB. When the file that receives the output of the tracing operation (filename) reaches 2 MB, filename is renamed filename.0, and a new file called filename is created. When the new filename reaches 2 MB, filename.0 is renamed filename.1 and filename is renamed filename.0. This process repeats until there are three trace files. Then the oldest file (filename.2) is overwritten by the newest file (filename.0).

To configure the size of trace files:

  • Specify the name and size of the file used for the trace output.
    [edit system services packet-triggered-subscribers traceoptions]user@host# set file ptsp-subs_1 _logfile_1 size 2097152

Configuring the Packet-Triggered Subscribers Tracing Flags

By default, only important events are logged. You can specify which trace operations are logged by including specific tracing flags. The following table describes the flags that you can include.

Flag

Description

all

Trace all operations

configuration

Trace configuration events

general

Trace general flow.

peer

Trace SRC peer events

pic

Trace PIC events

rtsock

Trace routing socket events

session

Trace session events

To configure the flags for the events to be logged:

  • Configure the flags.
    [edit system services packet-triggered-subscribers traceoptions]user@host# set flag peeruser@host# set flag session

Published: 2010-04-15

[an error occurred while processing this directive]