<?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: packet loss on summit 670 connected with LAG, MLAG ? in Network Architecture &amp; Design</title>
    <link>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13404#M808</link>
    <description>Thanks for circling back to validate Pedro.  Good stuff!</description>
    <pubDate>Thu, 13 Aug 2015 12:24:00 GMT</pubDate>
    <dc:creator>Ryan_Mathews</dc:creator>
    <dc:date>2015-08-13T12:24:00Z</dc:date>
    <item>
      <title>packet loss on summit 670 connected with LAG, MLAG ?</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13401#M805</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
    Strange problem with packets loss. I have LAG on port 47-48 connected to 2 different switches with MLAG. I see problem only between pair:&lt;BR /&gt;
&lt;BR /&gt;
src mac  f0:1f:af:d7:b5:37  and dst  mac  00:18:9d:08:c8:59 rest of traffic are ok. &lt;BR /&gt;
&lt;BR /&gt;
Summit sees in fdb table dst mac on port 47 but he sends via port 48 ( according to counters on port 47,48).. On next switch (uplink, also summit) i can't see any packets ( checked by port mirroring and ingress counters)&lt;BR /&gt;
&lt;BR /&gt;
If i disable port 48 all works correct. If i change src mac address on server - all works also correct. &lt;BR /&gt;
&lt;BR /&gt;
There is  some well known bug in hashing in LAG/MLAG in 15.3.1.4 v1531b4-patch1-18 ?&lt;BR /&gt;
&lt;BR /&gt;
    What has higher precedence when switch have to choose wich port use to send: entry in fdb or hash alghoritm ? &lt;BR /&gt;
&lt;BR /&gt;
     some outputs:&lt;BR /&gt;
&lt;BR /&gt;
     Summit8.48  # show fdb 00:18:9d:08:c8:59&lt;BR /&gt;
&lt;BR /&gt;
    Mac Vlan  Age Flags Port / Virtual Port List&lt;BR /&gt;
&lt;BR /&gt;
    ------------------------------------------------------------------------------&lt;BR /&gt;
&lt;BR /&gt;
    00:18:9d:08:c8:59  vlan183(0183) 0041 d m 47&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    *  Summit8.49 # debug hal show fdb | include 00:18:9d:08:c8:59&lt;BR /&gt;
&lt;BR /&gt;
    00:18:9d:08:c8:59  183 00001021 47 TRUE FALSE&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    *  Summit8.65 # show policy trampek&lt;BR /&gt;
&lt;BR /&gt;
    Policies  at Policy Server:&lt;BR /&gt;
&lt;BR /&gt;
    Policy:  trampek&lt;BR /&gt;
&lt;BR /&gt;
    entry  test4 {&lt;BR /&gt;
&lt;BR /&gt;
    if match  all {&lt;BR /&gt;
&lt;BR /&gt;
    ethernet-source-address f0:1f:af:d7:b5:37;&lt;BR /&gt;
&lt;BR /&gt;
    }&lt;BR /&gt;
&lt;BR /&gt;
    then {&lt;BR /&gt;
&lt;BR /&gt;
    log ;&lt;BR /&gt;
&lt;BR /&gt;
    count  trampek4 ;&lt;BR /&gt;
&lt;BR /&gt;
    permit ;&lt;BR /&gt;
&lt;BR /&gt;
    }&lt;BR /&gt;
&lt;BR /&gt;
    }&lt;BR /&gt;
&lt;BR /&gt;
    Number  of clients bound to policy: 1&lt;BR /&gt;
&lt;BR /&gt;
    Client:  acl bound once&lt;BR /&gt;
&lt;BR /&gt;
      &lt;BR /&gt;
&lt;BR /&gt;
    Summit8.62  # show access-list counter ports 47 48 egress&lt;BR /&gt;
&lt;BR /&gt;
    Policy  Name Vlan Name Port Direction&lt;BR /&gt;
&lt;BR /&gt;
    Counter  Name Packet Count Byte Count&lt;BR /&gt;
&lt;BR /&gt;
    ==================================================================&lt;BR /&gt;
&lt;BR /&gt;
    trampek  * 47 egress&lt;BR /&gt;
&lt;BR /&gt;
    trampek4  0&lt;BR /&gt;
&lt;BR /&gt;
    trampek  * 48 egress&lt;BR /&gt;
&lt;BR /&gt;
    trampek4  10&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    Image :  ExtremeXOS version 15.3.1.4 v1531b4-patch1-18&lt;BR /&gt;
&lt;BR /&gt;
     enable  sharing 47 grouping 47-48 algorithm address-based L3_L4 lacp&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    thanks for help,&lt;BR /&gt;
&lt;BR /&gt;
Pedro&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Aug 2015 20:14:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13401#M805</guid>
      <dc:creator>Pedro2</dc:creator>
      <dc:date>2015-08-04T20:14:00Z</dc:date>
    </item>
    <item>
      <title>RE: packet loss on summit 670 connected with LAG, MLAG ?</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13402#M806</link>
      <description>Pedro,&lt;BR /&gt;
&lt;BR /&gt;
The EXOS software version you are running is susceptible to a known defect that can cause traffic forwarding problems:&lt;BR /&gt;
&lt;BR /&gt;
PD4-4490184741:Traffic loss occurs on switches due to parity errors in L3 table.With this issue only certain traffic flows will be affected (as you have described.  To confirm this issue a debug session with the GTAC would be required.&lt;BR /&gt;
&lt;BR /&gt;
PD4-4490184741 was corrected in 15.3.1.4patch1-36.  However, the current recommended software version for the X670 platform is EXOS 15.5.4.2-patch1-5.xos.&lt;BR /&gt;
&lt;BR /&gt;
           &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Aug 2015 20:37:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13402#M806</guid>
      <dc:creator>Chad_Smith1</dc:creator>
      <dc:date>2015-08-04T20:37:00Z</dc:date>
    </item>
    <item>
      <title>RE: packet loss on summit 670 connected with LAG, MLAG ?</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13403#M807</link>
      <description>after upgrade it works for me, thanks!</description>
      <pubDate>Thu, 13 Aug 2015 12:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13403#M807</guid>
      <dc:creator>Pedro2</dc:creator>
      <dc:date>2015-08-13T12:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: packet loss on summit 670 connected with LAG, MLAG ?</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13404#M808</link>
      <description>Thanks for circling back to validate Pedro.  Good stuff!</description>
      <pubDate>Thu, 13 Aug 2015 12:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13404#M808</guid>
      <dc:creator>Ryan_Mathews</dc:creator>
      <dc:date>2015-08-13T12:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: packet loss on summit 670 connected with LAG, MLAG ?</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13405#M809</link>
      <description>I have created a GTAC Knowledge article that provides further information on these software defects: &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Traffic-loss-due-to-parity-errors/?q=parity&amp;amp;#38;l=en_US&amp;amp;#38;fs=Search&amp;amp;#38;pn=1" target="_blank" rel="nofollow noreferrer noopener"&gt;Traffic loss due to parity errors&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Aug 2015 00:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/packet-loss-on-summit-670-connected-with-lag-mlag/m-p/13405#M809</guid>
      <dc:creator>Chad_Smith1</dc:creator>
      <dc:date>2015-08-18T00:15:00Z</dc:date>
    </item>
  </channel>
</rss>

