<?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: hds 9900 connected to  rp7400 ioscan multiple  lun0 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665235#M4038</link>
    <description>This is the way that HP-UX sees the HDS.&lt;BR /&gt;The fiber channel is emulated as F/W SCSI on the HP9000 host and the LUN number (0-119) will be translated by the host to SCSI target IDs and LUN numbers.&lt;BR /&gt;&lt;BR /&gt;Bear in mind that there are basic LUN assignment rules.&lt;BR /&gt;1. Each SCSI target must have a LUN 0 or none of the LUNs on that target will be visible to the host.&lt;BR /&gt;2. Don't break a string of LUNs or the subsequent LUNs will not be visible to the host.&lt;BR /&gt;(Ex: if LUN 30,31,32, and 36 are assigned, the host will only see LUNs 30,31,32 but this vulnerability can be overcome by creating a pseudo device. I'll explain that below)&lt;BR /&gt;&lt;BR /&gt;The array fools the host into thinking LUN 0 and the string are available by creating a psuedo device for each SCSI target ID on a given FC card, that is, a fake device will show up for SCSI IDs 0,1,2,3,4, etc even if a LUN is not assigned to that target.&lt;BR /&gt;This allows you to assign LUNs without having to assign to LUN 0 and also allows you to skip a LUN in the string.&lt;BR /&gt;That's why you see a psuedo device file on each&lt;BR /&gt;SCSI target ID when you issue ioscan.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Insu,</description>
    <pubDate>Fri, 15 Feb 2002 11:44:24 GMT</pubDate>
    <dc:creator>Insu Kim</dc:creator>
    <dc:date>2002-02-15T11:44:24Z</dc:date>
    <item>
      <title>hds 9900 connected to  rp7400 ioscan multiple  lun0</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665234#M4037</link>
      <description>The rp7400 ioscan -fn of a hds 9900 is displaying entries /dev/dsk/cxt(0 to 15)d0 (lun 0) even though lun 0 has not been allocated any size or presented to the FC port and has a description of "HITACHI DISK-SUBSYSTEM". The HDS HP extension to allow 120 luns is installed. This is duplicated for every SCSI target 0 to 15. The ioscan for open-E devices is fine. (See example below). Is there any way to stop the rp7400 seeing these lun0  entries when they have not been created on the hds?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; disk        6  0/10/0/0.1.64.0.0.2.0    sdisk     CLAIMED     DEVICE       HITACHI DISK-SUBSYSTEM&lt;BR /&gt;                             /dev/dsk/c4t2d0   /dev/rdsk/c4t2d0&lt;BR /&gt;disk       37  0/10/0/0.1.64.0.0.2.4    sdisk     CLAIMED     DEVICE       HITACHI OPEN-E&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Feb 2002 20:29:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665234#M4037</guid>
      <dc:creator>kavanagh_1</dc:creator>
      <dc:date>2002-02-14T20:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: hds 9900 connected to  rp7400 ioscan multiple  lun0</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665235#M4038</link>
      <description>This is the way that HP-UX sees the HDS.&lt;BR /&gt;The fiber channel is emulated as F/W SCSI on the HP9000 host and the LUN number (0-119) will be translated by the host to SCSI target IDs and LUN numbers.&lt;BR /&gt;&lt;BR /&gt;Bear in mind that there are basic LUN assignment rules.&lt;BR /&gt;1. Each SCSI target must have a LUN 0 or none of the LUNs on that target will be visible to the host.&lt;BR /&gt;2. Don't break a string of LUNs or the subsequent LUNs will not be visible to the host.&lt;BR /&gt;(Ex: if LUN 30,31,32, and 36 are assigned, the host will only see LUNs 30,31,32 but this vulnerability can be overcome by creating a pseudo device. I'll explain that below)&lt;BR /&gt;&lt;BR /&gt;The array fools the host into thinking LUN 0 and the string are available by creating a psuedo device for each SCSI target ID on a given FC card, that is, a fake device will show up for SCSI IDs 0,1,2,3,4, etc even if a LUN is not assigned to that target.&lt;BR /&gt;This allows you to assign LUNs without having to assign to LUN 0 and also allows you to skip a LUN in the string.&lt;BR /&gt;That's why you see a psuedo device file on each&lt;BR /&gt;SCSI target ID when you issue ioscan.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Insu,</description>
      <pubDate>Fri, 15 Feb 2002 11:44:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665235#M4038</guid>
      <dc:creator>Insu Kim</dc:creator>
      <dc:date>2002-02-15T11:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: hds 9900 connected to  rp7400 ioscan multiple  lun0</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665236#M4039</link>
      <description>You can ignore the DISK-SUBSYSTEM lines in the ioscan.  They really mean nothing.&lt;BR /&gt;&lt;BR /&gt;The non-consecutive LUN problem has been fixed; you need only download the patch (which I forget the number of...)&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Feb 2002 21:11:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665236#M4039</guid>
      <dc:creator>Vincent Fleming</dc:creator>
      <dc:date>2002-02-22T21:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: hds 9900 connected to  rp7400 ioscan multiple  lun0</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665237#M4040</link>
      <description>Thanks for the help. &lt;BR /&gt;&lt;BR /&gt;The other gotcha with the LUN0s which I have discovered is that EMS doesn't like them! The file /var/stm/data/tools/monitor/disabled_instances needs the hardware path of each LUN0 adding to it to stop EMS reporting errors on them.</description>
      <pubDate>Thu, 07 Mar 2002 11:50:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hds-9900-connected-to-rp7400-ioscan-multiple-lun0/m-p/2665237#M4040</guid>
      <dc:creator>kavanagh_1</dc:creator>
      <dc:date>2002-03-07T11:50:52Z</dc:date>
    </item>
  </channel>
</rss>

