<?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: How does 100G work with 4x25G lanes in ExtremeSwitching (Other)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-other/how-does-100g-work-with-4x25g-lanes/m-p/96359#M4077</link>
    <description>&lt;P&gt;When you split by 4x25G you have four ports at 25G rate. If those 4 ports service 4 interfaces on the same host/server and you use lacp to aggregate them, one session will use only one port.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Jul 2023 09:30:58 GMT</pubDate>
    <dc:creator>AdrianO</dc:creator>
    <dc:date>2023-07-10T09:30:58Z</dc:date>
    <item>
      <title>How does 100G work with 4x25G lanes</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/how-does-100g-work-with-4x25g-lanes/m-p/96351#M4076</link>
      <description>&lt;P&gt;Hello &lt;SPAN&gt;Community&lt;/SPAN&gt;,&lt;/P&gt;&lt;P&gt;We are currently dealing with 100Gbit/s connections. I have heard that for 100G with 4x25G lanes a session can only be 25G in size, so one session can only use one of the four lanes. On the other hand I also read that the traffic is split into 64 bit portions and then distributed over the lanes parallel.&amp;nbsp;Does anyone know a good source where i can find more about this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&lt;BR /&gt;Jan&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 11:33:36 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/how-does-100g-work-with-4x25g-lanes/m-p/96351#M4076</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-07-07T11:33:36Z</dc:date>
    </item>
    <item>
      <title>Re: How does 100G work with 4x25G lanes</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/how-does-100g-work-with-4x25g-lanes/m-p/96359#M4077</link>
      <description>&lt;P&gt;When you split by 4x25G you have four ports at 25G rate. If those 4 ports service 4 interfaces on the same host/server and you use lacp to aggregate them, one session will use only one port.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jul 2023 09:30:58 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/how-does-100g-work-with-4x25g-lanes/m-p/96359#M4077</guid>
      <dc:creator>AdrianO</dc:creator>
      <dc:date>2023-07-10T09:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: How does 100G work with 4x25G lanes</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/how-does-100g-work-with-4x25g-lanes/m-p/96401#M4078</link>
      <description>&lt;P&gt;Just like 40 G links, 100 G links use four lanes. This enables us to break out separate 25 G (or 10 G in the 40 G case) connections. This is NOT to be confused with how a 100 G link works when split into four 25 G links. In 1 x 100 G mode, it certainly behaves as a single 100 G link, enabling you to have one single TCP, UDP or whatever session to occupy the entire 100 G link if you need. If you were to split the 100 G interface into 4 x 25 G and create a LAG of those, then every flow or session would use one of those LAG members, limiting it to 25 G.&lt;/P&gt;&lt;P&gt;An interface in 1 x 100 G mode will behave just like that, one single 100 G link. When it comes to the split in 64 bit portions, you're probably referring to the 64b/66b encoding used by 10 and 100 G Ethernet (1 G uses 8b/10b), but that is totally transparent to the user, so nothing you will ever notice.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 17:27:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/how-does-100g-work-with-4x25g-lanes/m-p/96401#M4078</guid>
      <dc:creator>FredrikB-NN2</dc:creator>
      <dc:date>2023-07-11T17:27:39Z</dc:date>
    </item>
  </channel>
</rss>

