<?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 EVA6000 moved disks 'Command View EVA has detected this array as inoperative' in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642162#M44811</link>
    <description>We have two old EVA that we decommissioned a while ago.  I have been asked to connect one of them up using all the large disk (500TB and 1TB disks) for our development department to use on a temporary basis.  However when I discover the EVA using command view I get the error ‘Command View EVA has detected this array as inoperative. Contact HP Service for assistance.’ &lt;BR /&gt;&lt;BR /&gt;I am guessing that the error is generated due to the metadata on the disks being from two different EVA’s.  We do not need the data that is on any of the disks so they could all be wipe clean.  Can any one let me how I can scrub all the disks so I can create a new disk group. Or will I need to work out which disk were from which EVA and move all the original disks back?  Then removed and add each disk one at a time?&lt;BR /&gt;&lt;BR /&gt;Jo&lt;BR /&gt;</description>
    <pubDate>Thu, 03 Jun 2010 15:41:22 GMT</pubDate>
    <dc:creator>homehome16</dc:creator>
    <dc:date>2010-06-03T15:41:22Z</dc:date>
    <item>
      <title>EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642162#M44811</link>
      <description>We have two old EVA that we decommissioned a while ago.  I have been asked to connect one of them up using all the large disk (500TB and 1TB disks) for our development department to use on a temporary basis.  However when I discover the EVA using command view I get the error ‘Command View EVA has detected this array as inoperative. Contact HP Service for assistance.’ &lt;BR /&gt;&lt;BR /&gt;I am guessing that the error is generated due to the metadata on the disks being from two different EVA’s.  We do not need the data that is on any of the disks so they could all be wipe clean.  Can any one let me how I can scrub all the disks so I can create a new disk group. Or will I need to work out which disk were from which EVA and move all the original disks back?  Then removed and add each disk one at a time?&lt;BR /&gt;&lt;BR /&gt;Jo&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Jun 2010 15:41:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642162#M44811</guid>
      <dc:creator>homehome16</dc:creator>
      <dc:date>2010-06-03T15:41:22Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642163#M44812</link>
      <description>In this case, without any other information, I would&lt;BR /&gt;&lt;BR /&gt;- make sure the EVA has the latest firmare&lt;BR /&gt;&lt;BR /&gt;- make sure the disk drives have the latest firmware&lt;BR /&gt;&lt;BR /&gt;- initalize the eva, thereby functionally wiping the disks and creating new metadata&lt;BR /&gt;&lt;BR /&gt;I suspect you will only have to do the last step, but should do the first two.</description>
      <pubDate>Fri, 04 Jun 2010 00:26:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642163#M44812</guid>
      <dc:creator>McCready</dc:creator>
      <dc:date>2010-06-04T00:26:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642164#M44813</link>
      <description>Thanks for the responce.  I know that all the fireware is up to date as this was all updated before we decommissioned them.&lt;BR /&gt;&lt;BR /&gt;Just one more questsion how do I re-initalize the eva. Is this an option that I can select when the EVA boot up?</description>
      <pubDate>Fri, 04 Jun 2010 05:47:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642164#M44813</guid>
      <dc:creator>homehome16</dc:creator>
      <dc:date>2010-06-04T05:47:13Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642165#M44814</link>
      <description>Good morning, &lt;BR /&gt;&lt;BR /&gt;This is under the system options in command view - uninitialize array.</description>
      <pubDate>Fri, 04 Jun 2010 05:57:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642165#M44814</guid>
      <dc:creator>Johan Guldmyr</dc:creator>
      <dc:date>2010-06-04T05:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642166#M44815</link>
      <description>I canâ  t login to Command View.  Can it be done via the menu directly on the controller?</description>
      <pubDate>Fri, 04 Jun 2010 06:13:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642166#M44815</guid>
      <dc:creator>homehome16</dc:creator>
      <dc:date>2010-06-04T06:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642167#M44816</link>
      <description>Look under here in the OCP display (this varies between the firmware/XCS versions):&lt;BR /&gt;&lt;BR /&gt;Shutdown options&lt;BR /&gt;    Restart&lt;BR /&gt;        RESTART SYSTEM? NO&lt;BR /&gt;    Power Off&lt;BR /&gt;        POWER OFF SYSTEM? NO&lt;BR /&gt;    System Uninitialize&lt;BR /&gt;        REALLY uNITIALIZE NO &lt;BR /&gt;&lt;BR /&gt;I would recommend that you make sure that yuo have the WWN+checksum and serial number available of the EVA. Should be available on a sticker on the controller.</description>
      <pubDate>Fri, 04 Jun 2010 06:23:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642167#M44816</guid>
      <dc:creator>Johan Guldmyr</dc:creator>
      <dc:date>2010-06-04T06:23:23Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642168#M44817</link>
      <description>Thanks for this...  We have the WWN and the check sum..  Will give it a go later on today.&lt;BR /&gt;&lt;BR /&gt;Thanks again.&lt;BR /&gt;&lt;BR /&gt;Jo</description>
      <pubDate>Fri, 04 Jun 2010 06:25:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642168#M44817</guid>
      <dc:creator>homehome16</dc:creator>
      <dc:date>2010-06-04T06:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642169#M44818</link>
      <description>Good luck :)&lt;BR /&gt;&lt;BR /&gt;I would also recommend that you check over the backend cabling of the EVA, make sure that it is cabled correctly.&lt;BR /&gt;&lt;BR /&gt;Check out this guide:&lt;BR /&gt;&lt;BR /&gt;"HP StorageWorks 4x00/6x00/8x00 Enterprise Virtual Array hardware configuration guide (5697-7338, February 2008)"&lt;BR /&gt;&lt;BR /&gt;on &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=101&amp;amp;prodClassId=-1&amp;amp;contentType=SupportManual&amp;amp;docIndexId=64180&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=470490" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=101&amp;amp;prodClassId=-1&amp;amp;contentType=SupportManual&amp;amp;docIndexId=64180&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=470490&lt;/A&gt;</description>
      <pubDate>Fri, 04 Jun 2010 06:30:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642169#M44818</guid>
      <dc:creator>Johan Guldmyr</dc:creator>
      <dc:date>2010-06-04T06:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642170#M44819</link>
      <description>There maybe another issue here.  You did not mention Command View (CV) version. If you are using CV 7.0 and higher you need a CV lic. If you don't have a service contract with HP you have to pay for it.&lt;BR /&gt;&lt;BR /&gt;CV 9.01 and higher is now the only HP supported version.</description>
      <pubDate>Fri, 04 Jun 2010 16:51:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642170#M44819</guid>
      <dc:creator>Clint Placette_2</dc:creator>
      <dc:date>2010-06-04T16:51:12Z</dc:date>
    </item>
    <item>
      <title>Re: EVA6000 moved disks 'Command View EVA has detected this array as inoperative'</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642171#M44820</link>
      <description>What your experinceing is what I call double vision.  Its the results of the MPIO driver not funtion properly.  As long as you don't select the other unmount driver you are ok for now.  &lt;BR /&gt;&lt;BR /&gt;What version of MPIO are you running.  You should have loaded FF DSM 4.0 and DSM MGR 4.1.  The MPIO can be found &lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&amp;amp;cc=us&amp;amp;prodNameId=421494&amp;amp;prodTypeId=18964&amp;amp;prodSeriesId=421492&amp;amp;swLang=13&amp;amp;taskId=135&amp;amp;swEnvOID=4064" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&amp;amp;cc=us&amp;amp;prodNameId=421494&amp;amp;prodTypeId=18964&amp;amp;prodSeriesId=421492&amp;amp;swLang=13&amp;amp;taskId=135&amp;amp;swEnvOID=4064&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Once loaded you can go to control panel find MPIO there should be a listing of HSV contollers if not something is wrong.&lt;BR /&gt;&lt;BR /&gt;Another thing you can try unload MPIO leave  only one fibre connected and then reload MPIO. &lt;BR /&gt;</description>
      <pubDate>Fri, 04 Jun 2010 18:27:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/eva6000-moved-disks-command-view-eva-has-detected-this-array-as/m-p/4642171#M44820</guid>
      <dc:creator>Clint Placette_2</dc:creator>
      <dc:date>2010-06-04T18:27:26Z</dc:date>
    </item>
  </channel>
</rss>

