Rss

  • twitter
  • facebook

Avoid udev rules

Are you like me and hate setting permissions with outside scripts on dm-multipath devices? Best way to avoid this mess (and udev rules to boot) is to include the following on your multipath.conf device:
 
 
 

multipath {
    wwid 360a98000486e58526c34515944703277
    alias devicename
    mode 660
    uid 501
    gid 502
}

What's great about this is when DM-multipath instantiates the new mapper devices, they will all be set with the permissions, user, and group assignments that you want. No muss, no fuss!

Enjoy!

Share on Facebook

Deployement of ALUA with Red Hat and NetApp

I love the idea of having failover on my primary database. So if you haven't done so, I would highly recommend it. With Netapp and Red Hat, here's the skinny:

1) Set up your /etc/multipath.conf to use mpath_prio_alua rather then the default mpath_prio_ontap. I have not verified if mpath_prio_ontap reads the SCSI-3 ALUA commands, but I know the latter does, so it was easier to use it than the former.

2) Set the ALUA on the igroup with:
igroup set alua on

3) Reboot your hosts

4) Enjoy ALUA goodness!

With this configuration, when cf failover is initiated, your Red Hat server will know when the primary path is dead and use the secondary path without intervention. It really is a beautiful thing, and I recommend it for any storage heads out there.

Share on Facebook
This site is using Web Stats, created by emailextractor14.com