Tracing operations track all AS PIC operations and record them in a log file in the /var/log directory. By default, this file is named /var/log/l2tpd.
To trace L2TP operations, include the traceoptions statement at the [edit services l2tp] hierarchy level:
-
traceoptions {
- debug-level level;
-
- filter {
- protocol name;
- }
- flag flag;
-
- interfaces interface-name {
- debug-level level;
- flag flag;
- }
- }
You can specify the following L2TP tracing flags:
You can specify a trace level for PPP, L2TP, RADIUS, and User Datagram Protocol (UDP) tracing. To configure a trace level, include the debug-level statement at the [edit services l2tp traceoptions] hierarchy level and specify one of the following values:
You can filter by protocol. To configure filters, include the filter protocol statement at the [edit services l2tp traceoptions] hierarchy level and specify one or more of the following protocol values:
To implement filtering by protocol name, you must also configure either flag protocol or flag all.
You can also configure traceoptions for L2TP on a specific adaptive services interface. To configure per-interface tracing, include the interfaces statement at the [edit services l2tp traceoptions] hierarchy level:
- interfaces interface-name {
- debug-level level;
- flag flag;
- }
![]() |
Note: Implementing traceoptions consumes CPU resources and affects the packet processing performance. |
You can specify the debug-level and flag statements for the interface, but the options are slightly different from the general L2TP traceoptions. You specify the debug level as detail, error, or extensive, which provides complete PIC debug information. The following flags are available: