<?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: fiber channel host adpater question in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788286#M66121</link>
    <description>The device driver will do multipath filtering only for _disk_ arrays it has in its internal table. You should be fine using one driver.</description>
    <pubDate>Mon, 15 May 2006 11:14:18 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2006-05-15T11:14:18Z</dc:date>
    <item>
      <title>fiber channel host adpater question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788285#M66120</link>
      <description>Hello, &lt;BR /&gt;we have a proliant dl740 with Red Hat AS4.&lt;BR /&gt;We have 3 identical adapters for fiber channel.&lt;BR /&gt;2 of these are used for the storage (they are linked to an EVA 5000), the other one is linked to an MSL 5026 Tape Library.&lt;BR /&gt;The adapaters are: "Fibre Channel Host Adapter for QLA2340" &lt;BR /&gt;&lt;BR /&gt;We'd like to load 2 modules: one for the 2 "Storage adapters", with some options (fail over for example), and one for the "Tape Library Adapters", with other options (here fail over is useless, for example).&lt;BR /&gt;&lt;BR /&gt;For the moment we use only one module for the 3 adapters; here our modprobe.conf:&lt;BR /&gt;&lt;BR /&gt;install bonding0 /sbin/modprobe bmc5700; /sbin/modprobe e1000; /sbin/modprobe --ignore-install bonding0&lt;BR /&gt;install bonding0 /sbin/modprobe bonding -obond0 mode=1 miimon=100&lt;BR /&gt;install bonding1 /sbin/modprobe bonding -obond1 mode=4 miimon=100&lt;BR /&gt;alias bond0 bonding0&lt;BR /&gt;alias bond1 bonding1&lt;BR /&gt;alias eth0 bcm5700&lt;BR /&gt;alias eth1 bcm5700&lt;BR /&gt;alias eth2 bcm5700&lt;BR /&gt;alias eth4 e1000&lt;BR /&gt;alias eth3 e1000&lt;BR /&gt;alias scsi_hostadapter cciss&lt;BR /&gt;alias usb-controller ohci-hcd&lt;BR /&gt;options scsi_mod max_luns=128&lt;BR /&gt;alias scsi_hostadapter1 qla2xxx_conf&lt;BR /&gt;alias scsi_hostadapter2 qla2300&lt;BR /&gt;alias scsi_hostadapter3 qla6312&lt;BR /&gt;options qla2xxx  ql2xmaxqdepth=16 qlport_down_retry=30 ql2xloginretrycount=30 ql2xfailover=1 ql2xlbType=1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We suppose we have to do something similar to what we have done for bonding.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We now use: hp_qla2x00src-8.01.03p4-20&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If someone can help...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Filippo&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 15 May 2006 10:05:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788285#M66120</guid>
      <dc:creator>NPI</dc:creator>
      <dc:date>2006-05-15T10:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: fiber channel host adpater question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788286#M66121</link>
      <description>The device driver will do multipath filtering only for _disk_ arrays it has in its internal table. You should be fine using one driver.</description>
      <pubDate>Mon, 15 May 2006 11:14:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788286#M66121</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2006-05-15T11:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: fiber channel host adpater question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788287#M66122</link>
      <description>I think if You want that granular configuration You need to use the devicemapper MPIO implementation.&lt;BR /&gt;&lt;BR /&gt;From what I understood reading &lt;BR /&gt;&lt;A href="http://www.linuxsymposium.org/2005/linuxsymposium_procv1.pdf" target="_blank"&gt;http://www.linuxsymposium.org/2005/linuxsymposium_procv1.pdf&lt;/A&gt;&lt;BR /&gt;it will allow You to freely configure failover settings per device and mostly autoconfigure them. I have yet to try it out, though.&lt;BR /&gt;&lt;BR /&gt;Just don't waste Your time using md 'pseudo-raid' high availability ;)</description>
      <pubDate>Mon, 15 May 2006 17:45:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788287#M66122</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2006-05-15T17:45:58Z</dc:date>
    </item>
    <item>
      <title>Re: fiber channel host adpater question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788288#M66123</link>
      <description>Thanks for the answers.&lt;BR /&gt;In the fact, the question I made is due to a problem we have with our Tape Library (which has 2 Tape Drives)...&lt;BR /&gt;&lt;BR /&gt;Unfortunatly This morning another problem (different from the one for which we've opened this case) has occurred on our tape library: /dev/nst1 can't eject the tape that has inside (and is marked as "uninstalled" by the library monitor), and the other drive is doing an important (and quite long)backup that we can't stop...&lt;BR /&gt;&lt;BR /&gt;So, for the moment, we can consider this case as close: we'll write again when this hardware problem will be solved.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks to all, anyway&lt;BR /&gt;&lt;BR /&gt;Filippo</description>
      <pubDate>Tue, 16 May 2006 09:10:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fiber-channel-host-adpater-question/m-p/3788288#M66123</guid>
      <dc:creator>NPI</dc:creator>
      <dc:date>2006-05-16T09:10:00Z</dc:date>
    </item>
  </channel>
</rss>

