Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

traceoptions (Protocols MPLS)

 

Syntax

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3X50 for the QFX Series.

ted-export option introduced in Junos OS Release 14.2.

ted-import option introduced in Junos OS Release 14.2.

lsp-history option added in Junos OS Release 15.1.

Description

Configure MPLS tracing options at the protocol level or for a label-switched path.

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

Default

The default MPLS protocol-level tracing options are inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level.

Options

filename—Name of the file to receive the output of the tracing operation. All files are placed in the directory /var/log. We recommend that you place MPLS tracing output in the file mpls-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.

MPLS Tracing Flags

  • all—Trace all operations

  • autobw-state—Automatic bandwidth events.

  • connection—All circuit cross-connect (CCC) activity

  • connection-detail—Detailed CCC activity

  • cspf—CSPF computations

  • cspf-link—Links visited during CSPF computations

  • cspf-node—Nodes visited during CSPF computations

  • error—MPLS error packets

  • graceful-restart—Trace MPLS graceful restart events

  • lsp-history—Trace LSP history events

  • lsping—Trace lsping packets and return codes

  • nsr-synchronization—Trace NSR synchronization events

  • nsr-synchronization-detail—Trace NSR synchronization events in detail

  • state—All LSP state transitions

  • static—Trace static label-switched path

  • ted-export—Trace leaking of entries from lsdist.0 table into the traffic engineering database

  • ted-import—Trace leaking traffic engineering database entries into the lsdist.0 table

  • timer—Timer usage

no-world-readable—(Optional) Allow 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) Allow 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.