multicast mx

IMPLEMENTATION GUIDE

Copyright © 2009, Juniper Networks, Inc. 1

ENTERPRISE MULTICAST IMPLEMENTATION GUIDE FOR LAYER 2 NETWORKS USING THE EX SERIES ETHERNET SWITCHES AND MX SERIES 3D UNIVERSAL EDGE ROUTERS

Although Juniper Networks has attempted to provide accurate information in this guide, Juniper Networks does not warrant or guarantee the accuracy of the information provided herein. Third party product descriptions and related technical details provided in this document are for information purposes only and such products are not supported by Juniper Networks. All information provided in this guide is provided “as is”, with all faults, and without warranty of any kind, either expressed or implied or statutory. Juniper Networks and its suppliers hereby disclaim all warranties related to this guide and the information contained herein, whether expressed or implied of statutory including, without limitation, those of merchantability, fitness for a particular purpose and noninfringement, or arising from a course of dealing, usage, or trade practice.

2 Copyright © 2009, Juniper Networks, Inc.

IMPLEMENTATION GUIDE - Enterprise Multicast Implementation Guide for Layer 2 Networks Using the EX Series Ethernet Switches and MX Series 3D Universal Edge Routers

Table of Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Overview of IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

IGMP Version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

IGMP Version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

IGMP Version 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Selecting the IGMP Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Reducing Multicast Flooding With IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Reducing IGMP Membership Packets with IGMP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Implementation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

IGMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

IGMP Snooping Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Implementation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Hardware Used For the Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Software Used For the Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Detailed Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

MX-B Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Show IGMP Snooping Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Show IGMP Snooping Route Ethernet-Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Show IGMP Snooping Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Show IGMP Snooping VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Show IGMP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Show IGMP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Show IGMP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Clearing Statistics and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Restarting Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Trace Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Appendix: Conventions/Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

About Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47



Table of Figures

Figure 1: IGMPv1 packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Figure 2: IGMPv2 join, query, and leave processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 3: IGMPv2 packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 4: IGMPv3 query message packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Figure 5: IGMPv3 membership report packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Figure 6: IGMPv3 group record format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Figure 7: Network topology diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13



Introduction

Enterprise customers are increasingly deploying multicast forwarding in their networks to deliver applications such

as video conferencing, distance learning, and distribution of software, stock quotes, and news. They use Protocol

Independent Multicast (PIM) for multicast signaling and the Internet Group Management Protocol (IGMP) to manage

host multicast group membership.

The objective of this document is to provide a Layer 2 multicast implementation guide for enterprise networks using

the Juniper Networks® EX Series Ethernet Switches and Juniper Networks MX Series 3D Universal Edge Routers. This

document is targeted for deployments where the EX Series Ethernet Switches are used in the access layer, while

core and aggregation are collapsed into one layer using the MX Series 3D Universal Edge Routers. It first provides

an overview of IGMP and general design considerations and deployment options. It then provides implementation

guidelines with configuration procedures. Finally, an implementation example is included along with the network

topology, detailed configurations, as well as verification and troubleshooting procedures.

Scope

This guide describes a Layer 2 implementation for enterprise environments using the EX Series and MX Series. Its main

focus is IGMP and IGMP snooping. In this implementation, the Juniper Networks EX4200 Ethernet Switch and Juniper

Networks EX3200 Ethernet Switch are used as Layer 2 access devices with IGMP snooping enabled, while the MX

Series sits at the Layer 2/Layer 3 boundary of the network and use IGMP and PIM.

Rapid Spanning Tree Protocol (RSTP) is enabled for loop prevention but is not the main focus of this document.

It is described in more details in “Enterprise Layer 2 Network Designs, Implementing a Layer 2 Design with RSTP”

implementation guide. PIM is also used but is described in more detail in “Enterprise Layer 3 Multicast Implementation

Guide using the EX Series and MX Series.” This document does not discuss Distance Vector Multicast Routing Protocol

(DVMRP), Multicast Source Discovery Protocol (MSDP), Session Announcement Protocol (SAP), or multicast VPN. It

also does not cover IPv6.

Target Audience

This document is intended for network design and operation engineers or other technical audiences seeking multicast

implementation guidelines for Layer 2 enterprise deployments using the EX Series and MX Series.

Overview of IGMP

The IGMP manages group membership between hosts and routers. For each attached network, a multicast router can

be either a querier or a nonquerier. The following types of messages are exchanged between IGMP hosts and routers:

• Query messages are sent periodically by querier routers to solicit group membership information.

• Report messages are sent by hosts on the network that are members of a multicast group.

• Leave-group messages are sent by hosts when they leave a group (if running IGMP version 2).

IGMP Version 1

IGMP version 1 is defined by RFC 1112. IGMPv1 routers periodically transmit host membership query messages to the all

hosts address (224.0.0.1) to determine which groups have listeners on directly attached networks. When a host receives

a query message (that has IP TTL set to 1), it responds with a membership report for each group to which it belongs.

The packet format for IGMPv1 is shown below:

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Version Type Unused IGMP Checksum

Group Address

Figure 1: IGMPv1 packet format

In a query message, the group address field is zeroed when sent and ignored when received. In a report message, the

group address field holds the IP host group address of the group being reported.



IGMP Version 2

IGMP version 2 is defined by RFC 2236. IGMPv2 enhances IGMPv1 by:

• Adding group specific query messages

• Allowing the querier router to specify a maximum query/response time to control burstiness and fine tune leave latencies

• Adding query election process where the router with the lowest IP address on the subnet is elected the querier

• Adding explicit leave-group messages that significantly improve the leave latency

The following figure shows examples of IGMPv2 join (A), query-response (B) and leave-group (C) mechanisms:

Figure 2: IGMPv2 join, query, and leave processes

The packet format for IGMP v2 is shown below:

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Type Type IGMP Checksum

Group Address

Figure 3: IGMPv2 packet format

The max response time field is used only in membership query messages. It specifies the maximum allowed time

before sending a responding report in units of 1/10 second. In all other messages, it is set to zero by the sender and

ignored by receivers.

A) IGMPv2 join process

Unsolicited Membership ReportGroup = 225.0.0.3

General QueryDestination = 224.0.0.1

Membership ReportGroup = 225.0.0.3

Leave-group MessageGroup = 225.0.0.3

Group Specific QueryGroup = 225.0.0.3

B) IGMPv2 query-response process

