hpacucli doesn't detect MSA1500 after OS upgrade

[toomas_aas]

Hello!

I was running SLES10 SP2, attached to MSA1500cs via dual-pathed configuration using two FC switches. I could run hpacucli and it successfully did all the needed tasks on the MSA1500.

Now I upgraded my server to SLES10 SP3 and hpacucli no longer detects the MSA1500 controller, it only sees the server's integrated Smart Array controller.

With SLES10 SP2 I was using the HP QLogic driver to manage the multipathing. Since this is no longer supported with SLES10 SP3, I removed the HP QLogic driver and am now using the Linux in-box driver with device mapper multipathing. Is there a way to still use hpacucli for managing the MSA1500 in this configuration? Is anyone running hpacucli with SLES10 SP3, or SLES11 ?

The version of hpacucli I'm running now is 8.60-8.0

[Sivaramakrishna_1 · Accepted solution]

Hi,

As per HP Docs, There is no support for MSA 1500 for SLES10SP3 onwards.

NOTE: Beginning with SLES 11, HP no longer supports the following arrays: MSA1000, MSA1500, EVA3000, EVA5000, XP128, and XP1024. Beginning with RHEL 5.3 and SLES 10 SP3, HP no longer supports the following arrays: MSA1000, MSA1500, EVA3000, and EVA5000. Beginning with RHEL 6.0, HP no longer supports the XP128 and XP1024.

But you can try by installing the fc enablement kit from the below link. It may work even though there is no support from HP.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=3709945&prodSeriesId=1844104&swItem=co-82357-1&prodNameId=1844105&swEnvOID=2065&swLang=8&taskId=135&mode=4&idx=0

Regards,
Siva

[Venkadesh Kannan]

You can check the support matrix at
www.hp.com/storage/spock

[toomas_aas]

Thanks a lot, Siva! After installing the Enablement Kit that you pointed out, hpacucli is again able to see the MSA. It seems, though, that SAN failover is a bit more problematic after installing the Enablement Kit installed than it was before. It does work, but takes something like 3-4 minutes and it seems that the entire adapter is being reset in the process (which didn't happen before). Maybe I need to adjust some of the qla2xxx module parameters in /etc/modprobe.conf.local. Currently they are:

options qla2xxx ql2xmaxqdepth=16 ql2xloginretrycount=30 qlport_down_retry=10

But overall, things look rather good.