traceoptions (Protocols PCEP)
Syntax
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
Hierarchy Level
[edit protocols pcep]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Configure the Path Computation Element Protocol (PCEP) tracing options.
Options
filename |
Name of the file to receive the output of the tracing
operation. All files are placed in the directory |
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.
|
flag |
Area of path computation client process (pccd) to enable debugging output. PCEP Tracing Flags
|
no-remote-trace |
(Optional) Disable remote tracing options. |
no-world-readable |
(Optional) Allow only certain users to read the log file. |
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 this 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.
|
world-readable |
(Optional) Allow any user to read the log file. |
Required Privilege Level
routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration.