<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2014-01-02 13:58,
<a class="moz-txt-link-abbreviated" href="mailto:tfauriant@mousquetaires.com">tfauriant@mousquetaires.com</a> wrote:<br>
</div>
<blockquote
cite="mid:OFC11399C7.CCA436E5-ONC1257C54.0046CE01-C1257C54.00473B7A@mousquetaires.com"
type="cite"><font face="sans-serif" size="2">Marcin,</font>
<br>
<br>
<font face="sans-serif" size="2">it's correct. by default, without
igmp
snooping, the multicast flows are broadcasted on a L2 switch.</font>
<br>
</blockquote>
<br>
Comming back to the subject.<br>
You are right, it is quite obvious but it took me a moment to get it
understood.<br>
<br>
<blockquote
cite="mid:OFC11399C7.CCA436E5-ONC1257C54.0046CE01-C1257C54.00473B7A@mousquetaires.com"
type="cite">
<br>
<font face="sans-serif" size="2">Did you have put the multicast
flow
(in entry) on a protected VLAN of EAPS ring ? </font>
<br>
</blockquote>
<br>
There is no manual configuration.<br>
What will happen if I do it ?<br>
Is it going to do a proper switchover if particular flow is "routed"
manually on protected vlan ?<br>
<br>
Regards,<br>
Marcin<br>
<br>
<br>
<blockquote
cite="mid:OFC11399C7.CCA436E5-ONC1257C54.0046CE01-C1257C54.00473B7A@mousquetaires.com"
type="cite">
<br>
<font face="sans-serif" size="2">Regards,</font>
<br>
<br>
<br>
<font face="sans-serif" size="2">Tristan Fauriant<br>
</font>
<br>
<br>
<br>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">De :
</font><font face="sans-serif" size="1">Marcin Kuczera
<a class="moz-txt-link-rfc2396E" href="mailto:marcin@leon.pl"><marcin@leon.pl></a></font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">A :
</font><font face="sans-serif" size="1"><a class="moz-txt-link-rfc2396E" href="mailto:extreme-nsp@puck.nether.net">"extreme-nsp@puck.nether.net"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:extreme-nsp@puck.nether.net"><extreme-nsp@puck.nether.net></a></font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">Date :
</font><font face="sans-serif" size="1">30/12/2013 14:47</font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">Objet :
</font><font face="sans-serif" size="1">[e-nsp] VLAN
without IGMP snooping and multicasts</font>
<br>
<font color="#5f5f5f" face="sans-serif" size="1">Envoyé par :
</font><font face="sans-serif" size="1">"extreme-nsp"
<a class="moz-txt-link-rfc2396E" href="mailto:extreme-nsp-bounces@puck.nether.net"><extreme-nsp-bounces@puck.nether.net></a></font>
<br>
<hr noshade="noshade">
<br>
<br>
<br>
<tt><font size="2">hello,<br>
<br>
we have a customer who has some strange devices transmitting
"fixed"
<br>
multicast stream without using IGMP requests in a regular way.<br>
So we had to turn off IGMP snooping on that vlan, otherwise
transmission
<br>
was extinguished after IGMP timers expire.<br>
I'am not arguing with these devices, they transmit DVB-T MUX
signal in
<br>
their own, properitary way.<br>
<br>
However, because it passes EAPS ring, I have noticed that this
stream is
<br>
also broadcasted to backup port of EAPS ring.<br>
<br>
So my question is - is it correct that multicasts when IGMP
snooping is
<br>
off are broadcasted instead of using regular FDB ?<br>
<br>
Switches: Summit-X650-24x<br>
Soft: ExtremeXOS version 15.3 series<br>
<br>
Regards,<br>
Marcin<br>
<br>
_______________________________________________<br>
extreme-nsp mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:extreme-nsp@puck.nether.net">extreme-nsp@puck.nether.net</a><br>
</font></tt><a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/extreme-nsp"><tt><font
size="2">https://puck.nether.net/mailman/listinfo/extreme-nsp</font></tt></a><tt><font
size="2"><br>
</font></tt>
<br>
<p>----------------------------- Disclaimer
------------------------------<br>
--- Ce message ainsi que les éventuelles pièces jointes
constituent une<br>
correspondance privée et confidentielle à l'attention exclusive
du<br>
destinataire désigné ci-dessus. Si vous n'êtes pas le
destinataire du<br>
présent message ou une personne susceptible de pouvoir le lui
délivrer,<br>
il vous est signifié que toute divulgation, distribution ou
copie,<br>
totale ou partielle, sur un quelconque support de cette
transmission<br>
est strictement interdite. Si vous avez recu ce message par
erreur,<br>
nous vous remercions d'en informer l'expéditeur par téléphone ou
de lui<br>
retourner le présent message, puis d'effacer immédiatement ce
message<br>
de votre systeme. Tout message électronique est susceptible<br>
d'altération. Le "groupement des Mousquetaires" décline toute<br>
responsabilité au titre de ce message s'il a été altéré, déformé
ou<br>
falsifié.---<br>
--- This e-mail and any attachments is a confidential
correspondence<br>
intended only for use of the individual or entity named above.
If you<br>
are not the intended recipient or the agent responsible for
delivering<br>
the message to the intended recipient, you are hereby notified
that any<br>
disclosure, distribution or copying, either whole or partial, in
any<br>
medium of this communication is strictly prohibited. If you have<br>
received this communication by mistake, please notify the sender
by<br>
phone or by replying this message, and then delete this message
from<br>
your system. E-mails are susceptible of alteration. The<br>
"Mousquetaires' group" shall not therefore be liable for the
message<br>
if altered, changed or falsified.---<br>
-----------------------------------------------------------------------</p>
<p> </p>
</blockquote>
<br>
</body>
</html>