[Contents] [Prev] [Next] [Index] [Report an Error]

Tracing LDP Protocol Traffic at the Protocol and Routing Instance Levels

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




traceoptions { 
file filename <replace> <size size> <files number> <no-stamp>
<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.

Use the file statement to specify the name of the file that receives the output of the tracing operation. All files are placed in the directory /var/log. We recommend that you place LDP-tracing output in the file ldp-log.

The following trace flags display the operations associated with the sending and receiving of various LDP messages. Each can carry one or more of the following modifiers:

address—Trace the operation of address and address withdrawal messages.
binding—Trace label-binding operations.
error—Trace error conditions.
event—Trace protocol events.
initialization—Trace the operation of initialization messages.
label—Trace the operation of label request, label map, label withdrawal, and label release messages.
notification—Trace the operation of notification messages.
packet—Trace the operation of address, address withdrawal, initialization, label request, label map, label withdrawal, label release, notification, and periodic messages. This modifier is equivalent to setting the address, initialization, label, notification, and periodic modifiers.
path—Trace label-switched path operations.
periodic—Trace the operation of hello and keepalive messages.
route—Trace the operation of route messages.
state—Trace protocol state transitions.

[Contents] [Prev] [Next] [Index] [Report an Error]