<?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: DM Multipath with SVSP on SLES11 SP1 in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/dm-multipath-with-svsp-on-sles11-sp1/m-p/4679276#M41973</link>
    <description>Very much appreciated! :-)&lt;BR /&gt;&lt;BR /&gt;For compatibility check out SPOCK:&lt;BR /&gt;&lt;A href="http://hp.com/storage/spock/" target="_blank"&gt;http://hp.com/storage/spock/&lt;/A&gt; (select View by Array/OS)&lt;BR /&gt;&lt;BR /&gt;It looks like SVSP 3 alone is not supported with SLES, but the EVA Cluster is... strange. And on RHEL they used the native Qlogic failover drives. I really hope they start supporting it with DM multipath.</description>
    <pubDate>Wed, 25 Aug 2010 17:43:23 GMT</pubDate>
    <dc:creator>Michael Leu</dc:creator>
    <dc:date>2010-08-25T17:43:23Z</dc:date>
    <item>
      <title>DM Multipath with SVSP on SLES11 SP1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dm-multipath-with-svsp-on-sles11-sp1/m-p/4679274#M41971</link>
      <description>We have a SVSP installation with two HP EVA 4400 as backend storage and two data path modules and want to integrate a SLES11 SP1 server with two HP AE312A HBA (QLogic based Dual Port FC 4GBit HBA), but this configuration seems to have problems with DM multipathing.&lt;BR /&gt;&lt;BR /&gt;First, I could not install the HP DM Multipathing software package (HPDMmultipath-4.4.0) as SLES11 SP1 is not supported (only SLES11), but the multipath-tools in the HP package seems to be older (2007, v0.4.5?) than the SLES11 SP1 multipath-tools (v0.4.8), anyway.&lt;BR /&gt;&lt;BR /&gt;I then tried to use the onboard utilities provided by SLES11 SP1 (multipath-tools-0.4.8-40.23.1, original SLES11 SP1 Linux kernel qla2xxx driver).&lt;BR /&gt;With that, I can successfully activate mutlipathing to a vDisk, but only if I use the paths active at mapping creation time! I have to blacklist the standby paths to get a working mapping:&lt;BR /&gt;&lt;BR /&gt;blacklist {&lt;BR /&gt;[...]&lt;BR /&gt;        devnode         "^sdb[0-9]*"&lt;BR /&gt;        devnode         "^sdd[0-9]*"&lt;BR /&gt;        devnode         "^sdf[0-9]*"&lt;BR /&gt;        devnode         "^sdh[0-9]*"&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;# multipath -ll&lt;BR /&gt;svsp (3600a0b80001111550000ace86fa4734c) dm-8 HP,HSVX700&lt;BR /&gt;size=480G features='1 queue_if_no_path' hwhandler='0' wp=rw&lt;BR /&gt;`-+- policy='round-robin 0' prio=4 status=active&lt;BR /&gt;  |- 5:0:0:1 sda 8:0   active ready  running&lt;BR /&gt;  |- 7:0:0:1 sde 8:64  active ready  running&lt;BR /&gt;  |- 6:0:0:1 sdc 8:32  active ready  running&lt;BR /&gt;  `- 8:0:0:1 sdg 8:96  active ready  running&lt;BR /&gt;&lt;BR /&gt;I then can use this multipath device, create a filesystem, mount it, etc. &lt;BR /&gt;&lt;BR /&gt;But if I use all 8 paths provided by SVSP (4 active, 4 standby), the multipath mapping creation is rejected and no mapping is created:&lt;BR /&gt;&lt;BR /&gt;reject: svsp (3600a0b80001111550000ace86fa4734c) undef HP,HSVX700&lt;BR /&gt;size=480G features='1 queue_if_no_path' hwhandler='0' wp=undef&lt;BR /&gt;|-+- policy='round-robin 0' prio=0 status=undef&lt;BR /&gt;| |- 5:0:1:1 sdb 8:16  undef faulty running&lt;BR /&gt;| |- 6:0:1:1 sdd 8:48  undef faulty running&lt;BR /&gt;| |- 7:0:1:1 sdf 8:80  undef faulty running&lt;BR /&gt;| `- 8:0:1:1 sdh 8:112 undef faulty running&lt;BR /&gt;`-+- policy='round-robin 0' prio=4 status=undef&lt;BR /&gt;  |- 5:0:0:1 sda 8:0   active ready  running&lt;BR /&gt;  |- 7:0:0:1 sde 8:64  active ready  running&lt;BR /&gt;  |- 6:0:0:1 sdc 8:32  active ready  running&lt;BR /&gt;  `- 8:0:0:1 sdg 8:96  active ready  running&lt;BR /&gt;&lt;BR /&gt;I tried various settings in /etc/multipath.conf but could not find a working one with all 8 paths enabled. &lt;BR /&gt;Even multipath-tools seems to provide a default configuration for this hardware (entry for HP HSVX700), which does not work, too.&lt;BR /&gt;But blacklisting the 4 standby paths in /etc/multipath.conf is not a real solution I want to use in production, of course.&lt;BR /&gt;&lt;BR /&gt;Does anyone actually use this kind of setup (HP SVSP with SLES11 SP1) and can provide me with a working configuration example?&lt;BR /&gt;&lt;BR /&gt;Or is this really a non supported setup? (I found a short HP knowledge base article which seems to indicate that SVSP DM multipathing is not supported yet(?) with Linux)&lt;BR /&gt;&lt;BR /&gt;Many thanks in advance!</description>
      <pubDate>Wed, 25 Aug 2010 07:34:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dm-multipath-with-svsp-on-sles11-sp1/m-p/4679274#M41971</guid>
      <dc:creator>Andreas Haumer</dc:creator>
      <dc:date>2010-08-25T07:34:04Z</dc:date>
    </item>
    <item>
      <title>Re: DM Multipath with SVSP on SLES11 SP1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dm-multipath-with-svsp-on-sles11-sp1/m-p/4679275#M41972</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;We did some more testing and now we have a configuration which seems to work just as expected!&lt;BR /&gt;&lt;BR /&gt;# multipath -ll&lt;BR /&gt;svsp (3600a0b80001111550000ace86fa4734c) dm-8 HP,HSVX700&lt;BR /&gt;size=480G features='1 queue_if_no_path' hwhandler='0' wp=rw&lt;BR /&gt;|-+- policy='round-robin 0' prio=4 status=active&lt;BR /&gt;| |- 5:0:0:1 sda 8:0   active ready running&lt;BR /&gt;| |- 6:0:0:1 sdc 8:32  active ready running&lt;BR /&gt;| |- 7:0:0:1 sde 8:64  active ready running&lt;BR /&gt;| `- 8:0:0:1 sdg 8:96  active ready running&lt;BR /&gt;`-+- policy='round-robin 0' prio=2 status=enabled&lt;BR /&gt;  |- 5:0:1:1 sdb 8:16  active ghost running&lt;BR /&gt;  |- 8:0:1:1 sdh 8:112 active ghost running&lt;BR /&gt;  |- 6:0:1:1 sdd 8:48  active ghost running&lt;BR /&gt;  `- 7:0:1:1 sdf 8:80  active ghost running&lt;BR /&gt;&lt;BR /&gt;The trick was to use option "hp_sw" for configuration parameter "path_checker".&lt;BR /&gt;&lt;BR /&gt;My /etc/multipath.conf now contains the following settings:&lt;BR /&gt;&lt;BR /&gt;defaults {&lt;BR /&gt;        udev_dir                /dev&lt;BR /&gt;        polling_interval        10&lt;BR /&gt;        selector                "round-robin 0"&lt;BR /&gt;        path_grouping_policy    failover&lt;BR /&gt;        getuid_callout          "/lib/udev/scsi_id -g -u /dev/%n"&lt;BR /&gt;        prio                    const&lt;BR /&gt;        path_checker            tur&lt;BR /&gt;        rr_min_io               100&lt;BR /&gt;        rr_weight               uniform&lt;BR /&gt;        failback                immediate&lt;BR /&gt;        no_path_retry           12&lt;BR /&gt;        user_friendly_names     yes&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;blacklist {&lt;BR /&gt;        devnode         "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"&lt;BR /&gt;        devnode         "^hd[a-z][[0-9]*]"&lt;BR /&gt;        devnode         "^cciss!c[0-9]d[0-9]*"&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;multipaths {&lt;BR /&gt;multipath {&lt;BR /&gt;        wwid                    3600a0b80001111550000ace86fa4734c&lt;BR /&gt;        alias                   svsp&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;device {&lt;BR /&gt;        vendor                  "HP"&lt;BR /&gt;        product                 "HSVX700"&lt;BR /&gt;        path_grouping_policy     group_by_prio&lt;BR /&gt;        getuid_callout          "/lib/udev/scsi_id -g -u /dev/%n"&lt;BR /&gt;        path_checker            hp_sw&lt;BR /&gt;        path_selector           "round-robin 0"&lt;BR /&gt;        prio                    hp_sw&lt;BR /&gt;        rr_weight               uniform&lt;BR /&gt;        failback                immediate&lt;BR /&gt;        hardware_handler        "0"&lt;BR /&gt;        rr_min_io               100&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;There might be room for optimization, but for now we are happy. All tests (reboot, failover, switchback, ...) did work fine.&lt;BR /&gt;&lt;BR /&gt;Just in case someone is looking for a solution for the same problem... ;-)</description>
      <pubDate>Wed, 25 Aug 2010 09:19:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dm-multipath-with-svsp-on-sles11-sp1/m-p/4679275#M41972</guid>
      <dc:creator>Andreas Haumer</dc:creator>
      <dc:date>2010-08-25T09:19:37Z</dc:date>
    </item>
    <item>
      <title>Re: DM Multipath with SVSP on SLES11 SP1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dm-multipath-with-svsp-on-sles11-sp1/m-p/4679276#M41973</link>
      <description>Very much appreciated! :-)&lt;BR /&gt;&lt;BR /&gt;For compatibility check out SPOCK:&lt;BR /&gt;&lt;A href="http://hp.com/storage/spock/" target="_blank"&gt;http://hp.com/storage/spock/&lt;/A&gt; (select View by Array/OS)&lt;BR /&gt;&lt;BR /&gt;It looks like SVSP 3 alone is not supported with SLES, but the EVA Cluster is... strange. And on RHEL they used the native Qlogic failover drives. I really hope they start supporting it with DM multipath.</description>
      <pubDate>Wed, 25 Aug 2010 17:43:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dm-multipath-with-svsp-on-sles11-sp1/m-p/4679276#M41973</guid>
      <dc:creator>Michael Leu</dc:creator>
      <dc:date>2010-08-25T17:43:23Z</dc:date>
    </item>
  </channel>
</rss>

