Tracing ICMP Protocol Traffic

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

[edit protocols router-discovery]

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 these statements, see the statement summary sections for these statements.

You can specify the following ICMP-specific options in the ICMP flag statement:

• error—Trace error packets.
• info—Trace information packets.
• routerdiscovery—Trace all ICMP packets.
• redirect—Trace redirect packets.

You can specify the following global flag options:

• all—Trace everything.
• general—Trace general events.
• normal—Trace normal events.
• policy—Trace policy processing.
• route—Trace routing information.
• state—Trace state transitions.
• task—Trace routing protocol task processing.
• timer—Trace routing protocol timer processing.
  

  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 Tracing Global Routing Protocol Operations.

Example: Tracing ICMP Protocol Traffic

Trace only unusual or abnormal operations to a file called routing-log, and trace router discovery state transitions to a file called icmp-log:

[edit]

routing-options {

    traceoptions {

        file routing-log;

    }

}

protocols {

    router-discovery { 

        traceoptions {

            file icmp-log;

            flag state;

        }

    }

}