Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Oracle VM 3.0.3 cant Add Storage EMC CLARiiON CX4 Model 240

909818Jan 9 2012 — edited Jan 14 2012

Hi all,

has any of you ever had the problem here?

- Freshly installed Oracle VM Server 3.0.3
Since hanging behind an EMC CLARiiON CX4 Model 240th

When I type:

[root@servername ~]# multipath -ll
[root@servername ~]#

Nothing comes.

--
When I type:

[root@servername ~]# multipath -v2 -d
Jan 09 14:33:52 | sdc: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdd: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sde: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdb: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdf: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdg: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdi: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdh: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdj: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdk: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdl: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdm: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdn: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdp: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdq: emc prio: path not correctly configured for failover
Jan 09 14:33:52 | sdo: emc prio: path not correctly configured for failover
create: 36006016017002b00da76fe254b1be111 undef DGC,CX4-240WDVR
size=50G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=0 status=undef
| |- 3:0:0:16385 sdc 8:32 undef faulty running
| `- 4:0:1:16385 sdo 8:224 undef faulty running
`-+- policy='round-robin 0' prio=0 status=undef
|- 4:0:0:16385 sdg 8:96 undef faulty running
`- 3:0:1:16385 sdk 8:160 undef faulty running
create: 36006016017002b00f4d633354b1be111 undef DGC,CX4-240WDVR
size=20G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=0 status=undef
| |- 4:0:0:16386 sdh 8:112 undef faulty running
| `- 3:0:1:16386 sdl 8:176 undef faulty running
`-+- policy='round-robin 0' prio=0 status=undef
|- 3:0:0:16386 sdd 8:48 undef faulty running
`- 4:0:1:16386 sdp 8:240 undef faulty running
create: 36006016017002b00a8f8860a8b37e111 undef DGC,CX4-240WDVR
size=14G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=0 status=undef
| |- 3:0:0:16387 sde 8:64 undef faulty running
| `- 4:0:1:16387 sdq 65:0 undef faulty running
`-+- policy='round-robin 0' prio=0 status=undef
|- 4:0:0:16387 sdi 8:128 undef faulty running
`- 3:0:1:16387 sdm 8:192 undef faulty running
create: 36006016017002b0040b3d9ee4a1be111 undef DGC,CX4-240WDVR
size=200G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=0 status=undef
| |- 3:0:0:16384 sdb 8:16 undef faulty running
| `- 4:0:1:16384 sdn 8:208 undef faulty running
`-+- policy='round-robin 0' prio=0 status=undef
|- 4:0:0:16384 sdf 8:80 undef faulty running
`- 3:0:1:16384 sdj 8:144 undef faulty running

So far so good.

But now when I look in the dmesg, I find this:

[root@servername ~]# dmesg | grep -i device-mapper
[ 12.583976] device-mapper: uevent: version 1.0.3
[ 12.584383] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[ 64.021054] device-mapper: multipath: version 1.1.0 loaded
[ 64.040746] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 64.041517] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.041521] device-mapper: ioctl: error adding target to table
[ 64.146505] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.146507] device-mapper: ioctl: error adding target to table
[ 64.249745] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.249747] device-mapper: ioctl: error adding target to table
[ 64.358748] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.358750] device-mapper: ioctl: error adding target to table
[ 64.448352] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.448354] device-mapper: ioctl: error adding target to table
[ 64.559250] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.559252] device-mapper: ioctl: error adding target to table
[ 64.648305] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.648308] device-mapper: ioctl: error adding target to table
[ 64.755134] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.755136] device-mapper: ioctl: error adding target to table
[ 64.863800] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.863802] device-mapper: ioctl: error adding target to table
[ 64.970677] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 64.970679] device-mapper: ioctl: error adding target to table
[ 65.059904] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.059906] device-mapper: ioctl: error adding target to table
[ 65.166677] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.166679] device-mapper: ioctl: error adding target to table
[ 65.268430] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.268432] device-mapper: ioctl: error adding target to table
[ 65.347575] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.347577] device-mapper: ioctl: error adding target to table
[ 65.380230] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.380232] device-mapper: ioctl: error adding target to table
[ 65.511204] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.511207] device-mapper: ioctl: error adding target to table
[ 65.596132] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.596134] device-mapper: ioctl: error adding target to table
[ 65.658550] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.658551] device-mapper: ioctl: error adding target to table
[ 65.759973] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.759975] device-mapper: ioctl: error adding target to table
[ 65.862650] device-mapper: table: 253:0: multipath: error attaching hardware handler
[ 65.862652] device-mapper: ioctl: error adding target to table

