<?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: Device in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740101#M946691</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnH 0/4/0/0&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
    <pubDate>Fri, 07 Jun 2002 13:53:10 GMT</pubDate>
    <dc:creator>Steven Sim Kok Leong</dc:creator>
    <dc:date>2002-06-07T13:53:10Z</dc:date>
    <item>
      <title>Device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740100#M946690</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;I need run this command:&lt;BR /&gt;/opt/fcms/bin/fcmsutil &lt;DEVICE_FILE&gt; enable&lt;BR /&gt;&lt;BR /&gt;But I don't know the device_file name, I just have the adapter hardware path (0/4/0/0).&lt;BR /&gt;&lt;BR /&gt;How do I discover the device file, using hardware path??&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/DEVICE_FILE&gt;</description>
      <pubDate>Fri, 07 Jun 2002 13:51:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740100#M946690</guid>
      <dc:creator>Tiago Marques_2</dc:creator>
      <dc:date>2002-06-07T13:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: Device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740101#M946691</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnH 0/4/0/0&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
      <pubDate>Fri, 07 Jun 2002 13:53:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740101#M946691</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-06-07T13:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: Device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740102#M946692</link>
      <description>Use this command:&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnH 0/4/0/0&lt;BR /&gt;&lt;BR /&gt;# man ioscan (for details)</description>
      <pubDate>Fri, 07 Jun 2002 13:55:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740102#M946692</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-06-07T13:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: Device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740103#M946693</link>
      <description>fcmsutil can only run on Fibre Channel Mass Storage Adapter devices, so you can run "ioscan -k -fnC fc" to identify all the FC devices, usually they are called "/dev/td?", then you can run fcmsutil on them.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jun 2002 05:34:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740103#M946693</guid>
      <dc:creator>zhaogui</dc:creator>
      <dc:date>2002-06-10T05:34:42Z</dc:date>
    </item>
    <item>
      <title>Re: Device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740104#M946694</link>
      <description>I ignored one case, you should also run "ioscan -k -fnC lan" to find out other possible FC cards because sometimes they may fall under lan Class.</description>
      <pubDate>Mon, 10 Jun 2002 05:38:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device/m-p/2740104#M946694</guid>
      <dc:creator>zhaogui</dc:creator>
      <dc:date>2002-06-10T05:38:35Z</dc:date>
    </item>
  </channel>
</rss>

