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

Tracing OSPF Protocol Traffic

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




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 OSPF-specific trace flags in the OSPF traceoptions statement:

all—Everything
database-description—All database description packets, which are used in synchronizing the OSPF topological database
error—OSPF error packets
event—OSPF state transitions
flooding—Link-state flooding packets
general—General events
graceful-restart—Graceful-restart events.
hello—Hello packets, which are used to establish neighbor adjacencies and to determine whether neighbors are reachable
lsa-ack—Link-state acknowledgment packets, which are used in synchronizing the OSPF topological database
lsa-request—Link-state request packets, which are used in synchronizing the OSPF topological database
lsa-update—Link-state updates packets, which are used in synchronizing the OSPF topological database
normal—Normal events
on-demand—Trace demand circuit extensions
packets—All OSPF packets
packet-dump—Dump the contents of selected packet types
policy—Policy processing
spf—Shortest path first (SPF) calculations
state—State transitions
task—Routing protocol task processing
timer—Routing protocol timer processing

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

For general information about tracing and global tracing options, see Tracing Global Routing Protocol Operations.

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