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 (sFlow Technology)

date_range 23-Feb-24

Syntax

content_copy zoom_out_map
traceoptions { 
    file filename <files number> <no-stamp> <replace> <size size> <world-readable | no-world-readable>;
    flag flag;
}

Hierarchy Level

content_copy zoom_out_map
[edit protocols sflow]

Description

Define tracing operations for sFlow technology.

Default

The traceoptions feature is disabled.

Note:

In Junos OS Evolved, the traceoptions functions have been moved to the trace application command. Use trace application commands instead. See Junos OS Evolved Differences and Tracing Architecture for details.

Options

file filename

Name of the file to receive the tracing operation output. Enclose the name in quotation marks. Output files are located in the /var/log/ directory.

files number

(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0. Incoming trace file data is logged in the now empty trace-file. When 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 the maximum number of files, you must also specify the maximum file size using the size option.

  • Range: 2 through 1000 files

  • Default: 1 trace file

flag flag

Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements.

  • all—Trace all sFlow monitoring events.

  • client-server—Trace sFlow monitoring client-server events.

  • configuration—Trace sFlow monitoring configuration events.

  • interface—Trace sFlow monitoring interface events.

  • rtsock—Trace routing socket code events.

no-stamp

(Optional) Do not place timestamp information at the beginning of each line in the trace file.

no-world-readable

(Optional) Prevent any user from reading the trace file.

replace

(Optional) Replace an existing trace file if there is one.

size size

(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0. Incoming trace file data is logged in the now empty trace-file. When 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 must also specify a maximum number of trace files with the files option.

  • Syntax: xk to specify KB, xm to specify MB, or xg to specify GB

  • Range: 10 KB through the maximum file size of 4 GB

  • Default: 128 KB

world-readable

(Optional) Allow any user to read the trace file.

Required Privilege Level

routing and trace—To view this statement in the configuration.routing-control and trace-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 11.3.

footer-navigation