Download This Guide
Supported Platforms
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 finally a .2. When the maximum number of trace files is reached, the oldest trace file is overwritten.
To configure packet-triggered subscriber tracing operations:
- Specify that you want to configure tracing options.[edit system services packet-triggered-subscribers]user@host# edit traceoptions
- (Optional) Configure the name for the file used for the trace output.
- (Optional) Configure the number and size of the log files.
- (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
You can optionally specify the number of compressed, archived trace log files to be from 2 through 1000. You can also configure the maximum file size to be from 10 KB through 1 gigabyte (GB); the default size is 128 kilobytes (KB).
The archived files are differentiated by a suffix in the format .number.gz. The newest archived file is .0.gz and the oldest archived file is .(maximum number)-1.gz. When the current trace log file reaches the maximum size, it is compressed and renamed, and any existing archived files are renamed. This process repeats until the maximum number of archived files is reached, at which point the oldest file is overwritten.
For example, you can set the maximum file size to 2 MB, and the maximum number of files to 20. When the file that receives the output of the tracing operation, filename, reaches 2 MB, filename is compressed and renamed filename.0.gz, and a new file called filename is created. When the new filename reaches 2 MB, filename.0.gz is renamed filename.1.gz and filename is compressed and renamed filename.0.gz. This process repeats until there are 20 trace files. Then the oldest file, filename.19.gz, is simply overwritten when the next oldest file, filename.18.gz is compressed and renamed to filename.19.gz.
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
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