C) IGMPv2 leave-group process

Host 1 Querier

Host 1 Querier

Host 1 Querier



IGMP Version 3

IGMP version 3 is defined by RFC 3376. IGMPv3 supports source-specific multicast (SSM), which allows a host to issue

a join to a specific source (S,G) as opposed to all sources (*,G).

The query message packet format for IGMPv3 is shown below. The first entries for type, max response code (same as

IGMPv2 maximum response time), checksum, and group address match IGMPv2 for backwards compatibility. Source

address information is also added to support SSM. The query packet may be sent to the all hosts 224.0.0.1 multicast

group address for general queries or may be sent to a specific multicast group address when querying for members of

that group.

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Type Max Response Time IGMP Checksum

Group Address

Resv S QRV QQIC Number of Sources (N)

Source Address [1]

.

.

Source Address [N]

Figure 4: IGMPv3 query message packet format

The membership report message packet format for IGMPv3 is shown below. The packet consists of one or more

group records, each record detailing specific IGMPv3 state information. It is sent to the 224.0.0.22 group address

(all IGMPv3 routers).

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Type Max Response Time IGMP Checksum

Group Address

Reserved Number of Sources (N)

.

Group Record [1]

.

.

.

.

.

.

.

.

Group Record [M]

.

Figure 5: IGMPv3 membership report packet format



Each group record has the following internal format:

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Record Type Aux Data Len Number of Sources (N)

Multicast Address

Source Address [1]

.

.

Source Address [N]

.

Auxiliary Data

.

Figure 6: IGMPv3 group record format

Design Considerations

Selecting the IGMP Version

The table below provides a comparison of IGMP versions supported by Juniper Networks Junos® operating system:

Table 1: IGMP Versions ComparisonVERSION RFC PROS CONS

Version 1 1112 • Periodic host membership query messages sent by

all routers to all-hosts group address (224.0.0.1).

• High latency. Since there is no leave-group

mechanism, multicast traffic can continue to be

forwarded for several minutes after the last host

leaves the group.

Version 2 2236 • Adds querier election process: the lowest IP

address on the LAN is selected.

• Defines group-specific query and explicit leave-

group messages.

• Improved latency compared to version 1.

Version 3 3376 • Enhances version 2 support of leave-group

messages by introducing group-and-source

specific report messages.

• Accommodates SSM.

• Improved latency compared to version 1.

• Efficiency gain compared to version 2.

• Can also support a sparse-mode topology without

a rendezvous point (RP).

• Hosts need to have a priori knowledge of the

specific sources active for a given group.

Note: Junos OS defaults to IGMPv2.

Reducing Multicast Flooding With IGMP Snooping

To avoid flooding of all multicast traffic on a virtual LAN (VLAN), IGMP snooping should be enabled on access switches

so they intercept IGMP packets. The switch then uses the content of the packets to build a multicast cache table that

is a database of multicast groups and their corresponding member ports. This table is used to regulate multicast traffic

on the VLAN.

Note: Factory-deafult configuration on EX Series switches enables IGMP snooping on all VLANs using “set protocols

igmp-snooping vlan all” command.

Reducing IGMP Membership Packets with IGMP Proxy

In deployments where an aggregation switch is an IGMP querier and the access switch has many hosts, sending IGMP

queries to all hosts results into a storm of IGMP membership packets. IGMP proxy allows the access switch to prevent

that by generating IGMP reports on behalf of the hosts. The switch also generates a periodic IGMP query to hosts to

maintain its list of group/port membership. When a host sends an IGMP join message, the switch suppresses this

report (and update its timer) if this is not the first join for the group on that VLAN. Similarly, leave messages received

from a host are suppressed unless it is the last leave for the group on the VLAN.

Note: IGMP snooping proxy is not supported on EX Series platforms according to release 9.3.



Implementation

Implementation Guidelines

IGMP Configuration

Enabling/Disabling IGMP

PIM is needed on upstream IGMP interfaces to distribute IGMP group memberships into the multicast routing domain.

By default, IGMP is automatically enabled on all interfaces on which PIM is configured. It is also possible to enable/

disable IGMP explicitly on an interface with the following statements:

Enabling IGMP explicitly on an interface: protocols{ igmp{ interfaceinterface-name; } }Disabling IGMP explicitly on an interface: protocols{ igmp{ interfaceinterface-name; disable; } }

Note: To enable/disable IGMP on all interfaces at once, use the same commands replacing the interface name with the

keyword “all”.

IGMP Version

The default IGMP version applied by Junos OS is version 2. The version used can be changed with the following

statement. Note that this can be done also at the interface level.

Changing the IGMP version: protocols{ igmp{ versionversion-number; } }

Note: If two routers run different versions of IGMP, they negotiate the lowest common version of IGMP that is

supported by hosts on their subnet.

IGMP Query-Interval

The querier interval is the time between periodic host-query messages sent to the all-systems IP address of 224.0.0.1. It

is set by default to 125 seconds but can be modified to a value from one to 1024 seconds using the following statement:

Modifying the IGMP query-interval: protocols{ igmp{ query-intervalseconds; } }



IGMP Query-Response Interval

The query-response-interval indicates the maximum duration between when the querier router sends a host-query

message and when it receives a response from a host. To adjust the burst peaks of IGMP messages on a subnet, this

timer can be modified from its default value of 10 seconds to a value between one and 1024 seconds as shown below:

Modifying the IGMP query-response-interval: protocols{ igmp{ query-response-intervalseconds; } }

IGMP Query-Last-Member-Interval

The following commands can be used to modify the IGMP query-last-member-interval. This interval indicates the

maximum amount of time between group-specific query messages, including those sent in response to leave-group

messages. Lowering this interval from its default value allows reducing the amount of time it takes to detect the loss of

the last member of a group.

By default, the last-member query interval is one second. It can be configured to any value in the range 0.1 through 0.9

seconds, and then one-second intervals from one through 1024 seconds.

Modifying the IGMP query-last-member interval: protocols{ igmp{ query-last-member-intervalseconds; } }

IGMP Robust-Count

The robust-count indicates the number of timeout intervals the switch waits before timing out a multicast group. You

can wait for more intervals if the subnet packet loss is high and IGMP report messages might be lost.

By default, the robust count is two. It can be configured to any value in the range two through 10 intervals.

Setting IGMP robust-count: protocols{ igmp{ robust-countcount; } }

IGMP Immediate-Leave

