<?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 Cluster Extension for windows (Clx) in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/cluster-extension-for-windows-clx/m-p/4700514#M46494</link>
    <description>Dear all.... I have recently had to change the Ip address of the storage management server looking after 2 x EVA4400.  We have several windows clusters (WS2k3) utilising the Clx cluster resource based CA replication.  I have started to reconfigure the Clx cluster resources within the various virtual servers and getting the error in the attachment.  Any clues?</description>
    <pubDate>Sun, 17 Oct 2010 18:57:09 GMT</pubDate>
    <dc:creator>Dja_1</dc:creator>
    <dc:date>2010-10-17T18:57:09Z</dc:date>
    <item>
      <title>Cluster Extension for windows (Clx)</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/cluster-extension-for-windows-clx/m-p/4700514#M46494</link>
      <description>Dear all.... I have recently had to change the Ip address of the storage management server looking after 2 x EVA4400.  We have several windows clusters (WS2k3) utilising the Clx cluster resource based CA replication.  I have started to reconfigure the Clx cluster resources within the various virtual servers and getting the error in the attachment.  Any clues?</description>
      <pubDate>Sun, 17 Oct 2010 18:57:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/cluster-extension-for-windows-clx/m-p/4700514#M46494</guid>
      <dc:creator>Dja_1</dc:creator>
      <dc:date>2010-10-17T18:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Extension for windows (Clx)</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/cluster-extension-for-windows-clx/m-p/4700515#M46495</link>
      <description>"...Make sure that one EVA management server is actively managing both the arrays."&lt;BR /&gt;&lt;BR /&gt;So is it? When you browse to the Command View for EVA interface, do you correctly see both EVA arrays? Click on each EVA and drill down to something like the replication information.</description>
      <pubDate>Mon, 18 Oct 2010 13:11:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/cluster-extension-for-windows-clx/m-p/4700515#M46495</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2010-10-18T13:11:54Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Extension for windows (Clx)</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/cluster-extension-for-windows-clx/m-p/4700516#M46496</link>
      <description>Yes the sms is defintely managing both arrays.  Incidentally I get a similiar error when attempting to create  a new Clx resource.  The behaviour is the same on all clusters.</description>
      <pubDate>Mon, 18 Oct 2010 17:40:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/cluster-extension-for-windows-clx/m-p/4700516#M46496</guid>
      <dc:creator>Dja_1</dc:creator>
      <dc:date>2010-10-18T17:40:57Z</dc:date>
    </item>
  </channel>
</rss>

