<?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: EVA 5000 CV-EVA problem in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921409#M39129</link>
    <description>Did the complete shutdown of SMS box.&lt;BR /&gt;But same error while creating Vdisk in DG1&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 26 Aug 2005 17:27:28 GMT</pubDate>
    <dc:creator>rccmum</dc:creator>
    <dc:date>2005-08-26T17:27:28Z</dc:date>
    <item>
      <title>EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921404#M39124</link>
      <description>Guys,&lt;BR /&gt;&lt;BR /&gt;We have one prodution EVA 5000 ( 2C6D ) with 56 disks VCS 3025 CV-EVA 3.3 BC 2.3, 2 DGs ( 1DG- 40, 2DG- 16 disks)&lt;BR /&gt;&lt;BR /&gt;We were trying to add new Vdisks in DG1 using CV-EVA . First time it gave error as Storage System is not initialized!!!!&lt;BR /&gt;But the EVA is showing operational state as Good ( initilised ).&lt;BR /&gt;We could able to add 2 Vdisks successfully after waiting for some time. We are trying to add more Vdisk, but it is not going through giving the above error again. We are selecting &lt;BR /&gt;Vraid1 and path a &amp;amp; b alternatly as preferred mode.&lt;BR /&gt;We could able to add Vdisks to DG2 though.&lt;BR /&gt;&lt;BR /&gt;We are not sure whats wrong with EVA as it is not allowing to add new Vdisks in DG1.&lt;BR /&gt;&lt;BR /&gt;Early replies would be appretiated.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Aug 2005 13:52:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921404#M39124</guid>
      <dc:creator>rccmum</dc:creator>
      <dc:date>2005-08-26T13:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921405#M39125</link>
      <description>The RSS state of DG1 is None . We guess is this a cause of not able to add Vdisk  to DG1. Are we right?&lt;BR /&gt;If yes, can anyone tell the resolution of the same&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Aug 2005 14:31:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921405#M39125</guid>
      <dc:creator>rccmum</dc:creator>
      <dc:date>2005-08-26T14:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921406#M39126</link>
      <description>Did you restarted the CV service?&lt;BR /&gt;&lt;BR /&gt;Most times the restart of the service "refresh" the display if you are getting errors.&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Aug 2005 15:20:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921406#M39126</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-08-26T15:20:42Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921407#M39127</link>
      <description>No we didn't restart the CV service ?&lt;BR /&gt;How do I do that ? &lt;BR /&gt;Can we do it in production environment?&lt;BR /&gt;Our EVA is in production now..&lt;BR /&gt;&lt;BR /&gt;Are you sure it will resolve the issue becuase we can add Vdisks to other grpup DG2.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Aug 2005 16:05:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921407#M39127</guid>
      <dc:creator>rccmum</dc:creator>
      <dc:date>2005-08-26T16:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921408#M39128</link>
      <description>You can safely restart the service in production, it does not affect the EVA.&lt;BR /&gt;&lt;BR /&gt;To do that, it depends if you are using an SMA or a Management server.&lt;BR /&gt;&lt;BR /&gt;On SMA, logon using the web browsers, settings, manage toosl, select CV and stop and start.&lt;BR /&gt;&lt;BR /&gt;On Management server, use My Computer, then services, and restart CV service.&lt;BR /&gt;&lt;BR /&gt;But i'm not sure if this will solve the problem, but is the first thing you should do.</description>
      <pubDate>Fri, 26 Aug 2005 16:47:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921408#M39128</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-08-26T16:47:02Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921409#M39129</link>
      <description>Did the complete shutdown of SMS box.&lt;BR /&gt;But same error while creating Vdisk in DG1&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Aug 2005 17:27:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921409#M39129</guid>
      <dc:creator>rccmum</dc:creator>
      <dc:date>2005-08-26T17:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921410#M39130</link>
      <description>An RSS state of 'none' should not prevent proper communication with the storage array nor the creation of additional Vdisks.&lt;BR /&gt;&lt;BR /&gt;I would first upgrade CV-EVA V3.3 to V3.3.4:&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=434214&amp;amp;locale=en_US&amp;amp;taskId=135&amp;amp;prodSeriesId=435210&amp;amp;prodTypeId=12169&amp;amp;swEnvOID=181" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=434214&amp;amp;locale=en_US&amp;amp;taskId=135&amp;amp;prodSeriesId=435210&amp;amp;prodTypeId=12169&amp;amp;swEnvOID=181&lt;/A&gt;</description>
      <pubDate>Sat, 27 Aug 2005 13:46:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921410#M39130</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-08-27T13:46:09Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921411#M39131</link>
      <description>The CV-EVA version is 4.0 not 3.3.&lt;BR /&gt;&lt;BR /&gt;The issue seems to be very peculier as it is happening intermittently. We were suspecting the HBA installed in SMS  But it seems to be working fine as we could able to see all details on CV GUI normally. &lt;BR /&gt;&lt;BR /&gt;It seems that the DG1 infomation on the EVA metadeta is not being communicated by CV properly. We tried to create Vdisks in DG2 , it works fine.&lt;BR /&gt;&lt;BR /&gt;We feel the EVA is OK .Something is wrong with CV or with SMS but not sure though&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 27 Aug 2005 14:32:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921411#M39131</guid>
      <dc:creator>rccmum</dc:creator>
      <dc:date>2005-08-27T14:32:15Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921412#M39132</link>
      <description>One of the controllers is not in a proper state. If you reset one controller. (preferably the slave) and wait for a couple of minutes it should work fine. The remark of Uwe is also important, upgrade CVEVA to at least 3.3.3. The 4.x versions are mostly for the 4/6/8K arrays.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;Erwin van Londen&lt;BR /&gt;HP Master ASE SAN Architect.</description>
      <pubDate>Tue, 30 Aug 2005 07:09:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921412#M39132</guid>
      <dc:creator>Erwin van Londen</dc:creator>
      <dc:date>2005-08-30T07:09:04Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 5000 CV-EVA problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921413#M39133</link>
      <description>Thanks</description>
      <pubDate>Fri, 19 May 2006 17:45:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-5000-cv-eva-problem/m-p/4921413#M39133</guid>
      <dc:creator>rccmum</dc:creator>
      <dc:date>2006-05-19T17:45:52Z</dc:date>
    </item>
  </channel>
</rss>

