<?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 and VMware vSwitch question in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-vmware-vswitch-question/m-p/5568419#M32160</link>
    <description>&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Mike had a customer question:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the following from one of my customers.&amp;nbsp; He’s using BL460/BL490 G6’s with VC Flex-10.&amp;nbsp; Not sure of the current FW version.&amp;nbsp; Any thoughts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question:&amp;nbsp; When using the Virtual Connect is there a specific type of Load Balancing required on the VMware virtual switches?&amp;nbsp; We are running ESX 4.1 with vmxnet3 drivers and standard virtual switches connecting through the HP Bladeframe to a physical Nexus 5k switch.&amp;nbsp; I listed the 4 options below.&amp;nbsp; We are currently running “Route based on the originating virtual port ID” which is not failing over properly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;1.&amp;nbsp; Route based on the originating virtual port ID&amp;nbsp; 2.&amp;nbsp; Route based on IP hash&amp;nbsp; 3.&amp;nbsp; Route based on source MAC hash&amp;nbsp; 4.&amp;nbsp; Use explicit failover order.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*******************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;From Dan:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Those are load balancing choices and don't necessarily have anything to do with failover.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If they are configured for Active Active uplinks, make site they have Smart Link turned on for all networks that exit the chassis.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Virtual Connect does not support "Route based &amp;nbsp;IP hash" load balancing, so your "route based on the originating virtual port ID" setting should be fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*****************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Other comments or questions?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 29 Feb 2012 16:33:37 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2012-02-29T16:33:37Z</dc:date>
    <item>
      <title>Virtual Connect and VMware vSwitch question</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-vmware-vswitch-question/m-p/5568419#M32160</link>
      <description>&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Mike had a customer question:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the following from one of my customers.&amp;nbsp; He’s using BL460/BL490 G6’s with VC Flex-10.&amp;nbsp; Not sure of the current FW version.&amp;nbsp; Any thoughts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question:&amp;nbsp; When using the Virtual Connect is there a specific type of Load Balancing required on the VMware virtual switches?&amp;nbsp; We are running ESX 4.1 with vmxnet3 drivers and standard virtual switches connecting through the HP Bladeframe to a physical Nexus 5k switch.&amp;nbsp; I listed the 4 options below.&amp;nbsp; We are currently running “Route based on the originating virtual port ID” which is not failing over properly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;1.&amp;nbsp; Route based on the originating virtual port ID&amp;nbsp; 2.&amp;nbsp; Route based on IP hash&amp;nbsp; 3.&amp;nbsp; Route based on source MAC hash&amp;nbsp; 4.&amp;nbsp; Use explicit failover order.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*******************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;From Dan:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Those are load balancing choices and don't necessarily have anything to do with failover.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If they are configured for Active Active uplinks, make site they have Smart Link turned on for all networks that exit the chassis.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Virtual Connect does not support "Route based &amp;nbsp;IP hash" load balancing, so your "route based on the originating virtual port ID" setting should be fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*****************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Other comments or questions?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Feb 2012 16:33:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-vmware-vswitch-question/m-p/5568419#M32160</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2012-02-29T16:33:37Z</dc:date>
    </item>
  </channel>
</rss>

