<?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 How to find out the actual physical path of pv . EVA preformace issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099162#M600033</link>
    <description>Hi All:&lt;BR /&gt;To improve IO adn enlarge disk space, we replaced a va7000 with a EVA40000.but the improvement is not as we expected.&lt;BR /&gt;and #sar -d has some avwait &lt;BR /&gt;&lt;BR /&gt;sa$sar -d -f sa20080114.dat|more&lt;BR /&gt;device %busy  avque  r+w/s blks/s avwait avserv&lt;BR /&gt;c12t0d1 0.04  0.50    0     1      4.02   2.88&lt;BR /&gt;c12t0d2 86.03 0.59   864  5824     5.01   1.94&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HP-UX 11.11&lt;BR /&gt;2 SAN 4GB switchs&lt;BR /&gt;2 2GB HBA&lt;BR /&gt;2 VD in EVA4000&lt;BR /&gt;2 VG in LVM&lt;BR /&gt;2VGs are both using /dev/dsk/c12txdx as primary pv path now.&lt;BR /&gt;Since we don't have Secure Path.is there any way to find out the actual PV device's physical path? then I can change one of the VG's primary path to operate these 2 VGs though differente EVA controller to share controller's loading.&lt;BR /&gt;&lt;BR /&gt;OR , any other suggestion ? VD's prefer path of EVA ? any best practice of such case?&lt;BR /&gt;&lt;BR /&gt;vgeva02&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name /dev/dsk/c12t0d2&lt;BR /&gt;PV Name /dev/dsk/c13t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c20t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c21t0d2 Alternate Link&lt;BR /&gt;PV Status available &lt;BR /&gt;Total PE 3839 &lt;BR /&gt;Free PE 0 &lt;BR /&gt;Autoswitch On &lt;BR /&gt;&lt;BR /&gt;----------------&lt;BR /&gt;vgeva01&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name /dev/dsk/c12t0d1&lt;BR /&gt;PV Name /dev/dsk/c13t0d1 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c20t0d1 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c21t0d1 Alternate Link&lt;BR /&gt;PV Status available &lt;BR /&gt;Total PE 15357 &lt;BR /&gt;Free PE 2221 &lt;BR /&gt;Autoswitch On &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;----------------&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
    <pubDate>Sun, 23 Mar 2008 05:16:31 GMT</pubDate>
    <dc:creator>Nicholas Chang</dc:creator>
    <dc:date>2008-03-23T05:16:31Z</dc:date>
    <item>
      <title>How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099162#M600033</link>
      <description>Hi All:&lt;BR /&gt;To improve IO adn enlarge disk space, we replaced a va7000 with a EVA40000.but the improvement is not as we expected.&lt;BR /&gt;and #sar -d has some avwait &lt;BR /&gt;&lt;BR /&gt;sa$sar -d -f sa20080114.dat|more&lt;BR /&gt;device %busy  avque  r+w/s blks/s avwait avserv&lt;BR /&gt;c12t0d1 0.04  0.50    0     1      4.02   2.88&lt;BR /&gt;c12t0d2 86.03 0.59   864  5824     5.01   1.94&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HP-UX 11.11&lt;BR /&gt;2 SAN 4GB switchs&lt;BR /&gt;2 2GB HBA&lt;BR /&gt;2 VD in EVA4000&lt;BR /&gt;2 VG in LVM&lt;BR /&gt;2VGs are both using /dev/dsk/c12txdx as primary pv path now.&lt;BR /&gt;Since we don't have Secure Path.is there any way to find out the actual PV device's physical path? then I can change one of the VG's primary path to operate these 2 VGs though differente EVA controller to share controller's loading.&lt;BR /&gt;&lt;BR /&gt;OR , any other suggestion ? VD's prefer path of EVA ? any best practice of such case?&lt;BR /&gt;&lt;BR /&gt;vgeva02&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name /dev/dsk/c12t0d2&lt;BR /&gt;PV Name /dev/dsk/c13t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c20t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c21t0d2 Alternate Link&lt;BR /&gt;PV Status available &lt;BR /&gt;Total PE 3839 &lt;BR /&gt;Free PE 0 &lt;BR /&gt;Autoswitch On &lt;BR /&gt;&lt;BR /&gt;----------------&lt;BR /&gt;vgeva01&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name /dev/dsk/c12t0d1&lt;BR /&gt;PV Name /dev/dsk/c13t0d1 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c20t0d1 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c21t0d1 Alternate Link&lt;BR /&gt;PV Status available &lt;BR /&gt;Total PE 15357 &lt;BR /&gt;Free PE 2221 &lt;BR /&gt;Autoswitch On &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;----------------&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Sun, 23 Mar 2008 05:16:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099162#M600033</guid>
      <dc:creator>Nicholas Chang</dc:creator>
      <dc:date>2008-03-23T05:16:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099163#M600034</link>
      <description>&lt;BR /&gt;The diskname without "alternative link" in the "vgdisplay -v vgname" is the primary disk.&lt;BR /&gt;&lt;BR /&gt;To make it alternative , just remove the primary and then again extend vg with the removed one. this will make alternative as primary and the primary will be added as alternative.&lt;BR /&gt;&lt;BR /&gt;Can u pleae provide the disk size,&lt;BR /&gt;&lt;BR /&gt;#diskinfo &lt;DISK name=""&gt;&lt;/DISK&gt;</description>
      <pubDate>Sun, 23 Mar 2008 06:13:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099163#M600034</guid>
      <dc:creator>Siju Vadakkan</dc:creator>
      <dc:date>2008-03-23T06:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099164#M600035</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;what I' trying to verify is which one shoule be replaced with to be the new primary path? &lt;BR /&gt;The purpose is sharing loading.&lt;BR /&gt;&lt;BR /&gt;Ex: for the same VD in EVA ,if c12t0d1 is rp7410 HBA #1 to SAN switch #1 to EVA controller #1, then which path is rp7410 HBA #2 to SAN switch #2 to EVA controller #2?c13, c20 or c21?&lt;BR /&gt;&lt;BR /&gt;the PE size is 16MB&lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Sun, 23 Mar 2008 06:38:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099164#M600035</guid>
      <dc:creator>Nicholas Chang</dc:creator>
      <dc:date>2008-03-23T06:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099165#M600036</link>
      <description>Provide the following details: &lt;BR /&gt;&lt;BR /&gt;# ioscan -fnkC fc&lt;BR /&gt;#diskinfo /dev/rdsk/c12t0d1&lt;BR /&gt;</description>
      <pubDate>Sun, 23 Mar 2008 06:48:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099165#M600036</guid>
      <dc:creator>Siju Vadakkan</dc:creator>
      <dc:date>2008-03-23T06:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099166#M600037</link>
      <description>sorry , I can not access to the devices right now&lt;BR /&gt;&lt;BR /&gt;Do you mean I can track the connection form ioscan and diskinfo ?&lt;BR /&gt;&lt;BR /&gt;I'll post ASAP&lt;BR /&gt;&lt;BR /&gt;thanks a lot</description>
      <pubDate>Sun, 23 Mar 2008 07:45:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099166#M600037</guid>
      <dc:creator>Nicholas Chang</dc:creator>
      <dc:date>2008-03-23T07:45:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099167#M600038</link>
      <description>Increase scsi queuedepth of the implicated luns.&lt;BR /&gt;&lt;BR /&gt;And see if that will allow to push through more IOs per second. When you do the sar, always do sar -d 1 1000.&lt;BR /&gt;&lt;BR /&gt;Default scsi queuedepth on HP-UX equals to 8. (which is good to up to a 8Gbyte lun.) Youre c12t0d2 seems to be 64Gbyte, so scsi queuedepth of 64 should be better for this lun.&lt;BR /&gt;&lt;BR /&gt;Check man scsictl to check how to set the scsiqueuedepth on a lun.&lt;BR /&gt;&lt;BR /&gt;Then monitor the result, if it works, then you will also have to create a startupscript that makes sure that after every bootup the scsi queuedepth is set on the lun(s).</description>
      <pubDate>Sat, 29 Mar 2008 17:54:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099167#M600038</guid>
      <dc:creator>chris huys_4</dc:creator>
      <dc:date>2008-03-29T17:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099168#M600039</link>
      <description>Get some background data from these reports.  As there are several ways to look at this and they all provide unique information.&lt;BR /&gt;&lt;BR /&gt;Can you use 'ioscan -funC td' to find your HBAs.  They'll be listed like /dev/td0, td1, etc.  Then use 'fcmsutil /dev/td!' to find the WWN.  Each HBA will have its own WWN.  Also refer to the man page for additional arguements like 'stat'.&lt;BR /&gt;&lt;BR /&gt;Re: "...what I' trying to verify is which one shoule be replaced with to be the new primary path?  The purpose is sharing loading....".&lt;BR /&gt;&lt;BR /&gt;This is a round robin algorithm that  frequently comes up in the forum.  Using 'vgdisplay -v /dev/vg##' you can list out all of your PV, primary and alternate.  &lt;BR /&gt;&lt;BR /&gt;Since you state "...2VGs are both using /dev/dsk/c12txdx as primary pv path now...."....&lt;BR /&gt;&lt;BR /&gt;...then you will want to vgreduce /dev/vg02 /dev/dsk/c12t#d#....&lt;BR /&gt;&lt;BR /&gt;Now your alternate slide up to be the primary and you 'vgextend /dev/vg02/c13t#d#...".&lt;BR /&gt;&lt;BR /&gt;Here's what you have:&lt;BR /&gt;&lt;BR /&gt;vgeva02&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name /dev/dsk/c12t0d2&lt;BR /&gt;PV Name /dev/dsk/c13t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c20t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c21t0d2 Alternate Link&lt;BR /&gt;PV Status available &lt;BR /&gt;&lt;BR /&gt;Here's what you'll get:&lt;BR /&gt;&lt;BR /&gt;vgeva02&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name /dev/dsk/c13t0d2&lt;BR /&gt;PV Name /dev/dsk/c20t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c21t0d2 Alternate Link&lt;BR /&gt;PV Name /dev/dsk/c12t0d2 Alternate Link&lt;BR /&gt;PV Status available &lt;BR /&gt;&lt;BR /&gt;If trouble arise verify the PV with 'pvdisplay'.  Refer to the -S autoswitch arguement.&lt;BR /&gt;&lt;BR /&gt;"...y   LVM is directed to automatically switch from the path it is using whenever a better path to the physical volume is available. LVM will switch paths when a better path recovers (after it had failed earlier), or if the current path fails and another path is available. This is the default....&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-60130/pvchange.1M.html" target="_blank"&gt;http://docs.hp.com/en/B2355-60130/pvchange.1M.html&lt;/A&gt;</description>
      <pubDate>Sun, 30 Mar 2008 00:05:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099168#M600039</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2008-03-30T00:05:34Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099169#M600040</link>
      <description>thanks Michael:&lt;BR /&gt;&lt;BR /&gt;I know how to change primary path.&lt;BR /&gt;but ,why c13?  why not c20 or c21 ?&lt;BR /&gt;&lt;BR /&gt;my purpose is to access 2 VGs through 2 totaly seperate fibre path and controller of EVA.&lt;BR /&gt;&lt;BR /&gt;or is this  only my imagination , nothing good for my avwait problem &lt;BR /&gt;&lt;BR /&gt;And , I'll try to modify SCSI queue length.&lt;BR /&gt;&lt;BR /&gt;Thanks a lot</description>
      <pubDate>Mon, 31 Mar 2008 01:40:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099169#M600040</guid>
      <dc:creator>Nicholas Chang</dc:creator>
      <dc:date>2008-03-31T01:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099170#M600041</link>
      <description>Well of course you can vgreduce c20 or c21.  You can vgreduce up to three, maybe all four but I believe you have to keep at least one PV in the vg at all times.  Its been awhile since I removed all disks from a vg.&lt;BR /&gt;&lt;BR /&gt;vgreduce /dev/vg## /dev/dsk/c12 13 20 21&lt;BR /&gt;vgextend /dev/vg#3 /dev/dsk/c20 21 12 13</description>
      <pubDate>Mon, 31 Mar 2008 03:10:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099170#M600041</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2008-03-31T03:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099171#M600042</link>
      <description>thanks you all&lt;BR /&gt;&lt;BR /&gt;I found that I can trace from the sequece of ioscan -fnk output.&lt;BR /&gt;&lt;BR /&gt;c12 and c20 are through same HBA td0&lt;BR /&gt;c13 and c21 are throuth the other one td1&lt;BR /&gt;&lt;BR /&gt;thanks Siji , I wish I had given you more points, or you can post another reply. ^^&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;thanks again</description>
      <pubDate>Mon, 31 Mar 2008 05:05:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099171#M600042</guid>
      <dc:creator>Nicholas Chang</dc:creator>
      <dc:date>2008-03-31T05:05:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099172#M600043</link>
      <description>Nicolas,&lt;BR /&gt;&lt;BR /&gt;The levels of usage you are currently should barely tickle the capacity of a single connection or the EVA. Don't woory about using multiple paths untill you approach 1/2 of theoretical throughput for longer durations.&lt;BR /&gt;So with 2gb fiber, you might start to worry at 50MB/sec, that would be 100,000 blks/s and 10,000 r+w/s.&lt;BR /&gt;Some might not like 1/2. So pick 1/4... &lt;BR /&gt;You would still have 5x room for more.&lt;BR /&gt;&lt;BR /&gt;Chris&amp;gt;&amp;gt; Increase scsi queuedepth of the implicated luns.&lt;BR /&gt;&lt;BR /&gt;Yes, it looks ( avwait -versus- avserv )like the throughput is constricted due to this artificial limit.&lt;BR /&gt;&lt;BR /&gt;Chris&amp;gt;&amp;gt; Default scsi queuedepth on HP-UX equals to 8. (which is good to up to a 8Gbyte lun.) Youre c12t0d2 seems to be 64Gbyte, so scsi queuedepth of 64 should be better for this lun.&lt;BR /&gt;&lt;BR /&gt;Good point, BAD explanation.&lt;BR /&gt;The desirable queue depth has absolutely nothing, zero, nada, to do with the lun size. &lt;BR /&gt;&lt;BR /&gt;On of the most important factor the queue depth is the number of spindles behind the LUN presented by a controller like an EVA.&lt;BR /&gt;You should allow for at least one per spindle, more than 2 per spindle is unlikely to help much more.&lt;BR /&gt;&lt;BR /&gt;Hope this helps some,&lt;BR /&gt;Hein van den Heuvel (at gmail dot com)&lt;BR /&gt;HvdH Performance Consulting&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Mar 2008 11:48:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099172#M600043</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2008-03-31T11:48:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099173#M600044</link>
      <description>Thanks Pharaoh&lt;BR /&gt;&lt;BR /&gt;very clear explaination&lt;BR /&gt;&lt;BR /&gt;this is what I wat to know&lt;BR /&gt;&lt;BR /&gt;thanks again</description>
      <pubDate>Tue, 01 Apr 2008 02:57:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099173#M600044</guid>
      <dc:creator>Nicholas Chang</dc:creator>
      <dc:date>2008-04-01T02:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to find out the actual physical path of pv . EVA preformace issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099174#M600045</link>
      <description>^_^</description>
      <pubDate>Tue, 01 Apr 2008 02:58:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-find-out-the-actual-physical-path-of-pv-eva-preformace/m-p/5099174#M600045</guid>
      <dc:creator>Nicholas Chang</dc:creator>
      <dc:date>2008-04-01T02:58:06Z</dc:date>
    </item>
  </channel>
</rss>

