<?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: Round-Robin Trunking in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53090#M14847</link>
    <description>Mrxlazuardin I would hope that your network doesn't have a lot of out of sequence packets.  Yes they do happen but it is better to send a whole flow over the same link to min any disruption.  In a situation where you have one hop maybe there is less concern but across a network that is fro Edge to aggregation to core  having a lot of that traffic could be a big issue.&lt;BR /&gt;
&lt;BR /&gt;
Because our products can go from Enterprise to SP, from k-12 to high end DC or internet exchanges we need to have confidence that the network will work in all environments.&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
P&lt;BR /&gt;</description>
    <pubDate>Thu, 16 Apr 2015 23:34:00 GMT</pubDate>
    <dc:creator>Paul_Russo</dc:creator>
    <dc:date>2015-04-16T23:34:00Z</dc:date>
    <item>
      <title>Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53083#M14840</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Is there anyway to configure round-robin algorithm on trunking (ports grouping)? I can do that easily on Linux, but I don't have idea on EXOS. With that algorithm, the load of each member of ports group will be balanced, no matter of the source and destination.&lt;BR /&gt;
&lt;BR /&gt;
Basically it will works if the each member doing Tx in round-robin manner and all members doing Rx.&lt;BR /&gt;
&lt;BR /&gt;
Best regards,</description>
      <pubDate>Thu, 16 Apr 2015 17:07:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53083#M14840</guid>
      <dc:creator>Mrxlazuardin</dc:creator>
      <dc:date>2015-04-16T17:07:00Z</dc:date>
    </item>
    <item>
      <title>RE: Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53084#M14841</link>
      <description>Maybe lacp can take care of it:&lt;BR /&gt;
e.g.&lt;BR /&gt;
ena sharing 1 grouping 1-2 lacp</description>
      <pubDate>Thu, 16 Apr 2015 17:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53084#M14841</guid>
      <dc:creator>jackmikel</dc:creator>
      <dc:date>2015-04-16T17:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53085#M14842</link>
      <description>Hi Jack,&lt;BR /&gt;
&lt;BR /&gt;
Based on my experience, LACP is not so "balanced" on port grouping of connection to server or any end node. It is because of the destination is same.&lt;BR /&gt;
&lt;BR /&gt;
Best regards,</description>
      <pubDate>Thu, 16 Apr 2015 17:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53085#M14842</guid>
      <dc:creator>Mrxlazuardin</dc:creator>
      <dc:date>2015-04-16T17:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53086#M14843</link>
      <description>Hello Mrxlazuardin&lt;BR /&gt;
&lt;BR /&gt;
We do not support round robin on LAG ports as it can lead to packet out of sequence errors. &lt;BR /&gt;
&lt;BR /&gt;
Hope that helps&lt;BR /&gt;
&lt;BR /&gt;
P&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Apr 2015 18:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53086#M14843</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2015-04-16T18:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53087#M14844</link>
      <description>Hi Paul,&lt;BR /&gt;
&lt;BR /&gt;
Don't you think that unsequenced packet is common in TCP/IP networking and TCP/IP has capability to deal with that?&lt;BR /&gt;
&lt;BR /&gt;
Best regards,</description>
      <pubDate>Thu, 16 Apr 2015 18:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53087#M14844</guid>
      <dc:creator>Mrxlazuardin</dc:creator>
      <dc:date>2015-04-16T18:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53088#M14845</link>
      <description>Mrxlazuardin,&lt;BR /&gt;
&lt;BR /&gt;
TCP does indeed have the capability to deal with out of order packets. But to reorder them requires storing misordered packets in buffers which requires memory and increases latency.&lt;BR /&gt;
&lt;BR /&gt;
In a slow link, a few misordered packets don't hurt. In a LAG of high speed links the number can be high and so will be the amount of buffer memory and the processing time needed to reorder them.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Apr 2015 18:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53088#M14845</guid>
      <dc:creator>dflouret</dc:creator>
      <dc:date>2015-04-16T18:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53089#M14846</link>
      <description>No. EXOS supports only port-based or address-based algorithms:&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Apr 2015 21:07:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53089#M14846</guid>
      <dc:creator>dflouret</dc:creator>
      <dc:date>2015-04-16T21:07:00Z</dc:date>
    </item>
    <item>
      <title>RE: Round-Robin Trunking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53090#M14847</link>
      <description>Mrxlazuardin I would hope that your network doesn't have a lot of out of sequence packets.  Yes they do happen but it is better to send a whole flow over the same link to min any disruption.  In a situation where you have one hop maybe there is less concern but across a network that is fro Edge to aggregation to core  having a lot of that traffic could be a big issue.&lt;BR /&gt;
&lt;BR /&gt;
Because our products can go from Enterprise to SP, from k-12 to high end DC or internet exchanges we need to have confidence that the network will work in all environments.&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
P&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Apr 2015 23:34:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/round-robin-trunking/m-p/53090#M14847</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2015-04-16T23:34:00Z</dc:date>
    </item>
  </channel>
</rss>

