Supported Platforms
Related Documentation
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- log-updown statement
- ACX, M, MX, PTX, QFX, T Series
- Understanding Trace Operations for BGP Protocol Traffic
- ACX, EX, M, PTX, QFX, T Series
- Configuring OSPF Refresh and Flooding Reduction in Stable Topologies
traceoptions (Protocols BGP)
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
4byte-as statement introduced in Junos OS Release 9.2.
4byte-as statement introduced in Junos OS Release 9.2 for EX Series switches.
Description
Configure BGP protocol-level tracing options. To specify more than one tracing operation, include multiple flag statements.
![]() | Note: The traceoptions statement is not supported on QFabric systems. |
Default
The default BGP protocol-level tracing options are inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level. The default group-level trace options are inherited from the BGP protocol-level traceoptions statement. The default peer-level trace options are inherited from the group-level traceoptions statement.
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 BGP tracing output in the file bgp-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 must also specify a maximum file size with the size option.
Range: 2 through 1000 files
Default: 10 files
flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements.
BGP Tracing Flags
- 4byte-as—4-byte AS events.
- bfd—BFD protocol events.
- damping—Damping operations.
- graceful-restart—Graceful restart events.
- keepalive—BGP keepalive messages. If you enable the the BGP update flag only, received keepalive messages do not generate a trace message.
- nsr-synchronization—Nonstop routing synchronization events.
- open—Open packets. These packets are sent between peers when they are establishing a connection.
- packets—All BGP protocol packets.
- refresh—BGP refresh packets.
- update—Update packets. These packets provide routing updates to BGP systems. If you enable only this flag, received keepalive messages do not generate a trace message. Use the keepalive flag to generate a trace message for keepalive messages.
Global Tracing Flags
- all—All tracing operations
- general—A combination of the normal and route trace operations
- normal—All normal operations
Default: If you do not specify this option, only unusual or abnormal operations are traced.
- policy—Policy operations and actions
- route—Routing table changes
- state—State transitions
- task—Routing protocol task processing
- timer—Routing protocol timer processing
flag-modifier—(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers:
- detail—Provide detailed trace information.
- filter—Provide filter trace information. Applies only to route and damping tracing flags.
- receive—Trace the packets being received.
- send—Trace the packets being transmitted.
no-world-readable—(Optional) Prevent any user 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.
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: 128 KB
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.
Related Documentation
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- log-updown statement
- ACX, M, MX, PTX, QFX, T Series
- Understanding Trace Operations for BGP Protocol Traffic
- ACX, EX, M, PTX, QFX, T Series
- Configuring OSPF Refresh and Flooding Reduction in Stable Topologies
Published: 2013-04-03
Supported Platforms
Related Documentation
- ACX, EX, M, MX, PTX, QFX, SRX, T Series
- log-updown statement
- ACX, M, MX, PTX, QFX, T Series
- Understanding Trace Operations for BGP Protocol Traffic
- ACX, EX, M, PTX, QFX, T Series
- Configuring OSPF Refresh and Flooding Reduction in Stable Topologies