<?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 LACP negotiation failure in ExtremeSwitching (EOS)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/100856#M2425</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm encountering an issue with an active LACP connection on my X450e-48t and X450e-48p switches when using a long timeout.&lt;/P&gt;&lt;P&gt;Here's the scenario:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;My switch sends an LACPDU with activity and aggregation flags to remove a link from the LAG.&lt;/LI&gt;&lt;LI&gt;The Extreme switch accepts this and removes the link from the LAG, then starts a new connection by sending activity, aggregation, and sync packets.&lt;/LI&gt;&lt;LI&gt;However, my switch later replies with activity, aggregation, defaulted, and expired flags.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;At this point, the Extreme switch sometimes doesn't reply back immediately. When it does, it takes around 20-30 seconds to respond.&lt;/P&gt;&lt;P&gt;Has anyone experienced this issue? Is this a known bug, or is it expected behavior? Any insights or solutions would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jul 2024 06:16:53 GMT</pubDate>
    <dc:creator>khanjan</dc:creator>
    <dc:date>2024-07-08T06:16:53Z</dc:date>
    <item>
      <title>LACP negotiation failure</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/100856#M2425</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm encountering an issue with an active LACP connection on my X450e-48t and X450e-48p switches when using a long timeout.&lt;/P&gt;&lt;P&gt;Here's the scenario:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;My switch sends an LACPDU with activity and aggregation flags to remove a link from the LAG.&lt;/LI&gt;&lt;LI&gt;The Extreme switch accepts this and removes the link from the LAG, then starts a new connection by sending activity, aggregation, and sync packets.&lt;/LI&gt;&lt;LI&gt;However, my switch later replies with activity, aggregation, defaulted, and expired flags.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;At this point, the Extreme switch sometimes doesn't reply back immediately. When it does, it takes around 20-30 seconds to respond.&lt;/P&gt;&lt;P&gt;Has anyone experienced this issue? Is this a known bug, or is it expected behavior? Any insights or solutions would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 06:16:53 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/100856#M2425</guid>
      <dc:creator>khanjan</dc:creator>
      <dc:date>2024-07-08T06:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: LACP negotiation failure</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/100865#M2426</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I think you should like there is a problem with how your Extreme switches are handling LACP connections when using a longer timeout setting. After removing a link from the LAG there is a delay or inconsistency in how the switches respond to each other's LACP messages. This could be due to compatibility issues between the switches or a configuration mismatch. Checking and aligning the firmware versions and LACP settings on both switches might help resolve this issue.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 12:36:30 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/100865#M2426</guid>
      <dc:creator>selenaadone</dc:creator>
      <dc:date>2024-07-08T12:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: LACP negotiation failure</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/100869#M2427</link>
      <description>&lt;P&gt;okay, Thanks&amp;nbsp;&lt;a href="https://community.extremenetworks.com/t5/user/viewprofilepage/user-id/47686"&gt;@selenaadone&lt;/a&gt;&amp;nbsp;, I will take up upgrading extreme switch and run these tests.&amp;nbsp; It looks like switches are old and version too, it is&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;15.1.3.4 (Dec 2012).&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2024 04:34:09 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/100869#M2427</guid>
      <dc:creator>khanjan</dc:creator>
      <dc:date>2024-07-09T04:34:09Z</dc:date>
    </item>
    <item>
      <title>Re: LACP negotiation failure</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/110716#M2551</link>
      <description>&lt;P&gt;thanks for sharing...&amp;nbsp;&lt;A href="https://brevardcountypropertyappraiser.website/" target="_self"&gt;Brevard Property Appraiser BCPAO&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Aug 2024 06:59:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/lacp-negotiation-failure/m-p/110716#M2551</guid>
      <dc:creator>Clarence765</dc:creator>
      <dc:date>2024-08-05T06:59:51Z</dc:date>
    </item>
  </channel>
</rss>

