<?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 command view software in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/command-view-software/m-p/2585955#M126</link>
    <description>We have Command View Software (Single Node Version), currently installed on the system, It all works correctly as do the arm commands and we can talk to and configure the VA7400 but we would like to move the software to another system within the SAN.&lt;BR /&gt;&lt;BR /&gt;After loading the software on to a different system within the cluster, and then turning of the old system with the command view software on we are unable to access the VA7400. It looks as though the VA7400 holds a file or some form of id of the host, can this be changed.&lt;BR /&gt;&lt;BR /&gt;The software needs to be moved to be part of a cluster with the ultimate aim of having the software fail-over within the cluster. I don?t know whether this is feasible or not.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
    <pubDate>Thu, 27 Sep 2001 12:53:48 GMT</pubDate>
    <dc:creator>Mark Jones_1</dc:creator>
    <dc:date>2001-09-27T12:53:48Z</dc:date>
    <item>
      <title>command view software</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/command-view-software/m-p/2585955#M126</link>
      <description>We have Command View Software (Single Node Version), currently installed on the system, It all works correctly as do the arm commands and we can talk to and configure the VA7400 but we would like to move the software to another system within the SAN.&lt;BR /&gt;&lt;BR /&gt;After loading the software on to a different system within the cluster, and then turning of the old system with the command view software on we are unable to access the VA7400. It looks as though the VA7400 holds a file or some form of id of the host, can this be changed.&lt;BR /&gt;&lt;BR /&gt;The software needs to be moved to be part of a cluster with the ultimate aim of having the software fail-over within the cluster. I don?t know whether this is feasible or not.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Thu, 27 Sep 2001 12:53:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/command-view-software/m-p/2585955#M126</guid>
      <dc:creator>Mark Jones_1</dc:creator>
      <dc:date>2001-09-27T12:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: command view software</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/command-view-software/m-p/2585956#M127</link>
      <description>You have to buy another licence for second cluster node. HP requires that, even if both copies will never run simultanosly. (HP licences software per host, not per user.)</description>
      <pubDate>Sat, 29 Sep 2001 10:12:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/command-view-software/m-p/2585956#M127</guid>
      <dc:creator>Enes Dizdarevic</dc:creator>
      <dc:date>2001-09-29T10:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: command view software</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/command-view-software/m-p/2585957#M128</link>
      <description>Are you using Secure Manager?  Do both hosts have access to at least LUN 0 on tha VA?&lt;BR /&gt;&lt;BR /&gt;FYI the part number for CV SDM is T1001A for a 1 host LTU.  I'm not so sure that you need two copies, however.  It can only run on one at a time (the array can have only one manager), and a license comes with every VA.</description>
      <pubDate>Sat, 29 Sep 2001 12:47:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/command-view-software/m-p/2585957#M128</guid>
      <dc:creator>Vincent Fleming</dc:creator>
      <dc:date>2001-09-29T12:47:39Z</dc:date>
    </item>
  </channel>
</rss>