When I look in the / var / log / messages to EMC I find the following:

Jan 6 13:36:01 servername kernel: [ 62.564545] emc: device handler registered
Jan 6 13:36:01 servername kernel: [ 62.573294] device-mapper: multipath round-robin: version 1.0.0 loaded
Jan 6 13:36:01 servername kernel: [ 62.573898] sd 3:0:0:16384: emc: Invalid information section length 128
Jan 6 13:36:01 servername kernel: [ 62.573904] sd 3:0:0:16384: emc: detected Clariion FC (Legacy), flags 1
Jan 6 13:36:01 servername kernel: [ 62.574033] sd 3:0:0:16384: emc: Invalid failover mode 2
Jan 6 13:36:01 servername kernel: [ 62.574036] sd 3:0:0:16384: emc: not attached
Jan 6 13:36:01 servername kernel: [ 62.574062] device-mapper: table: 253:0: multipath: error attaching hardware handler
Jan 6 13:36:01 servername kernel: [ 62.574066] device-mapper: ioctl: error adding target to table
Jan 6 13:36:01 servername kernel: [ 62.632339] IPv6: Loaded, but administratively disabled, reboot required to enable
Jan 6 13:36:01 servername kernel: [ 62.658052] cnic: Broadcom NetXtreme II CNIC Driver cnic v2.2.14 (Mar 30, 2011)
Jan 6 13:36:01 servername kernel: [ 62.671045] Broadcom NetXtreme II iSCSI Driver bnx2i v2.6.2.3 (Jan 06, 2010)
Jan 6 13:36:01 servername kernel: [ 62.671073] iscsi: registered transport (bnx2i)
Jan 6 13:36:01 servername kernel: [ 62.684774] iscsi: registered transport (tcp)
Jan 6 13:36:01 servername kernel: [ 62.768677] iscsi: registered transport (iser)
Jan 6 13:36:01 servername kernel: [ 62.789699] iscsi: registered transport (be2iscsi)
Jan 6 13:36:01 servername kernel: [ 62.983179] sd 3:0:0:16384: emc: Invalid information section length 128
Jan 6 13:36:01 servername kernel: [ 62.983188] sd 3:0:0:16384: emc: detected Clariion FC (Legacy), flags 1
Jan 6 13:36:01 servername kernel: [ 62.983339] sd 3:0:0:16384: emc: Invalid failover mode 2
Jan 6 13:36:01 servername kernel: [ 62.983346] sd 3:0:0:16384: emc: not attached
Jan 6 13:36:01 servername kernel: [ 62.983384] device-mapper: table: 253:0: multipath: error attaching hardware handler
Jan 6 13:36:01 servername kernel: [ 62.983390] device-mapper: ioctl: error adding target to table
Jan 6 13:36:01 servername kernel: [ 63.132545] sd 3:0:0:16385: emc: Invalid information section length 128
Jan 6 13:36:01 servername kernel: [ 63.132554] sd 3:0:0:16385: emc: detected Clariion FC (Legacy), flags 1
Jan 6 13:36:01 servername kernel: [ 63.132687] sd 3:0:0:16385: emc: Invalid failover mode 2
Jan 6 13:36:01 servername kernel: [ 63.132691] sd 3:0:0:16385: emc: not attached
Jan 6 13:36:01 servername kernel: [ 63.132715] device-mapper: table: 253:0: multipath: error attaching hardware handler

[root@servername ~]# ll /dev/disk/by*
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root 9 Jan 9 15:09 scsi-3600508b1001cf3d7f85cf18c0b3be9fd -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 9 15:09 scsi-3600508b1001cf3d7f85cf18c0b3be9fd-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 9 15:09 scsi-3600508b1001cf3d7f85cf18c0b3be9fd-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 9 15:09 scsi-3600508b1001cf3d7f85cf18c0b3be9fd-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 Jan 9 15:09 scsi-36006016017002b0040b3d9ee4a1be111 -> ../../sdn
lrwxrwxrwx 1 root root 9 Jan 9 15:09 scsi-36006016017002b00a8f8860a8b37e111 -> ../../sdq
lrwxrwxrwx 1 root root 9 Jan 9 15:09 scsi-36006016017002b00da76fe254b1be111 -> ../../sdo
lrwxrwxrwx 1 root root 9 Jan 9 15:09 scsi-36006016017002b00f4d633354b1be111 -> ../../sdp

/dev/disk/by-label:
total 0
lrwxrwxrwx 1 root root 10 Jan 9 15:09 1 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 9 15:09 boot -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 9 15:09 SWAP-sda2 -> ../../sda2

