traceoptions (Traffic Load Balancer)

Syntax

Hierarchy Level

Description

CAUTION:

Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.

Configure tracing options for the traffic load balancer.

Options

For Next Gen Services on the MX-SPC3 services card, set the monitor-object-name to either:

file file-name

Name of the file to receive the output of the tracing operation.

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 files
Default: 3 files

flag flag

Specify which operations you want to trace from Table 1. To specify more than one operation, include multiple flag statements.

Table 1: Trace Flags
Flag	Support on MS-MPC and MX-SPC3 Cards	Description
all	MS-MPC and MX-SPC3	Trace all operations.
all-real-services	MS-MPC and MX-SPC3	Trace all real services.
database	MS-MPC and MX-SPC3	Trace database events.
file-descriptor-queue	MS-MPC and MX-SPC3	Trace file descriptor queue events.
inter-thread	MS-MPC and MX-SPC3	Trace inter-thread communication events.
messages	MS-MPC and MX-SPC3	Trace normal events.
probe	MS-MPC and MX-SPC3	Trace probe events.
probe-infra	MS-MPC and MX-SPC3	Trace probe infra events.

instance-name instance-name

(Optional) Name of the TLB instance to monitor.

level

Use the specified level of tracing. You can specify any of the following levels:

all—Match all levels.
error—Match error conditions.
info—Match informational messages.
notice—Match conditions that must be handled specially.
verbose—Match verbose messages.
warning—Match warning messages.

These trace levels are available for both the MS-MPC and MX-SPC3 services cards unless otherwise specified.

monitor monitor-object-name

Name of a monitoring object that contains an instance name or virtual service name.

no-remote-trace

(Optional) Disable remote tracing.

no-world-readable

(Optional) Disable unrestricted file access.

group-name

Name of the group.

real-services-name

Name of the real service

size size

(Optional) Use the maximum size of each trace file, in kilobytes (KB) or megabytes (MB). 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 number of files, you must also specify a maximum file size with the size option.

Syntax: xk to specify KB, xm to specify MB, or xg to specify GB.
Range: 10,240 through 1,073,741,824 bytes.
Default: 128 KB

virtual-svc-name virtual-service-name

(Optional) Name of the virtual service to monitor.

word-readable

(Optional) Enable unrestricted file access.

Required Privilege Level

trace and interface—To view this statement in the configuration.

trace-control and interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 16.1.

instance-name and virtual-service-name options added in Junos OS Release 16.1R6 and 18.2R1 on MX Series.

Support for Next Gen Services MX-SPC3 services card add in Junos OS Release 19.3R2.

ON THIS PAGE