On IGMPv2, interfaces that have only one host connected, the router can be configured to remove a host from the

multicast group immediately after receiving a leave group message. The syntax is shown below:

Applying immediate-leave to an interface: protocols{ igmp{ interfaceinterface-name{ immediate-leave; } } }

Note: This should not be applied to interfaces attached to multiple hosts as the router would remove all hosts until

they send join requests in response to the router’s next general group membership query.



IGMP Promiscuous Mode

You can allow a router to accept IGMP messages from indirectly connected subnets (for example, from sources that do

not match the IP subnet of the interface). An interface is set to promiscuous mode using the following statements:

Applying the promiscuous-mode to an interface: protocols{ igmp{ interfaceinterface-name{ promiscuous-mode; } } }

Static IGMP

You can configure static IGMP to help test and verify multicast forwarding in the absence of receivers. The static join

can take the form of a (*,G) or (S,G) entry, based on the inclusion of a source address. If a source address is specified,

the IGMP version must be set to IGMPv3.

Configuring static IGMP: protocols{ igmp{ interfaceinterface-name{ static{ groupgroup-address{ sourceaddress; } } } } }

IGMP Snooping Configuration

Enabling IGMP Snooping

You can configure IGMP snooping:

• On all VLANs which is the factory-default configuration for EX Series switches.

• On all interfaces in a VLAN

• On individual interfaces in the VLAN

• Statically for a group on an individual interface

Enabling IGMP snooping in a VLAN: protocols{ igmp-snooping{ vlanvlan-id; } } }

Enabling IGMP snooping on a specific interface: protocols{ igmp-snooping{ vlanvlan-id interfaceinterface-name; } } }



Statically configuring IGMP snooping for a specific group on an interface: protocols{ igmp-snooping{ vlanvlan-id{ interfaceinterface-name{ static{ groupgroup-address; } } } } }

IGMP Snooping Immediate-Leave

It is possible to configure the switch to immediately remove a multicast group membership from an interface when it

receives a leave message from that interface and suppress the sending of any group-specific queries for the multicast

group (IGMPv2 only) as shown below:

Setting IGMP snooping on a VLAN to immediate leave: protocols{ igmp-snooping{ vlanvlan-id{ immediate-leave; } } }

IGMP Snooping Query-Interval

The following commands can be used to modify the IGMP snooping query-interval. This interval indicates how

often the querier router sends general host-query messages. By default, the query interval is 125 seconds. It can be

configured to any value in the range one through 1024 seconds.

Modifying the IGMP snooping query interval on a VLAN: protocols{ igmp-snooping{ vlanvlan-id{ query-intervalseconds; } } } }

IGMP Snooping Query-Response-Interval

The following commands can be used to modify the IGMP snooping query-response-interval. This interval indicates

how long the querier router waits to receive a response to a host-query message from a host. By default, the query

response interval is 10 seconds. It can be configured to any value in the range one through 1024 seconds. However, it

must be less than the query-interval.

Modifying the IGMP snooping query-response interval on a VLAN: protocols{ igmp-snooping{ vlanvlan-id{ query-response-intervalseconds; } } } }



IGMP Snooping Query-Last-Member-Interval

The following commands can be used to modify the IGMP snooping query-last-member-interval. This interval indicates

the maximum amount of time between group-specific query messages, including those sent in response to leave-

group messages. Lowering this interval from its default value allows reducing the amount of time it takes to detect the

loss of the last member of a group.

By default, the last-member query interval is one second. It can be configured to any value in the range of 0.1 through

0.9 seconds, and then one-second intervals from one through 1024 seconds.

Modifying the IGMP snooping query-last-member interval on a VLAN: protocols{ igmp-snooping{ vlanvlan-id{ query-last-member-intervalseconds; } } } }

IGMP Snooping Robust-Count

The robust-count indicates the number of timeout intervals the switch waits before timing out a multicast group. You

can wait more intervals if subnet packet loss is high and IGMP report messages might be lost.

By default, the robust count is two. It can be configured to any value in the range two through 10 intervals.

Setting IGMP snooping robust-count on a VLAN: protocols{ igmp-snooping{ vlanvlan-id{ robust-countcount; } } } }

Static Configuration of IGMP Group Membership on a Port

An interface can be configured with IGMP snooping to be a static member of a group:

Statically configuring IGMP group membership on a port: protocols{ igmp-snooping{ interfaceinterface-name{ static{ groupgroup-address; } } } }



Static Configuration of a Multicast-Router-Interface

An interface can be statically configured as a switching interface toward a multicast router (the interface to receive

multicast traffic):

VL

AN

40

0

VL

AN

40

0

VL

AN

30

0

VL

AN

20

0

VL

AN

30

0

VL

AN

20

0

VL

AN

50

0

VL

AN

50

0

EX-FC-2EX-VC-7, Backup

MX480

Virtual Chassis BVirtual Chassis A

EX-VC-6, LC1

EX-VC-5, Master

EX-VC-10, LC1

Virtual Chassis C

EX-VC-9, Backup

EX-VC-8, Master

M120

MX240

VL

AN

10

0

VLAN 100, 200, 300, 400, 500 VLAN 100, 200, 300, 400, 500 VLAN 100, 200, 300, 400, 500

VLAN 100, 200, 300, 400, 500

VLAN 100, 200, 300, 400, 500

VL

AN

100

OSPFArea 0.0.0.0

RSTP

Agilent N2XSender

Agilent N2XReceiver225.0.0.1

Agilent N2XSender

Agilent N2XReceivers225.0.0.2

Agilent N2XReceiver

225.0.0.2 & 225.0.0.3

ge-0/0/0

ge-2/0/0ge-2/0/23

203/4

ge-0/0/23

203/1

ge-0/0/0

ge-0/0/23ge-0/0/0ge-2/0/0ge-2/0/23

202/1201/2201/1203/3

ge-0/0/19

ge-0/0/1

ge-2/0/8ge-5/0/8

ge-2/0/9172.18.16.137/30

ge-5/0/9172.18.16.133/30

ge-5/1/0172.18.16.141/30

ge-5/0/1172.18.16.138/30

ge-5/0/0172.18.16.134/30

202/2172.18.16.142

ge-2/0/1

ae3ge-2/0/3, ge-2/0/7

ae0ge-5/0/0, ge-0/0/4

ae2ge-2/0/2, ge-2/0/6

ae1ge-2/0/1, ge-2/0/5

ae0ge-2/0/0, ge-2/0/4

ae3ge-5/0/3, ge-5/0/7

ae2ge-5/0/2, ge-5/0/6ae1

ge-5/0/1, ge-5/0/5

ae0ge-0/1/0, ge-0/1/2

ae1ge-0/1/1, ge-1/1/1

ae0ge-0/1/0, ge-1/1/0

ae1ge-2/1/2, ge-2/1/3

ae0ge-2/1/0, ge-2/1/1ae1

ge-0/1/1, ge-1/1/1

ge-0/0/2

ge-2/0/1ge-0/0/0

ae0ge-0/1/0, ge-1/1/0

203/2172.18.16.102

Berry-R1

Madras-MX-AAveo-MX-B

EX-VC-4, Backup

EX-VC-1, Master

ae1ge-0/1/1, ge-0/1/3

VLAN 100, 200, 300, 400, 500 VLAN 100, 200, 300, 400, 500

VLAN 100, 200, 300, 400, 500 VLAN 100, 200, 300, 400, 500

Statically configuring a multicast-router interface: protocols{ igmp-snooping{ interfaceinterface-name{ multicast-router-interface; } } }

Implementation Example

Figure 7: Network topology diagram



Hardware Used For the Implementation

Table 3: Implementation Example-Hardware RequirementsEQUIPMENT COMPONENTS

4 x EX4200 Ethernet Switch • 4 x 4-port uplink 1-Gigabit Ethernet module (EX Series UM-4SFP)

• 16 SFPs

• 8 x VCP cables

1 x MX240 Ethernet Services Router

1 x MX480 Ethernet Services Router

• 2 x 40-port 1-Gigabit Ethernet L2/L3 DPCs (DPCE-R-40GE-SFP or DPCE-R-Q-40GE-SFP)

• 20 SFPs

1 x M120 Multiservice Edge Router • 1 x FPC Type 3

• 1 x 10-port 1-Gigabit Ethernet PIC

• 2 SFPs

Agilent N2X tester • 10x 1-Gigabit Ethernet ports (9x RJ45 and 1 SFP type)

• 1 SFP

Software Used For the Implementation

In this topology, the EX Series acts as Layer 2 switches and uses RSTP for loop prevention. All EX Series Ethernet

Switches have IGMP snooping enabled. The MX Series switches have IRRBs configured with VRRP. They run RSTP

towards the access layer and OSPF towards the core. PIM-SM is used and MX-A and MX-B are configured as RPs using

Anycast-PIM without MSDP.

Table 4: Implementation Example–Software RequirementsEQUIPMENT FEATURES AND PROTOCOLS SOFTWARE

EX Series • RSTP

• AE

• IGMP snooping

Junos OS 9.3

MX Series • RSTP

• AE

• IRBs with VRRP

• OSPF

• IGMPv2

• PIM-SM

• Anycast RP

M Series platforms • OSPF

• PIM-SM

• Anycast RP



Detailed Configurations

EX-VC-1 Configuration

#…truncated…chassis{redundancy{graceful-switchover;}aggregated-devices{ethernet{device-count2;}}}interfaces{ge-0/0/0{unit0{familyethernet-switching{port-modeaccess;vlan{membersHR;}}}}ge-0/0/2{unit0{familyethernet-switching{port-modetrunk;vlan{members[ENGSALESHRSUPPORTFINANCE];}}}}ge-0/0/23{unit0{familyethernet-switching{port-modeaccess;vlan{membersHR;}}}}ge-0/1/0{ether-options{speed{1g;}802.3adae0;}}ge-0/1/1{ether-options{speed{1g;}



802.3adae1;}}ge-1/1/0{ether-options{speed{1g;}802.3adae0;}}ge-1/1/1{ether-options{speed{1g;}802.3adae1;}}ae0{unit0{familyethernet-switching{port-modetrunk;vlan{members[HRENGSALESSUPPORTFINANCE];}}}}ae1{unit0{familyethernet-switching{port-modetrunk;vlan{members[HRENGSALESSUPPORTFINANCE];}}}}lo0{unit0{familyinet{address172.18.8.1/32;}}}vme{unit0{familyinet{address172.19.59.190/24;}}}}routing-options{graceful-restart;}protocols{



igmp-snooping {vlanHR{#EnableIGMPsnoopingonVLANHRinterfaceae0.0{multicast-router-interface;}interfaceae1.0{multicast-router-interface;}}}rstp{interfacege-0/0/0.0{edge;}interfacege-0/0/2.0{modepoint-to-point;}interfacege-0/0/23.0{edge;}interfaceae0.0{modepoint-to-point;}interfaceae1.0{modepoint-to-point;}}}vlans{ENG{vlan-id200;}FINANCE{vlan-id500;}HR{vlan-id100;}SALES{vlan-id300;}SUPPORT{vlan-id400;}}virtual-chassis{preprovisioned;member0{rolerouting-engine;serial-numberBM0208105257;}member1{rolerouting-engine;serial-numberBP0208137931;}}




#…truncated…chassis{redundancy{graceful-switchover;}aggregated-devices{ethernet{device-count2;}}}interfaces{ge-0/0/0{unit0{familyethernet-switching{port-modeaccess;vlan{membersSALES;}}}}ge-0/0/23{unit0{familyethernet-switching{port-modeaccess;vlan{membersENG;}}}}ge-2/0/0{unit0{familyethernet-switching{port-modeaccess;vlan{membersENG;}}}}ge-2/0/1{unit0{familyethernet-switching{port-modetrunk;vlan{members[ENGSALESHRSUPPORTFINANCE];}}}}ge-2/0/23{unit0{familyethernet-switching{port-modeaccess;



vlan{membersSALES;}}}}ge-2/1/0{ether-options{speed{1g;}802.3adae0;}}ge-2/1/1{ether-options{speed{1g;}802.3adae0;}}ge-2/1/2{ether-options{speed{1g;}802.3adae1;}}ge-2/1/3{ether-options{speed{1g;}802.3adae1;}}ae0{unit0{familyethernet-switching{port-modetrunk;vlan{members[ENGSALESHRSUPPORTFINANCE];}}}}ae1{unit0{familyethernet-switching{port-modetrunk;vlan{members[ENGSALESHRSUPPORTFINANCE];}}}}



