We have some Sun storage arrays which require RDAC for multipathing
and here is the configuration we are using successfully. I have not
tried to boot from the SAN with it, but this works for us:
device {
vendor "SUN"
product "*"
selector "round-robin 0"
path_grouping_policy group_by_prio
path_checker tur
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_rdac /dev/%n"
failback immediate
rr_min_io 100
rr_weight priorities
polling_interval 1
user_friendly_names yes
}
With the Sun RDAC stuff, one key was to use TUR instead of readsector0
because a failover path in RDAC should have no IO going against it.
You have "rdac" listed in your path checker, not sure if that'll work
or not but I do know that this works for me.
-Dave.
On Tue, Nov 10, 2009 at 9:19 PM, D Canfield <[email protected]> wrote:
>
> ----- Original Message -----
> From: "Win Htin" <[email protected]>
> To: [email protected]
> Sent: Tuesday, November 10, 2009 4:01:43 PM
> Subject: [rhelv5-list] multipath and rdac driver
>
> My questions are;
> 1. Do I need to install the rdac package from LSI website or the
> multipath RPM good enough to proceed with assigning more partitions
> and configure DMpath?
> 2. Can I enable both paths from each HBA for a total of FOUR? (two
> active/two passive). Searching on the web, I found articles saying it
> is not supported natively.
>
> 1. I do believe the two are mutually exclusive. Just stick with the contents
> of RHEL, assuming you're running 5.3 or greater (5.2 and older lacked the
> rdac module).
> 2. I'm currently running only the one path, but VMware ESX 3.5 seems to
> require both paths to be connected (this is explained in their best practices
> manual, and there is no way to set a preferred path). I've connected it this
> way on my test SAN (a DS4100), and it seems to work, but I haven't
> extensively tested it yet.
>
> If you're booting from the SAN, you will need to add a line to
> /etc/sysconfig/mkinitrd/modules so that the rdac module gets included in the
> initrd. I don't have access to my config files at the moment, so I'll try to
> remember to follow up with that (and the contents of *my* multipath.conf)
> tomorrow.
>
> It's been a looooooooong road, but it's nice to see the bladecenter,
> DS4000's, and RHEL finally playing nice together without a lot of manual
> labor after every kernel bump!
>
>
>
> --
> Dana Canfield
> Sr. Systems Administrator
> University of Indianapolis
>
> _______________________________________________
> rhelv5-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhelv5-list
>
--
Dave Costakos
mailto:[email protected]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
