<?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 Virtual Connect + VMware?! in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-vmware/m-p/4441876#M6413</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Still tinkering with my C7000&lt;BR /&gt;&lt;BR /&gt;(2 x VC-FC modules, and 2 x VC-1/10GB Ethernet modules)...&lt;BR /&gt;&lt;BR /&gt;Basically trying now to work out the network side of things..&lt;BR /&gt;&lt;BR /&gt;I have heard people mention that route based on IP hash is not possible with VC, is this true, if so why??&lt;BR /&gt;&lt;BR /&gt;I am looking to basically have 6 NIC's per blade and perform the best aggregation/redundancy I can. I have read the Cookbook guide but it does not really help me understand the limitations regarding VC and IP hash?&lt;BR /&gt;&lt;BR /&gt;I can sort of see the issues as it looks like a lot of the VMware stuff is duplicated in the VC (Shared Uplink and Teaming etc)...&lt;BR /&gt;&lt;BR /&gt;Any tips?</description>
    <pubDate>Wed, 17 Jun 2009 18:16:56 GMT</pubDate>
    <dc:creator>UselessUser</dc:creator>
    <dc:date>2009-06-17T18:16:56Z</dc:date>
    <item>
      <title>Virtual Connect + VMware?!</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-vmware/m-p/4441876#M6413</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Still tinkering with my C7000&lt;BR /&gt;&lt;BR /&gt;(2 x VC-FC modules, and 2 x VC-1/10GB Ethernet modules)...&lt;BR /&gt;&lt;BR /&gt;Basically trying now to work out the network side of things..&lt;BR /&gt;&lt;BR /&gt;I have heard people mention that route based on IP hash is not possible with VC, is this true, if so why??&lt;BR /&gt;&lt;BR /&gt;I am looking to basically have 6 NIC's per blade and perform the best aggregation/redundancy I can. I have read the Cookbook guide but it does not really help me understand the limitations regarding VC and IP hash?&lt;BR /&gt;&lt;BR /&gt;I can sort of see the issues as it looks like a lot of the VMware stuff is duplicated in the VC (Shared Uplink and Teaming etc)...&lt;BR /&gt;&lt;BR /&gt;Any tips?</description>
      <pubDate>Wed, 17 Jun 2009 18:16:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-vmware/m-p/4441876#M6413</guid>
      <dc:creator>UselessUser</dc:creator>
      <dc:date>2009-06-17T18:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect + VMware?!</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-vmware/m-p/4441877#M6414</link>
      <description>You can only have two NICs with two VC-1/10GB. Are you looking at purchasing four more VC 1/10GB modules?&lt;BR /&gt;&lt;BR /&gt;And i think you find the answer to the hash question here.&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1245312143266+28353475&amp;amp;threadId=1201089" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1245312143266+28353475&amp;amp;threadId=1201089&lt;/A&gt;</description>
      <pubDate>Thu, 18 Jun 2009 07:03:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-vmware/m-p/4441877#M6414</guid>
      <dc:creator>Adrian Clint</dc:creator>
      <dc:date>2009-06-18T07:03:26Z</dc:date>
    </item>
  </channel>
</rss>

