Curious MPxIO problem

Hello folks,
I have a newly installed Solaris 10 system running on a T6320 blade. I have set up LDM with the intent to move an ldom from another blade to this one. So far, so good.

I had the SAN folks make the LUNs belonging to the ldom visible to my new blade and I can see them, all 4 paths. I have run stmsboot and I still see all 4 paths. I have disabled and re-enabled multipath with stmsboot (reboots both times).

On the old blade I see a single path, and the ldom config is based on that, so I want to get mpxio to work, but obviously I need to be careful not to trash the existing data on the LUNs. Anyone have any ideas to try?

root@Antinous:~#mpathadm list initiator-port
Initiator Port:  iqn.1986-03.com.sun:01:00144fefa2b0.4c98c071,4000002a00ff
Initiator Port:  2101001b32a12a83
Initiator Port:  2100001b32812a83
Initiator Port:  2101001b32a15183
Initiator Port:  2100001b32815183
root@Antinous:~#mpathadm list lu
root@Antinous:~#cfgadm -la
Ap_Id                          Type         Receptacle   Occupant     Condition
PCI-EM0                        fibre/hp     connected    configured   ok
PCI-EM1                        fibre/hp     connected    configured   ok
c0                             scsi-sata    connected    configured   unknown
c0::dsk/c0t0d0                 disk         connected    configured   unknown
c1                             fc-fabric    connected    configured   unknown
c1::500a098597e9755e           disk         connected    configured   unknown
c1::500a098887e9755e           disk         connected    configured   unknown
c2                             fc           connected    unconfigured unknown
c3                             fc-fabric    connected    configured   unknown
c3::500a098587e9755e           disk         connected    configured   unknown
c3::500a098897e9755e           disk         connected    configured   unknown
c4                             fc           connected    unconfigured unknown
usb0/1                         unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok
usb0/3                         unknown      empty        unconfigured ok
usb1/1                         unknown      empty        unconfigured ok
usb1/2                         unknown      empty        unconfigured ok
usb2/1                         unknown      empty        unconfigured ok
usb2/2                         unknown      empty        unconfigured ok
usb2/3                         usb-hub      connected    configured   ok
usb2/3.1                       unknown      empty        unconfigured ok
usb2/3.2                       unknown      empty        unconfigured ok
usb2/3.3                       unknown      empty        unconfigured ok
usb2/3.4                       unknown      empty        unconfigured ok
usb2/4                         unknown      empty        unconfigured ok
usb2/5                         unknown      empty        unconfigured ok
usb3/1                         unknown      empty        unconfigured ok
usb3/2                         unknown      empty        unconfigured ok
usb3/3                         unknown      empty        unconfigured ok
usb4/1                         unknown      empty        unconfigured ok
usb4/2                         unknown      empty        unconfigured ok
usb5/1                         unknown      empty        unconfigured ok
usb5/2                         unknown      empty        unconfigured ok
usb5/3                         unknown      empty        unconfigured ok
usb5/4                         unknown      empty        unconfigured ok
usb5/5                         unknown      empty        unconfigured ok

To enable it, edit the file /kernel/drv/fp.conf file. At the end it should say:

mpxio-disable="yes"

Just change yes to no and it will be enabled:

mpxio-disable="no"

Hope this works

I've yet to see a Solaris 10 install that has MPxIO disabled out-of-the-box in /kernel/drv/fp.conf.

Do the LUNs show up under format?

Have you run devfsadm?

What's the output from fcinfo? See the man page of that command for options.

If you're still stumped, it may be easier to just "reboot -- -r".

who's the SAN vendor ?

I recently faced a similar problem with HP storage and stms on Solaris. There're some known issues.

I could have sworn I posted this yesterday . . .

I have resolved the problem. The SAN storage administrator had forgotten to enable ALUA on the NetApp end. Once he did that, and I disabled and re-enabled with the stmsboot command, I've got single images of the LUNs and everything is fine.