RE: Using different configuration for arrays with identicalvendor/product

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Tore.

	You should be able to use the emc_handler for both arrays.
Depending on the distro you are using only implicit ALUA is supported,
explicit ALUA is in being worked on for upcoming distros. Whether the
storage group within the array attached to the server is ALUA or not is
determined by the failover mode you set for the host on that array. At
the server side you will not know the difference between the two
failover modes, PNR or ALUA.

Regards,
Wayne.
EMC Corp 

-----Original Message-----
From: dm-devel-bounces@xxxxxxxxxx [mailto:dm-devel-bounces@xxxxxxxxxx]
On Behalf Of Tore Anderson
Sent: Friday, March 28, 2008 7:24 AM
To: dm-devel@xxxxxxxxxx
Subject:  Using different configuration for arrays with
identicalvendor/product

Hey.  I've got an EMC CX200 and a CX3-40 in my SAN.  The latter one
supports ALUA, which I'm using as much as I can, the former does not.
The hosts need to be able to access volumes on both the arrays at the
same time.

Unfortunately the volumes on both of these boxes have vendor <DGC> and
product <RAID 5>, so making two different device sections for them with
different hardware_handler and path_checker settings isn't trivial.  I
figured I could simply override the two settings in the multipath{}
blocks for volumes on the CX200, making the device{} block specific for
the CX3-40.  Doesn't appear to work, though, the path_checker- and
hardware_handler-settings in the multipath{} blocks appears to be
silently ignored.

Am I out of luck or is there any other way to do what I want?

For reference, this is the device section I use for the CX200 in
standard <trespassing> mode:

device {
  vendor               DGC.*
  product              RAID.*
  hardware_handler     "1 emc"
  path_checker         emc_clariion
  prio_callout         "/sbin/mpath_prio_emc /dev/%n"
  features             "1 queue_if_no_path"
  path_grouping_policy group_by_prio
  failback             immediate
}

And for the CX3-40 in ALUA mode:

device {
  vendor               DGC.*
  product              RAID.*
  hardware_handler     "0"
  path_checker         tur
  prio_callout         "/sbin/mpath_prio_emc /dev/%n"
  features             "1 queue_if_no_path"
  path_grouping_policy group_by_prio
  failback             immediate
}

These both work fine on hosts that only connect to one of the arrays at
a time.

Regards
-- 
Tore Anderson

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel


--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux