Stopping Snoopers From Snooping Non-Igmp Messages; Example - Allied Telesis AR400 Series How To Configure

Alliedware os igmp for multicasting on routers and managed layer 3 switches
Hide thumbs Also See for AR400 Series:
Table of Contents

Advertisement

Stopping snoopers from snooping non-IGMP
messages
Some networks include routers that have no interest in IGMP, but still generate multicast
messages by running protocols like OSPF. When a Snooper receives multicast messages from
such a router, the Snooper adds the router's port to its All Groups port list. This means the
router is unnecessarily sent IGMP and multicast traffic. Using IGMP features to prevent the
excess traffic is particularly helpful when you cannot or do not want to control the traffic at
the router.
This example describes how to use AlliedWare's advanced IGMP features to prevent this
behaviour, by limiting the ports that the Snooper adds to the All Groups list, or by stopping
particular types of traffic from adding ports to the All Groups list.

Example

The example is based around a network that has a router running OSPF. The router is
connected to a LAN through a switch. The LAN is a single subnet with no OSPF routers
inside it. The network for this example uses the same loop as for
with a router attached to switch 2. The network is shown in the following figure.
We used an AR410 router, but the router configuration works on any AR400 or AR700
series router.
Each example in this section modifies the following base configuration.
Page 86 | AlliedWare™ OS How To Note: IGMP
Multicast Server
port 26
Rapier 24i
Switch 2:
Snooper
port 24
port 2
Client 1
Router
Stopping snoopers from snooping non-IGMP messages > Example
port 1
AT-8948
Switch 1:
Querier
port 50
port 49
(blocked by STP)
OSPF
port 25
"IGMP snooping" on page
port 26
Rapier 24i
Switch 3:
port 25
Snooper
port 3
Client 2
igmp-all-groups.eps
9,

Advertisement

Table of Contents
loading

Table of Contents

Save Article as PDF