/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 10 Jan 9 15:09 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../scd0
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:03:00.0-scsi-0:0:0:1 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 9 15:09 pci-0000:03:00.0-scsi-0:0:0:1-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 9 15:09 pci-0000:03:00.0-scsi-0:0:0:1-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 9 15:09 pci-0000:03:00.0-scsi-0:0:0:1-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016446e02c08:0x4000000000000000 -> ../../sdn
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016446e02c08:0x4001000000000000 -> ../../sdo
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016446e02c08:0x4002000000000000 -> ../../sdp
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016446e02c08:0x4003000000000000 -> ../../sdq
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016d46e02c08:0x4000000000000000 -> ../../sdf
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016d46e02c08:0x4001000000000000 -> ../../sdg
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016d46e02c08:0x4002000000000000 -> ../../sdh
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0b:00.0-fc-0x5006016d46e02c08:0x4003000000000000 -> ../../sdi
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016546e02c08:0x4000000000000000 -> ../../sdb
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016546e02c08:0x4001000000000000 -> ../../sdc
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016546e02c08:0x4002000000000000 -> ../../sdd
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016546e02c08:0x4003000000000000 -> ../../sde
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016c46e02c08:0x4000000000000000 -> ../../sdj
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016c46e02c08:0x4001000000000000 -> ../../sdk
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016c46e02c08:0x4002000000000000 -> ../../sdl
lrwxrwxrwx 1 root root 9 Jan 9 15:09 pci-0000:0e:00.0-fc-0x5006016c46e02c08:0x4003000000000000 -> ../../sdm

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 10 Jan 9 15:09 198077a5-0485-47fb-b398-b271e41f200d -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 9 15:09 8cf36398-6a96-4d57-a019-c88ff91765c5 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 9 15:09 bd9a0321-419e-453e-807f-0a839efbfc4a -> ../../sda1

/etc/multipath.conf

## IMPORTANT for OVS do not blacklist all devices by default.
#blacklist {
# devnode "*"
#}

## By default, devices with vendor = "IBM" and product = "S/390.*" are
## blacklisted. To enable mulitpathing on these devies, uncomment the
## following lines.
#blacklist_exceptions {
# device {
#    vendor "IBM"
#    product "S/390.*"
# }
#}

## IMPORTANT for OVS this must be no. OVS does not support user friendly
## names and instead uses the WWIDs as names.
defaults {
user_friendly_names no
}

# List of device names to discard as not multipath candidates
#
## IMPORTANT for OVS do not remove the black listed devices.
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|nbd)[0-9]*"
devnode "^hd[a-z][0-9]*"
devnode "^etherd"
%include "/etc/blacklisted.wwids"
}

