Tracing on Junos OS Evolved
For Junos OS Evolved, the traceoptions statement is deprecated at all hierarchy levels, except for rpd ptotocols. Instead, use the tracing session command at the [edit system] level hierarchy to configure tracing on the system.
You have to configure a tracing session to activate that tracing
session on the system. After a tracing session is configured, trace
data from all nodes is collected on the master Routing Engine in
Configure a tracing session by setting the session name. For each session, you can define tracing options for any applications you select—you can also select all to select for all applications. You can control how many trace files are created before the first one is overwritten (file-count), and the size of a trace file before rollover occurs (file-size. You can also select to purge trace files when the trace session is deleted (purge-on-delete.
To delete a tracing session, use the delete system tracing session session-name command from configuration mode.
You can view collected traces with the show trace command.
You can remove inactive tracing sessions with the clear trace command.
For protocols, you need to continue using the traceoptions statement. as before. traceoptions log files created by rpd cannot be viewed or accessed from the CLI. They can be viewed by logging into Junos VM.