<?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 EVA-8100 Parse File Missing in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354420#M30076</link>
    <description>Hi There,&lt;BR /&gt;&lt;BR /&gt;I have an EVA 8100. It seems that the parse file of the EVA is missing for the firmware. Can anyone suggest me how to check the firmware revison &amp;amp; restore the parse file?&lt;BR /&gt;&lt;BR /&gt;Regards-Kranti</description>
    <pubDate>Mon, 09 Feb 2009 03:38:07 GMT</pubDate>
    <dc:creator>Kranti Mahmud</dc:creator>
    <dc:date>2009-02-09T03:38:07Z</dc:date>
    <item>
      <title>EVA-8100 Parse File Missing</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354420#M30076</link>
      <description>Hi There,&lt;BR /&gt;&lt;BR /&gt;I have an EVA 8100. It seems that the parse file of the EVA is missing for the firmware. Can anyone suggest me how to check the firmware revison &amp;amp; restore the parse file?&lt;BR /&gt;&lt;BR /&gt;Regards-Kranti</description>
      <pubDate>Mon, 09 Feb 2009 03:38:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354420#M30076</guid>
      <dc:creator>Kranti Mahmud</dc:creator>
      <dc:date>2009-02-09T03:38:07Z</dc:date>
    </item>
    <item>
      <title>Re: EVA-8100 Parse File Missing</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354421#M30077</link>
      <description>The firmware for the EVA or for the server?</description>
      <pubDate>Mon, 09 Feb 2009 05:05:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354421#M30077</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-02-09T05:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: EVA-8100 Parse File Missing</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354422#M30078</link>
      <description>Firmware version of EVA....&lt;BR /&gt;&lt;BR /&gt;Regards-Kranti</description>
      <pubDate>Mon, 09 Feb 2009 08:34:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354422#M30078</guid>
      <dc:creator>Kranti Mahmud</dc:creator>
      <dc:date>2009-02-09T08:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: EVA-8100 Parse File Missing</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354423#M30079</link>
      <description>The full "software version", you can check it clicking on one of the controllers, for example:&lt;BR /&gt;&lt;BR /&gt;CR0ECA-6110</description>
      <pubDate>Mon, 09 Feb 2009 09:59:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354423#M30079</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2009-02-09T09:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: EVA-8100 Parse File Missing</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354424#M30080</link>
      <description>If you have found out the version, get hold of the .TXT representation of the file or the controller firmware image (e.g. 210_6110.SSS or whatever it is called), which includes a copy.&lt;BR /&gt;&lt;BR /&gt;Then use the [Send parse file] button, specify the file and send it to the management server.</description>
      <pubDate>Mon, 09 Feb 2009 10:23:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-8100-parse-file-missing/m-p/4354424#M30080</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2009-02-09T10:23:27Z</dc:date>
    </item>
  </channel>
</rss>

