[an error occurred while processing this directive][an error occurred while processing this directive]

traceoptions (PPP Process)

Syntax

traceoptions {file filename <files number> <match regular-expression> <size size> <world-readable | no-world-readable>;flag flag;level severity-level;no-remote-trace;}

Hierarchy Level

[edit protocols ppp]

Release Information

Statement introduced in JUNOS Release 7.5.

Description

Define tracing operations for the PPP process.

To specify more than one tracing operation, include multiple flag statements.

You cannot specify a separate trace tile. Tracing information is placed in the system syslog file in the directory /var/log/pppd.

Default

If you do not include this statement, no PPPD-specific tracing operations are performed.

Options

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. By default, commit script process tracing output is placed in the file ppd. If you include the file statement, you must specify a filename. To retain the default, you can specify eventd as the filename.

files number—(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten.

If you specify a maximum number of files, you also must specify a maximum file size with the size option and a filename.

Range: 2 through 1000
Default: 3 files

disable—(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all.

flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. The following are the PPPD-specific tracing options.

  • access—Access code
  • address-pool—Address pool code
  • all—All areas of code
  • auth—Authentication code
  • chap—Challenge Handshake Authentication Protocol (CHAP) code
  • config—Configuration code
  • ifdb—Interface database code
  • lcp—LCP state machine code
  • memory—Memory management code
  • message—Message processing code
  • mlppp—Trace MLPPP code
  • ncp—NCP state machine code
  • pap—Password Authentication Protocol (PAP) code
  • ppp—PPP protocol processing code
  • radius—RADIUS processing code
  • rtsock—Routing socket code
  • session—Session management code
  • signal—Signal handling code
  • timer—Timer code
  • ui—User interface code

match regex—(Optional) Refine the output to include only those lines that match the given regular expression.

size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues until the maximum number of trace files is reached. Then the oldest trace file is overwritten.

If you specify a maximum file size, you also must specify a maximum number of trace files with the files option and filename.

Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through 1 GB
Default: 128 KB

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

non-world-readable—(Optional) By default, log files can be accessed only by the user who configures the tracing operation. Specify non-world-readable to reset the default.

Required Privilege Level

interface—To view this statement in the configuration.

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


Published: 2010-04-20

[an error occurred while processing this directive]