Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

traceoptions (Protocols BFD)

Syntax

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

issu flag for BFD added in Junos OS Release 9.1.

Description

Define tracing operations that track unified in-service software upgrade (ISSU) functionality in the router.

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

Default

If you do not include this statement, no global tracing operations are performed.

Options

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.

file name—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 global routing protocol tracing output in the file routing-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.

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

flag flag—Tracing operation to perform. The tracing options are as follows:

• adjacency—Trace adjacency messages.
• all—Trace everything.
• error—Trace all errors.
• events—Trace all events.
• issu—Trace ISSU packet activity.
• nsr-packet—Trace packet activity of NSR.
• nsr-synchronization—Trace NSR synchronization events.
• packet—Trace all packets.
• pipe—Trace pipe messages.
• pipe-detail—Trace pipe messages in detail.
• ppm-packet—Trace packet activity by periodic packet management.
• state—Trace state transitions.
• timer—Trace timer processing.

no-world-readable—Restrict users from reading 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 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.

world-readable—Allow users 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.