<?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 Why did HP use the switch port number to create device files? in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/why-did-hp-use-the-switch-port-number-to-create-device-files/m-p/2735889#M824</link>
    <description>Is there a good technical reason why HP creates the devices files based on switch domain ID and port number?  It would certainly be nice to be able to move a cable to any port (say if a port fails...), and not have to export/import.&lt;BR /&gt;&lt;BR /&gt;-tjh</description>
    <pubDate>Sun, 02 Jun 2002 05:12:52 GMT</pubDate>
    <dc:creator>Thomas J. Harrold</dc:creator>
    <dc:date>2002-06-02T05:12:52Z</dc:date>
    <item>
      <title>Why did HP use the switch port number to create device files?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/why-did-hp-use-the-switch-port-number-to-create-device-files/m-p/2735889#M824</link>
      <description>Is there a good technical reason why HP creates the devices files based on switch domain ID and port number?  It would certainly be nice to be able to move a cable to any port (say if a port fails...), and not have to export/import.&lt;BR /&gt;&lt;BR /&gt;-tjh</description>
      <pubDate>Sun, 02 Jun 2002 05:12:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/why-did-hp-use-the-switch-port-number-to-create-device-files/m-p/2735889#M824</guid>
      <dc:creator>Thomas J. Harrold</dc:creator>
      <dc:date>2002-06-02T05:12:52Z</dc:date>
    </item>
    <item>
      <title>Re: Why did HP use the switch port number to create device files?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/why-did-hp-use-the-switch-port-number-to-create-device-files/m-p/2735890#M825</link>
      <description>Hi Thomas,&lt;BR /&gt;&lt;BR /&gt;this behavior is not an invention of HP.&lt;BR /&gt;It's part of the Fibre Channel Protokoll (FCP).&lt;BR /&gt;&lt;BR /&gt;Bye</description>
      <pubDate>Mon, 03 Jun 2002 08:26:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/why-did-hp-use-the-switch-port-number-to-create-device-files/m-p/2735890#M825</guid>
      <dc:creator>Paul Barmettler</dc:creator>
      <dc:date>2002-06-03T08:26:08Z</dc:date>
    </item>
    <item>
      <title>Re: Why did HP use the switch port number to create device files?</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/why-did-hp-use-the-switch-port-number-to-create-device-files/m-p/2735891#M826</link>
      <description>HPUX is a hardware path oriented operating system.&lt;BR /&gt;&lt;BR /&gt;When HPUX is booting, it does an ioscan and compares the hardware path information to what is stored in the&lt;BR /&gt;/etc/ioconfig file. &lt;BR /&gt;If it finds a match, it will assign the instance number in the /etc/ioconfig file to the matching hardware path. &lt;BR /&gt;If it does not find a match, it will assign the next available instance number to the path. This permits&lt;BR /&gt;the system to maintain the same instance numbers across reboots of the system.&lt;BR /&gt;&lt;BR /&gt;If software address is allowd, these hardware paths and their associated device files could change at any time.&lt;BR /&gt;To avoid this, soft address is not allowed by the HPUX FC driver.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,</description>
      <pubDate>Tue, 11 Jun 2002 14:10:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/why-did-hp-use-the-switch-port-number-to-create-device-files/m-p/2735891#M826</guid>
      <dc:creator>Insu Kim</dc:creator>
      <dc:date>2002-06-11T14:10:42Z</dc:date>
    </item>
  </channel>
</rss>

