Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring IGMP Snooping Tracing Operations (CLI Procedure)

    By enabling tracing operations for IGMP 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 IGMP Snooping

    Tracing Operation

    Flag

    Trace all (equivalent of including all flags).

    all

    Trace general IGMP snooping protocol events.

    general

    Trace communication over routing socket events.

    krt

    Trace leave reports (IGMPv2 and IGMPv3 only).

    leave

    Trace nexthop-related events.

    nexthop

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

    normal

    Trace all IGMP packets.

    packets

    Trace policy processing.

    policy

    Trace IGMP 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

    This topic covers:

    Configuring Tracing Operations

    To configure tracing operations for IGMP snooping:

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

      For example:

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

      For example:

      [edit protocols igmp-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:
      [edit protocols igmp-snooping ]
      user@switch # set traceoptions flag flagname

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

      [edit protocols igmp-snooping ]
      user@switch# set traceoptions flag vlan
      [edit protocols igmp-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:

    user@switch> file show /var/log/igmp-snoop-trace

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

    [edit] 
    user@switch# deactivate protocols igmp-snooping traceoptions
    [edit] 
    user@switch# activate protocols igmp-snooping traceoptions

    Modified: 2014-09-24