A better understanding of multicast issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

  It seems to me that a very good number of clustering problems end up
being multicast and smart switch related. I know that IGMP snooping and
STP are often the cause, and PIM can help solve it. Despite
understanding this, though, I can't quite understand exactly *why* IGMP
snooping and STP break things.

  Reading up on them leads me to think that they should cleanly create
and handle multicast groups, but this obviously isn't the case. When a
switch restarts, shouldn't it send a request to clients asking to
resubscribe to multicast groups? When corosync starts, I expect it would
also send multicast joins.

  Sorry if the question is a little vague or odd. I'm trying to get my
head around the troubles when, on the surface, the docs seem to make the
process of creating/managing multicast quite simple and straight forward.

Thanks!

-- 
Digimer
E-Mail: digimer@xxxxxxxxxxx
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster


[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux