Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Example: Recording MLD Join and Leave Events

This example shows how to determine whether MLD tuning is needed in a network by configuring the routing device to record MLD join and leave events.

Requirements

Before you begin:

Overview

Table 1 describes the recordable MLD join and leave events.

Table 1: MLD Event Messages

ERRMSG Tag

Definition

RPD_MLD_JOIN

Records MLD join events.

RPD_MLD_LEAVE

Records MLD leave events.

RPD_MLD_ACCOUNTING_ON

Records when MLD accounting is enabled on an MLD interface.

RPD_MLD_ACCOUNTING_OFF

Records when MLD accounting is disabled on an MLD interface.

RPD_MLD_MEMBERSHIP_TIMEOUT

Records MLD membership timeout events.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

set protocols mld interface fe-0/1/0.2 accountingset system syslog file mld-events any infoset system syslog file mld-events match ".*RPD_MLD_JOIN.* | .*RPD_MLD_LEAVE.* | .*RPD_MLD_ACCOUNTING.* | .*RPD_MLD_MEMBERSHIP_TIMEOUT.*"set system syslog file mld-events archive size 100000set system syslog file mld-events archive files 3set system syslog file mld-events archive transfer-interval 1440set system syslog file mld-events archive archive-sites "ftp://user@host1//var/tmp" password "anonymous"set system syslog file mld-events archive archive-sites "ftp://user@host2//var/tmp" password "test"

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure recording of MLD join and leave events:

  1. Enable accounting globally or on an MLD interface. This example shows the interface configuration.

    [edit protocols mld]user@host# set interface fe–0/1/0.2 accounting
  2. Configure the events to be recorded, and filter the events to a system log file with a descriptive filename, such as mld-events.
    [edit system syslog file mld-events]user@host# set any info[edit system syslog file mld-events]user@host# set match “.*RPD_MLD_JOIN.* | .*RPD_MLD_LEAVE.* | .*RPD_MLD_ACCOUNTING.* | .*RPD_MLD_MEMBERSHIP_TIMEOUT.*”
  3. Periodically archive the log file.

    This example rotates the file every 24 hours (1440 minutes) when it reaches 100 KB and keeps three files.

    [edit system syslog file mld-events]user@host# set archive size 100000[edit system syslog file mld-events]user@host# set archive files 3[edit system syslog file mld-events]user@host# set archive archive-sites “ftp://user@host1//var/tmp” password “anonymous”[edit system syslog file mld-events]user@host# set archive archive-sites “ftp://user@host2//var/tmp” password “test”[edit system syslog file mld-events]user@host# set archive transfer-interval 1440[edit system syslog file mld-events]user@host# set archive start-time 2011–01–07:12:30
  4. If you are done configuring the device, commit the configuration.

    [edit system syslog file mld-events]]user@host# commit

Verification

You can view the system log file by running the file show command.

user@host> file show mld-events

You can monitor the system log file as entries are added to the file by running the monitor start and monitor stop commands.

user@host> monitor start mld-events
*** mld-events ***
Apr 16 13:08:23  host mgd[16416]: UI_CMDLINE_READ_LINE: User 'user', command 'run monitor start mld-events '
monitor 

Published: 2013-08-13