Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Understanding RIPng Protocol Traffic Trace Operations

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

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

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

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

  • error—RIPng error packets
  • expiration—RIPng route expiration processing
  • holddown—RIPng hold-down processing
  • nsr-synchronization—Nonstop routing synchronization events
  • packets—All RIPng packets
  • request—RIPng information packets
  • trigger—RIPng triggered updates
  • update—RIPng 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 might 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 RIPng protocol using the traceoptions flag statement included at the [edit protocols ripng] 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 as this might cause the CPU to become very busy.

 

Related Documentation

 

Published: 2012-12-08

Previous Page Next Page