Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

traceoptions (Chassis Cluster)

date_range 19-Nov-23

Syntax

content_copy zoom_out_map
traceoptions {
    file {
        filename;
        files number;
        match regular-expression;
        (world-readable | no-world-readable);
        size maximum-file-size;
    }
    flag flag;
    level {
        (alert | all | critical | debug | emergency | error | info | notice | warning);
    }
    no-remote-trace;
}

Hierarchy Level

content_copy zoom_out_map
[edit chassis cluster]

Description

Define chassis cluster redundancy process tracing operations.

A minimum traceoptions configuration must include both a target file and a flag. The target file determines where the trace output is recorded. The flag defines what type of data is collected.

Options

  • file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log.

  • files number—(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed to trace-file.0, then trace-file.1 , and so on, until the maximum number of trace files is reached. The oldest archived file is overwritten.

  • If you specify a maximum number of files, you also must specify a maximum file size with the size option and a filename.

  • Range: 2 through 1000 files

  • Default: 10 files

  • match regular-expression—(Optional) Refine the output to include lines that contain the regular expression.

  • size maximum-file-size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed trace-file .0. When the trace-file again reaches its maximum size, trace-file .0 is renamed trace-file .1 and trace-file is renamed trace-file .0. This renaming scheme continues until the maximum number of trace files is reached. Then the oldest trace file is overwritten.

  • If you specify a maximum file size, you also must specify a maximum number of trace files with the files option and filename.

  • Syntax: x k to specify KB, x m to specify MB, or x g to specify GB

  • Range: 0 KB through 1 GB

  • Default: 128 KB

  • world-readable | no-world-readable—(Optional) By default, log files can be accessed only by the user who configures the tracing operation. The world-readable option enables any user to read the file. To explicitly set the default behavior, use the no-world-readable option.

  • flag—Trace operation or operations to perform on chassis cluster redundancy processes. To specify more than one trace operation, include multiple flag statements.

    • all—Trace all the events

      • configuration—Trace configuration events

      • routing-socket—Trace logging of rtsock activity

      • snmp—Trace SNMP events

Required Privilege Level

trace—To view this statement in the configuration.

trace-control—To add this statement to the configuration.

Release Information

Statement modified in Junos OS Release 9.5.

footer-navigation