Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

traceoptions (Protocols VRRP)

 

Syntax

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

Description

Define tracing operations for the Virtual Router Redundancy Protocol (VRRP) process.

To specify more than one tracing operation, include multiple flag statements.

By default, VRRP logs the error, dcd configuration, and routing socket events in a file in the directory /var/log.

Default

If you do not include this statement, no VRRP-specific tracing operations are performed.

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. By default, VRRP tracing output is placed in the file vrrpd.

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. When the maximum number is reached, the oldest trace file is overwritten.

Range: 0 through 4,294,967,296 files

Default: 3 files

If you specify a maximum number of files, you also must specify a maximum file size with the size option.

flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. These are the VRRP-specific tracing options:

  • all—All VRRP tracing operations

  • database—Database changes

  • general—General events

  • interfaces—Interface changes

  • normal—Normal events

  • packets—Packets sent and received

  • state—State transitions

  • timer—Timer events

match regular-expression—(Optional) Refine the output to include only those lines that match the given regular expression.

microsecond-stamp—(Optional) Provide a timestamp with microsecond granularity.

no-world-readable—(Optional) Restrict users from reading the log file.

size size—(Optional) Maximum size of each trace file, in kilobytes, megabytes, or gigabytes. 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.

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

Range: 10 KB through the maximum file size supported on your routing platform

Default: 1 MB

If you specify a maximum file size, you also must specify a maximum number of trace files with the files option.

world-readable—(Optional) Allow users to read the log file.

Required Privilege Level

trace—To view this statement in the configuration.

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

Related Documentation