Recording IGMP Join and Leave Events

To determine whether IGMP tuning is needed in a network, you can configure the routing device to record IGMP join and leave events. You can record events globally for the routing device or for individual interfaces.

Table 4 describes the recordable IGMP events.

To enable IGMP accounting:

1. Enable accounting globally or on an IGMP interface. This example shows both options.
   [edit]user@host# edit protocols igmpuser@host# set accountinguser@host# set interface fe–0/1/0.2 accountinguser@host# exit
2. Configure the events to be recorded and filter the events to a system log file with a descriptive filename, such as igmp-events.
   [edit]user@host# edit system syslog file igmp-eventsuser@host# set any infouser@host# set match “.*RPD_IGMP_JOIN.* | .*RPD_IGMP_LEAVE.* | .*RPD_IGMP_ACCOUNTING.* | .*RPD_IGMP_MEMBERSHIP_TIMEOUT.*”
3. Periodically archive the log file.

   This example rotates the file size when it reaches 100 KB and keeps three files.

   [edit system syslog file igmp-events]user@host# set archive size 100000user@host# set archive files 3user@host# set archive archive-sites “ftp://user@host1//var/tmp” password “anonymous”user@host# set archive archive-sites “ftp://user@host2//var/tmp” password “test”user@host# set archive transfer-interval 24user@host# set archive start-time 2011–01–07:12:30
4. 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 igmp-events

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

Related Topics

• IGMP Overview
• Specifying Log File Size, Number, and Archiving Properties in the Junos System Basics Configuration Guide