Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    traceoptions (Resource Management Server)


    traceoptions {file filename {files files;match match;(no-world-readable | world-readable);size size;}flag {flag;}level level;no-remote-trace;}

    Hierarchy Level

    [edit unified-edge resource-management server]

    Release Information

    Statement introduced in Junos OS Mobility Release 11.2W.


    Define the tracing options for the resource management server (the active Routing Engine). Resource management tracing operations record detailed messages about the operation of the resource management server on the broadband gateway. You can specify which trace operations are logged by including specific tracing flags and levels.


    file filename—Name of the file that receives the output of the tracing operation. All files are placed in the /var/log directory.

    Note: The FPC and PIC slot numbers are appended to the specified filename to obtain a unique filename for each DPC.

    files files— (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 must also specify a maximum file size with the size option and a filename.

    Range: 2 through 1000

    Default: 3 files


    • flag—You can use one of the following flags:

      Note: Currently, only the all flag is supported. The other flags are not fully supported.

      • all—Trace everything.
      • communication—Trace infra code.
      • configuration—Trace configuration code.
      • gres—Trace graceful Routing Engine switchover (GRES) code.
      • info-manager—Trace information management code.
      • init—Trace events related to the Resource Management and Packet Steering Deamon(RMPSD) initialization sequence of messages.
      • memory—Trace memory management code.
      • packet-steering—Trace packet-steering code.
      • resource-manager—Trace resource management code.
      • signal—Trace signal-handling code.
      • state—Trace state-handling code.
      • timer—Trace timer code.
      • ui—Trace user interface code.

    level level—(Optional) Level of tracing to perform. You can specify any of the following levels:

    • all—Match all levels.
    • error—Match error conditions.
    • info—Match informational messages.
    • notice—Match conditions that should be handled specially
    • verbose—Match verbose messages.
    • warning—Match warning messages.

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

    no-remote-trace—(Optional) Disable remote tracing.

    no-world-readable—(Optional) Restrict access to the originator of the trace operation only.

    size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). If you specify a maximum file size, you must also 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.

    Required Privilege Level

    interface—To view this statement in the configuration.

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

    Published: 2011-11-18