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

Tracing RIPng Protocol Traffic

To trace RIPng protocol traffic, you can specify options in the global traceoptions statement at the [edit routing-options] hierarchy level, and you can specify RIPng-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 RIPng-specific options in the RIPng traceoptions statement:

all—Trace everything.
error—Trace RIPng errors.
expiration—Trace RIPng route expiration processing.
general—Trace general events.
holddown—Trace RIPng hold-down processing.
normal—Trace normal events.
packets—Trace all RIPng packets.
policy—Trace policy processing.
request—Trace RIPng information packets.
route—Trace routing information.
state—Trace state transitions.
task—Trace routing protocol task processing.
timer—Trace routing protocol timer processing.
trigger—Trace RIPng triggered updates.
update—Trace RIPng update packets.

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

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