<?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: 8200 stack member traffic issue in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97631#M6901</link>
    <description>&lt;P&gt;Also, the firmware is RDR10010c_cd3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Sep 2024 13:54:33 GMT</pubDate>
    <dc:creator>KabalVT</dc:creator>
    <dc:date>2024-09-19T13:54:33Z</dc:date>
    <item>
      <title>8200 stack member traffic issue</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97630#M6900</link>
      <description>&lt;P&gt;Hi, we have seen this twice now in two different stacks of ICX 8200 switches. If one of the stack members reboots for some reason while the other stack members stay up, it will successfully rejoin the stack after reboot but only seems to pass broadcast traffic. Devices connected to it, no matter the vlan, can receive DHCP IPs but no other communication works. The entire stack must be reloaded to correct this. Anyone know what this might be and if there is a resolution?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 13:53:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97630#M6900</guid>
      <dc:creator>KabalVT</dc:creator>
      <dc:date>2024-09-19T13:53:19Z</dc:date>
    </item>
    <item>
      <title>Re: 8200 stack member traffic issue</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97631#M6901</link>
      <description>&lt;P&gt;Also, the firmware is RDR10010c_cd3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 13:54:33 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97631#M6901</guid>
      <dc:creator>KabalVT</dc:creator>
      <dc:date>2024-09-19T13:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: 8200 stack member traffic issue</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97632#M6902</link>
      <description>&lt;P&gt;Hey there,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is likely a known issue being fixed in 10010e. Please open a support case and list it here. I will grab it and get you the code prior to the formal GA date (Sept. 27th).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 14:31:00 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97632#M6902</guid>
      <dc:creator>BenBeck</dc:creator>
      <dc:date>2024-09-19T14:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: 8200 stack member traffic issue</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97637#M6903</link>
      <description>&lt;P&gt;Thanks. It is case 01819491.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 14:51:24 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/8200-stack-member-traffic-issue/m-p/97637#M6903</guid>
      <dc:creator>KabalVT</dc:creator>
      <dc:date>2024-09-19T14:51:24Z</dc:date>
    </item>
  </channel>
</rss>

