traceoptions (Services L2TP)
Syntax
traceoptions { debug-level level; file filename <files number> <match regular-expression > <size maximum-file-size> <world-readable | no-world-readable>; filter { protocol name; user user@domain; user-name username; } flag flag; interfaces interface-name { debug-level level; flag flag; } level (all | error | info | notice | verbose | warning); no-remote-trace; }
Hierarchy Level
[edit services l2tp]
Description
Define tracing operations for L2TP processes.
Options
debug-level level
—Trace
level for PPP, L2TP, RADIUS, and UDP; this option does not apply to
L2TP on MX Series routers:
detail
—Trace detailed debug information.error
—Trace error information.packet-dump
—Trace packet decoding information.
file 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.
files number
—(Optional)
Maximum number of trace files to create before overwriting the oldest
one. If you specify a maximum number of files, you also must specify
a maximum file size with the size
option.
Range: 2 through 1000
Default: 3 files
filter
—Additional filter to refine the
output to display particular subscribers. Filtering based on the following
subscriber identifiers simplifies troubleshooting in a scaled environment.
protocol
name—One of the following protocols; this option does not apply to L2TP on MX Series routers:l2tp
ppp
radius
udp
user
user@domain—Username of a subscriber; this option does not apply to L2TP on M Series routers. Optionally use an asterisk (*) as a wildcard to substitute for characters at the beginning or end of either term or both terms.user-name
username—Username of a subscriber; this option does not apply to L2TP on MX Series routers.
flag flag
—Tracing
operation to perform. To specify more than one tracing operation,
include multiple flag
statements. You can include the following
flags:
all
—Trace all operations.configuration
—Trace configuration events.events
—Trace interface events.general
—Trace general events.gres
—Trace GRES events.init
—Trace daemon initialization.ipc-rx
—Trace IPC receive events.ipc-tx
—Trace IPC transmit events.memory
—Trace memory management code.message
—Trace message processing code.packet-error
—Trace packet error events.parse
—Trace parsing events.protocol
—Trace L2TP events.receive-packets
—Trace received L2TP packets.routing-process
—Trace routing process interactions.routing-socket
—Trace routing socket events.session-db
—Trace session database interactions.states
—Trace state machine events.timer
—Trace timer events.transmit-packets
—Trace transmitted L2TP packets.tunnel
—Trace tunnel events.
interfaces interface-name
—Apply L2TP traceoptions to a specific services interface.
This option does not apply to L2TP on MX Series routers.
debug-level level
—Trace level for the interface; this option does not apply to L2TP on MX Series routers:detail
—Trace detailed debug information.error
—Trace error information.extensive
—Trace all PIC debug information.
flag flag
—Tracing operation to perform for the interface. This option does not apply to L2TP on MX Series routers. To specify more than one tracing operation, include multipleflag
statements. You can include the following flags:all
—Trace everything.ipc
—Trace L2TP Inter-Process Communication (IPC) messages between the PIC and the Routing Engine.packet-dump
—Dump each packet content based on debug level.protocol
—Trace L2TP, PPP, and multilink handling.system
—Trace packet processing on the PIC.
level
—Specify level of tracing to perform.
The option you configure enables tracing of events at that level and
all higher (more restrictive) levels. You can specify any of the following
levels:
all
—Match messages of all levels.error
—Match error messages.info
—Match informational messages.notice
—Match notice messages about conditions requiring special handling.verbose
—Match verbose messages. This is the lowest (least restrictive) severity level; when you configureverbose
, messages at all higher levels are traced. Therefore, the result is the same as when you configureall
.warning
—Match warning messages.
Default:
error
match regular-expression
—(Optional)
Refine the output to include lines that contain the regular expression.
no-remote-trace
—Disable remote tracing.
no-world-readable
—(Optional) Disable unrestricted
file access.
size maximum-file-size
—(Optional)
Maximum size of each trace file. By default, the number entered is
treated as bytes. Alternatively, you can include a suffix to the number
to indicate kilobytes (KB), megabytes (MB), or gigabytes (GB). If
you specify a maximum file size, you also must specify a maximum number
of trace files with the files
option.
Syntax:
sizek
to specify KB,sizem
to specify MB, orsizeg
to specify GB
Range: 10240 through 1073741824
world-readable
—(Optional) Enable unrestricted
file access.
Required Privilege Level
trace—To view this statement in the configuration.
trace-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.