##
## Here is an example of how to configure some standard options.
##
#
#defaults {
# udev_dir /dev
# polling_interval 10
# selector "round-robin 0"
# path_grouping_policy multibus
# getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
# rr_min_io    100
# max_fds   8192
# rr_weight    priorities
# failback immediate
# no_path_retry    fail
# user_friendly_names no
#}
##
## The wwid line in the following blacklist section is shown as an example
## of how to blacklist devices by wwid. The 2 devnode lines are the
## compiled in default blacklist. If you want to blacklist entire types
## of devices, such as all scsi devices, you should use a devnode line.
## However, if you want to blacklist specific devices, you should use
## a wwid line. Since there is no guarantee that a specific device will
## not change names on reboot (from /dev/sda to /dev/sdb for example)
## devnode lines are not recommended for blacklisting specific devices.
##
#blacklist {
# wwid 26353900f02796769
# devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
# devnode "^hd[a-z]"
# devnode "^sd[ab]"
#}
#multipaths {
# multipath {
#    wwid 3600508b4000156d700012000000b0000
#    alias    yellow
#    path_grouping_policy multibus
#    path_selector    "round-robin 0"
#    failback manual
#    rr_weight    priorities
#    no_path_retry    10
# }
# multipath {
#    wwid 1DEC_____321816758474
#    alias    red
# }
#}
devices {
# device {
#    vendor "COMPAQ "
#    product   "HSV110 (C)COMPAQ"
#    path_grouping_policy multibus
#    getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
#    path_selector    "round-robin 0"
#    hardware_handler "0"
#    failback 15
#    rr_weight    priorities
#    no_path_retry    queue
# }
# device {
#    vendor "COMPAQ "
#    product   "MSA1000 "
#    path_grouping_policy multibus
# }
#

#
# IBM DS4100 :: Active-Passive
# IBM storage expert says functionally equivalent to DS4300
#
device {
vendor "IBM"
product   "1724-100"
hardware_handler "1 rdac"
path_grouping_policy group_by_prio
prio    rdac
path_checker rdac
no_path_retry    10
}

#
# IBM DS4400 (FAStT700) :: Active-Passive
# Verified @ Waltham, IBM
#
device {
vendor "IBM"
product   "1742-900"
hardware_handler "1 rdac"
path_grouping_policy group_by_prio
prio    "rdac"
failback immediate
path_checker rdac
no_path_retry    10
}

#
# IBM XIV Nextra - combined iSCSI/FC :: Active-Active
# Verified @ Waltham, IBM
#
device {
vendor "XIV"
product   "NEXTRA"
path_grouping_policy multibus
rr_min_io    1000
path_checker tur
failback immediate
no_path_retry    10
}

#
# Re-branded XIV Nextra
#
device {
vendor "IBM"
product   "2810XIV"
path_grouping_policy multibus
rr_min_io    1000
path_checker tur
failback immediate
no_path_retry    10
}

#
# HP MSA1510i :: Active-Active. Latest firmare (v2.00) supports Linux.
# Tested @ HP, Marlboro facility.
#
device {
vendor "HP"
product   "MSA1510i VOLUME"
path_grouping_policy group_by_prio
path_checker tur
prio    "alua"
no_path_retry    10
}

#
# DataCore SANmelody FC and iSCSI :: Active-Passive
#
device {
vendor "DataCore"
product   "SAN*"
path_grouping_policy failover
path_checker tur
failback 10
no_path_retry    10
}

#
# EqualLogic iSCSI :: Active-Passive
#
device {
vendor "EQLOGIC"
product   "100E-00"
path_grouping_policy failover
failback immediate
no_path_retry    10
}

#
# Compellent FC :: Active-Active
#
device {
vendor "COMPELNT"
product   "Compellent *"
path_grouping_policy multibus
path_checker tur
failback immediate
rr_min_io    1024
no_path_retry    10
}

#
# FalconStor :: Active-Active
#
device {
vendor "FALCON"
product   ".*"
path_grouping_policy multibus
failback immediate
no_path_retry    10
}

#
# EMD FC (ES 12F) and iSCSI (SA 16i) :: Active-Active
# Tested in-house.
device {
vendor "EMD.*"
product "ASTRA (ES 12F)|(SA 16i)"
path_grouping_policy failover
failback immediate
path_checker tur
no_path_retry 10
}
#
# Fujitsu :: Active-Passive (ALUA)
#
device {
vendor "FUJITSU"
product   "E[234]000"
path_grouping_policy group_by_prio
prio "alua"
failback immediate
no_path_retry    10
path_checker tur
}
#
# Fujitsu :: Active-Active
#
device {
vendor "FUJITSU"
product   "E[68]000"
path_grouping_policy multibus
failback immediate
no_path_retry    10
path_checker tur
}
#
# JetStor :: Active-Active
# Tested in-house.
device {
vendor "AC&Ncorp"
product   "JetStorSAS516iS"
path_grouping_policy multibus
failback 15
no_path_retry 10
rr_weight    priorities
path_checker tur
}
#
# Xyratex/Overland :: Active-Active
# Tested in-house
#
device {
vendor "XYRATEX"
product   "F5402E|[FE]5412E|[FE]5404E|F6512E|[FEI]6500E"
path_grouping_policy failover
failback 3
no_path_retry    10
path_checker tur
}

device {
vendor "FUJITSU"
product "ETERNUS_DXL|ETERNUS_DX400|ETERNUS_DX8000"
prio alua
path_grouping_policy group_by_prio
path_selector "round-robin 0"
failback immediate
no_path_retry 10
}
## Device attributes for EMC CLARiiON
device {
vendor "DGC"
product "*"
path_grouping_policy group_by_prio
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_emc /dev/%n"
path_checker emc_clariion
path_selector "round-robin 0"
# features "1 queue_if_no_path"
features "0"
no_path_retry "1"
hardware_handler "1 emc"
failback immediate
}
device {
vendor "ATA*"
product   ".*"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
}

}

These problems continue to exist, whether with a standard or customized multipath.conf
Has anyone of you have any idea?

Best regards
Sven Timmermann

Locked Post

New comments cannot be posted to this locked post.

Locked on Feb 11 2012

Added on Jan 9 2012

#configuration, #installation, #oracle, #oracle-virtualization, #oracle-vm-server-for-x86

2 comments

1,404 views