<?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: EVA4000 performance path in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696694#M18883</link>
    <description>yes it is active on both, however, there should still be a "primary" or "owning" controller which provides the best performance for the respective vdisk.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhard</description>
    <pubDate>Thu, 22 Dec 2005 10:19:14 GMT</pubDate>
    <dc:creator>Bernhard Mueller</dc:creator>
    <dc:date>2005-12-22T10:19:14Z</dc:date>
    <item>
      <title>EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696689#M18878</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;how can I find out (as quick as possible) which controller currently owns a certain vdisk of an EVA4K?&lt;BR /&gt;&lt;BR /&gt;Explanation: server is HP-UX using pvlinks, would like to make sure all vdisks are on performance path.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhard</description>
      <pubDate>Thu, 22 Dec 2005 07:06:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696689#M18878</guid>
      <dc:creator>Bernhard Mueller</dc:creator>
      <dc:date>2005-12-22T07:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696690#M18879</link>
      <description>C:\Program Files\Hewlett-Packard\EVA Performance Monitor&amp;gt;evaperf vd&lt;BR /&gt;&lt;BR /&gt;In the "Online To" column.</description>
      <pubDate>Thu, 22 Dec 2005 07:49:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696690#M18879</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-12-22T07:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696691#M18880</link>
      <description>You have to use evaperf. But by default, the VDISK WWID is printed, not the VDISK name. You must create a file called fnames.conf to make the conversion. (See command view user guide).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Dec 2005 08:06:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696691#M18880</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-12-22T08:06:17Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696692#M18881</link>
      <description>thanks for your help,&lt;BR /&gt;&lt;BR /&gt;can I manually "move" vdisk, i.e. assign it to the other controller?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhard</description>
      <pubDate>Thu, 22 Dec 2005 09:15:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696692#M18881</guid>
      <dc:creator>Bernhard Mueller</dc:creator>
      <dc:date>2005-12-22T09:15:01Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696693#M18882</link>
      <description>I could be mistaken, but I thought the EVA 4/6/8 were active/active.  When I do an evaperf vd it shows the vdisk connected to both controllers.</description>
      <pubDate>Thu, 22 Dec 2005 09:58:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696693#M18882</guid>
      <dc:creator>NathanK</dc:creator>
      <dc:date>2005-12-22T09:58:17Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696694#M18883</link>
      <description>yes it is active on both, however, there should still be a "primary" or "owning" controller which provides the best performance for the respective vdisk.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhard</description>
      <pubDate>Thu, 22 Dec 2005 10:19:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696694#M18883</guid>
      <dc:creator>Bernhard Mueller</dc:creator>
      <dc:date>2005-12-22T10:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696695#M18884</link>
      <description>I haven't tried it on the EVA XL yet, but on the first generation EVAs I was able to change the preferred path in CV-EVA and a scan from the server (WWIDMGR on AlphaServer) did show that the change had happened.</description>
      <pubDate>Thu, 22 Dec 2005 13:26:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696695#M18884</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-12-22T13:26:38Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696696#M18885</link>
      <description>What should be the best performance path setting on EVA4K?&lt;BR /&gt;We used the default setting for every VD, but the read hit ratio was too slow. Most of all the  read requests were missed from the controller cache.&lt;BR /&gt;How we could tune the EVA4K performance ?&lt;BR /&gt;Who can help me? &lt;BR /&gt;Thanks a lot.</description>
      <pubDate>Tue, 10 Oct 2006 03:32:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696696#M18885</guid>
      <dc:creator>sdbs</dc:creator>
      <dc:date>2006-10-10T03:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696697#M18886</link>
      <description>&lt;BR /&gt;The cache hit rate itself shouldn't depend on the LUN owning controller. &lt;BR /&gt;&lt;BR /&gt;Are you using evaperf to determine your cache hit rate?</description>
      <pubDate>Tue, 10 Oct 2006 14:05:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696697#M18886</guid>
      <dc:creator>Tom O'Toole</dc:creator>
      <dc:date>2006-10-10T14:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000 performance path</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696698#M18887</link>
      <description>Yes! I got the performance raw data by evaperf utility.&lt;BR /&gt;&lt;BR /&gt;And we used 16 * 146GB 10K-rpm FC disks in two disk shelves.&lt;BR /&gt;Just create only one disk group.&lt;BR /&gt;Without DR and snapshot.</description>
      <pubDate>Tue, 10 Oct 2006 20:07:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva4000-performance-path/m-p/3696698#M18887</guid>
      <dc:creator>sdbs</dc:creator>
      <dc:date>2006-10-10T20:07:43Z</dc:date>
    </item>
  </channel>
</rss>