lo0{unit0{familyinet{address172.18.8.2/32;}}}vme{unit0{familyinet{address172.19.59.195/24;}}}}routing-options{graceful-restart;}protocols{igmp-snooping { traceoptions { # Traceoptions for IGMP snooping troubleshooting file snooping; flag query; flag report; flag route; flag state; flag task; flag timer; flag vlan; flag leave; }

vlanSALES{#EnableIGMPsnoopingonVLANSALESinterfaceae0.0{multicast-router-interface;}interfaceae1.0{multicast-router-interface;}}

vlanENG{#EnableIGMPsnoopingonVLANENGinterfaceae0.0{multicast-router-interface;}interfaceae1.0{multicast-router-interface;}}}rstp{interfacege-0/0/0.0{edge;}interfacege-0/0/23.0{edge;}interfacege-2/0/0.0{



edge;}interfacege-2/0/1.0{modepoint-to-point;}interfacege-2/0/23.0{edge;}interfaceae0.0{modepoint-to-point;}interfaceae1.0{modepoint-to-point;}}}vlans{ENG{vlan-id200;}FINANCE{vlan-id500;}HR{vlan-id100;}SALES{vlan-id300;}SUPPORT{vlan-id400;}}virtual-chassis{preprovisioned;/*ex-vc-5*/member0{rolerouting-engine;serial-numberBP0208180059;}/*ex-vc-7*/member1{rolerouting-engine;serial-numberBP0208180087;}/*ex-vc-6*/member2{roleline-card;serial-numberBQ0208189143;}}




#…truncated…chassis{redundancy{graceful-switchover;}aggregated-devices{ethernet{device-count2;}}}interfaces{ge-0/1/0{ether-options{speed{1g;}802.3adae0;}}ge-0/1/1{ether-options{speed{1g;}802.3adae1;}}ge-1/1/0{ether-options{speed{1g;}802.3adae0;}}ge-1/1/1{ether-options{speed{1g;}802.3adae1;}}ge-2/0/0{unit0{familyethernet-switching{port-modeaccess;vlan{membersSUPPORT;}}}}ge-2/0/1{unit0{familyethernet-switching{



port-modetrunk;vlan{members[HRENGSALESSUPPORTFINANCE];}}}}ge-2/0/23{unit0{familyethernet-switching{port-modeaccess;vlan{membersSUPPORT;}}}}ae0{unit0{familyethernet-switching{port-modetrunk;vlan{members[SUPPORTENGSALESHRFINANCE];}}}}ae1{unit0{familyethernet-switching{port-modetrunk;vlan{members[SUPPORTENGSALESHRFINANCE];}}}}lo0{unit0{familyinet{address172.18.12.1/32;}}}vme{unit0{familyinet{address172.19.59.198/24;}}}}routing-options{graceful-restart;}protocols{ igmp-snooping { vlan SUPPORT; # Enable IGMP snooping for VLAN SUPPORTinterfaceae0.0{



multicast-router-interface;}interfaceae1.0{multicast-router-interface;}}}rstp{interfacege-2/0/0.0{edge;}interfacege-2/0/1.0{modepoint-to-point;}interfacege-2/0/23.0{edge;}interfaceae0.0{modepoint-to-point;}interfaceae1.0{modepoint-to-point;}}}vlans{ENG{vlan-id200;}FINANCE{vlan-id500;}HR{vlan-id100;}SALES{vlan-id300;}SUPPORT{vlan-id400;}}virtual-chassis{preprovisioned;/*ex-vc-8*/member0{rolerouting-engine;serial-numberBN0208189106;}/*ex-vc-9*/member1{rolerouting-engine;serial-numberBP0208180160;}/*ex-vc-10*/member2{roleline-card;serial-numberBP0208180149;}



EX-FC-2 Configuration

#…truncated…chassis{aggregated-devices{ethernet{device-count2;}}}interfaces{ge-0/0/0{unit0{familyethernet-switching{vlan{membersFINANCE;}}}}ge-0/0/1{unit0{familyethernet-switching{port-modetrunk;vlan{members[HRENGSALESSUPPORTFINANCE];}}}}ge-0/0/19{unit0{familyethernet-switching{port-modeaccess;vlan{membersFINANCE;}}}}ge-0/1/0{ether-options{speed{1g;}802.3adae0;}}ge-0/1/1{ether-options{speed{1g;}802.3adae1;}}ge-0/1/2{ether-options{speed{



1g;}802.3adae0;}}ge-0/1/3{ether-options{speed{1g;}802.3adae1;}}ae0{unit0{familyethernet-switching{port-modetrunk;vlan{members[FINANCEHRENGSALESSUPPORT];}}}}ae1{unit0{familyethernet-switching{port-modetrunk;vlan{members[FINANCEHRENGSALESSUPPORT];}}}}lo0{unit0{familyinet{address172.18.12.2/32;}}}me0{unit0{familyinet{address172.19.59.208/24;}}}}routing-options{graceful-restart;}protocols{ igmp-snooping {

vlan FINANCE { # Enable IGMP snooping on VLAN FINANCEinterfaceae0.0{multicast-router-interface;}



interfaceae1.0{multicast-router-interface;}}}rstp{interfacege-0/0/0.0{edge;}interfacege-0/0/1.0{modepoint-to-point;}interfacege-0/0/19.0{edge;}interfaceae0.0{modepoint-to-point;}interfaceae1.0{modepoint-to-point;}}}vlans{ENG{vlan-id200;}FINANCE{vlan-id500;}HR{vlan-id100;}SALES{vlan-id300;}SUPPORT{vlan-id400;}



MX-A Configuration

#…truncated…chassis{redundancy{graceful-switchover;}aggregated-devices{ethernet{device-count4;}} fpc 5 { # Needed to create tunnel interface to de-encapsulate PIM register messages pic 0 { tunnel-services { bandwidth 1g; } } }}interfaces{ge-5/0/0{gigether-options{802.3adae0;}}ge-5/0/1{gigether-options{802.3adae1;}}ge-5/0/2{gigether-options{802.3adae2;}}ge-5/0/3{gigether-options{802.3adae3;}}ge-5/0/4{gigether-options{802.3adae0;}}ge-5/0/5{gigether-options{802.3adae1;}}ge-5/0/6{gigether-options{802.3adae2;}}ge-5/0/7{gigether-options{



802.3adae3;}}ge-5/0/8{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}ge-5/0/9{unit0{familyinet{address172.18.16.133/30;}}}ge-5/1/0{unit0{familyinet{address172.18.16.141/30;}}}ae0{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}ae1{vlan-tagging;encapsulationextended-vlan-bridge;



unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}ae2{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}ae3{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}irb{unit100{familyinet{address172.18.9.4/24{



vrrp-group1{virtual-address172.18.9.1;priority254;accept-data;}}}}unit200{familyinet{address172.18.10.4/24{vrrp-group2{virtual-address172.18.10.1;priority254;accept-data;}}}}unit300{familyinet{address172.18.11.4/24{vrrp-group3{virtual-address172.18.11.1;priority254;accept-data;}}}}unit400{familyinet{address172.18.13.4/24{vrrp-group4{virtual-address172.18.13.1;priority254;accept-data;}}}}unit500{familyinet{address172.18.14.4/24{vrrp-group5{virtual-address172.18.14.1;priority254;accept-data;}}}}}lo0 { unit 0 { family inet { address 172.18.19.1/32 { primary;



} address 172.18.19.254/32; # Loopback address used as shared anycast address } } }}routing-options{graceful-restart;static{route200.0.1.0/24reject;route200.0.2.0/24reject;}router-id172.18.19.1;}protocols{ospf{exportstat;area0.0.0.0{interfacege-5/0/9.0{authentication{md510key“$9$aPGjqTz6uORmfORhSMWJGDj.P”;##SECRET-DATA}}interfacelo0.0{passive;}interfacefxp0.0{disable;}interfacege-5/1/0.0{passive;}}}pim { rp { # Configuration of anycast-PIM on RP devices local { family inet { address 172.18.19.254; # Anycast-PIM address shared by the RPs anycast-pim { rp-set { address 172.18.19.2; # Local address of the other RP } local-address 172.18.19.1; # Local address of this RP } } } } interface all { # Sets all interfaces to PIM sparse mode mode sparse; } interface fxp0.0 { # Explicitly disables PIM on the management interface disable; }



}rstp{bridge-priority4k;interfacege-5/0/8{modepoint-to-point;}interfaceae0{modepoint-to-point;}interfaceae1{modepoint-to-point;}interfaceae2{modepoint-to-point;}interfaceae3{modepoint-to-point;}}}policy-options{policy-statementstat{fromprotocolstatic;thenaccept;}}bridge-domains{ENG{domain-typebridge;vlan-id200;interfaceae0.200;interfaceae1.200;interfaceae2.200;interfaceae3.200;interfacege-5/0/8.200;routing-interfaceirb.200;}FINANCE{domain-typebridge;vlan-id500;interfaceae0.500;interfaceae1.500;interfaceae2.500;interfaceae3.500;interfacege-5/0/8.500;routing-interfaceirb.500;}HR{domain-typebridge;vlan-id100;interfaceae0.100;interfaceae1.100;interfaceae2.100;interfaceae3.100;interfacege-5/0/8.100;routing-interfaceirb.100;}SALES{



domain-typebridge;vlan-id300;interfaceae0.300;interfaceae1.300;interfaceae2.300;interfaceae3.300;interfacege-5/0/8.300;routing-interfaceirb.300;}SUPPORT{domain-typebridge;vlan-id400;interfaceae0.400;interfaceae1.400;interfaceae2.400;interfaceae3.400;interfacege-5/0/8.400;routing-interfaceirb.400;}}



MX-B Configuration

#…truncated…chassis{redundancy{graceful-switchover;}aggregated-devices{ethernet{device-count4;}}fpc 2 { # Needed to create tunnel interface to de-encapsulate PIM register messages pic 0 { tunnel-services { bandwidth 1g; } } }}interfaces{ge-2/0/0{gigether-options{802.3adae0;}}ge-2/0/1{gigether-options{802.3adae1;}}ge-2/0/2{gigether-options{802.3adae2;}}ge-2/0/3{gigether-options{802.3adae3;}}ge-2/0/4{gigether-options{802.3adae0;}}ge-2/0/5{gigether-options{802.3adae1;}}ge-2/0/6{gigether-options{802.3adae2;}}ge-2/0/7{gigether-options{802.3adae3;}



}ge-2/0/8{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}ge-2/0/9{unit0{familyinet{address172.18.16.137/30;}}}ae0{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}ae1{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;



}unit500{vlan-id500;}}ae2{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}ae3{vlan-tagging;encapsulationextended-vlan-bridge;unit100{vlan-id100;}unit200{vlan-id200;}unit300{vlan-id300;}unit400{vlan-id400;}unit500{vlan-id500;}}irb{unit100{familyinet{address172.18.9.3/24{vrrp-group1{virtual-address172.18.9.1;accept-data;}}}}unit200{familyinet{address172.18.10.3/24{vrrp-group2{virtual-address172.18.10.1;accept-data;



}}}}unit300{familyinet{address172.18.11.3/24{vrrp-group3{virtual-address172.18.11.1;accept-data;}}}}unit400{familyinet{address172.18.13.3/24{vrrp-group4{virtual-address172.18.13.1;accept-data;}}}}unit500{familyinet{address172.18.14.3/24{vrrp-group5{virtual-address172.18.14.1;accept-data;}}}}}lo0 { unit 0 { family inet { address 172.18.19.2/32 { primary; } address 172.18.19.254/32; # Loopback address used as shared anycast address } } }}routing-options{graceful-restart;static{route200.0.1.0/24reject;route200.0.2.0/24reject;}router-id172.18.19.2;}protocols{ospf{exportstat;area0.0.0.0{interfacege-2/0/9.0{



authentication{md510key“$9$m5z6p0IreW9AeWLxwsP5Qz/C”;##SECRET-DATA}}interfacelo0.0{passive;}interfacefxp0.0{disable;}}}pim { traceoptions { # Traceoptions for PIM troubleshooting file pim; flag join detail; flag task detail; flag state detail; flag packets detail; } rp { # Uses the shared anycast address as the RPs address local { family inet { address 172.18.19.254; # Anycast-PIM address shared by the RPs anycast-pim { rp-set { address 172.18.19.1; # Local address of the other RP } local-address 172.18.19.2; # Local address of this RP } } } } interface all { mode sparse; # Sets all interfaces to PIM sparse mode } interface fxp0.0 { disable; # Explicitly disables PIM on the management interface } }rstp{bridge-priority8k;interfacege-2/0/8{modepoint-to-point;}interfaceae0{modepoint-to-point;}interfaceae1{modepoint-to-point;}interfaceae2{modepoint-to-point;}interfaceae3{modepoint-to-point;}}



}policy-options{policy-statementstat{fromprotocolstatic;thenaccept;}}bridge-domains{ENG{domain-typebridge;vlan-id200;interfaceae0.200;interfaceae1.200;interfaceae2.200;interfaceae3.200;interfacege-2/0/8.200;routing-interfaceirb.200;}FINANCE{domain-typebridge;vlan-id500;interfaceae0.500;interfaceae1.500;interfaceae2.500;interfaceae3.500;interfacege-2/0/8.500;routing-interfaceirb.500;}HR{domain-typebridge;vlan-id100;interfaceae0.100;interfaceae1.100;interfaceae2.100;interfaceae3.100;interfacege-2/0/8.100;routing-interfaceirb.100;}SALES{domain-typebridge;vlan-id300;interfaceae0.300;interfaceae1.300;interfaceae2.300;interfaceae3.300;interfacege-2/0/8.300;routing-interfaceirb.300;}SUPPORT{domain-typebridge;vlan-id400;interfaceae0.400;interfaceae1.400;interfaceae2.400;interfaceae3.400;interfacege-2/0/8.400;routing-interfaceirb.400;}}



Juniper Networks M120 Multiservice Edge Router Configuration

#…truncated…chassis{redundancy{graceful-switchover;}}interfaces{ge-5/0/0{unit0{familyinet{address172.18.16.134/30;}}}ge-5/0/1{unit0{familyinet{address172.18.16.138/30;}}}lo0{unit0{familyinet{address172.18.19.3/32{primary;}}}}}routing-options{graceful-restart;router-id172.18.19.3;}protocols{ospf{area0.0.0.0{interfacege-5/0/0.0{authentication{md510key“$9$aLGjqTz6uORmfORhSMWJGDj.P”;##SECRET-DATA}}interfacege-5/0/1.0{authentication{md510key“$9$.fQntu1ylM/ClM8XbwmfTQ69”;##SECRET-DATA}}interfacelo0.0{passive;}interfacefxp0.0{disable;}}}



pim { rp { # Configuration of anycast-PIM on non-RP devices static { address 172.18.19.254; # Uses the shared anycast address as the RP address } } interface all { mode sparse; # Sets all interfaces to PIM sparse mode } interface fxp0.0 { disable; # Explicitly disables PIM on the management interface } }}

Verification

This section lists some commands that can be used to verify this setup along with sample outputs:

IGMP Snooping

The following commands were executed on the EX Series switches to verify IGMP snooping:

Show IGMP Snooping Membership

The IGMP snooping cache can be displayed through the “show igmp-snooping membership” command as

shown below:

lab@ex-vc-1>show igmp-snooping membershipVLAN:HR225.0.0.1*171secsInterfaces:ge-0/0/23.0

{master:0}

Show IGMP Snooping Route Ethernet-Switching

The forwarding state that is generated can be seen through the “show igmp-snooping route ethernet-switching”:

lab@ex-vc-5>show igmp-snooping route ethernet-switching detailVLANGroupNext-hopENG224.0.0.0,*1303Interfaces:ae0.0VLANGroupNext-hopENG225.0.0.2,*1313Interfaces:ae0.0,ge-2/0/0.0,ge-0/0/23.0VLANGroupNext-hopSALES224.0.0.0,*1303Interfaces:ae0.0VLANGroupNext-hopSALES225.0.0.2,*1314Interfaces:ae0.0,ge-0/0/0.0,ge-2/0/23.0{master:0}



Show IGMP Snooping Statistics

This command shows message and error counts related to IGMP snooping:

lab@ex-vc-5>showigmp-snoopingstatisticsBadlength:0Badchecksum:0Invalidinterface:0Notlocal:0Receiveunknown:0Timedout:0

IGMPTypeReceivedTransmitedRecvErrorsQueries:7125100Reports:14254142520Leaves:000Other:000

{master:0}

Show IGMP Snooping VLANs

lab@ex-vc-5>show igmp-snooping vlans detailVLAN:ENG,Tag:200Membershiptimeout:260,Queriertimeout:255Interface:ae0.0,tagged,Groups:0,Reporters:0,Interface:ae1.0,tagged,Groups:0,Reporters:0Interface:ge-0/0/23.0,untagged,Groups:1,Reporters:1Interface:ge-2/0/0.0,untagged,Groups:1,Reporters:1Interface:ge-2/0/1.0,tagged,Groups:0,Reporters:0VLAN:SALES,Tag:300Membershiptimeout:260,Queriertimeout:255Interface:ae0.0,tagged,Groups:0,Reporters:0,Interface:ae1.0,tagged,Groups:0,Reporters:0Interface:ge-0/0/0.0,untagged,Groups:1,Reporters:1Interface:ge-2/0/1.0,tagged,Groups:0,Reporters:0Interface:ge-2/0/23.0,untagged,Groups:1,Reporters:1

{master:0}lab@ex-vc-5>

IGMP

The following commands were executed on the MX Series routers to verify IGMP:

Show IGMP Interface

This command lists information about the interfaces running IGMP including their state, the IGMP querier address,

the IGMP version, and the number of groups currently active. It also lists the derived and configured timer and counter

parameters for IGMP (all use the default values in the example below).

lab@Madras-MX-A>show igmp interfaceInterface:irb.100Querier:172.18.9.3State:UpTimeout:237Version:2Groups:1Immediateleave:OffPromiscuousmode:OffInterface:irb.200Querier:172.18.10.3State:UpTimeout:220Version:2Groups:1Immediateleave:OffPromiscuousmode:OffInterface:irb.300Querier:172.18.11.3



State:UpTimeout:254Version:2Groups:1Immediateleave:OffPromiscuousmode:OffInterface:irb.400Querier:172.18.13.3State:UpTimeout:146Version:2Groups:2Immediateleave:OffPromiscuousmode:OffInterface:ge-5/0/9.0Querier:172.18.16.133State:UpTimeout:NoneVersion:2Groups:0Immediateleave:OffPromiscuousmode:OffInterface:ge-5/1/0.0Querier:172.18.16.141State:UpTimeout:NoneVersion:2Groups:0Immediateleave:OffPromiscuousmode:OffInterface:irb.500Querier:172.18.14.3State:UpTimeout:163Version:2Groups:0Immediateleave:OffPromiscuousmode:Off

ConfiguredParameters:IGMPQueryInterval:125.0IGMPQueryResponseInterval:10.0IGMPLastMemberQueryInterval:1.0IGMPRobustnessCount:2

DerivedParameters:IGMPMembershipTimeout:260.0IGMPOtherQuerierPresentTimeout:255.0

{master}

Show IGMP Group

Use this command to show the groups joined by directly connected hosts and other routers. Note that if IGMP is

explicitly enabled but PIM is not enabled on an interface, the status of that interface will be shown as “Up” but it is

omitted from the output of the “show igmp group.”

lab@Madras-MX-A>show igmp groupInterface:irb.100Group:225.0.0.1Source:0.0.0.0Lastreportedby:172.18.9.2Timeout:178Type:DynamicInterface:irb.200Group:225.0.0.2Source:0.0.0.0Lastreportedby:172.18.10.2Timeout:165Type:DynamicInterface:irb.300Group:225.0.0.2Source:0.0.0.0Lastreportedby:172.18.11.2Timeout:197Type:Dynamic



Interface:irb.400Group:225.0.0.2Source:0.0.0.0Lastreportedby:172.18.13.2Timeout:210Type:DynamicGroup:225.0.0.3Source:0.0.0.0Lastreportedby:172.18.13.2Timeout:217Type:DynamicInterface:localGroup:224.0.0.2Source:0.0.0.0Lastreportedby:LocalTimeout:0Type:DynamicGroup:224.0.0.5Source:0.0.0.0Lastreportedby:LocalTimeout:0Type:DynamicGroup:224.0.0.6Source:0.0.0.0Lastreportedby:LocalTimeout:0Type:DynamicGroup:224.0.0.18Source:0.0.0.0Lastreportedby:LocalTimeout:0Type:DynamicGroup:224.0.0.22Source:0.0.0.0Lastreportedby:LocalTimeout:0Type:Dynamic

{master

Show IGMP Statistics

This command displays IGMP-related messages and error counts as shown in the example below:

lab@Madras-MX-A>show igmp statisticsIGMPpacketstatisticsforallinterfacesIGMPMessagetypeReceivedSentRxerrorsMembershipQuery620V1MembershipReport000DVMRP000PIMV1000CiscoTrace000V2MembershipReport700GroupLeave000MtraceResponse000MtraceRequest000DomainWideReport000V3MembershipReport000OtherUnknowntypes0IGMPv3unsupportedtype0IGMPv3sourcerequiredforSSM0IGMPv3modenotapplicableforSSM0



IGMPGlobalStatisticsBadLength0BadChecksum0BadReceiveIf14Rxnon-local0Timedout824RejectedReport0TotalInterfaces7

{master}

Troubleshooting

Clearing Statistics and Usage

• Clear IGMP statistics

• Clear IGMP snooping membership (for EX Series platforms)

• Clear IGMP snooping statistics (for EX Series platforms)

Restarting Processes

• Restart multicast snooping

• Restart Ethernet switching (for EX Series platforms)

Trace Options

• Set protocols IGMP traceoptions flag query detail

• Set protocols igmp traceoptions flag report detail

• Set protocols igmp traceoptions flag leave detail (IGMP version 2 only)

• Set protocols igmp traceoptions flag packets detail

• Set protocols igmp traceoptions flag route detail

• Set protocols igmp-snooping traceoptions flag query detail

• Set protocols igmp-snooping traceoptions flag report detail

• Set protocols igmp-snooping traceoptions flag leave detail (IGMP version 2 only)

• Set protocols igmp-snooping traceoptions flag packets detail

• Set protocols igmp-snooping traceoptions flag route detail

• Set protocols igmp-snooping traceoptions flag vlan detail

Summary

Juniper Networks provides enterprise customers with a variety of solutions to implement multicast forwarding

based on their specific requirements to deliver applications such as interactive distance learning, corporate video

conferencing, inventory updates, software, and content distribution. This document gave a brief overview of IGMP

support in Junos operating system. It then presented implementation guidelines for Layer 2 multicast deployments

in enterprise networks using the EX Series and MX Series. Finally, an implementation example was presented with

detailed configurations, verifications, and troubleshooting procedures.



8010061-001-EN Dec 2009

Copyright 2009 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

EMEA Headquarters

Juniper Networks Ireland

Airside Business Park

Swords, County Dublin, Ireland

Phone: 35.31.8903.600

EMEA Sales: 00800.4586.4737

Fax: 35.31.8903.601

APAC Headquarters

Juniper Networks (Hong Kong)

26/F, Cityplaza One

1111 King’s Road

Taikoo Shing, Hong Kong

Phone: 852.2332.3636

Fax: 852.2574.7803

Corporate and Sales Headquarters

Juniper Networks, Inc.

1194 North Mathilda Avenue

Sunnyvale, CA 94089 USA

Phone: 888.JUNIPER (888.586.4737)

or 408.745.2000

Fax: 408.745.2100

www.juniper.net

To purchase Juniper Networks solutions,

please contact your Juniper Networks

representative at 1-866-298-6428 or

authorized reseller.

Printed on recycled paper

Appendix: Conventions/Glossary

DPC Dense Port Concentrator

DVMRP Distance Vector Multicast Routing Protocol

FPC Flexible PIC Concentrator

IGMP Internet Group Management Protocol

MSDP Multicast Source Discovery Protocol

MVPN Multicast Virtual Private Network

OSPF Open Shortest Path First

P2P Point to Point

PIC Physical Interface Card

PIM Protocol Independent Multicast

PIM SM PIM sparse mode

PFE Packet Forwarding Engine

RE Routing Engine

RP Rendezvous Point

SFP Small form-factor pluggable transceiver

SPT Shortest Path Tree

SSM Source-specific multicast

VLAN Virtual LAN

VRRP Virtual Router Redundancy Protocol

About Juniper Networks

Juniper Networks, Inc. is the leader in high-performance networking. Juniper offers a high-performance network

infrastructure that creates a responsive and trusted environment for accelerating the deployment of services and

applications over a single network. This fuels high-performance businesses. Additional information can be found at

www.juniper.net.

multicast mx

Documents

igmp version

igmp configuration

igmp group

igmp proxy7 implementation

igmp snooping42

igmp interface

overview of igmp

igmp snooping configuration