Originally posted by: sirket

I have a small development lab that is using a ZFS storage array as a back end for iscsi/fiberchannel access and the disks are not recognized as being MPIO devices. Our production systems all use NetApp storage and work fine.

Since this is only a small development lab, I am comfortable with adding my own MPIO device entries and using this as an unsupported configuration. Unfortunately I'm not clear on how devices are matched against ODM and/or how I would determine what entry to add to get my disks recognized.

Specifically I am unclear how to determine what deflt and values strings to supply to get these disks recognized.

Any help would be appreciated.

Thanks-

PdAt:
uniquetype = "disk/fcp/mpioosdisk"
attribute = "mpio_model_map"
deflt = "<??????>"
values = "<?????>>"
width = ""
type = "R"
generic = ""
rep = "s"
nls_index = 0

Originally posted by: sirket

So we've taken the output of am odmget command and we end up with something like this:

uniquetype = "disk/iscsi/mpioosdisk"
attribute = "mpio_model_map"
deflt = "080BNETAPP LUN,6005V3020/V3040/V3050/V3070/V3140/V3160/V3170/V6030/V6040/V607/V6080"
values = "040C80:6005:*|21|8|*|*|*|*|*|60"
...

The "deflt" field above seems to contain the Vendor ID of the target as well as the Product ID as would be reported from a NetApp disk:

1. lscfg -vps -l hdisk2

hdisk2 MPIO Other iSCSI Disk Drive

Manufacturer................NETAPP
Machine Type and Model......LUN

Having said that- can anyone explain how that string is matched (Does it just use the Vendor and Product ID's strung together?)- and how the other parts of that field work (what effect does a / have versus a comma, etc.)?

Secondly- what about the values field? Again we have a ton of values. Some seem to correspond to common NetApp values like queue size and timeout but what about the rest of those fields? IBM must have a doc that explains this but I have not been able to find it yet.

Thanks in advance.

Originally posted by: sirket

So here is some additional information:

Our Vendor ID is "OI" (OpenIndiana- the OpenSolaris derivative).

We've added the following entry to our ODM:
PdAt:
uniquetype = "disk/fcp/mpioosdisk"
attribute = "mpio_model_map"
deflt = "0808OI "
values = "081083"
width = ""
type = "R"
generic = ""
rep = "s"
nls_index = 0

The String "OI " Matches our vendor ID and the disks now come in as "MPIO Other FC SCSI Disk Drive"

There are two problems however- First- we have no idea what the 0808 before OI means nor what the value 081083 in the values field means.

Second- we get the following error when running cfgmgr:
Method error (/usr/lib/methods/cfg_vt_scdisk -l vtscsi1 ):
0514-036 Cannot perform the requested function because of
missing customized information in the device configuration
database.

The disks seem to work- but we still seem to be missing some important information.

If anyone knows anything about these fields and/or this error and could supply information- it would be greatly appreciated.

Thanks-

Originally posted by: AlexFerguson

I am attempting to do this same thing, except with a FibreChannel array that we're developing in-house. Like @sirket 0a5cc1eb-8997-479d-86e0-43d275555fb9 5 years ago, I'm able to see and mount the volumes as non-mpio disks. I'm trying to figure out what to put into ODM to trick AIX into doing mpio, at least as a proof of concept.​

Has anybody got a hint on how to do this, or alternatively, is there some route we should go through with IBM towards making this a supported device?

 

Thanks!

Alex