Tracing IGMP Protocol Traffic

To trace IGMP protocol traffic, you can specify options in the global traceoptions statement at the [edit routing-options] or [edit logical-routers logical-router-name routing-options] hierarchy level.

You can specify IGMP-specific options by including the traceoptions statement:

traceoptions { 

    file name <replace> <size size> <files number> <no-stamp> 

        <(world-readable | no-world-readable)>;

    flag flag <flag-modifier> <disable>; 

}

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

• leave—Trace leave-group messages (for IGMP version 2 only).
• mtrace—Trace mtrace packets. Use the mtrace command to troubleshoot the software.
• packets—Trace all IGMP packets.
• query—Trace IGMP membership query messages, including general and group-specific queries.
• report—Trace membership report messages.

You can configure this statement at the following hierarchy levels:

• [edit protocols igmp]
• [edit logical-routers logical-router-name protocols igmp]

To trace the paths of multicast packets, use the mtrace command, as described in the JUNOS Protocols, Class of Service, and Systems Basics Management Command Reference.

For information about tracing and global tracing options, see the JUNOS Routing Protocols Configuration Guide.

Example: Tracing IGMP Protocol Traffic

Trace only unusual or abnormal operations to routing-log, and trace all IGMP packets to igmp-log:

[edit]

routing-options {

    traceoptions {

        file routing-log;

        flag errors;

    }

}

protocols {

    igmp { 

        traceoptions {

            file igmp-log;

            flag packets;

        }

    }

}