Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


traceoptions (Protocols RSVP)


Hierarchy Level


Enable RSVP-level trace options.


The default RSVP-level trace options are those inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level.


disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all.

enhanced-frr —(Optional) Enable this option to trace internal events and state changes related to the FRR facility protection enhancements associated with the increased RSVP scaling introduced in Junos OS Release 16.1.

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. We recommend that you place RSVP tracing output in the file rsvp-log.

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, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten.

  • Range: 2 through 1000

  • Default: 2 files

If you specify a maximum number of files, you must also include the size statement to specify the maximum file size.

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

  • all—All tracing operations

  • error—All detected error conditions

  • event—RSVP-related events. New trace messages are added in the file that you create.

  • io-event [detail] [disable] —Enable tracing of events that occur within the RSVP I/O task; can only be configured for the master routing instance. The trace output is generally independent of routing instance.

  • io-packets [detail] [disable] [receive] [send] —Enable tracing of messages as they are received from the network or as they are sent out. This flag can be configured independently for each routing instance. Both bundled and individual messages are identified. Use detail to show all objects contained in the message. Use send and receive to limit tracing to outgoing or incoming packets.

  • lmp—RSVP-LMP interactions

  • packets—All RSVP packets

  • path—All path messages

  • pathtear—PathTear messages

  • resv—Resv messages

  • resvtear—ResvTear messages

  • route—Routing information

  • state—Session state transitions, including when RSVP-signaled LSPs come up and go down.

flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers:

  • detail—Provide detailed trace information

  • receive—Packets being received

  • send—Packets being transmitted

no-world-readable—(Optional) Enable only certain users to read the log file.

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 this size, it is renamed trace-file.0. When the trace-file again reaches this 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.

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

  • Range: 10 KB through the maximum file size supported on your system

  • Default: 1 MB

If you specify a maximum file size, you must also include the files statement to specify the maximum number of files.

world-readable—(Optional) Enable any user to read the log 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 before Junos OS Release 7.4.