<?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: LACP on Nimble Array ports? in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/lacp-on-nimble-array-ports/m-p/6984583#M1352</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Prasad!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typically customers use MPIO (multi-path IO) for load balancing, instead of LACP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To put it in short form, the three devices in a storage conversation are the host, switch and array.&amp;nbsp; The two that know the most about the conversation are the host and array.&amp;nbsp; The LACP protocol is not optimized for storage traffic, whereas MPIO is built specifically for storage.&lt;/P&gt;&lt;P&gt;Using our Nimble Connect Manager makes setting up MPIO a very easy and quick process. Give it a try!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check out this great doc by Wen Yu for more detail!&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hpe.com/docs/DOC-1242"&gt;TO LACP or NOT to LACP for VM and iSCSI traffic&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jun 2014 18:33:17 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-06-19T18:33:17Z</dc:date>
    <item>
      <title>LACP on Nimble Array ports?</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/lacp-on-nimble-array-ports/m-p/6984582#M1351</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does it makes sense to have LACP on storage ports? If not, why? &lt;/P&gt;&lt;P&gt;I know the advantages of LACP on the host side, but wondering what value it brings if it is enabled/supported on storage ports?&lt;/P&gt;&lt;P&gt;Not sure if Nimble supports LACP on their ports. Which other storage vendor supports LACP on their ports?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 17:57:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/lacp-on-nimble-array-ports/m-p/6984582#M1351</guid>
      <dc:creator>pshinde96</dc:creator>
      <dc:date>2014-06-19T17:57:10Z</dc:date>
    </item>
    <item>
      <title>Re: LACP on Nimble Array ports?</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/lacp-on-nimble-array-ports/m-p/6984583#M1352</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Prasad!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typically customers use MPIO (multi-path IO) for load balancing, instead of LACP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To put it in short form, the three devices in a storage conversation are the host, switch and array.&amp;nbsp; The two that know the most about the conversation are the host and array.&amp;nbsp; The LACP protocol is not optimized for storage traffic, whereas MPIO is built specifically for storage.&lt;/P&gt;&lt;P&gt;Using our Nimble Connect Manager makes setting up MPIO a very easy and quick process. Give it a try!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check out this great doc by Wen Yu for more detail!&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hpe.com/docs/DOC-1242"&gt;TO LACP or NOT to LACP for VM and iSCSI traffic&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 18:33:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/lacp-on-nimble-array-ports/m-p/6984583#M1352</guid>
      <dc:creator />
      <dc:date>2014-06-19T18:33:17Z</dc:date>
    </item>
  </channel>
</rss>

