<?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: The algorithm of ECMP in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/the-algorithm-of-ecmp/m-p/51883#M14250</link>
    <description>Hello Elmer&lt;BR /&gt;
&lt;BR /&gt;
There is a detail description of this in the EXOS Command Reference guide 15_4 page 2336.&lt;BR /&gt;
&lt;BR /&gt;
Here's a brief summary&lt;BR /&gt;
&lt;BR /&gt;
The ECMP hash uses CRC based on SIP, DIP and (by default), the L4 port numbers. If you&lt;BR /&gt;
want, you can choose to exclude L4 port numbers by configuring "L3" using this XOS CLI&lt;BR /&gt;
command:&lt;BR /&gt;
configure forwarding sharing [L3 | L3_L4]&lt;BR /&gt;
&lt;BR /&gt;
ECMP support L3&lt;BR /&gt;
Uses only Layer 3 IP addresses to select ECMP routes and load-sharing ports.&lt;BR /&gt;
L3_L4 (Default)&lt;BR /&gt;
Uses Layer 3 IP addresses and Layer 4 TCP/UDP port numbers, if present, to select&lt;BR /&gt;
ECMP routes and load-sharing ports&lt;BR /&gt;
&lt;BR /&gt;
You can download the command reference guide at &lt;A href="http://www.extremenetworks.com/support/extreme-support/documentation/" target="_blank" rel="nofollow noreferrer noopener"&gt;http://www.extremenetworks.com/support/extreme-support/documentation/&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps&lt;BR /&gt;
P&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Thu, 10 Apr 2014 18:14:00 GMT</pubDate>
    <dc:creator>Paul_Russo</dc:creator>
    <dc:date>2014-04-10T18:14:00Z</dc:date>
    <item>
      <title>The algorithm of ECMP</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/the-algorithm-of-ecmp/m-p/51882#M14249</link>
      <description>What  is the algorithm of ECMP on XOS. Is it platform independent?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Apr 2014 09:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/the-algorithm-of-ecmp/m-p/51882#M14249</guid>
      <dc:creator>r_____________9</dc:creator>
      <dc:date>2014-04-10T09:15:00Z</dc:date>
    </item>
    <item>
      <title>RE: The algorithm of ECMP</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/the-algorithm-of-ecmp/m-p/51883#M14250</link>
      <description>Hello Elmer&lt;BR /&gt;
&lt;BR /&gt;
There is a detail description of this in the EXOS Command Reference guide 15_4 page 2336.&lt;BR /&gt;
&lt;BR /&gt;
Here's a brief summary&lt;BR /&gt;
&lt;BR /&gt;
The ECMP hash uses CRC based on SIP, DIP and (by default), the L4 port numbers. If you&lt;BR /&gt;
want, you can choose to exclude L4 port numbers by configuring "L3" using this XOS CLI&lt;BR /&gt;
command:&lt;BR /&gt;
configure forwarding sharing [L3 | L3_L4]&lt;BR /&gt;
&lt;BR /&gt;
ECMP support L3&lt;BR /&gt;
Uses only Layer 3 IP addresses to select ECMP routes and load-sharing ports.&lt;BR /&gt;
L3_L4 (Default)&lt;BR /&gt;
Uses Layer 3 IP addresses and Layer 4 TCP/UDP port numbers, if present, to select&lt;BR /&gt;
ECMP routes and load-sharing ports&lt;BR /&gt;
&lt;BR /&gt;
You can download the command reference guide at &lt;A href="http://www.extremenetworks.com/support/extreme-support/documentation/" target="_blank" rel="nofollow noreferrer noopener"&gt;http://www.extremenetworks.com/support/extreme-support/documentation/&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps&lt;BR /&gt;
P&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Apr 2014 18:14:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/the-algorithm-of-ecmp/m-p/51883#M14250</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2014-04-10T18:14:00Z</dc:date>
    </item>
  </channel>
</rss>

