TechLibrary

Table of Contents

Guide That Contains This Content

[+] Expand All

[-] Collapse All

Understanding RIP Trace Operations

You can trace various types of RIP protocol traffic to help debug RIP protocol issues.

To trace RIP protocol traffic, include the traceoptions statement at the [edit protocols rip] hierarchy level:

traceoptions {file filename <files number> <size size> <world-readable | no-world-readable>;flag flag <flag-modifier> <disable>;}

You can specify the following RIP protocol-specific trace options using the flag statement:

auth—RIP authentication
error—RIP error packets
expiration—RIP route expiration processing
holddown—RIP hold-down processing
nsr-synchronization—Nonstop active routing synchronization events
packets—All RIP packets
request—RIP information packets
trigger—RIP triggered updates
update—RIP update packets

You can optionally specify one or more of the following flag modifiers:

detail—Detailed trace information
receive—Packets being received
send—Packets being transmitted
Note: Use the detail flag modifier with caution as this may cause the CPU to become very busy.

Global tracing options are inherited from the configuration set by the traceoptions statement at the [edit routing-options] hierarchy level. You can override the following global trace options for the RIP protocol using the traceoptions flag statement included at the [edit protocols rip] hierarchy level:

all—All tracing operations
general—All normal operations and routing table changes (a combination of the normal and route trace operations)
normal—Normal events
policy—Policy processing
route—Routing information
state—State transitions
task—Routing protocol task processing
timer—Routing protocol timer processing

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

TechLibrary

Related Documentation

Understanding RIP Trace Operations

Related Documentation

Published: 2013-04-01