<?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 HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180409#M5108</link>
    <description>Thank you kevin&lt;BR /&gt;&lt;BR /&gt;Yes ,i mean what it does , How it works?&lt;BR /&gt;&lt;BR /&gt;Thank you again</description>
    <pubDate>Mon, 02 Feb 2004 12:23:38 GMT</pubDate>
    <dc:creator>David_492</dc:creator>
    <dc:date>2004-02-02T12:23:38Z</dc:date>
    <item>
      <title>Secure path</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180407#M5106</link>
      <description>Dear all&lt;BR /&gt;&lt;BR /&gt;i need to know about secure path methodology&lt;BR /&gt;Thank you all&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Feb 2004 12:09:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180407#M5106</guid>
      <dc:creator>David_492</dc:creator>
      <dc:date>2004-02-02T12:09:47Z</dc:date>
    </item>
    <item>
      <title>Re: Secure path</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180408#M5107</link>
      <description>What is your question with regard to Secure Path?  What it does?  How it works?  Something else?</description>
      <pubDate>Mon, 02 Feb 2004 12:17:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180408#M5107</guid>
      <dc:creator>Kevin Harlan</dc:creator>
      <dc:date>2004-02-02T12:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: Secure path</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180409#M5108</link>
      <description>Thank you kevin&lt;BR /&gt;&lt;BR /&gt;Yes ,i mean what it does , How it works?&lt;BR /&gt;&lt;BR /&gt;Thank you again</description>
      <pubDate>Mon, 02 Feb 2004 12:23:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180409#M5108</guid>
      <dc:creator>David_492</dc:creator>
      <dc:date>2004-02-02T12:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: Secure path</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180410#M5109</link>
      <description>I can answer a bit about what it does.  How it works will have to be answered by someone more knowledgeable than me...&lt;BR /&gt;&lt;BR /&gt;What this software does is manages multiple paths to the storage.&lt;BR /&gt;&lt;BR /&gt;Basically, in order to have redundancy (i.e. for high availability), you have to have multiple HBAs and multiple paths to the same storage.  That way, if an HBA fails, or a switch fails, or a fiber cable snaps, etc., then the server still has access to the storage.&lt;BR /&gt;&lt;BR /&gt;The problem is, if you have multiple paths to the same storage, then the OS sees the exact same storage as different volumes/LUNs/whatever.  Most OS filesystems are *not* cluster filesystems, and thus, cannot handle multiple accesses to the filesystem at the same time.&lt;BR /&gt;&lt;BR /&gt;For example, if you presented the same NTFS filesystem simultaneously to two Windows 2000/2003 nodes, and they weren't clustered or members of the same cluster, both nodes can write to the filesystem at the same time -- and step on each other, and corrupt the filesystem.&lt;BR /&gt;&lt;BR /&gt;The above is essentially what can happen if you present a LUN across multiple paths.  The OS sees multiple filesystems, and thinks they are separate filesystems.  Writes to drive E: and drive F: would really be simultaneous writes to the same filesystem at the same time, and would have the same problems.&lt;BR /&gt;&lt;BR /&gt;What Secure Path does is manage these multiple presentations of the same LUNs.  It makes it so that the OS sees only one copy of the LUN/filesystem at a time.&lt;BR /&gt;&lt;BR /&gt;Secure Path also manages the pathways.  It can detect failures on one path, and divert the I/Os down the another (working) path.&lt;BR /&gt;&lt;BR /&gt;Does that help?</description>
      <pubDate>Mon, 02 Feb 2004 12:48:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180410#M5109</guid>
      <dc:creator>Kevin Harlan</dc:creator>
      <dc:date>2004-02-02T12:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: Secure path</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180411#M5110</link>
      <description>If you want to know more go to the SAN Design Reference Guide on &lt;A href="http://h18006.www1.hp.com/products/storageworks/san/documentation.html" target="_blank"&gt;http://h18006.www1.hp.com/products/storageworks/san/documentation.html&lt;/A&gt; &lt;BR /&gt;In Chapter 6, start reading on page 170. &lt;BR /&gt;&lt;BR /&gt;Secure path Product info can be found here:&lt;BR /&gt;&lt;A href="http://h18006.www1.hp.com/products/sanworks/secure-path/index.html" target="_blank"&gt;http://h18006.www1.hp.com/products/sanworks/secure-path/index.html&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Peter</description>
      <pubDate>Tue, 03 Feb 2004 04:08:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/secure-path/m-p/3180411#M5110</guid>
      <dc:creator>Peter Mattei</dc:creator>
      <dc:date>2004-02-03T04:08:14Z</dc:date>
    </item>
  </channel>
</rss>

