<?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: EVA3000 problems in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267256#M28447</link>
    <description>Hi Rob,&lt;BR /&gt;&lt;BR /&gt;I rebooted CVE server and the situation is the same. Actualy it is worse, because I can't access CVE over WEB. I have to use RDP.&lt;BR /&gt;&lt;BR /&gt;Domen</description>
    <pubDate>Thu, 11 Sep 2008 06:57:17 GMT</pubDate>
    <dc:creator>Domen Setar</dc:creator>
    <dc:date>2008-09-11T06:57:17Z</dc:date>
    <item>
      <title>EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267254#M28445</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Yesterday we suffered power outage on our EVA3000 disk array and CVE server. After power returned, EVA booted normaly. Later I noticed following problem:&lt;BR /&gt;EVA3000 is alive. I can see LUN-s on servers, but I can't access EVA3000 neither over CVE (V8) nor over SSSU. SSSU error is "storage cell is not initialized".&lt;BR /&gt;&lt;BR /&gt;Does anyone have an idea what could be wrong?&lt;BR /&gt;&lt;BR /&gt;P.S.: I tried to manage EVA3000 over my old CVE aplliance. The problem is the same. It must be something wrong on EVA3000.&lt;BR /&gt;&lt;BR /&gt;Best regards&lt;BR /&gt;&lt;BR /&gt;Domen</description>
      <pubDate>Thu, 11 Sep 2008 06:40:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267254#M28445</guid>
      <dc:creator>Domen Setar</dc:creator>
      <dc:date>2008-09-11T06:40:08Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267255#M28446</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Have you tried restarting Command View ?&lt;BR /&gt;&lt;BR /&gt;It might just be that things came up in a strange order and CV EVA has got confused...&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;Rob</description>
      <pubDate>Thu, 11 Sep 2008 06:51:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267255#M28446</guid>
      <dc:creator>Rob Leadbeater</dc:creator>
      <dc:date>2008-09-11T06:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267256#M28447</link>
      <description>Hi Rob,&lt;BR /&gt;&lt;BR /&gt;I rebooted CVE server and the situation is the same. Actualy it is worse, because I can't access CVE over WEB. I have to use RDP.&lt;BR /&gt;&lt;BR /&gt;Domen</description>
      <pubDate>Thu, 11 Sep 2008 06:57:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267256#M28447</guid>
      <dc:creator>Domen Setar</dc:creator>
      <dc:date>2008-09-11T06:57:17Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267257#M28448</link>
      <description>Hi, &lt;BR /&gt;did you upgrade the CVE after the power cut pls?</description>
      <pubDate>Thu, 11 Sep 2008 07:10:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267257#M28448</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2008-09-11T07:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267258#M28449</link>
      <description>No. I didn't. Why?</description>
      <pubDate>Thu, 11 Sep 2008 07:38:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267258#M28449</guid>
      <dc:creator>Domen Setar</dc:creator>
      <dc:date>2008-09-11T07:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267259#M28450</link>
      <description>It was just a question towards the possible eva controller and cve version incompatibility...</description>
      <pubDate>Thu, 11 Sep 2008 07:58:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267259#M28450</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2008-09-11T07:58:06Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267260#M28451</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I can't access CVE over WEB. I have to use RDP&lt;BR /&gt;&lt;BR /&gt;Are you sure that all the other equipment came back up OK following the power outage ?Any network problems ?&lt;BR /&gt;&lt;BR /&gt;Is CV EVA box plugged into the same SAN switch as the EVA3000 and hosts ?  Maybe you only have one path to it ?&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;Rob</description>
      <pubDate>Thu, 11 Sep 2008 08:21:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267260#M28451</guid>
      <dc:creator>Rob Leadbeater</dc:creator>
      <dc:date>2008-09-11T08:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 problems</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267261#M28452</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thanks for the help. Resync of controlers was needed to solve the problem.&lt;BR /&gt;&lt;BR /&gt;Case closed.</description>
      <pubDate>Thu, 11 Sep 2008 09:57:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-problems/m-p/4267261#M28452</guid>
      <dc:creator>Domen Setar</dc:creator>
      <dc:date>2008-09-11T09:57:45Z</dc:date>
    </item>
  </channel>
</rss>

