<?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: hsx device question in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/hsx-device-question/m-p/3574396#M16675</link>
    <description>I don't have any experience with Solaris, but after a short look into the manual and a bit of experience on other OSes (HP-UX, Linux, Windows)...&lt;BR /&gt;&lt;BR /&gt;1. the output of 'spmgr' looks pretty similar to that of other operating system implementation, so I'd say: yes.&lt;BR /&gt;&lt;BR /&gt;3. there is a picture in the installation manual that shows the layering. Indeed, the I/O request goes from the Solaris disk driver to the 'swsp' driver which handles all paths and is then directed to the 'hsx' driver. The 'hsx' driver contains array-specific know-how, e.g. how to fail over a device. Then the I/O goes to the driver of the fibre channel adapter.</description>
    <pubDate>Thu, 30 Jun 2005 13:39:57 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2005-06-30T13:39:57Z</dc:date>
    <item>
      <title>hsx device question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hsx-device-question/m-p/3574395#M16674</link>
      <description>All,&lt;BR /&gt;&lt;BR /&gt;  I am running Secure Path version 3.0C_SP1 on a Solaris 8 machine.  When I do a 'spmgr display' it lists a hsx device name for each path, for instance hsx-2818-33-4.  I have several questions.  &lt;BR /&gt;1. Does the hsx instance have a 1 to 1 relationship to a device file? &lt;BR /&gt;2. Solaris 'sar' reports devices such as hsx840; do these devices map to a specific instance?&lt;BR /&gt;3. Does an IO request go to a sd device and then Secure Path take that disk IO request and pass it thru the active hsx path?  If not, what is the path of an IO request?  &lt;BR /&gt;&lt;BR /&gt;Thanks for your help!</description>
      <pubDate>Thu, 30 Jun 2005 13:19:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hsx-device-question/m-p/3574395#M16674</guid>
      <dc:creator>Spike Burkhardt</dc:creator>
      <dc:date>2005-06-30T13:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: hsx device question</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hsx-device-question/m-p/3574396#M16675</link>
      <description>I don't have any experience with Solaris, but after a short look into the manual and a bit of experience on other OSes (HP-UX, Linux, Windows)...&lt;BR /&gt;&lt;BR /&gt;1. the output of 'spmgr' looks pretty similar to that of other operating system implementation, so I'd say: yes.&lt;BR /&gt;&lt;BR /&gt;3. there is a picture in the installation manual that shows the layering. Indeed, the I/O request goes from the Solaris disk driver to the 'swsp' driver which handles all paths and is then directed to the 'hsx' driver. The 'hsx' driver contains array-specific know-how, e.g. how to fail over a device. Then the I/O goes to the driver of the fibre channel adapter.</description>
      <pubDate>Thu, 30 Jun 2005 13:39:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hsx-device-question/m-p/3574396#M16675</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-06-30T13:39:57Z</dc:date>
    </item>
  </channel>
</rss>

