[Contents] [Prev] [Next] [Index] [Report an Error]

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-systems logical-system-name routing-options] hierarchy level. Options applied at the routing options level trace all packets, and options applied at the protocol level trace only IGMP traffic. You can specify MLD-specific options by including the traceoptions statement:




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

You can include this statement at the following hierarchy levels:

[edit protocols mld]
[edit logical-systems logical-system-name protocols mld]

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.

To trace the paths of multicast packets, use the mtrace command, as described in the JUNOS System Basics and Services 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 the file routing-log, and trace all MLD packets to the file mld-log:



[edit]
routing-options {


traceoptions {
file routing-log;
flag errors;
}


}
protocols {



mld { 


traceoptions {
file mld-log;
flag packets;
}


}


}

[Contents] [Prev] [Next] [Index] [Report an Error]