<?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: Securepath functionality in Autopath? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892048#M281646</link>
    <description>Noooooooo, please say it ain't so!&lt;BR /&gt;&lt;BR /&gt;Are there any plans to add this functionaility into future versions?</description>
    <pubDate>Fri, 03 Nov 2006 10:46:36 GMT</pubDate>
    <dc:creator>Matthew Gwin</dc:creator>
    <dc:date>2006-11-03T10:46:36Z</dc:date>
    <item>
      <title>Securepath functionality in Autopath?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892046#M281644</link>
      <description>I'm looking for a way to make Autopath present a single device path to an HP-UX system, the way Securepath does.&lt;BR /&gt;&lt;BR /&gt;Does this feature exist in Autopath?</description>
      <pubDate>Fri, 03 Nov 2006 10:11:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892046#M281644</guid>
      <dc:creator>Matthew Gwin</dc:creator>
      <dc:date>2006-11-03T10:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: Securepath functionality in Autopath?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892047#M281645</link>
      <description>Unfortunately No, Autopath does not behave like SecurePath wherein it virtualizes the subpaths so the underlying subpaths are transparent.&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Nov 2006 10:32:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892047#M281645</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-11-03T10:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: Securepath functionality in Autopath?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892048#M281646</link>
      <description>Noooooooo, please say it ain't so!&lt;BR /&gt;&lt;BR /&gt;Are there any plans to add this functionaility into future versions?</description>
      <pubDate>Fri, 03 Nov 2006 10:46:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892048#M281646</guid>
      <dc:creator>Matthew Gwin</dc:creator>
      <dc:date>2006-11-03T10:46:36Z</dc:date>
    </item>
    <item>
      <title>Re: Securepath functionality in Autopath?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892049#M281647</link>
      <description>Well what is the problem?&lt;BR /&gt;&lt;BR /&gt;AutoPath will always have a primary Path just like DMP (Veritas VolMgr).. It has the added advantage of doing load balancing.. If the issue your having is you are dealing with more HP-UX disk device - one per Path, then I guess you'll just have o live with it and let AutoPath or VxVM DMP figure that out for you...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Nov 2006 10:53:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892049#M281647</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-11-03T10:53:21Z</dc:date>
    </item>
    <item>
      <title>Re: Securepath functionality in Autopath?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892050#M281648</link>
      <description>It's really more of a paperwork issue than anything else - our compliance process requires me to write down each device path for each LUN presented by the EVA.  On our EVA 8k this means eight paths for every LUN.&lt;BR /&gt;&lt;BR /&gt;It's also a filesystem management headache, as a new LUN must be presented to extend a filesystem, and all alt links must be added to the VG.&lt;BR /&gt;&lt;BR /&gt;The functions I need are still there, it's just more overhead than Securepath.  My shovel has been replaced by a spoon.&lt;BR /&gt;&lt;BR /&gt;Thanks for your comments!</description>
      <pubDate>Fri, 03 Nov 2006 11:01:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892050#M281648</guid>
      <dc:creator>Matthew Gwin</dc:creator>
      <dc:date>2006-11-03T11:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: Securepath functionality in Autopath?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892051#M281649</link>
      <description>Greetings Matthew;&lt;BR /&gt;&lt;BR /&gt;There is a new version of securepath (August 2006) 30F SP2.  This release gives autopath the functionality your looking for, in that it allows the creation of virtual devices.  After you have installed 30F SP2 of securepath, take a look autopath virtualdsf command.  &lt;BR /&gt;&lt;BR /&gt;Norm &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Nov 2006 12:40:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securepath-functionality-in-autopath/m-p/3892051#M281649</guid>
      <dc:creator>wvsa</dc:creator>
      <dc:date>2006-11-06T12:40:18Z</dc:date>
    </item>
  </channel>
</rss>

