Tracing Extended DHCP Operations for Specific Interfaces
In addition to the global DHCP tracing operations, subscriber management enables you
to trace extended DHCP operations for a specific interface or for a range of interfaces.
Configuring per-interface tracing is a two-step procedure. In the first step, you specify
the tracing options that you want to use, such as file information and flags. In the second
step, you enable the tracing operation on the specific interfaces.
To configure per-interface tracing operations:
1. Specify the tracing options you want to use.
NOTE: Per-interface tracing uses the same default tracing behavior as
the global extended DHCP tracing operation. The default behavior is
described in “Tracing Extended DHCP Operations” on page 353.
a. Specify that you want to configure per-interface tracing options.
[edit system processes dhcp-service]
user@host# edit interface-traceoptions
b. (Optional) Specify the tracing file options.
•
Configure the name for the file used for the trace output.
See “Configuring the Extended DHCP Log Filename” on page 354.
•
Configure the number and size of the log files.
See “Configuring the Number and Size of Extended DHCP Log Files” on page 355.
•
Configure access to the log file.
See “Configuring Access to the Extended DHCP Log File” on page 355.
•
Configure a regular expression to filter logging events.
See “Configuring a Regular Expression for Extended DHCP Messages to Be
Logged” on page 356.
c. (Optional) Specify tracing flag options.
See “Configuring the Extended DHCP Tracing Flags” on page 356.
d. (Optional) Configure a severity level for messages to specify which event messages
are logged.
See “Configuring the Severity Level to Filter Which Extended DHCP Messages Are
Logged” on page 357.
2. Enable tracing on an interface or interface range.
The following examples show a DHCP local server configuration.
Copyright © 2017, Juniper Networks, Inc.358
ACX Series Universal Access Router Configuration Guide
To Next Page
Loading...
Need help?
General
