[an error occurred while processing this directive][an error occurred while processing this directive]

Tracing BFD Protocol Traffic

To trace BFD protocol traffic, you can specify options in the global traceoptions statement at the [edit routing-options] hierarchy level, and you can specify BFD-specific options by including the traceoptions statement at the [edit protocols bfd hierarchy level.

[edit protocols]bfd {traceoptions {file filename <files number> <size size> <world-readable | no-world-readable>;flag flag <flag-modifier> <disable>;}}

For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.

You can specify the following BFD-specific options in the BFD traceoptions statement:

  • adjacency—Trace adjacency messages.
  • all—Trace all options.
  • error—Trace all error messages.
  • event—Trace all events.
  • issu—Trace in-service software upgrade (ISSU) packet activity.
  • nsr-packet—Trace active nonstop active routing (NSR) packet activity.
  • nsr-synchronization—Trace NSR synchronization events.
  • packet—Trace all packets.
  • pipe—Trace pipe messages.
  • pipe-detail—Trace pipe messages in detail.
  • ppm-packet—Trace packet activity by periodic packet management (PPM).
  • state—Trace state transitions.
  • timer—Trace timer processing.

Note: Use the all trace flag with caution. These flags may cause the CPU to become very busy.

For general information about tracing, see the tracing and logging information in the JUNOS System Basics Configuration Guide.

Published: 2010-04-14

[an error occurred while processing this directive]