<?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 eva / switch / lvol / filesystem question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034415#M301952</link>
    <description>Group, need some understanding.&lt;BR /&gt;&lt;BR /&gt;Both of my fibre switches rebooted Sunday morning (firmware issue that I'm addressing).  This looks to have caused some time where neither path to the array was available to the system.  However, I saw no consequences from a database or application standpoint, i.e. they both kept working as if nothing happened.  Is this dependent on the PV timeout value?  If so, mine is set to default which I believe is 30 seconds.  You can see from below that technically  the lun was dead for just under two minutes.  I'm trying to figure out why I didn't have any filesystem and therefore db or app problems.&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:10:04 sys1 vmunix: CPQswsp:       Path c5t0d1 Failed (LUN 600508B4001023BC0000900000600000 Controller P66C5E2AAQT016 Array 50001FE1500463F0 HBA td0)&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:10:05 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Reduced&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:06 sys1 vmunix: CPQswsp:       Path c15t0d1 Failed (LUN 600508B4001023BC0000900000600000 Controller P66C5E2AAQT016 Array 50001FE1500463F0 HBA td1)&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:06 sys1 vmunix: WARNING: CPQswsp:      All paths for Target/LUN 0/1 (WWID=600508B4001023BC0000900000600000) on Controller P66C5E2AAQT016 failed&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:07 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Critical&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:13 sys1 vmunix: WARNING: CPQswsp:      Availability for LUN 600508B4001023BC0000900000600000 changed to Dead&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:14:05 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Reduced&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:16:10 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Alive&lt;BR /&gt;&lt;BR /&gt;I appreciate any thoughts or comments</description>
    <pubDate>Mon, 09 Jul 2007 13:48:28 GMT</pubDate>
    <dc:creator>Charles McCary</dc:creator>
    <dc:date>2007-07-09T13:48:28Z</dc:date>
    <item>
      <title>eva / switch / lvol / filesystem question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034415#M301952</link>
      <description>Group, need some understanding.&lt;BR /&gt;&lt;BR /&gt;Both of my fibre switches rebooted Sunday morning (firmware issue that I'm addressing).  This looks to have caused some time where neither path to the array was available to the system.  However, I saw no consequences from a database or application standpoint, i.e. they both kept working as if nothing happened.  Is this dependent on the PV timeout value?  If so, mine is set to default which I believe is 30 seconds.  You can see from below that technically  the lun was dead for just under two minutes.  I'm trying to figure out why I didn't have any filesystem and therefore db or app problems.&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:10:04 sys1 vmunix: CPQswsp:       Path c5t0d1 Failed (LUN 600508B4001023BC0000900000600000 Controller P66C5E2AAQT016 Array 50001FE1500463F0 HBA td0)&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:10:05 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Reduced&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:06 sys1 vmunix: CPQswsp:       Path c15t0d1 Failed (LUN 600508B4001023BC0000900000600000 Controller P66C5E2AAQT016 Array 50001FE1500463F0 HBA td1)&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:06 sys1 vmunix: WARNING: CPQswsp:      All paths for Target/LUN 0/1 (WWID=600508B4001023BC0000900000600000) on Controller P66C5E2AAQT016 failed&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:07 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Critical&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:12:13 sys1 vmunix: WARNING: CPQswsp:      Availability for LUN 600508B4001023BC0000900000600000 changed to Dead&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:14:05 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Reduced&lt;BR /&gt;&lt;BR /&gt;Jul  8 01:16:10 sys1 vmunix: CPQswsp:       Availability for LUN 600508B4001023BC0000900000600000 changed to Alive&lt;BR /&gt;&lt;BR /&gt;I appreciate any thoughts or comments</description>
      <pubDate>Mon, 09 Jul 2007 13:48:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034415#M301952</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2007-07-09T13:48:28Z</dc:date>
    </item>
    <item>
      <title>Re: eva / switch / lvol / filesystem question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034416#M301953</link>
      <description>If a path fails, the system waits for timeout (30~90 sec are usual), then the system will use the next alternate path.&lt;BR /&gt;But your output looks like securepath is in use. The behaviour is the same here, more or less.</description>
      <pubDate>Mon, 09 Jul 2007 14:04:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034416#M301953</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2007-07-09T14:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: eva / switch / lvol / filesystem question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034417#M301954</link>
      <description>securepath is in use.  &lt;BR /&gt;&lt;BR /&gt;I'm just wondering how the timeout didn't kick in during the timeperiod above where the LUN was marked as Dead (1:12:13) to when it was changed back to Reduced (1:14:05), which is 114 seconds.&lt;BR /&gt;&lt;BR /&gt;What should have occured here?  I would assume that at the very least, the database would have generated something in the alert log, but that didn't happen.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Jul 2007 14:10:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034417#M301954</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2007-07-09T14:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: eva / switch / lvol / filesystem question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034418#M301955</link>
      <description>I can't point to why, but I can share my experiences. Most of my array failures have been due to hardware on VA7410's, so I've seen a lot of them.&lt;BR /&gt;&lt;BR /&gt;By and large, in my experience, HP-UX boxes, when the device shows as NOHW (ioscan -fnC disk) during a failure, just won't finish the read or write operations that are pending. It waits.&lt;BR /&gt;&lt;BR /&gt;I've had periods of up to 12 hours where Oracle Financials on Oracle 10g2 sat with all associated LUNs stuck as NOHW, and when it came back, the database continued on as if nothing happened. It's when you reboot in the middle that there's a serious problem, because what's stuck in the cache didn't get written out to the logs.&lt;BR /&gt;&lt;BR /&gt;Now, this isn't always going to be true, but if the data is stable on the disk, it's been okay from what I've seen.&lt;BR /&gt;&lt;BR /&gt;A call to backline support might answer the WHY better.</description>
      <pubDate>Tue, 10 Jul 2007 06:39:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034418#M301955</guid>
      <dc:creator>Don Mallory</dc:creator>
      <dc:date>2007-07-10T06:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: eva / switch / lvol / filesystem question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034419#M301956</link>
      <description>Thanks for sharing the info.  This explains what could have occured (I feel marginally better anyway).&lt;BR /&gt;&lt;BR /&gt;I of course opened a ticket when all of this occured.  Originally thought we had an issue with a controller on the EVA.   I asked the question of the folks on the storage team and they didn't have a good answer (redundant paths was their best effort).&lt;BR /&gt;&lt;BR /&gt;Anyway, thanks.  I'll leave this open a while longer in case anyone else wants to comment.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2007 07:38:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034419#M301956</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2007-07-11T07:38:18Z</dc:date>
    </item>
    <item>
      <title>Re: eva / switch / lvol / filesystem question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034420#M301957</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What is the Load balance policy (set_lbpolicy) set on this box for the Securepath ..  is it SQL (Shortest Queue Length).&lt;BR /&gt;&lt;BR /&gt;As some times this will also help to narrow down the issues.&lt;BR /&gt;&lt;BR /&gt;#autopath display all Ã¨ To check the load balance &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Just want to share my 2 cents ..&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Mani&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2007 10:31:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034420#M301957</guid>
      <dc:creator>Sudalaimani</dc:creator>
      <dc:date>2007-07-11T10:31:08Z</dc:date>
    </item>
    <item>
      <title>Re: eva / switch / lvol / filesystem question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034421#M301958</link>
      <description>spmgr shows the following (I've included only one lun due to space):&lt;BR /&gt;&lt;BR /&gt;  Command: spmgr display&lt;BR /&gt;  = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =&lt;BR /&gt;  Storage:  &lt;BR /&gt;  Load Balance: On   Auto-restore: On     Balance Policy: Round Robin&lt;BR /&gt;  Path Verify: On    Verify Interval: 30&lt;BR /&gt;  HBAs: td0  td1&lt;BR /&gt;  Controller:  P016, Operational&lt;BR /&gt;               P02B, Operational&lt;BR /&gt;  Devices:  c13t0d0  c13t0d1  c13t0d2  c13t0d3  c13t0d4  c13t0d5  c13t0d6&lt;BR /&gt;            c13t0d7  c13t1d0  c13t1d1  c13t1d2  c13t1d3  c13t1d4  c13t1d5&lt;BR /&gt;            c13t1d6  c13t1d7  c13t2d0  c13t2d1  c13t2d2  c13t2d3  c13t2d4&lt;BR /&gt;            c13t2d5  c13t2d6  c13t2d7  c13t3d0  c13t3d1  c13t3d2  c13t3d3&lt;BR /&gt;            c13t3d4  c13t3d5  c13t3d6  c13t3d7  c13t4d0  c13t4d1  c13t4d2&lt;BR /&gt;            c13t4d3  c13t4d4  c13t4d5&lt;BR /&gt;&lt;BR /&gt;  TGT/LUN   Device             WWLUN_ID             H/W_Path           #_Paths&lt;BR /&gt;    0/  0   c13t0d0            6005-08B4-0010-23BC-0000-9000-0060-0000   4&lt;BR /&gt;                                                    255/255/0/0.0&lt;BR /&gt;          Controller  Path_Instance      HBA             Preferred?  Path_Status&lt;BR /&gt;          P016                                     no&lt;BR /&gt;                      c5t0d1             td0             YES          Active&lt;BR /&gt;                      c15t0d1            td1             YES          Active&lt;BR /&gt;&lt;BR /&gt;          Controller  Path_Instance      HBA             Preferred?  Path_Status&lt;BR /&gt;          P02B                                     no&lt;BR /&gt;                      c7t0d1             td0             no           Standby&lt;BR /&gt;                      c17t0d1            td1             no           Standby&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2007 11:18:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-switch-lvol-filesystem-question/m-p/4034421#M301958</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2007-07-11T11:18:57Z</dc:date>
    </item>
  </channel>
</rss>

