traceoptions (PCEF)

Use the specified name of the file to receive the output of the tracing operation.

(Optional) Use the specified 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.

• Range: 2 through 1000

• Default: 3 files

Specify which operations are to be traced. To specify more than one operation, include multiple flag statements.

• all—Trace all operations.

• config—Trace configuration events.

• debug—Trace debug internal events.

• fsm—Trace finite state machine events.

• general—Trace general events that do not fit in any specific traces.

• high-availability—Trace high-availability events.

• init—Trace initialization events.

• tftmgr—Trace tftmgr events.

Use the specified level of tracing. You can specify any of the following levels:

• all—Match all levels.

• critical—Match critical conditions.

• error—Match error conditions.

• info—Match informational messages

• notice—Match conditions that must be handled specially.

• verbose—Match verbose messages.

• warning—Match warning messages.

(Optional) Disable remote tracing.

(Optional) Disable unrestricted file access.

(Optional) Use the specified maximum size of each trace file, in kilobytes (KB) or megabytes (MB). 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 number of files, you must also specify a maximum file size with the size option.

• Syntax: xk to specify KB, xm to specify MB, or xg to specify GB.

• Range: 10,240 through 1,073,741,824 bytes

• Default: 128 KB

(Optional) Enable unrestricted file access.