<?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 3000 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916257#M22503</link>
    <description>Hi, just press OK and you should get through and be able to manage the EVA.&lt;BR /&gt;&lt;BR /&gt;If another Command View is using the same EVA in the future, they will get the same message, and they will need to press OK.&lt;BR /&gt;&lt;BR /&gt;You see the IP in there, that is the other command view that is managing the EVA.</description>
    <pubDate>Tue, 05 Apr 2011 10:21:58 GMT</pubDate>
    <dc:creator>Johan Guldmyr</dc:creator>
    <dc:date>2011-04-05T10:21:58Z</dc:date>
    <item>
      <title>EVA 3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916253#M22499</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am getting following error when opened EVA management command view.&lt;BR /&gt;Another management agent on appliance SMAM01NFK353T at IP address may be actively managing this storage system. (System name: EVA3K).&lt;BR /&gt;&lt;BR /&gt;Only one agent is allowed to manage a system at a time. &lt;BR /&gt;&lt;BR /&gt;Version 2 management agents must be removed from the configuration for 15 minutes to ensure that management has ended. After removing a Version 2 management agent and waiting 15 minutes, click the OK button to continue. &lt;BR /&gt;&lt;BR /&gt;To disable Version 3 management agents, simply click the OK button and management will be redirected to this agent. &lt;BR /&gt;&lt;BR /&gt;How to solve this problem ?&lt;BR /&gt;&lt;BR /&gt;Please help me.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Sujeet</description>
      <pubDate>Thu, 21 Dec 2006 04:46:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916253#M22499</guid>
      <dc:creator>sujeet joshi</dc:creator>
      <dc:date>2006-12-21T04:46:27Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916254#M22500</link>
      <description>Check the IP Address and ensure no-one else is running Command View. &lt;BR /&gt;&lt;BR /&gt;You should be able to regain control use of the eva by pressing ok.&lt;BR /&gt;&lt;BR /&gt;What happens when you do ?&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;</description>
      <pubDate>Thu, 21 Dec 2006 05:48:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916254#M22500</guid>
      <dc:creator>gstonian</dc:creator>
      <dc:date>2006-12-21T05:48:04Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916255#M22501</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I'd suggest after the prior post to have a short downtime and reset the EVA. Either some other box is using the IP address or the management agent software has been run twice and a reset of the system will fix it.&lt;BR /&gt;&lt;BR /&gt;A rest of the EVA system includes the DL class system that usually controls the storage.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 21 Dec 2006 07:56:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916255#M22501</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-12-21T07:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916256#M22502</link>
      <description>Hi folks,&lt;BR /&gt;&lt;BR /&gt;i would like to know if this problem was solved, because i have same error and i don't know how to solve. Should i press OK and problem will be solved? Should reset solve the problem?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Thank you in advance</description>
      <pubDate>Mon, 04 Apr 2011 08:07:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916256#M22502</guid>
      <dc:creator>Victor Saelices Torres</dc:creator>
      <dc:date>2011-04-04T08:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916257#M22503</link>
      <description>Hi, just press OK and you should get through and be able to manage the EVA.&lt;BR /&gt;&lt;BR /&gt;If another Command View is using the same EVA in the future, they will get the same message, and they will need to press OK.&lt;BR /&gt;&lt;BR /&gt;You see the IP in there, that is the other command view that is managing the EVA.</description>
      <pubDate>Tue, 05 Apr 2011 10:21:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916257#M22503</guid>
      <dc:creator>Johan Guldmyr</dc:creator>
      <dc:date>2011-04-05T10:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916258#M22504</link>
      <description>Correct, just press OK.&lt;BR /&gt;&lt;BR /&gt;But let's make it clear: this is not a "problem".&lt;BR /&gt;This is how the EVA/CV-EVA works to restrict management to one active CV-EVA instance.</description>
      <pubDate>Wed, 06 Apr 2011 06:33:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-3000/m-p/3916258#M22504</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2011-04-06T06:33:33Z</dc:date>
    </item>
  </channel>
</rss>

