<?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 4100 controller mastership in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985600#M4084</link>
    <description>What operating systems are involved? It sounds like you have a non-consistent I/O access - maybe a different cabeling and/or non-optimized multipath setting.</description>
    <pubDate>Fri, 08 Aug 2008 07:08:26 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2008-08-08T07:08:26Z</dc:date>
    <item>
      <title>EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985599#M4083</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
We have in our EVA4100 the continuous change of controller mastership, day in day out, every X hours; is it caused by the battery? &lt;BR /&gt;
see logs, at the end battery logging&lt;BR /&gt;
&lt;BR /&gt;
Rik&lt;BR /&gt;
&lt;BR /&gt;
      07:34:38:865&lt;BR /&gt;
8-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3629 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
07:34:38:391&lt;BR /&gt;
8-Aug-2008&lt;BR /&gt;
Controller A  4207001b #3628 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
04:34:24:987&lt;BR /&gt;
8-Aug-2008&lt;BR /&gt;
Controller A  04130003 #3627 &lt;BR /&gt;
Storage System event reporting is still active.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
16:34:24:564&lt;BR /&gt;
7-Aug-2008&lt;BR /&gt;
Controller A  04130003 #3626 &lt;BR /&gt;
Storage System event reporting is still active.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
04:34:24:069&lt;BR /&gt;
7-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3625 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
04:34:23:455&lt;BR /&gt;
7-Aug-2008&lt;BR /&gt;
Controller A  4207001b #3624 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
23:34:18:920&lt;BR /&gt;
6-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3623 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
23:34:05:939&lt;BR /&gt;
6-Aug-2008&lt;BR /&gt;
Controller B  4207001b #3622 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
20:34:14:839&lt;BR /&gt;
6-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3621 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
20:34:01:850&lt;BR /&gt;
6-Aug-2008&lt;BR /&gt;
Controller B  4207001b #3620 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
12:33:55:803&lt;BR /&gt;
6-Aug-2008&lt;BR /&gt;
Controller A  04130003 #3619 &lt;BR /&gt;
Storage System event reporting is still active.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
00:33:55:338&lt;BR /&gt;
6-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3618 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
00:33:54:475&lt;BR /&gt;
6-Aug-2008&lt;BR /&gt;
Controller A  4207001b #3617 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
13:33:42:706&lt;BR /&gt;
5-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3616 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
13:33:42:098&lt;BR /&gt;
5-Aug-2008&lt;BR /&gt;
Controller A  4207001b #3615 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
03:33:33:433&lt;BR /&gt;
5-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3614 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
03:33:20:616&lt;BR /&gt;
5-Aug-2008&lt;BR /&gt;
Controller B  4207001b #3613 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
17:33:10:007&lt;BR /&gt;
4-Aug-2008&lt;BR /&gt;
Controller A  04130003 #3612 &lt;BR /&gt;
Storage System event reporting is still active.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
05:33:09:574&lt;BR /&gt;
4-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3611 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
05:32:56:943&lt;BR /&gt;
4-Aug-2008&lt;BR /&gt;
Controller B  4207001b #3610 &lt;BR /&gt;
Indicated Virtual Disk has transitioned to ownership by the other HSV200 controller.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
02:52:31:526&lt;BR /&gt;
4-Aug-2008&lt;BR /&gt;
Controller A  0e030019 #3609 &lt;BR /&gt;
The status of battery assembly '0' has changed.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
02:47:12:187&lt;BR /&gt;
4-Aug-2008&lt;BR /&gt;
Controller A  0e030019 #3608 &lt;BR /&gt;
The status of battery assembly '0' has changed.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
02:33:06:635&lt;BR /&gt;
4-Aug-2008&lt;BR /&gt;
Controller A  0310001f #3607 &lt;BR /&gt;
A Storage System Virtual Disk has changed controller mastership.&lt;BR /&gt;
Corrective action code: 00 More details &lt;BR /&gt;
 &lt;BR /&gt;
 &lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2008 06:53:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985599#M4083</guid>
      <dc:creator>Rik-Bel</dc:creator>
      <dc:date>2008-08-08T06:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985600#M4084</link>
      <description>What operating systems are involved? It sounds like you have a non-consistent I/O access - maybe a different cabeling and/or non-optimized multipath setting.</description>
      <pubDate>Fri, 08 Aug 2008 07:08:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985600#M4084</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-08-08T07:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985601#M4085</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have 2 W2k3 and 4 ESX 3.0x, how start troubleshoot this ? The status of the battery assy ?&lt;BR /&gt;&lt;BR /&gt;Rik</description>
      <pubDate>Fri, 08 Aug 2008 07:16:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985601#M4085</guid>
      <dc:creator>Rik-Bel</dc:creator>
      <dc:date>2008-08-08T07:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985602#M4086</link>
      <description>&amp;gt; The status of the battery assy ?&lt;BR /&gt;&lt;BR /&gt;A CAC value of 0 means that no action is necessary. It is just an informational message.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;You will have to do a traffic analysis to find out which server(s) are causing the ownership transfers.&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2008 07:29:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985602#M4086</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-08-08T07:29:48Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985603#M4087</link>
      <description>How can this be done ?</description>
      <pubDate>Fri, 08 Aug 2008 07:41:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985603#M4087</guid>
      <dc:creator>Rik-Bel</dc:creator>
      <dc:date>2008-08-08T07:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985604#M4088</link>
      <description>You need full documentation about the infrastructure (e.g. which adapter port goes to which switch port and has connectivity to which controller ports).&lt;BR /&gt;&lt;BR /&gt;From there you need to find out which hosts are causing traffic to the virtual disks which results in ownership transfers. The tools are the Fibre Channel switch performance monitor and the EVAperf utility.</description>
      <pubDate>Fri, 08 Aug 2008 07:49:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985604#M4088</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2008-08-08T07:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985605#M4089</link>
      <description>Thanks, I'll do this.</description>
      <pubDate>Fri, 08 Aug 2008 08:01:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985605#M4089</guid>
      <dc:creator>Rik-Bel</dc:creator>
      <dc:date>2008-08-08T08:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985606#M4090</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The eva perf let me see the usage and statistics but why it will change mastership is not obvious, the usage i divided over the 2 contollers because i divided the lun presentation over the 2 controllers manually.&lt;BR /&gt;&lt;BR /&gt;Rik</description>
      <pubDate>Mon, 11 Aug 2008 11:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985606#M4090</guid>
      <dc:creator>Rik-Bel</dc:creator>
      <dc:date>2008-08-11T11:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985607#M4091</link>
      <description>More than likely, your VMFS pathing is not configured correctly.&lt;BR /&gt;&lt;BR /&gt;With EVA, the default is FIXED, with a single ACTIVE path.  &lt;BR /&gt;&lt;BR /&gt;Make sure the PREFERRED ACTIVE path of each VMFS volume, ON EACH HOST, is configured to use the same storage controller!&lt;BR /&gt;&lt;BR /&gt;Multiple ESX hosts access the same VMFS volumes.  So, if you have multiple VMs on a VMFS volume, and the VMs are running on a different ESX hosts, and the VMFS volume is configured with different paths on your hosts, each time a read/write operation is performed the Vdisk will transfer ownership.&lt;BR /&gt;&lt;BR /&gt;For each VMFS on each host, choose the same preferred path.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 31 Aug 2008 02:24:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985607#M4091</guid>
      <dc:creator>Paul .</dc:creator>
      <dc:date>2008-08-31T02:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4100 controller mastership</title>
      <link>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985608#M4092</link>
      <description>Very late Comment:&lt;BR /&gt;&lt;BR /&gt;Could this be a scheduled battery load test log ?</description>
      <pubDate>Wed, 25 Feb 2009 02:20:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/eva-4100-controller-mastership/m-p/985608#M4092</guid>
      <dc:creator>georgemad</dc:creator>
      <dc:date>2009-02-25T02:20:44Z</dc:date>
    </item>
  </channel>
</rss>

