Skip to main content

RHEL4 with dm-multipath on root


I got a mail today from another group working with Linux servers on Dell PE2950's. They have HP EVA boxes as their SAN, instead of our EMC DMX-3/4, and wanted to know how we got multi-pathing to work in Oracle's Enterprise Linux 4, update 5. They had heard that it was terrible and were thinking of using RHEL/OEL 5u2 instead. I told them, we were using PowerPath for this reason, and because EMC would only support us iff we used PowerPath. dm-multipath was not supported. Hmmm. Fair enough...

While dm-multipathing is available in OEL 4u5, you have to go through some tricks to get it to support your root volume over dm-multipath. TuxyTurvy has instructions and people report it works. The trick he uses is to make a custom initrd image. Another solution may be to use HP StorageWorks for Linux or HP's own dm-multipath.

Update: We going a different route... We'll install ESX 3.5 on the Dell servers and install Linux in VMs only, virtualizing the whole setup. ESX is compatible with the HP EVA and provides us with a nice path for the future. The Linux LSI drivers in the VM will work nicely with ESX and SAN and using VMware prevents the need for multipath HBAs.

Comments

Popular posts from this blog

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size <==== 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries <==== 20 seconds time to live for negative entries

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.

Setting up SR-IOV in RHEL6 on PowerEdge servers

Dell Community : "RHEL 6 provides SR-IOV functionality on supported hardware which provides near native performance for virtualized guests. Single-Root I/O Virtualization (SR-IOV) specification, introduced by PCI-SIG details how a single PCIe device can be shared between various virtualization guests. Devices capable of SR-IOV functionality support multiple virtual functions on top of the physical function. Virtual Function is enabled in hardware as a light weight PCIe function. Operating System cannot discover this function as it does not respond to the PCI bus scan and requires support in the host’s driver. As in PCIe pass-through, a Virtual function of a SR-IOV capable card can be directly assigned to the guest operating system. A virtual function driver running in the guest manages this device."