<?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: E-series Firmware version explanation in AFF</title>
    <link>https://community.netapp.com/t5/AFF/E-series-Firmware-version-explanation/m-p/146523#M532</link>
    <description>&lt;P&gt;is there any references for the company id in "third octet" . ?&lt;/P&gt;</description>
    <pubDate>Fri, 08 Feb 2019 15:16:15 GMT</pubDate>
    <dc:creator>saranraj456</dc:creator>
    <dc:date>2019-02-08T15:16:15Z</dc:date>
    <item>
      <title>E-series Firmware version explanation</title>
      <link>https://community.netapp.com/t5/AFF/E-series-Firmware-version-explanation/m-p/146035#M521</link>
      <description>&lt;P&gt;Is there any reason behind the lengthy E-series Firmware version like -&amp;nbsp;&lt;SPAN&gt;8.25.14.00&amp;nbsp;( with Four octet) , first octet can be assumed as Major version, next one can be classified as a minor release or patch.However , why do we need to have such a long version .&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:56:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/E-series-Firmware-version-explanation/m-p/146035#M521</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2025-06-04T12:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: E-series Firmware version explanation</title>
      <link>https://community.netapp.com/t5/AFF/E-series-Firmware-version-explanation/m-p/146371#M524</link>
      <description>&lt;P&gt;Hi there!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The first two octets are the important ones - major and minor version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The E-Series product line has a long history of OEM usage - so we make software and hardware for others to resell, based on the E-Series platform, but with different branding. This flows on into documentation, software, user interface, hardware, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Usage varies based on what part of E-Series is being discussed, but generally the third octet is based on which company it is&amp;nbsp;branded for, and the 4th one is a build number.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 02:23:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/E-series-Firmware-version-explanation/m-p/146371#M524</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2019-02-04T02:23:50Z</dc:date>
    </item>
    <item>
      <title>Re: E-series Firmware version explanation</title>
      <link>https://community.netapp.com/t5/AFF/E-series-Firmware-version-explanation/m-p/146523#M532</link>
      <description>&lt;P&gt;is there any references for the company id in "third octet" . ?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2019 15:16:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/E-series-Firmware-version-explanation/m-p/146523#M532</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2019-02-08T15:16:15Z</dc:date>
    </item>
  </channel>
</rss>

