<?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: EVA5000 - cannot initialize in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107288#M10129</link>
    <description>When Media inaccesable is returned &lt;BR /&gt;(a failure of a SCMI command), &lt;BR /&gt;it means the EVA has been discovered. Zoning and WWN will not be a problem i guess. &lt;BR /&gt;&lt;BR /&gt;Most probably the NSA service crashed.&lt;BR /&gt;Restarting Command view EVA is then a solution, and if that doens`t work, rebooting the appliance does. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 31 Oct 2003 14:29:39 GMT</pubDate>
    <dc:creator>Ronald Hendriks</dc:creator>
    <dc:date>2003-10-31T14:29:39Z</dc:date>
    <item>
      <title>EVA5000 - cannot initialize</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107285#M10126</link>
      <description>EVA5000, SMA 2.0 SP4, SANWorks Edge Switches 2/32. Every attempt to initalize storage system fails with error "Media is Innaccessible". Any hints?</description>
      <pubDate>Fri, 31 Oct 2003 05:35:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107285#M10126</guid>
      <dc:creator>Enes Dizdarevic</dc:creator>
      <dc:date>2003-10-31T05:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA5000 - cannot initialize</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107286#M10127</link>
      <description>try to restart Command view EVA, if that doesn`t work, reboot the appliance. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 31 Oct 2003 07:57:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107286#M10127</guid>
      <dc:creator>Ronald Hendriks</dc:creator>
      <dc:date>2003-10-31T07:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: EVA5000 - cannot initialize</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107287#M10128</link>
      <description>Have you entered the WWN and checksum in the OCP (On the controller)?&lt;BR /&gt;&lt;BR /&gt;Do you have zoning set up, and if so, do you have a zone that includes the management appliance, and the controllers?</description>
      <pubDate>Fri, 31 Oct 2003 12:45:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107287#M10128</guid>
      <dc:creator>Lee Solomonson_1</dc:creator>
      <dc:date>2003-10-31T12:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: EVA5000 - cannot initialize</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107288#M10129</link>
      <description>When Media inaccesable is returned &lt;BR /&gt;(a failure of a SCMI command), &lt;BR /&gt;it means the EVA has been discovered. Zoning and WWN will not be a problem i guess. &lt;BR /&gt;&lt;BR /&gt;Most probably the NSA service crashed.&lt;BR /&gt;Restarting Command view EVA is then a solution, and if that doens`t work, rebooting the appliance does. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 31 Oct 2003 14:29:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107288#M10129</guid>
      <dc:creator>Ronald Hendriks</dc:creator>
      <dc:date>2003-10-31T14:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA5000 - cannot initialize</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107289#M10130</link>
      <description>Thank you all for your responses. I have solved the problem. I had factory preinstalled firmware ver. 3001. After I downgraded firmware to ver. 3000 which I had im my VCS kit problem disappeared.&lt;BR /&gt;&lt;BR /&gt;The question is why HP delivers firmware 3000 in VCS kit and 3001 installed.</description>
      <pubDate>Fri, 31 Oct 2003 16:32:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva5000-cannot-initialize/m-p/3107289#M10130</guid>
      <dc:creator>Enes Dizdarevic</dc:creator>
      <dc:date>2003-10-31T16:32:23Z</dc:date>
    </item>
  </channel>
</rss>

