<?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: EVA4400 - Command View License - Lost after upgrade in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6875640#M67722</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;if you have a server with command view that manages EVA systems&lt;/P&gt;&lt;P&gt;all licneses of EVA's connected to this server are placed:&lt;/P&gt;&lt;P&gt;C:\Program Files (x86)\Common Files\Hewlett-Packard\HPCvEvaLic\data&lt;/P&gt;&lt;P&gt;the file name is&amp;nbsp;LicFile.txt&lt;/P&gt;&lt;P&gt;if you connect an EVA that has been recognized by this server ( model and WWN) the licenses will be loaded automaticly.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jul 2016 09:26:26 GMT</pubDate>
    <dc:creator>giladzzz</dc:creator>
    <dc:date>2016-07-06T09:26:26Z</dc:date>
    <item>
      <title>EVA4400 - Command View License - Lost after upgrade</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6870583#M67676</link>
      <description>&lt;P&gt;A smaller client of ours still uses the EoL EVA4400 as a backup SAN. Until now all has been well, but an internal decision was made to repurpose the device and the array was reinitialized. With the later versions of firmware this wipes the CV license details which need to be re-entered; which of course they didn't make a note of.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The device was purchased a number of years ago, and came with a CV license at the time - it doesn't now have any form of active warranty or support contract though. Surely it is still possible to recover the license details from HPE (which didn't exist at the time of purchase..) and put the device back in active sercice. It's currently using at the Instant-On licensing but this will of course expire.&lt;/P&gt;&lt;P&gt;So far I've been told it will be aroudn £10k to purchase a new license, but I can't understand how the original license is considered "null and void" it the client didn't keep a copy of the activation key, that can't be right? Can HPE look up the original license from the node's WWN, has anyone had a similar experience or idea of how to assist our customer?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2016 07:58:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6870583#M67676</guid>
      <dc:creator>SSITSupport</dc:creator>
      <dc:date>2016-06-20T07:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 - Command View License - Lost after upgrade</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6870625#M67677</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;if you have command view server the license is on the server&lt;/P&gt;&lt;P&gt;if youwere using the managment module then you have a problem&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2016 10:13:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6870625#M67677</guid>
      <dc:creator>giladzzz</dc:creator>
      <dc:date>2016-06-20T10:13:43Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 - Command View License - Lost after upgrade</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6873872#M67692</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp; All licensing is actually stored on the array itself (the array keeps an array of internal data for configurations, licenses, etc. called quorum space). When you reinitialize an EVA, all of this data is erased and reconfigured. No license information is kept on any Command View server. Firmware upgrades will not cause any of this information to be deleted. However, this information must be re-entered to the array. The license is tied to the original array WWN and customer. That customer (must be the original purchaser) should be able to contact HPE licensing to recover that information. However, it must be the original purchaser.&lt;/P&gt;&lt;P&gt;I do not work with the licensing team and cannot claim for any of their policies. I work for the engineering team and can only speak for the array on a technical aspect.&lt;/P&gt;&lt;P&gt;Good Luck&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jun 2016 16:41:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6873872#M67692</guid>
      <dc:creator>MHuff</dc:creator>
      <dc:date>2016-06-29T16:41:58Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4400 - Command View License - Lost after upgrade</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6875640#M67722</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;if you have a server with command view that manages EVA systems&lt;/P&gt;&lt;P&gt;all licneses of EVA's connected to this server are placed:&lt;/P&gt;&lt;P&gt;C:\Program Files (x86)\Common Files\Hewlett-Packard\HPCvEvaLic\data&lt;/P&gt;&lt;P&gt;the file name is&amp;nbsp;LicFile.txt&lt;/P&gt;&lt;P&gt;if you connect an EVA that has been recognized by this server ( model and WWN) the licenses will be loaded automaticly.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2016 09:26:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva4400-command-view-license-lost-after-upgrade/m-p/6875640#M67722</guid>
      <dc:creator>giladzzz</dc:creator>
      <dc:date>2016-07-06T09:26:26Z</dc:date>
    </item>
  </channel>
</rss>

