<?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: G and H firmware? in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/G-and-H-firmware/m-p/113078#M7955</link>
    <description>&lt;P&gt;Hey Robert,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is a great question! There is no issue with H. The naming conventions and patch strategy over the years has evolved a bit. 10010h_cd1 has quite a bit of new stuff in there (&lt;SPAN&gt;new hardware support, ICX8100-X stacking, 8100 L3 support, 4x25 module support on 7550, ERSPAN on 8200, etc.). This inherently leads to more code change when compared to a patch that is strictly customer found defects. We have decided to continue the 10010g_cdx line as stability train within 10010. The goal here is stability and minimal code change. 10010g_cd6 is our current target path and 10010g_cd7 will build on that patch. For the time being, we will continue to recommend 10010g_cd6 or cd7 over 10010h_cdx if it has all of the hardware/feature support that is needed for you network. If you need something in 10010h_cd1, you can absolutely use it! Hope that helps. Here is reference on recommended code:&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;A href="https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/What-code-should-I-run-on-my-ICX-Check-the-Recommended-Firmware/td-p/33612" target="_blank" rel="noopener"&gt;https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/What-code-should-I-run-on-my-ICX-Check-the-Recommended-Firmware/td-p/33612&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Feb 2026 17:12:05 GMT</pubDate>
    <dc:creator>BenBeck</dc:creator>
    <dc:date>2026-02-20T17:12:05Z</dc:date>
    <item>
      <title>G and H firmware?</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/G-and-H-firmware/m-p/113077#M7954</link>
      <description>&lt;P&gt;There was an H firmware released a few days ago but now a G_cd7 released today. Is there an issue with the H? What's the deal with the seaming "downgraded" firmware release?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Feb 2026 16:59:40 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/G-and-H-firmware/m-p/113077#M7954</guid>
      <dc:creator>robert_berki</dc:creator>
      <dc:date>2026-02-20T16:59:40Z</dc:date>
    </item>
    <item>
      <title>Re: G and H firmware?</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/G-and-H-firmware/m-p/113078#M7955</link>
      <description>&lt;P&gt;Hey Robert,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is a great question! There is no issue with H. The naming conventions and patch strategy over the years has evolved a bit. 10010h_cd1 has quite a bit of new stuff in there (&lt;SPAN&gt;new hardware support, ICX8100-X stacking, 8100 L3 support, 4x25 module support on 7550, ERSPAN on 8200, etc.). This inherently leads to more code change when compared to a patch that is strictly customer found defects. We have decided to continue the 10010g_cdx line as stability train within 10010. The goal here is stability and minimal code change. 10010g_cd6 is our current target path and 10010g_cd7 will build on that patch. For the time being, we will continue to recommend 10010g_cd6 or cd7 over 10010h_cdx if it has all of the hardware/feature support that is needed for you network. If you need something in 10010h_cd1, you can absolutely use it! Hope that helps. Here is reference on recommended code:&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;A href="https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/What-code-should-I-run-on-my-ICX-Check-the-Recommended-Firmware/td-p/33612" target="_blank" rel="noopener"&gt;https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/What-code-should-I-run-on-my-ICX-Check-the-Recommended-Firmware/td-p/33612&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Feb 2026 17:12:05 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/G-and-H-firmware/m-p/113078#M7955</guid>
      <dc:creator>BenBeck</dc:creator>
      <dc:date>2026-02-20T17:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: G and H firmware?</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/G-and-H-firmware/m-p/113079#M7956</link>
      <description>&lt;P&gt;thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 20 Feb 2026 17:53:22 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/G-and-H-firmware/m-p/113079#M7956</guid>
      <dc:creator>robert_berki</dc:creator>
      <dc:date>2026-02-20T17:53:22Z</dc:date>
    </item>
  </channel>
</rss>

