Static Igmp; Example - Allied Telesis AR400 Series How To Configure

Static IGMP

Static IGMP enables you to configure a switch with specified group-to-interface or group-to-
port mappings, which you may want to do if:
your network includes hosts that cannot send IGMP Membership Reports
you need to guarantee that a specific multicast stream is instantly available on a port,
without any delay from the joining process
A common usage of Static IGMP is for protocols like Service Location Protocol (SLP). This
protocol sends out multicast packets that need to be forwarded to designated ports. You may
want SLP packets to be forwarded to ports that have servers who need to respond to these
packets. Static IGMP allows you to specify that traffic for this group should go to hosts who
will respond to, or are interested in, these messages. For detailed information about using
Static IGMP and SLP, see How to configure IGMP snooping with unregistered multicast addresses
such as Service Location Protocol (SLP) in the
Static IGMP is available on all the Allied Telesis managed layer 3 switches listed on

Example

In this example, we will start by setting an IGMP static entry for the group 224.12.13.14 to go
to port 5 on switch 1 (part of vlan100). On that port we have attached a host which has no
multicast client software running. After examining the effect of static IGMP on switch 1, we
will add a static IGMP entry to switch 3 and consider the effect this has on multicasting
through the network.
The network for this example has three switches in a loop and is shown in the following
figure.
Page 48 | AlliedWare™ OS How To Note: IGMP
Multicast Server
port 1
port 26
Rapier 24i
Switch 2:
Snooper
Allied Telesis website's Technical
Static client
port 5
AT-8948
port 50 port 49
(blocked by STP)
port 25
Static IGMP > Example
Library.
Switch 1:
Querier
port 26
Rapier 24i
Switch 3
port 25
port 5
Static client
(added later in example)
page 3.
igmp-static.eps