<?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: Secure Path in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941796#M617665</link>
    <description>Excuse me, but what is that supposed to mean?&lt;BR /&gt;&lt;BR /&gt;Doesn't multipathing provide for failover when one path goes down or did you mean some other 'failover'?</description>
    <pubDate>Fri, 13 Jan 2006 01:05:04 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2006-01-13T01:05:04Z</dc:date>
    <item>
      <title>Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941790#M617659</link>
      <description>HI:&lt;BR /&gt;&lt;BR /&gt;Some body, know how works the secure path for HPUX, o how interative with Logic Volumen Manager (LVM)? In hpux i need continue using PVlink  for the alternate link o the Secure Path does the work?</description>
      <pubDate>Fri, 18 Nov 2005 10:52:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941790#M617659</guid>
      <dc:creator>Isaac_4</dc:creator>
      <dc:date>2005-11-18T10:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941791#M617660</link>
      <description>You use SecurePath specifically for HSG and HSV100/110 (EVA3000/5000) based arrays that do not support PVlinks or Alternate-Pathing. It is your onlyway of protecting your Paths to those arrays.&lt;BR /&gt;&lt;BR /&gt;With newer EVAs (4/6/8K) I heard SecurePath is already optional as PVLINKS/AP and VxVM's DMP (and MPIO on Windows/Linux) now is compatible.&lt;BR /&gt;&lt;BR /&gt;HTH.&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Nov 2005 11:02:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941791#M617660</guid>
      <dc:creator>Zinky</dc:creator>
      <dc:date>2005-11-18T11:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941792#M617661</link>
      <description>In the case of Secure Path for HSG and EVA3000/5000 it creates a new adapter with devices through which you access the disk space. You do not enter alternate paths like when using PVlinks.&lt;BR /&gt;&lt;BR /&gt;The documentation has a nice picture which explains the device and driver layering.</description>
      <pubDate>Fri, 18 Nov 2005 11:06:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941792#M617661</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-18T11:06:38Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941793#M617662</link>
      <description>I have a Eva 4000&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Nov 2005 14:32:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941793#M617662</guid>
      <dc:creator>Isaac_4</dc:creator>
      <dc:date>2005-11-18T14:32:49Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941794#M617663</link>
      <description>In that case you can use PVlinks or install the AutoPath component of Secure Path. AutoPath does not create a new virtual adapter.</description>
      <pubDate>Fri, 18 Nov 2005 14:36:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941794#M617663</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-18T14:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941795#M617664</link>
      <description>And when you use autopath feature of secure path, you also need to use pvlinks for failover.  autopath does multipathing only.</description>
      <pubDate>Thu, 12 Jan 2006 15:50:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941795#M617664</guid>
      <dc:creator>Pat Obrien_1</dc:creator>
      <dc:date>2006-01-12T15:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941796#M617665</link>
      <description>Excuse me, but what is that supposed to mean?&lt;BR /&gt;&lt;BR /&gt;Doesn't multipathing provide for failover when one path goes down or did you mean some other 'failover'?</description>
      <pubDate>Fri, 13 Jan 2006 01:05:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941796#M617665</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-01-13T01:05:04Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941797#M617666</link>
      <description>thank you</description>
      <pubDate>Sat, 14 Jan 2006 02:03:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941797#M617666</guid>
      <dc:creator>Isaac_4</dc:creator>
      <dc:date>2006-01-14T02:03:40Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941798#M617667</link>
      <description>The landscape has gotten muddy.  We have EVA5K and EVAXL.  the EVA5K can be active-active or default active-passive.  Todays version of SecurePath 3.0F is a combination of premerger Compaq SecurePath product and HP AutoPath product.  The AutoPath product is used for active-active and SecurePath for active-passive arrays. AutoPath only provides  multi-pathing support without the failover capabilities of the traditional SecurePath product.  hence with AutoPath you need pvlinks also.</description>
      <pubDate>Tue, 17 Jan 2006 12:42:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941798#M617667</guid>
      <dc:creator>Pat Obrien_1</dc:creator>
      <dc:date>2006-01-17T12:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Path</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941799#M617668</link>
      <description>Pat.. you're last post nailed it.&lt;BR /&gt;&lt;BR /&gt;3.0F still has the old pre-merger SecurePath for Active-Passive arrays (works for EVA5K/3K with the HSV100/110 controllers). It also has the AutoPath product which they now call SecurePath for Active-Active arrays (ie.e HSV101/111 and newer EVA4/6/8K, VA as well as XP) -- for which you will still need to use PVLINKS as I understand it.&lt;BR /&gt;&lt;BR /&gt;Multi-pathing IMHO is not the same as failover. Multi-pathing is the ability to provide multiple paths to the same LUN which can either be for load balancing or failover. That is why one still needs PVLINKS with Autopath.&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Jan 2006 13:27:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secure-path/m-p/4941799#M617668</guid>
      <dc:creator>Zinky</dc:creator>
      <dc:date>2006-01-17T13:27:26Z</dc:date>
    </item>
  </channel>
</rss>

