<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Multicast address ranges with virtual connect in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5671775#M31420</link>
    <description>&lt;P&gt;We have built several Red Hat clusters on BL465 g7 blades, using the RHEL5 Cluster Suite software. The basic premise of thie cluster software is that the nodes contact each other using a private multicast&amp;nbsp; IP of 239.192.x.x. We have several blades on the cisco catalyst blade switch (not virtual connect) where this works fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But on VC Flex-10 modules, these ranges cannot be used, and the nodes never see each. If I change the multicast IP to 239.0.0.1, then the nodes can see each other again. This happens with or without IGMP snooping enabled in VC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My suspicion is that virtual connect does not forward multicast packets for the 239.192.x.x multicast range. Can anyone comfirm if this is true or not, and why would it be the case if so ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 28 May 2012 13:58:23 GMT</pubDate>
    <dc:creator>Michael Pye</dc:creator>
    <dc:date>2012-05-28T13:58:23Z</dc:date>
    <item>
      <title>Multicast address ranges with virtual connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5671775#M31420</link>
      <description>&lt;P&gt;We have built several Red Hat clusters on BL465 g7 blades, using the RHEL5 Cluster Suite software. The basic premise of thie cluster software is that the nodes contact each other using a private multicast&amp;nbsp; IP of 239.192.x.x. We have several blades on the cisco catalyst blade switch (not virtual connect) where this works fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But on VC Flex-10 modules, these ranges cannot be used, and the nodes never see each. If I change the multicast IP to 239.0.0.1, then the nodes can see each other again. This happens with or without IGMP snooping enabled in VC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My suspicion is that virtual connect does not forward multicast packets for the 239.192.x.x multicast range. Can anyone comfirm if this is true or not, and why would it be the case if so ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 28 May 2012 13:58:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5671775#M31420</guid>
      <dc:creator>Michael Pye</dc:creator>
      <dc:date>2012-05-28T13:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast address ranges with virtual connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5673849#M31421</link>
      <description>&lt;P&gt;what's VC version? for earlier release with igmp snooping on, there were some issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&amp;amp;objectID=c02535509"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&amp;amp;objectID=c02535509&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know you mentioned that you see the problem with or without IGMP snooping.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the address should work fine. I suggest you open an HP support case for further troubleshooting.&lt;/P&gt;</description>
      <pubDate>Wed, 30 May 2012 06:12:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5673849#M31421</guid>
      <dc:creator>Hongjun Ma</dc:creator>
      <dc:date>2012-05-30T06:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast address ranges with virtual connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5674727#M31422</link>
      <description>&lt;P&gt;Interesting advisory there, thanks for the response. I have one two-node cluster that both nodes use VC version is 3.30 , and another two-node cluster with 3.51 one node and 3.18 the other node. They all exhitbit this problem. Does sound like maybe a case for HP. There must be other vc users running red hat clusters that have this problem?&lt;/P&gt;</description>
      <pubDate>Wed, 30 May 2012 21:31:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5674727#M31422</guid>
      <dc:creator>Michael Pye</dc:creator>
      <dc:date>2012-05-30T21:31:20Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast address ranges with virtual connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5674729#M31423</link>
      <description>&lt;P&gt;if you want to dig in further, try enable igmp snooping and do the following command for enc0:1 or end0:2(VC-1 or VC2). also, you can set up port monitoring on VC to sniff the traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-&amp;gt;show igmp-group enc0:1&lt;/P&gt;&lt;P&gt;===========================================&lt;/P&gt;&lt;P&gt;Port&amp;nbsp; Group IP Address&amp;nbsp; MAC Address&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;===========================================&lt;/P&gt;&lt;P&gt;d6:c&amp;nbsp; 224.224.224.224&amp;nbsp;&amp;nbsp; 01:00:5e:60:e0:e0&amp;nbsp;&lt;/P&gt;&lt;P&gt;d8:c&amp;nbsp; 224.224.224.224&amp;nbsp;&amp;nbsp; 01:00:5e:60:e0:e0&amp;nbsp;&lt;/P&gt;&lt;P&gt;d9:c&amp;nbsp; 224.224.224.224&amp;nbsp;&amp;nbsp; 01:00:5e:60:e0:e0&amp;nbsp;&lt;/P&gt;&lt;P&gt;d1:c&amp;nbsp; 239.193.0.107&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 01:00:5e:41:00:6b&amp;nbsp;&lt;/P&gt;&lt;P&gt;d1:c&amp;nbsp; 239.192.0.107&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 01:00:5e:40:00:6b&amp;nbsp;&lt;/P&gt;&lt;P&gt;d1:a&amp;nbsp; 239.255.255.253&amp;nbsp;&amp;nbsp; 01:00:5e:7f:ff:fd&amp;nbsp;&lt;/P&gt;&lt;P&gt;d2:a&amp;nbsp; 239.255.255.253&amp;nbsp;&amp;nbsp; 01:00:5e:7f:ff:fd&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 May 2012 21:34:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/multicast-address-ranges-with-virtual-connect/m-p/5674729#M31423</guid>
      <dc:creator>Hongjun Ma</dc:creator>
      <dc:date>2012-05-30T21:34:37Z</dc:date>
    </item>
  </channel>
</rss>

