<?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 Re: Virtual connect and NIC teaming/bonding in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709418#M11879</link>
    <description>What is the Linux bonding mode corresponding to transmit based load balancing? Mode 5?&lt;BR /&gt;&lt;BR /&gt;Is there any possible catch using this instead of network fault tolerance (active-backup)?</description>
    <pubDate>Fri, 05 Nov 2010 02:28:06 GMT</pubDate>
    <dc:creator>Ugo Bellavance (ATQ)</dc:creator>
    <dc:date>2010-11-05T02:28:06Z</dc:date>
    <item>
      <title>Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709413#M11874</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have a C-7000 with two Virtual Connect Flex-10.  I was wondering what were the best practices for the configuration to have a network redundancy for the blades.&lt;BR /&gt;&lt;BR /&gt;We have 2 shared uplink sets defined.  One uses Virtual Connect #1, the other Virtual Connect #2.  Then, we configured the nic using LACP, but we don't see traffic on both LOM.  I think that the most appropriate NIC config in this case would be a simple failover (Network fault tolerance in Windows, active-backup in Linux).  Does LACP-configured NICs work like a simple failover if it is not connected to LACP-configured ports?&lt;BR /&gt;&lt;BR /&gt;Are we in the right way?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Ugo</description>
      <pubDate>Thu, 04 Nov 2010 14:14:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709413#M11874</guid>
      <dc:creator>Ugo Bellavance (ATQ)</dc:creator>
      <dc:date>2010-11-04T14:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709414#M11875</link>
      <description>Where did You configure LACP ?&lt;BR /&gt;What OS ?&lt;BR /&gt;&lt;BR /&gt;You configured the same networks to SUS_A and SUS_B (best practice)?&lt;BR /&gt;&lt;BR /&gt;I would use transmit load balancing with fault tolerance in OS team/bond to get benefit from both active uplinks. &lt;BR /&gt;&lt;BR /&gt;LACP is different thing.</description>
      <pubDate>Thu, 04 Nov 2010 15:06:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709414#M11875</guid>
      <dc:creator>JKytsi</dc:creator>
      <dc:date>2010-11-04T15:06:20Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709415#M11876</link>
      <description>We configured LACP on the NICs (linux). eth0 and eth1.&lt;BR /&gt;&lt;BR /&gt;OS: RHEL 5.5&lt;BR /&gt;&lt;BR /&gt;You mean mode 5 for the bond on linux?</description>
      <pubDate>Thu, 04 Nov 2010 15:37:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709415#M11876</guid>
      <dc:creator>Ugo Bellavance (ATQ)</dc:creator>
      <dc:date>2010-11-04T15:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709416#M11877</link>
      <description>Could we configure LACP on the VCs and do a distributed link aggregation on our H3C 5800 switches?</description>
      <pubDate>Thu, 04 Nov 2010 15:38:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709416#M11877</guid>
      <dc:creator>Ugo Bellavance (ATQ)</dc:creator>
      <dc:date>2010-11-04T15:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709417#M11878</link>
      <description>You can't create a LACP trunk across separate Flex10 modules. You will have to use either Transmit based load balancing or Network Fault Tolerance mode.&lt;BR /&gt;&lt;BR /&gt;This also applies when going from the Flex10 to external switches. Multiple links from an individual Flex10 can establish an LACP trunk (you do this by setting LACP active ports on the external switch side) however if you define an Uplink Set that spans Flex-10 modules the connection on one Flex10 module will appear as Active and the ones on the other module will appear as Passive.</description>
      <pubDate>Thu, 04 Nov 2010 22:43:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709417#M11878</guid>
      <dc:creator>Mark Wibaux</dc:creator>
      <dc:date>2010-11-04T22:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709418#M11879</link>
      <description>What is the Linux bonding mode corresponding to transmit based load balancing? Mode 5?&lt;BR /&gt;&lt;BR /&gt;Is there any possible catch using this instead of network fault tolerance (active-backup)?</description>
      <pubDate>Fri, 05 Nov 2010 02:28:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709418#M11879</guid>
      <dc:creator>Ugo Bellavance (ATQ)</dc:creator>
      <dc:date>2010-11-05T02:28:06Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709419#M11880</link>
      <description>I've put it in active-backup (network fault tolerance), and during the VC firmware update, I have had a loss of connectivity of a few seconds.  Is that normal?  I lost my ssh session.</description>
      <pubDate>Fri, 05 Nov 2010 04:41:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709419#M11880</guid>
      <dc:creator>Ugo Bellavance (ATQ)</dc:creator>
      <dc:date>2010-11-05T04:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect and NIC teaming/bonding</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709420#M11881</link>
      <description>I closed the thread in error, please see my other postes.</description>
      <pubDate>Wed, 10 Nov 2010 12:50:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-and-nic-teaming-bonding/m-p/4709420#M11881</guid>
      <dc:creator>Ugo Bellavance (ATQ)</dc:creator>
      <dc:date>2010-11-10T12:50:23Z</dc:date>
    </item>
  </channel>
</rss>

