Related Documentation
- M, T Series
- Configuring Tracing Operations for DHCP Processes
- M, MX, PTX, T Series
- System Management Configuration Statements
traceoptions (DHCP Server)
Syntax
Hierarchy Level
Release Information
Statement for tracing J Series Services Router DHCP processes introduced in Junos OS Release 8.0.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Description
Define tracing operations for DHCP processes for J Series Services Routers and EX Series switches.
Options
file filename
—Name of the file that receives the output
of the tracing operation. Enclose the name in quotation marks. All
files are placed in the directory /var/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 and a filename.
Range: 2 through 1000
Default: 3 files
flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:
- all—All tracing operations
- binding—Trace binding operations
- config—Log reading of configuration
- conflict—Trace user-detected conflicts for IP addresses
- event—Trace important events
- ifdb—Trace interface database operations
- io— Trace I/O operations
- lease—Trace lease operations
- main—Trace main loop operations
- misc— Trace miscellaneous operations
- packet—Trace DHCP packets
- options—Trace DHCP options
- pool—Trace address pool operations
- protocol—Trace protocol operations
- rtsock—Trace routing socket operations
- scope—Trace scope operations
- signal—Trace DHCP signal operations
- trace—All tracing operations
- ui—Trace user interface operations
match regex—(Optional) Refine the output to include lines that contain the regular expression.
- all—All tracing operations
- binding—Trace binding operations
- config— Log reading of configuration
- conflict—Trace user-detected conflicts for IP addresses
- event—Trace important events
- ifdb— Trace interface database operations
- io—Trace I/O operations
- lease—Trace lease operations
- main—Trace main loop operations
- match regex— Refine the output to include lines that contain the regular expression.
- misc—Trace miscellaneous operations
- packet—Trace DHCP packets
- options—Trace DHCP options
- pool—Trace address pool operations
- protocol—Trace protocol operations
- rtsock—Trace routing socket operations
- scope—Trace scope operations
- signal—Trace DHCP signal operations
- trace—All tracing operations
- ui—Trace user interface operations
no-world-readable—(Optional) Disable unrestricted file access.
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 and filename.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through 1 GB
Default: 128 KB
world-readable—(Optional) Enable unrestricted file access.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Related Documentation
- M, T Series
- Configuring Tracing Operations for DHCP Processes
- M, MX, PTX, T Series
- System Management Configuration Statements
Published: 2013-02-22
Related Documentation
- M, T Series
- Configuring Tracing Operations for DHCP Processes
- M, MX, PTX, T Series
- System Management Configuration Statements