Tracing MLD Protocol Traffic

To trace MLD 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, and you can specify MLD-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 MLD-specific options in the MLD flag statement:

• leave—Trace leave-group messages (for version 2 only).
• mtrace—Trace mtrace packets. Use the mtrace command to troubleshoot the software.
• packets—Trace all MLD packets.
• query—Trace MLD 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 mld]
• [edit logical-routers logical-router-name protocols mld]

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

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

Example: Tracing MLD Protocol Traffic

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

[edit]

routing-options {

    traceoptions {

        file routing-log;

        flag errors;

    }

}

protocols {

    mld { 

        traceoptions {

            file mld-log;

            flag packets;

        }

    }

}