Technical Documentation

traceoptions (Mobile IP)

Syntax

traceoptions { file <filename> <files number> <match regular-expression > <size maximum-file-size> <world-readable | no-world-readable>;flag flag;level (all | error | info | notice | verbose | warning);no-remote-trace;}

Hierarchy Level

[edit logical-systems logical-system-name services mobile-ip],[edit logical-systems logical-system-name routing-instances routing-instances-name services mobile-ip],[edit routing-instances routing-instances-name services mobile-ip],[edit services mobile-ip]

Release Information

Statement introduced in JUNOS Release 9.3.

Support at the [edit logical-systems logical-system-name services mobile-ip], [edit logical-systems logical-system-name routing-instances routing-instances-name services mobile-ip], and [edit routing-instances routing-instances-name services mobile-ip] hierarchy levels added in JUNOS Release 9.5.

Description

Define tracing operations for Mobile IP processes.

Options

file 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. Ensure that filenames are unique for each logical system or routing instance in which Mobile IP is configured.

Note: Global messages (common to all logical systems and routing instances) are always saved in /var/log/mipd. Messages that are specific to a logical system or routing instance are never saved in /var/log/mipd. If you do not configure a trace filename for a logical system or routing instance, then nothing is traced for that entity.

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.

Range: 2 through 1000
Default: 3 files

flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:

  • all—Trace all operations.
  • authentication—Trace authentication operations.
  • binding—Trace bindings.
  • event—Trace events.
  • ha-fsm—Trace home agent state machine operations.
  • home-agent—Trace home agent operations.
  • interface-database—Trace interface database operations.
  • packet—Trace packet decoding operations.
  • protocol—Trace protocol operations.
  • rtsock—Trace routing socket operations.
  • session-db—Trace session database events.
  • signal—Trace signal operations.
  • subscriber—Trace subscriber events.
  • timer—Trace timer events.
  • trace—Trace changes in tracing.
  • tunnel—Trace tunneling operations.
  • user-interface—Trace user interface events.

level—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 notice messages about conditions requiring special handling.
  • verbose—Match verbose messages.
  • warning—Match verbose messages.

no-remote-trace—Disable remote tracing.

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

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

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 also must specify a maximum number of trace files with the files option.

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

trace—To view this statement in the configuration.

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


Published: 2010-04-15