Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • you're correct regarding netstat -g . We are using hazelcast for this. I just realized that nodes without hazelcast, that don't even need to be listening to those multicasts, according to tcpdump are still getting it - even when not part of the group - which is fine. But it doesn't explain why one node doesn't seem to be receiving them properly. Commented Jul 7, 2012 at 15:38
  • The continuing reception of mcast packets means one of two things: 1. You once ran hazelcast on that node, the switch saw the IGMP group join, didn't see a group drop, and so is still sending packets...some switches have a "fast leave" feature to fix this, but it can cause more problems than it solves; or 2. the hosting provider hasn't enabled IGMP snooping, in which case you have some problem with the node itself. Try the tcpdump test, looking for the IGMP group add request. Commented Jul 7, 2012 at 15:48