Based on documentation provided by the manufacturer:
http://support2.imation.com/downloads/nxs/crmkb5/Nexsan_Multipathing_Best_Practices_Guide.pdf

Cc: Christophe Varoqui <christophe.varo...@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Signed-off-by: Xose Vazquez Perez <xose.vazq...@gmail.com>
---
 libmultipath/hwtable.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
index 637be3d..9a968a7 100644
--- a/libmultipath/hwtable.c
+++ b/libmultipath/hwtable.c
@@ -905,6 +905,27 @@ static struct hwentry default_hw[] = {
                .prio_name     = PRIO_ALUA,
                .no_path_retry = 10,
        },
+       /*
+        * Imation/Nexsan
+        */
+       {
+               /* E-Series */
+               .vendor        = "NEXSAN",
+               .product       = "NXS-B0",
+               .pgpolicy      = GROUP_BY_PRIO,
+               .pgfailback    = -FAILBACK_IMMEDIATE,
+               .prio_name     = PRIO_ALUA,
+               .no_path_retry = 15,
+       },
+       {
+               /* SATABeast / SATABoy */
+               .vendor        = "NEXSAN",
+               .product       = "SATAB",
+               .pgpolicy      = GROUP_BY_PRIO,
+               .pgfailback    = -FAILBACK_IMMEDIATE,
+               .prio_name     = PRIO_ALUA,
+               .no_path_retry = 15,
+       },
 #if 0
        /*
         * Copy this TEMPLATE to add new hardware.
-- 
2.10.1

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

Reply via email to