Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Multicast Protocols User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring MLD Snooping Tracing Operations on EX Series Switches (CLI Procedure)

date_range 10-Jun-22

By enabling tracing operations for MLD snooping, you can record detailed messages about the operation of the protocol, such as the various types of protocol packets sent and received. Table 1 describes the tracing operations you can enable and the flags used to specify them in the tracing configuration.

Table 1: Supported Tracing Operations for MLD Snooping

Tracing Operation

Flag

Trace all (equivalent of including all flags).

all

Trace general MLD snooping protocol events.

general

Trace communication over routing socket events.

krt

Trace leave reports.

leave

Trace next-hop-related events.

nexthop

Trace normal MLD snooping protocol events. If you do not specify this flag, only unusual or abnormal operations are traced.

normal

Trace all MLD packets.

packets

Trace policy processing.

policy

Trace MLD membership query messages.

query

Trace membership reports

report

Trace routing information.

route

Trace state transitions.

state

Trace routing protocol task processing.

task

Trace timer processing.

timer

Trace VLAN-related events.

vlan

Configuring Tracing Operations

To configure tracing operations for MLD snooping:

  1. Configure the filename for the trace file:
    content_copy zoom_out_map
    [edit protocols mld-snooping ]user@switch# set traceoptions file filename

    For example:

    content_copy zoom_out_map
    [edit protocols mld-snooping ]user@switch# set traceoptions file mld-snoop-trace
  2. (Optional) Configure the maximum number of trace files and size of the trace files:
    content_copy zoom_out_map
    [edit protocols mld-snooping ]user@switch # set file files number size size

    For example:

    content_copy zoom_out_map
    [edit protocols mld-snooping ]user@switch # set traceoptions file files 5 size 1m

    causes the contents of the trace file to be emptied and archived in a .gz file when the file reaches 1 MB. Four archive files are maintained, the contents of which are rotated whenever the current active trace file is archived.

    If you omit this step, the maximum number of trace files defaults to 10, with the maximum file size defaulting to 128 K.

  3. Specify one of the tracing flags shown in Table 1:
    content_copy zoom_out_map
    [edit protocols mld-snooping ]user@switch # set traceoptions flag flagname

    For example, to perform trace operations on VLAN-related events and MLD query messages:

    content_copy zoom_out_map
    [edit protocols mld-snooping ]user@switch# set traceoptions flag vlan
    content_copy zoom_out_map
    [edit protocols mld-snooping ]user@switch# set traceoptions flag query

Viewing, Stopping, and Restarting Tracing Operations

When you commit the configuration, tracing operations begin. You can view the trace file in the /var/log directory. For example:

content_copy zoom_out_map
user@switch> file show /var/log/mld-snoop-trace

You can stop and restart tracing operations by deactivating and reactivating the configuration:

content_copy zoom_out_map
[edit] user@switch# deactivate protocols mld-snooping traceoptions
content_copy zoom_out_map
[edit] user@switch# activate protocols mld-snooping traceoptions
footer-navigation