Trace RIP Protocol Traffic

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

[edit protocols rip]

traceoptions { 

    file name <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 configure this statement, see the statement summary section for this statement.

You can specify the following RIP-specific options in the RIP traceoptions statement:

• auth—Trace RIP authentication.
• error—Trace RIP errors.
• expiration—Trace RIP route expiration processing.
• holddown—Trace RIP hold-down processing.
• packets—Trace all RIP packets.
• request—Trace RIP information packets.
• trigger—Trace RIP triggered updates.
• update—Trace RIP update packets.
  

  NOTE: Use the traceoption 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 Trace Global Routing Protocol Operations.

Example: Trace RIP Protocol Traffic

Trace only unusual or abnormal operations to /var/log/routing-log, and trace detailed information about all RIP packets to /var/log/rip-log:

[edit]

routing-options {

    traceoptions {

        file /var/log/routing-log;

        flag errors;

    }

}

protocols {

    rip { 

        traceoptions {

            file /var/log/rip-log;

            flag packets detail;

        }

    }

}