<?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: TRAFFIC ONLY GOING THROUGH ONE LINK IN LAG SETUP in ExtremeSwitching (ERS)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-ers/traffic-only-going-through-one-link-in-lag-setup/m-p/93960#M303</link>
    <description>&lt;P&gt;On the ERS side, an MLT/LAG by default does L2 MAC based hashing. Which can be sub-optimal if the ERS is connected to a router, towards which all traffic uses the same MAC.&lt;/P&gt;&lt;P&gt;You can make ERS do L3 IP based hashing on the MLT/LAG, but you need to set "load-balance advanced" on the MLT group.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Nov 2022 15:04:07 GMT</pubDate>
    <dc:creator>Ludovico_Steven</dc:creator>
    <dc:date>2022-11-30T15:04:07Z</dc:date>
    <item>
      <title>TRAFFIC ONLY GOING THROUGH ONE LINK IN LAG SETUP</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-ers/traffic-only-going-through-one-link-in-lag-setup/m-p/93952#M302</link>
      <description>&lt;P&gt;Please i need a suggestion or an advice on what could be the issue ,&lt;BR /&gt;I have an extreme switch connecting to a juniper SRX Firewall through a LAG (5 interface lag together) connection .&lt;BR /&gt;Then recently i noticed out of the LAG only one of the link is picking traffic while others are not doing anything . what could be the problem ? as my traffic is expected to grow as we get into festive period.&lt;/P&gt;&lt;P&gt;Below show command for reference on the extreme switch BD-8810&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ola_0-1669799134607.png" style="width: 400px;"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/6254iAC2C644BDC1822FF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ola_0-1669799134607.png" alt="ola_0-1669799134607.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ola_1-1669799172529.png" style="width: 400px;"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/6255i5DF94D29547813FA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ola_1-1669799172529.png" alt="ola_1-1669799172529.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ola_5-1669799403232.png" style="width: 400px;"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/6259i5F26EEEC881825A0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ola_5-1669799403232.png" alt="ola_5-1669799403232.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial black,avant garde"&gt;&lt;U&gt;&lt;STRONG&gt;chassis cluster configuration on the firewall&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;show configuration |match redundancy| display set&lt;BR /&gt;set chassis cluster redundancy-group 0 node 0 priority 250&lt;BR /&gt;set chassis cluster redundancy-group 0 node 1 priority 100&lt;BR /&gt;set chassis cluster redundancy-group 1 node 0 priority 250&lt;BR /&gt;set chassis cluster redundancy-group 1 node 1 priority 100&lt;BR /&gt;set chassis cluster redundancy-group 1 preempt&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-7/2/0 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-19/2/0 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-7/2/1 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-19/2/1 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-7/2/2 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-7/2/3 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-19/2/2 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-19/2/3 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-7/2/4 weight 255&lt;BR /&gt;set chassis cluster redundancy-group 1 interface-monitor xe-19/2/4 weight 255&lt;BR /&gt;set interfaces reth0 redundant-ether-options redundancy-group 1&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 09:11:53 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-ers/traffic-only-going-through-one-link-in-lag-setup/m-p/93952#M302</guid>
      <dc:creator>ola</dc:creator>
      <dc:date>2022-11-30T09:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: TRAFFIC ONLY GOING THROUGH ONE LINK IN LAG SETUP</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-ers/traffic-only-going-through-one-link-in-lag-setup/m-p/93960#M303</link>
      <description>&lt;P&gt;On the ERS side, an MLT/LAG by default does L2 MAC based hashing. Which can be sub-optimal if the ERS is connected to a router, towards which all traffic uses the same MAC.&lt;/P&gt;&lt;P&gt;You can make ERS do L3 IP based hashing on the MLT/LAG, but you need to set "load-balance advanced" on the MLT group.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 15:04:07 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-ers/traffic-only-going-through-one-link-in-lag-setup/m-p/93960#M303</guid>
      <dc:creator>Ludovico_Steven</dc:creator>
      <dc:date>2022-11-30T15:04:07Z</dc:date>
    </item>
  </channel>
</rss>

