[Contents] [Prev] [Next] [Index] [Report an Error]

Tracing Extended DHCP Relay Agent Operations

The extended DHCP tracing operations track all extended DHCP relay agent operations and record them in a log file. The logged error descriptions provide detailed information to help you solve problems faster.

By default, nothing is traced. If you include the traceoptions statement at the [edit forwarding-options dhcp-relay] hierarchy level, the default tracing behavior is the following:

Important events are logged in a file called jdhcpd located in the /var/log directory. You cannot change the directory (/var/log) in which trace files are located.
When the file jdhcpd reaches 128 kilobytes (KB), it is renamed jdhcpd.0, then jdhcpd.1, and so on, until there are three trace files. Then the oldest trace file (jdhcpd.2) is overwritten. (For more information about how log files are created, see the JUNOS System Log Messages Reference.)
Log files can be accessed only by the user who configures the tracing operation.

To trace the extended DHCP relay agent operations, include the traceoptions statement at the [edit forwarding-options dhcp-relay] hierarchy level:



[edit forwarding-options dhcp-relay]

traceoptions {
flag all;
flag auth;
flag database;
flag state;
flag interface;
flag rtsock;
flag packet;
flag packet-option;
flag io;
flag ha;
flag ui;
flag general;
flag fwd;
flag rpd;
flag session-db;


file file-name {
<files number>;
<size maximum-file-size>;
<match regex>;
<(world-readable | no-world-readable)>;
}


}

The extended DHCP relay agent traceoptions statements are described in the following sections:

[Contents] [Prev] [Next] [Index] [Report an Error]