Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

traceoptions (L2TP)

Syntax

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

Description

Define tracing operations for L2TP processes.

Options

• detail—Trace detailed debug information.
• error—Trace error information.
• packet-dump—Trace packet decoding information.

file filename—Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log.

files number—(Optional) Maximum number of trace files to create before overwriting the oldest one. If you specify a maximum number of files, you also must specify a maximum file size with the size option.

• l2tp
• ppp
• radius
• udp

filter user-name username—Additional filter for the specified username; this option does not apply to L2TP on MX Series routers.

• all—Trace all operations.
• configuration—Trace configuration events.
• events—Trace interface events.
• general—Trace general events.
• gres—Trace GRES events.
• init—Trace daemon initialization.
• ipc-rx—Trace IPC receive events.
• ipc-tx—Trace IPC transmit events.
• memory—Trace memory management code.
• message—Trace message processing code.
• packet-error—Trace packet error events.
• parse—Trace parsing events.
• protocol—Trace L2TP events.
• receive-packets—Trace received L2TP packets.
• routing-process—Trace routing process interactions.
• routing-socket—Trace routing socket events.
• session-db—Trace session database interactions.
• states—Trace state machine events.
• timer—Trace timer events.
• transmit-packets—Trace transmitted L2TP packets.
• tunnel—Trace tunnel events.

• debug-level level—Trace level for the interface; this option does not apply to L2TP on MX Series routers:
  • detail—Trace detailed debug information.
  • error—Trace error information.
  • extensive—Trace all PIC debug information.
• flag flag—Tracing operation to perform for the interface. This option does not apply to L2TP on MX Series routers. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:
  • all—Trace everything.
  • ipc—Trace L2TP Inter-Process Communication (IPC) messages between the PIC and the Routing Engine.
  • packet-dump—Dump each packet content based on debug level.
  • protocol—Trace L2TP, PPP, and multilink handling.
  • system—Trace packet processing on the PIC.

• all—Match messages of all levels.
• error—Match error messages.
• info—Match informational messages.
• notice—Match notice messages about conditions requiring special handling.
• verbose—Match verbose messages. This is the lowest (least restrictive) severity level; when you configure verbose, messages at all higher levels are traced. Therefore, the result is the same as when you configure all.
• warning—Match warning messages.

match regular-expression—(Optional) Refine the output to include lines that contain the regular expression.

no-remote-trace—Disable remote tracing.

no-world-readable—(Optional) Disable unrestricted file access.

size maximum-file-size—(Optional) Maximum size of each trace file. By default, the number entered is treated as bytes. Alternatively, you can include a suffix to the number to indicate kilobytes (KB), megabytes (MB), or gigabytes (GB). If you specify a maximum file size, you also must specify a maximum number of trace files with the files option.

world-readable—(Optional) Enable unrestricted file access.

Required Privilege Level

trace—To view this statement in the configuration.

trace-control—To add this statement to the configuration.