<?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 Are New Keys Required upon Upgrade to new NetSight versions? in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/are-new-keys-required-upon-upgrade-to-new-netsight-versions/m-p/42446#M109</link>
    <description>Article ID: 5368 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
Netsight&lt;BR /&gt;
Atlas Console&lt;BR /&gt;
Policy Manager&lt;BR /&gt;
ACL Manager&lt;BR /&gt;
Inventory Manager &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
New license key required?&lt;BR /&gt;
Upgrade &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
The NetSight products generally require a different License Key for each major release. &lt;BR /&gt;
&lt;BR /&gt;
Given a version format of x.y.z, each major release is defined by the first two digits, x.y. &lt;BR /&gt;
For example, Atlas Console versions 1.4 and 1.4.1 could use the same key, while an upgrade from version 1.3 to 1.4 would require a new key. &lt;BR /&gt;
&lt;BR /&gt;
Customers purchasing a NetSight product without a service contract are restricted to use of that major release only.&lt;BR /&gt;
Exceptions:&lt;UL&gt; 
&lt;LI&gt;A 2.1 unhosted license will work for 2.1 and 2.2 and 2.3 versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;A 2.2 hosted license will work for 2.2 and 2.3 versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;A 3.0 hosted license will work for 3.0 through 4.4 versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;A 3.1 hosted license will work for 3.1 through 4.4 (&lt;A href="http://bit.ly/IimEi5" target="_blank" rel="nofollow noreferrer noopener"&gt;15005&lt;/A&gt;) versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;An Enterprise license will work for 4.2.1 and higher versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;An Enterprise license is required for all 5.0 and higher installs, and 64-bit Linux/Ubuntu installs.&lt;/LI&gt;&lt;/UL&gt;
Customers purchasing a NetSight product &lt;I&gt;with&lt;/I&gt; a service contract are entitled to upgrade to later major releases of the same product; and upon request will be issued a new License key as necessary for that purpose.&lt;BR /&gt;
See &lt;A href="https://extranet.enterasys.com/MySupport/Licensing/Pages/NetSightV5Upgrade.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extranet.enterasys.com/MySupport/Licensing/Pages/NetSightV5Upgrade.aspx&lt;/A&gt;. &lt;BR /&gt;
&lt;BR /&gt;
See &lt;A href="http://bit.ly/1aTRMLm" target="_blank" rel="nofollow noreferrer noopener"&gt;5461&lt;/A&gt;, for the NetSight download &amp;amp; licensing procedure.</description>
    <pubDate>Thu, 05 Sep 2013 06:04:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-09-05T06:04:00Z</dc:date>
    <item>
      <title>Are New Keys Required upon Upgrade to new NetSight versions?</title>
      <link>https://community.extremenetworks.com/t5/faqs/are-new-keys-required-upon-upgrade-to-new-netsight-versions/m-p/42446#M109</link>
      <description>Article ID: 5368 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
Netsight&lt;BR /&gt;
Atlas Console&lt;BR /&gt;
Policy Manager&lt;BR /&gt;
ACL Manager&lt;BR /&gt;
Inventory Manager &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
New license key required?&lt;BR /&gt;
Upgrade &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
The NetSight products generally require a different License Key for each major release. &lt;BR /&gt;
&lt;BR /&gt;
Given a version format of x.y.z, each major release is defined by the first two digits, x.y. &lt;BR /&gt;
For example, Atlas Console versions 1.4 and 1.4.1 could use the same key, while an upgrade from version 1.3 to 1.4 would require a new key. &lt;BR /&gt;
&lt;BR /&gt;
Customers purchasing a NetSight product without a service contract are restricted to use of that major release only.&lt;BR /&gt;
Exceptions:&lt;UL&gt; 
&lt;LI&gt;A 2.1 unhosted license will work for 2.1 and 2.2 and 2.3 versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;A 2.2 hosted license will work for 2.2 and 2.3 versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;A 3.0 hosted license will work for 3.0 through 4.4 versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;A 3.1 hosted license will work for 3.1 through 4.4 (&lt;A href="http://bit.ly/IimEi5" target="_blank" rel="nofollow noreferrer noopener"&gt;15005&lt;/A&gt;) versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;An Enterprise license will work for 4.2.1 and higher versions, whether from upgrade or new install. 
&lt;/LI&gt;&lt;LI&gt;An Enterprise license is required for all 5.0 and higher installs, and 64-bit Linux/Ubuntu installs.&lt;/LI&gt;&lt;/UL&gt;
Customers purchasing a NetSight product &lt;I&gt;with&lt;/I&gt; a service contract are entitled to upgrade to later major releases of the same product; and upon request will be issued a new License key as necessary for that purpose.&lt;BR /&gt;
See &lt;A href="https://extranet.enterasys.com/MySupport/Licensing/Pages/NetSightV5Upgrade.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extranet.enterasys.com/MySupport/Licensing/Pages/NetSightV5Upgrade.aspx&lt;/A&gt;. &lt;BR /&gt;
&lt;BR /&gt;
See &lt;A href="http://bit.ly/1aTRMLm" target="_blank" rel="nofollow noreferrer noopener"&gt;5461&lt;/A&gt;, for the NetSight download &amp;amp; licensing procedure.</description>
      <pubDate>Thu, 05 Sep 2013 06:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/are-new-keys-required-upon-upgrade-to-new-netsight-versions/m-p/42446#M109</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-09-05T06:04:00Z</dc:date>
    </item>
  </channel>
</rss>

