<?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 Multipulse or Device Mapper Multipath? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/multipulse-or-device-mapper-multipath/m-p/4344486#M54711</link>
    <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;Following is my configuration.&lt;BR /&gt;&lt;BR /&gt;Hardware - BL460c Servers, Emulex LPe1105 (HP) HBAs, IBM System Storage DS8100&lt;BR /&gt;&lt;BR /&gt;OS - RHEL 5 Update 2 x86_64, Oracle Enterprise Linux Update 2 x86_64&lt;BR /&gt;&lt;BR /&gt;This is a new installation and we've successfully presented the san volumes from the DS8100 to Linux (RHEL and Oracle Linux).&lt;BR /&gt;&lt;BR /&gt;For multipath I have two options in my mind.&lt;BR /&gt;&lt;BR /&gt;1. Emulex Multipulse.&lt;BR /&gt;2. Device Mapper Multipath.&lt;BR /&gt;&lt;BR /&gt;I've already configured both on two blades and everything works fine but it seems Multipulse is preferable because it abstracts all the redundant path devices.&lt;BR /&gt;&lt;BR /&gt;Searching on IBM DS8100 site for Multipulse I was unable to find any recommendations nor oppositions for Multipulse.&lt;BR /&gt;&lt;BR /&gt;Ths support site for DS8100 provides a multipath.conf file to configure Device Mapper for RHEL 5.&lt;BR /&gt;&lt;BR /&gt;Are there any good reasons to stick with device mapper rather than using multipulse?&lt;BR /&gt;&lt;BR /&gt;Your opinions are much appreciated.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Shiraj.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. This thread has been moved&amp;nbsp;from General to &amp;gt; Linux &amp;gt; System Administration. - Hp Forum moderator&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2015 04:24:32 GMT</pubDate>
    <dc:creator>Shiraj Fernando</dc:creator>
    <dc:date>2015-04-27T04:24:32Z</dc:date>
    <item>
      <title>Multipulse or Device Mapper Multipath?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/multipulse-or-device-mapper-multipath/m-p/4344486#M54711</link>
      <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;Following is my configuration.&lt;BR /&gt;&lt;BR /&gt;Hardware - BL460c Servers, Emulex LPe1105 (HP) HBAs, IBM System Storage DS8100&lt;BR /&gt;&lt;BR /&gt;OS - RHEL 5 Update 2 x86_64, Oracle Enterprise Linux Update 2 x86_64&lt;BR /&gt;&lt;BR /&gt;This is a new installation and we've successfully presented the san volumes from the DS8100 to Linux (RHEL and Oracle Linux).&lt;BR /&gt;&lt;BR /&gt;For multipath I have two options in my mind.&lt;BR /&gt;&lt;BR /&gt;1. Emulex Multipulse.&lt;BR /&gt;2. Device Mapper Multipath.&lt;BR /&gt;&lt;BR /&gt;I've already configured both on two blades and everything works fine but it seems Multipulse is preferable because it abstracts all the redundant path devices.&lt;BR /&gt;&lt;BR /&gt;Searching on IBM DS8100 site for Multipulse I was unable to find any recommendations nor oppositions for Multipulse.&lt;BR /&gt;&lt;BR /&gt;Ths support site for DS8100 provides a multipath.conf file to configure Device Mapper for RHEL 5.&lt;BR /&gt;&lt;BR /&gt;Are there any good reasons to stick with device mapper rather than using multipulse?&lt;BR /&gt;&lt;BR /&gt;Your opinions are much appreciated.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Shiraj.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. This thread has been moved&amp;nbsp;from General to &amp;gt; Linux &amp;gt; System Administration. - Hp Forum moderator&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2015 04:24:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/multipulse-or-device-mapper-multipath/m-p/4344486#M54711</guid>
      <dc:creator>Shiraj Fernando</dc:creator>
      <dc:date>2015-04-27T04:24:32Z</dc:date>
    </item>
  </channel>
</rss>

