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

    Related Documentation


    traceoptions (Charging)


    traceoptions {file file-name <files number> <no-world-readable | world-readable> <size size>;flag flag;level (all | critical | error | info | notice | verbose | warning);no-remote-trace;}

    Hierarchy Level

    [edit unified-edge gateways ggsn-pgw gateway-name charging]

    Release Information

    Statement introduced in Junos OS Mobility Release 11.2W.


    Specify tracing options for charging.


    file file-name—Name of the file to receive the output of the tracing operation. The router appends the -ms#fic#pic term to the filename and places the file in the /var/log directory. For example, if you have configured the filename to be smd, then the actual log filename that you see on the router is, smd-ms#fic#pic (ms in the filename stands for the multi service card).

    Range: 1 through 1024 bytes

    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.

    Range: 2 through 1000 files

    Default: 3 files

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

    Caution: You may want to enable traceoptions only when you want to debug specific charging operations. Enabling the traceoption flags might have an impact on the system performance.

    • all—Trace all operations of all charging submodules.
    • cdr-encoding—Trace ASN1 encoding of the CDRs.
    • client-fsm—Trace the charging-specific finite-state machine (FSM) in the application framework (mobile-smd).
    • config—Trace configuration events on both daemons (chargemand and mobile-smd).
    • fsm—Trace FSM.
    • general—Trace general events, which do not fit in any specific traces, such as errors in chargemand.
    • group-fsm—Trace the transport-profile FSM in chargemand.
    • init—Trace initialization events.
    • ipc—Trace the IPC between mobile-smd and chargemand.
    • path-management—Trace path management operations within the path manager module within chargemand.
    • resource—Trace resources, such as memory, counters, and so on.
    • timers—Trace resources associated with timer processing.
    • transport—Trace transport-profile-level operations in chargemand.
    • triggers—Trace trigger-profile-related operations used by the mobile-smd charging module.

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

    • all—Match all levels.
    • critical—Match error 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.

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

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

    size size—(Optional) 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

    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.


    Related Documentation


    Published: 2011-11-16