Trace Op Script Processing on Devices Running Junos OS

Example: Minimum Configuration for Enabling Traceoptions for Op Scripts

Display the trace output of the op script file source-route.xsl:

[edit]
system {
    scripts {
        op {
            file source-route.xsl;
            traceoptions {
                flag output;
            }
        }
    }
}

[edit]
user@host# commit
[edit]
user@host# run show log op-script.log | last

Configuring the Op Script Log Filename

By default, the name of the file that records trace output for all op scripts is op-script.log. You can record the trace output for local op scripts in a different file by including the file statement at the [edit system scripts op traceoptions] hierarchy level:

[edit system scripts op traceoptions]
file filename;

Configuring the Number and Size of Op Script Log Files

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

You can configure the limits on the number and size of trace files by including the following statements at the [edit system scripts op traceoptions file <filename>] hierarchy level:

[edit system scripts op traceoptions file <filename>]
files number size size;

For example, set the maximum file size to 640 KB and the maximum number of files to 20. When the file that receives the output of the tracing operation (filename) reaches 640 KB, it is renamed and compressed to filename.0.gz, and a new file called filename is created. When filename reaches 640 KB, filename.0.gz is renamed filename.1.gz and filename is renamed and compressed to filename.0.gz. This process repeats until there are 20 trace files. Then the oldest file (filename.19.gz) is overwritten.

The number of files can range from 2 through 1000 files. The file size can range from 10 KB through 1 gigabyte (GB).

Configuring Access to Op Script Log Files

By default, access to the op script log file is restricted to the owner. You can manually configure access by including the world-readable or no-world-readable statement at the [edit system scripts op traceoptions file <filename>] hierarchy level.

[edit system scripts op traceoptions file <filename>]
(world-readable | no-world-readable);

The no-world-readable statement restricts op script log access to the owner. The world-readable statement enables unrestricted access to the op script log file.

Configuring the Op Script Trace Operations

By default, the traceoptions events flag is turned on, regardless of the configuration settings, and only important events are logged. This includes errors, warnings, progress messages, and script processing events. You can configure the trace operations to be logged for local op scripts by including the following statements at the [edit system scripts op traceoptions] hierarchy level:

[edit system scripts op traceoptions]
flag all;
flag events;
flag input;
flag offline;
flag output;
flag rpc;
flag xslt;

Table 2 describes the meaning of the op script tracing flags.