<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Rdac on BAFM</title><link>https://christian.blog.pakiheim.de/tags/rdac/</link><description>Recent content in Rdac on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sat, 16 Aug 2014 09:56:43 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/rdac/index.xml" rel="self" type="application/rss+xml"/><item><title>IBM RDAC and Windows Cluster Service</title><link>https://christian.blog.pakiheim.de/posts/2014-08-16_ibm-rdac-and-windows-cluster-service/</link><pubDate>Sat, 16 Aug 2014 09:56:43 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=328</guid><description>&lt;p&gt;Okay, so we received a brand new &lt;a href="http://www-03.ibm.com/systems/x/hardware/rack/x3650/index.html"&gt;x3650&lt;/a&gt; the other day entitled to replace one (or better two) of our NAS frontend servers. We installed Windows on it the other day (had to create a custom Windows Server 2003 CD first, since the default one doesn&amp;rsquo;t recognize the integrated ServeRAID), and we prepped the box during the week with the usual things.&lt;/p&gt;
&lt;p&gt;On Monday I started installing the &amp;quot; &lt;a href="http://www-947.ibm.com/support/entry/portal/sdd?brand=5000028&amp;amp;key=5329827&amp;amp;osKey=0#5365978"&gt;&lt;em&gt;IBM StorageManager RDAC&lt;/em&gt;&lt;/a&gt;&amp;quot; MultiPath driver (since the box got two single port PCIe FC-HBA&amp;rsquo;s) and figured I&amp;rsquo;d be nice if we had this. I asked a IBM Systems Engineer of one of our partners, which told me generally there wouldn&amp;rsquo;t be a problem with Microsoft Cluster Services (MSCS) and the IBM MPIO driver. Only requirement would be that I&amp;rsquo;d install the new storport.sys driver (version 5.2.3790.4021) first (as in Microsoft &lt;a href="http://support.microsoft.com/kb/932755/en"&gt;KB932755&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>IBM RDAC: Installing the driver for a (not yet) running version</title><link>https://christian.blog.pakiheim.de/posts/2014-08-08_ibm-rdac-installing-the-driver-for-a-not-yet-running-version/</link><pubDate>Fri, 08 Aug 2014 09:04:36 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2029</guid><description>&lt;p&gt;Well, kernel updates on our Linux servers running IBM&amp;rsquo;s RDAC driver (developed by &lt;a href="http://www.lsi.com/rdac/ds4000.html#current"&gt;LSI&lt;/a&gt;) is a real pest .. especially if you have to reboot the box two times in order to install the drivers/initrd correctly.&lt;/p&gt;
&lt;p&gt;So I sat down and looked at the Makefile. Turns out, it just needs four tweaks in order to be working with a different kernel version (which you have to pass using environment variables to make).&lt;/p&gt;</description></item><item><title>Novell KMP: KMP'ing IBM's RDAC driver</title><link>https://christian.blog.pakiheim.de/posts/2014-08-08_novell-kmp-kmp-ing-ibm-s-rdac-driver/</link><pubDate>Fri, 08 Aug 2014 09:03:51 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2033</guid><description>&lt;p&gt;Well, after yesterday&amp;rsquo;s lesson about &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-08_ibm-rdac-installing-the-driver-for-a-not-yet-running-version" title="IBM RDAC: Installing the driver for a (not yet) running version"&gt;getting the IBM RDAC to install for a not-yet-running kernel&lt;/a&gt;, I decided to take it a step further. Novell does have some &lt;a href="http://developer.novell.com/wiki/index.php/Creating_a_Kernel_Module_Source_RPM"&gt;documentation about KMP&amp;rsquo;s&lt;/a&gt;, which is actually rather good, especially the &lt;a href="http://www.suse.de/~agruen/KMPM/old/KernelModulePackagesManual-CODE10.pdf"&gt;guide written by Andreas Grünbacher&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;After a short tinkering, I got it actually working. I was kinda surprised, at how easily it actually is. One problem I still have to deal with, is modifying the %post, to generate the mpp-initrd image. For now, the KMP only contains the default %post, which updates the modules.* stuff.&lt;/p&gt;</description></item><item><title>Novell KMP: Useable version of ibm-rdac-ds4000</title><link>https://christian.blog.pakiheim.de/posts/2014-08-08_novell-kmp-useable-version-of-ibm-rdac-ds4000/</link><pubDate>Fri, 08 Aug 2014 09:03:03 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2042</guid><description>&lt;p&gt;After some more tinkering, a lot more looking at the macros in /usr/lib/rpm/rpm-suse-kernel-module-subpackage and /usr/lib/rpm/suse_macros, I think I finally have a usable RPM&amp;rsquo;ified version of IBM&amp;rsquo;s Multipathing driver ready for use.&lt;/p&gt;
&lt;p&gt;There is still one major annoyance left: each time you install a new ibm-rdac-ds4000-kmp RPM, you also need to reinstall the corresponding ibm-rdac-ds4000-initrd package, as the macros in /usr/lib/rpm don&amp;rsquo;t allow for custom %post or %postun.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-08_novell-kmp-kmp-ing-ibm-s-rdac-driver" title="Novell KMP: KMP'ing IBM's RDAC driver"&gt;As mentioned before&lt;/a&gt;, I&amp;rsquo;m gonna send them to LSI/IBM for review, and maybe, MAYBE they are actually gonna make use of that.&lt;/p&gt;</description></item><item><title>New IBM RDAC version (or not)</title><link>https://christian.blog.pakiheim.de/posts/2009-09-09_new-ibm-rdac-version-or-not/</link><pubDate>Wed, 09 Sep 2009 20:03:30 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2577</guid><description>&lt;p&gt;A week ago (September 02nd), I received a mail detailing the release of IBM&amp;rsquo;s new multipathing device driver for the DS4x00 series, which finally works with SLES11 (the available software up till now doesn&amp;rsquo;t &amp;ndash; as in fails with kernels &amp;gt; 2.6.26 iirc).&lt;/p&gt;
&lt;figure&gt;
&lt;img loading="lazy" src="https://christian.blog.pakiheim.de/uploads/2009/09/ibm-rdac-new-version.png"
alt="ESC&amp;#43; notification detailing the release" width="450"/&gt; &lt;figcaption&gt;
&lt;p&gt;ESC+ notification detailing the release&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;There wouldn&amp;rsquo;t be any trouble, if IBM (or rather the vendor providing the driver &amp;ndash; LSI) would actually release the driver &amp;hellip; up till today, I have yet to see the new version appear on the &lt;a href="http://www.lsi.com/rdac/ds4000.html"&gt;download page&lt;/a&gt;. I already tried to notify IBM about the trouble, but as usual there is lack of ways to actually get this to the right person.&lt;/p&gt;</description></item><item><title>Microsoft Cluster Services powered by IBM</title><link>https://christian.blog.pakiheim.de/posts/2008-07-26_microsoft-cluster-services-powered-by-ibm/</link><pubDate>Sat, 26 Jul 2008 18:47:46 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=691</guid><description>&lt;p&gt;If you think back, I talked about &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-16_windows-cluster-service-continued" title="Windows Cluster Service (continued)"&gt;my problems&lt;/a&gt; with &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-16_ibm-rdac-and-windows-cluster-service" title="IBM RDAC and Windows Cluster Service"&gt;MSCS while utilizing the IBM RDAC Multipath&lt;/a&gt; driver for Windows.&lt;/p&gt;
&lt;p&gt;Everyone I talked to about this, including our IBM business partner and it&amp;rsquo;s systems engineers; as well as some IBM systems engineer (who in fact was an freelance guy hired by IBM), told me it had to do with how we did the zoning (stuffing every controller into a single zone), and that would be the reason why the x3650 was seeing that many drives.&lt;/p&gt;</description></item></channel></rss>