•
Important events for both global and per-interface tracing are logged in a file located
in the /var/log directory. By default, the router uses the filename, jdhcpd. You can
specify a different filename, but you cannot change the directory in which trace files
are located.
•
When the trace log file filename reaches 128 kilobytes (KB), it is compressed and
renamed filename.0.gz. Subsequent events are logged in a new file called filename,
until it reaches capacity again. At this point, filename.0.gz is renamed filename.1.gz and
filename is compressed and renamed filename.0.gz. This process repeats until the
number of archived files reaches the maximum file number. Then the oldest trace
file—the one with the highest number—is overwritten.
You can optionally specify the number of trace files to be from 2 through 1000. You
can also configure the maximum file size to be from 10 KB through 1 gigabyte (GB).
(For more information about how log files are created, see the System Log Explorer.)
•
By default, only the user who configures the tracing operation can access log files. You
can optionally configure read-only access for all users.
To configure global DHCP tracing operations.
•
Specify tracing operations for DHCP local server:
[edit system processes dhcp-service]
user@host# edit traceoptions
The tracing configuration is applied globally to DHCP local server in every LS:RI.
Configuration of event tracing on a per-LS:RI basis is not supported. DHCP tracing is
configurable only in the default LS:RI. However, the DHCP local server do not have to be
configured in the default LS:RI.
For information about configuring per-interface tracing options, see “Tracing Extended
DHCP Operations for Specific Interfaces” on page 358.
The extended DHCP traceoptions operations are described in the following sections:
•
Configuring the Extended DHCP Log Filename on page 354
•
Configuring the Number and Size of Extended DHCP Log Files on page 355
•
Configuring Access to the Extended DHCP Log File on page 355
•
Configuring a Regular Expression for Extended DHCP Messages to Be Logged on page 356
•
Configuring the Extended DHCP Tracing Flags on page 356
•
Configuring the Severity Level to Filter Which Extended DHCP Messages Are
Logged on page 357
•
Tracing Extended DHCP Operations for Specific Interfaces on page 358
Configuring the Extended DHCP Log Filename
By default, the name of the file that records trace output is jdhcpd. You can specify a
different name by including the file option. DHCP local server supports the file option for
the traceoptions statement and the interface-traceoptions statement.
Copyright © 2017, Juniper Networks, Inc.354
ACX Series Universal Access Router Configuration Guide