<?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 Interpreting hardware path on HP-UX connected to McData 6064 in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046896#M3455</link>
    <description>Can anyone verify the output below?&lt;BR /&gt;This is from an ioscan of a hp server connected to a 9960 by a McData 6064.&lt;BR /&gt;&lt;BR /&gt;0/0/8/0/0.97.34.19.0.1.1&lt;BR /&gt;&lt;BR /&gt;0/0/8/0/0/0               Is the address of the HBA in the server.&lt;BR /&gt;&lt;BR /&gt;97                   Domain Address (McData 6064 domain address of 1 is 61hex which converts to 97 decimal )&lt;BR /&gt;&lt;BR /&gt;34                   Port number on McData ( 34 - 4 for mcdata = port 30 )&lt;BR /&gt;&lt;BR /&gt;19                   Is set for private loop    ?? is this correct???&lt;BR /&gt;&lt;BR /&gt;0                   Is for Fibre Attached F_Port (Direct Fabric Attach), the port ID is set to 0.   ?? is this correct??&lt;BR /&gt;&lt;BR /&gt;1.1 is the lun # ( which would be 9 )&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;</description>
    <pubDate>Tue, 12 Aug 2003 02:53:17 GMT</pubDate>
    <dc:creator>Keith C. Patterson</dc:creator>
    <dc:date>2003-08-12T02:53:17Z</dc:date>
    <item>
      <title>Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046896#M3455</link>
      <description>Can anyone verify the output below?&lt;BR /&gt;This is from an ioscan of a hp server connected to a 9960 by a McData 6064.&lt;BR /&gt;&lt;BR /&gt;0/0/8/0/0.97.34.19.0.1.1&lt;BR /&gt;&lt;BR /&gt;0/0/8/0/0/0               Is the address of the HBA in the server.&lt;BR /&gt;&lt;BR /&gt;97                   Domain Address (McData 6064 domain address of 1 is 61hex which converts to 97 decimal )&lt;BR /&gt;&lt;BR /&gt;34                   Port number on McData ( 34 - 4 for mcdata = port 30 )&lt;BR /&gt;&lt;BR /&gt;19                   Is set for private loop    ?? is this correct???&lt;BR /&gt;&lt;BR /&gt;0                   Is for Fibre Attached F_Port (Direct Fabric Attach), the port ID is set to 0.   ?? is this correct??&lt;BR /&gt;&lt;BR /&gt;1.1 is the lun # ( which would be 9 )&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Aug 2003 02:53:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046896#M3455</guid>
      <dc:creator>Keith C. Patterson</dc:creator>
      <dc:date>2003-08-12T02:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046897#M3456</link>
      <description>0/8/0/0 is a slot where FC HBA is installed;&lt;BR /&gt;97.34.19 is switch and port properties to which STORAGE device is connected: 97 is domain ID, 34 is port ID, 19 is for fabric connection (note: McData fabric identifier is 19, but brocade's is 0);&lt;BR /&gt;0.1.1 is LUN number: 1+8*1+0*128=9 (LUN 9)&lt;BR /&gt;Eugeny</description>
      <pubDate>Tue, 12 Aug 2003 05:28:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046897#M3456</guid>
      <dc:creator>Eugeny Brychkov</dc:creator>
      <dc:date>2003-08-12T05:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046898#M3457</link>
      <description>This is how I interpret these things:&lt;BR /&gt;&lt;BR /&gt;# /opt/fcms/bin/fcmsutil /dev/td0 get remote all&lt;BR /&gt;&lt;BR /&gt;Using the 'Target N_Port_id' is = xxYYxx (YY should be equal to the port number)&lt;BR /&gt;&lt;BR /&gt;19 is the set addressing mode (I believe 19 to be loop)&lt;BR /&gt;0 is the VBUS (virtual bus, seeing it is direct connect, I would expect 0 to be the value)&lt;BR /&gt;1 is the target&lt;BR /&gt;1 is the LUN &lt;BR /&gt;&lt;BR /&gt;0/0/8/0/0.97.34.19.0.1.1&lt;BR /&gt;&lt;BR /&gt;Your example device should end up being cXt1d1 &lt;BR /&gt;The LUN addressing is from t0 - t7 then the next target address is used.&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Aug 2003 05:53:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046898#M3457</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2003-08-12T05:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046899#M3458</link>
      <description>Eugeny,&lt;BR /&gt;Thanks for your response. I'm sure you are correct about 19 is McData's way to identify fabric addressing but do you have any McData doc's that back this up?&lt;BR /&gt;I have scoured the web and am unable to find anything.&lt;BR /&gt;My main concern is that Michael responded that 19 is used for loop which is contrary to your response.&lt;BR /&gt;I need to be certain on this and would prefer any documentation that you can provide?&lt;BR /&gt;By the way, I have looked at HP's Fabric Migration Guide and it seems to be Brocade centric.</description>
      <pubDate>Wed, 13 Aug 2003 19:53:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046899#M3458</guid>
      <dc:creator>Keith C. Patterson</dc:creator>
      <dc:date>2003-08-13T19:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046900#M3459</link>
      <description>Who can provide the zone function about McDATA switch?&lt;BR /&gt;Because I know the McDATA switch can only support one zone,is it true?</description>
      <pubDate>Sun, 17 Aug 2003 13:05:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046900#M3459</guid>
      <dc:creator>david5337_1</dc:creator>
      <dc:date>2003-08-17T13:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046901#M3460</link>
      <description>David,&lt;BR /&gt;This makes absolutely no sense. The function of zoning is to mask devices from one another on the switch.&lt;BR /&gt;If you were only able to create one zone then only those devices that existed in that zone would be masked and all other devices that you left out of that single zone would not have the ability to mask their presence.&lt;BR /&gt;In short, yes, you can enable multiple zones on a McData switch as well as Brocade for that matter,</description>
      <pubDate>Sat, 23 Aug 2003 01:58:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046901#M3460</guid>
      <dc:creator>Keith C. Patterson</dc:creator>
      <dc:date>2003-08-23T01:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046902#M3461</link>
      <description>David,&lt;BR /&gt;This makes absolutely no sense. The function of zoning is to mask devices from one another on the switch.&lt;BR /&gt;If you were only able to create one zone then only those devices that existed in that zone would be masked and all other devices that you left out of that single zone would not have the ability to mask their presence.&lt;BR /&gt;In short, yes, you can enable multiple zones on a McData switch as well as Brocade for that matter.</description>
      <pubDate>Sat, 23 Aug 2003 01:59:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046902#M3461</guid>
      <dc:creator>Keith C. Patterson</dc:creator>
      <dc:date>2003-08-23T01:59:19Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046903#M3462</link>
      <description>With McData switches there can only be one zoning definition active at any one time. This zoning definition can include a collection of zones and ports so it's not an issue of only having one zone - many zone can be defined within an active zone.</description>
      <pubDate>Thu, 30 Oct 2003 11:26:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046903#M3462</guid>
      <dc:creator>Perry Lichtinger</dc:creator>
      <dc:date>2003-10-30T11:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: Interpreting hardware path on HP-UX connected to McData 6064</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046904#M3463</link>
      <description>as far as I know , Mcdata switches don't support loop , they are only fabric .&lt;BR /&gt;&lt;BR /&gt;19 is definitely a fabric identifier for Mcdata , I can say for sure .&lt;BR /&gt;&lt;BR /&gt;As far as zoning goes , there can be multiple zones . However there can be only one active zone set on the switch . A zone set is a collection of zones .&lt;BR /&gt;&lt;BR /&gt;THere can be multple zone sets but only one zone set can be active at any given time .</description>
      <pubDate>Thu, 30 Oct 2003 14:58:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/interpreting-hardware-path-on-hp-ux-connected-to-mcdata-6064/m-p/3046904#M3463</guid>
      <dc:creator>Ashwani Kashyap</dc:creator>
      <dc:date>2003-10-30T14:58:20Z</dc:date>
    </item>
  </channel>
</rss>

